Orbi WiFi 7 RBE973
Reply

Re: D7800 Bricked / Firmware fail

Verlisper
Aspirant

D7800 Bricked / Firmware fail

Hello,

Looking for help unbricking my router,

-bricked after trying to update from .24 to .31

-can ping router on static ip

-tftp2.exe failure to update firmware version

-cmd tftp failure to update firmware version 

Any help would be lovely, as I'm not interested in paying $50 for a conversation from support telling me to read the articles. 

Thanks in advance,

Curtis T

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 1 of 22

Accepted Solutions
antinode
Guru

Re: D7800 Bricked / Firmware fail

> [...] I'm changing the static IP for my router in the TCP/IPv4
> settings from my ethernet connection, is that not correct?

   If you're looking at Windows settings, then you're not looking at
router settings.  The Windows system has (or needs) an IP address, which
you can set using Windows stuff.  None of that affects the router.

   If you can use a web browser to talk to the router, then you can
change the router settings.  If you can't use a web browser to talk to
the router, then you're stuck with what the router settings are after a
reset.

   "192.168.1.77" (netmask: 255.255.255.0) is fine with me as an address
for your computer.  If you've reset the router, then I'd expect it to be
at "192.168.1.1".

> [...] could you please send one more instruction for my mess?

   The Netgear instructions for the command-line TFTP program should be
fine; you need to specify a ".img" file which can be found, and you need
to specify the IP address of the router (most likely "192.168.1.1"), not
the address of your Windows system.  (The file's already on your
computer, with the TFTP program.  What the TFTP program needs to know is
where you want the file sent ("put"), which is the router, not the
computer where it already is.)

View solution in original post

Message 19 of 22

All Replies
antinode
Guru

Re: D7800 Bricked / Firmware fail

> -tftp2.exe failure to update firmware version
> -cmd tftp failure to update firmware version

   What kind of "failure"?  When you did what, exactly?  You're doing
this on some kind of Windows system?

Message 2 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

I'm running win10

when tftp2.exe attempts to load the firmware it stops aobut 3/4 way through the bar, then proceeds to cancel and try again

when I use cmd tftp command it says unable to read file, not sure if it has anything to do with it but if iItry to mount the img file, it tells me that its corrupted

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 3 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> when tftp2.exe attempts to load the firmware it stops [...]

   I believe that others have reported similar problems with that
program.

> when I use cmd tftp command it says unable to read file, [...]

   Where is the file?  Where are you in your CMD (Command Prompt)
window?  The easiest thing to do may be to copy the ".img" file to the
directory where you run the "tftp" program.  Otherwise, you'd need to
specify a proper path for the ".img" file to the "tftp" program.  You
could also use use "cd" commands to get to the directory where the
".img" file is stored, and run the "tftp" program by specifying a proper
path to it.

> [...] not sure if it has anything to do with it but if iItry to mount
> the img file, it tells me that its corrupted

   Nope.  It's a Netgear firmware image, not a Windows (or Mac) disk
image, so Windows (or macOS) won't see any familiar contents.

Message 4 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

Thanks for the detailed reply,

I have been using the windows built in tftp through cmd, using placing the img file directly onto the desktop, then simply cd desktop

I can screenshot it tonight if that would help
Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 5 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> I have been using the windows built in tftp through cmd, using placing
> the img file directly onto the desktop, then simply cd desktop

   Sounds normal enough.  If the file's in your current directory, then

a command like, say:
     dir <file_name>
should also succeed.

> I can screenshot it tonight if that would help

   It might, but copy+paste of the plain text transcript might be
friendlier than a picture of the plain text transcript.

Message 6 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

here is the cmd log;

 

C:\Users\Curtis>ping 192.168.1.77

Pinging 192.168.1.77 with 32 bytes of data
Reply from 192.168.1.77: bytes=32 time<1ms TTL=128
Reply from 192.168.1.77: bytes=32 time<1ms TTL=128
Reply from 192.168.1.77: bytes=32 time<1ms TTL=128
Reply from 192.168.1.77: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Curtis>cd desktop

C:\Users\Curtis\Desktop>tftp -i 192.168.1.77 put D7800-V1.0.1.31
tftp: can't read from local file 'D7800-V1.0.1.31'

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 7 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> C:\Users\Curtis\Desktop>tftp -i 192.168.1.77 put D7800-V1.0.1.31
> tftp: can't read from local file 'D7800-V1.0.1.31'

> [...] If the file's in your current directory, then
> a command like, say:
>      dir <file_name>
> should also succeed.

   "D7800-V1.0.1.31"?  What happened to the ".img"?

   TFTP.EXE is a general-purpose file-transfer program, with no reason

to default to any particular file name/type.

Message 8 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

i didnt type .img for that last log, it didnt seem to help find the file...

 

C:\Users\Curtis\Desktop>dir D7800-V1.0.1.31.img
Volume in drive C has no label.
Volume Serial Number is 0EF1-6BB2

Directory of C:\Users\Curtis\Desktop

File Not Found

C:\Users\Curtis\Desktop>dir D7800-V1.0.1.31
Volume in drive C has no label.
Volume Serial Number is 0EF1-6BB2

Directory of C:\Users\Curtis\Desktop

File Not Found

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 9 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> C:\Users\Curtis\Desktop>dir D7800-V1.0.1.31.img
> [...]
> Directory of C:\Users\Curtis\Desktop
> File Not Found

   Apparently, it's not there, which would be consistent with "tftp" not
finding it there.   What, exactly, does File Explorer say is on your

Desktop?  You should have downloaded "D7800_V1.0.1.31_FW.zip". 

   Then, Right-click > Extract All... would normally extract the
contents of that archive into a (new) "D7800_V1.0.1.31_FW" folder, so
you'd normally find the firmware image in
"C:\Users\Curtis\Desktop\D7800_V1.0.1.31_FW" (not immediately in
"Desktop").  Around here, for example:

C:\Users\sms\Desktop\D7800_V1.0.1.31_FW>dir D7800-V1.0.1.31.img
 Volume in drive C is Win10
 Volume Serial Number is E102-9FD3

 Directory of C:\Users\sms\Desktop\D7800_V1.0.1.31_FW

2018-01-10  00:25        25,483,393 D7800-V1.0.1.31.img
               1 File(s)     25,483,393 bytes
               0 Dir(s)  100,148,633,600 bytes free

   Note that, ever helpful, Netgear has named the archive with an
underscore, and the firmware image file with a hyphen, so some care may
be needed when dealing with these names.  (Copy+paste is your friend.)

Message 10 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

yes, the zip was extracted, i then placed the .img onto the desktop.

file explorer shows D7800-V1.0.1.31 which makes sense as thats where i placed it... i took just the .img file out of the extracted folder and placed to desktop. i can try moving the whole folder to desktop ? not sure if you saw the image i linked in the previous comment

Message 11 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> C:\Users\Curtis\Desktop>tftp -i 192.168.1.77 put D7800-V1.0.1.31

   Who is "192.168.1.77"?  You need to specify the destination of the
file which you want to transfer, the IP address of your router (not the
IP address of your Windows system).  Same for the "ping" command.

   Presumably, your router is at "192.168.1.1".

Message 12 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

Hey antinode I tried to reply here the last few days, if you could check your pms, I've sent a reply
Message 13 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> [...] I've sent a reply

   I got it/them.  I was trying to keep things visible to all.


> [...]
> C:\Users\Curtis\Downloads\D7800_V1.0.1.31_FW>ping 192.168.1.77
> Pinging 192.168.1.77 with 32 bytes of data
> Reply from 192.168.1.77: bytes=32 time<1ms TTL=128
> [...]
> C:\Users\Curtis\Downloads\D7800_V1.0.1.31_FW>tftp -i 192.168.1.77 put D7800-V1.0.1.31.img
> Connect request failed


> [...] my router is static to 192.168.1.77

   Your "ping" test suggests that there's something at "192.168.1.77".
But, whatever it is, it seems not to be running a TFTP server.

   If you haven't already tried a full ("factory") reset on this thing,
then now might be the time.  If you have, then I wouldn't expect it to
be at "192.168.1.77".

Message 14 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

I have previously tried factory resetting, tried again today to no avail. The power light goes from blinking orange, to solid orange, to solid white but I still cannot communicate with the router (same as first factory reset).

 

Changing my static IP to .1 instead of .77 should make no difference? It could be anything I set it to (could be completely wrong, I have no experience with this) I tried again, changing to 192.168.1.1, the command seems to communicate with the router, the power light turns off and blinks white seemingly sporadically, before the cmd tells me that it has failed to connect (same as before), and the power light returns to blinking white.

 

I feel like we are getting nowhere with this and it is really draining me. Unless there is something else you can recommend I try, I'm going to have to buy a new router (probably try a new brand as my last two netgear routers had also caused me trouble).

 

I really appreciate your help antinode, and I'm willing to try one more time, but then that's it for me... 

 

Thank you,

Curtis

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 15 of 22
TerryPh
Virtuoso

Re: D7800 Bricked / Firmware fail

Hi Curtis.
Wonder if you can follow to the teeth the procedure outlined here
http://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP?cid=wmt_netgear_or...

Best regards,
Message 16 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> Changing my static IP to .1 instead of .77 should make no difference?

   "my static IP" address is the IP address of what?  Your computer or
the router?  If you've reset the router, then I'm pretty confident that
the router's IP address is not "192.168.1.77".

   The whole idea here is as follows.

   Normally, your computer gets its IP address from the router using
DHCP.  The DHCP server in your router supplies an address for your
computer which is compatible with (on the same subnet as) the router
itself.  Thus, if the router's address is "192.168.1.1", then it will
give your computer an address like "192.168.1.x", where (typically)
1 < x < 255.  Then, because the router and your computer have IP
addresses on the same subnet, they can communicate with each other.

   If your router loses its little mind, then its DHCP server no longer
works, so your computer can't get its address from the DHCP server in
your router.  If you want your computer to be able to talk to your
router, and (the DHCP server in) your router can't give your computer a
compatible IP address, then _you_ need to give your computer a suitable
static IP address.  ("Static" means "not dynamic"; that is, not from a
DHCP server.)

   I'm guessing that you gave your computer the address "192.168.1.77".
That should be fine if you want to talk to your router, which should be
at "192.168.1.1" since you reset it.  That's fine, but it also means
that "ping 192.168.1.77" would be testing the ability of your computer
to talk to itself.  Similarly, "tftp -i 192.168.1.77 put file" would be
trying to send "file" from your computer to itself, using TFTP.  (And
your computer is not running a TFTP server, so you'd get that "Connect
request failed" error message.)

   If you use a command like "tftp -i 192.168.1.1 put file", and you
still get a "Connect request failed" error message, then it would seem
that the TFTP server in the (reset) router is not working, in which case
you may be doomed.

   Of course, if you gave your computer the same "192.168.1.1" address
as the router uses when it's reset, then you'd confuse everyone, and
approximately nothing would work because of the address conflict.

Message 17 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

Hi Terry, I originally tried using the tftp2.exe and it failed to update the firmware.

 

antinode, I'm changing the static IP for my router in the TCP/IPv4 settings from my ethernet connection, is that not correct? I did try many options along "192.168.1.x" and yes, I noticed that the DHCP Server is not working (and all cmd instructions after that) in the netgear genie details after the factory reset.

 

If that is not the correct way to do the tftp could you please send one more instruction for my mess?

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 18 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> [...] I'm changing the static IP for my router in the TCP/IPv4
> settings from my ethernet connection, is that not correct?

   If you're looking at Windows settings, then you're not looking at
router settings.  The Windows system has (or needs) an IP address, which
you can set using Windows stuff.  None of that affects the router.

   If you can use a web browser to talk to the router, then you can
change the router settings.  If you can't use a web browser to talk to
the router, then you're stuck with what the router settings are after a
reset.

   "192.168.1.77" (netmask: 255.255.255.0) is fine with me as an address
for your computer.  If you've reset the router, then I'd expect it to be
at "192.168.1.1".

> [...] could you please send one more instruction for my mess?

   The Netgear instructions for the command-line TFTP program should be
fine; you need to specify a ".img" file which can be found, and you need
to specify the IP address of the router (most likely "192.168.1.1"), not
the address of your Windows system.  (The file's already on your
computer, with the TFTP program.  What the TFTP program needs to know is
where you want the file sent ("put"), which is the router, not the
computer where it already is.)

Message 19 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

Either I'm missing something here or it's doomed. Update, as I was typing this something clicked in my head with all this newfound information, so I tried one last time...

 

C:\Users\Curtis\Downloads\D7800_V1.0.1.31_FW>tftp -i 192.168.1.1 put D7800-V1.0.1.31.img
Transfer successful: 25483393 bytes in 7 second(s), 3640484 bytes/s

C:\Users\Curtis\Downloads\D7800_V1.0.1.31_FW>

 

Thank you so much antinode and for being so patient and understanding with me!

 

Curtis

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 20 of 22
antinode
Guru

Re: D7800 Bricked / Firmware fail

> Transfer successful: 25483393 bytes in 7 second(s), 3640484 bytes/s

   Glad to hear that you got it to go.  (What could go wrong?)  And,
after all that, it's a modem+router again?

   If all's well again with the router, then you might want to go back
to your computer's network settings, and restore it to "Get
Automatically" instead of keeping that static address.

Message 21 of 22
Verlisper
Aspirant

Re: D7800 Bricked / Firmware fail

Yeah, all up and running, settings all fixed too 🙂 Cheers

Message 22 of 22
Top Contributors
Discussion stats
  • 21 replies
  • 13837 views
  • 2 kudos
  • 3 in conversation
Announcements

Orbi WiFi 7