New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#2009 - Netgear R8000 - Unable to install OpenWRT firmware #8430
Comments
mjevans: I was able to enable telnet console with these older instructions: BusyBox v1.7.2 (2018-10-09 16:42:16 CST) built-in shell (ash) burnboardidBoard ID - U12H315T00_NETGEAR helpBuilt-in commands:
nvram show also worked, but lists over 2000 lines of key=value pairs; nearly all of which seems like junk at this point, but the password is probably somewhere in there. |
mjevans: I've also tried Netgear's current TFTP flashing instructions: https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP (though from Linux with a standalone system, NetworkManager disabled, and a static assigned address of 192.168.1.3/24 ; I was able to ping the router at the point where their instructions say to remove the paperclip.) atftp --option "mode octet" --option "timeout 60" --verbose --trace -p -l openwrt-18.06.1-bcm53xx-netgear-r8000-squashfs.chk 192.168.1.1 atftp times out several times and the router continues booting -- I'm also including Netgear's directions in case they relocate or otherwise update this page again. To upload firmware using Windows TFTP:
|
mjevans: Could this really be as simple as getting back in to the telnet connection mode and updating... board_id=U12H315T00_NETGEAR to board_id=U12H315T00_NETGEARHDR0 saving the nvram Rebooting Trying to flash the image from the web interface? Alternately, are there instructions for flashing a .chk file from said telnet interface on the factory firmware (I can arrange some way of getting the firmware in to ram)? Or should the .chk file/sources be broken apart and manually flashed in some other way? Finally, would this tool likely work for delivering the firmware I'd prefer to have on the router? |
mjevans: My attempt at getting it to take a TFTP image upload the other day did succeed in performing a 'factory reset' on the config. I made a complete backup of the flash partitions, MTD table, and some other stuff to a USB drive by:
The upgrade system webpage files are under /www/ (UPG*.htm) however they direct to a couple different .cgi files that don't actually exist in the filesystem. Grepping all the files of that magic string directed me to the /usr/sbin/httpd file, a 1628500 byte binary that seems to include the actual CGI bin files within it's self. That's probably where figuring out why it rejects openwrt firmware should focus. cat /proc/mtd My first guess is to just take the headder off of the chk image and put the result inside of: mtd2 "linux" However looking at the actual upgrade process for when OpenWRT is in use... it seems to expect a completely different set of mtd partition names, it also wants a number of binaries that don't exist as those names in the factory firmware. (E.G. mtd otrx osafeloader oseama dd) Even dd is missing (I chose to use cat to redirect the MTD sections). -- At this point I see four potential choices:
|
mjevans: I got this working my modifying mkchkimg.patch and running it manually with the extracted TRX file (starts with the HDR0 bytes, and offset specified in the header_len field). I've attached a patch to the mkchkimg program. I spent an evening trying to figure out why OpenWRT's files weren't being accepted by the r8000 that was recently purchased.
This router has a LOT of releases now, around 20 of them. Patterns become more obvious with more data. What is previously known only as a 'reserved' section with magic numbers is now far more obvious as a set of build numbers. Literally the actual numbers in the filename that I'm dumping. I'm hoping that by setting most of those numbers to higher values, I can make the router realize that this upgrade superceeds the stock firmware. $ hexdump -Cn64 openwrt-18.06.1-bcm53xx-netgear-r8000-squashfs__999999.chk $ hexdump -Cn80 openwrt-18.06.1-bcm53xx-netgear-r8000-squashfs.chk v4 magic = '*#$^' $ hexdump -Cn80 R8000-V1.0.4.28_10.1.54.chk v4 magic = '*#$^' -rw-r--r-- 1 user user 24465466 Jun 11 2014 R8000-V1.0.0.46_1.0.17.chk 01 01 00 00 2e 01 00 11 |#$^...:........| |
mkresin: Please follow https://openwrt.org/submitting-patches to submit your patch. |
mjevans:
Netgear R8000 - Unable to install OpenWRT firmware
https://openwrt.org/toh/netgear/r8000#tab__firmware_downloads
A recently purchased from Amazon Netgear R8000 (Nighthawk X6) refuses to accept the OpenWRT firmware file and there are not directions for an alternate installation method.
Full model from the back:
NETGEAR Nighthawk X6
AC3200 Tri-Band WiFiRouter
Model: R8000
FCCID: PY314200264
Made in Vietnam 272-12664-01
The text was updated successfully, but these errors were encountered: