I am able to build android from source for the Nexus 7. The OTA package I generate is flashable on the device with success. It is a completely empty image, only about 10 apps.
We require to install something as a system app on boot. So this brings up two questions:
- Is it possible/how to build android ota package that is already rooted?
- Is it possible/how to include a system app in android as it builds?
Thanks!
halsafar said:
I am able to build android from source for the Nexus 7. The OTA package I generate is flashable on the device with success. It is a completely empty image, only about 10 apps.
We require to install something as a system app on boot. So this brings up two questions:
- Is it possible/how to build android ota package that is already rooted?
- Is it possible/how to include a system app in android as it builds?
Thanks!
Click to expand...
Click to collapse
I think you just add the files to the source or/to the appropriate out folders...
For apps I believe (never done or attempted) you have to add it in a folder called prebuilts, you then have to edit some mk files to include everything in the prebuilt/where it goes in the out folder...again I've never done it or attempted, just what I think needs to be done
Root is acquired by Su and super user...so add a rooted Su to working/system/core/xbin I think...not positive ill double check when I get home...
Sent from my HTC PH39100 using Tapatalk 2
I figured out adding apps.
Need to create an Android.mk for the compiled APK, see here:
http://www.kandroid.org/online-pdk/guide/build_cookbook.html#prebuiltAPK
Place the Android.mk and compiled APK into packages/apps/SOMEDIR/
Modify build/target/product/core.mk to include your packages LOCAL_MODULE name under PRODUCT_PACKAGES.
Similar approach for SuperUser I imagine. Problem is manually copying su in as part of the build.
halsafar said:
I figured out adding apps.
Need to create an Android.mk for the compiled APK, see here:
http://www.kandroid.org/online-pdk/guide/build_cookbook.html#prebuiltAPK
Place the Android.mk and compiled APK into packages/apps/SOMEDIR/
Modify build/target/product/core.mk to include your packages LOCAL_MODULE name under PRODUCT_PACKAGES.
Similar approach for SuperUser I imagine. Problem is manually copying su in as part of the build.
Click to expand...
Click to collapse
You can replace the su folder that is built in with the chainsDD superuser files from github. This will compile the correct su right in your build. Should make everything work for you.
blazingwolf said:
You can replace the su folder that is built in with the chainsDD superuser files from github. This will compile the correct su right in your build. Should make everything work for you.
Click to expand...
Click to collapse
This seemed to work to gain access to su. However apps like busybox still don't think the device is rooted even though I can su via adb shell and modify things.
I placed the chainsDD repo into /system/extras/su during my build.
halsafar said:
This seemed to work to gain access to su. However apps like busybox still don't think the device is rooted even though I can su via adb shell and modify things.
Click to expand...
Click to collapse
Did you add the Superuser.apk as well?
blazingwolf said:
Did you add the Superuser.apk as well?
Click to expand...
Click to collapse
Okay now I have Superuser.apk installed in /packages/apps and chainsDD in /system/su, then I rebuild the ROM.
They both install, su works via adb shell.
Superuser is in the app list, opens fine.
Busybox still thinks it is not rooted and the "grant, deny" dialog window from Superuser does not open as I would have expected.
halsafar said:
Okay now I have Superuser.apk installed in /packages/apps and chainsDD in /system/su, then I rebuild the ROM.
They both install, su works via adb shell.
Superuser is in the app list, opens fine.
Busybox still thinks it is not rooted and the "grant, deny" dialog window from Superuser does not open as I would have expected.
Click to expand...
Click to collapse
Does your updater-script give the right permissions to su? set_perm(0, 0, 06755, "/system/xbin/su"); (This assumes su is in the xbin folder).
blazingwolf said:
Does your updater-script give the right permissions to su? set_perm(0, 0, 06755, "/system/xbin/su"); (This assumes su is in the xbin folder).
Click to expand...
Click to collapse
When I look at the otapackage.zip I can find inside the updater-script:
set_perm(0, 0, 06755, "/system/xbin/su");
I verified that is the correct location of su.
Hmm. Your boot.img is set for secure = 0?
I don't believe I changed that, likely it is whatever default value comes down in AOSP.
Where can I check? I grepped the repo and turned up a ton of secure ='s
AOSP has su, it is just not enabled for non debug builds. You can adjust its makefile so it is built into release build ROMS. This works to get su.
Like I said I adb shell, su, and run whatever commands I want as root. That works fine. I can write to /data/ for example.
The Superuser.apk appears to be the issue. It is being built into the OTA. It installs fine, appears in the app screen. However no apps can seem to figure out they can ask for root. TitaniumBackup is a good one to test. It appears the Superuser grant, allow window not popping up is what concerns me most.
halsafar said:
I don't believe I changed that, likely it is whatever default value comes down in AOSP.
Where can I check? I grepped the repo and turned up a ton of secure ='s
AOSP has su, it is just not enabled for non debug builds. You can adjust its makefile so it is built into release build ROMS. This works to get su.
Like I said I adb shell, su, and run whatever commands I want as root. That works fine. I can write to /data/ for example.
The Superuser.apk appears to be the issue. It is being built into the OTA. It installs fine, appears in the app screen. However no apps can seem to figure out they can ask for root. TitaniumBackup is a good one to test. It appears the Superuser grant, allow window not popping up is what concerns me most.
Click to expand...
Click to collapse
You need a modified su binary. Get the cm su to use SuperUser or SuperSu su. Either way you can't use stock su.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
You need a modified su binary. Get the cm su to use SuperUser or SuperSu su. Either way you can't use stock su.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
He added the chainsDD su code to his build. So it should be a modified one.
blazingwolf said:
He added the chainsDD su code to his build. So it should be a modified one.
Click to expand...
Click to collapse
Then he is doing something else wrong. In my aosp build I replaced su. That's it. Installed supersu and everything worked.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
Then he is doing something else wrong. In my aosp build I replaced su. That's it. Installed supersu and everything worked.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Agreed. Just trying to figure out what.
blazingwolf said:
Agreed. Just trying to figure out what.
Click to expand...
Click to collapse
Could be 1/1000s of things. If its not working the correct way it should. Then need to back track some changes.
Sent from my Galaxy Nexus using xda premium
I did this
https://github.com/GeekRom/android_system_extras/commit/9bd296ad4f674d30712f000560df47109dbc420c
https://github.com/GeekRom/android_vendor_geek/commit/e5d5a1f379b8dfc4b6a4868855b225ce3bc1df35
You can check the repo. Nothing else done for su.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
I did this
https://github.com/GeekRom/android_system_extras/commit/9bd296ad4f674d30712f000560df47109dbc420c
https://github.com/GeekRom/android_vendor_geek/commit/e5d5a1f379b8dfc4b6a4868855b225ce3bc1df35
You can check the repo. Nothing else done for su.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
OK. So that is a prebuilt module. Why not build su as you build the ROM.
blazingwolf said:
He added the chainsDD su code to his build. So it should be a modified one.
Click to expand...
Click to collapse
In regards to using chainDD's build I learned as I was back tracking that it was not building properly into the system, or so it appeared it wasn't. The 'su' I had was still the stock AOSP 'su'. All I did to add chainDD to the build was replace /system/extras/su with the contents of that repo.
lithid-cm said:
You need a modified su binary. Get the cm su to use SuperUser or SuperSu su. Either way you can't use stock su.
Click to expand...
Click to collapse
I manually copied in to the build the 'su' binary from Superuser.
Now I definitely see Superuser apk pop up when I 'su' under adb shell. Superuser logged the attempt, excellent.
All other apps get instant denied when attempting to ask for root (BusyBox, TitaniumBackup).
blazingwolf said:
OK. So that is a prebuilt module. Why not build su as you build the ROM.
Click to expand...
Click to collapse
SuperSu didn't release source for it.
Sent from my Galaxy Nexus using xda premium
Related
I've been building from AOSP for a few weeks now and have a decent product, but there's a couple things that I have yet to work out.
First is adding root permissions (i.e. changing the permissions to su) from source. Currently, I have pulled this[URL] code from ChainsDD's github into my tree and added the Superuser.apk via my [URL="http://github.com/rmgeren/android_vendor_rmg/blob/master/products/rmg_passion.mk"]vendor file. Some things work, others don't. Rommanager seems to be fine, but Titanium Backup isn't. I think the problem is that su is installed into /system/bin but not xbin. When I use dsixda's rom kitchen it installs to both places and sets the permissions for su in my update-script.
Second part is more of a "like to have." I make a nice ROM, install it via RomManager (like everyone should!) and, as soon as I boot, I'm back into RomManager installing the custom recovery image.
Here's the question part:
How do I get su to install to /system/bin with a symlink to /system/xbin?
Can I just pull koush's recovery image source into my build and have a nice, custom recovery?
Is it better to just somehow not build the recovery image? How would I make that happen?
RMGeren said:
I've been building from AOSP for a few weeks now and have a decent product, but there's a couple things that I have yet to work out.
First is adding root permissions (i.e. changing the permissions to su) from source. Currently, I have pulled this[URL] code from ChainsDD's github into my tree and added the Superuser.apk via my [URL="http://github.com/rmgeren/android_vendor_rmg/blob/master/products/rmg_passion.mk"]vendor file. Some things work, others don't. Rommanager seems to be fine, but Titanium Backup isn't. I think the problem is that su is installed into /system/bin but not xbin. When I use dsixda's rom kitchen it installs to both places and sets the permissions for su in my update-script.
Second part is more of a "like to have." I make a nice ROM, install it via RomManager (like everyone should!) and, as soon as I boot, I'm back into RomManager installing the custom recovery image.
Here's the question part:
How do I get su to install to /system/bin with a symlink to /system/xbin?
Can I just pull koush's recovery image source into my build and have a nice, custom recovery?
Is it better to just somehow not build the recovery image? How would I make that happen?
Click to expand...
Click to collapse
For the symlink, just add the following to your updater-script (assuming you're using a binary update) immediately after you extract the system partition.
Code:
symlink("../xbin/su", "/system/bin/su");
If you include a recovery image in your build you will overwrite the users' recovery image which isn't such a good idea for a rom... I'd leave that one alone to be honest. And problems writing the image and you could bork their phone. It's easy though, just create the .img, put it in the root of your update zip and install it using your updater-script as such:
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
I don't understand your third question sorry...
Thanks for the response! I actually solved the problem by including busybox as a pre built package and pulling the su source from chainsdd
Before, I was including the binary su
By compiling from his source, it installs the symlink correctly.
Sent from my Nexus One using XDA App
im rooting a friends tbolt, it meets all the requirements, but i dont get root access, busybox installed but no root. any ideas? SU is in the app list but it doesnt work. this process worked flawlessy on my tbolt. and all matched up, and compatible version
T41NT204 said:
im rooting a friends tbolt, it meets all the requirements, but i dont get root access, busybox installed but no root. any ideas? SU is in the app list but it doesnt work. this process worked flawlessy on my tbolt. and all matched up, and compatible version
Click to expand...
Click to collapse
SU is in the app list, as in the App Drawer? You mean SuperUser if that's what you're talking about. SuperUser is the GUI interface to the actual su binary.
The su binary (which should be located in /system/bin on the phone) is the actual file that grants root access rights. Can you confirm that that file has actually been installed and what its permissions are?
Will the SuperUser app let you download/update su? Also, you should be able to install it from CWM under the extras menu if I recall correctly.
My phone's not handy to confirm above, I'm doing by memory, which isn't so great these days, but hopefully this will give you some ideas of what's wrong.
distortedloop said:
SU is in the app list, as in the App Drawer? You mean SuperUser if that's what you're talking about. SuperUser is the GUI interface to the actual su binary.
The su binary (which should be located in /system/bin on the phone) is the actual file that grants root access rights. Can you confirm that that file has actually been installed and what its permissions are?
Will the SuperUser app let you download/update su? Also, you should be able to install it from CWM under the extras menu if I recall correctly.
My phone's not handy to confirm above, I'm doing by memory, which isn't so great these days, but hopefully this will give you some ideas of what's wrong.
Click to expand...
Click to collapse
i cant atm i dont have his phone. SU (superuser) is in the list, and it told me it was up-to-date when i tried updating it.
CWM? thats new to me atm
root checker sees busybox, but reports not rooted.
I should have replied to the SuperSU thread but since I have less than 10 posts...
I was doing a fresh flash/install. The first thing to do of course is to root the phone.
Installed SuperSU 0.94, open it up, says that I need to update the binary, clicked OK, Installation Failed, tried that several times via 3G/Wifi.
Tested under Better Terminal, typed su: not found.
Then I installed Superuser 3.1.3, run SuperSU again and the binary update worked.
Tested under Better Terminal, typed su: # it worked.
Uninstalled Superuser and tested under Better Terminal
SU gone again.
The binary update failure happened before when version<0.7.3.
So why is this? Why do I need to install Superuser to get SuperSU to work?
It depends on what su binary is installed when you root your phone or what app the author of the ROM prefers. You can download the supersu zip package and install it after you install a ROM but even then you'll have to update binary via launching the app itself.
Sent from my Nexus 7
Because every app that uses Superuser permissions needs a a management app to get access to su.
Sent from my DROID RAZR using Tapatalk 2
Leviathan26 said:
Because every app that uses Superuser permissions needs a a management app to get access to su.
Click to expand...
Click to collapse
Oh, by Supuruser I'm talking about Superuser - the old app, not the superuser permission.
evonc said:
It depends on what su binary is installed when you root your phone
Click to expand...
Click to collapse
Yep, you're right, I was just stupid not paying attention to the bat root script. I removed the old Superuser.apk from the scirpt but not the binary.
When I replaced the su with SuperSU binary, no errors anymore. Thanks.
My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
ilogik said:
My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
Click to expand...
Click to collapse
Its possible that you removed root permissions solely for wifitether by accident. Uninstall and reinstall then when it fires up make sure you select allow when superuser popup comes on. If you know your way around you can avoid the uninstall by simply going into superuser app and fixing permissions for wifi tether. If not then you'll need to boot into recovery and reflash supersu as you did during the original root process.
hope this helps!
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
Click to expand...
Click to collapse
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
Click to expand...
Click to collapse
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app. It has been confirmed that SuperSU does not work.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH FILES must be removed. Freezing SuperSU will not work
Next download and then flash the following zip in TWRP or CWM:
Superuser Binary+App
At this point you should have fully functional root on stock
S121Guy said:
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
Click to expand...
Click to collapse
Again, simply flashing Superuser over SuperSU will not work, the app and binary must be removed before flashing.
Jarocks said:
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH MUST be removed to avoid any issues
Next download and flash the following zip in TWRP or CWM:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
At this point you should have fully functional root on stock
Click to expand...
Click to collapse
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The zip contains both the superuser app and corresponding su binary.
Jarocks said:
The zip contains both the superuser app and corresponding su binary.
Click to expand...
Click to collapse
I overlooked the zip portion of your comment. I thought that you were saying to simply remove the app and the binary and reboot. However the binaries wont load from SuperSU in the first place so you should eb good to just get rid of SuperSU and install superuser. If everyone has been following the recommended rooting steps that is. But if that were the case noone would be installing SuperSU
My system folder only contains /bin and nothing else. is there another system folder I should be in?
ilogik said:
My system folder only contains /bin and nothing else. is there another system folder I should be in?
Click to expand...
Click to collapse
are you in adb or are you using a file explorer?
TWRP file explorer
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
droidmark said:
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
Click to expand...
Click to collapse
I know this is an old thread but if it helps others, I had the same issue with TWRP, there is an option in SuperSu to unistall and switch to a another superuser app. Put the superuser zip above on the phones memory card, then just install regular superuser from the market. Now go into SuperSu and pick the option to switch to another app, once done go into file explorer and delete the files stated above if they are there. Now reboot into recovery & flash the new superuser zip..
That's very helpful information. Somehow I solved it back in December but I don' know how!
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.