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.
Related
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
KidCarter93 said:
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
Click to expand...
Click to collapse
one of those 4.2.2 roms didn't have root i can't remember which one, they forgot superuser or something
KidCarter93 said:
Hi guys,
I just went into system apps, via Solid Explorer to grab an apk to put on my dev-host, when I got an error saying that I don't have root access.
I tried accessing other files in system root to get the same error. So I downloaded Root Checker and for some reason that's also saying that I don't have root access.
I know for a fact I have though as I've just been using root only features in ROM Toolbox Pro without an issue.
Any ideas as to why it's saying I don't have root access when I clearly do?
I'm on stock 4.2.2 and used the rooting tools in mike1986.'s thread to root once I'd flashed the stock ROM.
Click to expand...
Click to collapse
Hey,
Does SU allow permission to access solid explore???
Click Thank if you find my post as useful
Aldo101t said:
one of those 4.2.2 roms didn't have root i can't remember which one, they forgot superuser or something
Click to expand...
Click to collapse
I downloaded the deodexed version which had superuser installed by using the rooting tools.
I flashed it a few days ago and have had no issues with being rooted until now. As I say, I'm still rooted but my phone's telling me I'm not and I'm not sure why.
Sent from my HTC One using xda premium
naren_viswa said:
Hey,
Does SU allow permission to access solid explore???
Click Thank if you find my post as useful
Click to expand...
Click to collapse
It already had the permissions from when I first installed solid explorer.
I just found out what my problem was. Superuser was installed by default and I downloaded SuperSU afterwards and must've disabled superuser and therefore was getting partial unroot issues.
I've now uninstalled superuser and I've got full access back
Sent from my HTC One using xda premium
Hi
I have tested the root tool from China forum. My device is SGP312 WIFI 32GB 10.3.1.C.0.136. No need to unlocked.
Download the attachment and install. One click and then it will reboot. It is rooted!
But the root-mangement software is Chinese. You can download Supersu or Superuser.
Use the Chinese root software to give Supersu or Superuser root access.
Run Supersu or Superuser and upgrade the binary. Exit and uninstall the Chinese root software.
Reboot. Then you are rooted with Supersu or Superuser.
This is the original link: http://www.mgyun.com/vroot
incredible...works on sgp321 .244......good job....juat install supersu afterwards and remove the chinese app....greatttttt
Good! I can confirm it works, just rooted my still locked SGP311FR with it.
What I don't like it's an exe file, install the app then run it to root.
If someone can extract the script and replace the root apk by superSU it would be cool.
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Anyway thanks.
Btw : @insideccw posting a link to the source, and maybe the name of the autor of this tool, would be better if it's not your own tool.
babylonbwoy said:
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Click to expand...
Click to collapse
That might be the exploit that is accessing the framebuffer causing it.
works like a charm on my sgp351 lte 16gb .244, recomended, thans for the post
Also working with Xperia sp
Sent from my C5303 using Tapatalk 4
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Word fine With 4.2.2 thx a lot
Sent from my SGP321 using XDA Premium 4 mobile app
bugger561 said:
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Click to expand...
Click to collapse
I think you need to install the alternative superuser app before deleting the Chinese one. I used superuser by chainsdd on my sp
Sent from my C5303 using Tapatalk 4
works great...thanks
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
I don't know if the info in this thread may be of any use : http://forum.xda-developers.com/showthread.php?t=1539711.
Specifically in the OP :
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
And in Post #8 :
Confirmed working fine! Recommended to install via CWM. It will replace the other (superuser) automatically so you don't have to manually remove it.
I used the above zip file and instructions a long time ago on my Galaxy S....but it may still be relevant for Tablet Z.
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
bugger
That is because you dont have /system r/w access.
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
It worked for me...I accidentally removed the Chinese app.
1. I did a reroot again.
2. installed dualrecovery and flashed the UPDATE-SuperSU-v1.65.zip.
3. It works now.
Supersu and cwm superuser caused my phone to go in a reboot loop when I tried updating the binaries. Superuser by ChainsDD is working fine though.
Sent from my C5303 using Tapatalk 4
insideccw,
Any tips on how t go about correcting this? Would I need to use adb or can I handle this form within android?
EDIT: Looks like others are having the same issue.
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Geezer said:
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Click to expand...
Click to collapse
Works on mine. Update the superuser binaries before deleting Chinese superuser app. On mine, supersu detected the Chinese one and deleted it for me
Sent from my C5303 using Tapatalk 4
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
For those of you having this issue as I was, I just got mine to work with SuperSU. Hopefully these steps will work for you too:
-Gain root with the magical Chinese root tool
-install SuperSU
-update SuperSU binaries
-in SuperSU settings, choose "Switch superuser app"
-reboot the tablet and immediately go to the playstore and install SuperSU
-update SuperSU binaries
Let me know if it works!
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.
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!