Develop Bugs

[solved] su problems (superuser & ES File Explorer)

Hi,
on my phone runs Superuser v3.1.3 (46) with Su binary v3.1.1 (17)
if i click on update (the same version of binary) i got the most times errors.
- sometimes i dont get root
- when i got root the test of root faild
- the mounting of writeable system fails often
what can i do (i think this is te source of my next problem)
i use ES File Explorer v 1.6.1.8 and i dont get root access (in superuser i see that ES File Explorer have the permission to get root)
i deleted that permission and tried again to get root with ES File Explorer
ES File Explorer show me the dialog (sure you want root ... yes no) but no other question from superuser to granted the root access
EDIT:
Rommanager -> restart in recovery -> info that i got su-rigths but rommanager do nothing -> force close
I need help
EDIT 2:
i tried some older versions of superuser an su-binary but still not working correctly
I dont know why root no more works, it still do this for a long time (1 year)
root checker said "sorry! this device does not have proper root access"

With ES file explorer I have had a similar problem. Clearing data and cache in manage applications fixed it for me. Not sure it is going to work in your case though (but worth a try).
Otherwise nandroid backup up then flash superuser.zip from recovery http://androidsu.com/superuser/
If you still have problems re flash your Rom.
When superuser works ok it's best to leave it alone as updating sometimes causes problems on some roms.
Sent from my HTC Desire using xda app-developers app

@hans moleman: Thx for your reply:
first i tried an full wipe -> still not working (no app got root)
so i had remember me that i have an old backup (3 month old) -> restore backup over recovery -> update all apps without superuser -> root is working again
atm my phone can use root and works like before but i have now trouble with networklocation over wlan/mobil (no gps)

If you are having GPS trouble it could be a radio issue. Make sure you have the correct radio version installed for your rom. I use the latest version (on various roms) and I've not had any GPS problems for some time.
Sent from my HTC Desire using xda app-developers app

[Q] CM file manager

I'm running CM10 and when launching CM file manager I get the message Unable to run in root Access mode. Right after I loaded CM10 it was working, i'm not sure at what point it quit working. Any suggestions?

Go to the super user app and see if it's in the exception list. If not make sure that the prompt check mark is checked them open the app and see if you get a prompt for root access. If it pops up click grant access, if not you might need to go in the super user app and clear it.
Sent from my pimped out phone

Would the exception list be under the apps tab in super user(Sorry for my noobyness)? At any rate I don't see any mention of File Manager. Super User was hanging for a few seconds on launch I think because of the log so I cleared and disabled that. Notifications are on. I don't have the elite lic, i have no qualms spending $3 for it if it is necessary. I cleared File Manager cache and when it launches i get the welcome screen followed by "Unable to run in root access mode. Change to safe mode?" At this point it crashes whether I choose yes or no.
Thanks for the response.

Yea it would be under the apps tab, try going into apps and clearing cache for the super user app it should work after that.

N-Forced said:
Yea it would be under the apps tab, try going into apps and clearing cache for the super user app it should work after that.
Click to expand...
Click to collapse
Ugh, still didn't work. Maybe I broke it cleaning out a CM10.1 install. Thanks anyways.

In the cm file manager go to settings/access mode and set it to root and it should pop up asking for root access.

Also, check your root access setting in system settings -> development. Select one of the options that allows apps to get root access

no more root access

Hi all,
on my FP1 (nice phone!) I'm no more abled to have root access. For example, ES file explorer does't go into Root Explorer mode, DiskUsage does't show Root required folders (it shows: java.lang.RuntimeException: Error: no more data message). In Superuser log:
Superuser --> Enable;
Titanium backup --> Deny;
and no more.
FairphoneOS doesn't ask me (as it should) about app su request: no dialog appair.
If I try to issue su command in terminal I get "Permisson denied" message.
Can anyone help me?
Thank you a lot
Piero

Did you by any chance activate the "deceleration needed" (or something like that) setting in the superuser settings. It is the second checkbox from above.
If it is activated and the app does not declare that it needs superuser rights it won't get any.
--Hyst
Sent from my FP1 using xda app-developers app

Root my FairPhone
I also have a FairPhone.
Cannot startup Titanium. Should I, and if so how, root my phone.
Please help.
In your feedback, please keep it simple as I am not a programmer
Thank you in advance

Hyst said:
Did you by any chance activate the "deceleration needed" (or something like that) setting in the superuser settings. It is the second checkbox from above.
If it is activated and the app does not declare that it needs superuser rights it won't get any.
--Hyst
Sent from my FP1 using xda app-developers app
Click to expand...
Click to collapse
Hi Hyst,
I'm currently having similar problems. I tried looking in the superuser settings and trying what you suggested, but no luck unfortunately.
Here is a summary of how I got to this stage:
I have recently being trying to transfer my data from my old Samsung Galaxy S4 to my FP1, using Titanium Backup. FP1 is running stock android, not the FP OS.
Unfortunately this caused issues when I tried to restore my apps and settings using Titanium Backup, resulting in the FP hanging when it got to the lock screen. I suspect this may be because of some Samsung settings that were not compatible. I did get a error message saying one of the settings files had not worked properly, but I couldn't find a way of identifying which one. I then restarted the phone as prompted by Titanium Backup, and it wouldn't get past the lock screen.
Due the phone hanging, I had to do a hard reset of the phone, following the instructions on the FP website. However, when I now run Titanium Backup it reports that it could not acquire root privileges when attempting to use "...the "/system/bin/su" command"
I've tried reinstalling both the original FP OS and stock android from the SD card, but I get an 'installation aborted' error message. Any ideas?
Thanks in advance.

Hi i Have a Fairphone fp2 andriod 7.1.2 How To Root

SuperSU & Framaroot - Need help!

First of all, I have no idea where should this be posted as I am a total noobie to this forum and there is way too many categories.
I have a big problem. I installed Framaroot, used the first option (Boromir?) and have rooted my phone successfully. I tried to use *#*#supersu#*#* but nothing came up, the digits just disappeared, so I installed SuperSU from the market. I didn't do much on it, just changed the theme and hid it from my apps. I were rooted and happy for about a month, then however I got angered by SuperSU because I had to restart Hex Editor every time to get the root permissions (I were editing Terraria save files). The anger made me want to uninstall SuperSU, hoping it would just grant all the perms to the editor. First of all I disabled SuperSU, and when I realised it actually disabled the whole root, I enabled it again (unsure if it worked), I assumed everything is working, but I still wanted to get rid of the permission thing, so I pressed something like 'clean up to switch to a different superuser', and restarted my phone. I come back, and I have no root, so I went into Framaroot and used all the options, each returning that SuperSU and superuser binaries were installed. I restarted my phone, grabbed SuperSU from the Play store, just to find out that 'SuperSU binaries were not installed and SuperSU cannot install them, this is a problem!'. I then went on Framaroot, uninstalled root with all 3 options, restarted, then installed all, restarded, and the problem is still occuring. I am running Android Jelly Bean on Alcatel 4030X.
I have completely no PC access, so any USB roots or things like that are a no go. Please help!

Hi
since no-one has replied it may be because you have no paragraphs so it shows a disorganised mind....giggles
#########
Since you claim you used framaroot to install we now try to get root again
system settings security enable unknown sources
install framaroot ....if you lost it....to sdcard
install it
run it
choose first root exploit as you say that worked
if success you must reboot
###########
What you need to do if you have chainfire's superuser installed next time
go to app drawer
click on the red and yellow su icon
click on settings
change the default from .....ask each time to grant
reboot phone to test permission for apps is now auto granted. Especially test Hex Editor
###########
Altho you don't ask....there are 2 ways of updating chainfire's app
playstore ....click on update for app
open it
it will give you a dialog box to update
choose normal............it attempts to autoupdate
b) install a custom recovery and choose TWRP or CWM or CTR etc and try to update thru custom recovery
good luck

Es File Explorer issue

I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?

The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.

deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.

Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk

i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox

I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.

@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??

Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.

Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?

d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.

Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps

phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?

phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.

Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"

Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.