Database Users

super user

sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
sorry i think its a stupid question but what should i see in superuser permission one time i only saw this +2000-2000 and something else

I was having trouble with super user too. I reverted to a working back up

ampinc said:
sorry to bring this up i have the rooted phone 2.1(droid eris) i have an app that saying super permission, i click on it and show just black screen what does this so pose to do
and how do i remove the factory apps
Click to expand...
Click to collapse
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.

Framework43 said:
From now on ,it should work for everything.
Click to expand...
Click to collapse
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc

gohamstergo said:
"Always Allow" only allows connections from the same source (computer, etc) so if you load up Terminal Emulator, youll have to Always Accept for that too...etc etc
Click to expand...
Click to collapse
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.

Framework43 said:
Enable USB Debugging in
Settings > Applications > Development
If you have SDK set up on your computer, do ,
adb shell
$
type SU
$ su
Wait a while, you should see on your phone, press Always Accept
#
From now on ,it should work for everything.
Click to expand...
Click to collapse
iam sorry but i dont know where adb shell is

ampinc said:
iam sorry but i dont know where adb shell is
Click to expand...
Click to collapse
have you downloaded the Android SDK? If so, open a command prompt and navigate to the SDK's Tools folder. then do adb shell
Framework43 said:
Yeah but if you do it via adb shell first,
it will work everytime after that.
If not, it will always force close on you.
Click to expand...
Click to collapse
no, what i meant was, clicking Always Allow only allows the current process to be always allowed.
ex: if you connect via adb on a computer and Always Allow, then you still have to allow other programs like Terminal Emulator, drocap2, etc also Always Allow isn't universal, only applies to the current app that is requesting the permission.

don't remove this app
and there is no need to run this app manually
if an app requests root-rights, this app will auto popup

i dont know what i did wrong but its not working please some help thanks

jriley60 said:
I was having trouble with super user too. I reverted to a working back up
Click to expand...
Click to collapse
can you please link me to a working backup of superuser.....I am having issues too.

there isn't a fully working one. the version we are using is from another phone completely. Until the author of superuser.apk writes one for us. the only method of getting superuser.apk to work right is.
1. enable usb debugging
2. plug your usb into your phone
3. choose HTC sync and wait for it to fail to connect if not installed.
4. while in sync mode start the app that needs root access and wait for the su prompt
5. select always allow
6. enjoy your app
some root apps like wifi tether require multiple access prompts to be fully functional.
hope this helps

[Q] getting adbd on the phone to run as root...

Hi Folks,
Is there any way with just a temp root to get adbd on the G2 to run as root?
I fiddled for a half hour or so with no success.
Thanks

Adb should work out of the box
Sent from my T-Mobile G2 using XDA App

I don't believe so.
As I understand it, adbd won't run as root in Production Builds, as the error you're seeing probably says.

Is adbd different that adb? Adb runs without root, you just need to enable development mode in the Application settings. You cannot SU in adb without root, but you can do non superuser tasks.
If adbd is different than adb, then I don't know what that is.

nolsen311 said:
I don't believe so.
As I understand it, adbd won't run as root in Production Builds, as the error you're seeing probably says.
Click to expand...
Click to collapse
There's no error, it just launches itself as the user shell no matter what.

ilikepu said:
Adb should work out of the box
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
adb does work out of the box. adbd, which is the phone side of adb is the problem.

cparekh said:
Is adbd different that adb?
Click to expand...
Click to collapse
Yes it is. It's the daemon/service that runs on the phone that enables the adb "protocol."
cparekh said:
Adb runs without root, you just need to enable development mode in the Application settings. You cannot SU in adb without root, but you can do non superuser tasks.
If adbd is different than adb, then I don't know what that is.
Click to expand...
Click to collapse

fredsanfordX said:
Yes it is. It's the daemon/service that runs on the phone that enables the adb "protocol."
Click to expand...
Click to collapse
Got it. Thanks for the information.

[CM11S]Enabled functional built in Superuser

With some help on the cyanogenmod forums, I worked out a way to enable the integrated superuser manager to actually function!
REVISED EDITION:
WARNING! DO NOT ATTEMPT UNLESS YOU KNOW WHAT YOU ARE DOING.
This is an experimental step to bring a feature from regular Cyanogenmod to 11S. You have been warned.
This requires adb and fastboot to be installed.
Please read all the instructions before attempting
1)-- Optional-Flash a custom recovery of your choice. There are threads out there that explain this.
2)Next flash the debuggable kernel, found at the bottom of this post. You can easily flash it via fastboot.
fastboot flash boot ./path/to/boot-debuggable.img
2)Download su.zip I created.
3)Boot into custom recovery(a requirement). This can be done without actually flashing it. Look up how, plenty of threads already.
4)Flash su.zip
8) Reboot.
9)If you didn't before doing this, go to Settings => About Phone and enable developer mode. Under Settings => Developer Options select Root Access and change it to Apps and ADB. Now install any root application or root checker and test it out.
Debuggable Kernel is downloadable here at the bottom:
https://cyngn.com/products/oneplusone/
su.zip
http://www.androidfilehost.com/?fid=23578570567721138
https://mega.co.nz/#!sp8nmL5J!Pj2Z4UI-7vG2YsMwEpIbDLTWOwiyWwu398oLE9edFdk

RESERVED

RESERVED

I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.

joaocadide said:
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
Click to expand...
Click to collapse
What current superuser manager are you using? SuperSU?

Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.

Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
How can I get rid of the menu when I use SuperSU instead?

Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
That only makes the menu visible. The menu will not actually function as a Superuser manager. For that, you would need the debuggable kernel and the proper compatible su binary which is why I wrote my instructions.

Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?

jbass350z said:
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
Click to expand...
Click to collapse
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.

vladashram said:
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
Click to expand...
Click to collapse
I had this same exact issue with secure settings, and elected to follow the instructions on this page to activate the cyanogenmod root settings - it worked just fine. Interestingly, even after losing the "built in root" after updating to XPNH300, secure settings still seems happy.

I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app

chenkeikari said:
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/

vladashram said:
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Click to expand...
Click to collapse
As of right now, the stock debuggable kernel for 30O is live and available.

Thanks for your work.
But could you please update to the latest version of the SuperSU binaries or could you tell me, what you modified comparing it to the normal SuperSU.zip?

Would you please share how and why would this be different than a straight forward install of SuperSU?

@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.

Not working for me
Titokhan said:
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Click to expand...
Click to collapse
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit

remortr said:
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
Click to expand...
Click to collapse
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk

Pls help me step by step procedure..
sendhiloo7 said:
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Every thing done but fast boot wont work in my case pls help me sir .pls see my attachment...

Use this command to get your root changes to persist after a reboot

Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!

goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude

Cool Awsome!! Now my phone is working properly with ROOT.

Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.

Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.

Already did it. :cyclops:

Is this only needed if your bootloader is locked but you still wanna root ?

Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/

Haha needed to do this on the official root for EU as well.

Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..

I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app

Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong

nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.

xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.

nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.

xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions

nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.

xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.

nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.

xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?

Gsam on Nougat - how to grant permissions to see all battery usage on all processes

I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Click to expand...
Click to collapse
That's it. No root necessary.

hachamacha said:
I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
That's it. No root necessary.
Click to expand...
Click to collapse
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?

droid27 said:
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?
Click to expand...
Click to collapse
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.

hachamacha said:
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.
Click to expand...
Click to collapse
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?

droid27 said:
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?
Click to expand...
Click to collapse
I've done it once when upgrading to b360 Nougat and it has held and worked fine through a few reboots and a number of system changes. So, .. once should do it, but I'd never expect it to outlast an upgrade of OS.

I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.

F1Fanatic27 said:
I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.
Click to expand...
Click to collapse
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.

hachamacha said:
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.
Click to expand...
Click to collapse
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
Did you "force-close" the app after you enabled storage and reenabled the android.permission.BATTERY_STATS? If so, other than uninstall/reinstall and try again, I'm not sure. Are you running stock OS? There can always be something quirky in anyone's install that I'll never figure out. Good luck.
The only thing I recall is that the command doesn't do anything until after you've executed it, force closed and re-started the app. If it doesn't work then, then something else is going on.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.

StewMaker said:
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.
Click to expand...
Click to collapse
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs

ayush rao said:
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.

StewMaker said:
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.
Click to expand...
Click to collapse
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs

ayush rao said:
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.

StewMaker said:
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.
Click to expand...
Click to collapse
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs

Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs

ayush rao said:
Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Mine worked until I rooted at which point root takes care of that problem without the shell command.
The one thing I can think of is that the command differs (I read this somewhere) if you have GSAMPRO rather than GSAM (by just a word) and you'd have to google the correct word and substitute it. I got this the first time I started GSAM in an unrooted environment and just noted it. It showed up in a dialogue box on GSAM.

What iam doing wrong? :
adb>adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
Edit: problem solved: I have the Pro version and so the item was: 'com.gsamlabs.bbm.pro'

ayush rao said:
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
That's no problem. Hey, a response is better than no response.
I wrote the actual application name, not the goes here. Just a placeholder.

Sorry, but what is there a way to run this command locally in the Android Terminal Emulator?