What's new

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

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Sylphia

Regular Contributor
Upgrade as usual, but after the router have rebooted, it entered boot loop.
Then I boot it into rescue mode, upload the firmware, but it entered rescue mode boot loop (ttl 100), and the mini web page cannot be opened.
A 30-30-30 seems brought the router out of boot loop, entered rescue mode(slow blinking power led), but the web page remains down (connetion reset), then I tried to upload firmware by tftp, reboot the router after a full night, but it dosen't work, still rescue mode boot loop.

Any actions that I can do to bring it back?

P.S. I've got a ac86u as replacement, but sadly the iptable's geoip module didn't work.
 
30-30-30 resets do NOTHING on Asus routers. Try a proper reset by powering on the router while holding the WPS button till the power led flashes if possible.
 
Make sure you are trying to flash the correct model. Flashing over tftp/webui recovery should work, unless something is defective.
 
Make sure you are trying to flash the correct model. Flashing over tftp/webui recovery should work, unless something is defective.

I'm sure it's the right firmware for ac68u.
Current status is,
- normal boot: go into recovery mode (slow blinking power led), boot loop ~30 seconds, webui sometimes works but can't do anything because of boot loop;
- power off, long press reset button then power on: seems booted recovery mode (slow blinking power led), but webui didn't work, timeout or connection reset.
- power off, long press wps button then power on: same as normal boot.
In all situation tftp seems working, but as soon as I start uploading firmware, ping to router goes timeout.
Asus firmware recovery tool shows recovery failed after uploading.

I'll get a TTL cable later to see if there's anything I can do.
 
Tried TTL cable, no luck.
With TTL cable connected, power on the router results in all lan led lighted, dimmed power led, and nothing from com port.
 
Some TTL adapters are quirky, connect it after you power on the router.
 
I also had some issues with 384.6, so tried downgrading to 384.5 but realized that it seemed it might not be able to downgrade via webui as Merlin said in another thread.
Tried using the CFE miniweb and it did not work, only the power LED was on and nothing else. For the last week, I have tried several methods but have not succeed. I could use CFE Miniweb, Firmware Restoration, tftp and they all output successful messages "Transfered successfully", "Upload completed" etc... but the router power LED just kept staying On. This is really strange...
 
I also had some issues with 384.6, so tried downgrading to 384.5 but realized that it seemed it might not be able to downgrade via webui as Merlin said in another thread.
Tried using the CFE miniweb and it did not work, only the power LED was on and nothing else. For the last week, I have tried several methods but have not succeed. I could use CFE Miniweb, Firmware Restoration, tftp and they all output successful messages "Transfered successfully", "Upload completed" etc... but the router power LED just kept staying On. This is really strange...

Since your cfe miniweb still working, try reset nvram first, then flash a official firmware.
 
Since your cfe miniweb still working, try reset nvram first, then flash a official firmware.
When I said "several methods" I also implied that I tried several types of firmwares (Merlin, John, Official). The only thing left I will try is the "patience" method. Just flashed the very old 2014-era firmware 374.5656 using the Firmware Restoration tool, I will wait for a day as some people suggested.
 
you need a firmware smaller 32MB to be loaded via MiniWeb.
I tried some <32MB firmwares as well. As I said, the CFE Miniweb and other methods always "worked" (gave out successful messages). But they all just stayed at that level. Nothing else except the power LED is always lit. I even waited for around 4-5 hours, but someone said he waited at least 10 hours, that's why my next tries I will try to wait at least 12h-24h.
Btw, I can't use putty or scp, even when the router is in rescue mode. Is that normal?
 
Last edited:
Beside digging a lot of threads last week, yesterday I found someone mentioned that the only firmware he installed successfully for the debugging was OpenWrt (I have not thought of trying that one as people usually never mentioned about it due to its wireless support). It sounded reasonable as OpenWrt size is small (6-7 MB). So, after waited some long hours and the patience method I did yesterday did not work, I have just tried OpenWRT, and... well I can putty ssh into the router now. So tempted, wondering what I should do next... However, I am going on a vacation right now (yeah, just tried the flashing right before packing and going :), so I will get back in 3 days.
 
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".
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top