Note Air 3c 4.0 beta 02

farfromrefuge · 01-13-2025, 06:36 AM

Would someone have the update.upx from beta02 ?
I installed it, patched for magisk and now i cant install beta03
https://en-data.boox.com/api/firmwar...s%22%3A1860%7D

The reason is that i forgot to save boot_b (i only saved boot_a). Then i patched boot_b with magisk applied on boot_a :s So now even if i patch stock beta02 boot_a on boot_b the update process fails telling in adb that the hash of boot_b is wrong.

Thanks!

farfromrefuge · 01-13-2025, 10:15 AM

found it by playing with the onyx api to request updates.
if anyone is interested here is the beta02 http://firmware-us.boox.com/f442edcf...407/update.upx

starkruzr · 01-16-2025, 02:18 AM

just to confirm: what you normally do when an update is released is write both of your unrooted boot partitions back to the device with EDL, let it do the incremental update, and re-root?

Renate · 01-16-2025, 06:10 AM

Yes, incremental updates have hashes of the partitions before and after. Also, since the updates work on modifications of the existing data it wouldn't even do you any good to bypass this.

Apparently, you only get the beta links if you have opted-in to the beta program and they have noted your device MAC. Otherwise it will refer you to September's full update. The pixel width/height is not necessary.

farfromrefuge · 01-27-2025, 05:16 AM

Thanks. I managed to get the link of the update, then get boot.img then patch it ! So all good.

I did not write back unrooted boot partitions, the update did it so i ended up with unpatched. But then i could not get the boot img to patch it. I tried to get it from the device with Renate EDL tool but it seems that the boot.img i got from it was "small" (30mb while update one is 100mb)

Renate · 01-27-2025, 01:37 PM

Quote:

Originally Posted by farfromrefuge

I tried to get it from the device with Renate EDL tool but it seems that the boot.img i got from it was "small" (30mb while update one is 100mb)

If you use the /t option it will truncate Android images or ELF files to the actual active size.

In the old days an Android image was 12-20 MB, now more like 30-50 MB. Usually the partition itself is about 100 MB.

If you are dealing with stock images there are AVB footers at the end so instead of saving 30 MB you have to save all 100 MB (or whatever). If your image is Magisk it does have signatures after the "normal" active area but you don't really need them.

Sounds complicated? It is.

farfromrefuge · 01-28-2025, 04:12 PM

Thanks for the explanation. Indeed it is complicated. My main issue was that boox update process check boot hash and compare it with expected value.
So i guess that s it i did not have the headers and the hash was then different from what was expected

farfromrefuge · 02-02-2025, 04:46 AM

I found the issue which now prevents me from upgrading to latest rc of 4.0
Some small updates like beta03 just patch the boot.img thus changing its hash.
But i only store the boot.img i got from beta02, I didnt upload the patch boot img from beta03 with edl. So now whichever boot.img i get that i patch on the device it will always say the hash is wrong!

Is someone currently on beta03 by any chance? Could you get your boot.img using EDL?

Not a bad situation. I can live with beta03 or wait for actual 4.0 release.

01-13-2025, 06:36 AM	#1
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	Note Air 3c 4.0 beta 02 Would someone have the update.upx from beta02 ? I installed it, patched for magisk and now i cant install beta03 https://en-data.boox.com/api/firmwar...s%22%3A1860%7D The reason is that i forgot to save boot_b (i only saved boot_a). Then i patched boot_b with magisk applied on boot_a :s So now even if i patch stock beta02 boot_a on boot_b the update process fails telling in adb that the hash of boot_b is wrong. Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Note Air 3C	Renate	Onyx Boox	15	09-23-2023 01:57 PM
Ended Boox Note Air 2	Mr. Goodbar	Flea Market	3	02-25-2022 05:28 PM
Help with Note Air 2	Newby31	Onyx Boox	7	12-08-2021 06:00 AM
Note Air 2 firmware	downeaster59	Onyx Boox	3	12-06-2021 07:59 AM
Onyx Boox is recruiting Note Air firmware v3.2 beta testers	yokos	Onyx Boox	2	12-02-2021 07:05 PM

01-13-2025, 10:15 AM	#2
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	found it by playing with the onyx api to request updates. if anyone is interested here is the beta02 http://firmware-us.boox.com/f442edcf...407/update.upx

01-16-2025, 02:18 AM	#3
starkruzr Connoisseur Posts: 61 Karma: 10 Join Date: Nov 2024 Device: Boox Palma 2, Note Air 4C, Note Max	just to confirm: what you normally do when an update is released is write both of your unrooted boot partitions back to the device with EDL, let it do the incremental update, and re-root?

01-16-2025, 06:10 AM	#4
Renate Onyx-maniac Posts: 3,914 Karma: 17236157 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Yes, incremental updates have hashes of the partitions before and after. Also, since the updates work on modifications of the existing data it wouldn't even do you any good to bypass this. Apparently, you only get the beta links if you have opted-in to the beta program and they have noted your device MAC. Otherwise it will refer you to September's full update. The pixel width/height is not necessary.

01-27-2025, 05:16 AM	#5
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	Thanks. I managed to get the link of the update, then get boot.img then patch it ! So all good. I did not write back unrooted boot partitions, the update did it so i ended up with unpatched. But then i could not get the boot img to patch it. I tried to get it from the device with Renate EDL tool but it seems that the boot.img i got from it was "small" (30mb while update one is 100mb)

01-28-2025, 04:12 PM	#7
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	Thanks for the explanation. Indeed it is complicated. My main issue was that boox update process check boot hash and compare it with expected value. So i guess that s it i did not have the headers and the hash was then different from what was expected

02-02-2025, 04:46 AM	#8
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	I found the issue which now prevents me from upgrading to latest rc of 4.0 Some small updates like beta03 just patch the boot.img thus changing its hash. But i only store the boot.img i got from beta02, I didnt upload the patch boot img from beta03 with edl. So now whichever boot.img i get that i patch on the device it will always say the hash is wrong! Is someone currently on beta03 by any chance? Could you get your boot.img using EDL? Not a bad situation. I can live with beta03 or wait for actual 4.0 release.

Advert

Advert