Posted: Thu Sep 14, 2017 11:52 Post subject: firmware not upgrading Buffalo whr-g300n v2
Hello,
I have been running dd-wrt on two separate Buffalo whr-g300n v2 for a couple of years in order to run hotspotsystem software.
Both run build 21676.
However, the build has not always been completely stable therefore I have been waiting for a suitable firmware replacement. Builds later than this seemed to have an issue whereby a WAN address could not be obtained therefore I downgraded back.
Recently I have tried again, but when I try a firmware upgrade, the firmware upgrade is said to be successful, however the build never does, and stays at 21676 after the router reboots. Note that this is through the admin user interface.
I have also attempted with tftp but with no success yet. I have seen guides but I would like to double check I am doing this correct (using Windows):
Reset the router to factory defaults
connect to router via lan port
set a static ip on the interface compatible with router factory defaults - 192.168.1.100, subnet 255.255.255.0 - still auto dns
set retries in tftp2 to > 10 - do I reboot router at this point or wait until it has completely booted?
set tftp2 ip to 192.168.1.1
press start / connect
If I am doing something wrong or if anyone has any suggestions it would be greatly appreciated.
Posted: Thu Sep 14, 2017 14:55 Post subject: Update
Hello,
Using telnet I have managed to update to build 32170 so far, the newest builds are giving the following errors when the "write firmware.bin linux" is performed:
function stop_snmp not found
function stop_olsrd not found
function stop_openvpn not found
function stop_openvpnserver not found
function stop_freeradius not found
Image too big for partition: linux
linux: Invalid argument
I am going to continually update and report which firmware is the latest I can update to.
I have found that the 01 Jun 17 firmware is the newest whereby I can telnet into the router, download and install the firmware without any error. (and the hotspot still works as expected).
To be honest I am quite happy with the firmware for now, much better than running one from 4 years ago.
I am now getting myself into firewall rules at the moment. Wish me luck!
I have found that the 01 Jun 17 firmware is the newest whereby I can telnet into the router, download and install the firmware without any error. (and the hotspot still works as expected).
To be honest I am quite happy with the firmware for now, much better than running one from 4 years ago.
I am now getting myself into firewall rules at the moment. Wish me luck!
The reason of failed upgrading firmware you can see in telnet session:
root@DD-WRT:/tmp# write whr-g300nv2-firmware-MULTI.bin linux
function stop_snmp not found
function stop_olsrd not found
function stop_openvpn not found
function stop_openvpnserver not found
function stop_freeradius not found
Image too big for partition: linux
linux: Invalid argument
It's because the very first firmware (buffalo-to-dd-wrt_webflash-MULTI.bin) you choose to upgrade from stock Buffalo firmware to dd-wrt has formatted linux partition with so small size and it was not enough for firmwares from July until now
Solution: go back to stock g300n firmware and after that go back to dd-wrt with latest buffalo-to-dd-wrt_webflash-MULTI.bin file (r33345) so that we will have new partitions stucture
Solution: go back to stock g300n firmware and after that go back to dd-wrt with latest buffalo-to-dd-wrt_webflash-MULTI.bin file (r33345) so that we will have new partitions stucture
Thanks for the info. At least now we know how to upgrade in the future.
Hi,
I've encountered the same problem and the proposed solution provided by khoanb1 doesn't seem to work.
I've tried to flash multiple new builds and the newest one I got to work was r32597. The newest that I've tried is r33555.
I've tried flashing from DD-WRT web GUI and also by downgrading back to Buffalo firmware (v1.85) and then using Buffalo Web GUI:
- DD-WRT doesn't give any errors, but instead just doesn't flash the new image.
- Buffalo Web GUI immediately tells that the image is too large.
I believe the new images seem to be just a bit too large. As khoanb1 pointed out the 'linux'-partition size is 003a0000 ie. 3801088 bytes. For example the newest image (r33555) is 3862556 bytes, which is slightly too large.
Are there any workarounds to reduce the image size or somehow increase the 'linux'-partition size?
Hi khoanb1,
I've tried going back to Buffalo firmware and then tried to flash the newest dd-wrt from there, but it doesn't work. It just says that the image is too big. Check my post above for more details.
It looks doable, but I have no idea if this is basically the same problem or not, so I haven't tried it in fear of bricking the device. Has anybody tried that or has any other info regarding to that approach with this device?
Hi,
I took a look at the instructions in here https://www.dd-wrt.com/phpBB2/viewtopic.php?t=311642, but it says there that 'factory-to-ddwrt.bin' should be used. In case of Tplink-routers the factory-to-ddwrt.bin seems to be a "raw" image compared to tl-[model]-webflash.bin which contais a header beginning with magic 'HDR0' and with size of 28 bytes.
See here:
Now in case of Buffalo WHR-G300Nv2 the 'buffalo-to-dd-wrt_webflash-MULTI.bin' contains some kind of encrypted firmware to be used with Buffalo stock firmware. I presume that can't be used. So what is left is 'whr-g300nv2-firmware-MULTI.bin'. This contains the same header as the Tplink-images (beginning with 'HDR0', 28 bytes long) and then the image itself (starting with magic 27 05 19 56):
00000000 48 44 52 30 1c 00 3a 00 a8 ae c3 82 01 00 01 00 |HDR0..:.........|
00000010 1c 00 00 00 00 00 00 00 00 00 00 00 27 05 19 56 |............'..V|
00000020 43 6f 46 b9 59 60 33 b0 00 0d 7c ea 80 06 00 00 |CoF.Y`3...|.....|
Now my question is:
Will it work if I remove the header (ie. remove the first 28 bytes) and create a new image for fullflash with following layout (as in the instructions in the other thread):
[boot] (this is 262144 bytes long)
[whr-g300nv2-firmware-MULTI.bin WITHOUT the first 28 bytes] (this is 3866652 bytes long)
TOTAL: 262144 + 3866652 = 4128796
Full flash size is 4MB (ie. 4194304 bytes), so it should fit there. Is there something else than boot + linux partition that needs to be considered here?
And if all this works out is the "linux" partition resized to fit these new bigger firmwares or do I have to flash it like this in the future too?
Hopefully someone could confirm that this approach is feasible, so I could try it!
Posted: Wed Nov 29, 2017 4:36 Post subject: Stripping a build
First of all, no you can not easily cut a build down to make it fit on the router's flash.
The best thing you can do is create a ticket on the SVN to let Brainslayer know about the problem. We had this issue with the Linksys 160N v3 for about 6 months I think before it was fixed.
Don't expect it to happen over night. Also, in order for Brainslayer to make it fit some features that the router currently has may have to be excluded (VPN, Hotspot, etc). Some of those features may have already been excluded.
I would not suggest what you are attempting to do, you will most likely end up with a brick. _________________ 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
Posted: Sat Dec 02, 2017 16:44 Post subject: Re: Stripping a build
ian5142 wrote:
First of all, no you can not easily cut a build down to make it fit on the router's flash.
The best thing you can do is create a ticket on the SVN to let Brainslayer know about the problem. We had this issue with the Linksys 160N v3 for about 6 months I think before it was fixed.
Don't expect it to happen over night. Also, in order for Brainslayer to make it fit some features that the router currently has may have to be excluded (VPN, Hotspot, etc). Some of those features may have already been excluded.
I would not suggest what you are attempting to do, you will most likely end up with a brick.
Did anyone create a ticket to the SVN yet ?
On my Buffalo WHR HP-G300n the update is also failing .