Hi,
I've just flashed on my GT-P7510 tab the last ROM 4.0.4 from Russia, I've rooted my device. Because any reason when I try to disable any app from startup (system boot) list using both, System Tuner and Startup Cleaner, after 4 or 5 seconds since unchecking the corresponding app checkbox, it automatically check back again... Only System Tuner gives me the error message "Failed to disable event!"...
Of course, I'm root (I checked system tuner to have root permision) and I had not this problem on previous ROM (also 4.0.4).
Thanks in advance if anyone knows someting about this issue.
EDIT: I've just tried autostarts and same issue, the message given is "Unable to change the state of the selected component. Most likely, your device does not have root access, which is required", but previous this message, I saw the given permission message from superuser !! Also, I have overclocked the tab so, I'm root!!! Maybe half root ?¿?¿?¿?¿
Startup Auditor seems it works for me... but I think that, as startup manager, it kills the apps once they are started, instead of prevent the startup as System Turner, autostarts and startup cleaner...
It seems as my root process is not full done (?¿?¿)
SOLVED: I installed superSU and its su bin instead of using superuser and now root is full...
jaswinky said:
Hi,
I've just flashed on my GT-P7510 tab the last ROM 4.0.4 from Russia, I've rooted my device. Because any reason when I try to disable any app from startup (system boot) list using both, System Tuner and Startup Cleaner, after 4 or 5 seconds since unchecking the corresponding app checkbox, it automatically check back again... Only System Tuner gives me the error message "Failed to disable event!"...
Of course, I'm root (I checked system tuner to have root permision) and I had not this problem on previous ROM (also 4.0.4).
Thanks in advance if anyone knows someting about this issue.
EDIT: I've just tried autostarts and same issue, the message given is "Unable to change the state of the selected component. Most likely, your device does not have root access, which is required", but previous this message, I saw the given permission message from superuser !! Also, I have overclocked the tab so, I'm root!!! Maybe half root ?¿?¿?¿?¿
Startup Auditor seems it works for me... but I think that, as startup manager, it kills the apps once they are started, instead of prevent the startup as System Turner, autostarts and startup cleaner...
It seems as my root process is not full done (?¿?¿)
SOLVED: I installed superSU and its su bin instead of using superuser and now root is full...
Click to expand...
Click to collapse
Hi mate, can you explain how you installed supersu bin? because I have rooted phone with supersu and lot of apps with root access work fine on my 4.4 but can disable any startup app with any tool... with autoruns keeps telling me the same told to you
Thanks,
sebadamus said:
Hi mate, can you explain how you installed supersu bin? because I have rooted phone with supersu and lot of apps with root access work fine on my 4.4 but can disable any startup app with any tool... with autoruns keeps telling me the same told to you
Thanks,
Click to expand...
Click to collapse
Kit kat has that bug, and tool updates should fix it in the future. While it happens, you can delete system apps easily by deleting its apk on system/app using any root file Explorer.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
Kit kat has that bug, and tool updates should fix it in the future. While it happens, you can delete system apps easily by deleting its apk on system/app using any root file Explorer.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
Hello and thanks for you response! what a pity! if you in chance know the id or something of the bug I would really like to read more. Anyway I will try the forum.
So, I can delete the apk, but cant stop one app from autostarting "after boot" strange bug!
sebadamus said:
Hello and thanks for you response! what a pity! if you in chance know the id or something of the bug I would really like to read more. Anyway I will try the forum.
So, I can delete the apk, but cant stop one app from autostarting "after boot" strange bug!
Click to expand...
Click to collapse
There is no too much info about it. I thing it has to do with a new permission management for apps in kit Kat (there is some info about it on the Web), and tools still haven't been update to make full compatible with this KK "improvement", so i really don't think this is a KK bug as is.
Enviado desde mi GT-I9500 usando Tapatalk 2
I have just updated muy moto x ti 4.4.2 stocks, I get root access and installed every app I used to have and now I can disable and enable any app as in my paste 4.2.2 version!
Enviado desde mi XT1053 mediante Tapatalk
..
greenify worked for me :good:
Related
I have tried to update my Xperia Z tablet (Wi-Fi Xperia Tablet Z SGP311) but it fails each time. Bootloader is locked, and it is rooted. SuperSU(in survival mode) and the voodoo OTA root keeper are on.
Not sure why it wont flash to 4.2.2 (current stock 4.1.1 rooted).
Also Wondering if I should even bother updating to 4.2.2 this way or try the flashtool kernel workaround doomlord has?
Hello, i've the same problem with my SGP321. SuperSu in survivalmode and rootkeeper installed too.
Sent from my Xperia Tab Z using Tapatalk 4 beta.
Someone else had issues with update not installing, and someone asked if any system files have been modified?
If you do the OTA update only (as you stated), you dont need the OTA rootkeeper, just superuser ticked with survival mode, and SU installed as a system app (in settings menu). Maybe SU and OTA keeper conflicting, maybe OTA modify system files?
If you decide to install SU as system app, it might take several attempts, and several power downs. When I did it, it did not seem to be working, and tooks loads of reboots and attempts
Aid777 said:
Someone else had issues with update not installing, and someone asked if any system files have been modified?
If you do the OTA update only (as you stated), you dont need the OTA rootkeeper, just superuser ticked with survival mode, and SU installed as a system app (in settings menu). Maybe SU and OTA keeper conflicting, maybe OTA modify system files?
If you decide to install SU as system app, it might take several attempts, and several power downs. When I did it, it did not seem to be working, and tooks loads of reboots and attempts
Click to expand...
Click to collapse
Well I told voodo to remove its backup and uninstalled it. SuperSU is now a system app with survival mode on. Tried it again and same thing it gets about a quarter done installing then stops. Anyway to check to see if there's an error log?
Oh and I don't believe I messed with anything in the system files
Rainami said:
Well I told voodo to remove its backup and uninstalled it. SuperSU is now a system app with survival mode on. Tried it again and same thing it gets about a quarter done installing then stops. Anyway to check to see if there's an error log?
Oh and I don't believe I messed with anything in the system files
Click to expand...
Click to collapse
Do you have xposed framework installed?
WythDryden said:
Do you have xposed framework installed?
Click to expand...
Click to collapse
nope, was considering doing that tho
I'm in the same boat. Stock 4.1.2 rooted with su as system app and survival mode on, but nothing else. Install fails every time. Sgp312
I had the same problem. The cause was a modified /system/apps folder. As a solution i copied the missing files from a FTF-File back.
If for example facebook.apk is missing the update will fail.
Oh wow, didn't consider that getting rid of some of the bloat would count. Go figure Facebook would **** it up for me. I don't have a computer anymore at home so I guess I'll start figuring how to get back what I got rid of.
..could anyone upload that system/apps/ folder? In the meantime I guess I can try pulling the ones from the zip of the Japanese stock ROM posted around here..
I can't find any way of extracting a .sin in android
Never mind. Copying the missing files out of the Japanese zip worked and I'm successfully updated!
thanks ill have to do the same it seems, yeah i belive I nailed a good lot of the bloatware :/
My have found my issue I updated youtube with an official but not from the stock app. Now I cant seem to downgrade from the apk from the global ftf. Any help on why root explorer would crash the tablet when trying to reinstall it?
Rainami said:
My have found my issue I updated youtube with an official but not from the stock app. Now I cant seem to downgrade from the apk from the global ftf. Any help on why root explorer would crash the tablet when trying to reinstall it?
Click to expand...
Click to collapse
Does it crash when reinstalling or when running the app?
Sent from my SGP312 using XDA Premium HD app
jonathanp said:
Does it crash when reinstalling or when running the app?
Sent from my SGP312 using XDA Premium HD app
Click to expand...
Click to collapse
Yes it does, I try to reinstall and it eather says fail, or crashes the tablet. But the youtube app works for some reason?
I can't update via OTA. I have everything, i deleted Chrome but i reinstall and still fails.
Enviado desde mi GT-I9100 usando Tapatalk 2
DOOMF1GHTER said:
I can't update via OTA. I have everything, i deleted Chrome but i reinstall and still fails.
Enviado desde mi GT-I9100 usando Tapatalk 2
Click to expand...
Click to collapse
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
WythDryden said:
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
Click to expand...
Click to collapse
What is xposed framework? I have no mods. Only ad Block.
Thanks
I did a factory reset, install nothing else but the root (super SU, obviously) and I still can't install the update via OTA. Any ideas?
Enviado desde mi SGP311 usando Tapatalk 4
WythDryden said:
Your best bet is to copy the entire system/app from stock over to your device. Also uninstall xposed framework or any other mods
Click to expand...
Click to collapse
attempted this, used ADB to remount the system as r/w and was copying over the first of the files fine with push but as soon as it hits the lockscreen.apk it crashes the tablet. Then have to go do the command line fu to get the darn thing remounted. And did it again. Any suggestions?
Rainami said:
attempted this, used ADB to remount the system as r/w and was copying over the first of the files fine with push but as soon as it hits the lockscreen.apk it crashes the tablet. Then have to go do the command line fu to get the darn thing remounted. And did it again. Any suggestions?
Click to expand...
Click to collapse
Hmm, not sure. I did it all from within the tablet using solid explorer. I compared the two folders and just copied over the apks that were missing.
Hello, would appreciate help. I didn't care about warranty issues so I installed stock 4.3 on my international n7105 using the Kies update and rooted it and all works perfectly. I installed the new version of SuperSU and it asked me to remove Knox which I did. All seemed perfect and rooted programs like TItanium Backup and others are working perfectly. HOWEVER, I then tried to use tasker to access secure settings rooted parts of "parition lock" and also "VPN root" to setup auto vpn and with both of these apps I am told they fail to run the task and get the "unauthorized access..." notification telling me to "click here" I do and nothing happens. I have frozen all aspects of Knox in Titanium backup and still these programs are being blocked.
Any suggestions on how to disable it completely? Am I missing something? I want full control.
Thanks!
There's also an app called "ELM and somewhat" and "security policy update (or something)(with a white/grey shield)". This must be freezed too.
I use my Note in an other language so the apps names could be diffrent, sorry for that.
I have rooted my Note II without any KNOX warranthy void and without annoying messages.
I rooted my note this way:
-I have tapped 7 times on kernel version in settings/about device
-Than I choose developper options and tick on USB DEBUGGING
-pressed the home button
-now I started a program on my PC called KINGOROOT (you can download it here: http://limelinx.com/7j76)
-Run the program and give shell root permission. Wait untill 'finished' shows up on the pc
-Open SuperSu and disable KNOX
-Open Titanium Backup and freeze al knox related things + the ELM thing + security policy update (white/grey shield)
- Now you are completely free. Root without any pop ups and nodifications!
-And an extra: download (the latest) XPOSE installer with Wanam module.
You can make your system status official so you can receive OTA updates and you also can unable your favourite apps in multiwindow.
This should be in the Q and A section... not in dev
Sent from my GT-N7105 using XDA Premium 4 mobile app
DuratecPaul said:
This should be in the Q and A section... not in dev
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
great info though!
R0B3RTF1SH3R said:
great info though!
Click to expand...
Click to collapse
yes I learnt a thing or two from his reply.
ten ten ten
i have don that and work very well
delete all that you can see....
in system/containers/framework
KNOXModeSwitcher.apk
sec_container_1.zzzKnoxLauncher.apk
In system/app you need to pwn....
(1&2) KNOXAgent.apk & KNOXAgent.odex
(3&4) KnoxAttestationAgent.apk & KnoxAttestation.odex
(5&6) KNOXStore.apk&KNOXStore.odex
Found in System/framework
(7) KNOXModeSwitcher.apk
(8) sec_container_1.zzzKnoxLauncher.apk
Found in System/etc
(9) com.sec.knox.store
Found in system/lib
(10) libknoxdrawglfunction.so
Thanks for all the help. I tried to do it but one error kept coming. Ended up just installing the Lion version on here and it is working perfectly with no problems.
Thanks,
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.
Hi, anybody knows how to disable com.xiaomi.finddevice from auto starting? This process is really hard to block. Ive already frozen it, disable all services, broadcast recievers & activeties and it is still runnig consuming 20-40mb ram.. Process kill makes it restart. Ive already frozen most of xiaomi bulszit incl. Cloud backup etc. Not even sign in because of 0 gain from the services. cheers
Root your phone,use root explorer ,system/priv-app/and delete folder FindDevice .
mihayash said:
Root your phone,use root explorer ,system/priv-app/and delete folder FindDevice .
Click to expand...
Click to collapse
Cool, it worked. Thanks
Reviving this old thread. Do not try this on newer MIUI OS's (e.g. mine is Mi 11 running on MIUI EU 12.5.9).
I tried setting up a Magisk module to replace FindDevice with no content inside. The phone went into boot loop.
Had to use TWRP to delete my module before my phone can boot up once again.
Are you sure this is the right forum? It's virtually impossible to isntall Mi 11 in the Redmi Note 2 rofl
Debloater to remove "Find Device" after rooting with Magisk.
Hi,
I am currently on the latest version of global dev (MM)
After removing system apps (even gapps like Gmail and so on), the phone doesn't boot
It has this loading boot animation at the bottom, and after it finish "loading", half a minute later it's starts again
I want a debloated version of miui.
Is there any rom that provides that out of the box?
Try below MIUI debloating script..
http://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-miui-t3372437
What all you meant by 'so on'.. Now to get the Phone working again, Re flash the rom again.. Uninstall only those apps, you know for sure..
Sent from my Xiaomi Mi 5 using XDA Labs
Thanks for the replies
I have tried to Uninstall those apps which on the post but resulted in the same result.
And by "so on" I mean that every system app uninstalled results in a bootloop
The only thing I could uninstall was the precomed Facebook app
shose said:
Thanks for the replies
I have tried to Uninstall those apps which on the post but resulted in the same result.
And by "so on" I mean that every system app uninstalled results in a bootloop
The only thing I could uninstall was the precomed Facebook app
Click to expand...
Click to collapse
You are doing it wrong...
you are just uninstalling apks. there are folders on /system/app which contains oat, if you uninstall just apk there will be bootloop
If you have twrp then goto file manager of twrp and goto /system then app or priv-app and goto folder of that specific app for example you want to delete google drive then open google drive folder and give Chmod 777 permission to that folder *THIS IS COMPULSORY* then delete the entire google drive folder...
This is what that script do...
Please hit thanks if i help you ????
shose said:
Thanks for the replies
I have tried to Uninstall those apps which on the post but resulted in the same result.
And by "so on" I mean that every system app uninstalled results in a bootloop
The only thing I could uninstall was the precomed Facebook app
Click to expand...
Click to collapse
You can uninstall all the Google system apps, which are available in the play store.. So that you can install and uninstall anytime you want to.. But see to that you don't do that to play store, play services or the framework..
Sent from my Xiaomi Mi 5 using XDA Labs
I need to give chmod permission to the folder I delete or to the outer folder?
And I give the permission through twrp? (I have the zcx twrp)
shose said:
I need to give chmod permission to the folder I delete or to the outer folder?
And I give the permission through twrp? (I have the zcx twrp)
Click to expand...
Click to collapse
For what.? Uninstalling.?
Sent from my Xiaomi Mi 5 using XDA Labs
For deleting those apps (uninstalling = deleting apps, isn't the right way)
By what iceman says, it need to be done by the permission delete
shose said:
For deleting those apps (uninstalling = deleting apps, isn't the right way)
By what iceman says, it need to be done by the permission delete
Click to expand...
Click to collapse
Not necessarily, you should do from recovery.. Instead, Boot up the phone.. Install Link2SD or other root app manager.. Grant root permissions to it.. Clear the data of the system app.. Uninstall it.. Simple
Sent from my Xiaomi Mi 5 using XDA Labs
http://forum.xda-developers.com/redmi-note-3/how-to/miui-8-global-dev-bloater-recovery-t3465318
easier...just flash these scripts....no bootloops here.
Slightly off-topic I had this problem with a similar device. After rooting my phone I installed a system-app-uninstaller to get rid of the "Google App". Removing this specific app caused continuous boot looping.
To avoid this, I duckduckgo'd the problem and found this anonymous closed&deleted (but ingenious) post at Reddit:
{
[deleted] 2 points 2 years ago
Hey! I figured out a way to delete the app(using root of course) without causing a bootloop. The secret is to go to Settings>Apps>Advanced(In the top right)>Deafult Apps>Assist & voice input>None. After doing that, reboot, and then u can delete the app
}
Yes i made the mistake of changing the setting to "None" and then immediately uninstalling it.
Don't do that!
After restoring my twrp backup for the millionth time, I changed the setting to "None", rebooted my phone, disabled and force-stopped the service, rebooted my phone... And then uninstalled it. Victory!