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!
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.
SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?
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 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.
I used CF Auto Root a while back to root my Nexus 6 (months ago). It did the trick getting the bootloader unlocked and rooting the phone. I then proceeded to install TWRP and then installed Pure Nexus. From then to know the phone has been a joy to use. This ROM is fantastic.
Recently I decided to look into custom Kernels, Elementalx is the one I have been reading up on. I installed the kernel, and then purchase the EX Kernel Manager. Using the app I realized that the phone wasn't rooted, or so it told me. I test this with the Root Checker Basic App and it confirmed that the phone was not rooted.
I am not sure what happened but what I wanted to do was run the SuperSU zip via TWRP again, but wanted to ask you guys if this would be an issue. I can't see why it would but it Rooth had already been achived and then it was gone so..... I just wanted to ask in case.
Sorry that this was a little long winded. Thanks in advance.
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Strephon Alkhalikoi said:
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Click to expand...
Click to collapse
Thanks for the quick reply. That makes sense. I will run SuperSU again. Take care.