I have had dirty unicorn for a while, and it has been fine, but I was trying to back up with titanium and it said I didn't have root. Is there something I can do? I thought to update SU in the play store, and now my phone says that the SU binary is out of date, and when I open SU, it says "The Superuse binary (su) must be updated. please choose method of install, and I press recovery install since only other is cancel, and then it says "THere was an error installing. Please send log of the error to the dev. Should I be installing super SU from recovery?
I think the latest TB has issues. I lost root but had up-to-date su's. And root for all else. I wiped caches and fixed permissions and it worked. Otherwise get previous TB and don't allow it to update. You could also un-reinstall app. Believe there is a link to previous one at end of one of the rom threads, maybe Jamison's?
NO--Here for previous TB
http://forum.xda-developers.com/showthread.php?t=2537495&page=99
Sorry, I am in too many threads--
rugmankc said:
I think the latest TB has issues. I lost root but had up-to-date su's. And root for all else. I wiped caches and fixed permissions and it worked. Otherwise get previous TB and don't allow it to update. You could also un-reinstall app. Believe there is a link to previous one at end of one of the rom threads, maybe Jamison's?
NO--Here for previous TB
http://forum.xda-developers.com/showthread.php?t=2537495&page=99
Sorry, I am in too many threads--
Click to expand...
Click to collapse
Do you mean fix permsions and wipe cache in recovery?
Edit* I tried to do this, but it didn't fix the root problem. I still don't have root and I did install that older TB too
joeym11 said:
Do you mean fix permsions and wipe cache in recovery?
Edit* I tried to do this, but it didn't fix the root problem. I still don't have root and I did install that older TB too
Click to expand...
Click to collapse
Yes, that is what I meant. Do you have root with other apps like root explorer. there are root checker apps and you can use terminal emulater and type su.
If tb is only app not working as root. un and reinstall it. I remember one time I had to rebuy it.
Also, do you have a working nandroid of your rom where tb was seeing root--if not I would do one, if possible, before trying other things.
This is a flashable SuperSU zip thru recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/sVQpu6e2VL/UPDATE-SuperSU-v1.69.zip
Related
I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Twolazyg said:
I have seen a lot of people saying they are losing root access if they update SU Binary. I am to assume everyone who has lost their root access did it via some sort of one-click root app. These will only give temporary root access and will break root at the slightest kick in the teeth.
Anyway, I have updated my SU binary, and I still have my root access, I gained root via [GUIDE] How to Root Sprint 2.1 Release for CDMA Hero and I'm S-off. Hope this helps clear up any issues with SU.
Click to expand...
Click to collapse
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
poashll said:
I rooted same as you. When I updated binary and was on aosp 0.1.2, I did loose ability to use su like in terminal.
I was able to flash a different recovery with adb so I think it didn't wipe root but something with GB and the super user app didn't work together with the new binary.
I successfully updated binary in froyo. Were you using GB when you updated, and if so, which version?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Twolazyg said:
I was running aospGBmod 0.1.4, updated, then went into root explorer (worked), TE (worked), and TB (worked). I also deleted the old SU that came with the ROM, D/L'd the one from market, then updated. I'll try it again with 0.1.2 and test it out. Also, are you S-off or S-on?
Click to expand...
Click to collapse
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
poashll said:
I am S-on.
I just attempted it again using 0.1.4, but I have the same results. Nothing is able to get root rights.
I should've nandroided before trying that. I know better.
Click to expand...
Click to collapse
Reboot recovery and go back to your last nand, then reboot into whatever rom you were running. Uninstall SU, reinstall from the market, you should be fine then. But I would make a nandroid just to be safe
I attempted to uninstall and reinstall, but it didn't help.
Now that I have updated to 0.1.5, I can upgrade the binary and everything is working as it should.
Sent from my HERO200 using XDA App
I am on 2.3.3 and just updated SU Binary. Haven't noticed a problem yet. All previously installed root apps still work, newly installed root apps work as well.
disregard. I am retarded and didn't read what forum this was in.
My phone's still rooted, I used the same method as you.
I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.
BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)
Just rooted again and its still the same...
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?
Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.
I currently have the 4.4.2 Google Play edition rom by Danvdh installed. I was performing a backup to flash the new 4.4.3 through CWM.
After the backup, there was a message that root may be lost and if I should fix it. I selected 'Yes'.
After the reboot, I no longer have root access. I have tried to re-root with motochopper and it continues to fail.
Can I restore a backup to regain my root? Or is there another way to regain my root access?
I tried searching for similar issues but could not find one that addressed my problem specifically.
Thanks in advance.
FIXED!!!
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
tuffgong2k3 said:
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
Click to expand...
Click to collapse
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
sway8966 said:
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
Click to expand...
Click to collapse
Ahhh, thanks sway. I obviously did not find that section. I thought I had the latest CWM, but I guess I didn't. Time to update.
Hi, Can someone please help, I must have done something wrong. Flashed official 4.1.6 update through twrp successfully, but lost root, tried to flash super su again (ver 2.86), but got stuck in boot, logo froze.
Flashed 4.1.6 again, phone works but no root still.
Is that a wrong super su version or did I do something else wrong?
Help will be really appreciated.
Regards
After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.
Magisk all the way
1. Wipe data
2. Flash ROM
3. Flash root package, either SuperSU or Magisk
4. Reboot
I see no reason why wouldn't this work for you
Didgeridoohan said:
After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.
Click to expand...
Click to collapse
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards
dua999 said:
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards
Click to expand...
Click to collapse
When you flash the rom it will already be uninstalled
sakumaxp said:
When you flash the rom it will already be uninstalled
Click to expand...
Click to collapse
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers
dua999 said:
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers
Click to expand...
Click to collapse
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk
sakumaxp said:
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk
Click to expand...
Click to collapse
Thanks all for help, all sorted