On XT1095 - Pure Edition running 5.0 stock, unlocked.
I used ChainFire's autoroot batch (semi-)successfully. SuperSU is updated and prompts normally when apps request access. Problem is that even though they have been given root access, they don't. Root Checker app verifies that my device is rooted.
I have also tried the Multi-Tool which again rooted but same results (then soft bricked when I tried to install custom recovery). I have brought back my device to stock with SolarTran's Guide and tried the whole process over, again nothing seems to work.
Any help would be appreciated.
Related
Previously, I installed Cyanogenmod (http://download.cyanogenmod.org/?type=RC&device=mb886), and still had root access, but there was an issue with the baseband.
So I just installed HoloBlur (http://forum.xda-developers.com/showthread.php?t=2356624), fixed the baseband (http://forum.xda-developers.com/showthread.php?t=2233871) and now it seems that I do not have full root access and Superuser binaries will not update.
First, I downloaded the superuser binaries and zip files to try and update them that way (http://androidsu.com/superuser/)
But that didn't work so I downloaded and used this (https://play.google.com/store/apps/details?id=com.noshufou.android.su.fixer&hl=en), which crashed after trying to gain root access. No superuser options show up in settings, and Superuser wants to crash. I have tried superuser from Chainfire and Koush. Neither can update binaries, and the version by Koush wants to crash. I assumed I didn't have root access.
I have tried using motochopper again (http://forum.xda-developers.com/showthread.php?t=2227938)
and I have tried using Myth Tools again (http://forum.xda-developers.com/showthread.php?t=2262726) (basically another motochopper...)
Neither have worked.
So:
How do I gain root access again if none of the above methods work? Is it possible?
Yes, bootloader is still unlocked, and CWM is still installed. Just, no root access.
Flashing superuser.zip should work. That is what I did when I installed holoblur. I would need to find the link though
Sent from my Atrix HD using Tapatalk 4
That fixed it. Sorta.
Went back into CWM recovery, selected to install from zip, and installed the zip from here: http://androidsu.com/superuser/
This was the one that worked:
(3.2-RC3)
md5: 6462ac14cd38ed7c539ce3e29a6b92a8
Superuser-3.2-RC3-arm-signed.zip
Apps are now gaining superuser/root access but it doesn't seem to be working like the normal superuser.
The default superuser apps still aren't working.
I'll have to check up on it more when I get back from classes.
Oddly enough, the chainfire superuser app now installs correctly.
For some odd reason, it requested access from the first one installed. Either way, it's working, and it seems as if all the apps that need root access are getting it. I don't see any special Superuser settings in the menus, but I'm guessing that's just a feature i've been seeing in all the roms.
Long story short: Problem solved
Hope this topic helps anyone who has similar issues.
I was rooted updated my phone and lost root. I factory rest my phone and supersu was showing as a system app. So I enabled unknown sources and now I am on new update and back to root. I have installed several apps that require root access and everything works perfect. Hopes this helps you
When I purchased my Droid Maxx it was running 4.2.2 and I used the PIE exploit to root it. At the time, I didn't realize that allowing the 4.4.4 OTA update would completely frag the root so I took it. Now, on 4.4.4 I of course have very buggy and inconsistent root access. So, I decided to just unroot and forget about it for this phone. To that end, I ran a full unroot from SuperSU and the app disappeared. Great...until I rebooted and it came back. I went back into the app, disabled it via the app settings, full unroot again, and again the app reappears on reboot. I can't delete the apk from the System folder because even with SuperSU enabled it won't grant me write access (see above: root fragged). So what the hell am I supposed to do? The phone is essentially unrooted, but on every reboot, regardless of unroot attempts, SuperSU reinstalls itself.
Any ideas on how to get rid of it?
Either root it properly and use that to remove it, or reflash your full stock firmware.
Hello everyone,
I'm having an issue - I wasn't able to flash the newest extracted firmware in the development section so I went ahead and just ran the full RUU. I've been running custom roms for years and I decided that maybe I just wanted to run stock rooted for a while so I unlocked my bootloader again, flashed the most recent TWRP and installed the most recent SuperSU zip.
Unfortunately it does not seem to have rooted my phone. SuperSU is indeed installed in the system folder and it prompts for root permission when I use root apps, but even when I grant permission the apps cannot obtain root access. What happens is it looks like they are going to get root access, the phone slows down a bit for a second, and then I get an error message from the app in question saying that either my phone isn't rooted or that root permission has been denied. If I open SuperSU, it lists all of my root apps with the green hashtag indicating that permission is granted.
Am I correct in assuming that installing SuperSU did not root my phone? If so, is there a way to root without installing a custom rom?
For clarification, this is all on the most recent RUU, software version 6.23.651..10, Lollipop 5.0.2
Thanks in advance.
Which version of SuperSU are you flashing?
Sloth said:
Which version of SuperSU are you flashing?
Click to expand...
Click to collapse
Well I'm a dolt, I was using v1.69 but now I see that is a very old version. Going to try 2.46 right now, thanks.
Edit: Same issue on 2.46 :/
For anyone still looking at this thread, I was able to achieve root by flashing the newest SuperSU, version 2.52 which is actually still in beta and therefore not offered if you go to the main portion of the SuperSU website.
SuperSU v2.65 is the current stable offering
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Make sure you did reboot after root activation in dev options
Yes, as I said, I already rebooted. Any other idea?
ulysseh said:
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Click to expand...
Click to collapse
ulysseh said:
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Click to expand...
Click to collapse
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Davey126 said:
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Click to expand...
Click to collapse
Yeah, I did the whole thing from zero again. Happily it worked this time. Thanks!