[Q] app "system" package "system" requesting superuser permissions
I just noticed when my phone was booting (using AOKP m3 if that is relevant) that I was getting a "system has been granted superuser permissions" shortly after I log in. I removed the allow entry from superuser, and now when I boot I get a App : system Package : system is requesting root(0). Is this normal? I feel like the system shouldn't need root permissions, and any app that actually does should be identifying itself.
Anyone else experiencing this (or has?) I'm tempted to wipe the phone and start-over; I don't like granting superuser permissions to things that don't identify themselves properly. (Alternatively, is "system" a real thing that should be requesting superuser permissions?)
Thanks!
*if this should be moved to the Q/A forum, please do that? I placed it under CDMA android dev because I think it may have something to do with my rom or otherwise.*
Yea that's normal for that rom. Its the ROM control function that is built in.
Sent from my Galaxy Nexus using xda premium
cshort0982 said:
Yea that's normal for that rom. Its the ROM control function that is built in.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ive been on AOKP for weeks now and System just requested root yesterday?. I was going to ask the same question but found your answer here, thanks for that! Also the ROM control needing root for System sounds very plausible, but its weird that it is just now requesting it after all this time.
I just had this happen to me with my GalaxyTab 10.1 (7510wifi). It has stock rom and restore, however it is rooted.
Related
I have instslled Beastmod rom in my samsumg galasy s2. Yesteday I receive on my phone a new software system update from tmobile to install. My question is if I install this software update it would affect the Beastmod rom?
No flashing an official update on a custom rom is only asking for a bootloop
You can read this thread here but the basics are;
1) If you've only rooted your phone, (no custom ROM or kernel), you can let the update be applied and it should update correctly. Some folks have reported that it unrooted their phone in the process while others say it didn't.
2) If you've rooted your phone and installed a custom ROM, (like you say), then the update won't work, and will probably just boot you to the CWM screen. Your phone won't be affected but you'll still get the update notifications.
3) If you want to stop the update notifications, one method is to delete the data for the Device management app, and then freeze the app using something like Titanium Backup, NoBloat or SystemCleanup.
4) Or you can navigate to /system/app and delete or rename, wssyncmldm.apk and wssyncmlnps.apk
Good Luck..
Thank you very much jasnn and zelendel!!!
you can use perfect backup. look into system apps. click on device management -> details. -> clear cache. it clears it up for a few days. then you can repeat until there's an update on the ROM you have. that's what i've been doing and im using the beatmod v4.2 really good rom.
jasnn said:
You can read this thread here but the basics are;
1) If you've only rooted your phone, (no custom ROM or kernel), you can let the update be applied and it should update correctly. Some folks have reported that it unrooted their phone in the process while others say it didn't.
2) If you've rooted your phone and installed a custom ROM, (like you say), then the update won't work, and will probably just boot you to the CWM screen. Your phone won't be affected but you'll still get the update notifications.
3) If you want to stop the update notifications, one method is to delete the data for the Device management app, and then freeze the app using something like Titanium Backup, NoBloat or SystemCleanup.
4) Or you can navigate to /system/app and delete or rename, wssyncmldm.apk and wssyncmlnps.apk
Good Luck..
Click to expand...
Click to collapse
What is the difference between wssyncmldm.apk and wssyncmlnps.apk? I know that wssybcmldm.apk is the device management app.
Sent from my SGH-T989 using XDA App
wssyncmldm.apk is the Device Manager UI and wssyncmlnps.apk is the actual updater.
jasnn said:
wssyncmldm.apk is the Device Manager UI and wssyncmlnps.apk is the actual updater.
Click to expand...
Click to collapse
Ahh OK. So freezing the UI only wouldn't prevent it from downloading updates. . . Just informing you of them.
Sent from my SGH-T989 using XDA App
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
qtwrk said:
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
No good, I tried installed superuser
Sent from my Galaxy Nexus using xda premium
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
andQlimax said:
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
Click to expand...
Click to collapse
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
qtwrk said:
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
Click to expand...
Click to collapse
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
simms22 said:
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
Click to expand...
Click to collapse
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
qtwrk said:
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
Click to expand...
Click to collapse
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
simms22 said:
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
Click to expand...
Click to collapse
It's app for system optimization or something like firewall, kill auto run apps, process management...
Ok... were you able to get root access?
Sent from my Galaxy Nexus using xda premium
I have done as described in this link: //reviews.cnet.co.uk/mobile-phones/how-to-root-the-samsung-galaxy-note-2-50009855/
Result: Root Check: get message that system is very slow
Titanium Backup keeps the message "asking for root rights..." and stays on this message
BusyBox: "There was a problem opening a shell..."
Si I have clearly problem with my Rom but have no idea how to fix it.
Any help?
You have to oviously grant permission to the root app.
And try using a stock custom rom like omega cause it has int.d support and all tweaks.
You will find the rom in the android development section of this forum.
Make sure you have latest tb and supersu. I had this problem before update.
Sent from my GT-N7100 using xda app-developers app
clayteau said:
You have to oviously grant permission to the root app.
And try using a stock custom rom like omega cause it has int.d support and all tweaks.
You will find the rom in the android development section of this forum.
Click to expand...
Click to collapse
Seems to be a cool app but still Titanium Backup is not working. It freezes with "Asking for root rights" in white letters and black background without any botton to accept. When I look for app within Titanium I get (finally) message "I could not acquire root priveleges. Please verify that your rom is rooted. This attempt was made using the "/system/xbin/su" command"
Same for Root Checker with message "System appears to be running very slow" and also BusyBox with message "problem opening shell".
beside that my phone is working perfectly. Have now as well the Multi window module.
So how can I make Titanium make work?
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
android88 said:
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
I'm curious, but would it just be a matter of updating the binaries with Superuser?
treefrog321 said:
I'm curious, but would it just be a matter of updating the binaries with Superuser?
Click to expand...
Click to collapse
Well, I downloaded a fresh copy from the market, and when I open it it doesn't update. Just shows no apps are assigned to it..
Sent from my SGH-T989 using xda app-developers app
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
There are some /bin and /xbin files too.
Sent from my Nexus 4 using xda premium
blackangst said:
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Click to expand...
Click to collapse
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Thanks for the help and input guys
blackangst said:
Thanks for the help and input guys
Click to expand...
Click to collapse
Did you get it working the way you wanted?
RealPariah said:
Did you get it working the way you wanted?
Click to expand...
Click to collapse
Im gonna follow the advice that supersu is better and use it for awhile
RealPariah said:
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Click to expand...
Click to collapse
Can I do this with replacing Superuser with SuperSU (I'm running Avatar ROM & I miss using SuperSU)?
Guys/Gals,
I am running the newest version of PACman ROM by klin1344 on KToonsez Ktweaker kernel.
Cleanly installed, with newest Gapps
What I need help on:
I have an in settings superuser app (the new opensource settings integrated one from Koush) and I also have the standard SuperSU.
I was able to remove SuperSU, but wasn't getting prompted for any root requests afterwards. I also then went into the in-settings SU app to update the binary but wasn't prompted at all. I am wondering if I SHOULD be seeing a binary update prompt from the in-settings SU app? (this might be the extent of my issue) or if more steps need to be taken to migrate from 2 separate apps to one.
Any help is greatly appreciated!
Links to info I looked at: http://www.droiddog.com/android-blo...s-the-play-store-brings-open-source-goodness/
http://www.droiddog.com/android-blog/2013/03/cyanogenmod-integrates-cwm-superuser-into-settings/
http://forum.xda-developers.com/showthread.php?p=38760467
Edit:
turns out, after removing SuperSU and rebooting I still retained access to root but I am no longer getting prompted for it nor do any of the apps requesting the permission get logged in the in-settings Superuser app.
You need to install the superSU app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Gotcha and that handles which apps get access correct?
Is there anyway to boil it down to the single in-settings app? Or do u think supersu is the only way, currently, to handle su requests?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app