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).
Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.
mpadhu said:
Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.
Click to expand...
Click to collapse
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.
joeljose1001 said:
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.
Click to expand...
Click to collapse
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.
mpadhu said:
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.
Click to expand...
Click to collapse
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.
joeljose1001 said:
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.
Click to expand...
Click to collapse
Got your point. Thank you. I read that Magisk can be installed without root or even custom recovery.
The below is taken from the official Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
How to download or extract the stock boot image file from my official ROM?
"Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img"
vukis said:
vukis said:
1. Magisk Manager Tap "Uninstall" > Tap "Restore
Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the
full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" Tap "install" again Tap
"Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complet
Click to expand...
Click to collapse
Just tried this method with local upgrade. It works indeed! Thanks!
But TWRP got lost from local upgrade. So after restarting flashed twrp-installer-fajita-3.2.3-37.zip via Magisk Manager. But install script anounced that I am now unrooted.
Restarting phone confirmed that.
Anyway installed root again via TWRP.
What is safe way to install TWRP in between those 5 update OTA+keep root steps?
Click to expand...
Click to collapse
What is safe way to install TWRP in between those 5 update OTA+keep root steps? I once tried some kind of "OTA" update via twrp, but all was lost. (Could be a bit older twrp version without pattern unlock)
Why not just download the ZIP from the TWRP rather than use the OTA method?
The zips are available here.
I never uninstall magisk by the way. However that is part of the instructions. There are TWRP instructions, it's the third post, I believe.
OhioYJ said:
Why not just download the ZIP from the TWRP rather than use the OTA method?
The zips are available here.
I never uninstall magisk by the way. However that is part of the instructions. There are TWRP instructions, it's the third post, I believe.
Click to expand...
Click to collapse
Well I used this thread (How to Update/Return to Stock your OnePlus 6/6T(ROOT | NO ROOT | STOCK BASED |OTHERS)) from @mauronofrio as my guide. And in 2nd paragraph it states:
2. I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
Local update method is recommended. So I was following this "general knowledge". Also I lost all user data (with nandroid backup) updating via twrp. Could be that my TWRP was outdated, but I would rather not to loose my user data again :/
Are you just OOS, rooted, TWRP?
I just flash the ZIP in twrp, flash twrp installer, reboot recovery, flash magisk. You can Repeat those steps if you want to update both slots. No reason to complicate it. I've never lost any data. The only time I format or lose data is going between OOS and AOSP roms. Then it is definitely important to backup data (always important to backup data anyways though).
Is there a way to update system to .14 and preserve TWRP?
I know that I can preserve Magisk, but I don't want to lose TWRP because I need to flash few more things.
Two more constraints:
I don't want to lose data
I don't have access to pc
In what steps I can achieve it, if any?
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
MatheusPimentel said:
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
Click to expand...
Click to collapse
Exactly. But make sure to only use the full OTA and not the incremental one.
Full guide
1. Go to TWRP
2. Flash FULL ROM
3. Flash TWRP INSTALLER (if u fail to u will lose TWRP)
4. Reboot your device. (yes boot it...and access your phone)
5. Reboot back to TWRP
6. Flash Magisk
Working method...tried nd tested 50+ times
The following also works. Follow it precisely.
> Install the update through the OS Update UI.
> Open Magisk Manager and find the module that preserves TWRP. Flash it. It won't appear in the module list. Don't restart yet, you'll lose Magisk if you do.
> Open Magist Manager and click "install". Install to inactive slot (OTA)
> Reboot!
Done this a few times now, it's actually more convenient than booting to TWRP.
I use always that way. The module is called TWRP_A_B_Retention_Script-Magisk.zip.
Open Magisk Manager > Downloads and it's called : TWRP A/B Retention Script.
To find it easy order by name. Default it's by last update.
https://forum.xda-developers.com/showpost.php?p=79358976&postcount=2012
Done.
Thank you all.
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 imageThere 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 ReadBackThe 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 DumperNotes:
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 FoxI 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 TWRPIf 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 updateThis 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 SafeThe 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 SimpleThe 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 InstallThis 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 InstallThis 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 CLICLI (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 /dataWhen 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?