In our project we "lock down" the device and let only our homescreen app running.
therefore we remove all unnecessary apps, and wondering if we can remove superuser or supersu.apk
of course we need root rights, but we dont need the controlling app
we have tested it on many devices, there are a lot where we could remove supersu.akp and our app kept the root right, but on many other devices we lost the root when we removed it
is there anything we have to handle before we remove it, or how does it work?
thanks,
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
ИΘΘK¡€ said:
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
Click to expand...
Click to collapse
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
oisiss said:
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
Click to expand...
Click to collapse
Please notice how I phrased it like this:
NOOKIE said:
...root is dependent on whether or not there are the su binaries existent in /system/bin (among other things).
Click to expand...
Click to collapse
I am fully aware that root is not as simple as su being in /system/bin. :silly:
oisiss said:
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
Click to expand...
Click to collapse
Yes, this sounds right. :good:
Related
There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary
Hey guys,
This is the wrong place forum, but I like you guys, so I will ask you a question
Say there is an app that requires root (in this case Cisco AnyConnect rooted version), but I do not want to have root access enabled from within Android OS. Is there a way to install the app with automatic root access? E.g. by flashing it from within the recovery?
Thanks,
Su
Do it need root access or system permissions ?
If it needs root, you must have "su" in android OS.
If it needs system permisssions, you could push it in /system/app/ or /system/priv-app/ (more access than /system/app/)
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Sumanji said:
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Click to expand...
Click to collapse
every app that wants SU permission should be prompting you the first time to allow or deny it.
if any app gets SU permission without you allowing it, something is wrong.
what i dont understand is, you said the phone is NOT rooted, then mentioned cm11. if you are running cm11, your phone is already rooted.
Hi,
I have a banking app refusing to run since it thinks thatmy phone (Nexus 5 running 5.1.1) is rooted. Only problem is that it's not. Or at least i think so....
I have understood that the banking app concerned checks if the phone is rooted by checking for SU binary in system\bin and system\xbin, and fair enough, by xbin contains the SU file. I was rooted on 4.4 (or 5?) using towelroot. The bootloader has been locked all the time. I never rooted on 5.1 and above since I didnt want to wipe, and as it didnt matter much to me.
My questions are
1) Can I restore the root in some way, given that the SU binary exists without wiping the data? I tried Superuser app but naturally it failded to update the binary.
2) Can I delete the SU binary somehow without root access? At this point i only have read access to the system\xbin directory.
Bascha said:
Hi,
I have a banking app refusing to run since it thinks thatmy phone (Nexus 5 running 5.1.1) is rooted. Only problem is that it's not. Or at least i think so....
I have understood that the banking app concerned checks if the phone is rooted by checking for SU binary in system\bin and system\xbin, and fair enough, by xbin contains the SU file. I was rooted on 4.4 (or 5?) using towelroot. The bootloader has been locked all the time. I never rooted on 5.1 and above since I didnt want to wipe, and as it didnt matter much to me.
My questions are
1) Can I restore the root in some way, given that the SU binary exists without wiping the data? I tried Superuser app but naturally it failded to update the binary.
2) Can I delete the SU binary somehow without root access? At this point i only have read access to the system\xbin directory.
Click to expand...
Click to collapse
Every ROM has su in it, afaik.
You might have a hacked su in /system/xbin since 4.4, even though 5.x changes might have blocked that root access. Be advised that there's apps that can cloak root from apps.
beekay201 said:
Every ROM has su in it, afaik.
You might have a hacked su in /system/xbin since 4.4, even though 5.x changes might have blocked that root access. Be advised that there's apps that can cloak root from apps.
Click to expand...
Click to collapse
So even stock ROMs contain the SU binary? I only read somwhere that this is how tha apps checks if the phone is rooted or not. I'm aware of the cloaking apps, but those require me to be rootad, right? Som my problem root continues: I dont wan to root (or should i say wipe data) but the bank app wont run since it says that the phone is rooted, which it's not...
EDIT: I just checked on my galaxy tab s, and it does not contain anh SU file in bin or xbin.
some apps have root detect,most of the checks can be disabled by Xprivacy.
but they still check for the /system/xbin folder to recognize if the device had been rooted or not.
so,as the title,i'd like to know if there is any solution to prevent the apps from accessing the folder.
(now i can use them by set the folder's permission to 0750 rwxr-x---,but i have to launch supersu to correct the permission again after using the apps that will check root)
any suggestion is welcome and thanks for the idea
I get temp-root with Kingroot(locked bootlader). In some devices you can then install BusyBox, not my case because I don't have write permissions in /system.
If I install it in custom paths I've tried, it isn't detected.
Any ideas?
M4rcs said:
I get temp-root with Kingroot(locked bootlader). In some devices you can then install BusyBox, not my case because I don't have write permissions in /system.
If I install it in custom paths I've tried, it isn't detected.
Any ideas?
Click to expand...
Click to collapse
You cant install busybox without system write permissions and writting in any other location ( example. system/bin or system/xbin ) also requires write access
try magisk for rooting and what is temporary root, kingroot dont give temporary roots although it sometimes gives bootloops:silly::laugh:
Supreme Genius said:
You cant install busybox without system write permissions and writting in any other location ( example. system/bin or system/xbin ) also requires write access
try magisk for rooting and what is temporary root, kingroot dont give temporary roots although it sometimes gives bootloops:silly::laugh:
Click to expand...
Click to collapse
The thing is that I would want to do that with locked bootloader (I know it's possible in some devices).
I don't know exactly what Kingroot does, but it allows me to give root permissions to the apps that request it and everything seems to work except writting in system partition. When I reboot, that "root" disappear, that´s what I thought was called temporary-root.
However, I can write in directories like "/","/storage", but if I install BusyBox there, apps that require it seem unable to detect it.