Database Users

Issue with Magisk and OTA version 7.1.2

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?

I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.

Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.

It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.

ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.

_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?

ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).

Rooting SM-T380 with Pie

I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!

I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.

Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!

Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.

Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..

Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.

Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.

Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.

[Help] Be able to install OTA with loosing Root and Data

Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.

ptit developer said:
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
You can keep TWRP and Magisk module, you will only need to patch the boot image and install it from TWRP to regain root after the OTA
- Download full Recovery/zip package 2.4 GB for your MI/IN/EU/RU you currently have with MIUI 10
- Flash that zip from TWRP (Install, zip)
- Reboot to TWRP, not to Android, otherwise you will loose TWRP
- Backup Boot in TWRP
- Reboot to Android. You shouldn't have lost your apps and settings. Magisk Manager will be there but no root
- From Magisk Manager take Install, keep Preserve AVB and Preserve Encryption (first two) but UNCHECK Recovery mode
- Choose to Patch image and navigate to the Boot backup you just made in TWRP, boot.emmc.win, 128 MB
- Reboot to TWRP, take Install, Image (not zip) and navigate to magisk_patched.img in Download
- Upon installing keep in TWRP and Wipe Dalwik and Cache, ONlY
-Reboot to Android - you will have root, your previous modules, rooted apps, all
PS: Doing OTA from System Update requires stock Recovery - that's why it reboots for you to TWRP and fails.
To be able to do OTA that way, you would need to first flash back your stock Recovery.
Then OTA update will fail and you wouldl have to force Full OTA.
At the end, you would also loose root - hence the above procedure is simpler, you even don't need PC, you will keep TWRP and you will only need to patch and install the patched boot image to regain root

Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.

ptit developer said:
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
In the first post you said that you already have v10.3.3.0 and that you want to update
Hence why would you now download v10.3.3.0 - you should download v11 (supposidely), that the same newer version that OTA offers you
Yes, you can extract boot.img from that newer MIUI (v11) that you will download and flash but that requires PC - in my instructions you simply use TWRP and make backup of the boot image upon you do update
By extracting boot.img from v11 you will not save any step, you still must flash its zip (not tgz) from TWRP and you must nevertheless reboot to TWRP first
---
By flashing OTA zip (full, 2.4 GB) from TWRP, you should not loose your data and apps. I did it with Mi 9T (not PRO - you are not on the PRO forum) but things must work the same way for PRO for Global or EU (you must update to the same Global, EU, Indian, Russian as you already have, just fownload the same newer version that OTA offers you)

Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.

ptit developer said:
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
Better follow what OTA gives you. Find and download Recovery/zip for that Global v10.3.4.0 and install as suggested.
Later similarly follow the version numbers the same way as they come by OTA

What is update process for OP6T 9.0.16 > 10.3.3 rooted [Global]

I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global

a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Hello,
Here is a link that will help you out with this update process:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953

a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited

flash713 said:
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited
Click to expand...
Click to collapse
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.

Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
10.3.3 is all that you need. 9.0.17 isn't the only way anymore.

Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
I have a T-Mobile SIM unlock OnePlus 6t and I converted it to an international model so when my conversation was done I was on OOS 9.0.1.1 and I booted TWRP and installed 10.3.4 full rom on both slots and also recovery installer and all just like my previous posts stated and everything went fine. I used mauronofrio's TWRP the version just before the latest 3.4xx when I did this.
I always download quite a bit of various firmwares and also TWRP versions before I start flashing things just in case something goes wrong I already have other things maybe I can use and I don't have to stop and wait for some download to finish... And I'm quite sure you know this but definitely make a backup of everything beforehand to USB or transfer it to your pc just in case you end up needing it as a precaution.
Edit added:
I am assuming that you already unlocked your bootloader... I believe everyone knows to do that that's on XDA forums before you can do anything to any device .. I say this after reading post below me here. I guess I should have said that earlier but I just assume everyone knows that on the forums... My bad. ??
From fastboot on Linux PC:
sudo fastboot oem unlock (then hit enter on keyboard) use volume keys to move to unlock option and your Power button to select it and confirm. For more info see: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Super easy to unlock bootloader just remember it does wipe your device clean so move anything to want to PC or USB stick first...

I would think you could just update oxygenOS to latest then re-root no? Assuming your already bootloader unlocked which it seems like would be the case if you have an obsolete magisk installation.
Edit: re-reading your post maybe it is not unlocked as you failed to root. In this case just unlock then flash the latest fastboot image and then magisk as others have already stepped you through. You will lose data when you unlock so backup first.

So if I'm on 9.0.16 I could flash latest OOS directly from TWRP and then flash magisk? And no data loss? Of course I'm rooted with bootloader unlocked.

Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!

a4abbas said:
Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!
Click to expand...
Click to collapse
It is indeed a tough job. This A/B partition has had a lot of people bootloop/soft bricked their phones.
However, you need not pay anybody anything. If you are on stock, I would've recommended you upgrading it via Oxygen updater (a 3rd party app on the play store) and then using the latest recoveries (TWRP 3.4) and flashing it via Fastboot mode.
It is super easy.

[GUIDE] Root OOS with TWRP

Update 220823: Update for TWRP 12 and some other minor changes due to the switch from SafetyNet API to Play Integrity API
Updated 211203: include Magisk Canary
Edited 220113: correct a mistake in the Keeping Root process; some formatting changes
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
OOS 11: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449
OOS 12: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/...win-recovery-project-8t-9r-2022-07-27.4473983
Magisk apk - using stable from https://github.com/topjohnwu/Magisk/releases or using Canary from https://github.com/topjohnwu/magisk-files/tree/canary
Universal SafetyNet Fix (UNSF-MOD) by @Displax from https://github.com/Displax/safetynet-fix/tree/integrity
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
Boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it. Also install USNF if you are using Magisk Canary.
If you want to keep TWRP then install the TWRP installer zip.
Reboot.
If you are using Magisk Canary, in Magisk>Settings enable Zygisk, Enforce DenyList, and Configure DenyList. Then reboot.
Keeping Root on an incremental OTA update
Note: you do NOT need to (but can if you want to) follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you.
If your phone tells you you have an update:
If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot.
In Magisk tap on "Uninstall Magisk" and select "Restore images".
Install the OTA update but don't reboot yet.
Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root.
Reboot
When the phone has successfully rebooted the updated system, boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current recovery partition as you'll need it for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
If you want to keep TWRP then flash the TWRP installer zip.
Reboot and disable airplane mode.

BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggest this method (https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145) but this doesn't work for everybody (it doesn't for me).
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an OTA update
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.

morphius88 said:
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
Click to expand...
Click to collapse
Best place for getting support for Magisk is https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/

Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?

berthur said:
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
Click to expand...
Click to collapse
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin

BillGoss said:
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
Click to expand...
Click to collapse
Than you!

Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.

Wishmasterflo said:
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Click to expand...
Click to collapse
Download the zip from https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ and then use payload dumper to extract the files.

That worked like a charm. Thanks a lot.

I'm Magisk rooted and I have TWRP installed on my 8T EU model.
The OnePlus updater app registers that I am rooted and wants to download the full OTA.
Do I also have to do all the things you described after "Keeping Root on an OTA update" or is there a simpler way?
If yes, then I have a question regarding this step:
2. In Magisk tap on "Uninstall Magisk" and select "restore images".
Click to expand...
Click to collapse
Did Magisk automatically backup these images? Because I didn't do it myself. I only have backed up all my partitions (including boot) after I had installed TWRP and before I rooted.
EDIT:
BillGoss has thankfully already replied in another thread (in which I have basically asked the same question because I am an impatient bast***) where I suggested the overly present "easy" update scheme, which he expects to work. So this should be fine for other people in my situation:
1. Let the system download and install full OTA and DO NOT let the device reboot after it's done
2. Install TWRP A/B Retention Script
3. Install Magisk to inactive slot and reboot
EDIT2:
I just want to add that before having done the above mentioned steps 1-3, I have disabled all Magisk modules and rebooted the device. So the full procedure is the following:
1. Disable all Magisk modules and reboot
2. Let the system download and install full OTA and DO NOT let the device reboot after it's done
3. Install TWRP A/B Retention Script
4. Install Magisk to inactive slot and reboot
Youtube step by step video (he says that he "uninstalls" the Magisk modules but he just deactivates them):

Thanks @haitower
I've updated the OP to make it clear that the process described there only applies to incremental updates.
Also, to answer your question re Magisk backups: Magisk writes a copy of the installed boot image to /data/Magisk* before patching it. A "restore image" uses that backup.

BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" but this doesn't work for everybody (it doesn't for me) which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an incremental OTA update
Note: you do NOT need to follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.

e1thx said:
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
Click to expand...
Click to collapse
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/

Hello!
Today I saw that EU: 11.0.12.12.KB05BA was available as OTA Update so I started to download it using the "Keep root on OTA Update".
During the download I recognized that I was still only connected to mobile network 4G instead of WiFi.
So I stopped the download of the OTA, restarted the phone and turned on WiFi but now I don't get the notification for the new OTA Update anymore and when checking for new Updates it says that my OOS 11.0.11.11 is up to date.
I guess the system has somewhere already stored that I started the download of the new 11.0.12.12 OTA but did not finish it and now I don't get the message to download it anymore.
Any idea how I can fix this so that I can download the new OTA again?
Thanks a lot!
EDIT: I am downloading it now via OxygenOS Updater (the full OTA).

BillGoss said:
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Click to expand...
Click to collapse
I understand that if I want to restore system and data when something doesn't work for me then I just do recovery for all the partitions, system, data etc that I do in twrp?

Please see the update in the OP regarding OOS 12.