NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

CaptStevo's avatar
Apr 26, 2018
Solved

Bricked Orbit - Failed Firmware Update

Hello all,
I attempted an update to the 2.1.4 firmware tonight, and apparently didn't upload the entire file in the process of updating my router unit.

The orbit now powers on with a solid white ring, flashing power LED, and no access to the web GUI.

I tried several resets, and tried to TFTP the firmware image with no success. Has anyone had success getting support for something like this? I have had my unit for over a year so I'm worried I'm out of luck with a bricked unit.

Thanks for any help.
  • Well, I owe you a cold one for the hint to use the built-in TFTP client to attempt my unbricking.

     

    It worked!

     

    For anyone who has the same problem, I've highlighted what I used below in case you aren't as command-line savvy.

     

    My problems started after having my browser crash at about 85% through the upload doing a manual firmware update. I let the router sit for almost 30 minutes, but from then on, it would have a solid white light with an (eventual) flashing green power LED.  No amount of resets or power cycles would get it out of this state.

     

    So, I used the above mentioned article to factory reset the Orbi, and after waiting for the amber LED, then 10 flashing green LEDs, used the command: tftp -i 192.168.1.1 PUT path_to_your_firmware.img

     

     

    My screenshot looks a bit different, as I'm using Windows Powershell, not the regular command line.  When it's done, it should show "Transfer successful" - now wait!  The Orbi takes a few minutes to power-cycle and get set up.  Head to orbilogin.com and complete the initial setup.

     

    Here are a few links to get set up with Windows TFTP and a guide on how to flash.

    Install TFTP on Windows 7/10: https://www.pcwdld.com/tftp-client-for-windows-7

    Use TFTP to flash via command-line: http://visihow.com/Perform_a_firmware_recovery_on_a_router (Use STEP 7)

     

    Thanks again, disaster averted!

7 Replies