View Full Version : dd-wr-goo2 killed router
grubber
09-05-2013, 08:52 PM
I successfully loaded dd-wrt on my Linksys 54g v8 router. I went to install the goo2 file and the modem started to load the file then a screen came up cannot load file and the modem died. There is now no power and I cannot log into router @ 192.168.x.x. I tried a hard reboot 303030 but no help. Any idea how I am going to get it going again.
Thanks
Terryl
09-05-2013, 09:53 PM
Have you tried the master reset button in the back,(a little tiny hole) you need to use a paper clip and push it in for 10 to 15 seconds with the power on/attached.
dishuser
09-05-2013, 09:56 PM
can that version be jtagged?
goofather
09-05-2013, 10:12 PM
I have a version 8 and I have done worse things to it than a hiccup in the flashing.
The builtin TFTP server defaults to 192.168.0.1 and can only be available for a few seconds on boot (depending on how bad the flash is).
I change the IP on my computer to 192.168.0.100, open a CMD prompt and issue the command ping -n 10000 192.168.0.1
I get the TFTP2 gui ready with a firmware I know to work (like the factory bin). I then leave the CMD prompt in the background but still visible. Plug in the router and when the pings succeed I hit the Upgrade button in the TFTP2 gui. Sometimes the pings only succeed a few times.
I have never had to jtag and I have done some bad things to my router.
grubber
09-05-2013, 10:43 PM
I got the modem unbricked and working with dd-wrt again. I then tried to load the goo2 file again and it worked. Now I just need to figure out how to do a start up script
Thanks for the help.
Terryl
09-05-2013, 10:51 PM
I have a version 8 and I have done worse things to it than a hiccup in the flashing.
The builtin TFTP server defaults to 192.168.0.1 and can only be available for a few seconds on boot (depending on how bad the flash is).
I change the IP on my computer to 192.168.0.100, open a CMD prompt and issue the command ping -n 10000 192.168.0.1
I get the TFTP2 gui ready with a firmware I know to work (like the factory bin). I then leave the CMD prompt in the background but still visible. Plug in the router and when the pings succeed I hit the Upgrade button in the TFTP2 gui. Sometimes the pings only succeed a few times.
I have never had to jtag and I have done some bad things to my router.
Did it need a proper spanking???:lolpound::lolpound::willy_nilly:
Terryl
09-05-2013, 10:52 PM
I got the modem unbricked and working with dd-wrt again. I then tried to load the goo2 file again and it worked. Now I just need to figure out how to do a start up script
Thanks for the help.
What did you do to unbrick it?? Other may need to know.
dishuser
09-05-2013, 10:59 PM
What did you do to unbrick it?? Other may need to know.
probably what goo said to do
did the same a few years ago when I bricked a version 6 loading ddwrt
grubber
09-05-2013, 11:49 PM
I reinstalled the original script from Linksys, then I used tftp2 and ran vxworkskillerGv8-v3 bin, and after a hard reboot 303030 I installed the dd-wrt.v24_micro_generic bin and again a hard reboot and the modem came back to life.
airjam
09-06-2013, 01:08 AM
I got the modem unbricked and working with dd-wrt again. I then tried to load the goo2 file again and it worked. Now I just need to figure out how to do a start up script
Thanks for the help.
Why goo2 and not the later version goo3 ?
grubber
09-06-2013, 11:15 AM
It seemed to me that goo2 was more designed for my 54g v8 modem. I just checked out goo3 and you were right I will update my router to it.
Thanks,
shadalert
09-06-2013, 05:25 PM
goo3 works much better than goo2. Better stability, faster channel change, and quicker P$er change with multi-servers just to mention a few.
velocity9421
09-07-2013, 11:48 AM
The title of this thread should be changed to "I bricked my router because I don't know what I'm doing"
Because right now it suggests that the GOO bin bricked his router.
grubber
09-07-2013, 10:49 PM
Go ahead and change it.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.