Posted: Tue Mar 23, 2021 17:14 Post subject: R7800 only works with 1 Build. (Other builds loop) :?
I bought an used R7800 recently just to experiment with and compare to the R7000 I have been using for the last few years.
Change from OEM to Kong 40270 worked just fine. Erased nvram and all was good until I tried to upgrade to BS r46069. The firmware upgrade put the router into boot loop.
After using TFTP to go back to OEM, I again went to Kong 40270 without issue. This time I tried to go to BS r45632 but had the same bootloop issue as before.
The last thing I tried was going directly from the OEM firmware to r45632 without going to 40270 first, but the router still went into boot loop.
I've read about some R7800's having bad blocks, and am wondering if that is what's going on with this router, but what is special about the 40270 build that allows the router to work correctly?
I'll also add that when it arrived, it was running the latest stock NG firmware (V1.0.2.80). The couple times I had to use TFTP recovery, I used V1.0.2.62 just in case I wanted to enable telnet for some unknown reason.
I might try a couple earlier builds of DD-WRT just to see what happens.
Joined: 16 Nov 2015 Posts: 6407 Location: UK, London, just across the river..
Posted: Tue Mar 23, 2021 18:47 Post subject:
I do have some old, Kong's factory builds and some old Stock builds for R7800, give me a shout if you need any of those...2 days ago i used an old Kong factory to revert after 46130 gone bad..
In my all experience with R7800 (various made in's) never had a flashing issue, but i know there are few reports here in the forum, I guess its either bad blocks or flash chip funny...if TFTP is not helping you out, just forget it...do keep in mind last few BS builds are bigger... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Restore the R7800 back to stock firmware using the attached firmware (originally provided by Kong to revert back to stock. Other methods sometime cause bootloops)
Then run the 46069 factory to DD-WRT firmware
Are you saying that I might have better luck if I'm going to DD-WRT from stock 1.0.0.40 rather than from 1.0.2.62 or 1.0.2.80 like I have been?
For Tftpd32 see anticipation window, a checkbox and value in Tftpd32 settings under advanced tftp options.
This is a way to speed up the transfer if the router for some reason times out, try setting value 1024 bytes.
Restore the R7800 back to stock firmware using the attached firmware (originally provided by Kong to revert back to stock. Other methods sometime cause bootloops)
Then run the 46069 factory to DD-WRT firmware
Are you saying that I might have better luck if I'm going to DD-WRT from stock 1.0.0.40 rather than from 1.0.2.62 or 1.0.2.80 like I have been?
I usually update to the latest Netgear version when going to stock, before switching to DD-WRT, so no harm in updating to 1.0.2.80, but using the firmware update check within the Netgear system UI of their firmwares, rather than manually downloading and updating yourself. Thanks just my preference.
Have you tried to TFTP directly a factory-to-ddwrt.img?
I haven't tried it that way. This might be a dumb question, but I'd rather ask it up front. Would there be any reason that recovering back to stock FW would be more difficult if I used TFTP to attempt loading a factory-to-ddwrt.img and failed?
Is it necessary to use Tftpd32 instead of basic windows CLI TFTP Client?
Would there be any reason that recovering back to stock FW would be more difficult if I used TFTP to attempt loading a factory-to-ddwrt.img and failed? Is it necessary to use Tftpd32 instead of basic windows CLI TFTP Client?
No, only directly writes dd-wrt, you can always flash stock again. Windows CLI may not upload fast enough.
Those two dmesg lines are not related and normal. I only know how to check from serial u-boot (nand bad).