[Recovered!]Upgrading to 384.6 killed my ac68u :(

[Grisu]

Finally, I got it recovered by upload a openwrt firmware by ASUS recovery tool, and waited for over 24 hours, then flashed merlin 384.6.
After merlin firmware booted, there's many log entries like "jffs2_scan_eraseblock(): magic bitmask xxx not found at xx: xxx instead".

Hands up for your patience - well done!

 

[Sylphia]

But how to fix these jffs error messages? Searched and tried "mtd-erase2 brcmnand", command took only ~1 second, but seems nothing happened, these message still there after a reboot.

 

[Grisu]

maybe you could download a proper cfe for your router, edit the 3 MACs and security code and upload it in case your cfe got currupted.
https://www.snbforums.com/threads/asus-routers-cfe-dumps-collection.17793/

 

[RMerlin]

maybe you could download a proper cfe for your router, edit the 3 MACs and security code and upload it in case your cfe got currupted.
https://www.snbforums.com/threads/asus-routers-cfe-dumps-collection.17793/

Don't. If the router boots, then the CFE is fine.

But how to fix these jffs error messages? Searched and tried "mtd-erase2 brcmnand", command took only ~1 second, but seems nothing happened, these message still there after a reboot.

Could just be a side-effect of the flashing procedures, especially if using different sizes of firmware. Try setting the option to reformat the JFFS partition under Administration ->System. Reboot the router after enabling the option. Wait 5 minutes, then reboot it a second time.

 

[Grisu]

Don't. If the router boots, then the CFE is fine.
Could just be a side-effect of the flashing procedures, especially if using different sizes of firmware. Try setting the option to reformat the JFFS partition under Administration ->System. Reboot the router after enabling the option. Wait 5 minutes, then reboot it a second time.

good point, thought she (?) has done that after trying such many things to get it up again.

Would it be a good option to try the transversion release 32 to 64MB like your RT-AC68U_3.0.0.4_376_3626-g9a8323e.trx ?

 

[Sylphia]

Don't. If the router boots, then the CFE is fine.



Could just be a side-effect of the flashing procedures, especially if using different sizes of firmware. Try setting the option to reformat the JFFS partition under Administration ->System. Reboot the router after enabling the option. Wait 5 minutes, then reboot it a second time.

Tried as soon as I found these messages, not worked, then I tried mtd-erase2, also nothing.

 

[HowIFix]

Update in this order, do a factory reset, reformat the JFFS partition (under Administration ->System) between each update and reboot the router:

1. v378.55
   
2. v380.70
   
3. v384.5 (CFE Update)
4. v384.6 (Last version)

Read this:
https://github.com/RMerl/asuswrt-merlin/wiki/Installation

Since Asuswrt-Merlin is mostly a variant of the original Asuswrt, it means that there is no special procedure to flash it. Just flash it the same way you would flash any regular Asus firmware. A few notes:

• Starting with Asus's 3.0.0.4.380_3000, 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.)
• The RT-AC68U and RT-AC56U need to be at least on firmware 378.55 (or the last 378.xxx version from Asus) before you can flash 380.xx, due to the partition size change.
• It's recommended to reboot the router before flashing it, to free up sufficient memory. Otherwise, there's a chance the router might reject the firmware, due to running too low of free RAM.
• If coming from a non-Asuswrt firmware, you will have to do a factory default reset.
• While it is generally not necessary to restore to factory defaults, it's not a bad idea, especially if there is a big jump in version number (e.g. from 112 to 178). No need to do the 30/30/30 dance as required by DD-WRT - just do a plain Factory Default reset, or turn the device on while keeping the WPS button pressed. (The procedure can be different from one model to another.)
• It is very hard to brick an Asus router. If something goes wrong during flashing, you can put your router in Recovery mode by powering it on while you keep Reset pressed. After your release it, the power LED will either blink or stay off (depending on the model). At that point, you can either access it through http://192.168.1.1 (make sure you first give your PC a static IP within the same range, e.g. 192.168.1.100), or through the Firmware Recovery Tool provided on Asus's support CD. You will then be able to flash a working firmware.
• If something looks weird, don't waste too much time: save your settings, reset to factory default, reconfigure the basics, and see if the issue is resolved. If not, you can always restore your saved settings and do some more advanced troubleshooting.
• It is not recommended to restore settings saved under a different firmware version. It might work, but there is no guarantee.

STEP #2: Flash Asuswrt-Merlin Firmware

Here is my method for the extra cautious and definitely for people with odd problems that others are not seeing.

Unplug any USB drive First!

01. You have to do a factory reset before flashing the firmware:

• Administration -> Restore/Save/Upload Setting -> Click in Initialize

02. After the factory reset, Perform a Complete Power Cycle:

1. Turn off router
2. Unplug power
3. Turn it back on for 5 second to drain any residual electric charge
4. Turn it back off
5. Plug back the power
6. Turn it on and let it boot normally

03. Download, Unzip and Flash through the Web GUI the Asuswrt-Merlin Firmware:

• v384.6 or Newer for RT-AC68U

04. After flash the firmware, Perform another Factory reset:

• Administration -> Restore/Save/Upload Setting -> Click in Initialize

05. After the factory reset, Perform a Complete Power Cycle:

1. Turn off router
2. Unplug power
3. Turn it back on for 5 second to drain any residual electric charge
4. Turn it back off
5. Plug back the power
6. Turn it on and let it boot normally

06. After the Power Cycle, log in to the Web GUI, press Ctrl+F5 to reload the cache.
07. [IMPORTANT] Format JFFS partition:

• Administration -> System -> Format JFFS partition at next boot -> YES -> Apply and Reboot
• (You have to Apply before Reboot the router)

08. Do not use backup.
09. Setup the router the way you want.
10. [OTHER] Download CCleaner to clear the entire Browser Cache. (EZPZ)

And let me state the obvious... always upgrade over a wired connection and never over wireless.

If do not allow downgrade to v378 you have follow these steps:

STEP #1: Flash Stock Firmware

Unplug any USB drive First!

01. Perform a Factory reset on the router with the WPS method:

• Turn off the router, press the WPS button without releasing it, then turn on the router, Wait about 20 seconds, then release the WPS button.

02. Download and Install Firmware Restoration and Device Discovery:

• Firmware Restoration v2.1.0.2 (2018/07/23)
• Device Discovery v1.4.8.2 (2018/07/23)

03. Download and Unzip on the desktop the Official Firmware:

• v3.0.0.4.384.21140 or Newer for RT-AC68U

04. Add a Static IP in the Computer:

• IP address: 192.168.1.5
• Subnet mask: 255.255.255.0

05. Turn off the router.
06. Connect the Router to the Computer via Ethernet Cable.
07. [OPTIONAL] Open command prompt (CMD) and write "ping -t 192.168.1.1" and press Enter.
08. Use Rescue mode in the Router:

• Press the Reset button without releasing it and Turn on the router about 10 seconds, then release the Reset button. (If the power is flashing-slow, the router is on rescue mode)

09. Open the program Firmware Restoration, click on Browse and found the Official Firmware.
10. After click on Upload.
11. Wait 5 minutes to assure flash integrity.
12. After in the Browser write "192.168.1.1".
13. If you can not log in to Web GUI, then reset NVRAM with WPS method:

• Turn off the router, press the WPS button without releasing it, then turn on the router, Wait about 20 seconds, then release the WPS button.

14. Remove the Static IP in the Computer.
15. Perform Factory default Initialize:

• Administration -> Restore/Save/Upload Setting -> Click in Initialize

16. After the factory reset, log in to the Web GUI, press Ctrl+F5 to reload the cache.
17. [OTHER] Download CCleaner to clear the entire Browser Cache. (EZPZ)

This method works for all the routers.

 

[Grisu]

and just in case somebody changed clkspeed before and so caused all the troubles check speeds first, you should get 800,666 or 1000,666
SSH: nvram get clkfreq
If higher you would need to change it in cfe with: nvram set asuscfeclkfreq=1000,666 && nvram set asuscfecommit=1 && nvram set clkfreq=1000,666 && nvram commit && reboot

 

[RMerlin]

Would it be a good option to try the transversion release 32 to 64MB like your RT-AC68U_3.0.0.4_376_3626-g9a8323e.trx ?

No, it won't change anything at this point. The user succeeded in going to a 64 MB firmware, so there is no need to flash back to a 32 MB one.

 

[loveleeyoungae]

Finally, I got it recovered by upload a openwrt firmware by ASUS recovery tool, and waited for over 24 hours, then flashed merlin 384.6.
After merlin firmware booted, there's many log entries like "jffs2_scan_eraseblock(): magic bitmask xxx not found at xx: xxx instead".

Hi, Sylphia, glad to see you made it successfully! Did you use the Luci webgui of OpenWRT 18.06.1 to change to Merlin, or you just used the Asus Restoration Tool? I'm still stuck on OpenWRT.

 

[Sylphia]

Hi, Sylphia, glad to see you made it successfully! Did you use the Luci webgui of OpenWRT 18.06.1 to change to Merlin, or you just used the Asus Restoration Tool? I'm still stuck on OpenWRT.

I used webui, as OpenWRT fully functional, there was no reason to use restoration tool.

 

[Sylphia]

dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c62568 00020000 "rootfs"
mtd4: 03ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"

ran nandtest on these devices
mtd0 mtd1 mtd2 all showed several "Bad block at xxx"
mdt3 no permission
mtd4 mtd5 passed test.

Is that mean physical bad nand?
Tried running flash_erase on mtd1 didn't fix any bad blocks.

 

[Deleted member 28123]

dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c62568 00020000 "rootfs"
mtd4: 03ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"

ran nandtest on these devices
mtd0 mtd1 mtd2 all showed several "Bad block at xxx"
mdt3 no permission
mtd4 mtd5 passed test.

Is that mean physical bad nand?
Tried running flash_erase on mtd1 didn't fix any bad blocks.

Yes, bad block at xx means that xxxxxxxx address on the nand is bad/corrupt/unusable and has been marked as such. If the bad block occurs in a critical address range used by the cfe or firmware then the only way to recover your router is by replacing the nand chip.

 

[Grisu]

dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c62568 00020000 "rootfs"
mtd4: 03ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"

ran nandtest on these devices
mtd0 mtd1 mtd2 all showed several "Bad block at xxx"
mdt3 no permission
mtd4 mtd5 passed test.

Is that mean physical bad nand?
Tried running flash_erase on mtd1 didn't fix any bad blocks.

How can you call this nandtest?
Tried this:
xxx@RT-AC68U:/tmp/home/root# nandtest /dev/mtd5
-sh: nandtest: not found

 

[Sylphia]

How can you call this nandtest?
Tried this:
xxx@RT-AC68U:/tmp/home/root# nandtest /dev/mtd5
-sh: nandtest: not found

I compiled mtd tools myself.

 

[loveleeyoungae]

I compiled mtd tools myself.

Oh, you're a dev? Thought you got back to Merlin successfully and would not do any more tests.
Can your tools run on DD-WRT/OpenWRT, and if possible may I ask for a copy? Until now, only DD-WRT/OpenWRT can run on my router. I'm still stuck here, so I'd like to know if there was something wrong of my router nand.

 

[Sylphia]

Oh, you're a dev? Thought you got back to Merlin successfully and would not do any more tests.
Can your tools run on DD-WRT/OpenWRT, and if possible may I ask for a copy? Until now, only DD-WRT/OpenWRT can run on my router. I'm still stuck here, so I'd like to know if there was something wrong of my router nand.

I think you should install mtd tools from OpenWRT's software repo.

 

[loveleeyoungae]

I think you should install mtd tools from OpenWRT's software repo.

Actually, OpenWRT was TOTALLY new to me, had some strange restrictions (?) and bugs (spit out random garbage files all over some main directories) , and I also didn't debug with internet cable plugged in so I did not know if OpenWRT would actually work. So I'm on DD-WRT currently. However, I'll try again with OpenWRT to re-check. Thanks.

 

[loveleeyoungae]

I think you should install mtd tools from OpenWRT's software repo.

Well, I decided to buy a Serial-to-USB TTL cable to try the serial flash. I just used the common method "flash -noheader" and... the router booted successfully! Things have been normal since.

What still confuses me though is "flash -noheader" was basically a tftp method, but why did it work while other tftp methods failed? (Actually, there was a difference: After the flash, when I let it stay for a day (yes, around 24 hours), the LAN light was blinking all that time).

Now another router of mine started to have the same issue just like this one . Their common things are 384.6 and handling 15+ clients on 2.4GHz and 2-3 clients on 5Ghz... Don't know if people usually test the firmwares with many clients like that. Actually with the bricked one, I flashed 384.6 on it and tested with some devices for few days without any issues. Things just went nightmare after I replaced the old N66W with it.