RT-N66U very old version upgrade path

[innocuous]

Hi all, first time posting.

I hopped on the Merlin builds long ago when I bought my RT-N66U and kept up for awhile. Then I fell off the bandwagon and I'm now very very behind (376.45/almost 3.5 years ago).

I was reading the changelog and install documentation and came across the warnings about the change in firmware format:

Starting with Asus's 3.0.0.4.380_3000 and upward, a new firmware format is used. To flash Asuswrt-Merlin on one of these newer firmwares, you will need 380.61 or newer. Likewise, downgrading to an older version is not supported (try firmware recovery mode if you really need to downgrade)

After reading that I wasn't 100% sure what the upgrade path looked like for coming from a very old version. I know I need to do the factory default reset but what else is required when coming up from such an old version (if anything)? It seems like I need to stop off at 380.61 on my way to latest? It's entirely possible I'm just over thinking this.

Anyway, just looking for some clarity and if I missed some documentation somewhere about this I apologize. Just point me there.

Thanks in advance for the thoughts and a special thanks to RMerlin for the years of work. I really appreciate it.

 

[MoInSTL]

Hi all, first time posting.

I hopped on the Merlin builds long ago when I bought my RT-N66U and kept up for awhile. Then I fell off the bandwagon and I'm now very very behind (376.45/almost 3.5 years ago).

I was reading the changelog and install documentation and came across the warnings about the change in firmware format:


After reading that I wasn't 100% sure what the upgrade path looked like for coming from a very old version. I know I need to do the factory default reset but what else is required when coming up from such an old version (if anything)? It seems like I need to stop off at 380.61 on my way to latest? It's entirely possible I'm just over thinking this.

Anyway, just looking for some clarity and if I missed some documentation somewhere about this I apologize. Just point me there.

Thanks in advance for the thoughts and a special thanks to RMerlin for the years of work. I really appreciate it.

Hopefully an answer is posted here as I am in a similar boat with 374. 35

 

[nospamboz]

Anyway, just looking for some clarity and if I missed some documentation somewhere about this I apologize. Just point me there.

I'm in a somewhat similar position to you, though my RT-N66W is "brand new", in that I bought it in July 2017. I immediately installed the (then) latest asuswrt-merlin, version 380-something, a bit ahead of where you are, but it turns out you're in the better position now compared to me.

RMerlin says in his latest missive that he's ending support for the RT-N66U (and color variants) in a few months, mostly due to limited support from Asus themselves.

https://www.snbforums.com/threads/end-of-year-2017-development-update.42965/

He refers to "John's fork" for our "old" models, which can be found here.

https://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-v29e2.18914/

Though it's an "earlier" version, it's kept reasonably up-to-date with security fixes and the like, which is the important thing. I'm familiar with the "LTS" designation, for "Long Term Servicing", common on Ubuntu Linux installations (like the ones I have at home).

Fortunately for you (but not me), it looks like you can jump directly from your firmware into the LTS fork, just flashing it as a normal update. According to the details, it looks like I may have to take an extra step or two with the "Firmware Restoration Tool", if I'm reading it right. Not a big deal, just more work for me. I'll get around to it soon enough.

Be sure to let all of us know how the LTS fork works for you.

 

[ColinTaylor]

I'm familiar with the "LTS" designation, for "Long Term Servicing", common on Ubuntu Linux installations (like the ones I have at home).

Actually, to be pedantic, LTS is usually an acronym for Long Term Support (as used in product lifecycle management). I don't know why @john9527 calls it Long Term Service, but it's his firmware and he can call it what he wants.

 

[ColinTaylor]

After reading that I wasn't 100% sure what the upgrade path looked like for coming from a very old version. I know I need to do the factory default reset but what else is required when coming up from such an old version (if anything)? It seems like I need to stop off at 380.61 on my way to latest? It's entirely possible I'm just over thinking this.

As I understand it, that message is saying that if your router is currently on stock firmware 3.0.0.4.380_3000 or higher you cannot load Merlin versions older than 380.61. So it's a limitation on going backwards. Loading a firmware that is newer than the one you have shouldn't be a problem.

 

[nospamboz]

(Sorry about the LTS error. All those TLAs run together after a while.)

Managed to "downgrade" my 380.x N66W to the 374.43 LTS fork. Took a while to find the Asus firmware restorer for my Mac, on the Mac App Store of all places. Saved/restored my settings and jffs using the built-in "Administration > Restore / Save / Upload Setting" tab, in both the old and new firmware. Works just like before, only slight cosmetic differences as far as I can see. Glad to be on "long term" now, especially since the unit is really only six months old.

 

[ColinTaylor]

Saved/restored my settings and jffs using the built-in "Administration > Restore / Save / Upload Setting" tab, in both the old and new firmware.

Ouch! Wrong. See the installation notes.

For supported routers currently running ASUS firmware 380.3000 or above, or Merlin 380.60 or above, you cannot load this fork using the built in firmware update web interface. You must use the ASUS Firmware Restoration Tool from the ASUS support website to install this fork firmware. You must always perform a factory default reset following the firmware update when moving from ASUS OEM or Merlin firmware above level 374 regardless if you updated via the web interface or Restoration Tool.

This means that after loading the LTS fork you should perform a factory reset followed by a manual reconfigure. Restoring a "Save settings" file negates the effect of the factory reset.

You should perform a factory reset followed by a manual reconfigure now. If you really don't want to manually reconfigure you can use John's NVRAM utility to migrate your settings in a "clean" way.