Database Users

[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img

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?

OP2 cannot upgrade from Oxygen OS 2.2.1/Cannot flash TWRP versions newer than 3.0.2-0

So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.

Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.

Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:

Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!

Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?

Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.

thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.

Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?

Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,

Issue with Magisk and OTA version 7.1.2

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?

I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.

Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.

It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.

ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.

_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?

ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).

[GUIDE] How to root Stock Oreo 8.1 soak test with magisk

I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
INSTALLATION
1.back up your system, data and boot partition. If the process fails restoring those will revert the changes.
2.Download and flash Magisk 15.3 (later versions didn't work for me, phone wouldn't boot at all) through twrp.
3.Flash the latest f2fs loop back work around.
4. Flash magisk manager for recovery (mm-2018.8.1.zip attached below)
5.Boot your phone
UPDATING TO MAGISK 16.0
Once the phone has booted:
1.install magisk manager 5.8.3 (attached below)
2.Open magisk manager
3.if any update is available for magisk manager, install it.
4.click on the button that tells you to update magisk to latest version.
IMPORTANT:
5. Select the direct installation method. Flashing the update through recovery will render the phone unable to boot again.
That's it, thanks.
=======
Downloads:
Magisk 15.3
f2fs-loopback-bug-workaround-2018.8.1.zip
mm-2018.8.1.zip
Magisk Manager v5.8.3.apk

freeZbies said:
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
....snip
Click to expand...
Click to collapse
Interesting.
For what is the magisk manager for recovery needed?

Wolfcity said:
Interesting.
For what is the magisk manager for recovery needed?
Click to expand...
Click to collapse
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
EDIT: Mm for recovery is actually a module that allows you to list and Uninstall modules from Twrp in case your phone no longer boots after flashing a module.
and you're correct, magisk 15.3 does include magisk manager and will install it. the problem I had is that I flashed magisk 15.3 over a system where either the boot.img was already patched, and I experienced that magisk manager sometimes wont be installed in these cases
Sent from my Moto G (5) using Tapatalk

freeZbies said:
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
Click to expand...
Click to collapse
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.

nicolap8 said:
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
Click to expand...
Click to collapse
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.

freeZbies said:
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
Click to expand...
Click to collapse
At least it's inside the official 15.3. But I remember that MM was often not installed in earlier builds.
Sent from my Moto G5 Plus using XDA Labs

I Got Another Method Also
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy

Sonisudhanshu said:
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Click to expand...
Click to collapse
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Sent from my Moto G (5) using Tapatalk

freeZbies said:
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Click to expand...
Click to collapse
I'm on 3.2.2.0 and it offers the ability to backup EFS, 3.2.1.0 also.
As said, for persist there are several unofficial builds but you can back it up with those commands in TWRP terminal:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
for backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
for restore.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
1. Because I didn't have any option to backup efs in twrp.32.bit
2. I was not sure but I just flashed it so that no problem occurs like booting issue..
Hope this helps

Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming..... If this helped , i would be gladed

Do the magisk modules work ?

llucas_br said:
Do the magisk modules work ?
Click to expand...
Click to collapse
Which magisk module?
Sent from my Moto G5 Plus using XDA Labs

TWRP flashable Oreo 8.1 OTA updates
Sonisudhanshu said:
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming.....
Click to expand...
Click to collapse
There are already TWRP flashable Oreo 8.1 OTA updates available.
https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913

thanks

Chekm8Qc said:
I just installed magisk 17.1 and it worked right away. Even safety net passes.
Click to expand...
Click to collapse
Chekm8Qc confirmed here https://forum.xda-developers.com/showpost.php?p=77906610&postcount=56 that he could directly install the latest Magisk version (currently 17.1) on Oreo 8.1 OPP28.85-16 eliminating the need to install an older version first as recommended in this thread.

I can also confirm, installed straight away 17.1 and worked flawlessly, no bootloop and safety net passed.

Please Update!
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080

G5-User7080 said:
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
Click to expand...
Click to collapse
in oreo stock you dont need f2fs bug module, because is working without it

[GUIDE] Root OOS with TWRP

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.