Has anyone tried simply flashing a custom recovery, then using the recovery to flash SuperSU as a way to gain root access?
Or do i need to find a rootable kernel somewhere?? I google this issue alot recently, and just want to find out if someone has done this successfully. Odin is killing me because no matter what i DO try to flash using it, fails... other than the Stock Android 5.0.1 firmware. Am i missing something, or can someone give me directions to the simplest instructions possible to gain root on it. I know this has been asked alot, but most solutions i have found have only been for other carriers, and lower builds of the firmware. I would be willing to downgrade to KitKat if necessary... but also that seems impossible because the bootloader blocks downgrades... Please Help
Worked Like A Charm
So its done!! Simple and easy... Three steps! (make sure to copy the newest SuperSU file to your sdcard first)
***Boot into ODIN Download Mode***
1. Using ODIN flash TWRP 2.8.4.0 (dont let it reboot on its own afterwards!... YOU MUST BOOT INTO RECOVERY ON YOUR OWN THE FIRST TIME TO LET TWRP PATCH THE ROM)
2. While in TWRP recovery, then install SuperSU zip file from your SDcard
3. Select reset and perform the "Factory Reset" option.
!!! Success... !!! you now have a rooted Sprint S4 with the OF1 build of lollipop...
*********Credit to "bilgerryan"
For the proper process to use!
:laugh:
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?
hi I have bootloader unlocked and root, I downloaded nougat 7.0 firmware and tried to update manually, but allways error.
someone knows how to do?
You need to unroot first, if you have twrp, you need to flash the stock recovery. Make sure you download the correct one. Z017d. Once done, copy the nougat zip file, go to recovery and flash the zip file
Download stock img and install. Once installed, reboot. Click the volume button once you get to bootloader click recovery. In the stock recovery wipe cache if you want, this is preferred to prevent any issues. Then update via micro sd.
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
Should the phone must be rooted before instalilng CR or ROOT can be install of the trough CR instalation procedure (eg magic). Thanks
Your phone doesn't have to be rooted to install a custom recovery (I assume that's what you mean by CR). However, a custom recovery is required to flash either Magisk or SuperSU.
Flash a custom recovery using Odin first, then boot into recovery and flash the flashable zip containing a superuser management tool of your choice!