Closed martyfender closed 3 years ago
any log for launching Magisk app ?
In not sure about x86, but, the issue you mentioned previously happened on arm64-v8a devices, but, this was fixed about 2-3 updates ago...
any log for launching Magisk app ? logcat.txt
Is this what you mean? This is an adb logcat where I launched the magisk app then closed it.
any log for launching Magisk app ? logcat.txt
Is this what you mean? This is an adb logcat where I launched the magisk app then closed it.
yeap, but I didn't see the log of su handler. Can you show me the result of pm dump com.topjohnwu.magisk|grep CpuAbi
?
any log for launching Magisk app ? logcat.txt
Is this what you mean? This is an adb logcat where I launched the magisk app then closed it.
yeap, but I didn't see the log of su handler. Can you show me the result of
pm dump com.topjohnwu.magisk|grep CpuAbi
?
127|shell@NX16A8116K:/ $ pm dump com.topjohnwu.magisk|grep CpuAbi primaryCpuAbi=x86 secondaryCpuAbi=null shell@NX16A8116K:/ $
The kernel on this device is considered x86_64, a 32 bit device.
Here is that dump for my Onn 8, Android 9 devices where magisk works perfectly:
primaryCpuAbi=arm64-v8a
secondaryCpuAbi=armeabi-v7a
#
su
from adb shell ?su
, what's the output of command busybox
?1. can you execute `su` from adb shell ? 2. if you can run `su`, what's the output of command `busybox` ?
no I can't get adb root, I had already tried this many times:
C:\adb>adb shell shell@NX16A8116K:/ $ su shell@NX16A8116K:/ $ busybox /system/bin/sh: busybox: not found 127|shell@NX16A8116K:/ $
If I revert back to my saved 22001 patched boot.img, adb root works fine.
Would it be useful to upload the patched 22001 boot.img that works and the 22006 patched boot.img?
Thanks
I'm looking forward to a new build to test.
Thanks
Thanks everyone for fixing this issue. I will now close it.
Device: nextbook ares 8a intel x86 Android version:6.0.1 Magisk version name: canary 22006 Magisk version code: 22006
I save the patched boot.img from 22001 and it works fine. All newer versions show magisk as installed as na. Attached is a twrp recovery log, but the only magisk seen in twrp file manager is from 22001, so it appears that no new magisk log is being created after flashing and rebooting the system. recovery.log boot.zip
I also tried direct install and flashing suceeds but upon roboot no root is installed, in magisk manager it also shows installed N/A.
Attached is the magisk.log saved in mm from the working canary 22001, if that may be useful. magisk_log_2021-03-25T19:15:34Z.log
UPDATE: attached is a boot logcat after flashing 22006. bootlogcat.txt
All of the previous versions since 22001 work fine on my 2, Onn 8, Android 9 devices, using the patched boot.img method and flashing in TWRP. Thanks