Related
I've seen people talking about android pay working while being rooted and I can not get it working myself.
I've tried using the rootcloaker xposed module, and uninstalling xposed as well. Neither allows me add any cards.
I'm using a systemless root which I thought should help with this.
Any suggestions? I'm sure a ton of people are going to want to start using it now that Google is doing that ten tap deal.
Alex2x3 said:
I've seen people talking about android pay working while being rooted and I can not get it working myself.
I've tried using the rootcloaker xposed module, and uninstalling xposed as well. Neither allows me add any cards.
I'm using a systemless root which I thought should help with this.
Any suggestions? I'm sure a ton of people are going to want to start using it now that Google is doing that ten tap deal.
Click to expand...
Click to collapse
Loads of directions all over, but being I didn't know about that 10 tap thing and now I do, here ya go;
(this is what works for me...)
If your rom supports it of course, CM doesn't for example.
I'm using ElementialX and Cataclysm;
Flash Cat in TWRP
In TWRP issue these 2 commands via terminal, 1 forces systemless root and 1 deletes the folder that allows Pay to work;
"echo SYSTEMLESS=true>>/data/.supersu"
"echo BINDSYSTEMXBIN=false>>/data/. supersu"
flash su 2.66
flash ElementialX
Use app safetynet from Play --> https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en to test if Pay should work, it should show all green.
** You may want to flash UPDATE-unSU.zip if you have installed su before the above --> http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
ElementialX kernel requires flash of su before you flash it, Franco is after, so check your kernel.
That's kind of a basic flow, again, check your rom, my favorite, Benzo, does not support Pay.
If you have busybox, make sure you installed it to /su/bin/ and not /system.
jackpollard said:
Loads of directions all over, but being I didn't know about that 10 tap thing and now I do, here ya go;
(this is what works for me...)
If your rom supports it of course, CM doesn't for example.
I'm using ElementialX and Cataclysm;
Flash Cat in TWRP
In TWRP issue these 2 commands via terminal, 1 forces systemless root and 1 deletes the folder that allows Pay to work;
"echo SYSTEMLESS=true>>/data/.supersu"
"echo BINDSYSTEMXBIN=false>>/data/. supersu"
flash su 2.66
flash ElementialX
Use app safetynet from Play --> https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en to test if Pay should work, it should show all green.
** You may want to flash UPDATE-unSU.zip if you have installed su before the above --> http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
ElementialX kernel requires flash of su before you flash it, Franco is after, so check your kernel.
That's kind of a basic flow, again, check your rom, my favorite, Benzo, does not support Pay.
If you have busybox, make sure you installed it to /su/bin/ and not /system.
Click to expand...
Click to collapse
Thanks for the tip! When I update my rom or kernel do I need to enter terminal commands again?
Sent from my Nexus 6P using Tapatalk
Smallsmx3 said:
Thanks for the tip! When I update my rom or kernel do I need to enter terminal commands again?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Whenever I re-flash root for whatever reason, I do the commands, but not when I'm updating rom/kernel.
jackpollard said:
Loads of directions all over, but being I didn't know about that 10 tap thing and now I do, here ya go;
(this is what works for me...)
If your rom supports it of course, CM doesn't for example.
I'm using ElementialX and Cataclysm;
Flash Cat in TWRP
In TWRP issue these 2 commands via terminal, 1 forces systemless root and 1 deletes the folder that allows Pay to work;
"echo SYSTEMLESS=true>>/data/.supersu"
"echo BINDSYSTEMXBIN=false>>/data/. supersu"
flash su 2.66
flash ElementialX
Use app safetynet from Play --> https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en to test if Pay should work, it should show all green.
** You may want to flash UPDATE-unSU.zip if you have installed su before the above --> http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
ElementialX kernel requires flash of su before you flash it, Franco is after, so check your kernel.
That's kind of a basic flow, again, check your rom, my favorite, Benzo, does not support Pay.
If you have busybox, make sure you installed it to /su/bin/ and not /system.
Click to expand...
Click to collapse
Is it possible if I'm just running the stock rom rooted? Don't want to start messing around with roms and kernels yet, worried about relapsing into my flashoholic ways. haha
I feel like I can not ever find systemless root properly.
I recently reflashed the stock march security update factory image. I then reinstalled TWRP 3.0 and then flashed "BETA-SuperSU-v2.68-20160228150503.zip" found int eh thread below
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
however when i booted, I wasnt systemless I was full root with the SU app and everything. i was able to unroot and now android pay works.
i would like to install SYSTMLESS ROOT what ever the latest is so that i can remove the XBIN folder and use the CHMOD trick to get androidpay working but I just cant seem to find the actual systemless root.
i end up digging around like 3 or 4 different SU threads and its frustrating lol.
is the BETA-SuperSU-v2.68-20160228150503.zip the systemless version?
thanks!
2.68 is the one I flashed from TWRP,, but before I applied the zip I accessed the Terminal in TWRP and typed
echo "SYSTEMLESS=true" > /data/.supersu
Then I flashed the supersu.zip. Rebooted to system then used Root Explorer to change the permissions of /su/bin to 751. Removed the xbin_bind folder. Restarted and it was systemless root.
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
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
ap4ss3rby said:
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
Click to expand...
Click to collapse
Very cool :good:, could you provide a link and maybe some further informations?
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting sure is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
ap4ss3rby said:
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Click to expand...
Click to collapse
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
daktary said:
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
Click to expand...
Click to collapse
Fingerprint still works, but root access very rarely works, but SuperSu does install, and for installation:
In a nutshell unlock the bootloader, flash twrp, get supersu v2.82 flashable zip on the sdcard, install the latest available app from apkmirror, and you're done
just got nougat in the UK, and i was wondering if i can get twrp and root on it. The answer is probably yes but i just want to make sure, thanks
yes, i did it today
fliperpl said:
yes, i did it today
Click to expand...
Click to collapse
Thanks, good to know. Might wait on it, as if i do this and theres a new update im screwed
What about Systemless Root?
CLETjB said:
What about Systemless Root?
Click to expand...
Click to collapse
magisk works without problems
Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.
lmulli said:
Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.
Click to expand...
Click to collapse
Thanks a lot! The only problem was that suhide doesn't seem to want to flash. However my root works and so does my snapchat
Edit: Logging out of snapchat wont let me log back in? So is there any way to hide the root?
Edit 2: Nvm. You have to flash SuperSu-SR4 instead of the normal 2.82 one. I was now able to flash suhide and get everything working