• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Android 11 is here!

Search This thread

Nezorflame

Senior Member
Sep 7, 2009
934
2,644
Moscow
nezorfla.me
Google Nexus 5
OnePlus 3
I suggest everyone here to try sideloading Magisk v20.4 (I personally used Lineage recovery for this).
Only this version worked for me, all newer releases didn't causing the bootloop.

EDIT: it seems that while the device booted, Magisk is not detected by the Manager as installed. So, we're back at square one.
 
Last edited:

niaboc79

Recognized Developer / Inactive RT
Sep 8, 2007
12,444
68,206
Enghien
www.nirvana-records.be
I suggest everyone here to try sideloading Magisk v20.4 (I personally used Lineage recovery for this).
Only this version worked for me, all newer releases didn't causing the bootloop.

EDIT: it seems that while the device booted, Magisk is not detected by the Manager as installed. So, we're back at square one.

But it's a good information, that means that a modded kernel can be booted.

Maybe other needed parts are not installed at all by the recovery.
 

xda177

New member
May 31, 2021
3
0
I do as https://github.com/topjohnwu/Magisk/issues/3752 said,
1. Patch 58.1.A.5.159 boot.img with magisk
2. use Image Kitchen and unpack boot.img
3. Locate fstab.qcom and edit with notepad++ remove the system_ext line and save
4. Repack and flash the new .img ,fastboot flash boot_a & boot_b boot.img

but there is also a bootloop ... so is there any solution to this issue?
 

Top Liked Posts