I rooted by phone using the GNex toolkit on 4.2.2. I did everything right, SU had permissions, etc.
I downloaded Purity ROM, leanKernel, and GApps. I installed everything as normal, wiping cache and dalvik after the Kernel. I hit reboot and it came up "Your phone does not have root access, would you like to you? (gave some directory next to yes)" something along those lines.
Not sure what to do, I hit no hoping it would bring me back into recovery but it rebooted my device. The ROM works and everything, but I have no root access, and as far as I'm concerned, there's no root for Verizon 4.3.
I did create a backup of my stock ROM and the ROM right now works perfect.. but how do I regain root access?! I can't even boot into recovery out of ROM Manager.
Help would be much appreciated!
cont...
Further more, I rebooted to recovery, hit reboot, yes root, and it rebooted. Root checker says I don't have root access.
Open up SuperSU, "The SU binary needs to be updated. Continue?" >Continue "How would you like to install SU binary?" >Normal "Installing, please wait" "Installation failed! Please reboot and try again!"
ERGG! Rebooted and got the same thing.
cont...
Android Root User says "You are ROOT."
I deleted SuperSU and installed Superuser. Go to Binary Updater...
-Downloading manifest... okay!
-Parsing manifest... okay!
-Latest version = 3.1.1
-Checking installed version = legacy
-Fixing database... okay!
-Unpacking sutools... okay!
-Checking current install path... /system/xbin/su
-Downloading new binary... okay!
-Gaining root access... fail!
BUMP!
Will flashing my backup give me root privilege again?
Even if, are there any other solutions?
Try installing SuperSU zip via recovery:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
See what happens.
Sent from Google Nexus 4 @ CM10.2
Thanks!
It worked! Thanks bud! Much appreciated.
AndyYan said:
Try installing SuperSU zip via recovery:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
See what happens.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
Related
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Are you s-off? If so not sure what the problem is. If you're not s-off, that's your problem
Sent from my HTC Desire using XDA App
pspuser007 said:
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Click to expand...
Click to collapse
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this zip
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
pspuser007 said:
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
Click to expand...
Click to collapse
If u updated super user through the market, uninstall the update..after that flash the zip in recovery
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
pspuser007 said:
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
Click to expand...
Click to collapse
u never looked in settings/applications?
super user i guess is a system app (like gmails, gmaps, gtalk, etc)..so u can't uninstall those applications..but u can uninstall updates for those applications..mean for system apps u can only uninstall updates
so go in settings/applications, select super user app and u should see uninstall updates, if yes do uninstall updates, if not then its ok and flash the zip
do a nandroid backup in recovery before touch something, just to be sure
I hadn't checked system applications so far.
Unistalled the update, did a nandroid backup and flashed the zip!
Everything OK now!
Thanks a lot for your help!
Many many thanks!!!
what does the zip need to be named?
Does the zip need to be named update or does it stayed named like it is?
Name it whatever makes you happy. Remember its whats on the inside that counts.
Sent from my PG86100 using XDA Premium App
I'm getting the same warning message with my market updated su, when I open Titanium Backup but it hasn't affected anything. I just ignore the message and everything still seems to work. Am I missing something?
Problem Updating
andQlimax said:
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this "goo-inside.me/superuser/su-3.0-efgh-signed.zip"
Click to expand...
Click to collapse
I have uninstalled SU and installed the super user update and I get the following error when I update the binary updater:
"Failed to find currently installed su binary. Update cannot continue"
UPDATE:
I downloaded and installed the binary file (su-3.0-bin-efgh-signed.zip) from androidsu.com and now get FC error "The application Superuser has stopped unexpectedly. Please try again"
Thanks for your help.
When this issue occurred for I found that just by simply reflashing the SU zip in recovery and then running the update fix it seemed to fix it. I think for me it may have had to do with using an outdated version though.
su binary update failed..
Hi, I'm using CyanogenMod 7.1.0 RLS3 for Kaiser.. Today I got a "su binary outdated" I try to update it.. Going ok until "Moving su to it's final location - Fail" how to solve this? guide me please.. I'm newbie..
Hi, I had rooted my Garmin-Asus A50 about a year ago with help from these fora. Also installed Titanium backup and other related apps.
My question: upon waking thisr morning and waking the phone, a message said "SU binary outdated - tap to update" I let it update without thinking -but immediately had doubts about some trojan doing this to gain access.
So I switched off the phone and am trying to gather some info here and on WP. From your post I see that this 'update' message may be legit - or am I wrong?
Thanks ffor any further tips.
.-.
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
Hello, My HTC Desire has
MIUI Android v. 4.1.1
Kernel v. 2.6.38.8
Build nr.2.8.17 MIUI
I am trying the above unsuccesfuly
SuperSU 0.96 will say Installation failed when trying to update (tried several times)
I then disabled as advised and I get a message that uninstallation failed (even if the button is then in the off position)
I install the old superuser, I tap to check updates and I get the following errors:
1. The checked version is 3.0 rather than 3.1.1 (which I think it's not an error since I am using an older version)
2. Everything is OK until is trying to Copying su to system... fail!
Any ideea why?
Thank you!
P.S. Nevermind, I found SU update FIX on googleplay and it did the job.
chrisbard said:
Hello, My HTC Desire has
MIUI Android v. 4.1.1
Kernel v. 2.6.38.8
Build nr.2.8.17 MIUI
I am trying the above unsuccesfuly
SuperSU 0.96 will say Installation failed when trying to update (tried several times)
I then disabled as advised and I get a message that uninstallation failed (even if the button is then in the off position)
I install the old superuser, I tap to check updates and I get the following errors:
1. The checked version is 3.0 rather than 3.1.1 (which I think it's not an error since I am using an older version)
2. Everything is OK until is trying to Copying su to system... fail!
Any ideea why?
Thank you!
P.S. Nevermind, I found SU update FIX on googleplay and it did the job.
Click to expand...
Click to collapse
lol no wonder 1st post didn't work, you're using htc......well i think that's the problem
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
Thanks a bunch! That worked for me on an Android tablet with stock ROM. I had the same problem.
chrisbard said:
Hello, My HTC Desire has
MIUI Android v. 4.1.1
Kernel v. 2.6.38.8
Build nr.2.8.17 MIUI
I am trying the above unsuccesfuly
SuperSU 0.96 will say Installation failed when trying to update (tried several times)
I then disabled as advised and I get a message that uninstallation failed (even if the button is then in the off position)
I install the old superuser, I tap to check updates and I get the following errors:
1. The checked version is 3.0 rather than 3.1.1 (which I think it's not an error since I am using an older version)
2. Everything is OK until is trying to Copying su to system... fail!
Any ideea why?
Thank you!
P.S. Nevermind, I found SU update FIX on googleplay and it did the job.
Click to expand...
Click to collapse
Same problems
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
Thanks a ton for this fix! I was about to throw my phone out of the window but you saved its life.
In step 2. I think it's easier to say: Open SuperSU and deny root access on the Superuser prompt.
Don't get me wrong, I'm not criticizing (destructive).
I just say this because I couldn't find an option to add a denied application in Superuser. Maybe I didn't search too hard...
This works with Xperia-ICS v2i ROM port (http://forum.xda-developers.com/showthread.php?t=1855768).
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
What do you mean by "old superuser"?
That was cool, thanks a bunch!
It worked
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
1 + 2 + 4
Thank you a lot!
Issue Resolved :"Supersu binary failed"
Amigos,
Who is having issue of SuperSU Binary update than they should download the attachment which is an update for SuperSU & install or flash it through "Recovery mode" & reboot. It takes while to get up your device but it works for me.
Cheers.
This is what worked for me:
1. Install Superuser by ChainsDD.
2. Install SuperSU.
3. When the Superuser prompt comes up, click allow.
4. Update the binaries.
Thanks
kljb said:
For those having problem of updating Super SU binary after flashing rom [ROM][ARC/S][.587]JELLY SANDWICH 6.0 STABLE[22-09][Aroma][Uploaded] or any other rom that have the same problem.I found a way to fix it..
1. first try update binary using Super SU for few times, if still installation failed try to download old superuser through play store.
2. Disable superuser for Super SU in settings>Superuser
3. In old superuser, go to info and then tap the "tap to check updates" and update the binary.
4. Then, enable superuser in Super SU and voilaa!!... try it..
Click to expand...
Click to collapse
Worked for me. You saved me from factory resetting my phone!
chrisbard said:
Hello, My HTC Desire has
MIUI Android v. 4.1.1
Kernel v. 2.6.38.8
Build nr.2.8.17 MIUI
I am trying the above unsuccesfuly
SuperSU 0.96 will say Installation failed when trying to update (tried several times)
I then disabled as advised and I get a message that uninstallation failed (even if the button is then in the off position)
I install the old superuser, I tap to check updates and I get the following errors:
1. The checked version is 3.0 rather than 3.1.1 (which I think it's not an error since I am using an older version)
2. Everything is OK until is trying to Copying su to system... fail!
Any ideea why?
Thank you!
P.S. Nevermind, I found SU update FIX on googleplay and it did the job.
Click to expand...
Click to collapse
Worked for me!
tried everything, doesnt work.
Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.
Hey all,
Just installed the Official Cyanogenmod on my N1 and lo and behold, root has run away.
ROM here: cyanogenmod(dot)org/hardware/oppo-n1/#images
I installed the TWRP Recovery and tried to let it install Root and it appears that it sort of does with the SuperSU app, but other root checkers and Titanium fail hard on this.
Anybody got any ideas on how to root Cyanogenmod? (Just sounds weird to say that)
Thanks
Tal
I had to flash SuperSU in recovery. I encountered the same issue. TWRP didn't root, even though it said that it did. Updating SuperSU within android didn't help. So I flashed it manually.
Sent from my N1 using Tapatalk
When you say flashed it manually. Was that through fastboot? ADB? or from the recovery.
Also, are we talking about UPDATE-SuperSU-v1.86.zip from download.chainfire(dot)eu/supersu
I tried that through recovery and still get /system/xbin/su command missing in Titanium.
Thanks
Talung said:
When you say flashed it manually. Was that through fastboot? ADB? or from the recovery.
Also, are we talking about UPDATE-SuperSU-v1.86.zip from download.chainfire(dot)eu/supersu
I tried that through recovery and still get /system/xbin/su command missing in Titanium.
Thanks
Click to expand...
Click to collapse
Ok good News, what I mentioned above through recovery works just fine.
Issues:
Remove all previous instances of it from OS (from inside the SuperSU app, select Switch superuser app or Unroot)
WIPE DALVIK CACHE!!!
Hope this helps others.
Thanks
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods