Related
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Thank you! It's working!
Perfect, It's working!
Working,great
Sent from my XT1068 using Tapatalk
Where can we get the stock boot.img for Marshmallow?
If u r running stock mm, then ur boot.img is also stock.
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
mandar91 said:
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
Click to expand...
Click to collapse
It is recommended to use stock boot.img
gauravrai said:
It is recommended to use stock boot.img
Click to expand...
Click to collapse
BUT currently i m on cm 13
Failed Root with XT1064 6.0
Everything ran smoothly installing the zip from TWRP, but on reboot: no SuperSU; no root. Now warnings or errors came up in the TWRP text during root.
MotoG 2014 XT1064
System: 24.41.34 titan_retuaws.retuaws.en.US retus
Kernel version 3.4.42-gef77327
TWRP-3.0.0-0-titan
Installed zip: BETA-SuperSU-v2.62-3-20151211162651.zip
Device is unlocked. Status Code 3
Update to 6.0 was with OTA after flashing the stock rom using XT1064_TITAN_RETUAWS_5.0.2_LXB22.99-24.12_cid9_CFC.xml.
The phone was previously 5.0.2 Rooted.
I did not lock the bootloader during the process.
The OTA to 6.0 went smoothly.
Followed the above instructions to the letter....
The only thing odd I did was uninstall the SuperSU App on the phone before flashing TWRP and starting this Root operation.
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
fidorulz said:
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
Click to expand...
Click to collapse
This will work on all Moto devices running stock marshmallow.
Root Moto G2 running on Official 6.0 Android Marshmallow Without (modified boot image)
https://youtu.be/9_9vkJvzWcU
Every time i remove system apps it boot loop any work around for this in marshmallow.. In lollipop removing system apps can normally booted up without any problem..
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
wildingol said:
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
Click to expand...
Click to collapse
Now over 2.62 supersu u can also flash any upgraded version like stable or any latest beta.
Sent from my XT1068 using XDA-Developers mobile app
Confirmed working on TWRP 3.0.0.1, stock Marshmallow 6.0 from OTA updates. Every other SuperSU got stuck on unlocked bootloader screen.
Thanks!
gauravrai said:
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Click to expand...
Click to collapse
VIDEO TUTORIAL:-
https://www.youtube.com/watch?v=9_9vkJvzWcU
Work !
---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------
Work thanks
i Tried this on Xt1072 Moto G 2nd Gen 2014 LTE and had to use the UnSu first as per the instructions and for the reasons described in red. I was also stuck in bootloader with that horrible message that says your bootloader is now unlocked! Now the issue is I seem to be stuck on the Motorola hand stitched by peter crawley boot screen? I saw someone aske dhow long this lasts? I had to use an OTG usb flash drive to get my files on to the damn phone for some strange reason phone and pc having massive communication issues, not playing very nicely with each other????? wtf? anyway I got okays and successful messages when in TWRP 2.8.5.0 I just dont understand why there seems to be such a huge problem with getting this f"£$%^&*g phone sorted.
Nexus 5 rooted and flashed with the beautiful elemental x kernel, why cant we get elementalx for moto g? its absolute genius! now someone tel me what the hell is going on here, when will I ever have success with this damn phone? I hate bloat and it only has 8GB plus the sd card which is configured as internal storage, could this be what the problem is?
I am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
WTF? said:
I am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
Click to expand...
Click to collapse
Unlock your bootloader, which will void warranty.
Flash TWRP to your recovery partition via fastboot
Make sure you boot into TWRP first, then back into system
Install Magisk Manager, then download the latest version of Magisk through the app
Reboot to recovery the BACK UP EVERYTHING
Install the Magisk zip located under /MagiskManager
Reboot to bootloader
Flash stock recovery
Reboot to system
NOTE: If you cannot boot after Magisk is installed, you will need to restore your boot partition from within TWRP.
Personally, I don't think you should root and keep up with OTA, it may brick your system with root. (Never happened to me, I've only seen it happen)
Hit thanks if I helped.
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.
Ahhh... so it somehow got locked back and need to redo the procedure?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????
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?
Hi - I have a rooted OP6T on OOS 11.1.1.1.
I want to upgrade to OOS 11.1.2.2, but I am trying to keep root. Installing TWP would be nice, but not mandatory. I definitely don't want to lose my configuration / data during the upgrade.
Can I do it?
I have upgraded my OP 7 Pro to OOS 11 using Payload Dumper and a Magisk patched boot.bin file. Is the process the same with the OP6T?
Thanks!
@¿GotJazz?
Hello,
yes you can,
this is what i done at every update...
Disable all the Magisk modules
and the securities (fingerprints/pin, etc)
Let the OTA comes and install itself.
Do NOT reboot, instead open the Magisk
manager and via internal modules flasher
install the TWRP .zip, (i'm using 3.5.2_9-0,
but there are newer ones).
Do NOT reboot.
Open Magisk again and select install,
then install to inactive slot (after OTA).
When that's done you can reboot your phone
with lastest firmware, TWRP, root and untouched data.
Configure your securities and reinstall your modules.
Cheers
@¿GotJazz?
I saw that you also posted in other threads
with slight variations and the bootloop slot issue.
Well, if I were you I would not risk it
and I would proceed first with a backup
of the important stuff, then
I would use MSM tool with rollback
to the android 10 version, re-root it
via Payload Dumper or using a pre-patched image
and upgrade to android 11 with the method
I have already told you.
Let the community know how it went and
good luck.