OpenWrt Forum Archive

Topic: Need help with TFTP transfering

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

Hi,

I bricked my Netgear wifi router WNR854T while trying to flash OpenWrt firmware, over wireless connection. Yes, it doesn't work anymore, and i got freaked out. Luckily I found the fix on Netgear's website:
http://kb.netgear.com/app/answers/detai … _id/100109

I can ping it at 192.168.1.1, but the joy doesn't last very long, since Im gonna have to manually flash a new firmware over, and not having the web interface, but TFTP instead... I supposed that I dont have TFTP available in windows, so I downloaded a client exe file, but it keeps saying "no tftp server available"...

After a whole night messing around, I could enable the native TFTP in my laptop (Win 7, 64bit). But still, I can not flash the new firmware v1.4.38 - It keeps saying "Time out expired / Retries expired", and the syntax is right, i double checked.

I tried connect to the webinterface, and found the OpenWrt interface. Should I use this interface to flash the new original firmware from netgear?

Thanks so much for your help, and so sorry for my terrible english. I'm freaked out.

(Last edited by kant on 7 Feb 2013, 20:33)

If you have the OpenWRT interface running, the first thing I would try is a flash of the OpenWRT firmware. You would use the "generic" version for your router's hardware since you no longer need to "fool" the manufacturer's loader into thinking it is OEM firmware.

If you need to use TFTP again, http://wiki.openwrt.org/doc/howto/generic.flashing.tftp has some good suggestions.

I find that running tcpdump on the interface of the machine that you are going to flash from can help see the moment the router comes alive. I don't know the Windows equivalent, unfortunately.

It can be very frustrating with the short timeout of may devices. I remember spending hours one night when I soft-bricked a WRT54G.

P.S. Your English is very good!

(Last edited by jeffster on 7 Feb 2013, 20:36)

Thank you so much Jeffster, there're a lot to read, and to be honest I don't know where to start from. I didn't really know what i am doing, haha.

Will ask for help if i got anymore problem, thanks.

In windows, after struggling for years with different tftp software, I have used tftpd32 and tftpd64 successfully (after turning off the firewall--remember to turn it back on).  Easy as can be.  This is with a direct wire from the PC to the device.

(Last edited by lizby on 7 Feb 2013, 20:55)

Hi again, I tried the web interface, and flash this: openwrt-wnr854t-squashfs-webupgrade.img which i downloaded from the wiki- but got a red error:

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

I tried with the OEM firmware but also got the same error.

What should i do now? TFTP it is? The wiki asked me to check my hardware's bootloader ... but i couldn't find it yet:

You must determine whether your hardware's bootloader has a TFTP client or server. Consult your specific model's OpenWRT Wiki page for details on necessary settings and the TFTP type offered if any.

(Last edited by kant on 7 Feb 2013, 21:07)

Hi Lizby, Thanks for your help, I tried using TFTPD32, can you have a look at my settings?

Server Interface: my computer IPv4
I guess i'm going with "Client" tab, since that's the only tab I can input value - detail as below:
- Host: Router's IP
- Port: No idea
- Local File: Firmware to transfer
- Remote file: blank
- blocksize: default
- and then click on PUT ...

I waited on it like 5', and it keeps saying "block #0" ...

I'm not familiar with that specific router, but http://wiki.openwrt.org/toh/netgear/wnr854t suggests

LuCI Web Upgrade Process

Browse to the System → Flash Firmware page
Upload openwrt-orion-squashfs.img
Wait for reboot

Note that the image is a "generic" one for the hardware

I used "Tftp server" tab.  Under settings, make sure "Tftp Server" is checked.  Under "TFTP" in the settings window I didn't change anything except the base directory.

I have serial console available, so I did the tftpboot command from the console on the router.  I'm sorry I didn't notice that you didn't say you had serial console, so perhaps you do want "client" and "put".

For "Port", I would set it to the default tftp port, 69--but perhaps it's using that.

The wiki says the default server address is 192.168.1.2--do you have your PC set to that address?

If LuCI is not accepting the firmware file and you are sure you are using the right one, you can try SSH into the router and use the command line flash utility - that will allow you to override the checks if you are absolutely certain you are using the correct image.

That said if you can access the web interface and the command line then the router is hardly "bricked"

Thank you all for your support. I do appreciate all of this.

@Jeffster: I managed to successfully flash the generic orion firmware. The Web UI is up and running good now, but the router still have that orange dim light, just like when it's bricked. Tried to flash both OEM firmware and specific Orion firmware for wnr854t, but it keeps saying The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

@lizby: I found myself starring at a new error: "Error in recov. Error code is 10054 (an existing connectiong was forcibly removed by the remote host" - So, i'm stuck.

@qasdfdsaq: thanks for joining the circle, i'm not really familiar with the term "SSH into the router" to "use the cmd line flash utility" ... and i'm not that certain about this img...
i'm using the Netgear WNR854T - in the wiki it says, go with Orion, so I did, and I downloaded the "webupgrade" img ... but the LUCI doesn't accept it. Even the original firmware from manufacturer.

Can anyone please kindly use teamviewer to check my computer and see what's going on here??

Also, my skype name is kant.nguyen, if you have some freetime to help out, it'd be great.

(Last edited by kant on 8 Feb 2013, 05:52)

Hi, ive done something stupid.

Since there's a conflict in IP Address between my modem (192.168.1.1) and my wifi router (netgear - same ip), i supposed it's the cause why I don't have the internet connection. So i decided to change the wifi router's IP to 192.168.1.5 on the modem's mask (my apologize, im not familiar with the technical saying), and its broadcasting IP to 192.168.5.1 ...

Now i can't connect to the web interface anymore. The Power light which was dim orange, not change to blinking green, which was a positive news, i guess, since green is way better than red-ish orange. but turn out the homepage of the router says I got a corrupted firmware...


Here's the setup: My computer connect to 2 network:
+ Wireless: Tenda Wifi router at 192.168.0.1, so I can still go online yelling for help.
+ Cable: RJ45 to my almost-bricked Netgear - I set the IP manually: Router - 192.168.5.1 // Computer - 192.168.5.2
I ping 192.168.5.1, but i got this "Reply from 192.168.5.2: Destination Unreachable" and "Request time out"

...
I tried reset factory by holding the reset button for a while, but I guess either the router's been fried, or the OpenWRT have some other way of reset...

(Last edited by kant on 8 Feb 2013, 11:33)

you should check the routing table in your PC, you probably have two default routes, one of them as the real default route, the other one just dangling there. Something like this:

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.137.2  192.168.137.119     50
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.38     35
---
now, the real default route is the one wiht smaller Metric value.
As windows machines tend to make a mess of routing when connected to two networks, my suggestion is to be connected to one network at any given moment (so, try first to diconnect your "network for yelling for help", and see if it helps you reach the other device).

(Last edited by darki on 9 Feb 2013, 15:38)

The discussion might have continued from here.