RT-AX86U irrecoverably bricked after update?

[keastes]

picked up a RT-AX86U after the good old RT-AC66R started going terminal (loosing all the physical links). after updateing via rescue(couldn't even get it to load the official via webUI), its completely dead, no lights, no eth link to enter rescue or CPE. checked the power brick with a multimeter, and its working, looking to do a serial flash in the morning after the adapter arrives. what are the odds its recoverable that way?

edit: correction I'm an idiot, I think i flashed the RT-AC86U image.... question still stands, however.

 

[alex1236hk]

ASUS device is very hard to brick, the GUI itself won't let you go through if you selected a firmware its not for your router.
no lights at all? Even power lights?
If the power lights still on, use rescue mode to restore the firmware to bring it back.
[Wireless Router] How to use Rescue Mode (Firmware Restoration)? | Official Support | ASUS Global

Otherwise, return it as DOA if it still within the return period.

 

[keastes]

ASUS device is very hard to brick.
no lights at all? Even power lights?
If the power lights still on, use rescue mode to restore the firmware to bring it back.
[Wireless Router] How to use Rescue Mode (Firmware Restoration)? | Official Support | ASUS Global

Otherwise, return it as DOA if it still within the return period.

its completely dead, no lights, no eth link to enter rescue or CPE.

yeah, no dice there, thank you though

 

[alex1236hk]

yeah, no dice there, thank you though

Return it or RMA it then.

 

[kernol]

Can't fathom how you managed to upgrade wrong model firmware - unless of course you did not use the webui and forced the wrong one through command line? [which is never a good idea].

 

[keastes]

Can't fathom how you managed to upgrade wrong model firmware - unless of course you did not use the webui and forced the wrong one through command line? [which is never a good idea].

forced via rescue mode...

 

[RMerlin]

forced via rescue mode...

If you overwrote the bootloader by force uploading an invalid image and you can no longer enter recovery mode, then there's nothing you can do.

 

[keastes]

If you overwrote the bootloader by force uploading an invalid image and you can no longer enter recovery mode, then there's nothing you can do.

at least not without a bus pirate, a 48-TSOP clip, and more patience than i have at the moment.

 

[jsbeddow]

at least not without a bus pirate, a 48-TSOP clip, and more patience than i have at the moment.

Not to be critical, as you clearly have some advanced knowledge, but why did you start with the most "brute force" method that the bypasses safety checks that are built-in to the GUI firmware upgrade method.

 

[keastes]

Not to be critical,

totally deserve it, so no worries mate

as you clearly have some advanced knowledge, but why did you start with the most "brute force" method that the bypasses safety checks that are built-in to the GUI firmware upgrade method.

first actual weekend since christmas rush (people like their stores stocked, and us truck drivers get a chunk of it), and the RT-AC66U it was replaceing was terminal, dropping links to everything randomly. so much pressure to get this done nao!111eleven. that and i had the unconscious assumption that newer models would be above older in the download list, forgetting alphabetical sort is the default.

 

[L&LD]

Nothing makes you waste time than doing it fast.

Using the GUI method to update the firmware is always highly recommended.

 

[OzarkEdge]

Nothing makes you waste time than doing it fast.

Too funny!

OE

 

[L&LD]

Yet so true!

 

[RMerlin]

at least not without a bus pirate, a 48-TSOP clip, and more patience than i have at the moment.

The bootloader is encrypted. That might make it difficult for you to obtain a usable copy to replace yours (I don't know how the encryption key is handled).

 

[keastes]

The bootloader is encrypted. That might make it difficult for you to obtain a usable copy to replace yours (I don't know how the encryption key is handled).

big sticking point is if its per model, or per device. per model? dump another+extract from another of the same model. per device? that will probably be a deal breaker.

anyway that will be a fun hardware project at some point, seeing as i've already sourced and implemented a working replacement.