I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk
Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!
Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well
leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.
bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you
Related
Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.
DevonSloan said:
Just got the phone, updated to MDL. Stock root and TWRP recovery.
SU is installed. Downloaded and checked root with Root Checker - root affirmed.
Only mod so far is Hotspot with the MDL Odexed through TWRP.
Installed ES File Explorer, and it wont allow me to delete or rename system files (specifically ui sounds).
ES asked for and was given SU permission.
I am only good enough with Android as far as I can follow instructions in these forums - I know nothing beyond that.
Any ideas what the problem may be? I was considering getting Root Explorer, if that will work, but I dont want to drop the 3.99 if the problem is elsewhere or can be fixed.
Thanks for your help.
(And what I am currently trying to accomplish is silencing the camera (or more specifically, editing/saving the feature.xml file to allow menu switching of sound : http://forum.xda-developers.com/showthread.php?t=2261789 - it wont let me save the text edited file - I assume it;s the same problem that wont let me delete/rename.)
Thanks. Without you guys I'd be straight Sprint/Samsung stock - aint nobody got time for that.
Click to expand...
Click to collapse
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out
Goose0121 said:
Maybe try renaming the extensions of those files to ".bak"
Hope it helps bud
****'ll Buff Out
Click to expand...
Click to collapse
Thanks, but that was actually the first thing I tried - it brings up the rename dialogue, but then after change and "ok", nothing is changed. Same with Astro and Root File Manager.
Thanks, though.
Anyone else?
Try pressing Menu and then going to "Root Explorer" and then "Mount R/W"
From there, make sure the path shows RW instead of RO. Click ok.
Exit out of ES File Manager and come back in and check the Root Explorer Mount R/W again to see if RW stuck. If it did, try to see if you can delete.
apexcell said:
Try pressing Menu and then going to "Root Explorer" and then "Mount R/W".
Click to expand...
Click to collapse
Clicked on root explorer and it gave a (paraphrased) "ES File Explorer has been given superuser privileges for interactive shell" (or something close to that), but I cant find "Mount R/W" anywhere.
And trying various things keeps giving me "device not supported" errors. Again, a paraphrase as the message isnt on screen long enough for me to get the exact wording.
Thanks again for the help.
Is this what comes up when you click on root explorer?
apexcell said:
Is this what comes up when you click on root explorer?
Click to expand...
Click to collapse
No. Nothing opens up. Same settings menu screen, there is just the message that appears below, then disappears, about "superuser permission granted.
I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."
Hmm, that's definitely not right. Try going to the Application manager, to ES File Explorer, Clear data, Uninstall, then re-installing it through Play Store. See if it still does that.
You should definitely get that screen when you go to root explorer.
cap167 said:
I also have same issue where it tells me superuser access has been granted. However, about 15 seconds later I get another message saying "Sorry, test failed. This feature can not run on your phone."
Click to expand...
Click to collapse
That is exactly what is happening with me.
Thanks Apex - doing that now.
UPDATE:
Nope. clear, uninstall, reboot, reinstall, reboot... and still getting the same results. Bah.
Does Solid Explorer also fail to be able to delete?
https://play.google.com/store/apps/details?id=pl.solidexplorer
Thanks Apex. Solid Explorer worked. Thank you for not giving up on the ideas.
While I am glad I found a solution to deleting the files, I remain a bit concerned about the ES File Explorer problem. It make me think other problems exist that I just haven't hit yet.
Case closed!
Great, glad that worked out for you.
Did anyone else notice that ES file explorer can do root stuff with the systemless root method ? it doesn't see /data nor can mount /system in rw automatically.
It works perfectly fine with system-based root approach.
Other apps like kernel adiutor or busy box work fine with systemless root method.
Yeah ES not been updated to work with systemless root.
Must use hard coded path to su.
I use FX instead with the root add on.
Has ES been updated to work with systemless root?
Try again after SuperSU 2.62
Nope, still not working with SuperSU v2.62-3-20151211162651
I used to like ES file explorer but I´ve changed my mind. The developers destroyed the App by adding this nasty cleaner and some other nasty stuff. I mean, I can understand that they want to earn some cash now but the method is not something I like. I bought the pro version though which at least doesn´t force you to swipe away this awful cleaner. I dislike this kind of business.
This explorer requires the traditional root in order to work.
Works fine for me. I used it to delete the su/xbin_bind folder
Gorgtech said:
I used to like ES file explorer but I´ve changed my mind. The developers destroyed the App by adding this nasty cleaner and some other nasty stuff. I mean, I can understand that they want to earn some cash now but the method is not something I like. I bought the pro version though which at least doesn´t force you to swipe away this awful cleaner. I dislike this kind of business.
This explorer requires the traditional root in order to work.
Click to expand...
Click to collapse
Totally agree with you on the cleaner thing. First time I saw it I thought I had downloaded the wrong app. Backed out and then realized it was ES. Really sucks cause if you aren't paying attention you could possibly delete old pictures/videos/files you still want that the stupid cleaner considers junk just because they are old.
The Stig 04 said:
Totally agree with you on the cleaner thing. First time I saw it I thought I had downloaded the wrong app. Backed out and then realized it was ES. Really sucks cause if you aren't paying attention you could possibly delete old pictures/videos/files you still want that the stupid cleaner considers junk just because they are old.
Click to expand...
Click to collapse
I totally supports Estrongs desire to monetize their ubiquitous product. But this worries me even more than the added bloat (web browser, recommended apps). Half-assed features like a cleaner that deletes important files suggests that in their push to monetize, Estrongs isn't maintaining the same level of quality. And adding a pro version so people can bypass their recent "enhancements" doesn't suggest a much respect for their existing user base. People are going to stop using their product if they continue like this. At least they haven't added notifications (yet).
Personally, I just switched to Solid Explorer and I really like it.
That´s the point, they´ve destroyed a fully working App in order to sell you one without the extras. I sure hope that the pro version will remain somehow usable. Well, to be honest, even the pro version is not 100% clean. It still has the cleaner implemented ( but at least not on the first page ) and some recommended bloatware.
Agree, been using ES Explorer for a long time but this Cleaner bloat sux's!
Any good and *free* alternatives? Open source even better ...
Heinous said:
Works fine for me. I used it to delete the su/xbin_bind folder
Click to expand...
Click to collapse
I also did that. After a while, it failed to recognize root permissions
Sent from my Nexus 6P using Tapatalk
FWIW, Solid Explorer is on sale for 99c. Solid alternative.
SomeGuy4 said:
I also did that. After a while, it failed to recognize root permissions
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute " touch su "
/system/xbin and execute " touch su "
This helped me
That works but defeats the purpose of having a systemless root.
Sent from my Nexus 6P using Tapatalk
sirxdroid said:
FWIW, Solid Explorer is on sale for 99c. Solid alternative.
Click to expand...
Click to collapse
Thanks it works fine with the system-less root. TY!
This is not the only root file manager app that can't write to system with root permissions. File Manager Pro and HD also cannot.
Is there a list somewhere of which do and don't work? Is this only a problem with the way we chose to root?
Thanks
SomeGuy4 said:
I also did that. After a while, it failed to recognize root permissions
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The xbin_bind is what allows it to work w/systemless. However I think that "feature" breaks Android Pay(?)
ntegra said:
The xbin_bind is what allows it to work w/systemless. However I think that "feature" breaks Android Pay(?)
Click to expand...
Click to collapse
I believe you are correct.
Sent from my Nexus 6P using Tapatalk
I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?
Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"
That would modify system... Just freeze the apps.
geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.
But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.
Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
brkshr said:
Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
Click to expand...
Click to collapse
busybox maybe??
i42o said:
busybox maybe??
Click to expand...
Click to collapse
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
brkshr said:
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
Click to expand...
Click to collapse
You're welcome.
i42o said:
You're welcome.
Click to expand...
Click to collapse
Sorry. Forgot my manners. Trying to get this going and working at the same time. Thank you!
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...