Related
This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.
Hi, thanks for the tutorial. I am in the same state as your initial state and would like to give your solution a try. When you mentioned to wait for 10-15 minutes, exactly what happens on the phone during that time, ie. mutiple reboots, or boot animation, etc? I just want to know what to expect during that time.
Thanks again!
First backup & copy it to pc.
Flash codeworks recovery. Flash the rom. Flash codeworks recovery again. Reboot to recovery. If it's ok, reboot to system. System should charge in about 2 minutes, no more!
Set the phone for 2,3 minutes. Reboot to recovery & flash Magisk. For some users 14.6 works, for others 15.0. Here the man says, 15.2.
If one version of Magisk fail, you need to do it all again and when you rich to Magisk, try other version.
ToucanSam said:
This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.
Click to expand...
Click to collapse
was your phone encrypted?
What did you see during the wait?
Once the phone reboots, it's just the usual OnePlus loading logo. The red and white box with ball going around it. For a few minutes.
Your steps doesn't include wipe and format data. Was your phone in a decrypted state?
ToucanSam said:
This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.
Click to expand...
Click to collapse
So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance
0v3rl0rd said:
So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance
Click to expand...
Click to collapse
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.
shadowstep said:
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.
Click to expand...
Click to collapse
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?
0v3rl0rd said:
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?
Click to expand...
Click to collapse
It's not necessary to reboot to recovery after each step.
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).
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
ptit developer said:
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
You can keep TWRP and Magisk module, you will only need to patch the boot image and install it from TWRP to regain root after the OTA
- Download full Recovery/zip package 2.4 GB for your MI/IN/EU/RU you currently have with MIUI 10
- Flash that zip from TWRP (Install, zip)
- Reboot to TWRP, not to Android, otherwise you will loose TWRP
- Backup Boot in TWRP
- Reboot to Android. You shouldn't have lost your apps and settings. Magisk Manager will be there but no root
- From Magisk Manager take Install, keep Preserve AVB and Preserve Encryption (first two) but UNCHECK Recovery mode
- Choose to Patch image and navigate to the Boot backup you just made in TWRP, boot.emmc.win, 128 MB
- Reboot to TWRP, take Install, Image (not zip) and navigate to magisk_patched.img in Download
- Upon installing keep in TWRP and Wipe Dalwik and Cache, ONlY
-Reboot to Android - you will have root, your previous modules, rooted apps, all
PS: Doing OTA from System Update requires stock Recovery - that's why it reboots for you to TWRP and fails.
To be able to do OTA that way, you would need to first flash back your stock Recovery.
Then OTA update will fail and you wouldl have to force Full OTA.
At the end, you would also loose root - hence the above procedure is simpler, you even don't need PC, you will keep TWRP and you will only need to patch and install the patched boot image to regain root
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
ptit developer said:
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
In the first post you said that you already have v10.3.3.0 and that you want to update
Hence why would you now download v10.3.3.0 - you should download v11 (supposidely), that the same newer version that OTA offers you
Yes, you can extract boot.img from that newer MIUI (v11) that you will download and flash but that requires PC - in my instructions you simply use TWRP and make backup of the boot image upon you do update
By extracting boot.img from v11 you will not save any step, you still must flash its zip (not tgz) from TWRP and you must nevertheless reboot to TWRP first
---
By flashing OTA zip (full, 2.4 GB) from TWRP, you should not loose your data and apps. I did it with Mi 9T (not PRO - you are not on the PRO forum) but things must work the same way for PRO for Global or EU (you must update to the same Global, EU, Indian, Russian as you already have, just fownload the same newer version that OTA offers you)
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
ptit developer said:
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
Better follow what OTA gives you. Find and download Recovery/zip for that Global v10.3.4.0 and install as suggested.
Later similarly follow the version numbers the same way as they come by OTA
Update 220823: Update for TWRP 12 and some other minor changes due to the switch from SafetyNet API to Play Integrity API
Updated 211203: include Magisk Canary
Edited 220113: correct a mistake in the Keeping Root process; some formatting changes
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
OOS 11: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449
OOS 12: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/...win-recovery-project-8t-9r-2022-07-27.4473983
Magisk apk - using stable from https://github.com/topjohnwu/Magisk/releases or using Canary from https://github.com/topjohnwu/magisk-files/tree/canary
Universal SafetyNet Fix (UNSF-MOD) by @Displax from https://github.com/Displax/safetynet-fix/tree/integrity
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
Boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it. Also install USNF if you are using Magisk Canary.
If you want to keep TWRP then install the TWRP installer zip.
Reboot.
If you are using Magisk Canary, in Magisk>Settings enable Zygisk, Enforce DenyList, and Configure DenyList. Then reboot.
Keeping Root on an incremental OTA update
Note: you do NOT need to (but can if you want to) follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you.
If your phone tells you you have an update:
If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot.
In Magisk tap on "Uninstall Magisk" and select "Restore images".
Install the OTA update but don't reboot yet.
Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root.
Reboot
When the phone has successfully rebooted the updated system, boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current recovery partition as you'll need it for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
If you want to keep TWRP then flash the TWRP installer zip.
Reboot and disable airplane mode.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggest this method (https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145) but this doesn't work for everybody (it doesn't for me).
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an OTA update
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
morphius88 said:
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
Click to expand...
Click to collapse
Best place for getting support for Magisk is https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
berthur said:
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
Click to expand...
Click to collapse
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
BillGoss said:
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
Click to expand...
Click to collapse
Than you!
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Wishmasterflo said:
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Click to expand...
Click to collapse
Download the zip from https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ and then use payload dumper to extract the files.
That worked like a charm. Thanks a lot.
I'm Magisk rooted and I have TWRP installed on my 8T EU model.
The OnePlus updater app registers that I am rooted and wants to download the full OTA.
Do I also have to do all the things you described after "Keeping Root on an OTA update" or is there a simpler way?
If yes, then I have a question regarding this step:
2. In Magisk tap on "Uninstall Magisk" and select "restore images".
Click to expand...
Click to collapse
Did Magisk automatically backup these images? Because I didn't do it myself. I only have backed up all my partitions (including boot) after I had installed TWRP and before I rooted.
EDIT:
BillGoss has thankfully already replied in another thread (in which I have basically asked the same question because I am an impatient bast***) where I suggested the overly present "easy" update scheme, which he expects to work. So this should be fine for other people in my situation:
1. Let the system download and install full OTA and DO NOT let the device reboot after it's done
2. Install TWRP A/B Retention Script
3. Install Magisk to inactive slot and reboot
EDIT2:
I just want to add that before having done the above mentioned steps 1-3, I have disabled all Magisk modules and rebooted the device. So the full procedure is the following:
1. Disable all Magisk modules and reboot
2. Let the system download and install full OTA and DO NOT let the device reboot after it's done
3. Install TWRP A/B Retention Script
4. Install Magisk to inactive slot and reboot
Youtube step by step video (he says that he "uninstalls" the Magisk modules but he just deactivates them):
Thanks @haitower
I've updated the OP to make it clear that the process described there only applies to incremental updates.
Also, to answer your question re Magisk backups: Magisk writes a copy of the installed boot image to /data/Magisk* before patching it. A "restore image" uses that backup.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" but this doesn't work for everybody (it doesn't for me) which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an incremental OTA update
Note: you do NOT need to follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
e1thx said:
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
Click to expand...
Click to collapse
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Hello!
Today I saw that EU: 11.0.12.12.KB05BA was available as OTA Update so I started to download it using the "Keep root on OTA Update".
During the download I recognized that I was still only connected to mobile network 4G instead of WiFi.
So I stopped the download of the OTA, restarted the phone and turned on WiFi but now I don't get the notification for the new OTA Update anymore and when checking for new Updates it says that my OOS 11.0.11.11 is up to date.
I guess the system has somewhere already stored that I started the download of the new 11.0.12.12 OTA but did not finish it and now I don't get the message to download it anymore.
Any idea how I can fix this so that I can download the new OTA again?
Thanks a lot!
EDIT: I am downloading it now via OxygenOS Updater (the full OTA).
BillGoss said:
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Click to expand...
Click to collapse
I understand that if I want to restore system and data when something doesn't work for me then I just do recovery for all the partitions, system, data etc that I do in twrp?
Please see the update in the OP regarding OOS 12.