RT-BE88U can't install merlin

[Jackson]

Hello. I have a brand new RT-BE88U (arrived today). Tried install merlin image RT-BE88U_3006_102.2_0_nand_squashfs.pkgtb.
Comes up saying "firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again".

I have tried:
* re-downloading the merlin image
* re-installing official firmware manually (latest version available as below, successful)
* factory reset, logging in to 192.168.50.1 through browser, answering the initial questions then straight to firmware upgrade.

Any ideas please?

RT-BE88U	Current Version : 3.0.0.6.102_37094-g9192b87_980-gbd310_BB0B

 

[Treadler]

Hello. I have a brand new RT-BE88U (arrived today). Tried install merlin image RT-BE88U_3006_102.2_0_nand_squashfs.pkgtb.
Comes up saying "firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again".

I have tried:
* re-downloading the merlin image
* re-installing official firmware manually (latest version available as below, successful)
* factory reset, logging in to 192.168.50.1 through browser, answering the initial questions then straight to firmware upgrade.

Any ideas please?

​

RT-BE88U	Current Version : 3.0.0.6.102_37094-g9192b87_980-gbd310_BB0B

The 37094 you have was released only a day or so ago.
Maybe it sees the (slightly) older Merlin firmware as something it won’t/can’t go back to?

 

[wrink]

So I recently turned my old AX58u into an AImesh node, since I bought the BT10 to be my main router.

As I tried to get the Ax58u onto the latest Asus-released router from usual merlin-for-main router - I had encountered the same problem. The root of the problem, found from an old thread here, was that Asus had changed the firmware size/codebase after Oct 2021 - which required me to load up the Oct 2021 FW from Asus first on the Ax58u, and only then I could switch to the latest Asus release for the Ax58u. Otherwise, I got the same message you were getting. The older Oct 2021 fw binary had a size of ~56 MB, while the latest one had size of ~106 MB - indicative of Asus' change.

 

[Squall Leonhart]

negative, the size is just because this model has a v2 which uses a different cpu,

the actual cause of your issue issue was that code signing changed between the release of the product and the latest versions of the firmware, the older firmware has no idea how to interpret the hashing schemes of the current firmwares so you need to first flash a firmware that is still signed in the former hash scheme but knows how to read the newer scheme.

 

[wrink]

negative, the size is just because this model has a v2 which uses a different cpu,

the actual cause of your issue issue was that code signing changed between the release of the product and the latest versions of the firmware, the older firmware has no idea how to interpret the hashing schemes of the current firmwares so you need to first flash a firmware that is still signed in the former hash scheme but knows how to read the newer scheme.

Understand the hashing difference, thanks.

However, given I have v1 of the AX58u - why/how did the release of the v2 (with different CPU) cause the change/double the binary size of the same v1 hardware, after Oct 2021 ?

 

[Squall Leonhart]

Understand the hashing difference, thanks.

However, given I have v1 of the AX58u - why/how did the release of the v2 (with different CPU) cause the change/double the binary size of the same v1 hardware, after Oct 2021 ?

it includes unique platform code specific to each model, it will only deploy the code specific to either one on the corresponding model.

 

[baba69]

Hello. I have a brand new RT-BE88U (arrived today). Tried install merlin image RT-BE88U_3006_102.2_0_nand_squashfs.pkgtb.
Comes up saying "firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again".

I have tried:
* re-downloading the merlin image
* re-installing official firmware manually (latest version available as below, successful)
* factory reset, logging in to 192.168.50.1 through browser, answering the initial questions then straight to firmware upgrade.

Any ideas please?

​

RT-BE88U	Current Version : 3.0.0.6.102_37094-g9192b87_980-gbd310_BB0B

I have the exact same issue, on the exact same router. I read a few other ways to install custom firmware on asus routers, but I'm not sure what to do to be honest.

RT-AC66U_B1: Unable to flash - Invalid Firmware Upload/Firmware upgrade unsuccessful

I purchased a new RT-AC66U B1 (AC1750 ARM w/ USB3) but every Fresh Tomato firmware I attempt to install fails. All attempts to flash have been done through the Administration panel > Firmware Upgrade. I see either: "Invalid Firmware Upload" right away or it pretends to flash with a progress...

www.linksysinfo.org

 

[nucce]

I had same problem but came around it by installing Merlin from rescue mode.

When it was up in rescue mode(that you reach by holding down reset and plugging in DC power) was to browse to 192.168.1.1 and upload the latest Merlin file, note that you must unplug all other cables than the cable that you have connected to the PC from the router while trying to reach this, took me like 2 hours of before I understod this.

 

[WTOram]

I was just looking at the changelog for the Merlin 3006.102.3 pre-beta test build for the GT-BE98PRO and I found this which might help:

3006.102.3 (xx-xxx-xxxx)
- NOTE: If flashing on top of Asus stock firmware 3006.102_37000
or greater, then you first need to enable downgrade
capabilities before flashing Asuswrt-Merlin on top
of it. Over SSH, run the following command:

nvram set DOWNGRADE_CHECK_PASS=1

After that, you can upload Asuswrt-Merlin through
the webui like any regular firmware upgrade.

This is only required when flashing Asuswrt-Merlin
for the first time.

Note: I have not tried this. For the time being I am happy on the stock 3.0.0.6.102_37094 firmware although I shall be looking to move to Merlin firmware at some point in the future.

Maybe @RMerlin can comment on this in the context of an inability to migrate from the the above firmware to Merlin firmware using the normal method on the RT-BE88U.

 

[RMerlin]

Firmware 102_37xxx has some major wireless-related changes, so downgrading is blocked to prevent issues caused by incompatible settings. Asuswrt-Merlin is not recognized as being newer, hence the block. That nvram allows to bypass the block, however you WILL have to do a factory default reset after doing so, since Asuswrt-Merlin 3006.102.2 still uses the older wireless format.

 

[baba69]

Firmware 102_37xxx has some major wireless-related changes, so downgrading is blocked to prevent issues caused by incompatible settings. Asuswrt-Merlin is not recognized as being newer, hence the block. That nvram allows to bypass the block, however you WILL have to do a factory default reset after doing so, since Asuswrt-Merlin 3006.102.2 still uses the older wireless format.

Is there going to be a newer version of Asuswrt-Merlin where the installation wouldn't require a downgrade? (so skipping the factory reset)

 

[WTOram]

I would imagine that when ASUS issue a GPL release newer than 3.0.0.6.102.37000 for a router or a (set thereof), then that will be picked up by a subsequent asuswrt-merlin release.

At that time, I would imagine that the need for the nvram firmware block bypass will dissappear - at least until ASUS introduce another block.

However, it must be born in mind that the current 3006.102.2 asuswrt-merlin releases are based on different GPL baselines so it may be that some routers get past this block before others. I guess it all depends upon the GPL releases from ASUS.

 

[RMerlin]

Is there going to be a newer version of Asuswrt-Merlin where the installation wouldn't require a downgrade? (so skipping the factory reset)

Yes, if Asus can ever provide the damned GPLs I have been waiting on for months now...

At that time, I would imagine that the need for the nvram firmware block bypass will dissappear - at least until ASUS introduce another block.

The block only requires the nvram bypass when first coming from stock to Asuswrt-Merlin. Subsequent Asuswrt-Merlin upgrade don't need the variable any longer.