Router Model: Netgear R8000
Firmware Version: DD-WRT v3.0-r43813 std (07/15/20)
Kernel Version: Linux 4.4.230 #585 SMP Wed Jul 15 08:52:15 +04 2020 armv7l
Previous: DD-WRT v3.0-r43800 std (07/15/20)
Mode: Client
Drivers: not experimental
Reset: No
Upgrade: via webgui
Services: Client, 5.0Ghz AC only & dhcp enabled
Load Average: 0.08, 0.07, 0.01
Temps: CPU 54.7 °C / WL2 48.2 °C
Issues: Nothing that I can see so far
flashed 38570 then did a gui reset
flashed 39345 then did a nvram erase
then flashed the rest of the kong builds without reset
then flashed the most recent build and did a gui reset
the high and low channels are there just like kernel-panic69 said
even though i did do one nvram erase on kong i thing the lesson is don't use nvram erase
apologies for all my grief
I'm assuming a bs build will work as well. I think the key is to install a build before the wifi changes first before updating to the current
did you have to run the brcm_unlock command after a you did the last reset?
How's that bruise on your forehead I left? I already knew this was going to be the answer, so best bet to have any flexibility is to flash the way I did.
Also, to note for the R8000 folks:
Quote:
brcm_unlock will also not work on all devices. specific on the r8000 with 43602 chipset it will not work since i had to replace the firmware with a official one. before i used a special hacked one
did you have to run the brcm_unlock command after a you did the last reset?
no i didn't run that command. kp did and it opened all the channels. The command doesn't survive a reset so I'd assume it wouldn't do harm. Plus many others have used it no issues
i have been tinkering with my other router. i tried flashing 38570 and then coming to the most recent build and it didn't work.
so it appears flashing one over the other must have helped.
i started on kong 38570
after resetting i set up 5 GHz 80width upper upper channel 48 and did an additional reboot to ensure the channel survived the reboot
then repeated that process through all the kongs and then finally the current build
*That router I came from stock. I installed the first firmware and let it update to the current before flashing the kong build.
**I'm just going to repeat that process on my other. Some of it might be overkill but that path worked for me.
Good luck to all
***
the comparable bs builds in the early 2019 were using the r8000 firmware
*****
installed kong 38570
then do an nvram erase
after the nvram erase you can upgrade to the current build. at first it will appear all the channels are available. after a reboot you will have the low and high channels on 80 width
if you run the nvram commit you can get them all back or just switch regions for other channels. i wouldn't do another nvram erase
gonna try to figure out the most recent bs build with all channels to revert to. Will update
bs build 38570 has the r8000 firmware in the r7000p spot
it flashes but after an nvram erase it swapped the 2.4 Ghz and 5 Ghz interfaces at it didnt look right. so i just went back to the kong build
Last edited by tinkeruntilitworks on Thu Jul 16, 2020 17:39; edited 1 time in total
@nolimitz
install kong 38570
then do an nvram erase
then try the new build
at first it will appear all the channels are available
after a reboot you will have the low and high channels on 80 width
if you run the nvram commit you can get them all back or just switch regions for other channels
doing another nvram erase will probably send you back to square one. so just do the one nvram erase
**
actually after all the tinkering this path didn't work again just now
going back to factory must play a part as well.
so go to stock
then 38570 then did a gui reset
flash 39345 then did a nvram erase
then go to the current
Last edited by tinkeruntilitworks on Thu Jul 16, 2020 18:31; edited 2 times in total
@nolimitz
install kong 38570
then do an nvram erase
then try the new build
at first it will appear all the channels are available
after a reboot you will have the low and high channels on 80 width
if you run the nvram commit you can get them all back or just switch regions for other channels
doing another nvram erase will probably send you back to square one. so just do the one nvram erase
**
actually after all the tinkering this path didn't work again just now
going back to factory must play a part as well.
so go to stock
then 38570 then did a gui reset
flash 39345 then did a nvram erase
then go to the current
will try again and see when router is not in use
@kernel-panic69
@tinkeruntilitworks
can you check your WL0 and WL1 mac addresses, what is the last octet using latest build?
for me:
on build 43813 its AA for wl0 and BB for wl1
on build 35550M its AA for wl0 and AB for wl1. something wrong here on build 43813 i guess?
i flashed kong 38570 and all the channels were there
i did a gui reset
then flashed kong 39345 and the lower channels appeared to disappear
then i did a nvram erase
after setting it back up the all channels were back
i set up 80 width upper upper channel 48
then flashed to the current build
at first it appears all the channels are available
after a reboot the lower and upper channel are available
once you get the channels i wouldn't nvram erase again
*
It was just dumb luck that kong build 38570 was one of the ones I downloaded. I went and downloaded all the 2019 builds and that was the first one. if one of the 2018 builds were the crucial one to have I surely would have moved onto something else before that
Last edited by tinkeruntilitworks on Thu Jul 16, 2020 19:38; edited 1 time in total