-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magisk does not work on PineNote #5125
Comments
this is expected, and Magisk can handle this case properly.
|
Thanks. What is the first wrong line in the log? Should pGl3f9lRb not exit
or is the issue that its children are killed? The killing of children
behaviour exists since 2019, so that should not be the issue?
残页 ***@***.***> schrieb am Mo. 27. Dez. 2021 um 01:58:
… userdata partition is in f2fs format
this is expected, and Magisk can handle this case properly.
You problem is, magiskd gets killed by init:
[ 5.655935] init: starting service 'pGl3f9lRb'...
[ 6.300117] init: wait for '/dev/.magisk_unblock' took 641ms
[ 6.300224] init: Command 'wait /dev/.magisk_unblock 40' action=post-fs-data (/system/etc/init/hw/init.rc:1111) took 641ms and succeeded
[ 6.300361] init: Service 'pGl3f9lRb' (pid 201) exited with status 0 oneshot service took 0.643000 seconds in background
[ 6.300403] init: Sending signal 9 to service 'pGl3f9lRb' (pid 201) process group...
[ 6.306288] libprocessgroup: Successfully killed process cgroup uid 0 pid 201 in 5ms
[ 6.306588] init: Killed 1 additional processes from a oneshot process group for service 'pGl3f9lRb'. This is new behavior, previously child processes would not be killed in this case.
—
Reply to this email directly, view it on GitHub
<#5125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOY6TVAEBZOC5JGG5R34TLUS6237ANCNFSM5KZKXAEA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
magiskd should escape from current cgroup to prevent itself from being killed. May you upload |
Here is /proc/mounts Just for fun, I also tried Magisk 22 and 22.1, both of which did work even less because they did not even install the su file and took significantly longer to even boot. Log file: |
looks like a normal cgroup v2 mount structure... please test this build: https://github.com/canyie/Magisk/actions/runs/1627522914 EDIT: Download link updated since github action broken. |
Thanks a lot, this seems to work now! |
Fix #5125 cgroup root path might be mem cgroup instead of acct, especially on low-ram devices. https://android.googlesource.com/platform/system/core/+/bc131c3244a6aa4961092ba08285f9d0435a8882%5E%21/#F0
I'm trying to root the PineNote, which I am aware is an odd device.
I use the method of patching the boot.img
Install log:
magisk_install_log_2021-12-26T21_27_19Z.log
The Magisk app does not detect the installed magisk.
Running
su
ormagisk --daemon
both result in the outputNo daemon is currently running!
.Boot log from UART:
boot.log
Below are the parts that seemed relevant to me.
Regarding,
[ 2.666118] EXT4-fs (mmcblk2p16): VFS: Can't find ext4 filesystem
, I think the userdata partition is in f2fs format.Device: PineNote
Android version: 11
Magisk version name: 92546e8
Magisk version code: 23016
The text was updated successfully, but these errors were encountered: