If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Strange, because I loaded the Netgear firmware over serial connection after I bricked my v2 and it would not accept the 00 firmware (unless it was some freaky coincidence). It flashed without a problem after I changed the header to 30.
TFTP proably does not accept it, as netgears broadcom cfe checks the header to the one burned in flash. But firmware can do whatever it wants. But anyways this is really shitty, as netgear only offers T00 chks. I downloaded all of them today. Means, if you want to tftp factory fw you can't unless you know that you have to modify the header. I guess offering different chk's won't be as confusing, and inside it doesn't matter, we can just accept the T00 and it is the same netgear fw anyways.
Das habe ich mir schon gedacht I have used DDWRT for years and flashed and unbricked a lot. It’s a learning experience. Yes all firmwares have the 00, I figured that out pretty quick when I loaded them in the hex editor. I agree that tftp probably isn’t working unless the header is changed to the necessary value. It shouldn’t be a problem for the v1, if I’m not mistaken the board ID there is 00 anyway. Thanks again for your great work over the years... (fanboy moment haha). And I can always appreciate a fellow German.
If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Posted in a parallel forum... 6700v3 board ID U12H332T77_NETGEAR
If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Posted in a parallel forum... 6700v3 board ID U12H332T77_NETGEAR
Well, I couldn't refuse any opportunity to join in playing with the R6400V2. I was in the US on Friday and picked up a couple and a very good price at Best Buy ($90 US$) and moved two to DD-WRT (thanks again Kong!!!). All were the U12H332T30_NETGEAR version.
The two I did went smoothly, though I have always disliked Netgear's stupid auto config tool when you first start one up out of the box.
Now I just have to figure out what to do with them...lol _________________ NetGear R7800 x2
Netgear R7000P
NetGear R6400V2 x 4
Buffalo WZR-HP-AG300H
Buffalo WZR-HP-G300NH2
Linksys WRT54G x3
Cisco NGFW
If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Posted in a parallel forum... 6700v3 board ID U12H332T77_NETGEAR
Build will come shortly, just need someone brave to test:-)
Are we moving closer to an official release of the build ? Anyone knows ? The one in the test folder has been standing for a while now...
If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Posted in a parallel forum... 6700v3 board ID U12H332T77_NETGEAR
Build will come shortly, just need someone brave to test:-)
Are we moving closer to an official release of the build ? Anyone knows ? The one in the test folder has been standing for a while now...
What you mean by official? The detection fix will be in the next BS release if that's what you meant by official. Other than that all releases are beta. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
If anyone has trouble getting the stock firmware to install again... you might have to load a hex editor and open the Netgear firmware and adjust the board ID to the one your router has... I haven’t checked lately but the one that Netgear posted as a download for the v2 actually was the same file as the v1 version (ID ending in 00, which did not work for my v2).
Already committed a change that accepts T00. I just checked netgear fw page an itseems like they use T00 for all of these models. Thus they have a unified fw for R6400v1/R6400v2/R6700v3. Does anyone have the boardid from the R6700v3 at hand?
This also meas, we do not need different chk files for the R6400v1/R6400v2/R6700v3, we just need to use T00 header for all of them.
Posted in a parallel forum... 6700v3 board ID U12H332T77_NETGEAR
Build will come shortly, just need someone brave to test:-)
Are we moving closer to an official release of the build ? Anyone knows ? The one in the test folder has been standing for a while now...
What you mean by official? The detection fix will be in the next BS release if that's what you meant by official. Other than that all releases are beta.
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Mon Sep 10, 2018 17:55 Post subject:
The (minor) differences between Kong's and BS's build are explained in the guide.
Both use the same repository (source code), so I would classify both as official.
I personally use Kong's, he tests his builds for the routers he supports and ddup for upgrading is great, but that is my personal preference.
At the moment you can only use Kong's TEST build because BS has not released a build after buildnumber 36820 (the build with support for all R6400v2) or after 36840 (support for R6700v3).
But if BS makes a new build available all users with R6400v2 and R6700v3 can also use that build
All builds are beta so check the build threads for problems before upgrading.
Beside a TEST build Kong keeps a regular build which he knows has been working on most routers he supports without a problem (But as explained not yet for the R6400v2 or R6700v3)
Question: if `nvram show | grep boardid` returns the xxx20 version is it still safe to use BS builds?
[OT]
Btw: honestly if I knew Netgear did such nasty things (changing HW with the same model and making it so difficult for customers to know which version they have or are buying) I would've opted for something else I think. I mean... they don't have to support unofficial firmwares but they know they exist and IMHO it's not good for their image if they do such things. I think routers are still behind years and years (if compared with what happened with smartphones for instance) when it comes to aftermarket modifications and since it is such a crucial component of a network, I think it shouldn't be so. Thank God there are people and companies like NewMedia trying to make some things better.
[/OT]
I have used DDWRT for years and flashed and unbricked a lot. It’s a learning experience. Yes all firmwares have the 00, I figured that out pretty quick when I loaded them in the hex editor. I agree that tftp probably isn’t working unless the header is changed to the necessary value. It shouldn’t be a problem for the v1, if I’m not mistaken the board ID there is 00 anyway. Thanks again for your great work over the years... (fanboy moment haha). And I can always appreciate a fellow German.