Database Info

Magisk v16 bootloop

Hi all,
Just tried to flash the latest Magisk (16.0) from TWRP on my honor 8 running B360 and am now in a a bootloop.. Nothing new fixing this but does anyone know what version of magisk will work or why this could have happened? I'm keen to get it working!
Cheers

So I've tried to flash back to an unrooted rom and must've broken something because I now cannot get into TWRP at all. I fastboot flash version 3.1.1-1 which has worked for me countless times and fastboot says it flashes fine but when I try and boot into it with power+vol up the phone goes off for a second, vibrates, pauses for another second before vibrating again and then showing the device cannot be trusted screen. Has anyone ever had this? I'm not sure what else to try here (I also tried flash stock recovery and it does the same thing)
Edit: Got TWRP back, I think my device must be on an earlier version (even though it's corrupt). In case anyone else finds this, this thread helped me https://forum.xda-developers.com/honor-8/help/please-help-boot-enter-recovery-t3660408/page3

First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.

Mumtaz77 said:
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Click to expand...
Click to collapse
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!

JoshSnitz said:
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
Click to expand...
Click to collapse
Unfortunately it didn't work - resulted in the bootloop again

Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?

xuso77 said:
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
Click to expand...
Click to collapse
Yeah, using twrp-3.1.1-1-frd.img. Phone is EMUI 5.0, android 7.0 FRD-L09C432B360
Edit: I have the AL version with dual sim that I've re-branded. Could this be causing an issue?

I don't think so, but I don't know.
Can you try to flash the last magisk developer version, or wait for another user that rebranded the honor.
Good luck!

You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.

hackslash said:
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
Click to expand...
Click to collapse
Oh, I'll give it a go. Is it more reliable to just flash through fastboot or the zip through twrp?
Edit: Both v14 and 13 gives boot loop when flashed from twrp

Bootloop to TWRP on PIE

Hi, the title says almost all... I can't get past the TWRP screen on both official TWRP and Bluespark one, only solution is flashing Magisk but i have to remove it in order to use some Apps that detect it, any advice...?

Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?

whizeguy said:
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
Click to expand...
Click to collapse
I need twrp so I can flash magisk if I need it.
And yes, tried to use latest versions of Magisk and, obviously, the Uninstaller, every time I run the Uninstaller it just boot back to twrp.
Anyway I've solved by dirty flashing Pie, now it's working, thanks

Can't root after full 9.0.4 installation

I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?

Solanoantuna said:
I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?
Click to expand...
Click to collapse
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.

PeterSmusi said:
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.
Click to expand...
Click to collapse
My apologies for the late reply. I'm not heavily into these things so I was reluctant to go into TWRP. So I ended up resetting my phone and now it all roots quite happily. But thanks for the ideas.

hii i have one plus 6 oxygen 9.0.6 but am not able to find out patched file
image

Deleted

May security update is out

https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."

i did clean install of the recovery image this morning. all seems fine. nothing visually different

Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.

Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.

sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.

208.9mb too! Quite large for just a small incremental update too!

considering locking my BL and clean wiping...
google pay no longer works and its fustrating.

virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.

Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.

Aren't you supposed to boot system before flashing magisk?

Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.

since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs

Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.

Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?

virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse

Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.

Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.

Anyone try to sideload the OTA? I believe the file is too big to sideload?

lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.

Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.

Magisk Bootloop OOS 10

Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!

ImperatorShade said:
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
Click to expand...
Click to collapse
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).

strongst said:
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
Click to expand...
Click to collapse
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!

ImperatorShade said:
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
Click to expand...
Click to collapse
Maybe you did have any magisk modules left?
Have you tried an older magisk version?

strongst said:
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
Click to expand...
Click to collapse
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.

ImperatorShade said:
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
Click to expand...
Click to collapse
And are there any magisk modules or mods left? It can be the reason for this.
Are there any errors within the log while flashing?
You have the twrp guacamole unified from mauronofrio 3.3.1-70, right? You can try 3.3.1-73 if you want.

There were no errors when flashing. But I'm not sure whether I had disabled Magisk Modules before flashing OxygenOS 10. Anyway, what would be the best way to untwrp and clean flash?