Following instructions are provided without any warranty, and may even get you in trouble legally. The instructions are provided for testing, learning, preventing e-waste, and should be use with care. We (including contributers + commentators) are not responsible for any damage to your device(s) or any legal issues.
Instructions have been moved to https://github.com/francoism90/asus-router. :)
Interesting on my GT-AC2900 160mhz becomes unavailable if these entries are set to anything but undefined (default setting):
nvram set location_code=
nvram set wl_country_code=
nvram set wl_country_rev=
I have to clear nvram to enable 160mhz again, nvram unset doesn't work. Not sure if all three entries cause it to break or just one of them.
@pabrognara You could test the latest changes I've pushed. It basically removes the cap limit, but I'm still finding out how it actually works. So I don't recommend actually doing nvran commit after (unless you don't mind a hard reset on connection issues).
For me after those changes, I finally have 160mhz working. Strangely enough it's only working for radio-1 on my AiMesh node. I think it's because they want you to use radio-2 for AiMesh to work when using it as a wireless node, and they don't allow to have multiple 160mhz bands. Hopefully I can get both working, radio-2 is stuck at 20mhz/149.
@Sildurs-shaders Are you testing on multiple devices? Some may decline upper channels or use LAR (see README), meaning you may have to force a channel.
You could test my latest commit (uncomment those lines), which basically removes the cap limit as well. But I still don't fully understand how they work. So use it at your own risk.
I've also added tools/reset.txt. I use ACS again, which may work getting them connected again.
Did a lot of rebooting and nvram clearing to figure out which entries broke it and tested it by going in media bridge mode and connecting it to my main router. It forces my main router in to 80mhz mode if those entries are changed and if I check the GT-AC2900 in router mode the tick box / selection for 160mhz is also gone. Nvram clear and changing everything but those three entries restores 160mhz functionality. (or one of them, haven't tried them one by one because it's pain in the ass to wipe nvram all the time)
@Sildurs-shaders Is this an AiMesh node? If so, is it wired backhaul or wireless?
You don't need to do nvram commit. You can test/set the nvram setting, and restart the wireless of your router. This is actually the recommended approach. I'll try to add the restart command later. It's something like service restart wireless, but cannot test right now.
If you don't have any cable/ethernet, you could also use the 2.4GHz channels as a backup.
@francoism90 > @pabrognara You could test the latest changes I've pushed. It basically removes the cap limit, but I'm still finding out how it actually works. So I don't recommend actually doing nvran commit after (unless you don't mind a hard reset on connection issues).
Would u pls copy those lines here? So I can try nvram and commiting without creating a script
BTW I am testing an ax88upro and last FW with my settings backup and it is working flawlessly without "dropping" to 80mhz when a non 160mhz device is connected to it.
@pabrognara Please see repo in first post.
Curiously as I said using firmware 46061 it works perfectly but really cant use the lastest firmwares to keep 160mhz in the main ax86u router. I also tried to reset without Ai mesh and didnt work. Once a 80mhz device connect to it, it downgrades to this bandwidth.