[Q] Android System UID seeking root permission - One (M8) Q&A, Help & Troubleshooting

All of a sudden today, I am getting continuous requests for Android System UID asking for root permission. I deny/fail to grant, but minutes later, it happens again. What is it? What should I do?

question too vague
wiredwrx said:
All of a sudden today, I am getting continuous requests for Android System UID asking for root permission. I deny/fail to grant, but minutes later, it happens again. What is it? What should I do?
Click to expand...
Click to collapse
are you s-off? rooted? what superuser app are you using? custom rom or stock? logcat? Your question is too open-ended for a real answer.
with that said, here are some shot-in-the-dark type answers, try them at your own discretion, I'm not liable for what you choose to do.
If you have a custom recovery, try rebooting to recovery and wiping cache/dalvik...fix permissions. Reboot to system.:fingers-crossed:
(this would be my first step)
open your superuser app and update binary and/or reinstall and/or switch apps
The Android System UI needs root permissions, but it shouldn't be asking for it, it should be part of the code. I personally would not deny my UI, aka User Interface any root permissions. Try granting and see what happens.

AGKdrOId said:
are you s-off? rooted? what superuser app are you using? custom rom or stock? logcat? Your question is too open-ended for a real answer.
with that said, here are some shot-in-the-dark type answers, try them at your own discretion, I'm not liable for what you choose to do.
If you have a custom recovery, try rebooting to recovery and wiping cache/dalvik...fix permissions. Reboot to system.:fingers-crossed:
(this would be my first step)
open your superuser app and update binary and/or reinstall and/or switch apps
The Android System UI needs root permissions, but it shouldn't be asking for it, it should be part of the code. I personally would not deny my UI, aka User Interface any root permissions. Try granting and see what happens.
Click to expand...
Click to collapse
Thank you for the response.
I am s-on. I am rooted, with "weaksauce" I tried installing busybox and busybox on rails. Each one had issues with installing. On Rails told me I was not rooted. I installed root checker, and I am rooted according to the app. I am using SuperSU.
I went ahead and granted UID superuser permission. I don't notice any difference. However, recently, I have been noticing random sound notifications. Nothing shows up in the notification shade. I installed an app called "Notification History" and most often, nothing shows up in the history when this happens. I wonder if this was a result of the failing to grant root access to the UID.

i actually had the same thing.
My phone started performing a little bit slowly, so I thought I'd reboot it (I hadn't in over a week probably). After the reboot everything went to crap. The system requested root a couple of times (i denied each attempt), the performance was really bad, in the end i have seemed to have narrowed it down to Sywpe? I changed keyboards (just back to the stock HTC keyboard now), and things seem to be better..
it's been about a month since i flashed a ROM on this thing, so maybe it's time.

I'm not too familiar with s-on...I always just go the extra 10% for s-off.
It honestly sounds like you need to just start over from scratch.
Uninstall the weeksauce uninstall supersu. hard reboot...
full directions right in the OP of weaksauce:
http://forum.xda-developers.com/showthread.php?t=2699089
I would try a cross between the "Troubleshooting" and "Install"
Make a BACKUP first JIC,
download all new files, and check the sums.

Related

Any Standard Rooted 1.47.651.1 ROMs out there?

Does anyone know of a "1.47.651.1 ROM" that:
• Is rooted WITHOUT Super User(meaning "adb shell" brings up "#", not a "$" and then "su" to get "#")
• Isn't tweaked to hell
• Has working AND updated EVDO & WiMax Radios
That's all I want, but can't seem to find it in this jumble of hacked ROMs and special do-dads.
I think that the "start over with 1.47" thread gets you to stock with everything updated, except that you're going to have superuser access.
It's probably your best bet. Why don't you want superuser permissions?
Because typing "su" an extra step, and it also asks me to give permissions everytime something with root access pops up. So annoying. I just want it to work lol.
Psionicsin said:
Because typing "su" an extra step, and it also asks me to give permissions everytime something with root access pops up. So annoying. I just want it to work lol.
Click to expand...
Click to collapse
It should only ask for the application once. If you don't have it, the application won't run at all will it?
Sirchuk said:
It should only ask for the application once. If you don't have it, the application won't run at all will it?
Click to expand...
Click to collapse
Seems to do it a lot, and even stops me to ask me if certain programs are allowed to communicate with Google servers every so often. Is SU something that is required NOW for a root to work? Because my last phone didn't (Black) didn't have it on there, had 1.47, and rooted fine with the flash exploit method.
It's not working for my white phone though, so I had to use SimpleRoot (which took me back to a WAY earlier version), and flash my way up to 1.47.
Psionicsin said:
Seems to do it a lot, and even stops me to ask me if certain programs are allowed to communicate with Google servers every so often. Is SU something that is required NOW for a root to work? Because my last phone didn't (Black) didn't have it on there, had 1.47, and rooted fine with the flash exploit method.
It's not working for my white phone though, so I had to use SimpleRoot, and flash my way up to 1.47.
Click to expand...
Click to collapse
I do not have your issues with the superuser permission app. It maintains a list of all allowed apps. Once you ass it as "always allowed", you never see it prompt for that app/function, again.
I am using whitslack

Rooted Desire keeps asking for Superuser permissions

I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Ommadawn said:
I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Click to expand...
Click to collapse
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Also, when being asked for permission, is "Remember" checked?
why not just re-root?
punky.mtp said:
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Click to expand...
Click to collapse
Yes you should have a list of allowed apps on opening the su app itself - click apps on top left. The allowed apps shouldn't keep requesting permission each time.
You coukkd uninstall su app then reinstall from market?
Nandroid backup first!
Thanks for the all the replies, much appreciated!
@punky.mtp & @stringer7: Yes, I can see the apps I've granted permissions to in the Superuser app, each has a green button against it. I'm not sure of the current version of SU I'm running, but I know it's not the latest version. I've tried to update it from the Market but it won't over-write the existing installed SU. I'm doing a nandroid as I type and will try uninstalling and reinstalling to see if that helps.
@HiVoltage85: Yes, I've set the remember checkbox as well for each app when granting permission.
@BigMrB: I've already re-rooted with different versions of unrevoked, several times, which hasn't fixed the problem.
I'll let you know how I go.
Sorry, I'm giving away my ignorance, but how do I uninstall my current Superuser app? The uninstall button is disabled in the manage applications part of the phone's setup.
Edit - Never mind, I found how to do it.
Looks like I have it fixed. I was able to remove the old Superuser app and install a new one from recovery (v2.3.6.3) which works properly and doesn't keep asking for permissions repeatedly. Thanks for the suggestions and help!

[Q] "unknown user granted SU permission" causes reboot on 4G only

My e4gt rebooting constantly on 4g. "Unknown user granted su permission" pops up before reboot.
how do i know whats causing this?
just installed calkulins 1.5a rom and installed some apps with titanium(which is probably the culprit)
Run Superuser from the app drawer and clear all the permissions. Then when the offending app asks for permission a prompt will come on your screen and you can identify the offender.
sfhub said:
Run Superuser from the app drawer and clear all the permissions. Then when the offending app asks for permission a prompt will come on your screen and you can identify the offender.
Click to expand...
Click to collapse
tried it...and no app shows up just the permission granted and then reboot. it seems to happen when i try using any app that uses the data service. the log in su has a permission granted but no description of offending app.
Personally I wouldn't be comfortable if an app I had no idea about started requesting root permissions on every startup. You probably do want to track it down. Worst case you can reinstall the base ROM and then put your apps back one at a time until you see the culprit.
Lettuce know what the app is too, it needs to be reported.
sfhub said:
Personally I wouldn't be comfortable if an app I had no idea about started requesting root permissions on every startup. You probably do want to track it down. Worst case you can reinstall the base ROM and then put your apps back one at a time until you see the culprit.
Click to expand...
Click to collapse
i just re flashed rom..ill try installing one by one, it will take forever but its necessary.
thanks
it turned out to be the viper mod los checker i flashed behind calkulins rom. reinstalled rom without los checker and everything works fine now. checker was a great fix to bad it didnt work on my phone.

Why do I keep losing root?

My Verizon GNex is rooted, I have CWM, superuser etc, even installed this rom, but I keep losing root after an hour or so. I use root explorer, open a terminal, su, do things, do it again in a few minutes and it suddenly won't log in as root.
When this happens, my wifi also craps out. It shows signal strength too low to connect when I'm standing next to the router. Reflashing CWM or superuser does nothing. Last night I wiped and went back to stock and it worked for a while, but I've found I can also flash that rom and it will work for a while and that is easier. Root survives multiple reboots but just stops working for no reason after a while.
Example: I flashed that rom this morning and rebooted 2-3 times, went to the mall and kept opening root explorer to see if root was working. I sat and watched my daughter play at the mall for nearly an hour. When she wanted something to drink, I checked and root was still working. I went to the store nearby, got a water, sat back down and no longer had root.
I'm not getting any OTA notification or anything, it just stops being rooted out of the blue.
Any ideas?
Darn, halfway down page two already and no replies...
same issue here
I'm glad I'm not the only one. How did you root?
followed this until step 5 http://forum.xda-developers.com/showthread.php?t=1392310
Me too. I used a different guide, but it looks like it was exactly same.
Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk
fubaya said:
Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Haven't seen this specific issue much with the Galaxy Nexus yet. I had this problem 1.5 yrs ago with an older Samsung Android device though. Solution was a bit complex, but haven't seen this issue in a long while.
I know root can be a bit hidden from Android unless adb is connect or using a terminal application. For this reason, m root check application is generally a good program to run a simple diagnostic of the root configuration on the device.
The Pro version, 99 cents in the Market and free on XDA has a widget which will update at the interval you pick, 1-24 hrs with the root status and gives a more thoroughly diagnostic output of the system su binaries and their properties.
Hope that helps!
Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.
I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk
motopig said:
Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.
Click to expand...
Click to collapse
The su binary will have also remained after an OTA, same as busybox. The difference is their permissions. Every OTA re-sets the binary direction permissions as 755 stripping out the setuid attribute required by su, but not required by busybox.
This would explain why after using an OTA the user will lose "root" access but maintain busybox access. Both binaries persist, but the su binary loses the setuid attribute required to elevate access for root.
fubaya said:
I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well the key here, as I stated above, would be to see whether or not the su binary still has the setuid attribute and UID/GID set as root.
Any of those changes could remove the ability of the su binary to esclate permissions as root. In theory, any application which has been granted root access through Superuser, could remove root access for the whole system.
I can't imagine any reason why a developer would intentionally write an application to do that under a different title which you would be using.
Hope the technical details help!
I never had an OTA update after rooting, at least there were no notifications or anything. I do agree it acted as if the binary permissions got screwed up somehow, I don't know why I didn't check. Reflashing the su.zip didn't help. I assume flashing would set the permissions.
Well, nearly 24 hours and I still have root so, whatever it was, I'm happy now.
I just realized i no longer have root and i did the ota update recently. Problem is i cant get root back no matter what i try. I reinstalled the latest superuser from market with no luck. Any advice?
I forgot to mention i am completly stock on 4.0.1 and ITL41F. All i did with this phone is unlock the bootloader and the guide i used i think pdanet put SU apk automatically installed. My apps like root explorer all showed they did have root access. But now i tried to use root explorer and it claimed it had access, but couldnt get root.
My SU apk was updated to latest from the market. I just uninstalled the update and still no luck. Reinstall update and still no luck..
When it happened to me, the only thing that worked was to reflash the rom and go through the rooting process again. There is a thread in the development section about going back to stock where you can find the stock rom. you'll lose apps and things and may want to back them up first.
You could probably flash a new rom instead. I don't remember which one it was, but I was using a 4.0 rom that had su and didn't require wiping anything so reflashing was painless.
Sent from my Galaxy Nexus
Crap ok thanks. I cant backup anything with titanium cause it cant get root, so i guess i jyst have to lose everything. Might as well go with one of the roms i guess. I kinda was just enjoying stock with root.
Oh the other problem i have is i'm getting a fastboot error. Boot into bootloader and at the bottom of the screen says "fastboot FAILstatus" below. Any idea what thats about?
Some apps can export their settings the sdcard so don't forget to check them. I know when I lose everything there's really only 4-5 apps that require much setup while the others just require a login, but luckily those 4-5 apps can export their settings.
I don't know about the error, I'm not very good with fastboot. I use it when I get a new phone then go a couple of years without using it.
i finally got rooted again. For some reason it just wouldnt take. I had to use superboot over and over and over again and then finally it just took successfully even though i didnt anything differently. Very strange.

[HELP]Shell has been granted Superuser permission?!?!

Okay, what the hell?! Every now and again (usually when I'm running Dolphin Browser and/or trying to cut/copy/paste) I get a floating notification at the bottom of the screen that says 'shell has been granted Superuser permissions'! It flashes a few times and then my phone restarts. When it turns back on, I have to restart Juice Defender and SwiftKey (default keyboard ALWAYS comes back, even if I shut down or restart myself!) manually. I went into the Superuser application the other day and there was nothing in there by the name of 'shell.' In fact, the only two things I have granted Superuser permissions to are Titanium Backup and the Android System (is this the culprit, I wonder). Either way, this problem has become a real pain in my ass. It always happens at the most inconvenient times. I would really, REALLY appreciate a solution to this problem.
Also, I have my phone set up just the way I like it, as far as the layout and what not. I've only rooted my phone, I have not replaced the G/UI or OS. If I backup my phone on Kies, wipe it and restore the backup, will it restore the root, Superuser, etc? Or just my apps, data, UI layout and what not? I'm beginning to think that I don't know enough about rooting, or just have horrible luck with it, and need to just run the phone stock. Is there a way to root, delete bloatware and unroot?
Thanks in advance for the help! I appreciate it.
KL
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Seriously? No one knows anything about this? There's another post about the same problem that has also gone unanswered.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
klewis1x said:
Okay, what the hell?! Every now and again (usually when I'm running Dolphin Browser and/or trying to cut/copy/paste) I get a floating notification at the bottom of the screen that says 'shell has been granted Superuser permissions'! It flashes a few times and then my phone restarts. When it turns back on, I have to restart Juice Defender and SwiftKey (default keyboard ALWAYS comes back, even if I shut down or restart myself!) manually. I went into the Superuser application the other day and there was nothing in there by the name of 'shell.' In fact, the only two things I have granted Superuser permissions to are Titanium Backup and the Android System (is this the culprit, I wonder). Either way, this problem has become a real pain in my ass. It always happens at the most inconvenient times. I would really, REALLY appreciate a solution to this problem.
Also, I have my phone set up just the way I like it, as far as the layout and what not. I've only rooted my phone, I have not replaced the G/UI or OS. If I backup my phone on Kies, wipe it and restore the backup, will it restore the root, Superuser, etc? Or just my apps, data, UI layout and what not? I'm beginning to think that I don't know enough about rooting, or just have horrible luck with it, and need to just run the phone stock. Is there a way to root, delete bloatware and unroot?
Thanks in advance for the help! I appreciate it.
KL
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Does it happen every time you copy paste something? Have you tied other browsers to copy paste from?
Something could have happened during rooting. I assume you have a cusom recovery? I might try and flash Chainfire's root method found here http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip It will just overwrite the supersu and the su binaries.
If that doesn't do anything for ya I would Odin back to the stock rooted ROM found here http://forum.xda-developers.com/showthread.php?t=1739426 and start over. Or try one of many great custom ROM that are available.
I don't know what else you could do. If you could get a logcat it would definitely help find out why you are having these issues, and actually solve them. There are plenty of resources on how to obtain a logcat here on xda. Or try an app from the store to save the logcat. PM me with the attachment and I will look at it for you.
I could be totally wrong. BUT I think its samsung doing it. When I denied it permissions it restarted. I did it again and it did the same. I think its intertwined b.c I never had it with AOSP roms

Categories

Resources