Hello, trying to update my SU binary. 4.0.4 IMM76K, 3.0.3.2 binary.
I go into superuser, hit update binary, it says OK and says it updated to 3.1. After reboot, it says I no longer have root. I've tried clearing cache/data of superuser, and reflashing the su.zip I have but still nothing.
How to fix?
Anybody?? Tried using the toolkit as well but nothing
Well for anybody else this happens to it appears it may have been an issue with the deodexed pre-rooted IMM76K I used from the Development section.
Reflashed to complete stock IMM76K with the toolkit, re-rooted then updated and it seems fine now. What a PITA
Related
I have rooted my Gnex 4.2.2 after receiving the OTA from VZ. I have CWM 5.5.2.3 and SuperUser Elite 3.1.3 installed. Running SU it doesn't complain about anything. As far as I can tell it thinks things are fine. But trying to run Root Explorer or Titanium backup both complain about not being able to get root access. And opening a terminal and attempting cd /root fails due to permissions. I went into CMW and found it didn't think it was installed so I tried it again and it fails while flashing.
Booting into recovery it shows CMW image 6.0.2.3 which matches the image I pushed via fastboot flash recovery. I tried the "fix permissions" option but it didn't make any difference.
It seems like it isn't really rooted even though I went through the steps. I've done this before successfully on previous Android versions.
Maybe the old su.zip I am using no longer works?
I uninstalled/reinstalled Root Explorer, Titanium Backup, and CMW apps. I could not find a way to uninstall the SU app -- very weird... Hmm.....
Use a new su app and make sure the updated binaries are installed.
Further research showed attempting an update of SU indicated it isn't rooted. Noticed, also, that uninstall of SU isn't an option. Hmmm...
AdvApp said:
I have rooted my Gnex 4.2.2 after receiving the OTA from VZ. I have CWM 5.5.2.3 and SuperUser Elite 3.1.3 installed. Running SU it doesn't complain about anything. As far as I can tell it thinks things are fine. But trying to run Root Explorer or Titanium backup both complain about not being able to get root access. And opening a terminal and attempting cd /root fails due to permissions. I went into CMW and found it didn't think it was installed so I tried it again and it fails while flashing.
Booting into recovery it shows CMW image 6.0.2.3 which matches the image I pushed via fastboot flash recovery. I tried the "fix permissions" option but it didn't make any difference.
It seems like it isn't really rooted even though I went through the steps. I've done this before successfully on previous Android versions.
Maybe the old su.zip I am using no longer works?
I uninstalled/reinstalled Root Explorer, Titanium Backup, and CMW apps. I could not find a way to uninstall the SU app -- very weird... Hmm.....
Click to expand...
Click to collapse
Update CWM to 6.0.2.3 (http://www.clockworkmod.com/rommanager)
Flash SuperSU to 1.25 (http://forum.xda-developers.com/showthread.php?t=1538053)
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.
Every time I reboot my Nexus, it would unroot itself.
When I press the supersu icon, it shows that "there is no SU binary installed, and supersu cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root-consult the relevant forums for your device!"
So, I flash the supersu by using CWM. SuperSU can then be used.
However, when I reboot my phone again, it shows the above message again.
I tried to fully unroot and use the toolkit to root it again. But the problem is still there.
I am using stock rom 4.3 JWR66Y and franco kernel.
Can anyone help me with this.:crying:
I had this problem too; I think it's got to do with using Franco's kernel with SuperSU v0.60 and above. SuperSU 0.55 works for me.
bananagranola said:
I had this problem too; I think it's got to do with using Franco's kernel with SuperSU v0.60 and above. SuperSU 0.55 works for me.
Click to expand...
Click to collapse
Just go to the Franco's Kernel topic, and flash the fixed version from Osm0sis, it's on the last couple of pages...
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
I occasionally get a message stating "cannot update supersu binary. This is a problem" (something to that nature). I usually fix this problem by going into philz recovery and fixing root or manually flashing an older version of supersu. However, every time I reboot the phone I get the same "cannot update supersu binary". I am wondering if this could be a recovery issue. Every time I reboot through recovery or just reboot I have to update binary again. Is there a setting on philz that I am unaware of? I recently downloaded twrp manager and cleared cache and dalvik through that and when the phone rebooted I had no binary update issues.
Another thing I was wondering is could this be a Knox problem? I actually tried ota update to 4.3 ( i was rooted in 4.1.2) and it failed. Some time after manually upgrading to 4.3 I received a android security upgrade request. I did not accept the ota update. Is there any way to check if I have knox on my phone? Thank you
Sent from my SPH-L710 using Tapatalk
One thing I noticed. I dl a previous version of super su in recovery. I will have root access and all my apps that require root will work but there is no super su app. Once I dl supersu from playstore I will not be able to use apps that require root after rebooting
Sent from my SPH-L710 using Tapatalk