Need help to unbrick Boox Max Lumi 1

[kekesed97]

Hi, I got this bricked device from a friend, so I don't have any idea on what he previously done.

This device always go into recovery. And the recovery says "Can't load Android system. Your data maybe corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored in this device."

I search the internet but got little to no info about unbricking a Boox Max Lumi.

Thanks in advance.

[Renate]

Does it give you an option for "factory reset"?

[kekesed97]

It does, and wiped succesfully. It booted, got the backlit up, then the power dropped (I got into Android's first boot loading screen once before the power drops).
I noticed that power-off charging percentage went haywire (from 54% instantly jumped to 100%). I suspect it was power issue?

[kekesed97]

Never mind, I got them working.
Turns out it really have a flat battery. Desoldered the original one and put a test battery I have, and it booted.
However I do want to know the unbricking method, just in case

[kekesed97]

Bumping this thread. I have another question but I don't think it should be posted on a new thread, so I'm posting them here.
My Max Lumi identifies itself as EPSLite2C09, refusing official firmware update. Does anybody have info on this?

[Renate]

Where exactly do you see "EPSLite2C09"?
That could just be some wacky Windows driver that got loaded.

It could be that someone flashed some incompatible firmware.

[kekesed97]

I saw them everywhere. About device, MTP name, ro.product.device...
ro.product.device: EPSLite2C09
ro.build.date: Wed Mar 31 10:46:56 CST 2021
ro.product.model: EPSLite2C09
ro.build.fingerprint: ONYX/EPSLite2C09/EPSLite2C09:10/2021-03-31_10-46_crea-3.1_09ca0952a/1908:user/dev-keys
ro.build.display.id: 2021-03-31_10-46_crea-3.1_09ca0952a
ro.build.version.incremental: 1908

I talked to Boox's customer support and they offered to flash retail firmware for a fee, but I figured the cost outweight the benefit for an out of support device.

[Renate]

So, get the latest update:

Model:  MaxLumi (English)
Finger: ONYX/MaxLumi/MaxLumi:10/2023-12-12_20-35_3.5_4687b1901/12698:user/dev-keys
Link:   http://firmware-us.boox.com/382647ca3866d28d1c3a519c8f1d62e6/update.upx
Size:   1,722,401,345
MD5:    382647ca3866d28d1c3a519c8f1d62e6

Decrypt it
Unpack META-INF/com/google/android/updater-script
In a text editor (NOT Windows Notepad) delete the first two lines (less_than & getprop)
Repack
Use the update

If it gives you any backtalk we can do update-binary directly.

[kekesed97]

Sorry but am I supposed to flash the modified update zip via fastboot?
Executing fastboot update update.zip gave me:

archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt

adb wasn't accessible through stock recovery so I can't execute adb update update.zip either.

[Renate]

There's no update option in recovery?

That update does not have a recovery in it so I can't patch it.
If somebody can pull a recovery off a Lumi I could.

If you can pull your recovery off with EDL I could.
(But that would be a bit wasteful of my time making a custom recovery for a rogue version of an obsolete device.)

[kekesed97]

No, unfortunately my recovery doesn't have that. But fortunately, my device can boot into yokos' magisk patched boot.img.
If a patched stock recovery is enough then don't really need to go the extra length. I pulled recovery partition from my device.

[Renate]

I sent you a PM a few days ago.

[kekesed97]

Sorry Renate, I just noticed that. And thank you.
I'll try them tomorrow morning my time and report back.

[kekesed97]

Hi Renate,
Continuing from PM, I tried to pull /system/lib64/libota_jni.so but apparently my device don't have them.

adb: error: failed to stat remote object '/system/lib64/libota_jni.so': No such file or directory

If you meant to pull decryption keys, I can pull them from /system/priv-app/OnyxOtaService/OnyxOtaService.apk, jadxed to find res/values/strings.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="action_settings">Settings</string>
    <string name="app_name">OTA service</string>
    <string name="battery_level_not_safe">Low battery! Please ensure a minimum of 30% of the battery for the update！</string>
    <string name="can_not_find_update_package">No update package detected!</string>
    <string name="cancel">Cancel</string>
    <string name="disk_io_error">Error in copying update package!</string>
    <string name="disk_space_not_enough">The remaining storage is less than 2GB. Please free some space and try to check for update again.</string>
    <string name="find_update_package_from_local">An update package detected from the local storage. Copying package...</string>
    <string name="hello_world">Hello world!</string>
    <string name="is_upgrad">Do you want to update your BOOX?</string>
    <string name="local">O4Xa9WRESDqXr0302UBYQ7hURqLxRufpRYRM56as</string>
    <string name="model_does_not_math">The update package is not for this model. Please download the right update package！</string>
    <string name="ok">OK</string>
    <string name="package_install_falied">Update failed.</string>
    <string name="package_verify_falied">The update package verification failed.</string>
    <string name="settings">JdGNuTFbE2XCV8qiouuFdHwvhcHCdHVVfFh0ODrZDMRs</string>
    <string name="upgrad">Update</string>
    <string name="upgrade">LaSNxzdeYWHYWK/hk8QLz4LkMKxkX+uq1acwVJ1qMXSb</string>
    <string name="upgrade_package_is_incomplete">The update package is damaged. Please download it again！</string>
    <string name="waiting">Updating! Do not power off or turn to sleep mode! The whole update will take a few minutes.</string>
</resources>

Running these strings through BooxKeyConvert.py:

D:\Android Tools\decryptBooxUpdateUpx-master> python .\BooxKeyConvert.py EPSLite2C09 JdGNuTFbE2XCV8qiouuFdHwvhcHCdHVVfFh0ODrZDMRs LaSNxzdeYWHYWK/hk8QLz4LkMKxkX+uq1acwVJ1qMXSb
JdGNuTFbE2XCV8qiouuFdHwvhcHCdHVVfFh0ODrZDMRs
10684070534AF96599E83D24F4A68DEC

LaSNxzdeYWHYWK/hk8QLz4LkMKxkX+uq1acwVJ1qMXSb
9E6F25E49DF0F4531CC3CB6F93758C86

Oh I should attach OnyxOtaService.apk as well...

[Renate]

Thanks. I hadn't realized that this was that old. The keys have been added.