Root Boox Note Air 3C - Page 4

Renate · 11-26-2024, 07:22 AM

Quote:

Originally Posted by farfromrefuge

Just for my info you did it with an edl cable?

With a working system it's as easy as "adb reboot edl". It's only sometimes with a bricked device that you need an EDL cable or even EDL test points.

farfromrefuge · 01-01-2025, 09:34 AM

Does anyone knows a way to boot the Note Air 3c in safe mode? I am stuck on boot and i think it is caused by magisk. Would need to start in safe mode to disable it

Renate · 01-01-2025, 10:56 AM

Onyx don't have the normal boot screens that a phone has so it would be hard to see if Safe Mode even exists. It probably does but requires volume buttons.

You could replace the Magisk boot image with the stock boot image, but that will leave you without root and you won't be able to disable the Magisk module that is causing the problems.

You might be able to patch your Magisk boot image so that it will disable the conflicting module.

This all can be a sticky situation, one reason that I don't use Magisk.

dcarvil · 01-01-2025, 11:08 AM

Quote:

Originally Posted by farfromrefuge

Does anyone knows a way to boot the Note Air 3c in safe mode? I am stuck on boot and i think it is caused by magisk. Would need to start in safe mode to disable it

If you still have adb, try this:

https://github.com/badabing2005/Magisk

cronkdonkey · 01-22-2025, 09:15 AM

Anyone have any additional tips for unbricking?

I successfully rooted my note air 3c on 3.5.4, but then I did some experimenting and messed things up...stuck on the onyx logo, not booting.

I tried to restore my system backup (minus userdata.bin, which I never backed up...) using `edl qfil rawprogram0.xml patch0.xml dumps_dir/lun01` for lun01 through lun05.

I have access to fastboot (crippled in the latest version) and edl using an edl cable. No adb. I also manually reflashed key partitions (boot, vbmeta), but still not booting.

(I even created a blank userdata.bin of the same size and flashed that, which probably screwed things up even more...I realize now I should have probably just read the entire flash to a single .bin...)

All I can figure is there is something is wrong with my backup...does anyone have the full stock firmware that I can flash? Would that save my $500+ brick? Again, I have edl mode, but nothing I do restores the ability to boot...

Also, in case people are having trouble following the thread (I did at first), the edl loader that worked for my note air 3c is 001b80e102e80000_8b2d1c830d9d8576_fhprg_moto_g52.b in

Renate · 01-22-2025, 10:12 AM

Many partitions are never included in even a full update.

If it were just a case of messed up Magisk a full update will fix that. You could even extract just the boot partition out of a full update.

cronkdonkey · 01-22-2025, 09:24 PM

Thank you, I appreciate the response. Still bricked!

I downloaded the 3.5.4 upx from boox, decrypted it, then flashed the boot partition with edl--no luck--then all of the other partitions in the update (except for system, vendor, and product, for which I'd need to rebuild a super partition to flash, from my limited understanding?). Still no luck. `fastboot reboot recovery` seems to do something, but it just again hangs on the onyx logo. Blue or purple led, onyx logo--that's all I can produce right now.

Come to think of it, I wonder if restoring my backup is what truly bricked things. I was having issues before that, caused by my own messing around, but I still had adb until I flashed the backup partitions...lesson learned, hopefully: always make a full, verified backup before tinkering...

Any unbricking tips?

Renate · 01-23-2025, 02:56 AM

Usually recovery is more bomb-proof than the normal system because it has less dependencies and no vbmeta.

When your device stalls on normal boot, are you sure that there is no ADB. ADB is technically independent of the Android subsystem, but is mostly started by it. Another reason that I make ADB entirely independent.

Bad userdata can break the normal system, but not recovery.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to Root the Onyx Boox Note Air 2 Plus (Windows)	Chitter	Onyx Boox	160	06-18-2025 01:58 PM
Root for Note Air 2?	downeaster59	Onyx Boox	187	11-08-2023 05:54 PM
Ended Boox Note Air 2	downeaster59	Flea Market	3	11-22-2022 08:59 AM
Ended Looking for Boox Note 2 or Air (or other?)	Neru	Flea Market	2	09-15-2022 08:09 AM
Boox Note Air 2 Plus	Sonnenfee	Android	0	06-16-2022 08:29 AM

01-01-2025, 09:34 AM	#47
farfromrefuge Member Posts: 25 Karma: 24 Join Date: Dec 2016 Device: none	Does anyone knows a way to boot the Note Air 3c in safe mode? I am stuck on boot and i think it is caused by magisk. Would need to start in safe mode to disable it

01-01-2025, 10:56 AM	#48
Renate Onyx-maniac Posts: 3,915 Karma: 17236157 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Onyx don't have the normal boot screens that a phone has so it would be hard to see if Safe Mode even exists. It probably does but requires volume buttons. You could replace the Magisk boot image with the stock boot image, but that will leave you without root and you won't be able to disable the Magisk module that is causing the problems. You might be able to patch your Magisk boot image so that it will disable the conflicting module. This all can be a sticky situation, one reason that I don't use Magisk.

01-22-2025, 09:15 AM	#50
cronkdonkey Junior Member Posts: 2 Karma: 10 Join Date: Jan 2025 Device: boox note air 3c	Anyone have any additional tips for unbricking? I successfully rooted my note air 3c on 3.5.4, but then I did some experimenting and messed things up...stuck on the onyx logo, not booting. I tried to restore my system backup (minus userdata.bin, which I never backed up...) using `edl qfil rawprogram0.xml patch0.xml dumps_dir/lun01` for lun01 through lun05. I have access to fastboot (crippled in the latest version) and edl using an edl cable. No adb. I also manually reflashed key partitions (boot, vbmeta), but still not booting. (I even created a blank userdata.bin of the same size and flashed that, which probably screwed things up even more...I realize now I should have probably just read the entire flash to a single .bin...) All I can figure is there is something is wrong with my backup...does anyone have the full stock firmware that I can flash? Would that save my $500+ brick? Again, I have edl mode, but nothing I do restores the ability to boot... Also, in case people are having trouble following the thread (I did at first), the edl loader that worked for my note air 3c is 001b80e102e80000_8b2d1c830d9d8576_fhprg_moto_g52.b in

01-22-2025, 10:12 AM	#51
Renate Onyx-maniac Posts: 3,915 Karma: 17236157 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Many partitions are never included in even a full update. If it were just a case of messed up Magisk a full update will fix that. You could even extract just the boot partition out of a full update.

01-22-2025, 09:24 PM	#52
cronkdonkey Junior Member Posts: 2 Karma: 10 Join Date: Jan 2025 Device: boox note air 3c	Thank you, I appreciate the response. Still bricked! I downloaded the 3.5.4 upx from boox, decrypted it, then flashed the boot partition with edl--no luck--then all of the other partitions in the update (except for system, vendor, and product, for which I'd need to rebuild a super partition to flash, from my limited understanding?). Still no luck. `fastboot reboot recovery` seems to do something, but it just again hangs on the onyx logo. Blue or purple led, onyx logo--that's all I can produce right now. Come to think of it, I wonder if restoring my backup is what truly bricked things. I was having issues before that, caused by my own messing around, but I still had adb until I flashed the backup partitions...lesson learned, hopefully: always make a full, verified backup before tinkering... Any unbricking tips?

01-23-2025, 02:56 AM	#53
Renate Onyx-maniac Posts: 3,915 Karma: 17236157 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Usually recovery is more bomb-proof than the normal system because it has less dependencies and no vbmeta. When your device stalls on normal boot, are you sure that there is no ADB. ADB is technically independent of the Android subsystem, but is mostly started by it. Another reason that I make ADB entirely independent. Bad userdata can break the normal system, but not recovery.