Hi, I have 6.0MM ROM on my Lenovo K3 Note (rooted S424) and I found one delictate isssue: Clean Master has problem with root access and can not change Autostart manager options. So, I am not able to boost my phone with closing some autostarted apps. I use SuperSU version v2.65
Do you have any solution?
Thanks
Same Issue
I have the same problem since upgrading to MM. Prior to upgrade, Clean Master had root privileges, but since upgrade, it never requested root and I don't know how to manually force it to. If you find a solution, please post.
Same for me, I tried to search for solutions but I think there is no way,
Related
Morning all,
I have a bit of an unusual issue at the moment. I currently have my Z3c rooted, with unlocked bootloader and running the latest .77 firmware. I also have the read/write permissions fixed through the recovery flash method. . I'm busy trying to uninstall apps via rom toolbox and it just resets the phone when I try to do this. They arent even system apps, just apps I may have installed earlier that I now want removed. Not sure what the issue is here because I've uninstalled rom toolbox and tried again but with no success. It will freeze them fine but it wont uninstall them without causing a phone reboot.
Anyone else come across this issue at all and if so, is there a way to sort this out.? Any other information you may need to help out with this issue, I will be glad to provide.
Thanks very much.
Since a few days now my root access has lost.. Had used CF-Auto Root and while was reading around noticed that other people are facing this issue too.. Can anyone suggest what needs to be done to get the root back.. People have failed while retrying CF Auto Root...
Getting an error while opening SUPERSU>>> There is no SU Binary installed, and SUPERSU cannot install it. This is a problem If you just upgraded to Android 5.0, you need to manually re-root-consult the relevant forums for your choice...
Can someone help please...
I recently used the "New Root Method For 5.1.1 w/o custom kernel" to root my otherwise stock Note4 SM-N910T.
Everything was fine, but after a few weeks I lost root. I was able to get it back by re-flashing SuperSU 2.65 from recovery.
After further research, I found the blog post by Chainfire on SuperSU 2.74, and understand that 2.74 addresses the Samsung security update.
I've been using "SuperSU 2.65 Stable" because of root access compatibility issues with some programs.
How do I know if the Security Policy update was the cause of losing root? My phone's About Device has "Android Security Patch level" as 2015-11-01. So it doesn't look like something that was updated in the last week.
If it was not the security policy, then what caused the loss of root?
I have automatic updates off, and did not update anything at the time I lost root. Is there any other way that an update or change can be pushed? My /data/security/spota folder is empty. Should I delete the empty folder just to be sure?
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Supersuer said:
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Click to expand...
Click to collapse
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
timg11 said:
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
Click to expand...
Click to collapse
This has only happened once? Interestingly, I had the same exact issue happen to me on my S5 with MM, I rooted using chainfire and just out of the blue, all root privelages were dismissed. So I flashed SuperSU v2.65. It happened multiple occasions until I was able to switch to an AOSP ROM. After going completely custom it seemed to have stop doing this. Maybe because of a contrast of coding that differ in security.
Sent from my SM-G900P using XDA-Developers mobile app
It has happened twice. I'm working on a Tasker recipe that will check for root regularly and report when it is lost.
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
timg11 said:
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
Click to expand...
Click to collapse
Nobody seems to have any idea what's going on. I'm guessing the loss of root was specific to SuperSU 2.65.
Here what I've tried today:
1) Recovery / Flash with SuperSU 2.65 to get root back.
2) Update SuperSU Pro to 2.76 from Google Store. Download and copy ZIP to phone storage just in case.
3) reboot and verify root still available from Titanium Backup
4) Uninstall ES File Explorer Pro. Install Solid Explorer
5) Test root access of Solid Explorer. It works. Buy Solid Explorer.
6) reboot again just to be sure root remains
7) Backup with TB.
So far, everything is working. Hopefully it will remain rooted.
Almost 3 weeks, and no loss of root. Super SU 2.76 seems to fix the problem.
J500G lost root minutes after connected to internet. I have to root every single day.
Root Issue Reporting - "Could not access the package manager.Is the system running?"
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
kevinkoo said:
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
Click to expand...
Click to collapse
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
bkk99213 said:
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
Click to expand...
Click to collapse
Thanks man! I just resolved this issue, actually it's quite easy.. I just unchecked the option "Mount namespace seperation" in SuperSU, then everything works fine now!
Hello, for a long time I have had this problem with root and bank apps on my (redmi note 8, cr droid, android 13). My mistake was not disabling root when trying to update the rom I had before (evolutionX), from that moment on I had problems with my bank apps, even when I had all the settings to hide root (and even when I completely uninstalled magisk), the banking app detected me as if I had it (as seen in the image). I had to do a hard reset and install a new ROM (crdroid), with that the applications worked for me, but when I try to install the root again and configure everything to hide it, I still have the same problem. Before making the mistake of not disabling root to update the rom, everything worked correctly with the banking apps, with root enabled. I hope you can help me with this, since I have been trying to solve it for a long time. I am aware that it was my mistake (a very dumb mistake) in not disabling root to flash the rom. Greetings and sorry for my english
What are the steps you are taking to hide root?