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.

Updated to 9.5.9 and now it reboots into TWRP over and over.

I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.

what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.

Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me

I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?

jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?

Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.

equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.

manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.

All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers

Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.

lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.

This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.

sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.

Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.

Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...

mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good

Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.

jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.

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

No longer booting with Magisk installed

Hi,
I have a rather odd problem:
My phone simply does not boot when Magisk is installed
Installed Magisk 20.0 on Stock 10.0.1-GM21BA a while ago and everything was fine.
Today it won't boot any more (stuck on the warning that my bootloader is unlocked, then bounces to fastboot)
As soon as I uninstall Magisk from TWRP it boots again
Then I Install Magisk 20.1 from TWRP, it does not boot.
Then I uninstall Magisk 20.1 from TWRP, it boots again
Then I flash the pre-patched boot image from here and it does not boot again
Then I flash the stock boot image from here and it boots again
I also tried installing Magisk without dm-verity (only forceencrypt), still not booting beyond unlock warning and fastboot
Does someone know what is going on with my phone
Can I root it without Magisk?
Thank you for any help

Try TWRP 70

Maybe you're on twrp v71... Try reverting to the older v70

had same problem.i reflashed stock and locked bootloader back to offical, andriod 10 lets twrp work but not masgik. i even used magisk manager to patch file and flashed that file to have no more root

NateDev said:
Try TWRP 70
Click to expand...
Click to collapse
santiagoruel13 said:
Maybe you're on twrp v71... Try reverting to the older v70
Click to expand...
Click to collapse
Thanks for the ideas, did not fix it unfortunately
Guess I will stay without Magisk for now

do you have any modules hanging out?
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
you could try that.

Hmm.
Try this with twrp v70
1. Boot to twrp
2. Flash the full a10.0.1 rom
3. Flash twrp v70
4. Reboot to twrp
5. Flash magisk v20.
Reboot
Thats what i do if something is wrong.. i always reflash a rom..
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Re flashing a rom also saved my friend's phone..after flashing boot.img for rooting purposes..he always boot without a wifi. So we dirty flash a rom.first . Then using that same rom that we flashed.. we extrscted its boot.img then patched it with magisk. Then re flashed.. then boom.. its working now..
Reflashing the full a10.0.1 rom.solved the issue..
---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------
My idea here is that
Flash the rom..
Then using the rom that you just flashed..
Get its boot.img.. then patch it then flash it again.. it will now boot. I havent tried directly flashing a patched boot.img without reflashing the rom first..

I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system

coolguy001 said:
I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system
Click to expand...
Click to collapse
do you mean in step 1, Magisk Manager v7.4.0

Did anyone figure out how to fix this issue? I have tmobile and after updating to 9.5.5 and installing magisk it works until I reboot again and then it hangs and goes to fastboot. I try to narrow down the problem and it happens after I install adaway maybe after I choose system less. Or after installing YouTubevanced. Idk what I'm doing

Did anyone find a fix to this ? I'm having the exact same issue.
Flashing magisk 20.4 gives a bootloop. Uninstalling via TWRP allows me to boot to system. No overlays no modules etc,everything uninstalled but still cant boot with magisk. Have I missed something? The only solution I can find is factory reset and begin again, which I can do but as a last resort.

Help! Bricked OP6 by trying to install TWRP via fastboot!

Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex

dr.zikzak said:
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
Click to expand...
Click to collapse
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.

soihuvuontrang said:
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
Click to expand...
Click to collapse
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex

dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.

dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
boot in to fastboot mode and your fone is not brick,so msm tool isn't used .
you can download newest driver for oneplus on google.
and you can find on forum. hope you will be successful

Kurtinaitis said:
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
Click to expand...
Click to collapse
I'll have a try..,.thanks for that!
Regards,
Alex

The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
I also tried fastboot flash recovery twrp.img -> no such partition..... don't know why it worked the first time I did it, root and custom ROM without any issues...
Thanks,
Alex

dr.zikzak said:
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
Thanks,
Alex
Click to expand...
Click to collapse
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash

Kurtinaitis said:
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Click to expand...
Click to collapse
I downloaded latest twrp-3-3-1.2 (I think) for my OP6, copied the belonging .zip file to my phone... started cmd as admin, typed fastboot devices....the device showed up, then fastboot boot twrp...........img.....enter, and afterwards the "1+" logo showed up, below it read Fastboot Mode...and nothing ever happened... till i switched the phone off again after 10 minutes...
Wrong version you think?
Thanks,
Alex

If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img

Flash a patched boot image of your rom via fastboot and than flash twrp installer through magisk manager. Done.

Kurtinaitis said:
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Click to expand...
Click to collapse
Yes that worked for me last time I attempted root.

TWRP update - no boot into system
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex

dr.zikzak said:
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
Click to expand...
Click to collapse
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.

Kurtinaitis said:
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Click to expand...
Click to collapse
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex

dr.zikzak said:
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
Click to expand...
Click to collapse
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before

Kurtinaitis said:
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Click to expand...
Click to collapse
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)

Kurtinaitis said:
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Click to expand...
Click to collapse
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex

Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex

dr.zikzak said:
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Click to expand...
Click to collapse
Did you try to install the Update since the app Oxygen Updater?
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
dr.zikzak said:
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
Click to expand...
Click to collapse
I think there's some thread in Guides and News in which OP uploads some patched boot.img le something like that to have root but i never tried.