Does this mean I need to first flash buffalo to dd-wrt (aka this: buffalo-to-dd-wrt_webflash-MULTI.bin) or this is legit dd-wrt and I can flash it normally (aka this: whr-hp-g300n-firmware-MULTI.bin)?
Second, regarding the current build, http://www.dd-wrt.com/site/support/router-database this page gives very confusing results (both in release date and the supported build number) compared to the buffalotech.com page or even the FTP. I have to assume that the FTP has the newest builds, despite being beta.
To answer your second question: Best and current build for you is whatever works. I only managed to install r32597 at the moment. If you manage to install anything higher let me know too. You can read my post if you run into a similar problem with upgrading.
To answer your second question: Best and current build for you is whatever works. I only managed to install r32597 at the moment. If you manage to install anything higher let me know too. You can read my post if you run into a similar problem with upgrading.
Edit: shrunk image
Thank you very much. I'll try flashing soon and will report back.
Before that I'd like to know though, how does one know that you're not able to flash above r32597? By that I mean does the flashing just stop/get cancelled? Or does not start because it does not accept the provided image? Or do I find that out after the router supposedly finished flashing and it's (soft-)bricked or something else is just plain wrong? To be honest I'm betting on the former, dealing with the latter seems quite painful as I have do not have much experience with flashing routers or recovering it from a softbrick.
@LordRevan
You'll flash the firmware and it will either fail or succeed. Failing will be obvious that the firmware failed to upgrade - either being too large or something else went wrong.
If it's showing up as succeeded but you're still on the same version then it's not upgrading - can't, won't; even with different browsers and clearing cache. Something might be wrong with the bootlooder from what I'm reading? Or maybe the WHR-HP-G300N just can't? I don't know until someone can confirm.
I've soft-bricked my router twice now; once from upgrading with WHR-G300N firmware(not the same as our routers) and second was from messing with the bootloader. Read the guide I had linked in my other post and you'll recover easily with TFTP if anything goes wrong.
I'm reporting that I was able to upgrade successfully, however as you all have already experienced - only to r32597 unfortunately, all newer builds failed.
Does anyone have any information why all newer builds fail? Has anyone looked into it or is aware of an issue?
Thank you all for the answers, I'll keep waiting for a future build that will work.
I guess I wasn't clear enough so here's the link to my post This is a link
The gist of it is that the linux partition is too small so we have to combine the firmware with the fullflash. And in order to do that we also need to know the size of the bootloader. Whether this will work on our routers I have no clue.
I don't want to risk permanently bricking my router if I'm wrong and I haven't received any word if it'll work either. It's also trickier than just combining the fullflash partition with the firmware.
I guess I wasn't clear enough so here's the link to my post This is a link
The gist of it is that the linux partition is too small so we have to combine the firmware with the fullflash. And in order to do that we also need to know the size of the bootloader. Whether this will work on our routers I have no clue.
I don't want to risk permanently bricking my router if I'm wrong and I haven't received any word if it'll work either. It's also trickier than just combining the fullflash partition with the firmware.
Since the update didn't brick it, I just barelly skimmed that topic, but thanks for the answer, I understand now.
However I am just a little confused as to what changed so much in later builds of the firmware that it cannot be upgraded any further? Pior versions work fine and I was able to upgrade. Could this be addressed in a future build by the dev team though? Or flashing "properly" by doing dumps and combing them with hex editors is the future of all builds for this router now? That in my opinion is putting too much responsibility on someone like me, who is unfortunatelly not experienced enough with this.
The point I am trying to make is that my hardware did not change, but the code did change, so basically: what gives? Do I cross my fingers and hope for the best with a future build or just abandon this router and get a new one?
I share your opinion about not wanting to brick the router, so no experimentation for me for now.
