Database Users

[ZCX TWRP] Install TWRP and Flash SuperSu without breaking incremental OTA's!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles. Use the SuperSU option under Advanced option for flashing SuperSU.
​
How to update Incremental OTA via ZCX TWRP?
1. Reboot to ZCX TWRP.
2. Go to Settings and select "support MIUI OTA".
3. Flash the full rom of the current version [Mandatory]. It will automatically back up system and boot for the OTA survival.
4. Now reboot to system and check for any update, when update releases, download it and press update.
5. Automatically device will reboot to TWRP and OTA flashing will start, this time the backed up system and boot will be flashed and thus patching will happen and your device will be updated.
Downlaod the instruction PDF from here.
Note: Step 1 to 3 to be done only while installing TWRP afterwards no need to follow those steps, when an update releases you need to follow from Step 4.
ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Changelog
20160917
Updated Translation
20160916
Built SuperSu Pro into official Supersu (before installing twrp built supersu pro, be sure to uninstall and then install)
Updated the partition table
20160914
Updated the partition table
Used android 7.0 TWRP source compiler
20160908
Updated the partition table
Repaired the previous version incorrectly installed
20160907
Updated TWRP source
Updated the partition table
Updated Translation
Other details Updated
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you already rooted your device or you used anyother TWRP you won't be able to use this recovery for flashing the OTA's. You should install this recovery in a factory ROM. Steps to follow,
1. Flash the latest beta through fastboot method using Mi flash tool.
2. Unlock bootloader if it is relocked (usually this happens when you flash rom from Lollipop to Marshamallow)
3. Now put your device in fastboot mode and connect to the PC.
4. Run the flash.bat and go to settings and tick the "Support MIUI OTA" option. Take a back up of your EFS,MODEM and Persist if you don't have one.
5. Use the SuperSU option under advanced option (refer the images above).
6. Now use your device as normal, when an OTA update releases, just download it using the OTA and flash using updater/TWRP.
Q. I am getting error in fastboot mod or while running Flash.bat?
Ans: Ensure the device is in fastboot mode (Press Volume up + Power button) and make sure that you have installed the drivers (or Install MI FLash tool).
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.Couldn't Restore back-up through this recovery?
Ans: Please untick firmware while selecting the restore option.
Note: Always it is advised to backup your EFS,MODEM and Persist partitions before flashing any zip files.
Q.Is this recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.
Credits: TWRP and BY~XM
Thank you,
Raaj

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Can i flash in miui 7 lollipop base

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Is this for MIUI OTA's only or it could be used with other custom ROMs too...?

Awesome! Flashing now

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Thanks for sharing
This works only for root or can be used with supersu and xposed framework too and one more thing how to flash Ota by twrp or by updater

Again posting plz confirm
Will i flash it ti lollipop bootloader??? plz tell

Thank ..awesone
Sent from my Redmi Note 3 using Tapatalk

Thank you Raaj52 for awesome work...

Ol cnfm working woith lollipop base but getting error while flashing error 7
Ota i am on miui 7 got update miui 8 555mb
Done all this as on op

Shulod we download OTA.zip from internet or we will get incremental update via updater app?

sasukay said:
Is this for MIUI OTA's only or it could be used with other custom ROMs too...?
Click to expand...
Click to collapse
I think it's only for MIUI
---------- Post added at 11:54 AM ---------- Previous post was at 11:37 AM ----------
p.chandra284 said:
Thanks for sharing
This works only for root or can be used with supersu and xposed framework too and one more thing how to flash Ota by twrp or by updater
Click to expand...
Click to collapse
If you have installed TWRP only and not root, then also MIUI incremental OTA fails. I think Supersu install systemless on MIUI 8 (Android M based) so it can be survived after OTA update. Xposed framework may be need to install again. May be not. Needs to check once next incremental update comes.

Can we flash any custom rom by this TWTP?

Can I flash this recovery from current cofface twrp ??

Go to advance setting you will see option for supersu you can also root from there..

iamnived said:
Can I flash this recovery from current cofface twrp ??
Click to expand...
Click to collapse
Yes. You can.
Yogendra Kher said:
Can we flash any custom rom by this TWTP?
Click to expand...
Click to collapse
Extract the zip and flash recovery.img using your current TWRP

I flash mm, 9.14... Working now. I not tested yet for Ota update.

So ota flash not work with miui 7 lollipop

Should i flash cracked boot.img for this twrp?

AldyRambe said:
Should i flash cracked boot.img for this twrp?
Click to expand...
Click to collapse
Check disable dm-verify in settings ,it will patch boot image itself,no need for cracked boot image.

I'm on MIUI Global Stable 8.0.1 & Android Version is 5.1.1 (Unrooted). I want to root my rn3, should I directly flash this recovery by this method??

OxygenOS 4.0.2 (N) OTA for OnePlus 3T

In order to install it just install Opera VPN, set it to Canada and boom. Here you go!
Hi all,
We are starting the incremental roll-out of OxygenOS 4.0.2 for the OnePlus 3T.
Here are the highlights:
Upgraded to Android 7.0 Nougat
New Notifications Design
New Settings Menu Design
Multi-Window View
Notification Direct Reply
Custom DPI Support
Added Status Bar Icon Options
Improved Shelf Customization
Updated APN Settings for select Carriers
Fixed Proximity Sensor bug during calls
Fixed Google Play Store download bug
Increased System Stability
***Known Issues and Fixes
WiFi connectivity might still fluctuate, if you experience this issue, please send me a pm.
LINK : https://forums.oneplus.net/threads/oxygenos-4-0-2-n-ota-for-oneplus-3t.489596/
In order to install it just install Opera VPN, set it to Canada and boom. Here you go!

i download and share link to google drive now.

Got the OTA in Canada. No issues to report.

Link for downloading the zip
Kudos to the uploader
https://drive.google.com/file/d/0B9BnJVUDKCskLTJBcWhaWF9PLUk/view

Did they release kernel sources with it :c

Hello guys,
Please help.. I am on 3.5.4 and rooted and installed latest twrp, can i upgrade to nougat without any problem and witout loosing data ? I have unlocked bootloader and rooted the phone.
Thanks

Isus <3 said:
Did they release kernel sources with it :c
Click to expand...
Click to collapse
Ofcourse not
Even Samsung uploaded the Nougat kernel sources WTF??!?!?!

[QUOTE=Isus No.

nice, after ota i hang in twrp and also after reflashing 4.0.1 full rom amd supersu 2.79 SR2 twrp tells me "no os installed" and boots every time into twrp instead of system. never seen this before, any help?

paratox said:
nice, after ota i hang in twrp and also after reflashing 4.0.1 full rom amd supersu 2.79 SR2 twrp tells me "no os installed" and boots every time into twrp instead of system. never seen this before, any help?
Click to expand...
Click to collapse
Flash stock recovery.

so does anyone have a changelog other than the one OnePlus have provided, seeing as it's the same as 4.0.0 & 4.0.1

https://drive.google.com/open?id=0B47Lm7PlGNiva00ydkdtb2owTGs
full rom 402 for 3T

MrOnizuka said:
Hello guys,
Please help.. I am on 3.5.4 and rooted and installed latest twrp, can i upgrade to nougat without any problem and witout loosing data ? I have unlocked bootloader and rooted the phone.
Thanks
Click to expand...
Click to collapse
are you on twrp 3.0.3-1? make sure you update twrp to the latest version first before you do anything
step 1: go to the "how to Install OxygenOS 4.0.1 with Stock Or Custom Recovery without Data Loss!!" thread and download the newest supersu zip file and the FULL 4.0.1 zip file (larger file)
step 2: boot to recovery and nandroid backup
step 3: go to wipe, advanced, wipe cache and dalvik
step 4: go to install and flash the full OOS 4.0.1 zip file then directly after flash the newest supersu 2.79 zip file
step 5: boot to system should take a bit longer than usual then you will be in nougat
hope this helps

spireweb said:
are you on twrp 3.0.3-1? make sure you update twrp to the latest version first before you do anything
step 1: go to the "how to Install OxygenOS 4.0.1 with Stock Or Custom Recovery without Data Loss!!" thread and download the newest supersu zip file and the FULL 4.0.1 zip file (larger file)
step 2: boot to recovery and nandroid backup
step 3: go to wipe, advanced, wipe cache and dalvik
step 4: go to install and flash the full OOS 4.0.1 zip file then directly after flash the newest supersu 2.79 zip file
step 5: boot to system should take a bit longer than usual then you will be in nougat
hope this helps
Click to expand...
Click to collapse
Hello,
Thanks, i am on twrp 3.0.3-1 latest !
But to update to 4.0.2 ?

Moderator Information,
Thread closed, please use existing threads before creating new ones, EG: [ROM][OFFICIAL][4.0.2] OOS 4.0.2 Nougat for OP3T !!!

[OFFICIAL] OxygenOS 9.0.6 FINAL Stable (Android 9.0) for OnePlus 3/3T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone!
We are starting to push the incremental roll-out of OxygenOS 9.0.6 for both the devices.
[Changelog]
System:
Updated Android security patch to 2019.10
General bug fixes and improvements
Updated GMS apps
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.com/feedback/
This OTA will have a staged rollout, the OTA will be received by a limited number of users initially and will have a broader rollout in a few days after making sure there are no critical bugs, so using VPN to download this build might not work as the rollout Is not based on regions and is randomly pushed out to a limited number of devices.
This will be the last update for these two devices and we can't thank you enough for your invaluable feedback throughout these three years. With your support, we improved Oxygen OS across three major Android versions and dozens of updates. This is not the end for the OnePlus 3 and 3T, though. Starting next week, we will start highlighting some of the great work done by the developer community, for those of you considering to have a go at Custom ROMs.
Your feedback is appreciated. Hope you enjoy and let us know how you feel about the update in the comments below.
Never Settle :fingers-crossed:

Downloads
OOS 9.0.6 for OnePlus 3T
MD5 : e4e46aa9eebffdd485071383dcda4218
OOS 9.0.6 for OnePlus 3
MD5 : 7c2a1e83ac1a83a3ceb287983496549b
OOS 9.0.5
OOS 9.0.5 for OnePlus 3T
MD5 : ba020a5047f6a166853ec77486f2fd62
OOS 9.0.5 for OnePlus 3
MD5 : f7e17059507758b90dd9709d24e243bb
Official TWRP 3.3.1-0
ROOT: Magisk

Installation Methods
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!
Download the necessary files from the post above and follow as below.
********************* For OOS Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3/3T is now running on the latest OxygenOS firmware & OS based on 9.0 Pie :fingers-crossed:
PS: The first boot may take some time so keep calm and wait for it to boot.
************************ For OOS users with TWRP and unlocked Bootloader************************
NOTE: This dirty flashing method is from the users who tried it and were successful. Please backup to be on safer side.
1. In TWRP, wipe cache & dalvik
2. Flash OOS Full Rom Zip
3. Flash Magisk for Root access (Optional)
4. Reboot to TWRP (to retain recovery as TWRP)
5. Reboot to system
************************ For Custom ROM Users with TWRP Recovery************************
Download the required files from Post 2
Once you have downloaded all the required files on your device, please follow as below:
Backup your phone storage contents to an external mass storage as everything will be wiped.
1. Reboot to TWRP recovery
2. Wipe Dalvik , System, Data & Cache
3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)
- Now your phone has been completely wiped. Copy the zip files to your phone by connecting to your PC/laptop while still in TWRP
3. Install Menu > Select OOS Full Rom Zip > Swipe to Flash
4. Flash Magisk for Root access (Optional)
5. Wipe Dalvik & Cache
6. Reboot System and enjoy latest OxygenOS based on 9.0 Pie :fingers-crossed:
PS: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.

Want to get rid of DM-Verity/Force Encryption? Check this THREAD

what is adaptive display mode ??

Hey i recently both a one plus 3t and rooted it how do i know which roms support sah charging and which do not?
i want to flash the latest nitrogen oreo 8.1 does that support dash charging?

ak_bagade said:
Hey i recently both a one plus 3t and rooted it how do i know which roms support sah charging and which do not?
i want to flash the latest nitrogen oreo 8.1 does that support dash charging?
Click to expand...
Click to collapse
fyi, almost all roms support dash charging. you are good to flash any rom
Sent from my OnePlus 3T using XDA Labs

VKD L!NK!N said:
what is adaptive display mode ??
Click to expand...
Click to collapse
looks like OnePlus copy pasted the update details from OnePlus 5 and forgot to remove the adaptive screen calibration which is not available for us. LOL
Sent from my OnePlus 3T using XDA Labs

@Siddk007 Flashing magisk right after 5.0.1 will make twrp stay as before? I always lose it after flashing oos

Siddk007 said:
Downloads
OOS 5.0.1 full zip : Gdrive
Blu_Spark TWRP
ROOT: Magisk OR SuperSU
Warning : Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Click to expand...
Click to collapse
Are you sure Magisk 15.1 is fine to be flashed with Rom 5.0.1 ?
Have you tried this yourself?
There are many posts mentioning bootloops because of this magisk version
Unleashed by my rooted OP3T in 8.0

Nice someone opened a new topic.
OP3T is still a beast

My OP3T is on OOS 4.5.1. It is rooted with Magisk 14.0. I have twrp version 3.1.1-x blu spark v38 . I want to update to the latest OOS 5.0.1. Can anyone give me advice on the steps to take and which versions I need of everything? I don't want any bootloops...

conephall said:
My OP3T is on OOS 4.5.1. It is rooted with Magisk 14.0. I have twrp version 3.1.1-x blu spark v38 . I want to update to the latest OOS 5.0.1. Can anyone give me advice on the steps to take and which versions I need of everything? I don't want any bootloops...
Click to expand...
Click to collapse
You need to get blu_spark TWRP 3.2.1.x (v8.61)
And to avoid problems, I suggest you go for Magisk v14.6. I myself am on Magisk v14.6 and didn't face any boot loop. And, to be on safer side, do take backup of all your data
Sent from my #FlagshipKiller 3T using Tapatalk

Hi,
thanks for this hint! Using Magisk 14.6 did the trick for me, combined with the blu_spark TWRP 3.2.1.x (v8.61) and wiping Dalvik/Cache.
After the first start, I ran the update to Magisk 15.1 directly in Magisk Manager and it also worked.
Every try befoe that led to a non starting system that got stuck in the OnePlus screen.
BR,
Matthias

matmike said:
Hi,
thanks for this hint! Using Magisk 14.6 did the trick for me, combined with the blu_spark TWRP 3.2.1.x (v8.61) and wiping Dalvik/Cache.
After the first start, I ran the update to Magisk 15.1 directly in Magisk Manager and it also worked.
Every try befoe that led to a non starting system that got stuck in the OnePlus screen.
BR,
Matthias
Click to expand...
Click to collapse
Can confirm same behavior with phone getting stuck on boot logo when updating with 15.1 but succeeding with 14.6.

tal123 said:
@Siddk007 Flashing magisk right after 5.0.1 will make twrp stay as before? I always lose it after flashing oos
Click to expand...
Click to collapse
after flashing oos in twrp, reboot to recovery not system, flash magisk. then reboot to system. twrp will stay
Sent from my OnePlus 3T using XDA Labs

RASTAVIPER said:
Are you sure Magisk 15.1 is fine to be flashed with Rom 5.0.1 ?
Have you tried this yourself?
There are many posts mentioning bootloops because of this magisk version
Unleashed by my rooted OP3T in 8.0
Click to expand...
Click to collapse
well, i have not tried myself but some have reported that magisk 15.1 works. let me confirm again. else i will update OP with 14.6
have u tried to unmount system prior to flashing magisk 15.1?
edit: 15.1 works if after rebooting oos and then flashed
Sent from my OnePlus 3T using XDA Labs

Siddk007 said:
Installation Methods
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Download the necessary files from the post above and follow as below
PS: Dirty flash is fine if you are running a previous OOS version or any rom based on OOS, else if you come from a custom rom Clean Flash is recommended.
********************* For Stock Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3T is now running on the latest OxygenOS 5.0.1 firmware & OS based on 8.0 Oreo :fingers-crossed:
PS: The first boot may take some time so keep calm and wait for it to boot.
* After flash is successful go back to recovery and a wipe of cache is recommended.
* If in any case flash is unsuccessful the system would prompt you to download the full 1.4GB zip.
* Download that and follow the same process as above.
************************ For Rooted Users with TWRP Recovery ************************
Download the required files from Post 2
Once you have downloaded all the required files on you device, please follow as below
1. Update TWRP to the ones provided above by flashing the downloaded image
2. Reboot Recovery and Take a Nandroid of your existing ROM
(Note: Nandroid from 3.0.4-1 cant be restored on older version or and visa-versa)
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe
4. Install Menu > Select OOS 5.0.1 Full Rom Zip > Swipe to Flash
5. Flash the provided SuperSU/Magisk to maintain root (Optional)
6. Wipe Dalvik & Cache
7. Reboot System and Enjoy OxygenOS 5.0.1 Firmware & Latest OOS based on 8.0 Oreo :fingers-crossed:
The first boot may take some time as the system would boot twice due to flash of supersu so keep calm :fingers-crossed:
PS: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Click to expand...
Click to collapse
Can magisk be flashed after rebooting the rom? I tried flashing rom and magisk at the same time and it was stuck at the 'powered by Android' screen for about 7 minutes.

goodoldie1996 said:
Can magisk be flashed after rebooting the rom? I tried flashing rom and magisk at the same time and it was stuck at the 'powered by Android' screen for about 7 minutes.
Click to expand...
Click to collapse
yes, flash magisk after rebooting the rom
Sent from my OnePlus 3T using XDA Labs

Siddk007 said:
well, i have not tried myself but some have reported that magisk 15.1 works. let me confirm again. else i will update OP with 14.6
have u tried to unmount system prior to flashing magisk 15.1?
edit: 15.1 works if after rebooting oos and then flashed
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
What do you mean?
If you flash the Rom and then you reboot without flashing Magisk,then you will lose the custom recovery.
In this case not only you wont be able to flash Magisk, you will have the stock recovery and you will have to start the whole process from scratch
Unleashed by my rooted OP3T in 8.0

Realme X2 Pro Root | RUI 1.0 | C.38 | Custom Recovery | Magisk Canary | SafetyNet Pass | FP

~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms
Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
​If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio​
Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
No need to wipe any partition (Dirty Flash)
[Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
Install vbmeta.imgwith TWRP by selecting vbmeta partition.
[This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Follow the below procedure to root RUI or to replace stock recovery
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to fastboot(power off device and hold vol- and power)
Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
TWRP - Download: TWRP 3.4.0-0 Thanks @mauronofrio
Code:
fastboot flash recovery twrp-3.4.0-0-RMX1931-mauronofrio.img
OrangeFox - Download: OrangeFox-R10.1 Thanks @Jerry08
Code:
fastboot flash recovery OrangeFox-R10.1_1-Unofficial-RMX1931.img
OrangeFox Recovery for realme X2 Pro - Download: OrangeFox-R11.0_1-Stable-RMX1931 Thanks @Jerry08
Code:
flash OrangeFox-R11.0_1-Stable-RMX1931.zip in custom recovery
Reboot to Custom Recovery
Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
Download: VBMETA
Flash Magisk Canary - Download to your device.
Download: Magisk Canary module[12.1 MB]
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu
[*]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
Download: Magisk Canary Uninstaller [2.54 MB]
Reboot to System (May take 5-7 minutes to complete booting)
New Magisk Canary app will be installed automatically in few seconds
Update Magisk Canary app
Download: Magisk Canary app [9.45 MB]
Uninstall any previous old versions of magisk
Open Magisk Canary app
Click Gear button on the Right Top Corner
Under section Manager click Hide Magisk Manager
Enter any new name of your preference
Modified Magisk manager will be installed
Under Magisk section, enable MagiskHide Toggle
Go Back to Magisk home and click shield icon present at the bottom
Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
Troubleshoot:
Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
Can follow the following instruction(s) in any order
Hold Vol+ and Power button till it restarts (more than 10 seconds)
Work in Flashboot to Flash or Wipe anything as per your requirement.
Try flashing Custom Recovery
Flash Magisk Uninstaller if issue related to Magisk
Download: Magisk Canary Uninstaller [2.54 MB]
Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.

Cool! Thanks.

Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.

Rj_Param said:
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
Click to expand...
Click to collapse
Install vbmeta only when you replace stock recovery with custom recovery. If custom recovery is previously installed with vbmeta, they don't need to install vbmeta again.

I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?

adsubzero said:
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
Click to expand...
Click to collapse
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.

hack-os said:
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
Click to expand...
Click to collapse
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?

I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure

adsubzero said:
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
Click to expand...
Click to collapse
Yes when you have custom recovery then you cant install ozip directly from file manager but when you click the ozip in file manager, it takes you to custom recovery if not de-bloated and its completely safe

minoccio said:
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
Click to expand...
Click to collapse
Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery

Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0

nkbhr said:
Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
Click to expand...
Click to collapse
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.

hack-os said:
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.
Click to expand...
Click to collapse
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.

Magisk hide keep failing
Please help

nkbhr said:
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
Click to expand...
Click to collapse
Data and system partitions enough imo

Series of the nightfall said:
Magisk hide keep failing
Please help
Click to expand...
Click to collapse
Did you enable magiskhide in settings? Check op for attached images

hack-os said:
Did you enable magiskhide in settings? Check op for attached images
Click to expand...
Click to collapse
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.

hack-os said:
Data and system partitions enough imo
Click to expand...
Click to collapse
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.

nkbhr said:
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.
Click to expand...
Click to collapse
System image should be what you need

Series of the nightfall said:
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.
Click to expand...
Click to collapse
Uninstall magisk and try everything again. If you never missed any steps and magisk hide option to rename should definitely work on devices above Android 9.

[GUIDE] Root and keeping root options

Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available
A. First time rooting​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This process is common across all options
A.1 Flashing Magisk patched boot image​There are two ways to sourcing a copy of the stock boot image (other than using TWRP - See A.2).
Using the MSM Tool readback option to pull a copy of the current boot image from the phone
Using Payload Dumper and a full update zip
A.1.1 Using MSM Tool ReadBack​The MSM Tool has a feature (ReadBack) that allows it to pull copies of partitions from a phone when it is connected in EDL mode to a PC.
This means that you can pull a copy of your currently running stock boot image directly from the (unrooted) phone and you are not dependent on having access to a full rom installation zip.
A big thanks to @scottlam1 for this information (see https://forum.xda-developers.com/t/oxygenos-a12-breaks-rooting.4456251/post-87067419 and following). You can get a copy of the MSM Tool from @Some_Random_Username's https://forum.xda-developers.com/t/...ol-to-restore-your-device-to-oxygenos.4180837. I used the one for OOS 11.0.7.9 for KB05AA when testing this process.
Find your current slot by connecting your phone to your PC and running adb shell getprop ro.boot.slot_suffix Note: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device.
Start MsmDownloadTool V4.0.exe
Select User type: Others and click Next
Press F8
Select the appropriate boot partition (boot_a or boot_b based on the getprop result). Note: do NOT select both boot_a and boot_b because ReadBack will only produce one boot.img file and the _b extract will overwrite the _a extracted file.
Enter the password: oneplus and then press OK. You should now see a ReadBack button underneath the Target dropdown list.
Reboot the phone into EDL mode using adb reboot edl . When you see it connected to the MSM Tool - it will show an entry with COM3 (for example) - click on the ReadBack button.
Warning: Do NOT click on the Start button as this will start the installation process and reset your phone.
MSM will show "ReadBack Complete" (in green) when it has copied the boot image and power off the phone. Close the MSM tool.
Disconnect the phone from the PC, turn on your phone, reconnect it to the PC, and copy the boot image (it's in C:\boot.img) to your phone.
The rest of the process is the same as that in section A.1.2 below, but starting from step 6 in @DroidFreak32's guide as you already have the boot image.
A.1.2 Using Payload Dumper​Notes:
This can ONLY be used on full update zips, NOT on incremental updates.
Note: if you use @mslezak's Payload Dumper (see https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/ then you may be able to use it on incremental updates. I personally have not done this.
Follow the instructions detailed in @DroidFreak32's https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/ paying attention to:
You can use the latest stable version of Magisk (my recommendation as of June 2022)
Do NOT use the "To flash" option in step 11 because this causes issues when you get the next OTA update. Use the the "To Temporarily boot into a rooted system (RECOMMENDED!!)" option.
Backup both the stock boot and Magisk patched boot images if you are going to use CLI
I also recommend that on OOS you install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/).
A.2 Using TWRP or Orange Fox​I will use TWRP throughout the document to mean TWRP or Orange Fox unless indicated otherwise.
I use the TWRP installer zip to create an installer for Orange Fox by replacing the recovery.img file in the TWRP installer zip with the Orange Fox recovery image (the file has to be named recovery.img). The advantage of this is that you can then flash the recovery zip in recovery as well as in Magisk (install it as a module). And the installer zip will flash recovery to both slots.
Notes:
on OOS 11 use TWRP 11 from https://dl.twrp.me/kebab/
on OOS 12 use the WIP TWRP 12 version from https://forum.xda-developers.com/t/...roject-8t-9r-2022-07-27.4473983/post-87271673 or Orange Fox from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/
on OOS 13 use Orange Fox for OOS 13 from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/ or @apophis9283's version of TWRP from https://forum.xda-developers.com/t/recovery-unofficial-twrp-oneplus-8t-oos13-1-19-23.4541965/
Boot bootloader
fastboot boot <twrp.img>
(optional - see next item) Backup current boot
Install Magisk-*.apk and note that Magisk will create a backup of the current stock boot (see section C)
Install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/)
Reboot system
Uninstall Magisk stub
Install Magisk-*.apk and in Magisk>Settings enable both Zygisk and Enforce DenyList
Reboot system
A.2.1 Keep TWRP​If you want to keep TWRP installed then the process is very similar to that described for Magisk. The difference is that this time we backup recovery and install TWRP. You can merge the Magisk process with the TWRP process by: Backing up current boot and recovery; Installing both the Magisk-*.apk and the TWRP installer zip.
Here's the process for just TWRP:
Boot bootloader
fastboot boot <twrp.img>
Backup current recovery
Note: the TWRP backups of physical partitions (like boot and recovery and so on) are actually image dumps. You could rename the files from *.emmc.win to *.img and install them using TWRP or other methods.
Install TWRP installer zip
Reboot system
B. Keeping root during an update​
B.1 System Update downloads and installs the update​This is using the built-in System Update tool, which you'll find in:
OOS 11: Settings>System settings> System Update
OOS 12 and higher: Settings>About device>Software update
The process is complicated because you cannot use Magisk>Magisk Install>"Install to inactive slot" as this will fail on OOS 11 (for incremental updates) and OOS 12 (for all updates, including the initial update from OOS 11 to OOS 12).
But testing on OOS 13 (updating from F.62 to F.63 on KB2003 and KB2005) shows that you can now use "Install to inactive slot" and, therefore, the simpler B.1.2 process can be used with System Updater for both incremental and full OTA updates. However this needs more testing (by adventurous IN users).
B.1.1 Safe​The following process is safe to use on all versions and types of OTA updates. It is courtesy of @osm0sis in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713 and @rage302 in https://forum.xda-developers.com/t/...ing-root-options.4387977/page-4#post-86830285.
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
Download and Install the update (and DO NOT reboot) using:
OOS 11: Settings>System Settings>System Update>Download and Install
OOS 12 and higher: Settings>About device>Software update
Copy the updated boot image as follows:
On PC:Find the inactive slot suffix:
adb shell getprop ro.boot.slot_suffix Note: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device.
If the result is _a then the inactive slot suffix is _b otherwise it is _a
Take a copy of the inactive slot boot image: adb shell su -c dd if=/dev/block/by-name/boot<inactive slot suffix> of=/sdcard/oos-ota-boot.img replacing <inactive slot suffix> with the value you previously determined (_a or _b). Note: Magisk may prompt you (on your phone) to grant root access to Shell - grant it.
On phone: Patch the dumped oos-ota-boot.img using Magisk>Magisk Install>"Select and Patch a File"
Copy /sdcard/Download/magisk_patched*.img to your PC
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Turn on Airplane Mode to prevent Google Play Services detecting that the phone is bootloader unlocked and making your phone uncertified in Google Play.
Reboot the phone from the System Update dialog; verify that you are now running the updated version
On PC: Reboot to bootloader using adb reboot bootloader
Boot (NOT flash) the patched boot image: fastboot boot <magisk-patched image> where <magisk-patched image> is the patched image you transferred to the PC
On phone: Verify that Magisk shows you are rooted
Make rooting permanent using Magisk>Magisk Install>"Direct Install (Recommended)" and reboot again
Turn off Airplane Mode
B.1.2 Simple​The following process is the simplest update method, but is limited to:
OOS 11 full image OTAs only
OOS 13+ full image OTAs and, starting with C.62, incremental OTAs (confirmed for KB2003 and KB2005)
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
Download and Install the update (and DO NOT reboot) using:
OOS 11: Settings>System Settings>System Update>Download and Install
OOS 13+: Settings>About device>Software update
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it and it is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting, leaving you without root.
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 reboot.
To re-install TWRP, follow the process in A.2.1
B.2 Manual Install​This involves manually downloading the update zip and then installing it using one of the following options.
It is up to you to download the update (from whichever source you use).
How to get a copy of the update zip
The simplest option is to use Oxygen Updater (https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater).
It is also possible to get a copy of the update zip if the OOS 13+ System Updater is showing that an update is available and the installation button is showing "Extract".
You'll find the installation zip (named my_manifest_*_patch.zip or my_manifest_*_all.zip for incremental or full OTA) in /data/ota_package/OTA/.otaPackage.
B.2.1 Local Install​This is using:
OOS 11: System Update>Gear icon (local install)
OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
OOS 13+: On EU and IN Settings>About device>Software update>3-dot menu>Local install; on NA: same as for OOS 12
Note: If the Local install option is greyed out because the System Updater is showing that an update is available, then you can still use Local install by:
Turn on Airplane mode to prevent the System Updater finding the update again after the next step.
Go to Settings>Apps>App Management>3-dot menu>Show system and clear storage from Software update
If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
Move the update zip to /sdcard (NOT a subdirectory of /sdcard).
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk.
Install the update using the appropriate local installer for your version of OOS and DO NOT reboot.
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it and it is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting, leaving you without root.
Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 and 12 reboot.
To re-install TWRP, follow the process in A.2.1
B.2.2 Using CLI​CLI (command line interface) tools, such as Terminal (I use Termux from https://f-droid.org/en/packages/com.termux/) or ADB shell, allows you to manually download delta updates avoiding the need to wait for full updates or for someone to post a copy of the delta update zip.
If you use Terminal then you can install updates without the need of a PC (my preferred option).
Using line commands, at one level, can simplify some processes by avoiding the need to switch out to recovery and back again. On the other hand, they complicate things by requiring knowledge of how to use them.
The commands you need to be familiar with are:
dd to read-from/write-to the partitions in /dev/block/by-name
grep to scan the output of a logcat
getprop to find out which are the active/inactive slots
logcat to read the Android logs
su to run commands as root
Get a copy of the update zip
Note: I'm running the NA version of OOS. If the URL below for the OTA is different for other OOS versions, please let me know via a PM.
Once the phone tells me that there's an update available I do the following in Termux:
su -c "logcat -d" | grep -Eo "https://android.googleapis.com/packages/ota-api/package/[a-z0-9]*.zip"
This looks for the the Google OTA server file name in logcat and returns the source address. For example, the KB2005 C.11 incremental update was https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Note: You should run these commands as soon as you get a notification that you have the update. If you leave it too long then the log file will roll over and you won't be able find the url.
wget -O /sdcard/oos-ota-update.zip <source address>
This pulls a copy of the file to /sdcard
Note: You could also just paste the URL into a browser to download the file
Find the active slot suffix: getprop ro.boot.slot_suffix
If the result is _a then the inactive slot suffix is _b otherwise it is _a
Restore active slot stock boot/recovery (recovery: only if TWRP is installed) using dd if=<copy of stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>
Note: you could also use Magisk to restore the stock boot using Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update using the appropriate local installer for your version of OOS and DO NOT reboot
Note that the OOS 13+ EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it. It is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting leaving you without root.
The local installer is:
OOS 11: System Update>Gear icon (local install)
OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
OOS 13+: On EU and IN Settings>About device>Software update>3-dot menu>Local install; to be advised on NA
Backup the new inactive slot stock boot/recovery (recovery: only if TWRP is installed) using dd if=/dev/block/by-name/<boot/recovery><inactive slot suffix> of=<new boot/recovery img>
Restore root to the current active slot dd if=<copy of current Magisk patched stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>. This is so you keep root in case the update somehow fails and you're returned to the current system.
Note: You could also use Magisk>Magisk Install>"Direct Install (Recommended)"
(ONLY if keeping TWRP) Magisk>Modules>Install from storage: Select <twrp-installer.zip>
Magisk>Magisk Install>"Install to inactive slot" and DO NOT reboot
Backup the new Magisk patched stock boot using dd if=/dev/block/by-name/<boot><inactive slot suffix> of=<new Magisk patched boot img>
On OOS 11 and 12: Reboot. On OOS 13+ now tap on Install in the local installer to finish the installation.
C. A note on Magisk backup folders in /data​When Magisk patches a stock boot image using either Magisk>Magisk Install>"Direct Install (Recommended)", Magisk>Magisk Install>"Install to inactive slot", or is installed in TWRP, then it creates a backup of the stock boot image in a directory named /data/magisk_backup_<SHA1 of stock image>.
When you use Magisk>Uninstall Magisk>Restore images the backup corresponding to the current patched boot image is used to restore the stock image to the current (active) slot.
Clearly, if you deleted these magisk_backup directories then Magisk will not be able to restore the stock boot image. You must, therefore, always keep the current backup.
If you don't delete these backups you can end up with a lot of obsolete backups. So, how to work out which one is the one you need to keep?
The simplest way is to:
Restore the current stock boot image using Magisk>Uninstall Magisk>Restore images
Delete all the /data/magisk_backup_* directories
Restore the rooted boot image using Magisk>Magisk Install>"Direct Install (Recommended)" - this also creates a new magisk_backup directory (no need to reboot)

Great write up. I know some people will appreciate the info when they have that "freak out moment" and something goes slightly wrong.
My question/suggestion would be in regards to your A.2 step. But please, if both options work, my post can be ignored. As you and I discussed in another thread, the update process via TWRP while keeping root has always been, on previous OnePlus Android OS versions.
Download full ROM zip from OnePlus or other available location. I.E. 11.0.12.12
Create Nandroid backup.
Install full ROM zip.
Install TWRP.
Reboot to recovery.
Install Magisk.
Reboot to system.
Assuming it's a full update and not a delta. You outlined...
Manually download the update (from whichever source you use)
Boot recovery
Restore the stock boot and recovery that you backed up previously
Install the update
Boot bootloader
fastboot boot <twrp.img>
Backup current boot and recovery
Install Magisk-*.apk
Install twrp-installer.zip
Reboot system
As you stated, if full update, skip steps 3, 5, 6. Does changing the order and installing Magisk before TWRP allow you to not install TWRP 2x in order to keep the recovery and preserve root?
I used my outlined steps to update to 11.0.12.12 and it worked perfectly. Sorry if this post seems out of sorts, I'm doing it from my phone.

The Apostle said:
Great write up. I know some people will appreciate the info when they have that "freak out moment" and something goes slightly wrong.
My question/suggestion would be in regards to your A.2 step. But please, if both options work, my post can be ignored. As you and I discussed in another thread, the update process via TWRP while keeping root has always been, on previous OnePlus Android OS versions.
Download full ROM zip from OnePlus or other available location. I.E. 11.0.12.12
Create Nandroid backup.
Install full ROM zip.
Install TWRP.
Reboot to recovery.
Install Magisk.
Reboot to system.
Assuming it's a full update and not a delta. You outlined...
Manually download the update (from whichever source you use)
Boot recovery
Restore the stock boot and recovery that you backed up previously
Install the update
Boot bootloader
fastboot boot <twrp.img>
Backup current boot and recovery
Install Magisk-*.apk
Install twrp-installer.zip
Reboot system
As you stated, if full update, skip steps 3, 5, 6. Does changing the order and installing Magisk before TWRP allow you to not install TWRP 2x in order to keep the recovery and preserve root?
I used my outlined steps to update to 11.0.12.12 and it worked perfectly. Sorry if this post seems out of sorts, I'm doing it from my phone.
Click to expand...
Click to collapse
The problem is that delta updates require you to restore both recovery and boot partitions to stock otherwise the installation fails.
The process I describe works for both full and delta updates. But, like I said, if you know that the update is a full OTA, then you can simplify the process and, <edit>if you know it's always going to be a full update, then<end-edit> you can use your "usual" process.
PS: this is a source of confusion because the BA ROMs are always full updates, while the AA ROMs are typically delta updates.
So what works for one user will not work for another even though they are both running OOS on an 8T.
And then there's the difference between letting System update download and install versus manual install, which creates another place for confusion is you just talk about "install update" instead of being specific as to the exact method.

BillGoss said:
The problem is that delta updates require you to restore both recovery and boot partitions to stock otherwise the installation fails.
The process I describe works for both full and delta updates. But, like I said, if you know that the update is a full OTA, then you can simplify the process as per your "usual" process.
Click to expand...
Click to collapse
I guess I don't know why people wouldn't simplify the process, download the full ROM, and eliminate steps. It's worked for years on OnePlus devices across android 9, 10, and now 11.

The Apostle said:
I guess I don't know why people wouldn't simplify the process, download the full ROM, and eliminate steps. It's worked for years on OnePlus devices across android 9, 10, and now 11.
Click to expand...
Click to collapse
Because there's often no AA full rom to download. They can take months to show up while the delta is available immediately from Google.

I've never had that issue. Between XDA and OnePlus forums, someone has always posted a host link... Since OnePlus stopped around October.
Regardless, good info you posted.

The Apostle said:
I've never had that issue. Between XDA and OnePlus forums, someone has always posted a host link... Since OnePlus stopped around October.
Regardless, good info you posted.
Click to expand...
Click to collapse
Thanks. By the way I edited my first reply to you because your "usual" process only works if you are always using full updates.

Hi!
I'm using this method for the update:
Without TWRP
Manually download the update (from whichever source you use) to /sdcard
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update in System Update>Gear icon (local install)
Magisk>Magisk Install>Install to inactive slot
Reboot system
2nd point, if I tap on uninstall magisk, It tells me that I don't have a backup original boot image, how can I proced?
Thanks

Feduz said:
Hi!
I'm using this method for the update:
Without TWRP
Manually download the update (from whichever source you use) to /sdcard
Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
Install the update in System Update>Gear icon (local install)
Magisk>Magisk Install>Install to inactive slot
Reboot system
2nd point, if I tap on uninstall magisk, It tells me that I don't have a backup original boot image, how can I proced?
Thanks
Click to expand...
Click to collapse
You can't proceed if your update is an incremental update. Otherwise you can go ahead.
You'll need to find a copy of the stock boot image to restore it before installing the incremental update.

BillGoss said:
You can't proceed if your update is an incremental update. Otherwise you can go ahead.
You'll need to find a copy of the stock boot image to restore it before installing the incremental update.
Click to expand...
Click to collapse
I'm on 11.0.11.11KB05BA, to 11.0.12.12. so I need to flash the original boot image via ADB/fastboot? Then proceed with point 3?

Feduz said:
I'm on 11.0.11.11KB05BA, to 11.0.12.12. so I need to flash the original boot image via ADB/fastboot? Then proceed with point 3?
Click to expand...
Click to collapse
You tell me. I use AA, not BA. If you don't know what type of update it is, then you need to replace stock using whatever method you like.

BillGoss said:
You tell me. I use AA, not BA. If you don't know what type of update it is, then you need to replace stock using whatever method you like.
Click to expand...
Click to collapse
It's a full update, about 2.8 GB. I'll flash the stock boot.img so

Feduz said:
It's a full update, about 2.8 GB. I'll flash the stock boot.img so
Click to expand...
Click to collapse
if it is a full update you don't need to restore anything before installing it.

Qnorsten said:
if it is a full update you don't need to restore anything before installing it.
Click to expand...
Click to collapse
Correct, I skipped this part in the first post. I've done the update and then installed via magisk. All went good. Thanks

What should I backup using TWRP before a custom rom update and before a jump from a custom rom to another?

rmroot said:
What should I backup using TWRP before a custom rom update and before a jump from a custom rom to another?
Click to expand...
Click to collapse
Read the TWRP OP posts for the answer.
[CLOSED] [No longer maintained] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (8T / Kebab) (2022-03-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

@BillGoss
I will be a user of an OP 9R in a few days and I saw that it shares the same version of TWRP.
In the 9r forum I still haven't found a well explained tutorial and if it's possible.
The instructions you put here allow you to update OxygenOS on 8T and keep root/TWRP, right? Would they be applicable to the 9R as well?

lvints said:
@BillGoss
I will be a user of an OP 9R in a few days and I saw that it shares the same version of TWRP.
In the 9r forum I still haven't found a well explained tutorial and if it's possible.
The instructions you put here allow you to update OxygenOS on 8T and keep root/TWRP, right? Would they be applicable to the 9R as well?
Click to expand...
Click to collapse
I know that the 8T and 9R share similar architecture so the process I've described may work on the 9R, but I can't confirm this.
I do know that as one point we had a common TWRP version for both the 8T and 9R, but that's no longer the case and there's no official TWRP for the 9R.
So, from my perspective, you're on your own on this. If it works, great. You may want to post your process and results in the 9R forum, but not here (this is strictly an 8T forum and thread).

Thanks very much for this thread, @BillGoss. Just easily upgraded 11.0.12.12.KB05AA to 11.0.13.13.KB05AA with your methods using fastboot boot trwp.xx.img from bootloader mode and simply reinstalling Magisk after letting the update run (airplane mode on, as you suggest). I had just upgraded Magisk before the update, so had the latest apk handy in my downloads.
To backup your boot in TWRP (first know your active slot), you can get to a terminal in the TWRP/Advanced menu. I use the same commands you list in your "Use a CLI" instructions.

Hi, I've updated correctly to the latest OOS, should I need to update Magisk? or will be fine this version?