Downgrade Note Air 3 Firmware

FrederickGeek8 · 11-07-2025, 04:11 PM

Hi everyone! In the midst of trying to root my (US) BOOX Note Air 3, I upgraded without thinking from 3.5.4 to 4.1 via the `update.upx` from data.onyx-international.cn (rather than data.boox.com).

I would really like to downgrade to 3.5.4 but I am blocked from the normal System Update and `adb sideload` methods by an anti-rollback mechanism. How can I force a downgrade?

If necessary, I am prepared to lose all the data on my device.

Thanks for your help! Let me know if you want other information from me such as `edl` information.

Renate · 11-08-2025, 05:24 AM

A custom recovery will bypass the anti-rollback.

Personally, I think rollbacks are a dead-end, but whatever.

FrederickGeek8 · 11-14-2025, 09:33 AM

What do you mean by "dead-end"?

Renate · 11-14-2025, 10:02 AM

Every new software has something good in it and very often something bad in it.
If you decide to stop at some point of development you might be missing out on something.
OTOH, if the development is dead anyway you might have picked a good point.

FrederickGeek8 · 11-14-2025, 12:05 PM

I decided to give your custom recovery a go, and despite seeming to flash successfully, I am now looking at a "Can't load Android system. Your data may be corrupt..." screen. The version listed appears to be correct, 3.5.4, at least.

There are two options listed here: "Try again" (it just reboots to the same screen) and "Factory data reset". What should I do next? I'm not sure if it's safe to "Factory data reset" and/or try "start autoupdate" again.

Thoughts on next steps, Renate?

For completeness, here is a overview of the steps I took:
1. Flash recovery_a/_b with edl with custom recovery
2. adb reboot recovery -> adb shell -> start autoupdate
3. Throw the 3.5.4 update.zip on a FAT32 + MBR flash drive and connect it
4. Watch as it appeared to flash correctly (I may have looked away for a second or two...)

I believe that it rebooted without manual intervention, but I may have tapped the power button to confirm a reboot if there was a prompt -- my memory is a little fuzzy.

Renate · 11-14-2025, 01:57 PM

As I said, going backwards can leave you with system configuration files that are not understood by the older system.
Factory data reset is probably what you need (as long as you are prepared to lose your data).

FrederickGeek8 · 11-14-2025, 06:46 PM

Factory reset brought me back to a working (albeit blank) system. Thanks a bunch!

11-07-2025, 04:11 PM	#1
FrederickGeek8 Junior Member Posts: 4 Karma: 10 Join Date: Nov 2025 Device: BOOX Note Air 3	Downgrade Note Air 3 Firmware Hi everyone! In the midst of trying to root my (US) BOOX Note Air 3, I upgraded without thinking from 3.5.4 to 4.1 via the `update.upx` from data.onyx-international.cn (rather than data.boox.com). I would really like to downgrade to 3.5.4 but I am blocked from the normal System Update and `adb sideload` methods by an anti-rollback mechanism. How can I force a downgrade? If necessary, I am prepared to lose all the data on my device. Thanks for your help! Let me know if you want other information from me such as `edl` information.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Need help flashing Boox Note Air firmware	Boox4ev	Onyx Boox	21	09-10-2025 05:03 AM
Note Air 1 firmware 3.3.1?	Nirodha	Onyx Boox	0	10-18-2023 03:12 PM
Boox Note Air 2 – A stylus downgrade?	MrE	Onyx Boox	3	03-07-2022 03:27 PM
Note Air 2 firmware	downeaster59	Onyx Boox	3	12-06-2021 08:59 AM
new firmware for note air	fbrzvnrnd	Onyx Boox	3	12-06-2021 04:13 AM

11-08-2025, 05:24 AM	#2
Renate Onyx-maniac Posts: 4,170 Karma: 19000001 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	A custom recovery will bypass the anti-rollback. Personally, I think rollbacks are a dead-end, but whatever.

11-14-2025, 09:33 AM	#3
FrederickGeek8 Junior Member Posts: 4 Karma: 10 Join Date: Nov 2025 Device: BOOX Note Air 3	What do you mean by "dead-end"?

11-14-2025, 10:02 AM	#4
Renate Onyx-maniac Posts: 4,170 Karma: 19000001 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Every new software has something good in it and very often something bad in it. If you decide to stop at some point of development you might be missing out on something. OTOH, if the development is dead anyway you might have picked a good point.

11-14-2025, 12:05 PM	#5
FrederickGeek8 Junior Member Posts: 4 Karma: 10 Join Date: Nov 2025 Device: BOOX Note Air 3	I decided to give your custom recovery a go, and despite seeming to flash successfully, I am now looking at a "Can't load Android system. Your data may be corrupt..." screen. The version listed appears to be correct, 3.5.4, at least. There are two options listed here: "Try again" (it just reboots to the same screen) and "Factory data reset". What should I do next? I'm not sure if it's safe to "Factory data reset" and/or try "start autoupdate" again. Thoughts on next steps, Renate? For completeness, here is a overview of the steps I took: 1. Flash recovery_a/_b with edl with custom recovery 2. adb reboot recovery -> adb shell -> start autoupdate 3. Throw the 3.5.4 update.zip on a FAT32 + MBR flash drive and connect it 4. Watch as it appeared to flash correctly (I may have looked away for a second or two...) I believe that it rebooted without manual intervention, but I may have tapped the power button to confirm a reboot if there was a prompt -- my memory is a little fuzzy.

11-14-2025, 01:57 PM	#6
Renate Onyx-maniac Posts: 4,170 Karma: 19000001 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	As I said, going backwards can leave you with system configuration files that are not understood by the older system. Factory data reset is probably what you need (as long as you are prepared to lose your data).

11-14-2025, 06:46 PM	#7
FrederickGeek8 Junior Member Posts: 4 Karma: 10 Join Date: Nov 2025 Device: BOOX Note Air 3	Factory reset brought me back to a working (albeit blank) system. Thanks a bunch!