Posted: Mon Mar 21, 2011 15:03 Post subject: Belkin F7D8302v1 / F7D4302 v1 Serial Recovery Sollution
This guide is is to help recover from a bad flash on the f7d8302 v1 and f7d4302 units only.
*note* if you have the f7d8302 v1... pull up on the little sticker on the bottom of the unit... you will see your unit is/was a f7d4302 v1
You've probably already voided your warranty if you got to this point but I assume no responsibility what-so-ever from your using this incomplete guide. If you choose to follow it you assume responsibility for your actions.
Using this tutorial assume that you cannot reach the GUI (Graphical User Interface) page through your browser at 192.168.2.1 or 192.168.1.1
Also you should not be able to get ping responses when you ping either one of the IP addresses listed above.
I got "destination host unreachable" or request" failed" when trying to ping.
This particular device has a serial port (mine had pins already in place to hook my serial ttl adapter to) ***third photo below***
I searched "RS232 Serial Port To TTL Converter Module SP3232 LED" on ebay and bought the device shown below (If that search term does not work try serial ttl (it should handle 3.3v to 5v) *** second photo shown below***
********************************************************to be edited later. someone please link the utility that determines what usb device you have connected to your computer (it finds the names for unkown usb devices)
Also you will need to get the firmware you wish to be flashed. (use the stock buid (the one you can DL from belkin's support page for this router or....))
the latest mini build eko has posted [url\http://www.dd-wrt.com/phpBB2/viewtopic.php?t=70454&postdays=0&postorder=asc&start=75[/url]
***read link above from this page foward***
So if you have the following:
1) windows xp or later pc
2) the serial ttl up converter listed above
3) a usb to serial adapter
4) the driver for the adapter
5) search google and download PUTTY
6) wires to connect serial ttl to pins on board (and solder if needed)
7)a simple 5 port switch
8)two ethernet cables
9) a tftp (search recover from bad flash in the wiki )program (just incase but I did not need one (although I tried and failed to flash this way) in this example.
... then continue below
1) the photos below will show you the connections for this router.
make sure the router is turned off while doing this. If you short the vcc with the ground you could seriously f*** things up. DO NOT WORRY ABOUT THE RX or TX connections..if putty doesnt show a connection then switch the two! (my picture might not be correct for the rx and tx )2)connect the serial ttl device to the router.
3)connect the serial ttl to the usb serial adapter and hook it to the computer.
install the driver and ook for it in the hardware and devices listed for your computer. It should be in the com port section.
4) Also hook your router to your pc through a switch using the ethernet cables. and turn them on.
5) set your PC IP address to 192.168.2.10
set the mask to 255.255.255.0
set the gateway to 192.168.2.1
4) configure putty as found here: http://www.dd-wrt.com/wiki/index.php/Serial_Recovery
***note ctrl +c function does not work for this device... use spacebar as soon as you get putty set and open. it boots REALLY FAST! ***note*** because your router already tried to boot you will not see it on the putty terminal screen. you will need to unplug the power from the router and plug it back in...then you should see it boot up.
**tip** I actually plugged it in at the power socker so it was easier to use one hand and use the other one to hit spacebar.
As LOM has said before, if you see the CFE> that's a good thing... you will most likely not need to use JTAG so do not attempt JTAG (if you are curious what JTAG flash is .,..search the wiki)
In putty use the help command at CFE> to find available commands.
CFE>help [press enter]
a list of commands and a brief description comes up.
clear the nvram
I had previously used nvram erase as a command and just nvram
ifconfig is the command that will be used.
I typed ifconfig in and got a result of =0
when you get =0 then it succeeded.
also note the ipaddr listed 192.168.2.1
or 192.168.1.1 and mask addr 255.255.255.0
After you have used the ifconfig command wait a minute or two.
(this step is probably not needed at all but it happened in my process so I will include it)
I had to reboot and repeat this process a few times... the last time I typed 192.168.2.0 into my browser and then quickly changed it to 192.168.2.1 and I saw the CFE browser page that allows you to reset clear the nvram and load firmware!!!!
Once you get here it is golden... then use a link from above to find the mini build and reload it for DDWRT or use the belkin stock firmware.
***NOTE*** on each of my routers...once I installed the BIG build via ddwrt upgrade GUI... I was not able to install any of the previous firmware and trying to caused my router to brick in the first place.****
this guide should only be followed if you have somehow erased the miniCFE server on your router. I have recovered from flashes where i thought my unit was completely bricked, however just doing a 30/30/30 reset puts these units into CFE recovery mode and you can upload any firmware from there. Things you may have overlooked: CFE miniserver does not look at NVRAM for its ip! It is hardcoded the stock belkin 192.160.0(ZERO!!).1, so your static IP must be 192.168.0.X to see it!
One more thing to notice: The CFE recovery page can be used to set NVRAM variables. This is especially useful if you want to set your root pw in case you forgot it.
Thanks for this info! Came across this thread searching to see if anyone has soldered a 2nd USB port to the dual band F7D8302, as it only comes with one
but i needed serial console. mini CFE took its IP definitly from nvram. it was, in my case, 192.168.178.250. so its not hardcoded anywhere.
however, i was wondering that 30/30/30 did not reset my unit to 192.168.2.1
to sketcherz: you have to change TX with RX. TX is on pin 2 _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
wow you guys just saved me a lot of work. I have a F7D8302v1 and I thought i bricked it. This was my first attempt at putting a third party firmware on anything. I think my mistake after reading the peacock thread was that I wasn't patient enough after the firmware update.
I thought I'd add what i saw: I was able to recover after a hard reset at 192.168.2.1. My system didn't respond to pings thought. I used wireshark to check out the arp requests and it responded to that. I was then able to use the web gui to restore it.
I'm new to all this. I tried to recover my F7D4302de from a dd-wrt firmware to the original. But now nothing seems to work anymore. I even won't get any flashlight to lighten up when i connect the router to the power plug.
Is it totally bricked or can I repair that? I tried the 30/30/30 thing but even after that no light shows up. Am I right that i have to use the modem ethernet port to recover?
Is there a chance to do the recovery on a mac?
Posted: Mon Jun 30, 2014 23:34 Post subject: Partially Bricked F7D8302 - f7D4302
I have a Belkin F7D8302 v1.0. I tried to put dd-wrt on it, like I have on my many other routers. I can no longer get it to boot successfully. I have tried the commands stated in this thread, using the serial connection, and I get = 0. But I can not successfully flash any firmware on it. I can access the CFE Mini web server on 192.168.2.1, by doing a 30/30/30 hard reset or by doing interrupting the boot sequence by pressing spacebar in Putty. I have not yet tried tftp.
What the light is doing:
If I am in CFE in putty then it is solid
After doing a hard reset it is off
Things I tried:
Serial connection, using putty, commands (nvram erase, nvram, ifconfig)
Uploading any compatible firmware to the router via CFE mini (dd-wrt big or mini, old or new, belkin firmware)
I also tried with a 5 port switch in between the router and my computer.
Any help would be appreciated.
The serial output of one loop is attached as a txt file.
Posted: Fri Jan 29, 2016 22:01 Post subject: Got it working
I just wanted to post that I got it working with a serial cable and lots of patience. The TFTP server takes a long time just wait it out.
I actually ended up completely erasing the previous firmware (dd-wrt corrupted) so that it would auto boot into the CFE TFTP server. Then TFTP the firmware at exactly the right time and wait, and wait, and wait.
Posted: Sun Mar 10, 2019 14:46 Post subject: Mistakenly flashed with a bin file from another model
It's great to see some helpful information here. I post my case as well and hopefully it could help someone later.
After being flashed a wrong bin file, my F7D8302 v1 (though FCC ID as F7D4302V1) won't up. No respond to ping. After a 30-30-30, nothing changed. The light on its top stayed consistent green, since a while after power-on.
Then I hooked out the serial port and saw the bootloader was working. The last part of one power cycle was as below:
Bootloader version 0.07e boot_version 0.07e
Project name : WG8017F22 1-LF-AK
Press space bar to cancel startup...
Device eth0: hwaddr 94-44-52-F5-E3-4E, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
鞍Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3832 bytes read
Entry at 0x80001000
Starting program at 0x80001000
So there is a small time window to accept some inputs. In my case, I tried Ctrl+C and Space multiple times but didn't catch it. After some vain I tried a Ctrl+Break then saw the "CFE>" prompt! Btw my wires were not in good connection thus some scramble codes coming out. I tried to key in commands but seems not being taken, while the connection was getting worse.
Then I tried to load image. The tftp2.exe in Windows won't help after repeated 11 rounds. Neither the tftp in Ubuntu worked for me, timeout after 300s. Eventually I tried CFE miniWeb Server and it's there. I realized my router was not in that bad shape yet. Tried to load dd-wrt mini but I got this on web page:
Receive file size=3571777
The file transferred is not a valid firmware image.
Invalid magic. This is not a TRX image.
TRX check magic for QA firmware = 12345678
Assume magic 0x20091006, Current magic 0x30524448
Repeated a couple of times, the size showing in web page was also different, while the real size was 3571712.
Receive file size=7188480
Upload completed. System will reboot. Please wait a few moments.
Then it's back to origin and I could update to dd-wrt mini/mega etc.
During the procedure I had window open for "ping 192.168.1.1". The ping time was around 1.7 ~ 1.8 ms. When running tftp there was no change. But when upload through web page the ping time changed to 6 ~ 9ms which means there were traffic through the cable. Someone mentioned the ttl was kind of indication of the device (lan port) status. I saw ttl=100 in my case.
and this is repeated all the time and nothing more is happening. So is there a possibility for recovering ?
In contrast with the log from my 8302, the booloader in that unit seems gone. It was with a very primitive loader. You may need more advanced tool to proceed or directly operate on/write to the flash chip.