Magisk 20.1 fails to boot

[ghost]

I'm not sure what kind of logs would be helpful, so if I'm missing any information please tell me and I'll kindly provide anything.

I've got Xiaomi Mi A2 Lite with it's stock ROM on Pie, October security update. Previously I had a somewhat older security update, but still Pie OS. I wanted to upgrade magisk, which I did. The phone went into bootloop. After reflashing the latest (mentinoned above) ROM I tried to manually patch the boot.img and then fastboot boot on it. The phone is now stuck at the loading screen (not rebooting, just stuck). Rebooting to my original boot img (I mean the installed ROM) works perfectly, which means I can't root my device.

I can't even patch the boot.img with the "old" 20.0, because the manager doesn't offer it.

Here is the patched img file: magisk_patched2.zip And here is the original boot img: boot.zip

[jasonsyoung]

Do you have any modules installed? If so, have you tried booting with a modified version of the magisk image that doesn't load modules as a method to test?

[ghost]

At the beginning after upgrade I ran into a bootloop, which I couldn't quickly solve, so I COMPLETELY reflashed my ROM. I know, there could be better solution, but nevermind that.

So, now my ROM is clean, no modules, nothing root-related is installed. I took the clean boot.img, let magisk patch it with the 20.1 and then hotbooted on the patched boot.img (because there is no good TWRP for my phone).

So, currently hotbooting into a patched boot.img fails.

[osm0sis]

Have you tried with the latest Canary? Worth a try.

[ghost]

I've just tried it right now, it's been trying to boot for more than 5min and still nothing happened.

Canary patched image: magisk_patched.zip

[osm0sis]

I don't immediately see anything structurally "wrong" with the image... Do you have a magisk_patched.img from the previous Magisk version that worked for you?

[ghost]

Sadly nope, but if you can tell me how can I try to patch an older, for example 20.0 version on the boot.img I can try to check if that works. I haven't seen such possiblity in magisk manager.

[osm0sis]

@Unc3nZureD, go to Manager Settings and choose Custom Channel, and set it to: https://github.com/topjohnwu/magisk_files/raw/3dec54c8a850660e3420f7668c7fb6dc8f7c199b/stable.json (the last commit where 19.3 was stable).

That should let you use the older Magisk zip to patch a file.

[redymedan]

How to get the custom update link? it really usefull. I can not find it, let me know to find the update link on this magisk section, thank you

[osm0sis]

Just follow the commit history to the tree at that time and link to the raw json like I did.

[redymedan]

Thank you, but I found like this https://github.com/topjohnwu/magisk_files/blob/a03d879d3512e2c0d49ca68b43344c9323dc8a4f/stable.json is it true?

[osm0sis]

Nope. You need the raw link. Compare to mine.

[redymedan]

I get it https://github.com/topjohnwu/magisk_files/raw/a03d879d3512e2c0d49ca68b43344c9323dc8a4f/stable.json Thanks You

[ghost]

@Unc3nZureD, go to Manager Settings and choose Custom Channel, and set it to: https://github.com/topjohnwu/magisk_files/raw/3dec54c8a850660e3420f7668c7fb6dc8f7c199b/stable.json (the last commit where 19.3 was stable).

That should let you use the older Magisk zip to patch a file.

Thank you for the suggestion!

It looks like I've got multiple issues. If I recall right, when it was last working I had pie with some old security update with magisk 20.0. I can't remember the exact version. Upgrading to 20.1 corrupted something and afterwards OS failed to load (infinite loading, not restarting).

I don't have any backup of that state/ROM. Now I've reflashed the WHOLE OFFICIAL ROM and running on the latest a2 lite update, which is october/pie. I have tried to fastboot boot on patched boot.img with all of the following versions: 19.3 (which you linked), 20.0 and of course the 20.1 - all of them are failing to load, producing the same issue as I described before.

I don't know how could I provide more info (logs?)

[osm0sis]

Not sure. You said it used to work, but now it doesn't, so I'm out it ideas for now. We'll need to wait for @topjohnwu to find time to take a look here.

[fr0zenrain]

Maybe this is another issue. v20.1 possible not work for pixel 2. i just test minutes before. when Magisk installed complete. i reboot to system. i can adb shell into system.but it seems the launcher not start. i haven't save much log. At last i roll back to Magisk v18.1 , it's work for me,i hope it's useful to fix bug. thanks.

i choose some log, which i think it's important

11-14 15:08:31.963 602 2167 I SurfaceFlinger: Boot is finished (126520 ms) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.display 11-14 15:08:31.966 4467 4491 E AndroidRuntime: java.lang.RuntimeException: Unable to connect to zygote for abi: armeabi-v7a 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.ZygoteProcess.establishZygoteConnectionForAbi(ZygoteProcess.java:465) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.am.ActivityManagerService.finishBooting(ActivityManagerService.java:8015) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.am.ActivityManagerService.bootAnimationComplete(ActivityManagerService.java:8116) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.wm.WindowManagerService.performEnableScreen(WindowManagerService.java:3476) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.wm.WindowManagerService.access$1100(WindowManagerService.java:272) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.wm.WindowManagerService$H.handleMessage(WindowManagerService.java:4807) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: Caused by: android.os.ZygoteStartFailedEx: Error connecting to secondary zygote 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.ZygoteProcess.openZygoteSocketIfNeeded(ZygoteProcess.java:584) 11-14 15:08:31.966 4467 4491 E AndroidRuntime: at android.os.ZygoteProcess.establishZygoteConnectionForAbi(ZygoteProcess.java:462)

[lindaiyu99]

same issues on nexus 7(2013)

[shakalaca]

@fr0zenrain Did you install Edge Sense Plus ?

[fr0zenrain]

@fr0zenrain Did you install Edge Sense Plus ?

I'm not sure, but I think No. I just take it from other fellow.This pixel2 just flashed Android 9.0 stock image for App development test.

[lightspot21]

Same issue on Redmi Note 4 (mido), November 5 security update on LineageOS 16 nightly (21/11/19). Tested both with canary 20107 (20.2-474cc7d5) and stable (20.1). Phone gets stuck in a bootloop after trying to reflash the zip when upgrading (dirty) from 15.1 to 16.

dmesg: https://pastebin.com/34a1WGnc

[Humaxx]

Today on S3Neo (GT-I9301I) Magisk 20.1 fail to boot with LOS16.0 Nightly from 24.11.2019. With older builds it was working correct.

[Humaxx]

With Build from 25.11.2019 ist again normal booting. Maybe 24.11.2019 was corrupt

[osm0sis]

Stop hijacking this issue thread with your clearly unrelated booting issues.

And @fr0zenrain, edit your post to remove that log and instead upload it in a .log file; you've made this issue painful to read on mobile.

[osm0sis]

@Unc3nZureD try with this image I made out of your last uploaded Canary magisk_patched.img. image-new.img.zip

[topjohnwu]

This thread is going nowhere, closed

[SoftwareSchlosser]

I have the same issue with 20.4 on my Xiaomi Mi A2 (non-lite). After uninstalling magisk and applying the latest OTA, the phone boots the stock bootloader as expected. Now I fastbooted into TWRP and extracted and copied both boot images. I'm on slot b - so back in Android I patched the corresponding boot image via magisk manager and tried to fastboot it. The colored line starts to move which means the boot process itself works but it runs like that forever. I also tried to fastboot the extracted unpatched image which also works so there must be something wrong with the patched image.

stock boot image patched boot image

Do you have any ideas on that?

[osm0sis]

Open a new issue for 20.4 instead of posting in an old, closed one for 20.1. 🙄