Database Users

[Q] running apps as root

For clarification...
An app has to request root permissions to run as root, you cannot just give it the permissions? Is there a setuid? The "/system" filesystem is ext3 on this phone. "ext3" supports setuid & setgid, are these supported by Android?
In other words, is there any way to give a non-root app root permissions?

nodots said:
For clarification...
An app has to request root permissions to run as root, you cannot just give it the permissions? Is there a setuid? The "/system" filesystem is ext3 on this phone. "ext3" supports setuid & setgid, are these supported by Android?
In other words, is there any way to give a non-root app root permissions?
Click to expand...
Click to collapse
have you "rooted" your bravo using super one click etc?
the su built for rooted android phones has a hook to the superuser.apk so that any app requesting root must be approved by the user. You can set the app to a whitelisted app so it always gets root permissions, so that is what i recommend. this is a much important security feature and i highly recommend you dont circumvent it. that being said, there is a su out there that doesnt require approval and just gives approval so you can find it on xda if you want it but really its not a good idea or recommended

I have a related question: How do pre-installed apps on unrooted phones get root permission? I would expect that there are some that do, although I cannot give any examples.

TF101 Problem, kinda lost OS root?

Hoping for some help because I've ran into some really odd issues with SuperUser/root on my TF101.
I used the guide in the Dev Forum and flashed to Prime 1.4, everything was great and working well. I made a Nandroid of my base to fall back on.
ChainsDD updated SuperUser on 6/10 or 6/11 and I accepted the update from the market. When I launched SU, I was prompted to update the Binary, I granted SU root access and it said it completed. However, since then, no app that requires root has requested SU according to the log and Kernel Manager is telling me I don't have root.
If I open Terminal Emulator, it is automatically at a # rather than a $
In Root Explorer, tapping the Mount R/W button changes to R/O and I was able to successfully create and delete a test folder in /system
I need to get SuperUser functioning again, any thoughts or ideas?

What's a TF104 model device?

Um. you do know that # in terminal emulator indicates that the app currently has root access?
Open superuser, its being recognized as permanent root because you allowed it to have root access.
And its TF101 not TF104.

Sorry, misread the model...
I know the # means root that's why the title is kinda lost root...
I'm not getting any of the notifications that SuperUser granted access, like I used to. Also, Kernel Manager isn't being granted Root access when I launch it
I think the SuperUser binary update failed, I got the binary from goo-inside.me and flashed it from CWM. Then I cleared the SuperUser app data and launched it. I was again prompted to update the binary version. It failed and prompted me to to flash a zip that it downloaded to my SD card. That zip is a 0kb file.

Try downloading superuser from the market.

david279 said:
Try downloading superuser from the market.
Click to expand...
Click to collapse
Same results
Also, Superuser is now randomly Force Closing on launch.

Talked with ChainsDD, it's a problem with how he compiled Super User for honeycomb. Fix will be released tomorrow.
Sent from my gginggerfied EVO

Fixed binary has been posted to goo-inside.me
Sent from my gginggerfied EVO

Run application as root

How can I launch an application to give it root permissions ? Can I possibly edit the apk without writing the program over ?
Sent from my HTC HD2 using Tapatalk

You first need to root your phone. You could use z4root.apk. try searching the forums or google it. Apply permanent or temporary. I applied permanent root. The app will notify if a root is successful. Then you will need to have superuser app installed. Normally all the roms comes preinstalled with superuser. If an app asks for permission for root access just grant it and you're done.
Sent from my HTC Runnymede using XDA App

hairuleff81 said:
You first need to root your phone. You could use z4root.apk. try searching the forums or google it. Apply permanent or temporary. I applied permanent root. The app will notify if a root is successful. Then you will need to have superuser app installed. Normally all the roms comes preinstalled with superuser. If an app asks for permission for root access just grant it and you're done.
Sent from my HTC Runnymede using XDA App
Click to expand...
Click to collapse
?
My device is already rooted with SuperUser added ...... What im trying to do is give an app which was downloaded from the market root permissions . now the only way i personally know how to give an app root permissions is by FIRST programming it with root permissions . Once its compiled i dont thing i can launch an app as root . But i may be wrong . hence the thread

elesbb said:
?
My device is already rooted with SuperUser added ...... What im trying to do is give an app which was downloaded from the market root permissions . now the only way i personally know how to give an app root permissions is by FIRST programming it with root permissions . Once its compiled i dont thing i can launch an app as root . But i may be wrong . hence the thread
Click to expand...
Click to collapse
U can only give Root Permission if the app and for it

[HELP] How to ROOT multi user

Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks

At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD

Thanks for your answer
waiting for this ...

It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!

Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.

Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!

craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2

djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.

craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app

jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...

drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4

Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app

Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)

Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf

1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.

KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf

1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.

Deleting /su/xbin_bind on SuperSu 2.62

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