T-Mobile Wi-Fi CellSpot Router (TM-AC1900) - Certified Pre-Owned $39.99 plus free shipping

Jan 29, 2019

1,655 Posts

Quote from stnick

:

So I literally tried everything you mentioned except trying incognito mode as I didn't see that posted anywhere. Perfect worked and was able to flash. You sir are amazing.

HAHA!
That is great news Big Grin

Interesting though.

Incognito Mode:
Chrome won't save the following information:

Your browsing history

Cookies and site data

Information entered in forms

Last edited by User17347427 January 28, 2019 at 10:56 PM.

ST1NGY

Jan 29, 2019

1,570 Posts

Joined Oct 2009

Jan 29, 2019

Jan 29, 2019

1,570 Posts

Quote from Hawbgobblin

:

Perhaps, it is time for me to upgrade from Version 3.0.0.4.384.32799 Ha ha

Full disclosure. The first time I installed 384.45149 I had some trouble getting to devices connected to one of my wifi range extenders. I use several to extend the reach of my Guest SSID for (untrusted) smart devices too far from my main ASUS router. Anyway, after installing 384_45149 I noticed that my client list was about 12 short of the normal number of clients. Rather than screw around and disrupt my network in the middle of the day, I quickly fell back to 384.32799.

A couple days later on a quiet weekend I gave 384.45149 another try. I still got fewer than expected clients in the client list, but I found that those missing clients were still accessible through their apps. These were some smart switches/bulbs/cameras. I realized that the clients that connected through one of my range extenders were missing but I could log-in to the extender's gui and see them. They even got assigned IP addresses from my main router's DHCP server.

So the problem is caused by some change in how the ASUS web gui displays clients, or some incompatibility with my range extender. Otherwise everything was working. I decided to stay with 45149 since it had some security fixes and (supposedly) other performance fixes. Everything else seems good.

new_yorker

Jan 29, 2019

1,220 Posts

Joined Dec 2010

Jan 29, 2019

new_yorker

Jan 29, 2019

1,220 Posts

Quote from ST1NGY

:

Full disclosure. The first time I installed 384.45149 I had some trouble getting to devices connected to one of my wifi range extenders. I use several to extend the reach of my Guest SSID for (untrusted) smart devices too far from my main ASUS router. Anyway, after installing 384_45149 I noticed that my client list was about 12 short of the normal number of clients. Rather than screw around and disrupt my network in the middle of the day, I quickly fell back to 384.32799.

A couple days later on a quiet weekend I gave 384.45149 another try. I still got fewer than expected clients in the client list, but I found that those missing clients were still accessible through their apps. These were some smart switches/bulbs/cameras. I realized that the clients that connected through one of my range extenders were missing but I could log-in to the extender's gui and see them. They even got assigned IP addresses from my main router's DHCP server.

So the problem is caused by some change in how the ASUS web gui displays clients, or some incompatibility with my range extender. Otherwise everything was working. I decided to stay with 45149 since it had some security fixes and (supposedly) other performance fixes. Everything else seems good.

I have noticed this behavior as well, it seems the issue is with GUI how it displays the client list. The client list shows 16+ devices initially on the page and suddenly shoots up to 31 ( my actual no). So I assume it's GUI and and may be refresh rate/time.

ST1NGY

Jan 29, 2019

1,570 Posts

Joined Oct 2009

Jan 29, 2019

Jan 29, 2019

1,570 Posts

Quote from new_yorker

:

I have noticed this behavior as well, it seems the issue is with GUI how it displays the client list. The client list shows 16+ devices initially on the page and suddenly shoots up to 31 ( my actual no). So I assume it's GUI and and may be refresh rate/time.

That's a different issue. My client list and the count is fairly stable, just incomplete. It never shows the full list - clients connecting through my TP-Link RE450 extender are missing. It does show clients connected through my other TP-Link TL-WA855RE extenders.

Keep in mind that some clients do not do not stay connected full-time. My android phones used to disconnect from wifi in standby mode (to conserve power - I fixed by changing settings). Some smart devices just connect periodically. The router doesn't have an accurate way to determine if a client goes away. So the list gets rebuilt every couple seconds (guestimate) based on recent activity. I think that accounts for some of the observed client list instability. I just don't spend much time watching it (better things to do) unless I am having some connectivity issue on my LAN. So this issue doesn't bother me.

Last edited by ST1NGY January 29, 2019 at 11:08 AM.

johnny2x4

Jan 29, 2019

1,549 Posts

Joined Nov 2012

Jan 29, 2019

Jan 29, 2019

1,549 Posts

// EDIT: corrected a few references

sharing my two cents after getting help on SD from another user - I used the steps below to reflash the router (mine had been in use and connected online previously)
https://www.bayareatechpros.com/ac1900-to-ac68u/

those steps are almost perfect, except that when running the code for fixing the mtd5 partition (after steps 1-22 are complete and confirming you're on Asus firmware), putty will hang on "./mtd-erase -d asus" so you need to go to the router UI and update the firmware to version 384 which can be found here [softpedia.com], Reset NVRAM after firmware install, and then re-run the remaining (or all, it's just redundant) code for fixing MTD5 partition

Couple other tips:

on step 15 remember to rename it to new_cfe.bin after downloading it since no error feedback will be provided if you don't and the following steps won't work otherwise (you'll remain on the t-mobile firmware)
to echo some users above, using chrome incognito mode helps a ton both for finding and seeing updates to the router webUI and recovery pages, since sometimes chrome caches stuff and it won't update on chrome.
if you complete all the steps successfully, but you plug in the router to your network and there is no internet, your cable/fiber modem may coincidentally be on the same default IP as the router is. To fix this, go to the router webUI and on the status page you'll see an error stating an IP conflict which you can click so the router will change itself to a different IP

Last edited by johnny2x4 January 29, 2019 at 01:59 PM.

Zwitterion

Jan 29, 2019

1,178 Posts

Joined Nov 2011

Jan 29, 2019

Zwitterion

Jan 29, 2019

1,178 Posts

Quote from johnny2x4

:

sharing my two cents after getting help on SD from another user - I used the steps below to reflash the router (mine had been in use and connected online previously)
https://www.bayareatechpros.com/ac1900-to-ac68u/

those steps are almost perfect, except that when running the code for fixing the mtd5 partition (after steps 1-24), putty will hang on "./mtd-erase -d asus" so you need to go to the router UI and update to a newer version [softpedia.com] (linked below, from another SD thread), and then re-run the remaining (or all, it's just redundant) code for fixing MTD5 partition

Couple other tips:

on step 15 remember to rename it to new_cfe.bin after downloading it since no error feedback will be provided if you don't and the following steps won't work otherwise (you'll remain on the t-mobile firmware)
to echo some users above, using chrome incognito mode helps a ton both for finding and seeing updates to the router webUI and recovery pages, since sometimes chrome caches stuff and it won't update on chrome.
if you complete all the steps successfully, but you plug in the router to your network and there is no internet, your cable/fiber modem may coincidentally be on the same default IP as the router is. To fix this, go to the router webUI and on the status page you'll see an error stating an IP conflict which you can click so the router will change itself to a different IP

Yes, in order to run the mtd erase commands, you must be on 384.xxxx or higher - I believe this was noted in the wiki.

johnny2x4

Jan 29, 2019

1,549 Posts

Joined Nov 2012

Jan 29, 2019

Jan 29, 2019

1,549 Posts

If I had to write a full up-to-date guide, it would be this:
(Up to date as of 5/2/19 with suggestions in this and later threads)
How to flash TM-AC1900 to RT-AC68U:

Install WinSCP, Putty, and a file archiver (click this link to download all 3 [ninite.com]). Install the Asus Restore Utility [asus.com], mirror [filedropper.com].
Connect your computer to the *yellow* port on the router by way of an Ethernet (LAN) cable
Check if SSH can be enabled - if so, enable it and jump to step #15
Go to Administration > System > Enable SSH > Yes > Apply
Ezlink: http://192.168.29.1/Advanced_System_Content.asp
Create a folder on your desktop, name it "router".
Download this file [mega.nz] and extract it to the newly made router folder. It contains a firmware to downgrade to, a firmware to upgrade to, and mtd-write.
Download firmware version 3.0.0.4.384.20308 from here [softpedia.com] and unzip the file
Disconnect the cellspot router from the internet if you haven't already
Set static IP for PC.
start > run > ncpa.cpl > double click Ethernet > properties > IPV4 >
IP: 192.168.29.5
Subnet: Default (255.255.255.0)
Gateway: 192.168.29.1
Place router into Recovery/Restore mode
a. Hold reset button 10 seconds
b. Power off router (keep holding reset)
c. Wait 10 seconds, keep holding reset
d. Power on router holding reset for 10 more seconds
Go to 192.168.29.1 in a web browser - you should see ASUSTek CFE miniWeb Server
If Mini-CFE webpage won't load, try Chrome Incognito mode, else use Asus Restore Utility (linked in #1)
If having trouble with this step perform NVRAM Reset (see #24) and try #9 again
Flash TM-AC1900_3.0.0.4_376_1703-g0ffdbba.trx from the "router" folder you created (hit the choose button, select the file, hit upload)
Wait for reboot at least 5 mins – WiFi lights on router will turn on when boot is complete
Log in to router (admin:password)
Go to Administration > System > Enable SSH > Yes > Apply
Ezlink: http://192.168.29.1/Advanced_System_Content.asp
Open Putty and WinSCP and connect them to 192.168.29.1 using a admin:admin or admin:password
Tip: In WinSCP select SCP as file protocol, in Putty SSH
In Putty type:
Code:
```
cat /dev/mtd0 > original_cfe.bin
```
In WinSCP refresh the window on the right side and note that original_cfe.bin is present
Copy original_cfe.bin to a local drive
Download the new .bin
a. Upload original_cfe.bin to http://cfeditor.pipeline.sh/
b. Select 1.0.2.0 US AiMesh as Source CFE for Asus/Merlin builds, (1.0.2.5 recommended for DD-WRT or Tomato)
c. Click Download
Rename the new .bin file to "new_cfe.bin"
Through WinSCP, Upload new_cfe.bin & mtd-write & FW_RT_AC68U_30043763626.trx to router

In Putty type:

Code:

chmod u+x mtd-write
./mtd-write new_cfe.bin boot
mtd-write2 FW_RT_AC68U_30043763626.trx linux

Wait until the CRC OK message comes up
Perform NVRAM Reset
a. Power off router
b. Wait 10 seconds
c. Press and hold WPS button
d. Power up the router and continue to hold WPS button for 15-20 seconds until power LED starts blinking very quickly.
e. wait 5 minutes
Reset PC IP back to default
Log in to router using 192.168.1.1 and the router is now an RT-AC68U with 64MB jffs
username:/password is now: admin:admin
If router isn't showing RT-AC68U, try Chrome Incognito Mode
Enable SSH (see #14) Ezlink: http://192.168.1.1/Advanced_System_Content.asp
Reconnect Putty (see #15)

In Putty, execute the code for fixing MTD5 partition.

Code:

cat /dev/mtd5 > /jffs/mtd5_backup.bin
mkdir /tmp/asus_jffs
mount -t jffs2 /dev/mtdblock5 /tmp/asus_jffs
rm -rf /tmp/asus_jffs/*
sync && umount /tmp/asus_jffs
ln -s /sbin/rc mtd-erase

In the router page, go to Administration > Firmware and upload RT-AC68U_3.0.0.4_384_20308-gead790e.trx
This is the file you downloaded in step #6
Perform NVRAM Reset (see #24)
Enable SSH (see #14) Ezlink: http://192.168.1.1/Advanced_System_Content.asp
When going back into the router at this point, it may prompt you to update the username/password, not allowing you to go directly to enable ssh
Make sure you don't forget what you change the username/password to
Reconnect Putty (see #15)

In Putty, execute the code for fixing MTD5 partition.

Code:

mkdir /tmp/asus_jffs
mount -t jffs2 /dev/mtdblock5 /tmp/asus_jffs
rm -rf /tmp/asus_jffs/*
sync && umount /tmp/asus_jffs
ln -s /sbin/rc mtd-erase
./mtd-erase -d asus
rm -rf /jffs/.sys/RT-AC68U
nvram unset fw_check && nvram commit && reboot

You now can (and should) flash an updated firmware, such as Asus, Merlin, Advanced Tomato, Tomato, and DD-WRT firmwares.
To flash newer Asus firmwares at this point, go to the router page, go to Administration > Firmware and upload the latest firmware from this page [asus.com].
At this point, for security purposes I'd recommend to either disable SSH or change it to 'LAN only". Also, definitely change both the default login id and password.

Additional Notes:

Yes, step 34 is partially redundant, but this is the way I did it twice and it caused no issues.
If you complete all the steps successfully, but you plug in the router to your network and there is no internet, your cable/fiber modem may coincidentally be on the same default IP as the router is. To fix this, go to the router webUI and on the status page you'll see an error stating an IP conflict which you can click so the router will change itself to a different IP
if you want to set up AiMesh, follow these steps

Feel free to message me if you get stuck, I may not respond immediately but I will try to help

Last edited by johnny2x4 May 16, 2019 at 08:58 AM.

6

ST1NGY

Jan 29, 2019

1,570 Posts

Joined Oct 2009

Jan 29, 2019

Jan 29, 2019

1,570 Posts

Very good write-up and you filled-in some areas where people go astray. I'l point out one mistake. Delete step #23 entirely. Since you are already on 384.20308 you can modify step 29 to:

Code:

cat /dev/mtd5 > /jffs/mtd5_backup.bin
rm -rf /jffs/.sys/RT-AC68U
ln -s /sbin/rc mtd-erase
./mtd-erase -d asus
nvram unset fw_check && nvram commit && reboot

This eliminates some redundant and useless commands. And a minor point. There no is value in backing-up /dev/mtd5 if you don't copy it off the router. Leaving it in /jffs isn't a safe place.

Quote from johnny2x4

:

If I had to write a full up-to-date guide, it would be this:

How to flash AC1900 to AC68U:

Install WinSCP, Putty, and a file archiver (click this link to download all 3 [ninite.com]). Install the Asus Restore Utility [asus.com], mirror [filedropper.com].
Create a folder on your desktop, name it "router".
Download this file [mega.nz] and extract it to the newly made router folder. It contains a firmware to downgrade to, a firmware to upgrade to, and mtd-write.
Disconnect the cellspot router from the internet if you haven't already
Set static IP for PC.
start > run > ncpa.cpl > double click Ethernet > properties > IPV4 >
IP: 192.168.29.5
Subnet: Default (255.255.255.0)
Gateway: 192.168.29.1
Place router into Recovery/Restore mode
Hold reset button 10 seconds
Power off router (keep holding reset)
Wait 10 seconds, keep holding reset
Power on router holding reset for 10 more seconds
Go to 192.168.29.1 in a web browser
If Mini-CFE webpage won't load, try Chrome Incognito mode, else use Asus Restore Utility
If having trouble with this step perform NVRam Reset (see # 20) and try #6 again
Flash TM-AC1900_3.0.0.4_376_1703-g0ffdbba.trx from the "router" folder you created
Wait for reboot at least 5 mins – WiFi lights on router will turn on when boot is complete
Log in to router (admin:password)
Go to Administration > System > Enable SSH > Yes > Apply
Ezlink: http://192.168.29.1/Advanced_System_Content.asp
Open Putty and WinSCP and connect them to 192.168.29.1 using a admin:admin or admin:password
Tip: In WinSCP select SCP as file protocol, in Putty SSH
In Putty type:
Code:
```
cat /dev/mtd0 > original_cfe.bin
```
In WinSCP refresh the window on the right side and note that original_cfe.bin is present
Copy original_cfe.bin to a local drive
Download the new .bin
a. Upload original_cfe.bin to https://cfeditor.pipeline.sh/
b. Select 1.0.2.0 US AiMesh as Source CFE for Asus/Merlin builds, (1.0.2.5 recommended for DD-WRT or Tomato)
c. Click Download
Rename the new .bin file to "new_cfe.bin"
Through WinSCP, Upload new_cfe.bin & mtd-write & FW_RT_AC68U_30043763626.trx to router

In Putty type:

Code:

chmod u+x mtd-write
./mtd-write new_cfe.bin boot
mtd-write2 FW_RT_AC68U_30043763626.trx linux

Perform NVRAM Reset
a. Power off router
b. Wait 10 seconds
c. Press and hold WPS button
d. Power up the router and continue to hold WPS button for 15-20 seconds until power LED starts blinking very quickly.
e. wait 5 minutes
Reset PC IP back to default
Log in to router using 192.168.1.1 and the router is now an AC68U with 64MB jffs
username:/password is now: admin:admin
If router isn't showing AC68U, try Chrome Incognito Mode

In Putty, execute the code for fixing MTD5 partition.

Code:

cat /dev/mtd5 > /jffs/mtd5_backup.bin
mkdir /tmp/asus_jffs
mount -t jffs2 /dev/mtdblock5 /tmp/asus_jffs
rm -rf /tmp/asus_jffs/*
sync && umount /tmp/asus_jffs
ln -s /sbin/rc mtd-erase

Download firmware version 3.0.0.4.384.20308 from here and unzip the file
In the router page, go to Administration > Firmware and upload RT-AC68U_3.0.0.4_384_20308-gead790e.trx
Perform NVRAM Reset (see #20)
Enable SSH (see #10) Ezlink: http://192.168.1.1/Advanced_System_Content.asp
Reconnect Putty (see #11)

In Putty, execute the code for fixing MTD5 partition.

Code:

cat /dev/mtd5 > /jffs/mtd5_backup.bin
mkdir /tmp/asus_jffs
mount -t jffs2 /dev/mtdblock5 /tmp/asus_jffs
rm -rf /tmp/asus_jffs/*
sync && umount /tmp/asus_jffs
ln -s /sbin/rc mtd-erase
./mtd-erase -d asus
rm -rf /jffs/.sys/RT-AC68U
nvram unset fw_check && nvram commit && reboot

You can now flash Asus [asus.com], Merlin, Advanced Tomato, Tomato, and DD-WRT firmwares

Additional Notes:

Yes, step 28 is partially redundant, but this is the way I did it and it caused no issues.
If you complete all the steps successfully, but you plug in the router to your network and there is no internet, your cable/fiber modem may coincidentally be on the same default IP as the router is. To fix this, go to the router webUI and on the status page you'll see an error stating an IP conflict which you can click so the router will change itself to a different IP

Last edited by ST1NGY January 29, 2019 at 03:46 PM.

1

johnny2x4

Jan 29, 2019

1,549 Posts

Joined Nov 2012

Jan 29, 2019

Jan 29, 2019

1,549 Posts

Quote from ST1NGY

:

Very good write-up and you filled-in some areas where people go astray. I'l point out one mistake. Delete step #23 entirely.

thanks for the feedback-
I was under the impression that some of those commands were needed prior to updating to 384? or is it okay to run them all after updating?

I put that in there pretty much as a just in case since it doesn't cause any issues.

Last edited by johnny2x4 January 29, 2019 at 03:35 PM.

User17347427

Jan 29, 2019

1,655 Posts

Joined Sep 2018

Jan 29, 2019

Jan 29, 2019

1,655 Posts

Haha!

BobbyFinstock

Jan 29, 2019

916 Posts

Joined Nov 2010

Jan 29, 2019

BobbyFinstock

Jan 29, 2019

916 Posts

edit: nvm previous question. i was stupid.

What if i already have the router i want to flash in ap mode and it has an ip address of 192.168.29.150?
do all the same steps still apply but where it says 192.168.29.1 i substitute 150 for 1?
I have another tmac1900 already as the main router and its address is 29.1 and I want to leave that alone for now.

Would I be better off with a factory reset on it before I start?

Last edited by BobbyFinstock January 29, 2019 at 05:28 PM.

User17347427

Jan 29, 2019

1,655 Posts

Joined Sep 2018

Jan 29, 2019

Jan 29, 2019

1,655 Posts

Quote from ST1NGY

:

Very good write-up and you filled-in some areas where people go astray. I'l point out one mistake. Delete step #23 entirely. Since you are already on 384.20308 you can modify step 29 to:Code:cat /dev/mtd5 > /jffs/mtd5_backup.bin
rm -rf /jffs/.sys/RT-AC68U
ln -s /sbin/rc mtd-erase
./mtd-erase -d asus
nvram unset fw_check && nvram commit && reboot This eliminates some redundant and useless commands. And a minor point. There no is value in backing-up /dev/mtd5 if you don't copy it off the router. Leaving it in /jffs isn't a safe place.

The only issue with this, (minus the elimination of the commands you mentioned) is if people mess up and go past 384.20308.. before doing the MTD (7 old commands) , is there router reverts back to a TM-AC1900.

Not only that, the firmware 384.20308 is rare to find. If that link gets taken down.. your 'new' way of doing it will no longer be valid.

Last edited by User17347427 January 29, 2019 at 04:18 PM.

ST1NGY

Jan 30, 2019

1,570 Posts

Joined Oct 2009

Jan 30, 2019

Jan 30, 2019

1,570 Posts

Quote from Hawbgobblin

:

The only issue with this, (minus the elimination of the commands you mentioned) is if people mess up and go past 384.20308.. before doing the MTD (7 old commands) , is there router reverts back to a TM-AC1900.

Not only that, the firmware 384.20308 is rare to find. If that link gets taken down.. your 'new' way of doing it will no longer be valid.

I agree. I was only commenting on the mentioned instructions which presumed that the user had already installed 384.20308 (for those unaware, 384.20308 was that last "safe" ASUS firmware that didn't require mtd5 cleanup).

Also for those unaware, the commands I deleted above are not necessary since they manipulate /dev/mtd5 (which isn't necessary to install 384.20308), then in step 29 /dev/mtd5 gets totally erased. So those step #23 commands added no value.

I'm not picking on johnny2x4 and he did do a good job and I thank him. The problem with a compilation from many sources is that many times the reason for the commands gets lost over time. A copying instructions from various sources often introduces this problem. I have no argument that correctly using johnny2x4's checklist will result in a good conversion. My only goal is to reduce the "rain dance" that often occurs ("I did this dance and sure enough - it rained". So for generations they believed the dance caused the rain). OK. that's hyperbole but you get the message.

Also, you're post reminds everyone that many times, things change. So a checklist may be perfect one day, and then becomes an albatross that causes unintended problems for those who stuble upon it later. These things need to be living documents and getting instructions in an SD thread is a very bad place to look. In a month all of this may be obsolete or dangerous. Best is to go to a known current source. I prefer this thread in Whirlpool.net [whirlpool.net.au]. You don't need to read it all unless you are technically curious. But it is the best place to go for current and vetted-accurate info.

Last edited by ST1NGY January 29, 2019 at 05:00 PM.

User17347427

Jan 30, 2019

1,655 Posts

Joined Sep 2018

Jan 30, 2019

Jan 30, 2019

1,655 Posts

Quote from ST1NGY

:

I agree. I was only commenting on the mentioned instructions which presumed that the user had already installed 384.20308 (for those unaware, 384.20308 was that last "safe" ASUS firmware that didn't require mtd5 cleanup).

I sure do like your way of doing it though Wink

johnny2x4

Jan 30, 2019

1,549 Posts

Joined Nov 2012

Jan 30, 2019