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...
Related
I rooted my phone at 4.0.2, then applied the update up to 4.0.4 and am still able to flash new versions of clockwork mod through rom manager... However, all my other apps won't be granted root access. In the superuser application, I'm running superuser v3.0.7(41) and my Su binary is at v3.0.3, for which there is an update available. However, when I try to apply the update, it tries to ask for root privileges and gets denied access... I tried reflashing su.zip through clockwork mod touch but I guess I may be flashing an outdated su.zip? Any insight into the matter would be greatly appreciated!
Same here
Same exact scenario, I went from 4.0.2 to 4.0.4, and even after a factory restore I cant seem to get root access for any app. I checked the bootloader, and I still am rooted.
Help appreciated for us both!
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
ezcats said:
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
Click to expand...
Click to collapse
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Clockwork recovery does not require root if it is already installed. If not, fastboot clockwork recovery.
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
evanextreme said:
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Click to expand...
Click to collapse
Flash from recovery, not an app.....
Sent from my Galaxy Nexus using xda premium
jerseyh22accord said:
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
Click to expand...
Click to collapse
This did the trick!
Had this same problem earlier
I need help
I am having the same problem. I am a noob and it sucks cause I can't figure it out. I can't even go into recovery since I installed 4.0.4 someone please dumb it down so i can understand
Install busybox free, then install titanium backup free. Open busybox and click inatall. Then run
Titanium backup, it will ask you do you want it to configure root, accept this. please note After completing busybox steps reboot. Then after titanium backup steps reboot again
Did this help?
If not pm me and il see if i can help
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
brightsideme said:
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Try flashing this:
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
brightsideme said:
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Do you have CWM installed yet?
If not...
I'd recommend simply starting from the top and using my guide.
But if you have CWM:
Just navigate to "Install Zip From SD Card"
"Choose Zip"
And find it.
Yes to install.
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
brightsideme said:
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
boot to clockworkmod manually, than flash the superuser zip from here http://www.box.com/s/jvcf196j7x8f8vrc9cyt (this does not require busybox, that why the other su zip was failing)
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
brightsideme said:
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Jubakuba said:
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Click to expand...
Click to collapse
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
andQlimax said:
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
Click to expand...
Click to collapse
nope, he was getting a permissions error because rom manager didn't have root access, that was the issue there.
edit: re-read the post, yes, you might be right about busybox in stock recovery, although i believe cwm has a set of minimal busybox tools.
if manually booting into recovery by shutting down the phone, pressing power+vol up until Google screen appears, doesn't take him to cwm but to stock recovery, he doesn't even have cwm installed, which could very well be the case, since stock rom default behaviour overrides any existing recovery when flashing.
I'm on a Vzw G-Nex and running the CM10 nightlies. the issue I'm having is that some apps like Titanium get superuser privileges and that gets remembered. other apps, like Wireless Tether, it asks me EVERY time I after I launch and then select the start tether and then again when I select stop tether.
I also see a warning when in CW recovery that root appears broken and it offers to fix that but I found out the hard way that this doesn't seem to fix anything and can break things instead...
when the phone was running the stock rom and was just unlocked and rooted, I did not have this issue.
it would seem that I'm partway rooted and partway not? any suggestions/ideas please?
*bump*
anyone got anything?
tgeery said:
*bump*
anyone got anything?
Click to expand...
Click to collapse
use supersu instead of superuser. heres a flashable in recovery version http://download.chainfire.eu/212/SuperSU/CWM-SuperSU-v0.96.zip
after you flash, open the supersu app, if it says to update your su binaries, press yes. if the problem still persists, update your busybox.
simms22 said:
use supersu instead of superuser.
after you flash, open the supersu app, if it says to update your su binaries, press yes. if the problem still persists, update your busybox.
Click to expand...
Click to collapse
thanks... I'll give that a shot.
my N7 2013 does not update to JSS15Q? i am having JSS15J now, my device is rooted using TWRP recovery. I got update notice but after reboot, it goest to TWRP installed something, then i need to manual reboot it. after all these, I still having JSS15J, what is wrong?
yuanfei said:
my N7 2013 does not update to JSS15Q? i am having JSS15J now, my device is rooted using TWRP recovery. I got update notice but after reboot, it goest to TWRP installed something, then i need to manual reboot it. after all these, I still having JSS15J, what is wrong?
Click to expand...
Click to collapse
Install the OTA again. See what the error is.
If you rooted with SuperSU prior to v1.55 and didn't apply the fix, then that is probably your problem.
Thanks
what is the fix you refering?
It is explained here:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
However, as I mentioned, the fix is incorporated into SuperSU v1.55
thanks
when I root, I used SuperSU 1.51, but later it get update from google play, now is 1.65.
my recovery is twrp 2.6.0.0.
Do I still have the issue mentioned in that thread?
I get it works.
Thank you for the help.
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.
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