Need help to unbrick Boox Max Lumi 1

[kekesed97]

Hi Renate,
I just flashed the recovery image you pm'd me through fastboot, but it didn't stick and always reverted to stock.

[Renate]

Booting into system will often overwrite recovery.
If you went directly to recovery after flashing it something different should have happened.
That is, unless it panicked and rebooted to the system.

[kekesed97]

I rebooted by executing fastboot reboot recovery and it booted into system.
I found that holding home button while I execute fastboot reboot does enter recovery, so I used that entry point.

Copied update.zip to a USB2.0 flash drive and connecting them using USBC->USB2 otg, ran the commands, and recovery returned "All done, update binary returned 256. Update failed, NOT rebooting". Tried using vanilla decrypted update.zip and checks removed update.zip, same result. Tried 2 different USB 2.0 flash drive, same result. Tried 2 different USBC -> USB2 dongle (one is a hub and the other isn't), same result.

Oh I should mention that both flash drives was formatted to FAT32.

[Renate]

It put the log back on your flash drive.
What does it say?

[kekesed97]

Uhm, no, I have no log file on my flash drive.

[Renate]

If it ran cleanly to "not rebooting" there should be autolog.txt on the flash drive.

If not try to get a photo of the last screen.
Since it doesn't reset it should be easy.

[kekesed97]

I found no log file in every run, and the process always halted at this screen.

[Renate]

Oh!
Yeah, this is the old script-based update.

autoupdate has two entirely separate chunks for old and new.
I might not have done sufficient due diligence on the old stuff.

It's bombing on the first couple of lines of the script where it verifies model and version.

Take your update.zip
Extract updater-script from META-INF...
Delete (probably) the first two lines.
Repack it back in the zip.

[kekesed97]

I tried that and the update process still halted. In fact, I used check-removed update.zip in my previous attachment.

[Renate]

Oops. Read PM. Try again.

[kekesed97]

I just tried the new recovery image and still have the same result.

[Renate]

Well, you've got ADB (in recovery).

C:\>adb shell
# ls -l /system/bin/update-binary
# update-binary
# update-binary 2 1 somefakename

Does it print some usage?

[kekesed97]

Uhh, it doesn't show usage?

PS D:\Android Tools\platform-tools> adb shell
# ls -l /system/bin/update-binary
-rwxr-xr-x 1 root root 2134344 1970-01-01 00:00 /system/bin/update-binary
# updatebinary
/system/bin/sh: updatebinary: inaccessible or not found
# update-binary
unexpected number of arguments: 1
# update-binary 2 1 MaxLumi4
Unable to open 'MaxLumi4': No such file or directory
failed to map package MaxLumi4
# update-binary 2 1 update.zip
Unable to open 'update.zip': No such file or directory
failed to map package update.zip
# update-binary 2 1 somefakename
Unable to open 'somefakename': No such file or directory
failed to map package somefakename

[Renate]

Oops. Ok. DL the new one. Try the regular update procedure again.

[kekesed97]

The update was success, thank you so much!
Now my MaxLumi identifies as retail MaxLumi as it should!

ro.product.device: MaxLumi
ro.build.date: Tue Dec 12 20:35:12 HKT 2023
ro.product.model: MaxLumi
ro.build.fingerprint: ONYX/MaxLumi/MaxLumi:10/2023-12-12_20-35_3.5_4687b1901/12698:user/dev-keys
ro.build.display.id: 2023-12-12_20-35_3.5_4687b1901
ro.build.version.incremental: 12698