Related
Hey everyone,
After I updated to MIUI 1.9.9 today, I lost root. This is my 5th or 6th MIUI update, and I've never had this issue before. I dl'd and flashed it thru ROM Manager. I discovered the problem when I installed Titanium in order to get all my apps/settings back. It gave be the "be sure your ROM has busybox" error message. Any thoughts on how to get back to root? I tried uninstalling Titanium and the Pro key, rebooting, then reinstalling Titanium with no luck. I didn't even get the "countdown" message where you have to allow Titanium root rights. Any help would be great!
Thanks
From MIUI.us
"UPDATE NOTICE: Superuser Permissions need to be enabled via Superuser.apk menu enable superuser Permissions. (Superuser is found in Tools folder)"
open SU, menu/settings/enable.
I don't know If this is different on every phone but on my Desire Z this app is not in the tools but on one of the home screens directly also you I had to kill titanium backup because it didn't try to acquire root again (I restarted the whole phone but I forgot that I could have kill it from application manager).
cartman09 said:
I don't know If this is different on every phone but on my Desire Z this app is not in the tools but on one of the home screens directly also you I had to kill titanium backup because it didn't try to acquire root again (I restarted the whole phone but I forgot that I could have kill it from application manager).
Click to expand...
Click to collapse
Same issue in my Galaxy Tab P1000 GSM after Miui update. Root access rights somehow disabled.
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.
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
I have lineage os android 7.1.1 on my galaxy core prime ve(sm-g361h) and installed snapchat and cant login plz what can i do .
Are you rooted? If so, that's what's stopping you.
A root error will tell you that your login failed. If it doesn't say it failed, then something else is the problem. I suggest using Magisk for root since you can hide superuser from being detected.
Sent from my Nexus 6P using Tapatalk
Basharharash said:
I have lineage os android 7.1.1 on my galaxy core prime ve(sm-g361h) and installed snapchat and cant login plz what can i do .
Click to expand...
Click to collapse
im currently on aosp v2.3.1 on my redmi note 2. when i first imstalled aosp, i went strqight into superSU and fully UNROOTED it. then i restarted my phone. once it restarted, i installed snapchat, logged in and then restarted the phone. i immediately restarted the phone again, flashed superSU. now im booth rooted with snapchat working.
shoeprano27 said:
im currently on aosp v2.3.1 on my redmi note 2. when i first imstalled aosp, i went strqight into superSU and fully UNROOTED it. then i restarted my phone. once it restarted, i installed snapchat, logged in and then restarted the phone. i immediately restarted the phone again, flashed superSU. now im booth rooted with snapchat working.
Click to expand...
Click to collapse
I just tried this way and snapchat still show me (there is a problem in you connection ) i cant know what the reason is
Basharharash said:
I just tried this way and snapchat still show me (there is a problem in you connection ) i cant know what the reason is
Click to expand...
Click to collapse
besides deleting busybox as well, i have no other solutions. sorry. maybe someone else can chime in...
Basharharash said:
I just tried this way and snapchat still show me (there is a problem in you connection ) i cant know what the reason is
Click to expand...
Click to collapse
Is it a connection problem? What error is snapchat giving?
If it's connection, make sure you have internet access allowed for snapchat or something (do you have a firewall?)
From my memory of trying to login to snapchat and the whole root issue was it failed at the verifying device phase. You could also download a safetynet checker app from Google Play to see if you're passing safetynet to help ensure everything is playing nicely.
you could always login on another device then restore it onto your main device.
You will have to use a rom that doesnt have root by default. You then have log in and then flash the root. Mind you that you won't be able to log in on any other device without refreshing from scratch.
Sent from my Nexus 6 using Tapatalk
well that sucks, because my rom comes default with root. i knew it was about root and once all apps was done downloading i unrooted with supersu and snapchat still didn't work. i hope there will be a way around this.
Not sure if anyone is still having issues with the snapchat log in, but i was able to make it work by using this method.
For some reason, I had no issues logging in with my old Galaxy S4, which is rooted.
So
1. I used Titanium Backup and made a backup of the Snapchat app and settings.
2. copied them to an sd card.
3. inserted the sd card into my current Note 4 unlocked, rooted, running LineageOS 14.1.
4. restored the Snapchat backup on the Note 4.
5. Opened the app and was already logged in and have since updated the app and still all is good.
I have not logged out, so I don't know if that will prevent me from logging back in. I keep a copy of that backup on my sd card just incase.
Hope this might work for others that may still be trying.
Thank you
You're amazing
Basharharash said:
I have lineage os android 7.1.1 on my galaxy core prime ve(sm-g361h) and installed snapchat and cant login plz what can i do .
Click to expand...
Click to collapse
Just for anyone who may still need this: Use magisk or another application which can hide root from certain apps, and if you have exposed installed (or EdExposed) just go to settings and you will find a toggle to bypass SafetyNet restrictions
Then you should be able to use snap like normal...
Hello, I have an alcatel pop 4 model 5051x.
4 useless apps consume 50% of the battery and I would like to delete them (force stop does not work) and for that I need to root my phone.
The problem is that this model has the bootloader locked.
I tried a lot of methods, from kingoroot to adb but nothing happened. Yet he is recognized by adb.
I also downloaded all the drivers including qualcomm as well as android studio ...
The phone does not even have a day with these apps, help me please!
And if you have the solution, do not hesitate to explain step by step, thanks!
i succeeded !
I succeeded !!!
For those who are interested :
- install Kingroot 5.3.0 apk on your mobile (uninstall the installed app)
- run the root as many times as necessary, making sure that you have granted the administrator and accessibility rights
when the phone restarts, restart it
- as soon as the phone is rooted (be careful it's temporary but you can start again if necessary), install the flashify app
- choose "recovery image", and choose where you put your twrp http.s://drive.google.com/file/d/0B6EQd1aL0EmWX3I2WEFuVmdUcUk/view
- restart on the twrp (I took the opportunity to make a backup above all, count 10/15 minutes)
- launch the Supersu zip install (SuperSU-v2.82-201705271822) that you have taken care to place at the base of your sd card
- restart, supersu is installed
- to transfer my apps, I chose besides the app uninstall system (root)
And finally, here is your Alcatel pop 4 5051x which holds the load again and you can control without parasites
Hi. Now I need your help, since you succeeded, and apparently you're the only one on xda-developers and on the whole Internet!
As I am a complete newbie, please tell me what exactly did you mean in your last bullet ("to transfer my apps, I chose besides the app uninstall system (root)"), and how do you actually remove the 4 useless apps?
Thanks!
RaNo99 said:
Hi. Now I need your help, since you succeeded, and apparently you're the only one on xda-developers and on the whole Internet!
As I am a complete newbie, please tell me what exactly did you mean in your last bullet ("to transfer my apps, I chose besides the app uninstall system (root)"), and how do you actually remove the 4 useless apps?
Thanks!
Click to expand...
Click to collapse
"App uninstall system (root)" is an app from Google play but you can choose another one of course, just choose one "root" in order to access to app system.
Be careful of what you desinstall. To choose apps, I've looke on the battery, which apps were consuming the most and I uninstalled they after searching the net to make sure they were not needed.
I offered this phone to my son 1 month ago and he works very well included with 3D games with a long life battery !
Just wanted to confirm that this is working. I installed Flashify, downloaded the TWRP img and supersu zip to my SD card in advance to avoid any issues, and after four tries or so it finally rooted. Thanks OP!