Related
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?
My XZU kitkat 4.4.4 .108 have rooted. Stock rom. I want to set Ext SDcard for Titanium Backup. But I can't access permission (etc/permissions/platform.xml) to change to writeable. I have tried Root Browser, Root Explorer, Solid Explorer and ES File Explorer. All no luck.
It pop up error ***operation failed message: cannot write to filesystem. Mount as read/write has failed***
But I have success to my rooted TabPro 8.4 SMT-325. Kitkat 4.4.2 with Solid Explorer or Root Explorer.
Another problem is I can't install busybox.
Any help or input
Thanks
Hi there,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
talongt said:
My XZU kitkat 4.4.4 .108 have rooted. Stock rom. I want to set Ext SDcard for Titanium Backup. But I can't access permission (etc/permissions/platform.xml) to change to writeable. I have tried Root Browser, Root Explorer, Solid Explorer and ES File Explorer. All no luck.
It pop up error ***operation failed message: cannot write to filesystem. Mount as read/write has failed***
But I have success to my rooted TabPro 8.4 SMT-325. Kitkat 4.4.2 with Solid Explorer or Root Explorer.
Another problem is I can't install busybox.
Any help or input
Thanks
Click to expand...
Click to collapse
Did you install nut's dual recovery by chance? It has busybox included and if you try to install another busybox it screws up root. For SD card try this app, if you are still rooted and have superuser installed properly it should work.
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
adfurgerson said:
Did you install nut's dual recovery by chance? It has busybox included and if you try to install another busybox it screws up root. For SD card try this app, if you are still rooted and have superuser installed properly it should work.
What's nut's dual recovery?
I did try SDFix already, it doesn't work to me.
The purpose I need access permission is modify platform.xml for Titanium backup and mixer_paths.xml for volume boost headphone.
I heard about a custom rom can access permission mostly, is it true? If yes, I might try flash to custom rom.
Click to expand...
Click to collapse
If SD card fix doesn't work and gives you an error message. You don't have true root access.
I know because I faced this issue about a month ago, I was able to get superuser access just not edit files I know because I tried to edit the platform as well, so re-root your phone and install the dual recovery (optional?) if you make it that far, run kk fix it should work.
The volume boost is meh, you're better with viper4android
RealityFails said:
If SD card fix doesn't work and gives you an error message. You don't have true root access.
I know because I faced this issue about a month ago, I was able to get superuser access just not edit files I know because I tried to edit the platform as well, so re-root your phone and install the dual recovery (optional?) if you make it that far, run kk fix it should work.
The volume boost is meh, you're better with viper4android
Click to expand...
Click to collapse
The root checker show **device have rooted**
I used Easyroot. Does your meaning use easyroot to re-root the phone again? Or get another tool? Any rooting tool suggestion.
Should I unroot from supersu before re-root?
Yes I know that.. Like I said I had the same issue, you may have root access but you don't have true root, so re-root your phone. It will fix the issue.
So again re root your phone.
And for me I did not uproot I just ran the root exploit and overwrited the old su
Great! I'll try to root again tonight.
BTW, is your device is XZU and root by Easyroot.
Thanks
Nah I have galaxy s2 but posting in xzu section. Yes I have Xperia Z ultra. And yes I did the easy Xperia root, plus I have dual recovery
IT WORK !
As you said re-root device again. Access permission available and Titanium backup to extsd.
Thanks all you guys input.
Zomg don't forget to thank me, hit the thanks button. *sarcasm
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
jgummeson said:
Guys,
I made a post a couple of days ago over on the 5x forums: http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659. With this permissions fix I have Android Pay working without having to enable/disable root in the SuperUser app. Hoping it will work on 6p as well.
Anyone willing to give this a try on the 6p? You would need a stock ROM (or possibly another ROM that previously worked prior to Google's recent change that broke it) with systemless root installed (I'm using 2.67). Basically all you need to do is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
So far this has worked for me and a couple of others on the 5x (both adding cards and making purchases). Let me know if anyone can confirm that this works on the 6p.
Click to expand...
Click to collapse
I just did it with Root Explorer. I changed the permissions for the /su/bin folder to 751. SafetyNet checks are passing now, but I haven't actually tried to purchase anything.
Worked on pure nexus after setting the permissions as suggested.
yep, purenexus, systemless, updated via terminal emu, works fine as of right now.
Worked with Chroma Rom using Root Explorer to change permissions. SafetyNet checks pass. Haven't set up AP yet . Will try that tomorrow.
Worked for me. Was able to pay for groceries.
Not working for me, used skipsoft toolkit to install systemless root.
Edit: Figured it out, still had the xbin_bind folder. Made a zip backup of it and deleted the original, safetynet passes now.
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
Reboot
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
i called google and they said it might actually be a syncing issue and that removing the card completely from your account (login web browser and account settings then remove card).
Se7eN43 said:
I've been on Pure Nexus 1/09 build with systemless SuperSU 1.61. Never had Android Pay working.
Without doing a clean install,
flashed busybox in TWRP.
Reboot
Made the permission changes using Root Browser.
SafetyNet passes.
Installed Android Pay, added card.
Used on soda machine.
PROFIT!!!
Thank you OP for find!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I disabled SuperSU and followed directions. AP accepted my credit card and is set up. Do I leave SuperSU disabled, or can I re-enable?
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
Did you delete the /su/xbin_bind folder?
synnyster said:
Did you delete the /su/xbin_bind folder?
Click to expand...
Click to collapse
I did not. I must have missed that step.
EDIT: When I do that, root is no longer detected. The SafetyNet turned green, but Titanium Backup said no root. Sorry, and thanks for the assistance. Any other suggestions?
Are you sure you have systemless root?
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
allen099 said:
Odd, no matter what I do, including disabling SuperSU, it doesn't work. Only if I full unroot. Setup is stock OS on Nexus 6P, on the latest 6.0.1 "Q" release. Set permissions to 751...no go. Even tried unrooting, reinstalling the OS, re-rooting, and setting permissions. No dice.
Click to expand...
Click to collapse
allen099 said:
100%. I just reinstalled 2.67 via TWRP. I've got it back now. What would you recommend I do? chmod 751 /su/bin/ and remove the xbin_bind folder again? I'm reading on reddit about moving it and symlinking. How were you able to successfully do it? Thanks again!
The contents of xbin_bind are: dexdump, su, wlutil
If deleting that folder also deletes su, then it makes sense as to why root is gone.
Click to expand...
Click to collapse
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
synnyster said:
I'm systemless root with SuperSU 2.66. I deleted xbin_binds after I was rooted. All I did was chmod 751 (I did the same thing via ES File Explorer) and AP works for me.
Click to expand...
Click to collapse
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
allen099 said:
I'll try again now. Using root explorer. Did you set all files inside of /su/bin to 751? Or just the folder itself.
EDIT: It worked this time! Thanks very much!!
Click to expand...
Click to collapse
Woohoo!
Wow this is amazing. I just made my first android pay purchase on a vending machine. Thanks for finding this method!
Just wish google won't take it from us again though.
For those who are confused, here are my steps for using Android Pay while rooted.
1. I reset my phone to factory defaults by installing all original software.
2. Unlocked the boot loader.
3. Installed TWRP, but kept it read only.
4. Installed Beta Super User 2.67
5. Through Android terminal after entering su and allowing terminal emulator root access:
6. rm -r /su/xbin_bind
7. chmod 751 /su/bin
Android Pay works, root is still active. Thanks all.