Related
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
It seems like any knowledge I've had has atrophied. I purchased a Moto X Pure and had it activated by USC. I was able to get the unlock code through motorola and was able to unlock the phone.
One issue I did have was at times when I would type 'adb devices' it would just show 'list of devices' and nothing else. I was able to reboot the server and unplug/replug my phone to get it work. I went through the root process with twrp 3.0.2.0 clark.img and for some reason it was not reason seen as valid file, I ended up renaming it 'recovery.img' and then I was able to work with it. I also flashed XT1575-logo-new-9-14-15.zip from https://www.youtube.com/watch?v=iPspDlbRf88 as I was hoping to get rid of the Unlocked Bootloader screen. At this point, everything seemed fine
I was then able to flash SuperSU 2.46 and it basically seemed fine. (The adb 'list of devices' did present again, but when my phone was booted and I typed 'adb devices' it would find my phone, when I would go into bootloader I would then lose it but I was able to flash SuperSU). As I went to boot my phone after I would get the motorola logo, stay there for a few minutes and then go to a blank screen.
I am able to get to bootloader but am not sure how to proceed at this point. I may need some elementary directions as my stress level and my archaic knowledge seems to inhibiting me.
I would try flashing the stock boot.img, then see if it boots. Then flash SuperSU 2.62-3.
On this page I found (http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833) would suggest the 5.1.1 FIRMWARE or the STOCK Unrooted twrp backup? Sorry if my questions are basic but I ended up spending a lot of time just getting through each thing and my confidence is running a touch low.
I was able to install the stock firmware and am in the process of updating. Thank you for your thoughts. So from here if I pursue root again, it would be flashing twrp 3.0.0.2 again, along with SuperSU 2.62.3, correct?
Yes. Flash twrp. Reboot to recovery. Flash 2.62-3 SuperSU. Then reboot to system. It will boot to the bootloader unlocked screen. Then reboot automatically. Then it should boot like normal. Good luck.
ok, I tried again using twrp 3.0.2 and all was going fine. I did a nandroid back up and then flashed SuperSU-v2.65-20151226141. As it went to reboot, it went through the bootloader unlock screen and then got stuck again at the moto logo. Right now, I am flash the backup. Not sure what went wrong?
You clearly used the wrong su.
The most recent one that is not beta, thoughts on which is the right one?
Sent from my XT1575 using Tapatalk
Post #5
i rooted my device with the lastest supersu beta this week.
*Boot in to twrp, go to "advanced " then select "Terminal" type this in the terminal: echo "SYSTEMLESS=true" > /data/.supersu
* Press enter to confirm
*Go back to the install option in twrp.
*Flash the supersu.zip. and now the latest supersu will be forced to install supersu systemless.
*reboot your phone and in will normal boot with root access.
running stock 6.0.1
lafester, it looks like you were right. the SuperSu 2.62.-3 appears to have been the ticket. I verified with root checker and it worked. Thanks for your input.
clonesr1 said:
lafester, it looks like you were right. the SuperSu 2.62.-3 appears to have been the ticket. I verified with root checker and it worked. Thanks for your input.
Click to expand...
Click to collapse
This solved my issue also. I used BETA-SuperSU-v2.62-3-20151211162651.zip on 6.0 Moto X Pure
Life Saver
This fixed it for me, MANY THANKS!!!!! :good::good::good::good:
arnoslag said:
i rooted my device with the lastest supersu beta this week.
*Boot in to twrp, go to "advanced " then select "Terminal" type this in the terminal: echo "SYSTEMLESS=true" > /data/.supersu
* Press enter to confirm
*Go back to the install option in twrp.
*Flash the supersu.zip. and now the latest supersu will be forced to install supersu systemless.
*reboot your phone and in will normal boot with root access.
running stock 6.0.1
Click to expand...
Click to collapse
Ok finally got CM13 working, still have TWRP as bootloader, but I don't have root anymore, I used Arabics One click for root access, but now its not working at all, I have downloaded Yemans root program, but it says its incompatible now. So any help ?
Was your previous rom rooted ? Try to flash SuperSU in recovery and see if that helps (this should work, haven't tested it). Else you might need to flash stock LP, root it with the one click root and then install TWRP, flash CM13 and SuperSU right after that.
No, I just rooted the stock setup, then flashed to CM13, and that was the problem I forgot to download and flash the beta SU
If you have a true custom recovery, you always have root - or a way to get there without flashing back to stock.
On my (CM13) phone, the SuperSU app does not show up in the regular app drawer, but is available in the Settings main menu once it is installed.
(If you followed the instructions in the cm13 OP, you should already have SuperSU installed.)
I can't remember if you need to turn on developer options in CM13 to see this menu entry.
(Settings->About phone -> tap on "Build Number" 6 or 7 times)
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.
Hello,
I wanted to test the Engineering Mode and I followed the guide posted on twitter by fsociety (Used the adb method to enter the 'angela' code). Turning engineering mode on had no visible impact but on subsequent reboot, I lost root and Safetyet got violated (More specifically, CTS).
Setup:
OnePlus 5
OxygenOS 4.5.14
Magisk (latest)
This setup used to work fine and SafetyNet was intact. Things got bad after unlocking the engineering mode.
This is what I have done so far:
Tried *#8011# code to reset settings but I have no luck.
Re-installed the ROM (dirty flash)
Uninstalled Magisk and re-installed Magisk. (but still no root)
Installed SuperSU (systemless) but no luck rooting the phone.
Tried setting "setprop persist.sys.adb.engineermode 0" and "setprop persist.sys.adbroot 0"
Can someone tell me what I can do to fix this?
There's a debloat app in the themes and apps section. You can remove the engineering mode bloatware and see if that helps. You can also try a clean flash instead of a dirty one. If that doesn't work either you can always format your data with TWRP which will wipe everything on the phone except TWRP, use a computer to copy the ROM zip and Magisk to your phone and flash them in TWRP. If you do a clean flash or the latter I would set up the phone fresh instead of from an Android cloud backup because the cloud backup will restore some OOS settings and data and might restore your problem.
There are probably less drastic ways to solve your problem but I don't know them. Good luck.
It got fixed somehow. I ran the *#8011# code and used my computer to set the ADB properties. I flashed TWRP again and installed Magisk and bam! It worked!