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?
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
omino said:
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
Click to expand...
Click to collapse
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sure, to be on the safe side, either flash stock ROM then apply all OTA updates as you suggest. Otherwise, one can take a backup of the system partition too. I am not sure why OEM would be modified... but if that is the case, I guess it can be backed up as well.
As a side note, OTA updates from Motorola are downloaded to the following folder: /data/data/com.motorola.ccc.ota/app_download
It is always a good idea to back up the ROM to SD card before applying it, especially for full upgrades (which contain all partitions). That way, it is easy to flash the latest working ROM.
As for the Magisk modules, I had your same experience. It's just my preference to install them through TWRP.
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Wolfcity is right. From my own experience ANY use of TWRP (i.e., booting or flashing) modifies the OEM partition and prevents OTA from succeeding.
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
ctwftp said:
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
Click to expand...
Click to collapse
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
ctwftp said:
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
Click to expand...
Click to collapse
No. You have to be on untouched stock firmware incl stock recovery to capture OTA.
Sent from my Moto G5 Plus using XDA Labs
Still need to load up both twrps?
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
TimelesslyPrecise said:
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
Click to expand...
Click to collapse
As the latest official TWRP has the decryption issue fixed it should work. Imo this guide won't work, a complete flash of stock is needed as I wrote before.
Sent from my Moto G5 Plus using XDA Labs
For some reason I could not get a backup of system and boot...
Ended up noticing a few issues with aosp, so flashed to lineage. Pretty smooth so far.
Been out of the game for awile, but it's coming back.
How G5 plus could be rooted.
Hi all,
So I am new to the game, I had an old(ish) phone and attempted to root the device. As some of you might have read on here before, I failed, I thought I had followed all the correct steps. I used the following steps as a guide: (from the unlockr). After attempting to install supersu I was left with a black screen. I can however access my recovery mode in bootloader, the thing is that bootloader is the only thing I can access. I cannot access my moto g4 plus via USB on windows, but for some reason I can access both internal and external memory on a mac. I can see the supersu version, my TWRP etc. I was wondering if someone could help me out, I know this has probably been posted before but I have not been able to find a possible solution as of yet. Thanks in advance
Is your device running stock Nougat (7.0) firmware? If so, then attempting to root on the stock Nougat Motorola kernel may result in a black screen and failure to boot, which appears to be what you've experienced. What those guides generally fail to mention (as they're quite old) is that rooting on the G4/Plus running Nougat requires flashing a custom kernel before you root. Failure to do so appears to trip the anti-rooting measures built into the stock kernel. A more recent guide that I've used for a stable root on a G4 Plus is this https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Bear in mind you do not need root to flash custom ROMs whatsoever, just TWRP.
If you can still access TWRP, you may have a way out. One thing to try is to flash a custom kernel onto your device - ElementalX is a good choice. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX v2.0.1 for stock . Download the kernel to your computer, ensure your device is connected to your computer and booted to TWRP, and copy the custom kernel to your device. Try to flash the kernel and then see if your device boots.
If your device still fails to boot, you could try flashing the stock kernel from your backup (you did make a backup before rooting?) or if you're running a more recent OS build, I've uploaded the Feb 2018 and April 2018 security patch stock kernels here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M To flash this in general:
a)Download the kernel boot.img to your device.
b)In TWRP, tap Install.
c)Tap Install image at the bottom of the screen.
d)Navigate to where you downloaded the boot.img and select the image file.
e)Target the image to boot (not recovery).
f)Flash, and wipe cache.
g)Reboot and see if that works.
If those don't work, restore your backup if you made one or you may have to re-flash your stock firmware - you do not have to re-lock your bootloader or wipe your device with this re-flash of the stock firmware.
Does your Windows computer have the correct Motorola USB drivers installed on it? https://support.motorola.com/uk/en/drivers
I just purchased the ph1 and plan on rooting the device and also flashing twrp. I've found the guides and everything seems pretty straight forward. The phone should be arriving tomorrow so at this point I'm unsure of the build it will have when I receive the device. I noticed a thread regarding the February update not working with twrp. Has this issue been resolved or will I need to flash to the January version to complete the task? Is the February and January builds mentioned the most recent updates for the device? I've found the links to the essential website but it gives me a error that its server IP cannot be found so I've been unable to check it. Is the site going to be down indefinitely due to no longer supporting the device? Does anyone have a link to the updates hosted elsewhere? The device was listed as GSM unlocked and did not mention any carrier tied to it so I'm assuming it's a factory unlocked device but will have to verify upon receiving it. Is the updates carrier dependant or do they all utilize the same files? Whats the consensus on roms/kernals on this device as opposed to rooting and using twrp on the most recent stock builds? Which Rom would you recommend if I do decide to go that route? Thanks for any advice you can offer, it's greatly appreciated.
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
SirDigitalKnight said:
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
Click to expand...
Click to collapse
I ended up receiving the device and it had Android 8 out of the box. I received a update that took me to Android 9 which was roughly 1100mb and another to Android 10 which was a little over 1000mb. The second update automatically included the February security patch. Rather than downgrade to January, I simply patched a February boot image with magisk and flashed with fastboot. I also flashed ElementalX kernel via fastboot. As far as I can tell they are not carrier specific. I am considering going to January now so I can use twrp to test some custom roms. For downgrading to January do I simply flash the January boot image which shows to be about 65mb or do I need to find the firmware in it's entirety? Also rather than down grade and use twrp can I just flash custom roms via fastboot? I would say you might have to downgrade to January to use twrp to flash Android 11 unless it's possible to flash the roms on fastboot, hopefully someone chimes in bc I'm unsure at this point.
Noob question, but what's the advantage to changing just the kernel?
Coming back to XDA after over a year. Realized Google Play Store update ruined my Magisk status, and evetually root (SafetyNet stuff). Here are some notes I took while I flashed in 2019, hope it helps.
1. DISABLE Security (PIN/Pattern/Fingerprint)
2. Backup Internal Storage
3. Boot to recovery TWRP, and backup nandroid.
(must go to bootloader and change slot to boot twrp.img flashed on that boot partition slot)
4. Normal boot and drag drop nandroid backup to PC.
5. Syncthing/Resilio for extra measure.
Have latest OTA.zip, boot.img (same version as OTA.zip), and latest Magisk.zip in root internal phone storage.
Have twrp.img in platform-tools adb root for flashing in fastboot.
twrp.zip is optional stored in root internal phone storage.
Flash OTA.zip update in TWRP. (assuming system is under slot_b)
This will flash to opposite slot, _a.
(I flashed under slot_b and new OTA went to slot_a, I booted back to _b and
old system version remained with broken Wifi becasue I accidentally flashed new boot.img in TWRP image over older system image
in slot_b, without the image flash, I suspect the old slot_b would have been perfectly untouched and rooted, as OTA applied to slot_a)
(Went back to A and new OTA was perfectly fine, although unrooted).
Boot to slot_a (system_a), make sure it runs good and verify version within settings, should be unrooted.
Boot to bootloader (under same OTA slot_a), default recovery should be stock recovery (droid logo) after OTA flash.
fastboot flash boot twrp.img (this will replace stock recovery to twrp recovery, deleting stock boot img as well, breaking OTA slot)
Reboot to recovery twrp (remain on same slot and will run off of RAM, leaving boot partition open to flash back stock boot.img)
Install boot.img (make sure version is correct) boot partition should be back to working condition although unrooted OTA system.
Try booting back to recovery on same slot, and stock droid recovery is back. (you cannot edit partitions from fastboot, hence twrp flip flop)
Try booting to system, it will boot but broken, no wifi. How? Not sure, maybe used old boot partition .img in slot_b to boot to system_a
Then flash latest magisk zip to patch stock boot.img for root.
(if you flashed twrp.img and magisk, then you're patching twrp, which is incorrect.
You want to boot to twrp, then flash boot.img back to boot_a partition, then run magisk.zip to patch stock boot.img in that boot_a partition)
Magisk.zip flash log:
Current boot slot: _a
Mounting system
Mounting vendor
Device is system-as-root
System-as-root, keep dm/avb-verity
Encrypted data, keep forceencrypt
Target image: /dev/block/sde11
Device platform: arm64
Constructing environment
Boot image is signed with AVB 1.0
Unpacking boot image
Checking ramdisk status
Stock boot image detected
Backing up stock boot image
Patching ramdisk
Repacking boot image
Flashing new boot image
Sign image with test keys
Unmounting partitions
Done
Updating partition details...
...done
Wipe cache/dalvik
In TWRP, tap reboot button and switch slot_a to other slot_b (older system version).
Reboot to bootloader_b in TWRP.
Flash twrp.img in that other old slot_b (For backup purposes and to have twrp at hand because boot_a has patched rooted boot.img and not twrp anymore)
Done!
Click to expand...
Click to collapse
I have moto x play xt1562 and on this page i see that there are different unofficial TWRP versions. Which version i have to install? ALso, if i have other custom recovery already installed, like linage custom recovery, do i have to take and precautions?
hi peter,
it depends on which image you want to install. since may 2020 there is a bug in twrp which no longer starts the phone with the ota update.
if you want to backup, delete or install your partitions you can install the current version 3.4.0. when you have everything set up you either have to import the updates manually or use its recovery as with lineage. twrp should also work in version 3.3.0 (or any other version before may 2020).
I am currently using the lineage with lineage recovery and it works. should you need more settings for the recovery you can simply boot twrp without installing! thus it is possible to set everything in twrp and still have the lineage recovery because of ota on the device.
if you want the recovery boot (no install) you have to execute this command:
Code:
fastboot boot twrpname.img
cheers