OpenWrt Forum Archive

Topic: Bricked Linksys wrt54g 1.1

The content of this topic has been archived on 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I've got an old Linksys wrt54g v1.1. After a flash try the router seems bricked. No IP seems to be assigned to the LAN ports. The Wifi seems to send with a hidden essid.

Several trials loading the firmware (whiterussian rc6) using stftp seems to load the firmware, but it does not write it to the eeprom. A reboot (power off/on) after 30 minutes waiting does not change anything. The LEDs are looking ok and signal the correct data, i.e LAN LED goes on when connecting the port to a PC.

Due this router does not have a serial port (please drive me wrong otherwise) i try to use the jtag connection. So far i have connected the router to the parallel port of linux host using a passive version a self made jtag cable.

Next i compiled the HairyDairyMaid debrick utility (v 4.8). But a test with
   ./wrt54g -backup:cfe

only displays

------------------------------- cut ------------------------------------
====================================
WRT54G/GS EJTAG Debrick Utility v4.8
====================================

Probing bus ... Done

Instruction Length set to 5

CPU Chip ID: 00000100011100010000000101111111 (0471017F)
*** Found a Broadcom BCM4702 Rev 1 CPU chip ***

    - EJTAG IMPCODE ....... : 00000000100000000000100100001000 (00800908)
    - EJTAG Version ....... : 1 or 2.0
    - EJTAG DMA Support ... : Yes

Issuing Processor / Peripheral Reset ... Done
Enabling Memory Writes ... Done
Halting Processor ... <Processor Entered Debug Mode!> ... Done

------------------------------- cut ------------------------------------

then the cursor stands with no further action. No prompt, nothing.

Actually i am lost. Do you have any hints for me ?

Finally i got it running - both the jtag tool and the router.

I had to use
  ./wrt54g -erase:nvram /noreset /nobreak

This for others getting this problem also.

regards

The discussion might have continued from here.