Database Info

Update with root/unlock

I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?

Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.

Anyone know how to root if I'm already on 9.5.6?

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.

I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.

larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.

The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk

larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions

OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you

With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk

skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.

Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi

Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.

Issues after installing latest update, keeps powering off?

Any help, I flashed magisk after latest update and I noticed it didnt reboot itself like it said it would. I clicked reboot myself and now I cant get back into my phone, just keeps saying powering off and takes me bootloader screen where I have enter my pin and it starts decrypting, then options to either reboot to recovery or fastboot. What can I do now?

Happened to me. My bet is you didn't delete all the magisk modules before running the update

mike710_0 said:
Happened to me. My bet is you didn't delete all the magisk modules before running the update
Click to expand...
Click to collapse
Never had to delete them before? What can I do now?

SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
To be honest I don't know. All I do know is the problem gradually got worse. I ended up having to use that recovery software (can't remember the name of it)
Hopefully someone can shed some more light on what to do though

SysAdmNj said:
Never had to delete them before? What can I do now?
Click to expand...
Click to collapse
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery

manor7777 said:
Boot into twrp of you have bootloader unlocked (fastboot boot whatever.img) and Flash magisk manager for recovery mode. You can use it to disable or remove modules in recovery
Click to expand...
Click to collapse
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
UPDATE: Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Only other weird thing I noticed was that after magisk finishes installing, it said it would force reboot my device but it doesn't. I have to manually push the reboot button and thats when I reboot into a boot loop. Any ideas?

Another thought, could it be that I bought this phone off oneplus but this is a verizon update 9.5.13 GM21AA? Although I do use a verizon sims card as a secondary line. Could this be causing the confusion? Maybe I"m just confused with this Slot A & B stuff :laugh:

SysAdmNj said:
Still need help but I was able to fastboot into twrp. I was able to reboot into Slot A and I was back in my phone ok. I was able to reboot and come back ok. I tried the update again, after it downloaded and installed. I opened magisk manager, went to install magisk, selected Install to Inactive Slot(After OTA) - I've been doing these steps all along - bu this time it failed again and put me in a bootloop. Luckily I know how to get back into Slot A but is something wrong with my other slot that the update isnt installing ok?
Click to expand...
Click to collapse
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
SysAdmNj said:
That will fix my issue? Never had to disable magisk modules before while doing an update, something changed?
Click to expand...
Click to collapse
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.

redpoint73 said:
You need to flash Magisk to both slots. Also need to flash TWRP installer again (if you have been wondering why you can't get into TWRP, that is why).
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
This isn't new, it's been known for some time. But only a few modules are actually known to cause problem (Call Recording module is one).
I've used the following process successfully every time I've updated, since getting the 7 Pro shortly after it was released.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
The steps have mostly stayed the some. Not sure exactly when the part about removing Magisk modules was added, but it's been a while.
Click to expand...
Click to collapse
I dont usually flash twrp, I usually just fastboot into twrp. Its how I got out of bootloop this time, then in twrp I selected reboot into slot A.
So those steps are definitely a bit different than how I've been updating recently. I will try those steps. Before I would just download and install update, go into magisk manager and install into inactive slot and it would reboot automatically and that was it.

Can´t boot to recovery. Always landing in QUALCOMM CrashDump Mode

Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boots normally.
Thanks in advance.

RealDanyo said:
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boot normally.
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue this morning when trying to update to 10.0.1. Just boot to bootloader and boot twrp then install 10.

I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2

ItsTecnoDavid said:
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
Click to expand...
Click to collapse
I have no issues with magisk or twrp.
It might be the way you are installing ota or rom.
Might be model specific not sure as I don't know what model you are on. Mine is GM1915.

I'm talking about the official recovery

GM21AA, exactly the same situation (from 10 stable to 10.0.1 and magisk from 19.4 beta to 20) and the stock recovery bump into Qualcomm Crashdump problem here, system bootup normal as well as bootloader.
Troubleshooting:
1. Local update twice, install magisk at inactive slot OTA before reboot, for Android 10's A/B partitions machinasm , try let magisk patch both boot.img. Same...
2. Local update and reboot, lost root but stock recovery work, Fastboot boot twrp.img (latest, not flash, cause I don't need the permanent twrp)->twrp install magisk, reboot system, then, again, same problem.
Todo:
Magisk manager or twrp uninstall magisk, but if it's fail maybe ended up to bootloop, scary.
May try to install back old 19.4 magisk.zip via twrp, it's working in 10.0.0
Anyone with the same problem have any idea?

Thats the exact same error I ran into.
But as mentioned earlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?

RealDanyo said:
Thats the exact same error I ran into.
But as mentioned erlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
Click to expand...
Click to collapse
The recovery here is the one to use.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Be sure to read through

So thanks erveryone who helped.
I now have TWRP running as recovery. So there is no need for official recovery. (and no Qualcomm CrashDump Mode)

Had this happen to me earlier this week. Just ended up using the MSM tool and restoring shipping firmware. You can look for the unbricking thread here for more info on that.

Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...

I don't get it why it have to be so hard.
I'm constantly soft bricking/ bootlooping this phone when trying to do simple things such flashing magisk and twrp. I remember it being so much easier with my Poco F1, never got close to bricking it.
Now every little mistake ends with a bricked phone and 5 hours on the internet trying to understand why

WillyRy said:
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
Click to expand...
Click to collapse
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.

JLine05 said:
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
Click to expand...
Click to collapse
Yea man, things are hinkey this update.
My big problem was i had twrp but it got wiped i guess (could no longer access) and couldn't access adb nor fastboot. But finally got into bootloader (cmd fastboot) so was able to fix.
Easier solution than installing Magisk uninstaller (presuming one has twrp installed, which would be the case if able to flash Magisk uninstaller) is go to TWRP>advanced>file manager and navigate data/adb/modules and delete from there

DO you guys know if there is an updated magisk being developed or what is the way to fix it? Uninstall magisk via TWRP (since I can temporarily install and get into TWRP using the all in one tool by the TWRP developer). Then install TWRP and then Install Magisk ?

I have same problem
How to fix it and bring back stock recovery?

wawanRedblack said:
I have same problem
How to fix it and bring back stock recovery?
Click to expand...
Click to collapse
Can you boot OS?
Can you get to bootloader?

WillyRy said:
Can you boot OS?
Can you get to bootloader?
Click to expand...
Click to collapse
Yes i can boot os and bootloader is ok

Issue with Magisk/TWRP

Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Not sure what to do at this point. Any ideas?
Thanks!

mobbdeep said:
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Edit sorry I updated magisk and now I don't have twrp
Not sure what to do at this point. Any ideas?
Thanks!
Click to expand...
Click to collapse
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry

SirFronts said:
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
Click to expand...
Click to collapse
I guess I will just backup my phone completely, factory reset it, and re-root the device again.

mobbdeep said:
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
Click to expand...
Click to collapse
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4

SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
I'll give that a try tonight.

I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?

SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
alex.coffen said:
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
Click to expand...
Click to collapse
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Boot TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.

mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
I tried something and soft bricked my phone...
Anyway, lucky that I did a backup with twrp for boot when magisk was 19.3, then i can get into twrp by "fastboot boot" the twrp boot img temporarily and restored the boot.
Now everything works fine.
Ps: fastboot boot is not 100% safe...

mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
My TWRP is gone too. But I can temporarily get in TWRP using my computer.
How do I flash OOS firmware? I am currently on PIE 9.5.13 intl. version. Should I download the full zip OOS and then flash it via TWRP ?
Then flash TWRP ?
And then flash Magisk 19.4 ?
Another question: DO you think uninstalling magisk via magisk uninstaller and installing the canary version of it would allow TWRP to stick ? There's threads that mention that the canary version doesn't erase TWRP.

mobbdeep said:
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.

redpoint73 said:
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
Click to expand...
Click to collapse
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh?

Dogstarlooma said:
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh
Click to expand...
Click to collapse
I just read that Magisk 20 has a bug, that prevents TWRP from "sticking", and to use 20.1 (or in your case, looks like 19.4).

URGENT: disabling magisk made OP6 stuck on bootloader, How to recover from it?

I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.

JerryGoyal said:
I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
Click to expand...
Click to collapse
Maybe you did something wrong and this isn't Magisk fault ?

Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data

J0nhy said:
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
Click to expand...
Click to collapse
too late for me i wiped all data. Thanks though, it shall help future readers.

next time, before wipe, try to flash magisk uninstaller first

Try to flash stock boot image.