Database Users

[Guide][Root] Magisk without TWRP on Android P

Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)

Sadly goes into a bootloop for me - no idea why though

This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.

reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.

I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide

reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?

hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?

reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin

newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?

I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP

reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.

newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?

I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)

@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk

Will work on the verizon variant (bootloader locked)?

sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.

What happens if you lock the bootloader after all of this?

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.

TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?

Magisk canary build running on QDP1

tested and working
DP1 no wipe, run TWRP skip password if it asks, push latest magisk canary build to /mnt and flash
you will have root though i cant seem to update magisk.apk or zip through the app cheers guys
EDIT
Just uninstalled magisk that flashed with canary build from telegram chat and downloaded lastest apk from github canary. and working fine!!!
attached is an updated installer should work fine!!

Anyone?

ne0ns4l4m4nder said:
Anyone?
Click to expand...
Click to collapse
Yep can confirm that the latest canary build is working great. John Wu pulls through again in record time.
And just an extra disclaimer for the sake of clarity this is only working on the previous gen Pixels. The 3/3 XL are still a work in progress for the time being.

couldnt install says invalid zip format

mysara saad said:
couldnt install says invalid zip format
Click to expand...
Click to collapse
Yeah that zip has an extra folder inside of it for some reason. Just use the one from the magisk canary thread.
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
I had to remove lock screen security first too since TWRP wasn't decrypting properly with it on. GL

You don't need to decrypt, just skip and push the magisk.zip to /mnt and install

Here's how I got to rooted q from the latest rooted stock p without wiping my internal memory. Please note that I do not have any passwords or patterns on my phone, so this works if you do not have encryption. Just make sure you back your phone up to your computer first just in case something goes wrong :
0. With your phone hooked to the computer, boot into bootloader and type "fastboot devices" to make sure your phone shows up. This is optional and just something I do to make sure everything is working as it should.
1. Download the factory image from here: https://developer.android.com/preview/download.html
2. Download and install the canary magisk manager from here: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337. Go to settings and change the update channel to canary. There will now be a new update, tap install but select "download only".
3. Unzip the factory image.
4. Open the "flash-all.bat" file in a text editor and remove the -w flag after the fastboot command near the bottom of the file.
5. Obtain the STOCK boot.img and dtbo.img of the system rom you are CURRENTLY running.
6. Type "adb devices" with your phone hooked up to the computer to make sure that you have a good connection and your phone has debugging on and authorized.
7. Reboot into TWRP and wipe Dalvik/ART cache, System, and Data.
8. Reboot into bootloader.
9. Take a command prompt to where your current stock boot.img and dtbo.img files are.
10. Command: fastboot flash boot {name_of_your_stock_boot.img}
11. Command: fastboot flash dtbo {name_of_your_stock_dtbo.img}
12. Now take your command prompt to where your unzipped q rom is.
13. Command: flash-all
14. When it's finished, your phone will reboot.
15. Download the latest twrp img and zip here: https://dl.twrp.me/taimen/
16. Once your phone is rebooted, go into settings and enable usb debugging.
17. Open a command prompt where you downloaded the twrp image.
17. Command: adb reboot bootloader
18. Command: fastboot boot {name_of_twrp_image_you_downloaded.img}
19. Flash the TWRP zip and the canary magisk zip you downloaded earlier and reboot.

19. uneseesery steps that dont work...

hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
That is exactly what I did to get on rooted q from rooted p, without losing anything on my internal storage, and it does work. If you can tell me any "uneseesery" steps here I'm all ears.

hanschke said:
19. uneseesery steps that dont work...
Click to expand...
Click to collapse
I don't think so..I rooted through that step only..

Help | Tried to root Android 11 and got stuck

Hi, I'm a newbie and I usually root my Pixel 4 on AT&T because I use a lot of tethering for my work which my carrier blocks.
Two weeks ago I had Android 10, unlocked and rooted. Life was good.
Phone automatically updated to Android 11 and I lost root.
Today I had some free time so I:
-Downloaded Android 11 factory img to my laptop
-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)
-Flashed the new patched img to my mobile
-Restarted
-Got stuck into the G with bar at the bottom eternally
-Couldn't get into ADB devices so I restarted to fastboot
-flashed the stock boot.img by: "fastboot flash boot boot.img"
-fastboot restart
-Now stuck on Fastboot Mode loop. Device Status "unlocked", boot slot a, enter reason: "reboot bootloader"
Now I don't know exactly what to do here and I do need my mobile to work. Sorry for the newbie question but what should I do? Ideally I would like to not lose my data given bootloader is already unlocked.
P.S. I ran stock image flash-all without the -w and I'm back to square 1. How should I root then?
Thank you so much!

luisbs said:
...-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)...
...How should I root then?
Thank you so much!
Click to expand...
Click to collapse
These Instructions might help:
First, you cannot root with the Stable Magisk Manager.
You can only root by using either the Beta or Canary Magisk Manager:
A. If Magisk Stable is installed:
1. Change the Update Channel to Beta or Canary
2. Install Beta or Canary Manager
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Uninstall all the modules
12. Uninstall Magisk - Restore images
13. Reboot
14. Goto D
B. If Beta or Canary Magisk Manager is installed:
1. Uninstall all modules
2 .Make sure the Update Channel is set to the version of the Manager installed.
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Goto D
C. If Magisk is not installed:
1. Download Beta or Canary Magisk Manager
2. Install Beta or Canary Magisk Manager
3. Make sure the Update Channel is set to the version of the Manager you installed.
4. patch the stock boot.img - tap Install next to Magisk
5. Select: Patch boot.image
6. Locate Stock boot.img you extracted from the current factory image.
7. Select it, tap the Checkmark (✓)
8. Tap Lets Go
9. Save log
10. Reboot
11. The magisk_patched.img size should be between 64-67 MB.
D. Flash magisk_patched.img:
1. Boot the phone into fastboot mode
(Power the phone Off ==> Press and hold the Power and Volumne down buttons until you see Start.)
2. Connect the phone to your Computer via a USB cable (A to B)
3. Open the Platform-tools folder and Right Click it.
(Make sure the magisk_patched.img is in this folder.)
Select Open Command prompt here. If you do not see Open a Command Prompt here. Click the folder icon on the left side of the address bar. The information in the address bar should be highlighted. Type cmd in the address bar and press Enter a Command Window should open. Type fastboot flash boot magisk_patched.img --slot all and press enter.
4. When it finishes, type fastboot reboot.
5. Disconnect your phone from the computer
6. Done! Your phone should be rooted

did it work on october update too?
my fastboot says: no valid slot to boot

Danieldergrosse said:
did it work on october update too?
my fastboot says: no valid slot to boot
Click to expand...
Click to collapse
Yes!

Than i am on Stock Boot lol

Danieldergrosse said:
Than i am on Stock Boot lol
Click to expand...
Click to collapse
Ok!

You dont Unserstand. My bootloader is unlocked. Why to flash the Stock boot.img Like you Said for d
Lol
Thats the Same as i Download factory extraxt and flash Boot. IMG
ITS the Same. So why you should get root with original Boot.img
Thats why i say loool
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?
I find a solution....i am Sure
Than i will Tell...

Danieldergrosse said:
You dont Unserstand...
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?...
Click to expand...
Click to collapse
Ok, I misunderstood your comments, I apologise.
No, I didn't rename the magisk_patched.img boot.img.

You dont understand what i mean....
If i flashed magisk patched it says No Slot to Boot. You Know.
Than i flash boot.img i am Back to Stock and it works....
My patched magisk doesnt Work....can you send me your patched magisk.img ?
Perhaps it works

Danieldergrosse said:
...My patched magisk doesnt Work...
Click to expand...
Click to collapse
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
Danieldergrosse said:
...I find a solution....i am Sure...
Click to expand...
Click to collapse
lol

??

Homeboy76 said:
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
lol
Click to expand...
Click to collapse
Don't know what's going wrong @Your side, but it works fine as ever

2WildFirE said:
Don't know what's going wrong @Your side, but it works fine as ever
Click to expand...
Click to collapse
I edited the post above to include Beta, thanks for the screenshot.

Danieldergrosse said:
??
Click to expand...
Click to collapse
Possible fix

Uploaded my patched boot.img for you: http://ul.to/utzm0kvc

Updates Thread

Hi Folkz,
the rollout for 11.0.3.4. begins.
I've already downloaded 11.0.3.4 KB05BA (EU) via Oxygen Updater.
Here is a Link to a Post someone in official OPForums who provided a GDrive Link -> https://forums.oneplus.com/threads/...-the-oneplus-8t.1338403/page-34#post-22346201
I will install it now and then I give feedback (rooting etc.).
greetings rage
P.S. Please feel free to add OOS Update News for OP8T (all Variants) here in this Thread.

Okay... installed it already with no problems and root persists... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage

Further Information:
* I used latest magisk canary version dc5e78e1 (21006) from here -> https://github.com/topjohnwu/magisk_files/tree/canary
* SafetyNet checks are sucessfull
I've already patched the boot.img with latest magisk canary, if you need it. -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146

is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)

ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
...I think it's just for you. I tried it and "fastboot devices" and "fastboot reboot" works.
Hint: If you use Windows PowerShell, the command looks like this (if you start PowerShell in the same directory where fastboot.exe is located) ->
Code:
.\fastboot.exe devices
greetings rage

rage302 said:
Okay... installed it already with no problems and root persits... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage
Click to expand...
Click to collapse
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?

Scrambler77 said:
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?
Click to expand...
Click to collapse
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage

rage302 said:
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage
Click to expand...
Click to collapse
Done it! Many thanks!

I couldn't get the OTA file for my variant. So, this is what I had to do to get it installed.
1. Open Magisk Manager -> Uninstall Magisk -> Restore Images
2. Don't reboot.
3. Take the OTA from Settings -> System -> System Updates
4. Don't reboot.
5. Open Magisk Manager -> Install Magisk -> Install To Inactive Slot
6. Reboot.
7. Your phone should be updated with Magisk still installed.

Next Update 11.0.4.5 is on it's way >
https://forums.oneplus.com/threads/oxygenos-11-0-4-5-for-the-oneplus-8t.1342473/
https://m.gsmarena.com/oxygenos_110...ls_out_with_11_different_fixes-news-46278.php
https://www.xda-developers.com/oneplus-8t-oxygenos-11-0-4-5-update/
Changelog
System
* Optimized the call stability
* Improved system power consumption performance to reduce heating
* Improved mis-touch prevention to offer better gaming experience
* Optimized fluidity with some mainstream games to reduce lagging risks
* Optimized user experience with Alert Slider by adding toast messages when switching among the 3 modes
* Fixed the issue that the status bar kept hovering on the screen in landscape mode
* Fixed the issue that NFC cannot be turned on in a small probability
Camera
* Optimized the imaging effect to bring you with better shooting experience
* Improved camera stability
Network
* Optimized mobile network connection to improve the network intensity with signal
* Fixed the small probability issue with network interruption while playing games
Click to expand...
Click to collapse
It is just a hot-fix update, so the changelog is nearly the same than 11.0.3.4.

Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
---UPDATE---
I've sucessfully upgraded to 11.0.4.5 KB05BA with keeping root and SafetyNet pass,
with my standard method -> https://forum.xda-developers.com/oneplus-8t/how-to/update-thread-t4188149#2
greetings rage

rage302 said:
Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
Click to expand...
Click to collapse
Lol, updated shortly before your post. First update post root and went flawlessly.
Sent from my OnePlus8T using XDA Labs

Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders

ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
This happened to me on first try.
Installed the Oneplus usb drivers
rebooted
All is well thereafter

blackknightavalon said:
Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders
Click to expand...
Click to collapse
It's on Oxygen Updater
Sent from my unknown using Tapatalk

Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.

card13 said:
Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.
Click to expand...
Click to collapse
If you're rooted you need to unroot before updating
Sent from my unknown using Tapatalk

@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.

card13 said:
@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.
Click to expand...
Click to collapse
Did you flash the 11.0.2.3 incremental in the past?

@g96818 I was able to flash 11.0.1.2 Incremental, 11.0.3.4 and 11.0.4.5 have both failed, with the exact same process I used to get 11.0.1.2 installed (unroot -> reboot -> install update -> boot patched boot img -> dd boot.img backup -> patch img -> boot to newly patched img -> direct install root).
****EDIT #1****
Looks like switching boot slots was a really bad idea and I irritated my phone. It's in a bootloop. "Boot reason: init_user0-failed unable to parse kernel log. For more debug information, adb pull /mnt/vendor/op2/rbr_log or pull op2.img".
***Edit #2****
Well that didn't go as planned. Tried to Factory Reset, still got install failed. Then locked the bootloader to see if it would installed and got stuck on DM-Verity Device Corrupted screen. Ended up using MSM to restore then update to 11.0.4.5. Good thing I was doing every couple days backups with SwiftBackup.

10.3.9 OTA reapplying Magisk fails

So I'm running stock, twrp, magisk and all OTAs so far have been a breeze by following
Let the OTA download and install
Flash twrp via magisk
Install Magisk to inactive slot
reboot
But with todays OTA, magisk fails to patch the inactive slot image with 'Unsupported/Unknown image format'
Direct install still works fine
Now I'm obviously terrified of rebooting, what should I do to resolve this?

Had the same problem, Had Magisk totally wipe my boot so I was stuck with Fastboot.
The solution me and my guys had were to:
Let OTA Update (reboot to bootloader afterwards)
Fastboot boot twrp.img > [Advanced] > [Install Recovery Ramdisk] > twrp.img (you can backup the boot when done.
Install Magisk.zip (I had the 3.4.0 at the time so if you had the latest I heard it can install the apks as well)
Reboot to system
Profit

Huskied said:
Had the same problem, Had Magisk totally wipe my boot so I was stuck with Fastboot.
The solution me and my guys had were to:
Let OTA Update (reboot to bootloader afterwards)
Fastboot boot twrp.img > [Advanced] > [Install Recovery Ramdisk] > twrp.img (you can backup the boot when done.
Install Magisk.zip (I had the 3.4.0 at the time so if you had the latest I heard it can install the apks as well)
Reboot to system
Profit
Click to expand...
Click to collapse
Thanks for the reply
As I am still in 'control' and rooted, isn't there a way to reflash the update zip manually and try again to retain root/patch the boot image?

Alintja said:
Thanks for the reply
As I am still in 'control' and rooted, isn't there a way to reflash the update zip manually and try again to retain root/patch the boot image?
Click to expand...
Click to collapse
Like a dirty flash? Yeah, Just reflash in TWRP. I have not tried to do it on Local Upgrade.