No options for Note Air 4C

[amperage4255]

Magisk after rooting in EDL just refuses to move past the splash screen and everyone github is like use Apatch, Apatch superuser section doesnt work but it installs completely.

[Renate]

Go to the bootloader (fastboot):

adb reboot bootloader
fastboot oem device-info
fastboot get_unlock_ability
fastboot reboot

If it's using the new stuff, the first will work.
If it's using the old stuff, the second will work.

[amperage4255]

My apologies, can you elaborate on what you mean by new stuff, do you mean new stuff as in new with the manufacturer or new with the software or kernel version and first being magisk and apatch being second.

My method is
https://github.com/jdkruzr/BooxPalma2RootGuide

do I follow this guide first and then your instruction second?

I'm not the smartest crayon in the knife drawer but I'm trying my best to understand. My intention is to debloat my device and limit its interactions on the internet. I have magisk patched boots on standby.

Thank you Renate

[Renate]

I think that's all basically right.
I don't know if something has changed with updates.
It's a question of locking and verifying.

Which is why I asked you to do a quick experiment above.

[amperage4255]

i flashed the patched boots from magisk as said the magisk app just hangs. I rebooted into fastboot using adb as you requested but the device is not being read as anything and stuck with the boot logo on screen. ./fastboot devices yields no results.

edit: nevermind my windows machine just doesn't recognize fastboot for this and it does on my fedora system

[amperage4255]

Okay yea the first one worked.
what now.

[Renate]

Originally Posted by amperage4255

Okay yea the first one worked.
what now.

Well, let me see...
How about you tell me what it typed out?

[amperage4255]

y'know what when i did this, I awaited a response but then had to go about my day and I didnt save the results of the first command but everything said "OK" at the end of it. sorry, like I said Its been a bit since i participated in forum and done anything like this in a bit, it didnt cross my mind at all to make sure to save the results before I left.

Thank you for your guidance, if you wish to continue trouble shooting, then feel free, if not disregard.

[amperage4255]

Does anyone have any other location that can provide any assistance that is a bit nicer and clearer. I'll me much appreciative and gracious for the help because I just want to be able to debloat my boox thoroughly and im currently dealing with incompatibility with magisk.

Would I have better luck with reddit? I've been lurking on this forum for a bit and was excited when i got my boox for christmas. The previous individual who's the backbone of this forum has decline to assist.

[Kisuke-CZE]

It is probably bug in combination with Onyx firmware 4.1 and Magisk.

If even APatch does not work for you, there is something strange.
I have Palma on 4.1.1 and Magisk works without issues. I would expect I will have same issues since software should be similar.

Can you try to enable Magisk to run in background? On Note Air series menu will be probably little different.

[amperage4255]

Magisk (presshold)> Optimize>Others>Stay active in the background

I'm just reading out my steps cause I'm very new with this device. But enabling this had no effect on it.

[amperage4255]

Originally Posted by Kisuke-CZE

It is probably bug in combination with Onyx firmware 4.1 and Magisk.

If even APatch does not work for you, there is something strange.
I have Palma on 4.1.1 and Magisk works without issues. I would expect I will have same issues since software should be similar.

Can you try to enable Magisk to run in background? On Note Air series menu will be probably little different.

Something interesting to add is that my device has its device oem toggle off indicating that my bootloader is unlocked which is what I think renate was trying to find out. I think I have a grasp as to what the command oem-device-info is for and they were trying to see what it was saying for me. I wish they had let me know that.


I'm trying to be as respectful in troubleshooting this, and hope that someone can chime in with a solution

oasis@secureblue:/var/home/oasis/edl$ fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
[1]oasis@secureblue:/var/home/oasis/edl$ fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
[1]oasis@secureblue:/var/home/oasis/edl$ fastboot devices
78c28bea	 fastboot
oasis@secureblue:/var/home/oasis/edl$ fastboot get_unlock_ability
fastboot: usage: unknown command get_unlock_ability
[1]oasis@secureblue:/var/home/oasis/edl$ fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
[1]oasis@secureblue:/var/home/oasis/edl$ fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed

Upon trying the commands again they online provide an error now. Before one of them came up as a bunch of "OK".

I also would like to add that I couldnt get EDL working on my Secureblue (Fedora) system but I got it working on the windows 11 computer i had around so im having to work with both. ADB and Fastboot works on Fedora and ADB and EDL works on Windows 11. I'm trying my best

[darkwill]

You could turn off Win driver enforcement, and add the device PID to the Google USB driver, and then install it to the system. Once done just reboot back to normal. Download the r13 driver, edit the inf file to add this below in the [Google.NTamd64] section:

;Boox
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D

[amperage4255]

Okay so i feel like this warrants another reply but i realize the reason why i couldnt replicate the results for renate was because I was in fastbootd mode and had to reboot back.

fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [  0.000s]
Finished. Total time: 0.000s

Here's the results for that

[Kisuke-CZE]

You said before you are already rooted. So another try of rooting would not do anything.

That thing with enabling Magisk to run on background was just my guessing. If it says installed, magisk should ask with popup window if you allow/dont allow root access for app that just requested it. So I was thinking maybe Magisk was killed by power management and cannot show you that popup.

Just from curiosity. When you connect that device to computer and run:

adb shell
su

Does anything happen?
Normally su should hang and on display of the device magisk should ask for allowing root.
If you click allow, then you get root shell - you can check with whoami command. this is usualy enough for me for any operation.


"DEBLOATING" is possible without root access using command

adb shell pm uninstall -k --user 0 PACKAGENAME

It is good enough tool to even kill the device (factory reset with some keycombo usually helps) if not used with caution.