LOM: I have checked again the wires. With respect to the same schematic at pinouts.ru, the red one is connected to the pin 2 (charger ground) and the yellow one is connected to the pin 3 (ACI) of the Nokia plug. Consequently, I don't know where to connect the 3.3V of the WRT160NL board.
My 5-wire cable had pin 2,3,4,6,and 7 connected.
No data ground, only "charger ground".
Data ground at pinouts.ru is also listed as "USB gnd", maybe you should use charger ground instead as I had to do? _________________ Kernel panic: Aiee, killing interrupt handler!
Well, that's confusing! I have performed more checks and the results are the same: red -> 2, yellow -> 3, white -> 6, green -> 7 and blue -> 8. Do you use the charger ground (pin 2) to connect to the WRT160NL board ground? As far as I know, there are cases where the signal ground is different than the power ground.
Well, using the ground at pin 2 seems to work fine! I can see a beautiful boot process followed by a kernel panic! Maybe that's why my router was bricked...!
You can stop the autoboot process by sending lots of Ctrl-C immediately when you see some text from the CFE appearing on the screen.
You will then get a U-Boot prompt and can see the available U-Boot cmds by typing ? or help.
There are cmds for starting a tftp firmware update and you are now not limited to the short tftp transfer window which you normally have before the kernel boots.
Start the tftp transfer on your computer just before you have given the U-Boot tftp command. _________________ Kernel panic: Aiee, killing interrupt handler!
Thank you, LOM. I have seen there was only one second to stop the boot process! Eventually, I have managed to send the linksys firmware (because I was sure it was working) and revive the router. The sequence was classic: Ctrl + C to stop the boot process, upgrade code.bin in the uboot prompt to receive the firmware, go to boot the router once the firmware was completely received and flashed. I find the restore process quite difficult. I would change the uboot to wait 3 seconds and make one of the LEDs blinking while uboot waits. If a user presses a button on the router (for instance, the one near the Wireless LED) or a combination, the boot process stops and waits for a firmware via tftp.
There is not much to do about the method to get into recovery mode unless one flashes a custom made U-Boot,
the U-Boot boot loader is not part of the dd-wrt firmware or the original Linksys firmware.
Flashing a new boot loader is also a risky operation because if something goes wrong during flashing then there is no way back.
I think we have to live with it as it is, you have now a serial cable and can provide the developers with boot and firmware logs if something should go wrong in the future. _________________ Kernel panic: Aiee, killing interrupt handler!
I` follow this guide and i` unable stop autoboot i` try three different TTL adapter one is ca-42, second is the same like in guide and third is MicroNova serial adaptor ,test with twisted(shorted) wires Tx Rx is ok i see output.but unable stop booting Plaess Help (F1)(F1)(F1)
Posted: Fri May 02, 2014 13:13 Post subject: Bricked wrt160nl
Hi, I also bricked and unbricked a Linksys wrt160nl
What is did was to get original Linksys firmware.
Rename it to code.bin
power on the router and withing a few seconds start;
tftp -I 192.168.1.1 put code.bin
Try it a few times if it doesnot work.
BTW. anyone noticed that the macaddresses of the dd-wrt firmware for the wrt160nl are incorrect!!!!
So if you have more then one, the are having the same mac address in the network, which have strange effects.