How to Root the Onyx Boox Note Air 2 Plus (Windows)

[bigwigs]

Weird this http://data.boox.com/api/1/firmware/update?where={"buildNumber":0,"buildType":"user"," deviceMAC":"","fingerprint":"","lang":"en_US","mod el":"NoteAir2P","submodel":""}

still shows 3.5 update and not 3.5.1 as on device.

[bigwigs]

Full update now available for Note2AirP - http://data.boox.com/api/1/firmware/update?where={%22buildNumber%22:0,%22buildType%22: %22user%22,%22deviceMAC%22:%22%22,%22fingerprint%2 2:%22%22,%22lang%22:%22en_US%22,%22model%22:%22Not eAir2P%22,%22submodel%22:%22%22}

For those who rooted, u would need to retrieve new boot.img and patch it again via Magisk and then repeat the earlier instructions.

[dcarvil]

Originally Posted by bigwigs

I'm getting error -"Update failed"- updating to latest firmware update. It is failing while applying update after downloading, and decrypting.
anyone else getting same error?

Below is log using logcat:-

**************************
03-26 14:20:56.402 1115 1115 I update_engine: [INFO:delta_performer.cc(397)] Applying 33 operations to partition "boot"
03-26 14:20:56.405 1115 1115 I update_engine: [INFO:delta_performer.cc(657)] Starting to apply update payload operations
03-26 14:20:56.418 1115 1115 E update_engine: [ERROR:delta_performer.cc(431)] Unable to open ECC source partition boot on slot A, file /dev/block/bootdevice/by-name/boot_a: Success (0)
03-26 14:20:56.422 1115 1115 E update_engine: [ERROR:delta_performer.cc(1158)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
03-26 14:20:56.426 1115 1115 E update_engine: [ERROR:delta_performer.cc(1163)] Expected: sha256|hex = 8445F2D8A5299B679B27FE0E74B8D3AD2A4DBF574CAC2E7AEF D5569951E8D4EB
03-26 14:20:56.429 1115 1115 E update_engine: [ERROR:delta_performer.cc(1166)] Calculated: sha256|hex = D392117B4BB96EE4F7E0540C0B6A1EA87CD2673F0ED862D639 195095BB6F4BF3
03-26 14:20:56.432 1115 1115 E update_engine: [ERROR:delta_performer.cc(1177)] Operation source (offset:size) in blocks: 0:1,9540:2,24575:1
03-26 14:20:56.437 1115 1115 E update_engine: [ERROR:delta_performer.cc(1498)] source_fd != nullptr failed.
03-26 14:20:56.441 1115 1115 E update_engine: [ERROR:delta_performer.cc(297)] Failed to perform BROTLI_BSDIFF operation 0, which is the operation 0 in partition "boot"
03-26 14:20:56.446 1115 1115 E update_engine: [ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
03-26 14:20:56.449 1115 1115 I update_engine: [INFO:delta_performer.cc(314)] Discarding 389 unused downloaded bytes
03-26 14:20:56.453 1115 1115 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
03-26 14:20:56.456 1115 1115 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
03-26 14:20:56.459 1115 1115 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
03-26 14:20:56.500 1115 1115 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
03-26 14:20:56.508 1115 1115 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
03-26 14:20:56.510 1115 1115 I update_engine: [INFO:update_attempter_android.cc(522)] Processing Done.

**************************

Wonder rooting is the cause or not?

Yes, rooting caused the error. This is an incremental update, which makes changes to the existing boot.img. If the existing boot.img is not what the code expects, it does not attempt to make the changes.

You'll have to restore boot.img to the stock, unrooted image to update, then re-root.

[bigwigs]

Originally Posted by dcarvil

Yes, rooting caused the error. This is an incremental update, which makes changes to the existing boot.img. If the existing boot.img is not what the code expects, it does not attempt to make the changes.

You'll have to restore boot.img to the stock, unrooted image to update, then re-root.

Do you have stock rom boot.img?

[dcarvil]

Originally Posted by bigwigs

Do you have stock rom boot.img?

Sorry, I don't have it for the NoteAir2P. I don't have that model, I have a NoteAir3. You might still have the stock image on your alternate slot, i.e. if your current boot slot is a, slot b might have the stock image depending on what you did when you originally rooted.

Also, you can try Magisk, Uninstall Magisk, Restore Images. Magisk may have a copy of the stock image.

[bigwigs]

Originally Posted by dcarvil

Sorry, I don't have it for the NoteAir2P. I don't have that model, I have a NoteAir3. You might still have the stock image on your alternate slot, i.e. if your current boot slot is a, slot b might have the stock image depending on what you did when you originally rooted.

Also, you can try Magisk, Uninstall Magisk, Restore Images. Magisk may have a copy of the stock image.

Thanks, I tried booting into another slot but it ends up in stuck fastboot mode.

[Renate]

Originally Posted by bigwigs

Do you have stock rom boot.img?

Model:  NoteAir2P (English)
Finger: Onyx/NoteAir2P/NoteAir2P:11/2024-03-19_07-14_3.5.1_857dde0262/45070:user/release-keys
Link:   http://firmware-us.boox.com/60381ca1bd76d6e0f4b7b91f39014f68/update.upx
Size:   1,686,820,005
MD5:    60381ca1bd76d6e0f4b7b91f39014f68

[bigwigs]

Originally Posted by Renate

Model:  NoteAir2P (English)
Finger: Onyx/NoteAir2P/NoteAir2P:11/2024-03-19_07-14_3.5.1_857dde0262/45070:user/release-keys
Link:   http://firmware-us.boox.com/60381ca1bd76d6e0f4b7b91f39014f68/update.upx
Size:   1,686,820,005
MD5:    60381ca1bd76d6e0f4b7b91f39014f68

no luck, same error even after using boot.img from above update.

[Renate]

Originally Posted by bigwigs

no luck, same error even after using boot.img from above update.

Don't just use the boot image out of the update.
Install the update completely.
Only that way are the kernel mods and the kernel guaranteed to be consistent.

You can download the update to the desktop and push the still encrypted update.upx to /sdcard.

am start -a onyx.settings.action.firmware

[bigwigs]

Originally Posted by Renate

Don't just use the boot image out of the update.
Install the update completely.
Only that way are the kernel mods and the kernel guaranteed to be consistent.

You can download the update to the desktop and push the still encrypted update.upx to /sdcard.

am start -a onyx.settings.action.firmware

ok, cool. i will try that.