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

[nagapow]

Originally Posted by Renate

An update will probably update the boot image and you will lose root.
At the very least you will need to replace the boot image with your last Magisk'ed boot image.
You probably should let the Magisk app process the latest boot image and use that.

@nagapow So you're seeing the boot animation for two minutes solid?
It should run for about 10 seconds. Mine counts and barely gets to ten.
You should run:

C:\>adb logcat

and see what it's doing.

Yes seeing boot animation for solid 2 and half minutes.

I may be regretting this....but to solve the long boot time problem, I thought i would get back to the original bootloader that was backed up by Magisk app. I used the Magisk app built in 'restore' image function, it showed 'done', I then rebooted. I then uninstalled afwall and Magisk app.

The problem with long boot time still persists. I thought i would restore the whole tablet to factory setting and reroot again.. but am not too sure how to proceed with this.

I ran logcat just now, as you advised, bunch of text came up, i am not sure what i am looking for. but something is definitely wrong, this error:

"10-13 13:43:58.703 1350 1859 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19"

is running constantly in the logcat, doesn't stop at all, the text keeps on running every second....

How do i get back to factory clean slate and then perhaps re-root again?

[nagapow]

I have been doing some reading online - it seems like its not the issue with the bootloader that is causing the slow down. The android system is loading very slow, so i would want to reset the android system.

Should i do a factory reset of my device? is there a risk a factory reset will brick my device?

[Renate]

I've been wary of "factory reset" because I don't know which stone-age version they mean by "factory version".

The question is, is it just the booting that is slow or is your device staggering under a load.
Once it boots is everything as fast as it was or slower?

C:\>adb shell
$ top

Are all the numbers at the top small-ish?

[nagapow]

Originally Posted by Renate

I've been wary of "factory reset" because I don't know which stone-age version they mean by "factory version".

The question is, is it just the booting that is slow or is your device staggering under a load.
Once it boots is everything as fast as it was or slower?

C:\>adb shell
$ top

Are all the numbers at the top small-ish?

Slow boot time, and once booted things are running at normal speed.

Here is an image what i am seeing:

[Renate]

Yeah, a single processor counts as 100% so 782% idle on octo-processor is just goofing off.
So, something makes it grind on boot-up, but it looks like it's doing no harm afterwards.

[ljfriese]

Friggin eh, great job.

I have literally never experienced such well put together instructions for something like this. I can add that restarting the PC is definitely a needed step. I didn't receive a prompt to do so, but nothing worked until I did it, at the one point where you mention it.

[Chitter]

@ljfriese, Haha! Awesome. I'm glad to hear it helped. It's what I wished I had when I tried. Thanks for the appreciation and for feedback about the reboot.

[readandread]

@Chitter Thanks for the great guide! I tried rooting on an old Win laptop, but can't seem to get passed the

edl.exe /u /r /pboot_a boota.img /t

where I get a "Unknown command flag R" error

@Renate Any ideas what that could be? The firehouse it detected in the previous step no probs. I also tried partition b

Edit: Now I'm getting "access denied" when the terminal tries to interact with the edl.exe. I've already excluded the app from the Windows defender just in case.

[Renate]

Originally Posted by readandread

Any ideas what that could be?

You must have a really old edl.exe, the /r flag came in a good while ago.
Grab a new one: http://www.temblast.com/edl.htm
Make sure that it's 137,216 bytes
MD5 d8c37f6b682f4b0a4f9ef7476c0bae0d

[readandread]

Ok, thanks. Will try.

[Onscreen5467]

@Chitter,

Your instructions worked great for me from a windows box. Thank you for putting that together!

In case someone else is googling around, the EDL software out on GitHub is a different version and the commands are different.

Ex:

edl.exe /l662.elf

Would be closer to:

./edl --loader=662.elf

Anywho, thank you again for sharing the detailed instructions! No trouble rooting a freshly shipped NA2+

[Chassid]

Critter, thank you so much for this! This saved me so many hours, you have no idea. Also Renate, thank you so much for your insane expertise!

I deviated a little bit from Chitter's guide by using the 'python' edl tool instead of the one by Renate, and by flashing the patched bootloader using Magisk direct install instead of fastboot flash. To me, this felt safer, although this may not be true at all. I just wanted to let people know that it is indeed possible this way.

[Chassid]

It's of course best and safest to dump the boot image yourself, but in case it might help anyone here are the patched (using Magisk) and unpatched dumps for 3.3.1: https://gofile.io/d/ErSRir

My apologies for the double post.

[Chitter]

@Onscreen5467 - You're welcome. I'm glad it worked for you!
@Chassid - No problem. That's what I was hoping it would do!

[Chitter]

Latest patched image and updated instructions.