Database Develop

Why the root message isn't showed like Hero&Others ?

All others rooted phones have a message showed when an application asks root, why don't we have this on Tattoo ?

On Tattoo root permissions are always enabled

Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/

JoOoSs said:
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
Click to expand...
Click to collapse
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.

I'm on stock ROM, this is the problem i think!
Anybody has SetCPU ?

The problem with this is that every application can obtain root without our knowledge.
It is a serious security flaw.

Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.

Netbuster said:
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
Click to expand...
Click to collapse
Because that rom you've flashed contains custom boot.img by mainfram3 that gives to you root at startup and loads tattoo-hack.ko (partition r/w always mounted)

Coburn64 said:
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Click to expand...
Click to collapse
Actually i wasn't having viruses in mind. More like keyloggers and such. SU prompt wasn't invented for no reason...

I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.

mainfram3 said:
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
Click to expand...
Click to collapse
Exactly my point.

MoDaCo Custom ROM 1 includes Superuser apk for root access.
P

Anyone know how to fix Superuser Permissions manually?
I have Tattoo with rooted boot.img (mainfram3)
I pushed su into /system/bin/
Made chmod 4577 /system/bin/su
Pushed superuser.apk from Modaco Rom to /system/app/
Restart sure...
SuperUser Permissions can be executed (list is clear)
But any app doesn't send request to Superuser Permissions.
What i could forget?

Finally, I solved it partially.
Sure, i have rooted boot.img
I extracted from Modaco Custom ROM for Tattoo:
su
Superuser.apk
copied su to: /system/bin/su
copied Superuser.apk to: /system/app
run in terminal: chmod 4577 /system/bin/su
restarted and everything works fine now... Superuser Permissions shows all root-requests, Titanium Backup works, other root-things works too
But i notice, that su-binary from Modaco ROM is about 34-36 kb, but
su-binary from guide of getting root is about 80-85 kb.
1-2 months ago we faced with difference in size of su. We choosed bigger su in case, what it can run "flash_image", smaller su can't run.
But maybe it fixed already? I did not test it yet.

Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.

lukic said:
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
Click to expand...
Click to collapse
What exactly wrote TB?
Did you download busybox via TB?

I don't remember exactly.
It did ask me to download busybox and I did that, but still it didn't work.

[Q] Superuser Denied

Hello,
My Nook HD+ is currently running on verygreen's cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip. I did not make any other customization.
I tried installing an app called Quick Boot from Playstore which needs root access. However, I'm getting error "Superuser denied to QuickBoot". However, the root/superuser access is working fine with other apps like Titanium Backup, AdAway, ES Explorer, Terminal Emulator, etc.
Superuser Access - Automatic Response setting is set to "Prompt". Prompt does work for other apps but not for Quickboot. I just get a flash message that "Superuser denied to QuickBoot". I have also changed Automatic Response setting to "Allow" and tried, but even then I get the same error.
I downloaded the Superuser (by ChainsDD) app from Playstore and tried. I am getting the same error "Superuser denied to Superuser" for this app as well. Also, this app does not show me any App list with superuser access, I just get a blank screen.
I'd appreciate any suggestion to fix this issue.
Thanks in advance...

TheLabyrinth said:
Hello,
My Nook HD+ is currently running on verygreen's cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip. I did not make any other customization.
I tried installing an app called Quick Boot from Playstore which needs root access. However, I'm getting error "Superuser denied to QuickBoot". However, the root/superuser access is working fine with other apps like Titanium Backup, AdAway, ES Explorer, Terminal Emulator, etc.
Superuser Access - Automatic Response setting is set to "Prompt". Prompt does work for other apps but not for Quickboot. I just get a flash message that "Superuser denied to QuickBoot". I have also changed Automatic Response setting to "Allow" and tried, but even then I get the same error.
I downloaded the Superuser (by ChainsDD) app from Playstore and tried. I am getting the same error "Superuser denied to Superuser" for this app as well. Also, this app does not show me any App list with superuser access, I just get a blank screen.
I'd appreciate any suggestion to fix this issue.
Thanks in advance...
Click to expand...
Click to collapse
You are looking in settings at the superuser section? And Quick Boot is not listed in the apps or history?
Sent from my Nook HD+ running CM10.1 on emmc.

Superuser Denied to Quick Boot and Superuser (by ChainsDD) app from Playstore
leapinlar said:
You are looking in settings at the superuser section? And Quick Boot is not listed in the apps or history?
.
Click to expand...
Click to collapse
In Superuser section under Settings, Quickboot is showing as "Deny", Titanium Backup, AdAway is showing as "Allow". Log is showing the same. Also, the Superuser (by ChainsDD) app from Playstore is showing as "Deny" under superuser settings.
When I am trying to run the Quickboot app, every time I am getting a flash message for a second "Superuser denied to QuickBoot".
I'm not understanding why some apps are getting root access, some not. I tried clearing the app data and cache and re-installed the apps as well. But it did not help.
It would be really helpful if you please let me know a way to fix this issue.

TheLabyrinth said:
In Superuser section under Settings, Quickboot is showing as "Deny", Titanium Backup, AdAway is showing as "Allow". Log is showing the same. Also, the Superuser (by ChainsDD) app from Playstore is showing as "Deny" under superuser settings.
When I am trying to run the Quickboot app, every time I am getting a flash message for a second "Superuser denied to QuickBoot".
I'm not understanding why some apps are getting root access, some not. I tried clearing the app data and cache and re-installed the apps as well. But it did not help.
It would be really helpful if you please let me know a way to fix this issue.
Click to expand...
Click to collapse
It got denied because you did not respond quick enough when it asked the first time. Once denied, it stays that way until you somehow clear it. But I don't know how to clear it on this new CM10.1 setup. There is no superuser app, it is part of the operating system.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
It got denied because you did not respond quick enough when it asked the first time. Once denied, it stays that way until you somehow clear it. But I don't know how to clear it on this new CM10.1 setup. There is no superuser app, it is part of the operating system.
Click to expand...
Click to collapse
I am very sure that there was no prompt to grant Superuser access when I opened Quickboot for first time because I was waiting for the prompt to come up. But it never came.
Also, do you mean that I should not use any other Superuser App other than the one that came with the Operating System?
I have another question regarding the default Superuser App that came with OS. Why is there no option in settings to change "Deny/Allow" for an App? Is there a way around to enable the "Deny/Allow" option in the Superuser App Settings?

TheLabyrinth said:
I am very sure that there was no prompt to grant Superuser access when I opened Quickboot for first time because I was waiting for the prompt to come up. But it never came.
Also, do you mean that I should not use any other Superuser App other than the one that came with the Operating System?
I have another question regarding the default Superuser App that came with OS. Why is there no option in settings to change "Deny/Allow" for an App? Is there a way around to enable the "Deny/Allow" option in the Superuser App Settings?
Click to expand...
Click to collapse
Well, if it is showing denied, it got denied somehow.
I don't know much about this new superuser setup in CM10.1. You might try going to cyanogenmod's forum on their site. It is a generic issue that applies to all their devices so there may be some discussion on it.
Sent from my Nook HD+ running CM10.1 on emmc.

Can anybody please confirm whether they are getting the same "Superuser denied" issue with Quickboot? We will know if it is a generic issue with everyone or issue with my Nook only. If it is a generic issue, we can bring this to the notice of the developers. Quick Boot is available in Play store.
Also, if anyone can test the Superuser (by ChainsDD) app from Playstore.

TheLabyrinth said:
Can anybody please confirm whether they are getting the same "Superuser denied" issue with Quickboot? We will know if it is a generic issue with everyone or issue with my Nook only. If it is a generic issue, we can bring this to the notice of the developers. Quick Boot is available in Play store.
Also, if anyone can test the Superuser (by ChainsDD) app from Playstore.
Click to expand...
Click to collapse
Well, I can tell you I have no issue with Quick Boot and the verygreen 7/08 emmc ROM.
And I did have a problem with an old version of Root Browser not activating superuser. It was not denied, it just did not recognize the CM superuser. So I installed ChainsDD superuser and it recognized it and got activated. It was listed in the CM superuser as allowed then. Then I could uninstall ChainsDD superuser and Root Browser continued to work fine.
Sent from my Nook HD+ running CM10.1 on emmc.

...has been denied Superuser permissions

Hello all,
A friend gave me his Droid 3 which was successfully rooted (Superuser version 3.13 is installed). When I look at the log I can see many past "Allowed" entries. However, I attempted to install Safestrap (version 3.05), and it was denied Superuser access (can see the denial in the log). I then attempted to grant other apps Superuser permissions and I get a "[App Name] has been denied Superuser permissions" message (and it shows "Denied" in the Superuser Log).
The really odd things are that (1) it doesn't prompt to allow or deny (despite the setting saying to prompt), and (2) if I select Superuser funcitons within the Superuser App, it will allow them. For example, if I select "temp unroot", it says "Superuser has been granted Superuser permissions".
I know I can SBF the phone and start over, but there are lots of paid Apps on the phone and I just assume try to work on getting Superuser working again if it's possible.
Please help!

Try setting to always allow
Sent from my DROIDX using XDA Free mobile app

Solved! Ok, with the device connected to my computer and playing around in adb, I noticed that the permissions for the SU binary were all goofed up. So I issued the command: adb shell "chmod 6755 /system/bin/su" and that solved the problem. Hope this helps someone else.

Shadow: Thank you sir for your reply. I should have mentioned in my original that I did try "always allow" in addition to prompting and it didn't make a difference. However, I solved it by changing the su binary's permissions (see above). Thanks again for takinig the time to reply.

Alternative to installing Better Battery Stats as system app

Starting with Android 4.4 (KitKat) Better Battery Stats (BBS) require installation as system app to be able to collect the stats.
BBS must re re-installed as system app after each ROM upgrade (upgrade that does not preserve third party system apps).
I have found an alternative to this - the required permissions can be granted to BBS when it is installed as a regular user app by running these commands in Android Terminal (or ADB shell session):
Code:
su
pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats android.permission.DUMP
After using these commands it might be required to restart BBS process (e.g. reboot the device). Permissions granted this way will be preserved across ROM upgrades (even across those completely overwriting /system partition).
This has been tested on CyanogenMod 12.1 nightlies (Android 5.1.1).
Update! This post on BBS thread describes a related method for granting (at least part of) the permissions without root.

Hi DavisNT,
I'm confirming that your adb code appears to be a successful workaround for the normal version of BBS downloaded from the Play Store when the phone is running Lollipop. I'm running the paid version of BBS, on the current CM12.1 Nightly (jfltetmo for my T-Mobilr SGH-M919 Galaxy S4).
Procedure:
1. Install BBS from the Play Store.
2. Use ADB (easy to cut and paste from here) or another terminal program (you'll be typing) to install the code.
3. Reboot the phone.
You'll notice that when you launch BBS, CM's "Privacy Guard" will see that BBS is trying to gain root access, and will prompt you to allow this. I selected "Always Allow" until I'm done my battery testing. You'll notice that you now see "#" up on the phone's status bar. That indicates an app is running with root access. You could probably quiescence this by choosing "Ignore" via Privacy Guard.
Could the developer please approve that this relatively easy workaround is kosher?
Thanks . . .

Moved to main thread to avoid orphan

For apk downloaded from xda change the code to
pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP

I tried this method, but failed on the BATTERY_STATS permission, the error said this 'permission type is not changeable'
is this method still valid?

andycjw said:
I tried this method, but failed on the BATTERY_STATS permission, the error said this 'permission type is not changeable'
is this method still valid?
Click to expand...
Click to collapse
On what version of Android did this fail? And was 'su' used before 'pm grant'?

Same problem. I'm on CM, Android version 4.4.4. Used 'su' before.

bobcote said:
Same problem. I'm on CM, Android version 4.4.4. Used 'su' before.
Click to expand...
Click to collapse
Most likely this method works only on Lollipop and Marshmallow.
Looks like on KitKat BATTERY_STATS permission does not have development in its protectionLevel, but on Lollipop and Marshmallow it has.
I assume (please correct me if I am wrong, preferably with link to some authoritative documentation) that development in protectionLevel allows a permission to be granted by pm grant command.

Thanks

I can confirm that this method works flawlessly for the Sprint version of the Galaxy Note 3 5.0. Many thanks.

Guys where is the main thread? Pls ?

DavisNT said:
Starting with Android 4.4 (KitKat) Better Battery Stats (BBS) require installation as system app to be able to collect the stats.
BBS must re re-installed as system app after each ROM upgrade (upgrade that does not preserve third party system apps).
I have found an alternative to this - the required permissions can be granted to BBS when it is installed as a regular user app by running these commands in Android Terminal (or ADB shell session):
Code:
su
pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
pm grant com.asksven.betterbatterystats android.permission.DUMP
After using these commands it might be required to restart BBS process (e.g. reboot the device). Permissions granted this way will be preserved across ROM upgrades (even across those completely overwriting /system partition).
This has been tested on CyanogenMod 12.1 nightlies (Android 5.1.1).
Click to expand...
Click to collapse
Does this method work on marshmallow?
Thank you

RoxAbout said:
Does this method work on marshmallow?
Thank you
Click to expand...
Click to collapse
Most likely yes. Feel free to test. [emoji2]

Can anyone post BBS apk please!! TQIA

Thanks dude. The command for xdaedition worked flawlessly on my RR rom. Android 6.0.1 Galaxy S3

Worked! Thanks.

Does this works on a non-rooted phone? if it works, is uninstalling as simple as accessing app under setting to uninstall?
Thanks.

nuthing03 said:
Does this works on a non-rooted phone? if it works, is uninstalling as simple as accessing app under setting to uninstall?
Thanks.
Click to expand...
Click to collapse
AFAIK This method should NOT work on non-rooted phones (but you can still try it :fingers-crossed: ). If it will work, uninstalling the app (via Settings - Applications) would also revoke the granted permissions.

Original Thread here: http://bit.ly/1ov1NNy
Can confirm that the workaround is OK on Samsung S6 with Android 6.0.1 (stock DTM/rooted).
Best regards

Glad I found this, thought BBS was bugged when it kept wanting the BATTERY_STAT permission despite having the XPosed module :\
Executing those 2 lines fixed the problem.... wonder why it's not like that by default. I even checked AppOpsXposed and didn't see anything about DUMP/BATTERY_STAT
Installing BBS into /system would break OTA, no? I've read somewhere the claim that it doesn't--maybe even in the app itself

Issues installing BusyBox

Hey guys, so I'm trying to install BusyBox on my new Nexus 6 running stock 6.0, rooted. When I try to install via Stericson's installer I got from the Play store, I get:
"We could not verify the integrity of the binary selected..." flashes for a moment, then:
"BusyBox installer was not allowed root access. This may be an issue with Superuser, open Superuser and make sure that you are allowing root access. This application will not work without root access."
I've made sure that the app is allowed root access, and have also tried deleting it from SuperSu so it would prompt me and I could grant it access again, but still the same issue. I'm not sure what the deal is, it seems like I could be having root issues? I appear to have root since I am able to use TiBu, but something seems funky. For example usually when I open FKUpdater it says "FKUpdater has been granted super user access..." and then "Unable to acquire ROOT access." Other times it only says "Unable to acquire ROOT access." I haven't tried flashing a kernel with it because I don't want to at the moment while I figure this other issue out, so I'm not sure if it's falsely reporting the root error.
So, I looked into things further and it seems like I may have some sort of permissions issue. I tried using JRummy's BusyBox installer, but that fails also and just tells me to try installing a different version of BusyBox. It also includes a script for fixing permissions, and when I run it I get "error: only position independent executables (PIE) are supported" and "/data/user/0/com.crummy.busybox.installer/files/temp.sh[118]: sync: can't be executed: permission denied."
Permissions for /data/user/0/com.crummy.busybox.installer are set to drwxr-x--x, as is /system. Also /system is only showing 58 MB free but I don't think that's a problem...
Any ideas? I'm totally stumped...

set your SElinux to be permissive(via app or terminal command)