Database Users

Rooting Stock XT1575 Marshmallow 6.0

This device seems to be a little trickier to root compared to my old Galaxy S3.
I just received a brand new Moto X Pure, XT1575 (North American variant I'm assuming since I bought it from the US).
It's currently running Marshmallow 6.0, and has been OTA updated to the Feburary 2016 security update.
I want to keep the stock ROM, but I want it to be rooted. XPosed would be nice as well, but not necessary. I do not want any custom ROMs, just the stock ROM rooted.

To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Fantastic advice!
Sent from my XT1575 using XDA-Developers mobile app

You'll have to use a very specific - older systemless root though. I think supersu-2.64, but I'll let someone else confirm that. The other superusers will not work.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Sorry I been away from the rooting methods for too long (since my note 2) I already unlocked the bootloader on my phone but to install twrp can I still follow this tutorial? TIA
https://youtu.be/iPspDlbRf88
Sent from my XT1575 using XDA-Developers mobile app

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Thanks!!! that little line of code for TWRPs built-in terminal did the work

rmaspons said:
Thanks!!! that little line of code for TWRPs built-in terminal did the work
Click to expand...
Click to collapse
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
It didn't work for me via adb command.... Had to use TWRPs built-in terminal. Just wrote wrote the line, as it is, go back to the main menu and flash Supersu (I used the latest one: 2.67) just as you normally do. Then reboot. No more stock in the M logo

jason2678 said:
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.
Click to expand...
Click to collapse
Thanks! This did work for me. I am now rooted.

I am using twrp 3.0.0.0 I used 2.62 however when I tried to click the option in the terminal keyboard for the = (equal sign) I keep getting a blue screen. 3.0 keyboard works ok. I entered the, echo "SYSTEMLESS=true" > /data/.supersu and pressed the go button. It showed up on the main terminal screen. Im a bit confused at this point....do I flash supersu from my pc using flashboot on the bootloader page? or download the supersu.zip to my phone and use twrp to flash it? When twrp asked to flash supersu I did that and wound up stuck on the big M again. I think I restored my phone about 6 times so far. lol

Flash in recovery. Use 2.62-3.

So using 2.62.3 will void having to type SYSTEMLESS=true" > /data/.supersu. or do u still have to type that in terminal? Plus using the twrp-3.0.2-0-clark. Should I use and older version?

No just flash.

Flashed Supersu 2.76 on top of xt-1575 18-4 image without any problems usung TWRP 3.0.2.
I did add .supersu text file to /data just as an insurance.

Nuts. Didn't see the part about doing a backup first (hitting head, as this isn't my first rodeo). Too anxious I guess. Now I'm stuck at the M android screen. (didn't do the "SYSTEMLESS=true" > /data/.supersu" command). Any way to fix or am I just screwed?
I can get to TWRP, so theoretically, I could flash a stock version of Android back onto it. Anyone know where I can pick one up?

Did the same ****. Was so excited getting the phone and didn't read the systemless =true crap for M. Didn't do a back up but got a system file from Motorola. You can pick one up here to start over. http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Anxiety might lead to unexpected results
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance

eat-man said:
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance
Click to expand...
Click to collapse
Not really sure what you need a video for, the process is simple and the same for all Gen3/4 Moto devices... the chanced of "breaking" something are near zero. You need fastboot working, that is on you.
1) Unlock the bootloader
2) Download the latest TWRP and SuperSU. Place TWRP img in your fastboot directory and SuperSU zip on your device so you know where it is, internal storage or SD card is not relevant.
3) Start the bootloader, either with `adb reboot bootloader` or power off and hold VOL DN and then press and hold POWER until the menu comes up
4) Start TWRP with `fastboot boot twrp-3.0.2-0-clark.img` and backup
5) Go to TWRP's Advanced menu and select Terminal
6) Enter `echo SYSTEMLESS=true>>/data/.supersu` press enter , exit, and Home button
7) Install (Flash) SuperSU ZIP file, clear caches if you wish but it isn't necessary.
8) Reboot
That is all there is too it

man u are awesome it took me a while and just stumbled on to this and u couldnt have made it less confusing

ADB Sideload SuperSU on encrpyted phone

According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!

Help withAndroid N Preview 5

Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker

You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !

TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.

Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.

The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.

Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)

I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.

TWRP bootloop after flashing TWRP Solved

Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.

Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.

I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.

Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.

Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis

mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.

EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.

cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.

Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.

moto x pure stuck on motorola logo after installing superSU?

so i recently got the pixel, had the moto x for about a year and decided to see what was going on with the rooting scene with this device. turns out that someone came along and created a simple solution to rooting and installing twrp for this device. I was happy. TWRP works just fine. But upon flashing SuperSU and rebooting from that i'm now stuck on the M logo permanently it seems. Yes i can reboot back into recovery and fastboot mode. But i can't seem to get past the M logo and all i've done was flash TWRP and SuperSU any idea about what's going on?

You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120

Spasticdroid said:
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
awesome thanks!!!! <3 now i just need to find a rom to play around with :3

silvernirvash said:
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
Click to expand...
Click to collapse
No offense, but why are you bothering to root if you are just going to flash a ROM?
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.

acejavelin said:
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
Click to expand...
Click to collapse
That's exactly what my zip does. I've only put it together to make the process much simpler, and I love automating stuff when it's possible.
SuperSU inside is unmodified. Updater-script copies a file named "systemless" from the zip which has "SYSTEMLESS=true" in it to /data, renames it to ".supersu", then proceeds flashing SuperSU.

Hello all,
I need some help!I have a Moto X Pure Edition XT 1575 I just unlocked bootloader and then intalled TWRP 3.1.1 and then installed SuperSU 2.79 and now no Sim is detected. What did I do wrong?
Thanks!

Unroot & clean with supersu app. It should restore boot image.
/You can also restore boot, system, wipe data in twrp/
Reboot & check.
If ok try rooting with supersu 2.82 or magisk 14. @kaleend101