[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[john9527]

longer for the hub to reboot

What hub?

 

[InkyRag]

What hub?

Corrected. I meant the router takes a long time to reboot.

 

[john9527]

@InkyRag - I need some help since I can't recreate it. Can you capture a syslog (upload to a file sharing site and post a link - or PM me the link)?

 

[roundaway]

@roundaway @InkyRag @KGB7

Do any of you have an IPTV profile set?

I do not.

Replicated the issue this morning.
- Flash 19E1 on Win10 machine and router says to manually reboot. It doesn't come back and can't reset or use restoration tool
- Go to Linux machine to restore using USB to Serial Cable (Prologic Chip in cable doesn't support Win10)
- Come back to Win 10 and connect to default router set up. GUI says 19E1 is loaded
- Flash backup 18E3 configuration and router locks up
- Back to Linux machine to restore
- New - After restore, try to flash 18E3 firmaware from Linux machine and GUI says it's not compatable
- New - Come back to Win 10 and router enters boot loop on power up. Am able to reset and get blinking Power light
- New - Using restoration utility flash 18E3. GUI enters default configuration and I reflash 18E3 backup configuration
- Good to go

Standard home setup, no USB devices connected. Hope that helps, and again, thanks for your help.

 

[john9527]

I'm stumped...I did 10 firmware updates in a row last night, switching between 18E3 and 19E1. All completed successfully, with no manual reboot required.

Flash backup 18E3 configuration and router locks up

Is the backup via the gui and when was it taken?

- New - After restore, try to flash 18E3 firmaware from Linux machine and GUI says it's not compatable

What is the exact error message?

Have you ever had any of the firmware with the lockout (380.3xxx ASUS or 380.61 Merlin or above on the router?)

 

[roundaway]

Is the backup via the gui and when was it taken? The backup configuration was done just before flashing 19E1

What is the exact error message? Normally, a bar with percentages comes up when flashing. That didn't happen. Believe the message was Firmware Incompatible?

Have you ever had any of the firmware with the lockout (380.3xxx ASUS or 380.61 Merlin or above on the router?) Never

@dirtyclyde - you running a modified CFE?

 

[john9527]

@roundaway - I'm beginning to think you may have something corrupted in NVRAM.

Can you try the following.....
on V18E3 take a fresh configuration backup
while still on V18E3 do a factory reset
then try and load V19E1

If that is successful, then try and restore the config. V19 adds some new NVRAM variables, which are automatically added on boot if they are not there. If there is some corruption, I'm speculating that this process is making the corruption worse, resulting in the problems.

 

[roundaway]

yes 1.0.2.1 and 1.0.2.7 , I don't back up Firmware now! As I only use basic AP on 56u's and basic 68u on my charter ISP.. I have loaded 61 and 62 on all three, reloaded CFE and back to johns, will never load any other firmware on these 3 routers anymore, just Johns and or HGG's I have 3 more 56u's I play around with two 1.0.2.7 mod and one 1.0.2.7us the one 1.0.2.7us I tried 61 & 62 on find them so so.........

I returned the AC3200 and AC3100 and the other high price piece of CRAP..... with 60meg service not worth the $$$$$$

I've loaded CFE 1.0.2.8 and 1.0.2.9 bys me nothing so reloaded them back to 1.0.2.7

Can you PM me the instructions you used to update the CFE?

 

[john9527]

An FYI....I just updated the release info for V19E1 to include the following info concerning one of the fixes......

• Fix scheduled disk scans could run on the wrong drive
  IMPORTANT: If you have disk scans scheduled, you need to reapply the schedules in the Disk Utility or they may not work as expected.

 

[roundaway]

@roundaway - I'm beginning to think you may have something corrupted in NVRAM.

Can you try the following.....
on V18E3 take a fresh configuration backup
while still on V18E3 do a factory reset
then try and load V19E1

If that is successful, then try and restore the config. V19 adds some new NVRAM variables, which are automatically added on boot if they are not there. If there is some corruption, I'm speculating that this process is making the corruption worse, resulting in the problems.

- Fresh configuration backup, select factory defaults from GUI, flash 19E1
- Router rebooted to CFE miniWeb server. Selected reboot
- Again came up in miniWeb Server with router power button flashing
- Used firmware restoration to reload 19E1
- Router rebooted to a flashing power light
- USB to Serial restore by nvram erase
- From Linux machine and Chrome browser flashed 18V3. No status bar on progress. Chrome said software file may be invalid or corrupt
- Router rebooted and it worked
- Logged in with default information and reflashed backup configuration. Everything good.

Really weird. Sounds like this router may be going down hill since no one else is having a similar problem. CFE v1.0.1.9

 

[john9527]

Really weird. Sounds like this router may be going down hill since no one else is having a similar problem. CFE v1.0.1.9

Last thing to try....in the download directory for the fork, there is an ASUS folder with OEM code that will upgrade the CFE (I saw your other post about a CFE upgrade).

 

[Markmaster]

Hi. I was on 17E(pisode) for a time and trying to update to 19E1. I get a bad experience. I did a "clean install" every time, so I reset my router to the factory defaults, after that I upgrade to 19E1 and there were none. After update complete and factory reset performed router didn't get up a Wi-Fi connection. Simple Reset button do nothing. So I did 30-30-30 reset and trying again, trying to re-download firmware file - useless. All time one thing - no Wi-Fi connection. LED for Wi-Fi was OFF too. Now I am up(down)grade to 18E3 and seems to be all good here, I restore with Utility and can write this message. So, please, take a look around your 19E1 and further to figure out what is happening there. I am on AC-68U btw.
P.S. What is the "new version is out" channel for the updates? Any kind of email newsletter or IFTTT channel for this?

 

[john9527]

Just a reminder to all.....I cannot recreate any update failure on V19. If you have a problem, please collect a syslog or there is nothing I can do.

Also, please include your CFE bootloader level and NVRAM usage from the Tools>Sysinfo page.

 

[Pat57]

John,

Thanks for the great work on the fork!

I am having the same issue as others with 19E1 failing to boot after upgrade (same with the two betas after 18E3). When flashing, the progress bar finishes and the message to reboot manually comes up.

On a RT-N66R, I did the reset and entered the setup data again manually (simple media bridge). That fixed the router and it takes 19E1 update and boots fine.

On a RT-AC68R,

• Try 1 - Reset the router and 19E1 came up, reloaded 18E3 settings, Router would not boot without another reset.
• Try 2 - Reset the router and 19E1 came up, started loading settings manually, when router rebooted, it required reset.

When it does not boot right, the lights flash on and off, LAN port will not provide network address, no WLAN.

So I am back on 18E3 with the RT-AC68R. CFE is 1.0.2.0, IPv6 enabled, Router address set to 192.168.0.1, NTFS HDD attached to USB NVRAM usage 50667 / 65536 bytes (77% utilized)

One thing I thought of that I have not been able to test is that I have spaces in the SSID names and the names in the DHCP reservation list. This might cause issues when the fields are parsed.

 

[john9527]

I'm still at a loss as to explain any update problems (I've now done an additional set of firmware upgrades switching between 18E3 and 19E1, changing various setups such as the router ip address and enabled options, without any problems). So this change is purely speculative.

LATEST RELEASE: Update-19E2
10-September-2016
Merlin fork 374.43_2-19E2j9527
Download http://bit.ly/1YdgUcP
============================

Update-19E2 Highlights

• Disable some configuration changes not required by the currently supported IPTV profiles - these would be applied even if you were not using IPTV

SHA256

a4ba700960722e120cff45e8086f50642fed75a1da5ee5303204759e54b97dfd  RT-AC68U_3.0.0.4_374.43_2-19E2j9527.trx
d560f52cc7790aee2c6b844330c432c7280bdb7968042a2b4630b372c90dd04f  RT-AC56U_3.0.0.4_374.43_2-19E2j9527.trx
fe06fa82ddcf8e47ef2c8be85548fe215cfc3729129017f61bd827af47691ba7  RT-N16_3.0.0.4_374.43_2-19E2j9527.trx
1ab396ca7a1e1b8c2ca2263b62738907d06c6ae7fc125895c743e9e936ce6706  RT-AC66U_3.0.0.4_374.43_2-19E2j9527.trx
8d7cc0a5f0d125ea98945958b8267a46cd38fe9989e40493abe2200529b19574  RT-N66U_3.0.0.4_374.43_2-19E2j9527.trx

 

[jrmwvu04]

John - you posted 19E2 while I was getting myself ready to upgrade. Any preference on whether I should try 19E1 first? I have the rev A1 AC68W in signature.

edit: I'm on 19B4 currently

 

[john9527]

John - you posted 19E2 while I was getting myself ready to upgrade. Any preference on whether I should try 19E1 first? I have the rev A1 AC68W in signature.

edit: I'm on 19B4 currently

I suspect that if you are already on the V19 beta you won't have a problem with either. If you would, try the 19E2 so we will hopefully have a datapoint of a successful load.

 

[roundaway]

@john9527

Was able to grab the RT-AC-56U CFE v1.0.2.9 and edited the settings. Was able to use mtd-write. Funny thing. The nvram get bl_version is still 1.0.1.9 but the 18E3 "Tools", "Sysinfo" shows CFE 1.0.2.9

 

[john9527]

@john9527

Was able to grab the RT-AC-56U CFE v1.0.2.9 and edited the settings. Was able to use mtd-write. Funny thing. The nvram get bl_version is still 1.0.1.9 but the 18E3 "Tools", "Sysinfo" shows CFE 1.0.2.9

You need to do a factory reset to update the nvram....the tools page makes a call directly to the CFE.

EDIT: BTW....a saved config with the previous bootloader will now be invalid. You should reconfigure from scratch after a factory reset.

 

[jrmwvu04]

I loaded 19E2 directly over 19B4, and toggled power switch for a reboot. Worked fine. Wiped the nvram and toggled power again just to see what happened there, all normal after the fresh boot. Reconfigured, good to go on all fronts.

edit: my CFE is customized, if that makes any difference. I dumped the 1.0.2.5 that was factory installed, edited a few values, and replaced it.