Posted: Sun Mar 11, 2018 23:00 Post subject: WNDR3700v4 u-boot bootloader version ... ever updated?
I acquired a WNDR3700v4 last week that still had the original OEM firmware v1.0.1.32 (initial release) on it. The latest firmware v1.0.2.94 is from Dec 2017. I'm curious if the bootloader ever got updated thru OEM f/w on this model?
Got 4 of these boxes and yea they don't tend to change the uboot .. well not on same model version.
You can monkey with this stuff yoursef but there is really no point.
Two of mine run 24/7.
One is just a switch with wifi turned off but he also is an ovpn server and has a USB share device attached.
The other is at far end of my network running as a WAP + guests on both radio.
I hardly ever look at them these days -- got tired messing with them with new builds and just installed r33555 on both ...now I never have to worry with them.
If/when to get yours tangled up messing with new builds just put it in recovery and TFTP r23503 to it at 192.168.1.1
Don't ever try to reset it or anything fancy (just a waste of time) TFTP 23503 wndr3700v4.img
After it boots then you can load webif (at whatever its last IP was) then install last working build you had on it and all should be good.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Thu Mar 15, 2018 7:04 Post subject:
contact this guy https://github.com/pepe2k/u-boot_mod and send him one of yours unit... He'll update u-boot for you... and much more, you will get web server with u-boot...
Posted: Thu Mar 15, 2018 14:23 Post subject: TFTP Recovery
I just added the WNDR3700 v4 Recovery info to the dd-wrt wiki. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
contact this guy https://github.com/pepe2k/u-boot_mod and send him one of yours unit... He'll update u-boot for you... and much more, you will get web server with u-boot...
pepe2k github site wrote:
U-Boot 1.1.4 modification for routers
That is cool as hell. I'd do it if there was a pre-built image, as I'm running OpenWRT on it atm...been wanting to mess w/ it, and OpenWRT on Broadcom is schit. Plus it seems the recent DD builds have had issues (as also noted by mrjcd). So far it's working very well on a trunk build. LuCI and all is setup but still need to install the SFM QoS packages. But I digress... _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Posted: Thu Mar 15, 2018 16:58 Post subject: resets
mrjcd wrote:
Don't ever try to reset it or anything fancy (just a waste of time)
ian5142 wrote:
I just added the WNDR3700 v4 Recovery info to the dd-wrt wiki.
Thanks @ian5142; a note on the reset part... @mrjcd, I presume you mean that resetting (hard or GUI) isn't needed, so that you can retain your settings, but also isn't necessarily bad?
WNDR3700 wiki wrote:
Don't ever try to reset it (no 30/30/30, just Factory Defaults) or anything fancy.
That insinuates that a reset can cause problems; should that just say, "Reset (30/30/30 or GUI) is not necessary" ? _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
that would be cause the geniuses at netgear decided to neuter the bootloader so it cant use anything near it. i dont remember the exact number but i think we are within 0.1MB of the bricking size, as its happened at least 3 times prior. its probably fixable (as in to use bigger sizes) with a modified bootloader that is.. which apparently doesnt exist, & i assume if one was to revert to stock on it, stock fw wouldnt work _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Thus, 96 MB. caldata_backup prevents it from being extended beyond the firmware partition, and is the reason for the oversized firmware concern. There's a patch for openWRT to move caldata_backup to the end (then you copy your backup or caldata to it*), and extend the linux partition to 'reserved'; I had wondered what DD-WRT did with the partitions.
Anyone have a `cat /proc/mtd` handy?
* This is because u-boot check caldata against the backup, but the partition location doesn't matter. Would be nice to have an optional DD build to do the same thing...keep dreaming, I know. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
The size limitation is main reason
23503 wndr3700v4.img works so well to debrick (TFTP).
It is about the smallest size wndr3700v4 dd-wrt firmware you will find.
Most other (larger size) will stop several blocks from a successful TFTP.
About the reset - Post above refers to a non-resposive router after an install. Put it in recovery mode and TFTP to 192.168.1.1
After it fully boots it will have retained all previous settings --- note: this is where many think it is screwed because they cannot reach it at 192.168.1.1
IT WILL RETAIN ALL PREVIOUS SETTINGS so if it didn't have an IP of 192.168.1.1 you cannot reach it there .....IOW that address is set in uboot for TFTP and it don't give a damn what is in nvram.
Normal reset should use CLI 'erase nvram && reboot'
The GUI reset to factory don't work very good on 'bout half the builds and I wouldn't ever use the reset button -- besides there are several past builds where the reset button don't work anyways
