Nighthawk AC 1900 WiFi Cable Modem Router

[BobbyG58]

I have an AC1900 R6900V2 that has become bricked during an update R6900v2-V1.2.0.36_1.0.1.

I cannot do a factory reset Depending on how I Start it, Method 1 Power On) I get an orange power light and an orange light for the port I am hardwired to. No other lights.

Method 2 Press Reset and Power On) I get and orange then Flashing White with no other lights including the Port that my laptop is connected to.

What I have tried: I used the Netgear Instructions for a manual install of the update using two different versions. I pinged 192.168.1.1 before starting and the router returns the ping as successful 4 of 4 packets 100%. I tried connecting to 192.168.1.1 via browser but cannot connect.

Update results:

1) Manual Update using Win 10 tfpt put command for R6900v2-V1.2.0.36_1.0.1 Failed, Command prompt says transfer successful but no change on the router

2) Manual update using Win 10 tfpt put command for R6900v2-V1.2.0.24_1.0.1 which is the last version it was running on. Failed, Command prompt says transfer successful but no change on the router.

Am I missing something or is this unit unrecoverable?

[michaelkenward]

---

@BobbyG58 wrote:

Am I missing something or is this unit unrecoverable?

---

Hard to tell with incomplete details of what you did. No full "printout" from your TFTP session, for example.

TFTP is not the easiest thing to get right.

Netgear's advice:

How to upload firmware to a NETGEAR router using Windows TFTP | Answer | NETGEAR Support

is OK as far as it goes.

You might get clearer information if you ran a search to find a video that takes you through the process.

[BobbyG58]

I followed Netgears instructions to the letter using Windows 10 TFPT as I mentioned above using The latest version and Trying the version before that.

As I mentioned, I can put the router in two different states:

1) flashing white power light and no port light where the PC is plugged in 1,2,3, or 4. This is acheived by Doing a Hard Reset, and the transfer fails

2) Orange power and orange port where the pc is plugged in 1,2,3, or 4 and transfer fails.

I followed the Netgear instruction to the letter AND I have the correct firmware

Ethernet settings:

192.168.1.10

255.255.255.0

192.168.1.1

I also tried using  TFTP2 program with the same setting and set it to 3 tries and all attempts timed out.

[antinode]

> I followed Netgears instructions to the letter using Windows 10 TFPT
> [...]

   "to the letter"?  "TFPT"?  Copy+paste is your friend.

   What is the actual TFTP command which you're using?

[BobbyG58]

"tftp -i   192.168.1.1    put  R6900v2-V1.2.0.36_1.0.1.img" is the command   I am using without quotes.

https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

I am not new to computers by any means and use DOS Commands often. I apologize for the typo. It happens.

[michaelkenward]

More a case of "nothing to lose" how about trying a different firmware version?

[BobbyG58]

I did try the version prior to the newest. I think the issue is that I am not getting a port light when I get the flashing white power light after doing the reset procedure. However, I can ping the router with varied packet results from 100% to 25%.

If I just turn the unit on, then all I get is an Orange Power light and an Orange port light and cannot ping the router although the ipconfig command shows the router.

I read briefly on another forum that someone had a similar issue and used 192.168.1.2 instead of 192.168.1.1 and was able to get his unit to flash. That thread did not say if he had the same light status that I have. I think the 2 different light status that I have is where my issue is at.

[michaelkenward]

---

@BobbyG58 wrote:

I read briefly on another forum that someone had a similar issue and used 192.168.1.2 instead of 192.168.1.1 and was able to get his unit to flash.

---

Not sure if that matters. As I understand it, almost certainly wrong as the resident troll will point out, the idea is to put the source (your PC) on a different IP address from the router.

I'm afraid that my experience with using TFTP was in beta tests when we had to Telnet into the router and fool it into believing that it was something else. (All officially sanctioned.) TFTP worked find in that case, but the router wasn't really "bricked".

Did you set it up so that there was nothing more than the PC and router on the network?

The last thing you want is something else getting in the way.

[BobbyG58]

Yes. I shut down/ disabled WiFi, no other connection to the PC or Router, just the two units.

As outlined in the Netgear KB, I assigned the adapter

IP Address 192.168.1.10

 SubNet Mask 255.255.255.0

Default Gateway 192.168.1.1

It seems odd that I can get into reset mode but I cannot get a port assignment light on the router since there is no port light on in this "odd" mode. I don't understand why I could ping the router with success but the router will not take the firmware.

Since I don't understand how data flows through the Adapter settings, I cannot dig deeper into why this configuration would not work and why the "Put" Command is failing.

I would think that I need the port assignment light on, in order to complete the data flow. Just my simplistic thinking.

I will never do a firmware update via WiFi again although I had done it several times on this router.

[antinode]

> [...] I am not new to computers by any means and use DOS Commands
> often. [...]

   With my weak psychic powers, your experience (or intelligence, or any
other fine quality) is hidden behind what you write.  If what you write
is vague or incomplete, then the other (invisible) stuff is irrelevant.

   Some of the worst problem descriptions to be found in these forums
come from people who cite their own vast experience, and believe that
everyone should trust their analysis of the problem, while hiding any
evidence which might support it.

> [...] I apologize for the typo. [...]

   No need.  My point was that "followed [...] instructions to the
letter" is generally a useless description of what you did.  All the
more so when there are variables in the "instructions", and your ability
to transcribe has been proven fallible.

> "tftp -i 192.168.1.1 put R6900v2-V1.2.0.36_1.0.1.img"

   Looks ok to me.  If the error is a time-out, then it would appear
that the TFTP server is not running and/or is accessible.

   You're looking at a situation where normal operation has obviously
failed.  The TFTP server has a better chance of working, but it's not
fool-proof.  If you can't find a way to prod the router into a mode
where it will accept a TFTP load, then your last hope may be opening the
box ("Good-bye, warranty!"), and attacking it through its serial port.
(A Web search should find details.)

> [...] I would think that I need the port assignment light on, in order
> to complete the data flow. [...]

   I agree, but it's tough to tell if the problem is with the LED
indication of the port status, or the actual port status.  If you were
desperate, and had some time to kill, then you might try manually
setting the computer interface to 10, 100, or 1000MHz, just in case the
actual problem is with the link-speed auto-negotiation.  (As
straw-grasping goes, I'd guess that that would be pretty far out.)

> [...] I will never do a firmware update via WiFi again although I had
> done it several times on this router.

   You can find countless recommendations against wireless firmware
updates, but there's no shortage of wired failures.  Knowing nothing
about the actual code, it's tough (for me) to be authoritative, but I
wouldn't expect it to matter if the fundamental procedure is sound.  Or,
if it really is a problem, then the action should be prohibited, or, at
least, strongly discouraged when the user attempts it.  But what do I
know?

> [...] the resident troll [...]

   Personal insults from the single user who most frequently admonishes
others by citing the "NETGEAR Community Terms Of Service" are hilarious.
Keep up the fine entertainment!  Merely one recent example:

      https://community.netgear.com/t5/x/x/m-p/1698989#M122464

[BobbyG58]

Since I am at a loss for a way to "prompt" the unit into a mode that will accept the TFTP. I cannot think of any other ways to "prompt" it other than off and on, reset using power button or reset using the power adapter with the power button on. PC plugged in on power up or plug in after power up.

It seems I could try the serial port flash. I did see one on YT video using this method on a different model.

My warranty is expired anyway, hence coming here.

But without opening my unit, and having never opened a router, I have to wonder if all routers are built using basic/ standard board layouts, i.e. a serial port interface?

I am not beyond experimenting and learning something new. Afterall the unit is not usable in it's current state. I will have to do some more digging to see what I can find on serial port flashing.

A person's knowlege base should not be in question when they come to a forum like this. The reason anyone comes to a forum is because they lack the knowlege in the subject they are presenting to the forum and seeking that knowlege from those that have, either the knowlege or the experience from other users having,  or had the same problem in order to hopefully "fix" the problem.

I am open to discussion, diagnostic questions, diagnostic tasks and requests to provide relevant information to solve a problem.

Anything else is a waste of time and is not conducive to reach a solution or conclusion.

I belong to several forums and too many times I see people posting questions or problems and some members are either rude or condescending  to a member that has little, some or even vast knowlege in the topic.

These attitudes drive members away from what should have been a helpful diagnostic approach and not a let me stroke my ego by belittling and knit picking at a member that is looking for knowlege or help to solve a problem.

I am not interested in petty bickering between members as it serves no purpose and does not lead to solutions or conclusions for or about the problem that a member is looking for.

[michaelkenward]

---

@BobbyG58 wrote:

I cannot think of any other ways to "prompt" it other than off and on, reset using power button or reset using the power adapter with the power button on. PC plugged in on power up or plug in after power up.

---

Going back over this conversation I see no mention of something that you probably have tried, but there is no harm in bringing it up again.

You said earlier:

flashing white power light and no port light where the PC is plugged in 1,2,3, or 4. This is acheived by Doing a Hard Reset, and the transfer fails

That puts the finger on an important bit.

The flashing white power LED seems to be important. You want that rather than the yellow one.

Does that reference to a hard reset mean this one?

• Press reset for 30 seconds
• Keep pressing reset while removing power
• Keep pressing reset for another 30 seconds while apply power

This may be what you did to get your "Method 2", but it isn't obvious.

Does "no port light where the PC is plugged in 1,2,3, or 4" mean the LAN LED on the top doesn't show? Some devices have LAN LEDs on the rear.

If so, that's a puzzler.

How old is this thing? Still in the year's warranty?

[BobbyG58]

Yes, I have tried the 30,30,30 Press reset for 30, power down while holding reset for 30, apply power and hold reset for another 30, all without releasing the reset.

Doing it this way, I get flashing white power. All my LAN Port lights are on the front and I get no port LED in this mode.

If I just power up, I get Orange power LED and Orange LED on the LAN port that I am plugged into.

I purchased it  Sept 2017 and it is out of warranty, hence coming here.

[michaelkenward]

---

@BobbyG58 wrote:

Yes, I have tried the 30,30,30 Press reset for 30, power down while holding reset for 30, apply power and hold reset for another 30, all without releasing the reset.

Doing it this way, I get flashing white power.

---

That is where you should be in order to do the TFTP thing.

Puzzling.

But there have been so many reports here of people having to do strange things – standing on one foot and reciting strange incantatiions – that nothing surprises me.

[BobbyG58]

I am wondering if in the flashing white power light state if I should also have a Port light?

Although on one try to TFTP attempt with no port light, I got transfer successful but I waited an hour and the unit never rebooted.

At that point, I tried to connect through my browser and got cannot connect message.

After that I turned the power off and rebooted and I got orange power and orange port but no communication through my browser and could not ping the router.

So, that is the 2 modes I can get 1) flashing power light and no port light or 2) Orange power light and orange port light.

So, in the end, it seems the unit is not taking the firmware even though I did get the one "transfer successful" message that was still a failure.

I cannot find any other "tricks" that do not involve taking the unit apart. Which I might try but then again, I may just scrap it and buy another unit.

[BobbyG58]

I could not attach the txt file for some reason. So here is a copy of the command prompt window with the attempts that I tried today.

First try flashing white power light reset mode. Using 192.168.1.10/ 255.255.255.0/ 192.168.1.2

c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.2 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

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

Here I Changed adapter back to 192.168.1.1

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.
Reply from 192.168.1.10: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.1 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

Here I tried using Obtain IP Address Automatically

C:\Users\Bob\Desktop\NetGear Fix>ipconfig

Windows IP Configuration

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2de1:4ccc:a1a0:8fd9%23
Autoconfiguration IPv4 Address. . : 169.254.143.217
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Bob\Desktop\NetGear Fix>tftp -i 169.254.143.217 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

C:\Users\Bob\Desktop\NetGear Fix>ping 169.254.143.217

Pinging 169.254.143.217 with 32 bytes of data
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64

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

[antinode]

> First try flashing white power light reset mode. Using
> 192.168.1.10/ 255.255.255.0/ 192.168.1.2

   Those are the Ethernet interface IP address, subnet mask, and
gateway?  The gateway setting shouldn't matter, but, if you're setting
it to anything, then why ".2"?  What's at ".2"?  Anything?

> c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.2 put
> R6900v2-V1.2.0.36_1.0.1.img
> Connect request failed

   That does not amaze me.  I'd expect the router to be at ".1", and
nothing to be at ".2".  Hence, no TFTP server at ".2".

> Pinging 192.168.1.2 with 32 bytes of data
> Reply from 192.168.1.10: Destination host unreachable.

   Same.  What's at ".2"?  "Nothing" is usually unreachable.

> Pinging 192.168.1.10 with 32 bytes of data
> Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

   Also not amazing.  The computer's Ethernet interface (at
"192.168.1.10") can talk to itself.

> Here I Changed adapter back to 192.168.1.1

   Why?  If the router is at ".1", as it should be, then this could only
cause a conflict (and failure).

> Here I tried using Obtain IP Address Automatically

   Also doomed.  If the router's DHCP server is dead, and the
"169.254.x.y" address testifies to that, then there's little hope of
anything signifcant to work if it relies on DHCP.

> C:\Users\Bob\Desktop\NetGear Fix>tftp -i 169.254.143.217
> put R6900v2-V1.2.0.36_1.0.1.img

   Again, you're trying to send the file to the computer (where there's
no TFTP server), not to the router (where you hope that there is a TFTP
server).  The router is what needs the file.

   As the instructions say, set the computer's interface to
"192.168.1.10", and try to reach the router at "192.168.1.1".  If you
set the gateway, then set it to the same "192.168.1.1" where the router
should be.  Fiddling with these addresses (for no good reason) is much
more likely to induce failure than success.

   Fiddle with the reset operations, the command timing, and/or anything
else which is not certain to make trouble.

   Is the computer connected to the "LAN 1" port on the router?

[BobbyG58]

If you had read one of my previous posts, I mentioned another user, with a similar problem, acheived the flash by using

192.168.10

255.255.255.0

192.168.1.2

It was worth a try.

I then switched it back to

192.168.10

255.255.0

192.168.1

When that did not work, then I tried Obtain IP Automatically.

Since I have not received any advice on what diagnostic steps to try, I have no choice but to try anything.

I made it clear that I do not have much knowlege on how routers communicate.

This forum to date has not been helpful with anything in the way of instruction or diagnostic help. Instead my posts are ridiculed with snide remarks and ZERO helpful information.

I came here for information, knowlege a possible solution or conclusion, not sarcastic comments.

I posted everything that I see on the router and what attempts I have made to rectify the issue with my router.

I ignored the "resident troll" remark but now, maybe I understand the comment. So far, I have not received any meaningful help and anything I try using my limited knowlege only begets snide remarks and no help whatsoever.

I think the adage "If you can't say anything nice, don't say anything at all" should be practiced.

My  adage: "if you can't help provide knowlege, solutions or conclusional help, don't "help" at all".