I've got 1.6 "stable" version on my 1043nd 1.0, everything worked fine for few months. But today morning suddenly my router goes into infinite reboot loop. I've got the same issue 1,5 year ago with experimental software and a half year ago wit 1.4.7 version.
Reset didn't solve the problem this time. I cannot connect to the router via ethernet.
This model 1043nd is most painful experience i've ever had. It is considered the most stable unit with openwrt. But it isn't. It works stable for few months and turns into infinite loop. This repeats every few months. And wifi issue is still not fixed. I have to reset wifi every 1-2 weeks because the connection extremely slowes down or just hangs.
Please tell me how to fix it, because i don't have a strength to fight this annoying piece of crap.
Serious hardware problem. Infinite loop 1043ND
Moderator: Moderators
Re: Serious hardware problem. Infinite loop 1043ND
Hi i had my 1043ND
crash and get stuck in a bootloop wen testing a build of openwrt. how i got it back up again is by setting a static ip on my comp of 192.168.1.2 and putting a ethernet kable in to the wan port and starting a ping -t to 192.168.1.1 with the router switched off. then turn on the router wate for 2 seconds and then start tapping the wds / reset button until you get a ping from the router. then you are in safe mode and you can telnet in to the router.
In failsafe mode
You get a message similar or same like this (using OpenWrt 12.09):
=== IMPORTANT ============================
Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------
BusyBox v1.19.4 (2013-03-14 11:28:31 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
ATTITUDE ADJUSTMENT (12.09, r36088)
-----------------------------------------------------
* 1/4 oz Vodka Pour all ingredients into mixing
* 1/4 oz Gin tin with ice, strain into glass.
* 1/4 oz Amaretto
* 1/4 oz Triple sec
* 1/4 oz Peach schnapps
* 1/4 oz Sour mix
* 1 splash Cranberry juice
-----------------------------------------------------
root@(none):/#
NOTE: The root file system in failsafe mode is the only the
SquashFS
partition. The JFFS2 is not present. To mount JFFS2 in read-write mode run
mount_root:
mount_root
and then repair your system:
list of 3 items
•
In case you forgot your password, you need to set a new one. Type:passwd
•
In case you forgot the routers IP address, get it withuci get network.lan.ipaddr
•
In case you filled up the entire JFFS2 by installing too big/too many packages, clean the entire JFFS2 partition. All settings will be reset and all installed
packages are removed. (OpenWrt equivalent of a factory reset)firstbootor (this will reboot the device as part of the process) mtd -r erase rootfs_dataor
rm -r /overlay/*
list end
If you are done with failsafe mode use
reboot -fto reboot. Note: Normal /sbin/reboot will not work, because init is not running. Or power cycle the router.
sorce:: http://wiki.openwrt.org/doc/howto/generic.failsafe
crash and get stuck in a bootloop wen testing a build of openwrt. how i got it back up again is by setting a static ip on my comp of 192.168.1.2 and putting a ethernet kable in to the wan port and starting a ping -t to 192.168.1.1 with the router switched off. then turn on the router wate for 2 seconds and then start tapping the wds / reset button until you get a ping from the router. then you are in safe mode and you can telnet in to the router.
In failsafe mode
You get a message similar or same like this (using OpenWrt 12.09):
=== IMPORTANT ============================
Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------
BusyBox v1.19.4 (2013-03-14 11:28:31 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
ATTITUDE ADJUSTMENT (12.09, r36088)
-----------------------------------------------------
* 1/4 oz Vodka Pour all ingredients into mixing
* 1/4 oz Gin tin with ice, strain into glass.
* 1/4 oz Amaretto
* 1/4 oz Triple sec
* 1/4 oz Peach schnapps
* 1/4 oz Sour mix
* 1 splash Cranberry juice
-----------------------------------------------------
root@(none):/#
NOTE: The root file system in failsafe mode is the only the
SquashFS
partition. The JFFS2 is not present. To mount JFFS2 in read-write mode run
mount_root:
mount_root
and then repair your system:
list of 3 items
•
In case you forgot your password, you need to set a new one. Type:passwd
•
In case you forgot the routers IP address, get it withuci get network.lan.ipaddr
•
In case you filled up the entire JFFS2 by installing too big/too many packages, clean the entire JFFS2 partition. All settings will be reset and all installed
packages are removed. (OpenWrt equivalent of a factory reset)firstbootor (this will reboot the device as part of the process) mtd -r erase rootfs_dataor
rm -r /overlay/*
list end
If you are done with failsafe mode use
reboot -fto reboot. Note: Normal /sbin/reboot will not work, because init is not running. Or power cycle the router.
sorce:: http://wiki.openwrt.org/doc/howto/generic.failsafe
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
NETGEAR Nighthawk R7800
NETGEAR R6260
Re: Serious hardware problem. Infinite loop 1043ND
@tapper
Thank You very much for solution.
First of all i have to admin that failsafe method did'nt work, because setting ip manually then resetting, tapping wds button didn't work. I could not get ping response, it looked like the router bricked itself. Only sys diode was blinking all the time. Maybe it was internal memory failure?
My anger pushed me to follow the unbricking method.
What i've done was:
1. Disassembly the unit.
2. Solder 4 pins in P1 section
3. connect via ttl cable
4. Getting to the command mode via putty
5. restore sysupgrade firmware using putty / tftp
It finally worked, and the control over the unit was restored.
But i'm afraid that my problem is still not fixed and the same issue will occur in next few months. Like i said it wasn't the first time with similar issue.
Im pretty sure that this could be faulty memory issue.
Is there any procedure to run memory check on this hardware?
Thank You very much for solution.
First of all i have to admin that failsafe method did'nt work, because setting ip manually then resetting, tapping wds button didn't work. I could not get ping response, it looked like the router bricked itself. Only sys diode was blinking all the time. Maybe it was internal memory failure?
My anger pushed me to follow the unbricking method.
What i've done was:
1. Disassembly the unit.
2. Solder 4 pins in P1 section
3. connect via ttl cable
4. Getting to the command mode via putty
5. restore sysupgrade firmware using putty / tftp
It finally worked, and the control over the unit was restored.
But i'm afraid that my problem is still not fixed and the same issue will occur in next few months. Like i said it wasn't the first time with similar issue.
Im pretty sure that this could be faulty memory issue.
Is there any procedure to run memory check on this hardware?
Re: Serious hardware problem. Infinite loop 1043ND
I am sorry mate i just don't no. i am afraid that you got more complex than i wood have lol i wood of just put it in the trash. most of what i did i just found on google and the openwrt forum. well dun tho mate! i am glad you got it up and running again. may be it's time to have a look on ebay and see what cheep routers are floting around?
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
NETGEAR Nighthawk R7800
NETGEAR R6260