RT-AC66U - stuck on 380.65_2

[BSOD2600]

Long time merlin user and upgrades in the past have not been a problem. For some reason, unable to update to the latest 380.66_4. no errors displayed on the screen or in the system log after the update.

Ideas?

 

[octopus]

Try to remove any USB stick and reboot and try again.
If you are on very old FW you may use 378.55 first and then 380.66_4

 

[BSOD2600]

No usb devices connection.
router is already on 380.65_2... why would I want to downgrade to 378.55 to then upgrade??

 

[Blinkyz]

why would I want to downgrade to 378.55 to then

No , you dont need if you are already on 380.65
Simply reboot, flash

*378.55 is needed only if your are coming from something before 378.50.(the CFE bootloader need an upgrade for partition size)

 

[octopus]

No usb devices connection.
router is already on 380.65_2... why would I want to downgrade to 378.55 to then upgrade??

That wasn't what I said: "If you are on very old FW you may use 378.55 first and then 380.66_4" eg older than 378.55

 

[BSOD2600]

Since the post states I'm already on 380.65_2, whats the point of even mentioning the very old fw?

Anyways, since neither of those ideas apply, what else can be tried?

 

[Blinkyz]

what else can be tried?

This , and all steps are important.(reboot first and unhook usb drive or stick before )
https://www.asus.com/support/FAQ/1030652/

What is the version of your Ac66?( sticker behing the router)

*Note = RT-AC66U_B1 (use the RT-AC68U firmware)

 

[BSOD2600]

What is the version of your Ac66?( sticker behing the router)

HW Ver: A2

 

[BSOD2600]

Fixed.

Backup settings / JFFS
restore Factory Defaults
Upgrade to 380.66_4
Restore settings
-- lots of various settings were not correctly restored and needed to be reconfigured.
Restore JFFS.

 

[BSOD2600]

A month later, another release (RT-AC66U_380.67_0), and I'm having the same problem again.

How do I troubleshoot exactly why the updates are not getting correctly installed? I really dont want to have to reset for every update; thats ridiculous.

 

[RMerlin]

Do a factory default reset and manually reconfigure everything instead of reusing what appears to be a problematic config backup (since your upgrade worked fine after a factory default reset).

 

[BSOD2600]

Do a factory default reset and manually reconfigure everything instead of reusing what appears to be a problematic config backup

through debug logging, is there a way to identify which config setting(s) are causing the problem during an upgrade?

 

[RMerlin]

through debug logging, is there a way to identify which config setting(s) are causing the problem during an upgrade?

No.

 

[BSOD2600]

Darn. Ok tried the following this time. lets see if a normal upgrade will work with the next release...

nvram-save-r24a - nvram-save.sh
factory reset
upgrade to 380.67 (worked!)
factory reset
nvram-save-r24a - nvram-restore.sh

 

[BSOD2600]

Upgrade to 380.68 fails. arg!

noticed the following in the messages. possibly all caused by dying hardware?

Jul 31 17:00:14 kernel: NAND device: Manufacturer ID: 0x92, Chip ID: 0xf1 (Zentel NAND 128MiB 3,3V 8-bit)
Jul 31 17:00:14 kernel: Bad block table found at page 65408, version 0x01
Jul 31 17:00:14 kernel: Bad block table found at page 65344, version 0x01
Jul 31 17:00:14 kernel: nand_read_bbt: Bad block at 0x07fe0000

 

[RMerlin]

Upgrade to 380.68 fails. arg!

noticed the following in the messages. possibly all caused by dying hardware?

Jul 31 17:00:14 kernel: NAND device: Manufacturer ID: 0x92, Chip ID: 0xf1 (Zentel NAND 128MiB 3,3V 8-bit)
Jul 31 17:00:14 kernel: Bad block table found at page 65408, version 0x01
Jul 31 17:00:14 kernel: Bad block table found at page 65344, version 0x01
Jul 31 17:00:14 kernel: nand_read_bbt: Bad block at 0x07fe0000

badblocks are not unusual in NAND, that's why they use badblock tables so these can be skipped. I have a recent router here which has two of them.