A strange issue of rooting on Onyx Boox with system v4.1

SuiVu1fa · 09-12-2025, 06:33 PM

I am not sure whether it is device-specific. My device is Note Air 3C. After upgrading the system to v4.1 (2025-08-28_17-13_4.1-rel_0827_fc8adf71a), it seems that Magisk App does not work. After looking at the log, the key issue seems to be:

Code:

java.lang.NullPointerException: Attempt to read from field 'android.content.pm.ApplicationInfo com.android.server.am.ProcessRecord.info' on a null object reference

The same for APatch. Do you encounter similar issues?

Renate · 09-12-2025, 11:25 PM

Are you using the latest version of Magisk?
Where is the log?
Where is your boot image?

SuiVu1fa · Yesterday, 04:36 AM

Sorry, my previous post does not seem to be clear.

I use the latest release Magisk v29.0. It has no issue to open Magisk App on a non-rooted system, patch the boot (obtained via edl), and after flashing the patched boot, the system boots successfully with root.

The issue happens when I run Magisk App under this rooted device, which gets stuck at the splash. The log is captured via adb logcat.

Renate · Yesterday, 09:39 AM

Oh, well if the only point of your post is to canvas people and not necessarily get this problem fixed...

No, I don't have this problem.

SuiVu1fa · Yesterday, 12:28 PM

I do not see any way to report bug to Onyx Boox system (I think that it is an issue on their side, not on Magisk — this is reproducible on APatch as well, and it is a new issue after upgrading to this version of system), so I could only ask whether people are encountering similar issues to understand what to do next.

09-12-2025, 06:33 PM	#1
SuiVu1fa Member Posts: 22 Karma: 10 Join Date: Nov 2018 Device: Kindle	A strange issue of rooting on Onyx Boox with system v4.1 I am not sure whether it is device-specific. My device is Note Air 3C. After upgrading the system to v4.1 (2025-08-28_17-13_4.1-rel_0827_fc8adf71a), it seems that Magisk App does not work. After looking at the log, the key issue seems to be: Code: java.lang.NullPointerException: Attempt to read from field 'android.content.pm.ApplicationInfo com.android.server.am.ProcessRecord.info' on a null object reference The same for APatch. Do you encounter similar issues?

Yesterday, 04:36 AM	#3
SuiVu1fa Member Posts: 22 Karma: 10 Join Date: Nov 2018 Device: Kindle	Sorry, my previous post does not seem to be clear. I use the latest release Magisk v29.0. It has no issue to open Magisk App on a non-rooted system, patch the boot (obtained via edl), and after flashing the patched boot, the system boots successfully with root. The issue happens when I run Magisk App under this rooted device, which gets stuck at the splash. The log is captured via adb logcat. Last edited by SuiVu1fa; Yesterday at 09:11 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Rooting Onyx Boox Air Nova C problem	artyums	Onyx Boox	6	05-25-2024 10:31 AM
Rooting Onyx Boox Leaf 3C	bigwigs	Onyx Boox	5	04-25-2024 05:52 PM
Rooting Onyx Boox Note Air	afainber	Onyx Boox	8	01-04-2021 10:03 AM
Onyx Boox Note 2.0.1 Prerooted System Image	lvlrdka22	Onyx Boox	7	06-29-2020 09:35 AM
Rooting: Onyx Boox Note Pro - Build 2019-06-12	hansipansi65	Onyx Boox	12	01-25-2020 02:52 AM

09-12-2025, 11:25 PM	#2
Renate Onyx-maniac Posts: 4,058 Karma: 18027877 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Are you using the latest version of Magisk? Where is the log? Where is your boot image?

Yesterday, 09:39 AM	#4
Renate Onyx-maniac Posts: 4,058 Karma: 18027877 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Oh, well if the only point of your post is to canvas people and not necessarily get this problem fixed... No, I don't have this problem.

Yesterday, 12:28 PM	#5
SuiVu1fa Member Posts: 22 Karma: 10 Join Date: Nov 2018 Device: Kindle	I do not see any way to report bug to Onyx Boox system (I think that it is an issue on their side, not on Magisk — this is reproducible on APatch as well, and it is a new issue after upgrading to this version of system), so I could only ask whether people are encountering similar issues to understand what to do next.