search

topjohnwu / Magisk

The Magic Mask for Android
GNU General Public License v3.0
47.2k stars 11.94k forks source link

magisk does not open after One Ui 6 update #7887

Open Insomnya96 opened 6 months ago

Insomnya96 commented 6 months ago

Device: Samsung Galaxy M53 5G Android version: Android 14 Magisk version name: 27.0 Magisk version code: 27001

After the One Ui 6 update, magisk simply does not open after being routed, it remains frozen on the magisk mask screen infinitely.

installation method: I take the boot.img, use magisk to patch it, put it in .tar and pass it via odin

note: before installing the patched image, magisk opens normally, the problem occurs after it starts the first time after installing the patched image

Logs: logcat.log

anurag565 commented 6 months ago

I have same issue. Magisk wont open only after installing patched image.

NattanBR1 commented 5 months ago

Tenho o mesmo problema preciso de ajuda help pls

sumeet4evr commented 4 months ago

Hi Dev, it remains frozen on the magisk mask screen infinitely. Samsung F235g oneui6 with march security update, tried beta version as well. It works for sometime after reboot than freezes.

asdasd755 commented 2 months ago

לי גם נשאר תקוע מה עושים?

r3pek commented 1 month ago

Same here on a A13 5G. Just for context, this is what logcat shows on boot:

08-05 23:52:55.732   878   878 I Magisk  : Magisk 27.0(27000) daemon started
08-05 23:52:55.733   878   878 I Magisk  : * Device API level: 34
08-05 23:52:55.743   878   880 I Magisk  : ** post-fs-data mode running
08-05 23:52:55.749   878   880 E Magisk  : unlock mmcblk0p16 failed with 13: Permission denied
08-05 23:52:55.750   878   880 E Magisk  : unlock mmcblk0p18 failed with 13: Permission denied
08-05 23:52:55.751   878   880 E Magisk  : unlock mmcblk0p13 failed with 13: Permission denied
08-05 23:52:55.751   878   880 E Magisk  : unlock mmcblk0p15 failed with 13: Permission denied
08-05 23:52:55.752   878   880 E Magisk  : unlock mmcblk0p11 failed with 13: Permission denied
08-05 23:52:55.753   878   880 E Magisk  : unlock mmcblk0boot0 failed with 13: Permission denied
08-05 23:52:55.754   878   880 E Magisk  : unlock mmcblk0p10 failed with 13: Permission denied
08-05 23:52:55.754   878   880 E Magisk  : unlock mmcblk0p9 failed with 13: Permission denied
08-05 23:52:55.754   878   880 E Magisk  : unlock mmcblk0p12 failed with 13: Permission denied
08-05 23:52:55.754   878   880 E Magisk  : unlock mmcblk0p20 failed with 13: Permission denied
08-05 23:52:55.755   878   880 E Magisk  : unlock mmcblk0p22 failed with 13: Permission denied
08-05 23:52:55.759   878   880 E Magisk  : unlock mmcblk0 failed with 13: Permission denied
08-05 23:52:55.764   878   880 E Magisk  : unlock mmcblk0p8 failed with 13: Permission denied
08-05 23:52:55.765   878   880 E Magisk  : unlock mmcblk0p45 failed with 13: Permission denied
08-05 23:52:55.765   878   880 E Magisk  : unlock mmcblk0p19 failed with 13: Permission denied
08-05 23:52:55.769   878   880 E Magisk  : unlock mmcblk0p14 failed with 13: Permission denied
08-05 23:52:55.770   878   880 E Magisk  : unlock mmcblk0p21 failed with 13: Permission denied
08-05 23:52:55.770   878   880 E Magisk  : unlock mmcblk0p17 failed with 13: Permission denied
08-05 23:52:55.772   878   880 I Magisk  : * Mounting mirrors
08-05 23:52:55.825   878   880 I Magisk  : * Initializing Magisk environment
08-05 23:52:55.826   878   880 E Magisk  : * Magisk environment incomplete, abort
08-05 23:52:55.826   878   880 I Magisk  : * Loading modules
08-05 23:52:57.444   878   880 I Magisk  : ** late_start service mode running
08-05 23:52:57.444   878   880 I Magisk  : * Running service.d scripts
08-05 23:52:57.444   878   880 I Magisk  : * Running module service scripts

EDIT: tried with 27006, and it just boot-loops sorry, made the patch using the wrong arch. It does start with 27006 but still fails to load up. The errors above don't show up anymore but this is what I got when trying to start the app:

08-06 10:36:09.164 16215 16215 W ziparchive: Unable to open '/system/app/mediatek-res/mediatek-res.apk': No such file or directory
08-06 10:36:09.164 16215 16215 E com.topjohnwu.magisk:root:0: Failed to open APK '/system/app/mediatek-res/mediatek-res.apk': I/O error
08-06 10:36:09.164 16215 16215 E IPC     : Error in IPCMain
08-06 10:36:09.164 16215 16215 E IPC     : java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
08-06 10:36:09.164 16215 16215 E IPC     :      at com.topjohnwu.superuser.internal.RootServerMain.<init>(SourceFile:0)
08-06 10:36:09.164 16215 16215 E IPC     :      at com.topjohnwu.superuser.internal.RootServerMain.main(Unknown Source:23)
08-06 10:36:09.164 16215 16215 E IPC     :      at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
08-06 10:36:09.164 16215 16215 E IPC     :      at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:385)
08-06 10:36:09.164 16215 16215 E IPC     : Caused by: java.lang.reflect.InvocationTargetException
08-06 10:36:09.164 16215 16215 E IPC     :      at java.lang.reflect.Method.invoke(Native Method)
08-06 10:36:09.164 16215 16215 E IPC     :      ... 4 more
08-06 10:36:09.164 16215 16215 E IPC     : Caused by: java.lang.IllegalStateException: Failed to create system AssetManager
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.AssetManager.createSystemAssetsInZygoteLocked(AssetManager.java:291)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.AssetManager.getSystem(AssetManager.java:303)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.Resources.<init>(Resources.java:405)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.Resources.getSystem(Resources.java:288)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.app.ActivityManager.isHighEndGfx(ActivityManager.java:1639)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.view.ThreadedRenderer.initForSystemProcess(ThreadedRenderer.java:226)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.app.ActivityThread.systemMain(ActivityThread.java:8652)
08-06 10:36:09.164 16215 16215 E IPC     :      ... 5 more
08-06 10:36:09.164 16215 16215 E IPC     : Caused by: java.io.IOException: Failed to load asset path /system/app/mediatek-res/mediatek-res.apk
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.ApkAssets.nativeLoad(Native Method)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.ApkAssets.<init>(ApkAssets.java:298)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:147)
08-06 10:36:09.164 16215 16215 E IPC     :      at android.content.res.AssetManager.createSystemAssetsInZygoteLocked(AssetManager.java:282)
08-06 10:36:09.164 16215 16215 E IPC     :      ... 11 more
08-06 10:36:09.165 16215 16215 I com.topjohnwu.magisk:root:0: System.exit called, status: 1

EDIT2: Also, su is not accessible.

a13x:/ $ ls /system/bin/sh -lh                                                                                                                             
-rwxr-xr-x 1 root shell 211K 2008-12-31 15:00 /system/bin/sh
a13x:/ $ su                                                                                                                                                
/system/bin/sh: su: inaccessible or not found
ElsAr4e commented 1 month ago

It would be great if you can also test versions like One UI 6.1.1.

r3pek commented 1 month ago

It would be great if you can also test versions like One UI 6.1.1.

I only have 6.1. Don't think there's an EU version for 6.1.1... :thinking:

r3pek commented 3 weeks ago

just to report that the problem persists on 27007

anurag565 commented 2 weeks ago

Yeah and for some reason, no one is doing anything. Its been issue for 6 months.

vvb2060 commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

vvb2060 commented 2 weeks ago

/system/app/mediatek-res/mediatek-res.apk I want to know why this file cannot open by root process

anurag565 commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

How to do /debug_ramdisk/su ?

anurag565 commented 2 weeks ago

/system/app/mediatek-res/mediatek-res.apk I want to know why this file cannot open by root process

I dont have that app.

r3pek commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

This one works.

anurag565 commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

This one works.

How to do that buddy, please tell me.

r3pek commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

This one works.

How to do that buddy, please tell me.

It doesn't make the app work, but at least you get root. Just open an adb shell terminal and type /debug_ramdisk/su

G2Split commented 2 weeks ago

Hi. I've also been facing the same problem. My case is LITERALLY the same as yours, including the phone model. I have an M536B, and after updating to Android 14, I started experiencing exactly the same issue. It's funny that before the system update, on Android 13, everything worked perfectly, the problem only appeared after the software update. I have no idea why this is happening.

anurag565 commented 2 weeks ago

Safe mode is triggered, try /debug_ramdisk/su to get root shell

This one works.

How to do that buddy, please tell me.

It doesn't make the app work, but at least you get root. Just open an adb shell terminal and type /debug_ramdisk/su

I have root access on most of apps. I wanted app to work.

itztusharb commented 1 week ago

@topjohnwu @yujincheng08 Please fix magisk for one ui 6.1 users as we're having this problem a lot. We need root & the magisk modules for some important uses and now it's not working. Thanks