Database Develop

Magisk Boot Loop Nexus 6P

Just upgraded magisk to 11 this morning from inside the app and it has been stuck rebooting the past ten minutes. Can anyone help?

can still get into Twrp though if that helps figure out solutions.

I have similar problem, on a OnePlus 3 with a CM13 based Rom.
After the update from 10.2 to 11 the start of Android never finished.
Temporary solution (until I have more time to produce a real bug report or someone else finds the problem) uninstalled Magisk via Uninstaller zip in TWRP and reinstalled Magisk 10.2 there.

Same problem for me on Pure Nexus when installing v11. Stuck on boot screen.

Had to flash Magisk Uninstaller, and re-flash Magisk 11 through TWRP. Seems to work, until I installed ViperFX (through Magisk) and it asked me to reboot - now I'm back in a boot loop.
Going to roll back to Magisk 10.2 until something gets fixed.

Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.

Okay, so I finally got it to boot doing the following:
1) Factory Reset
3) Format System
2) Reflash Rom, GApps
3) Boot into Rom
4) Reboot, flash Magisk
5) Boot back into Rom
I think the issue is if you are coming from 10.2 (or earlier) you need to remove SU before flashing magisk. Magisk has SU built in (though should work with SuperSU or phh's for now) but I think there is some issue when upgrading. Maybe try flashing your preferred SU package after you reboot into the rom after Magisk is installed.
---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------
Didgeridoohan said:
Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.
Click to expand...
Click to collapse
Hehe, well, I only just found out about that before I nuked my phone.

OK for me the boot problem was fixed by restoring the boot partition from a backup without Magisk installed and the flashing version 11.
So the problem is mostly cased by something in the boot partition.
If you don't have a backup of the boot partition. Flashing the boot image of the ROM or the hole ROM should fix this.
At lest for me no need to reset everything.

Did a full unroot of supersu, told it to restore the backed up boot image, booted immediately into recovery, flashed magisk and magisksu stuck no problem. I like this all in one solution v11 brings.

It's viper4android now causing the bootloop... I flashed clean with magisk 11.1

lutanica said:
It's viper4android now causing the bootloop... I flashed clean with magisk 11.1
Click to expand...
Click to collapse
agreed. this seems to be unresolved right?

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
Still unresolved yes..

I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
Click to expand...
Click to collapse
And you've Viper4android installed and it's functioning?

I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.

denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Click to expand...
Click to collapse
Verified working with an extra step: after you reboot, remove SuperSU if you have it (app drawer, drag to uninstall). This seems to default the SU method to the MagiskSU, which allows it to pass safety net as well. Before I uninstalled SuperSU, I was getting safetynet fail CTS mismatches.
Also, after doing the quoted method, it did take a little longer than usual booting, give it 5 min at least.
Lastly, Viper4Arise doesn't work (driver won't load), probably because of something related to the new magisk, or because it preferred SuperSU.
Thanks

2hdq said:
I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.
Click to expand...
Click to collapse
Firstly unroot the SuperSU, flash the latest Magisk zip file v11.1. You don't need the suhide as the latest version of Magisk already has the necessary files to root your device. Hope this helped you

At the risk of sounding dumb, I couldn't figure out how to decrypt my data partition. I don't know if what I did made any actual difference but I did a nandroid of my data, rebooted twrp, restored data, entered the adb command, then installed magisk. Reboot to system, all set!
Hope this helps someone out.
Sent from my Nexus 6P using Tapatalk

I'm getting a constant boot loop (stuck at boot animation) each time I try to install magisk on my Oneplus 3. with OOS 4.0, it worked fine on MM but no go since updating to nougat.
Edit:Fixed it! I hadn't ran the uninstaller first. Once I did this it worked fine. Doh!

Hi on my lg g5 (with fulmics custom rom Android 7.0) magisk 11.1 crashes settings app, any solutions? I could revert back to 10.2?

Bootloop after magisk update

This morning, waking up I recieved the notification that a new magisk manager is available. I installed it as usual, except this time my device suddenly was not rooted anymore.
Si I press the install magisk button that pops up, it flashes magisk, and BAM. Phone restarts, and boot loop.
The phone's a OP5, android 7.1.1, and I had to do a factory reset twice before it would boot. Even using the magisk uninstaller did yield no results.
How come the phone suddenly got unrooted? Can I safely root it again now? Why wouldn't the first factory reset get it out of boot loop?
How can I prevent data loss in the future? Help?
Update 1 - Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Update 2 - TimMayle managed to run the uninstaller and re-flashing magisk v17 on TWRP, try this if you have the issue. (While the uninstaller wouldn't work for me, that might be a device specific issue.)
TimMayle said:
Hello,
I was on Magisk 16 and probably Manager 5.8.3.
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Click to expand...
Click to collapse
Update 3 - Thanks void74 for another potential procedure that might fix your issues.
void74 said:
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
I hope I have saved some lives.
Click to expand...
Click to collapse
Update 4 - Thank you Shampinger for giving ups a Linux-specific variation on the steps to follow.
Shampinger said:
Same issue here on Redmi Note 5 global (whyred). Thanks to this thread I could fix it.
Steps (on Linux):
1. boot into fastboot (vol down + power)
2. from folder with your twrp zip run:
Code:
sudo fastboot boot twrp-x.x.x-x-whyred.img
there might be an easier way to boot into recovery without having to use the zip on your computer that I don't know about
3. copy Magisk uninstaller and Magisk v17 to phone (if not already there)
4. flash uninstaller zip
5. go back and flash Magisk v17 zip
6. reboot
Click to expand...
Click to collapse
Update 5 - While a fixed version is being perfected, Mangraviti summed up what you should do:
Mangraviti said:
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
Click to expand...
Click to collapse
Update 6 - If you have Wi-Fi issues after update v17, you can attempt what TAJ_Rocks has found out:
TAJ_Rocks said:
Found fix for dead wifi
Delete this p2p supplicant.conf supplicant made wifi a c#nt:laugh:
Reboot after deleting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

+1.
Exactly the same issue. The phone lost root and is now stuck in bootloop. How to recover? Any hopes of saving the data?
Please throw some light....

Same issue here... bootloop after update. I wish I didn't update.
Oreo 8 on Huawei Nexus 6p.

Same here on HTC U11 with Lineage 15.1
Feels bad man.
How do I fix?

I fixed bootloop by uninstalling magisk with magisk uninstaller. After that I installed v16

Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?

Same here (bootloop) after update from 16 to 17. I used unnistaller but ended in fastboot after reboot :laugh:
Had to install rom and v17 to work.
Redmi Note 5 Pro MIUI 9.6.4.0 Global

Same thing on s7 with Android 7.0 , now I'm resetting the device.

Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)

Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?

ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.

Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Hello,
I was on Magisk 16 and probably Manager 5.8.3. (Xperia Z3C on OmniRom).
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim

Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Yes. That's exactly what I did. OK. So I now ran magisk uninstaller, booted fine. Then installed clean v17.0 and it works now - no bootloop. Many thanks!

I am having the same problem with magisk manager 5.8.3 + v16 zip. After upgrading to v5.9.0(138) all my previous setting all gone. Plus i can install v17 zip at all.
This is on HTC U11+ with android v8.0

Same for me had bootloop on android 7.1.2 i was on magisk 16.0 stable. I got notification before an hour. I upadted the apk and it showed magisk not installed. So i downloaded the zip and flashed 17.0 stable zip and had bootloop. So i just cleaned cache and dalvik now phone is started and root and magsik working. But now wifi is unable to switch on

Also got a bootloop on my Samsung Galaxy S4 jfltexx running Resurrection Remix v5.8.5 (Android 7.1.2). Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.

ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
I'm in the same situation with a s6. After another device (s7) has a bootloop I don't think that i flash the v17 from the manager

gkmac said:
Also got a bootloop on my Samsung Galaxy S4 jfltexx. Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In "Downloads" you have "Latest uninstaller" go to recovery and flash the zip, that should uninstall magisk.

Dacraun said:
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Click to expand...
Click to collapse
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...

ZioArturone said:
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
Click to expand...
Click to collapse
Check the first post, I quoted someone flashing the uninstaller and flashing v17 again and it worked. Maybe that'll work for you?
I do suggest doing a total backup in twrp first though. Just in case.

Everything Stock + root with OTA updates?

There were some years since i rooted my last phone, all is quite different now and magisk is new to me.
So, tomorrow i'll receive my 9T PRO and i wanted to know if its possible to just root it with magisk and keep using stock recovery and installing OTA updates without having to re-stock the phone to update and reroot again.
If so, is there any guide? I didn't find any.
Thanks a lot!

Firstly you will have to wait 7 days before you can unlock the bootloader because Xiaomi dont let you do it right away you need to be logged into the phone with your mi account and use it actively for about 168 hours before you can unlock it. I believe you can boot twrp instead of installing it and flash magisk to root and still be able to receive ota updates but be sure to only boot and not install it.

Ok then, i'll wait and try it out. Thanks a lot!

good luck you should be fine.

sam00561 said:
good luck you should be fine.
Click to expand...
Click to collapse
i have the same question..now im running MIUI 10.3.1.0 PFKMIXM Mi 9T PRO original from box + rooted..i got older device which is pocophone f1..now my mi 9t pro have new update which is 10.3.2.0..last time on pocophone everytime i flash newest MIUI via twrp..i need to reflash the twrp.img because updating MIUI will replace your twrp to stock recovery..my question is..am i going to lost twrp on mi 9t pro too iff i do the update?does this aply the same like pocophone?sorry bad english..

Yes if you take any official update you will usually lose the recovery and stock recovery will be installed.

sam00561 said:
Yes if you take any official update you will usually lose the recovery and stock recovery will be installed.
Click to expand...
Click to collapse
are u using mi9t pro/k20pro or you just good at operating system?

I'm using mi9t Pro in the UK.

Orangefox recovery has the ability in its settings to let you install OTA updates like normal.

strunx said:
Ok then, i'll wait and try it out. Thanks a lot!
Click to expand...
Click to collapse
its worked for you or not ?
booting from TWRP without flashing it

xNovaLeader said:
i have the same question..now im running MIUI 10.3.1.0 PFKMIXM Mi 9T PRO original from box + rooted..i got older device which is pocophone f1..now my mi 9t pro have new update which is 10.3.2.0..last time on pocophone everytime i flash newest MIUI via twrp..i need to reflash the twrp.img because updating MIUI will replace your twrp to stock recovery..my question is..am i going to lost twrp on mi 9t pro too iff i do the update?does this aply the same like pocophone?sorry bad english..
Click to expand...
Click to collapse
You can also read here ?
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post80318733

sam00561 said:
Yes if you take any official update you will usually lose the recovery and stock recovery will be installed.
Click to expand...
Click to collapse
Hi m8, I am in the same boat and want to avoid re-flashing everything when a new ROM/OTA comes out.
From what I understood, in order to get OTA and keep root, I will have to 'boot' via TWRP img and then flash magisk to get root which will then allow me to keep stock recovery/root even after OTA? Is there a step-by-step for this that you can link plz?
Also, does TWRP get auto erased after flashing magisk/reboot or do I have to follow some extra steps?
I just don't wanna go through the hassle of installing rom.
Thanks

If you boot to twrp rather than use the command fastboot flash twrp then when u reboot you will still have stock recovery because you only booted to twrp which will mean theoretically you can receive ota updates when they come out but i think after an ota update you wil have to flash magisk again in order to root. Hope it helps.

sam00561 said:
If you boot to twrp rather than use the command fastboot flash twrp then when u reboot you will still have stock recovery because you only booted to twrp which will mean theoretically you can receive ota updates when they come out but i think after an ota update you wil have to flash magisk again in order to root. Hope it helps.
Click to expand...
Click to collapse
I think I am going to use the method where I get a patched boot img via Magisk manager and flash it via fastboot. After that its just a matter of selecting the option to patch boot img after every OTA update.
Thanks again for your help

_ray_ said:
I think I am going to use the method where I get a patched boot img via Magisk manager and flash it via fastboot. After that its just a matter of selecting the option to patch boot img after every OTA update.
Thanks again for your help
Click to expand...
Click to collapse
I made the same thought.
I have already patched the boot file and rooted the ROM...
Everything works ok.
I would like to have stock AOSP feeling but they still have many bugs, so for now i am fine only rooting my phone.
Below i attach 2 screenshots from this forum showing the procedure for your info...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Fastboot devices
Sorry for the typo
Στάλθηκε από το Mi 9T Pro μου χρησιμοποιώντας Tapatalk

Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue

So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.

omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a

Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.

This is exactly what happened to me. I lost all my data trying to figure out what is going on. Now flashing Stock Root Oreo. Damn it.

BeardKing said:
Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.
Click to expand...
Click to collapse
You running arter97's kernel?

I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?

omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
...
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
slavomes said:
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a
Click to expand...
Click to collapse
totalnoob34 said:
I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?
Click to expand...
Click to collapse
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.

jdc said:
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.
Click to expand...
Click to collapse
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs

totalnoob34 said:
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG-H870 V30a

Let's try to figure out why things aren't working... If you're willing to help, take a look here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post81394545

slavomes said:
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.View attachment 4918541View attachment 4918543
LG-H870 V30a
Click to expand...
Click to collapse
It is easy. Just check the date and time files are created. Then identify the file that has a time stamp close to the time you updated Magisk to 20.2. That particular file is the right backup.

Confirm the problem. I own an Lg G3 D855 with the v30o. Fortunately i messed up things one day before trying to fix the fail of safetynet. A module caused my phone bootloop so i manually removed the module with the TWRP from the /data dir. So when i got the update 20.2 my phone had the same issue, my mind directly went to Magisk and installed the 20.1 via TWRP and everything's fine again.

I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.

Cloonix said:
I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.
Click to expand...
Click to collapse
G6 here, same issue. I dirty flashed my ROM and Magisk 19.3 and am back in business.
Nothing special about 19.3, it was just the version I happened to have a zip handy.

Latest magisk 20.3 canary (20202) working fine on lg g5 android 9 and 10.
Sent from my LG G5 using XDA Labs

20.3 and still the same issue. Reverted again to 20.1 (LG G3)

leopseft said:
20.3 and still the same issue. Reverted again to 20.1 (LG G3)
Click to expand...
Click to collapse
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.

Didgeridoohan said:
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.
Click to expand...
Click to collapse
It sure works on my G6

omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
how . pleas tell are we to flash a stock boot image when computer fastboot is not recognised by phone fastboot?
computer see's and id's phone. phone does not see computer.
fast boot is the onlything working on the phone. perioud.

Official TWRP for A12 ONEPLUS 7 PRO is now released.

Hello,
as I mentioned in the title, you can now download the official TWRP for the official website, and the most recent version supports encryption/decryption.
https://twrp.me/oneplus/oneplus7pro.html

Does it support 13? I'm running pixel experience.

fli2008 said:
Does it support 13? I'm running pixel experience.
Click to expand...
Click to collapse
they said A12 try it on A13 and see

I can't any more unlock the bl since A12. :/

khalisz said:
I can't any more unlock the bl since A12. :/
Click to expand...
Click to collapse
Yeah thats true, always unlocked it on A11 before flashing A12

yassine2217 said:
Hello,
as I mentioned in the title, you can now download the official TWRP for the official website, and the most recent version supports encryption/decryption.
https://twrp.me/oneplus/oneplus7pro.html
Click to expand...
Click to collapse
Did you manage to run this recovery on OOS A12? As experience shows, this version only works with OOS A11, on A12 I and many people get the "fastboot mod" logo in the center of the screen, without running TWRP.
By the way, here is the official theme of the TWRP developer on guacamole, on xda:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
He has a chat in Telegram, his unofficial recovery is published there.

Rein0ud said:
Did you manage to run this recovery on OOS A12? As experience shows, this version only works with OOS A11, on A12 I and many people get the "fastboot mod" logo in the center of the screen, without running TWRP.
By the way, here is the official theme of the TWRP developer on guacamole, on xda:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
He has a chat in Telegram, his unofficial recovery is published there.
Click to expand...
Click to collapse
I test it on my phone with elixir A12 work perfetcly and i made a nandroid also with no issue

yassine2217 said:
I test it on my phone with elixir A12 work perfetcly and i made a nandroid also with no issue
Click to expand...
Click to collapse
Yes, I know about support for custom ROMs, but they use FBEv2, OOS uses FEv1, as far as I can understand. Therefore, I am collecting information about the operation of TWRP 3.7 with OOS on A12 (because this version is declared to support OOS A12, but only works on OOS A11)
Thank you for your answer!

Rein0ud said:
Yes, I know about support for custom ROMs, but they use FBEv2, OOS uses FEv1, as far as I can understand. Therefore, I am collecting information about the operation of TWRP 3.7 with OOS on A12 (because this version is declared to support OOS A12, but only works on OOS A11)
Thank you for your answer!
Click to expand...
Click to collapse
I confirm that too, it works under OOS11 but not with OOS12, all on OnePlus 7Pro.

I'm on OOS12 stable. Installing it somehow managed to get my magisk looping in some "downloading the full magisk package"-mode. Didn't mind as I thought I might just flash it via TWRP later on. Unfortunately I don't even get that far.
Just to clarify - I tried "fastboot boot" the following items:
- a magisk patched boot.img extracted from the OOS12 stock image
- TWRP 3.6.2 (V1) unofficial by Nebrassy
- TWRP 3.7.0 V1 Official
All ways lead me to a "fastboot mode" logo.
Am I missing something here?

RfBob said:
I'm on OOS12 stable. Installing it somehow managed to get my magisk looping in some "downloading the full magisk package"-mode. Didn't mind as I thought I might just flash it via TWRP later on. Unfortunately I don't even get that far.
Just to clarify - I tried "fastboot boot" the following items:
- a magisk patched boot.img extracted from the OOS12 stock image
- TWRP 3.6.2 (V1) unofficial by Nebrassy
- TWRP 3.7.0 V1 Official
All ways lead me to a "fastboot mode" logo.
Am I missing something here?
Click to expand...
Click to collapse
As I wrote earlier, TWRP 3.7 and less cannot run on A12.
After flashed a modified boot, what happens to your phone? Bootloop ?

ADB tells me it sent and wrote boot partition via command "fastboot flash boot [...]". After that nothing happens.
Forced it to reboot afterwards and I am back to my UNpatched boot partition.
I patched the image with magisk manager on the device itself then transfered it back to my PC. I just transferred it to the phone again to verify, if it is actually patched. Magisk tells me it is.

RfBob said:
ADB tells me it sent and wrote boot partition via command "fastboot flash boot [...]". After that nothing happens.
Forced it to reboot afterwards and I am back to my UNpatched boot partition.
I patched the image with magisk manager on the device itself then transfered it back to my PC. I just transferred it to the phone again to verify, if it is actually patched. Magisk tells me it is.
Click to expand...
Click to collapse
If fastboot take a message "Finished. Total time: ..." and sending/writing have status OKAY, then new mod_boot.img flashing sucsessful. I don't quite understand what you get when you try to start the system after flashing ...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When restarting after flashing the patched boot image I am back to my unrooted state. Everything else is working. No bootloop or else. Just no root either.

RfBob said:
View attachment 5750285
When restarting after flashing the patched boot image I am back to my unrooted state. Everything else is working. No bootloop or else. Just no root either.
Click to expand...
Click to collapse
I can try to share patched_boot, which firmware version is on your device?

Rein0ud said:
I can try to share patched_boot, which firmware version is on your device?
Click to expand...
Click to collapse
Sure, please. Firmware - GM1913_11_H.30

RfBob said:
Sure, please. Firmware - GM1913_11_H.30
Click to expand...
Click to collapse
Pathed boot from H30

Phone booted up just fine with your patched image (just as with mine). Thanks mate, but still no root.

RfBob said:
Phone booted up just fine with your patched image (just as with mine). Thanks mate, but still no root.
Click to expand...
Click to collapse
Hmm, then you should try the method with getting root on OOS 11, local update via zip to 12 and then Magisk firmware in both slots, then reboot

This is exactly where I came from. Updating local caused magisk to redownload some additional files in a loop. So I had to reinstall magisk. Since then - although no reboot in between - I'm unable to get it rooted. Even booting the patched images tells me "no root".