Joined: 07 Jun 2006 Posts: 2032 Location: Odessa, Ukraine
Posted: Mon Feb 11, 2008 4:29 am Post subject:
And right there is your flash chip, with the white piece of paper on it, behind the serial 10 pin connector. Take the paper off and tell us what it says...Jtag cable for a WRT54G will work fine or build your own _________________ Want JTAG support - Donate a router
or Donate with PayPal !
Posted: Tue Feb 12, 2008 5:55 am Post subject: Same problem
I have tried to flash my wrt54g with dd-wrt, I got past the first two flashes and it wouldn't take the 3rd. I am stuck with a flashing power, ports switched 1 is 4, 3 is 2. I have tried to re flash it says it is complete, but does not reboot. I have gone to bed and gotten up still nothing. Tried powering cycling. I do not believe it is brick, because i can ping it, and flash it as many times as i want as long I power cycles after a flash. It does not let you do flash again with out power cycling.
Thnx for any help
Last edited by crazy48723 on Tue Feb 12, 2008 5:57 am; edited 1 time in total
It worked great.
No flaws.
Until I discovered that there's no support for PPPoE.
I looked everywhere for a way to enable or possibly get around PPPoE. But nothing came up.
So I decided to revert back to VxWorks.
I used a guide that went as follows:
1. Download [http://www.bitsum.com/files/vxworks_revert_v02.zip] and extract.
2. Download the latest Linksys firmware for your router from http://www.linksys.com.
3. In the DD-WRT Administration/Firmware? Upgrade tab, select and apply the openwrt-wrt54g_v4-squashfs.bin firmware you extracted in step 1.
4. DO NOT TOUCH YOUR ROUTER. DO NOT POWER DOWN YOUR ROUTER. IF YOU DO, YOU MAY/WILL BRICK YOUR ROUTER.
5. After a few minutes (have patience) your router will reboot itself and the VxWorks boot loader's Management Mode will be engaged. You can visit it at http://192.168.1.1. If the browser doesn't respond, WAIT LONGER. Do not power off your router.
6. In the Management Mode, select and apply the Linksys firmware you downloaded in step 2. DO NOT apply vxworks killer instead, even if you want to go back to linux again right away. You must first apply a Linksys firmware to re-initialize the flash before you can go back to linux.
7. Power cycle the router after you see 'Success'.
So I followed it, up until I reached management mode and loaded the Linksys firmware v1.02.2
It said success, but when I entered 192.168.1.1 into my web browser, it kept going to management mode.. so I loaded the Linksys firmware once more, but I got the same result.
Then I power cycled the router.. same thing: Management Mode. So I loaded the linux_upgrade_wrt54g.bin file
Everything was working again after that with the Linux firmware.. but because my ISP requires PPPoE, I wasn't able to get on the internet.
So I messed around with a few settings. I don't remember which, but they were part of the basic setup page.
And I power cycled my router. I can't access my router anymore. The 4 Ethernet LEDs stay on constantly, including the Internet LED.
The Power LED flashes on reboot.
Is there anyway I can fix my router?
Even if I can't get the Linksys firmware on it, I'd like the Linux firmware because I'm going to turn this router into a bridge. I just bought a WRT54GL to replace it.
-edit-
Forgot to mention I tried resetting, pinging with no success, and tftp.
Hi all, it happened to me as well - Ive got a bricked WRT54GS v6 on my hands - all the ethernet leds are on & the power led is flashing
I have been trying the jtag method of re-programming the chip - I accidently erased the cfe does anyone have one for the WRT54GS or know of an equivalent that would work?
Finaly got my WRT54G working. I described what happened with it on page 2 (in short - it was bricked when I was trying to get back to original Linksys firmware. The power LED was blinking and I couldn't ping the router)
Anyways, bought JTAG cable on eBay and used Hairydairy debrick Utility. At first, was no success since Debrick utility sat at 'Enabling Memory Write' forever. Then I found that I had to use /noemw switch. So , here is what I used:
*First - I issued 'wrt54g -probeonly /noemw' in order to check the connectivity. I got the Processor info
*Second - wrt54g -erase:nvram /noemw. After this command utility erased blocks of memory but I still couldn't ping the router.
*Third - wrt54g -erase:kernel /noemw. This got rid of bad firmware and I finally could ping the router.
P.S. I had to manually assign IP to my computer. Default IP that router has is 192.168.1.1. So make sure that you assign to your computer something 192.168.1.x , where X is number from 2 to 254
*Four - TFTP working firmware , router rebooted and it is working!!!
Posted: Wed Mar 12, 2008 11:39 am Post subject: JTAG and HairyDairyMaid utiliites worked for me :-)
I bricked my WRT54g v5.0 router while upgrading it to DD-WRT. The VXworkskiller part went fine, but (unknown to me at the time) I installed a *damaged* copy of the DD-WRT_micro kernel. The router never rebooted. When I finally cycled the power, the power LED was flashing, the LAN LEDs were all continuously on, and the unit would not answer a ping. BRICK
I tried both pin shorting and grounding and neither helped. I finally purchased a jtag cable (with header pins) for $15 USD+free shipping), downloaded the hairydairymaid utilities, and tried to reload the cfe and kernel. Unfortunately, I ass|u|med that the vxworkskiller binary could be used as the cfe component. After a lot of searching on google, I found a clue that ALL LAN LEDs ON=bad CFE. When I looked at the size of the vxworkskiller, it was 320KB. WRT54g CFE images available elsewhere on the internet were all 256KB.
What worked: I downloaded the Skynet utilities (skynet_repairkit_1.2_setup.exe) and built a CFE for "WRT54g version 5.0 linux" (with the MAC address from the bottom of my Linksys case). This file was 256KB. With the JTAG/hairydairymaid setup, I erased the nvram and then flashed the [Skynet-built] cfe and DD-WRT_micro as the kernel. Viola! My router not only was back, but it also was upgraded to DD-WRT.
Note: I used the Windows-based hairydairymaid utilities. I couldn't get the [included] parallel port software to install, but I found a substitute on SourceForge -- giveio_setup.exe. Also, as Charg3r noted, I couldn't get the router to respond to jtag commands without using the /noemw option ON ALL COMMANDS.
Posted: Wed Mar 12, 2008 11:54 am Post subject: DD-WRT doesn't support PPPoE?
Quote:
GMSkel wrote:
Until I discovered that there's no support for PPPoE.
I looked everywhere for a way to enable or possibly get around PPPoE. But nothing came up.
Hmmm. In my extended family there are fourWRT54g routers successfully running DD-WRT v24 RC-6 (01/02/08) with ISPs that use PPPoE.
Did you set the MTU to 1492? Some routers automatically set this when you select PPPoE and some don't, but it is a requirement for PPPoE to work properly.
And now my router powers up (to which i can ping to) the power light goes solid + 1 WLAN + 1 Nic light (for the connection to my laptop) but when this occurs I can no longer ping my router or get access to the DD-WRT GUI? I can also see the DD-WRT in my wireless connections that are available but cannot connect to it either
Any idea whats going on? Or how I can resolve this?
Any idea whats going on? Or how I can resolve this?
Sounds like the router is set up properly and the computer isn't. Do a hard reset on the router, just to be sure, and then make sure your computer is set to auto IP and Auto DNS for both your wireless and wired NIC. _________________ It takes a community to raise a router
Hmm okay, I will give that a go and see. I did the 30/30/30 reset on it, but cant remember if I did the auto IP, was doing this all @3am one day haha.... Damn late working hours. Thanks!
Set your LAN Nic to 192.168.1.7/255.255.255.0 and see if you can log into the router at 192.168.1.1.
You might have messed up a step in the flashing process. Usually the best thing to do is try repeating the process from the last process that worked, but you might need to jtag. What ping response are you getting? See note 6 of the peacock announcement. _________________ It takes a community to raise a router
Yep I tried the 192.168.1.7 as it was the settings used in the flashing process. When I ping i get TLL=100 until the router boots up and the power light goes solid then I get destination unreachable...
