Did this coupon
work for you?
work for you?
Forum Thread
looking for tech-savvy TM-ac1900 / RT-ac68u router owners to help me test a firmware upgrade/download multitool
So if you're reading this, you probably are aware of the thousands upon thousands of comments on SD in the deal posts for this router, full of people trying to upgrade/downgrade/otherwise modify their routers... maybe you even know the process is really not even that hairy... it just requires attention to detail that many people apparently can't muster. ...Or at the very least, it requires some monotonous annoying operations to get where you wanna go.
So I made a pile of powershell scripts that anyone with a pretty recently-updated Windows computer should be able to use without need to deal with other software. Since you could re-badge your tmo fw to stock asus firmware, I called the project The Badger... it's basically just a "user friendly" menu script wrapped around a bunch of separate operations:
You don't even need to flash anything if you don't want to -- just take a look at this thing, lemme know if there's an obvious improvement that needs to be made, suggestions, etc.
Project page: https://github.com/jasonbuechler/asus-rebadger
Video demo: https://www.youtube.com/watch?v=J7SYNOZ
So I made a pile of powershell scripts that anyone with a pretty recently-updated Windows computer should be able to use without need to deal with other software. Since you could re-badge your tmo fw to stock asus firmware, I called the project The Badger... it's basically just a "user friendly" menu script wrapped around a bunch of separate operations:
- download Tmo CFE to local.ps1
- module context strings.ps1
- secret sauce to clean MTD.ps1
- select ethernet adapter.ps1
- set auto IP by DHCP.ps1
- set manual IP in subnet 1.ps1
- set manual IP in subnet 29.ps1
- show current network config.ps1
- TFTP flash old Tmo FW via subnet 1.ps1
- TFTP flash old Tmo FW via subnet 29.ps1
- upload mod-CFE etc then write CFE and FW.ps1
- wait for router to return on subnet 1.ps1
- wait for router to return on subnet 29.ps1
You don't even need to flash anything if you don't want to -- just take a look at this thing, lemme know if there's an obvious improvement that needs to be made, suggestions, etc.
Project page: https://github.com/jasonbuechler/asus-rebadger
Video demo: https://www.youtube.com/watch?v=J7SYNOZ
If you purchase something through a post on our site, Slickdeals may get a small share of the sale.
20 Comments
Your comment cannot be blank.
Sign up for a Slickdeals account to remove this ad.
But not working for me. I have posted the issues to the github.
But not working for me. I have posted the issues to the github.
There's a likely solution to your apparent inability to use the TFTP stuff, BUT... before you go immediately fixing everything, I was hoping you could tell me some more about your particular router, and maybe grab me some files off of yours, since I could do more testing if I had them, I suspect. Also, could you verify what version of firmware you have on your router, that appears to have it locked down so hard?
thanks!
So when I got up this morning, I saw a merge request on github from someone who had found a bad oopsie with the then-latest version (2.5). I just uploaded a newer version (2.6) that fixes that. (I had combined 2 old scripts into one but part of the "main menu" was still pointing to a no-longer-existing old script.)
I'm a little concerned, though, about it pinging so long without success. ...and I now realize I prooobably need to add some code to *not* proceed if it never successfully pings the router. ...or at least some verbiage saying "this doesn't look right!"
Up until recently, the router will respond to pings while it is in recovery mode, but I have no idea if this is still true in 3199 and beyond... @pterrell do you know?
In any case, it won't hurt to get the 2.6 release and try that out instead.
The bad news is you may be in the same boat as @pterrell with one of the "unlucky" recent units that reportedly show an apparently unusable miniCFE and don't respond to TFTP... but the good news is, there's a workaround. It's not difficult, but it is involved. I link to it from this part of my wiki: https://github.com/jasonbuechler/...leshooting I'd gladly help you through it if you should need any advice/assistance.
I followed the NO CFE USB INSTRUCTIONS on the google doc guide. It took me a while (I'm not an IT guy, just someone who likes to tinker), took me a while, but it worked.
I'm now on the latest ASUS firmware.
In any case, it won't hurt to get the 2.6 release and try that out instead.
Sign up for a Slickdeals account to remove this ad.
It tried the regular efforts with bayareatech/lazyMocha site, but could not get the cfe page to work. Next spent time on the serial procedure since I had a usb to serial adapter from messing with arduino stuffs. That was close but I could not get the CFE to accept commands from putty. Gave up on that when I think I fried my usb-2-serial (I tried the logic-level adapter but think I may have applied too much voltage to the serial adapter by accident)
Luckily the router still worked as usual so I then attempted the web server method and that finally worked with Fenix app for windows 10. The usb method would've probably worked but I am interested in setting up a home server anyway and thought it would time well spent.
Your scripts seem really convenient and I was thinking of something like this the whole time I was attempting each method. I will keep this on the back burner in case this new firmware (3.0.0.4.384.45717) causes issues!
It might not belong here but I did the MTD5 clean up but am hesitant to update. Any one tried it yet (Version 3.0.0.4.384.45717 - 2019/05/13)??
It tried the regular efforts with bayareatech/lazyMocha site, but could not get the cfe page to work. Next spent time on the serial procedure since I had a usb to serial adapter from messing with arduino stuffs. That was close but I could not get the CFE to accept commands from putty. Gave up on that when I think I fried my usb-2-serial (I tried the logic-level adapter but think I may have applied too much voltage to the serial adapter by accident)
Luckily the router still worked as usual so I then attempted the web server method and that finally worked with Fenix app for windows 10. The usb method would've probably worked but I am interested in setting up a home server anyway and thought it would time well spent.
Your scripts seem really convenient and I was thinking of something like this the whole time I was attempting each method. I will keep this on the back burner in case this new firmware (3.0.0.4.384.45717) causes issues!
It might not belong here but I did the MTD5 clean up but am hesitant to update. Any one tried it yet (Version 3.0.0.4.384.45717 - 2019/05/13)??
See post #14 for the update!
Thanx
I'll update this post as I continue.
Thanx
Hey Kulardenu -- obviously I can't promise anything, but my gut says the 90% likely answer is 'yes', or at least "somewhat yes" ... if you bought yours that long ago, then I think the odds are good (unless you were really on top of upgrading your firmware) your existing firmware is the "pretty simple" kind that worked perfectly for The Badger up until very recently, where Asus crippled the connectivity options.
At the very least, you can use some of the specific tools in it to do onerous or complicated parts of the bayarea instructions... each one is compartmentalized... so, for example, if you just wanted a quick way to set your ethernet adapter to a manual IP address: boom done.
Plus you're not at any disadvantage trying: if yours is TOO updated and doesn't work, then the flow of the options leads you to a "well you're probably out of luck and need to try the new 'hack' located at the following address...."
lemme know, I can help! message me if you wanna hit me up on Hangouts or facebook.
At the very least, you can use some of the specific tools in it to do onerous or complicated parts of the bayarea instructions... each one is compartmentalized... so, for example, if you just wanted a quick way to set your ethernet adapter to a manual IP address: boom done.
Plus you're not at any disadvantage trying: if yours is TOO updated and doesn't work, then the flow of the options leads you to a "well you're probably out of luck and need to try the new 'hack' located at the following address...."
lemme know, I can help! message me if you wanna hit me up on Hangouts or facebook.
Thanx!
Hey Kulardenu -- obviously I can't promise anything, but my gut says the 90% likely answer is 'yes', or at least "somewhat yes" ... if you bought yours that long ago, then I think the odds are good (unless you were really on top of upgrading your firmware) your existing firmware is the "pretty simple" kind that worked perfectly for The Badger up until very recently, where Asus crippled the connectivity options.
At the very least, you can use some of the specific tools in it to do onerous or complicated parts of the bayarea instructions... each one is compartmentalized... so, for example, if you just wanted a quick way to set your ethernet adapter to a manual IP address: boom done.
Plus you're not at any disadvantage trying: if yours is TOO updated and doesn't work, then the flow of the options leads you to a "well you're probably out of luck and need to try the new 'hack' located at the following address...."
lemme know, I can help! message me if you wanna hit me up on Hangouts or facebook.
(These were the issues I ran into while trying the conversion. Not all were due to your script but left them for a holistic view of the process for any others trying this.)
- powershell wasn't starting due to some .net issues/ couldn't edit group policy - reverted windows back to clean install
- couldn't run scripts on this machine - Had to set the execution policy in powershell using this command 'set-executionpolicy remotesigned' (or unrestricted)
- tftp : The term 'tftp' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. tftp not installed - was using powershell_ise - switched to just powershell and it found tftp just fine.
- router wouldn't downgrade software. Had to use web server (used it last time and am familiar with it now) (I downloaded mini http server from microsoft app store for free)
- after flashing 1703 and setting up ssh. I skipped to 'F' but got the error: Cannot find path \.ssh because it does not exist - it was pointing to my machine as if I had a ~/.ssh/ locally (was it looking for linux??) - seemed to resolve itself and prompted for password
- 'password' didn't work - used admin - (probably because I uploaded the 1703 fw through web server)
- scp: /root/original_cfe.bin: no such file or directory - using bayareatechpros and this command in putty 'cat /dev/mtd0 > original_cfe.bin' to create it and then copy it out
_________________________After this was able to use the script to push through the MTD5 partition and allow unlocked firmware and finally finished the setup!
Let me know if you have any questions. I'll try to help out as much as I can!
Thanks for the script!
linux: CRC OK
Bus error
I ignored it and so far seems to be up and running.
My original firmware is (and still is) 3.0.0.4.376_3108. Was hoping this was a good FW but...
Took a bit in powershell but got the scripts to run. But then it was a No Go. I get as far as "E" All the IP addys and gateway get set fine but when I get to installing the file I the following.
Connect request failed
If Mini-CFE webpage won't load use Asus Restore Utility
If having trouble with this step perform NVRam Reset and try #6 again (see step #20)
Flash TM-AC1900_3.0.0.4_376_1703-g0ffdbba.trx
Not sure how I would do a web server to flash the downgrade software.
Bit of a head scratcher. Any ideas where I can go from here? I looked at the Google doc "From AC1900 To AC68U After Revert [google.com]" but does not seem to be what I need.