Related
http://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
Changelogs
10.05.2016 - v2.72 - BETA - RELEASE NOTES
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
Yes, baby !
wow! That's a surprise!
BaristaBot said:
wow! That's a surprise!
Click to expand...
Click to collapse
Indeed .. but now we have support.
Just tested 2.72 .. works perfectly.
Installed stock boot.img via TWRP and Supersu.zip directly afterwards ..
Supersu.zip is perfectly modifying the ramdisk and re-signing the kernel to chromeos.
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
Install it via TWRP, just before the supersu.zip installation.
No reboot required, nothing.
Download from here ..
http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Running on 2.72 now ... we don't need to build any stock rooted kernels anymore.
Don't be surprised .. after Supersu.zip installation the first boot will look like bootloop, but only once. Same like on other devices as well.
Cheers
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
@NYCHitman1 @cheep5k8 Did you see this? Great news eh?
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Great! I'd like to give the N preview a try now, too. Could you please elaborate on how you achieved root with the new SuperSU? Did you have to reflash a custom recovery after flashing Android N?
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
scoobydu said:
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
Click to expand...
Click to collapse
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
followmsi said:
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
Click to expand...
Click to collapse
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
For me on a previously unrooted encrypted device I couldn't get it to work by just installing it and supersu, no.
But that may have been user error on my part, but my guess is that encryption was causing an issue with just the v2 TWRP installed as it could not see my data partition, even after a format.
scoobydu said:
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Click to expand...
Click to collapse
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
Yes, it doesn´t solve the problem ..
There were no encryption related changes in this TWRP release.
But .... we have a new SuperSU now ..
Look here .. should be tested from the encryption fans .. Maybe this works on Pixel C too.
http://forum.xda-developers.com/htc...bootloader-t3365986/post66837323#post66837323
EDIT 2: Figured I might as well detail my complete procedure here, so others can confirm whether it works for them (or not):
Unlocked bootloader via HTC Dev
Flash TWRP
Boot into TWRP (Cancel decryption prompt & leave system read-only on boot)
Backup "Boot" and ""System Image" in TWRP to External SD
Wipe - Format Data (or Wipe Encryption) in TWRP
Boot device and let it re-encrypt
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPFORCEENCRYPT=true>>/cache/.supersu
Flash BETA-SuperSU 2.72 from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs
Do the SunShine
Boot into TWRP, restore stock boot and system image backup & Wipe - Format Data (or Wipe Encryption) again
Reboot device and let it encrypt again
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPVERITY=true>>/cache/.supersu (the file should still be there, so both commands will now be present)
Flash BETA-SuperSU 2.72 (again) from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs (again)
Now you're rooted, with pristine stock system image and with forced encryption and dm-verity still enabled. In this state, you should be able to Download OTAs, use Android Pay, etc.
Inside the SuperSU.zip are more informations ...
Overridable variables (shell, /system/.supersu, /cache/.supersu,
# /data/.supersu):
# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)
# PATCHBOOTIMAGE - Automatically patch boot image? (true/false,
# SYSTEMLESS only)
# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)
# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)
# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false,
# SYSTEMLESS only)
# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE
# only)
# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)
# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/
# false, PATCHBOOTIMAGE only)
# Shell overrides all, /data/.supersu overrides /cache/.supersu overrides
# /system/.supersu
Hope this helps .. but the external sd card could be tricky.
Cheers
followmsi said:
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
Click to expand...
Click to collapse
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
Click to expand...
Click to collapse
If you are on stock and unrooted it works the way above.
Sorry, I am not sure on encryption now.
Removed it on the first day.
Before copying SuperSu to data .. just followed the guide.
Needs to be verified if 3.0.0.0 version from xceed is able to access encrypted data ..
Sorry, can't help you better here ...
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
Click to expand...
Click to collapse
I saw only the first part of your answer ...
You got recovery boot-loop after installing TWRP ?
Never had any reboot issues, but I had always unencrypted data partition and could access my SuperSu.zip - all the time.
Never had to reboot without unchanged fstab nor stock kernel, as was able to flash SuperSu all the time.
As said before, I did remove encryption directly.
I did use xceed kernel for this .. some time ago.
Needs to be checked if xceed 3.0.0.0 TWRP has also problems to boot into system with stock kernel, was always used with xceed kernel together.
Version 3.0.2.0.img is using xceed only settings.
Version 3.0.2-0_v2.img has some parts from NYCHitman1 included.
Needs to be verified...
But we may need to adapt the instructions .. and may still need a stock rooted kernel for initial SuperSU installation.
Uploaded new TWRP version .. as TWRP flashable zip !
Just install this version with your current TWRP version and reboot to recovery again.
Have a look .. OTG is working now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Just made a fresh backup to my usb-stick via USB-OTG ..
Cheers
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Is your device still encrypted ?
Did you format the /data partiton inside TWRP ?
How did you access the SuperSu.zip file inside TWRP ?
Did you install other kernel for intermediate reboot into system to decrypt data ?
A lot of questions .. but it helps to understand problems better
Thanks
I just successfully rooted the Android N beta with this!
I upgraded from Preview 2 via flash-all without wiping data.
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
hartleyshc said:
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
Click to expand...
Click to collapse
Thank you for your quick reply!
Is it bad that it is already flashed permanent? Or do I need to flash original recovery again?
I'll try and sideload it. Haven't done that before.
bokkoman said:
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Click to expand...
Click to collapse
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Funk Wizard said:
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Click to expand...
Click to collapse
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
bokkoman said:
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
Click to expand...
Click to collapse
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Funk Wizard said:
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Click to expand...
Click to collapse
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
bokkoman said:
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
Click to expand...
Click to collapse
As and when the update comes, just let the system download and install the zip. It will auto download and install the full zip when it detects root/system modifications, just make sure you uninstall/deactivate all mods/magisk modules/ substratum overlays before you update. You can check for easy instruction on the third post of the update thread. I will update the thread as and when the OTA is released.
Also you guessed it right the update will unroot the device so you have to root it again so you can either do the same sideload way or just do it from the magisk manager - uninstall - install ota (do not reboot) - install magisk to second slot - reboot :good:
I will again update the detailed instructions for easy understanding and and when we have the update :good:
Just stay subscribed to the update thread :good:
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).
Dears, what is the correct procedure to install OTA updates if you are rooted? I mean without losing MAGISK & TWRP.
nithinte said:
Dears, what is the correct procedure to install OTA updates if you are rooted? I mean without losing MAGISK & TWRP.
Click to expand...
Click to collapse
Search my thread in Guide and News section
FunkWizard has a good Guide (link), use the TWRP instructions. It's in the same thread you can download the OTA zips from.
nithinte said:
Dears, what is the correct procedure to install OTA updates if you are rooted? I mean without losing MAGISK & TWRP.
Click to expand...
Click to collapse
Run update - dont reboot , launch magisk and add twrp.zip as a module - dont reboot , in magisk home "window" press install (on top) then press install to second slot (OTA) - reboot
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.