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.
ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.
I rooted my phone like 30 minutes before the latest update came out (LG2) and when a friend was playing with it, he updated it. Now it appears I do not have root anymore. How can I get this back so I can flash the CM10 rom on here? If I open super user my first 2 sets of data under "su binary v3.1" are red and then the 3rd item which is /system/xbin/su is green. Let me know if there is any other data I can provide to help assist. Thank you so much!
I lost root last week, titanium backup failed, super user was denied access etc. I tried to update binaries but that didn't work either. However when I booted into recovery it was still clockwork recovery not stock. So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me. If you boot into recovery and it's the stock recovery then my guess is you will probably need to reroot via the Odin method.
coogrrr94 said:
I lost root last week, titanium backup failed, super user was denied access etc. I tried to update binaries but that didn't work either. However when I booted into recovery it was still clockwork recovery not stock. So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me. If you boot into recovery and it's the stock recovery then my guess is you will probably need to reroot via the Odin method.
Click to expand...
Click to collapse
I have CWM installed and i can do the volume,home button, power on button and load into it, but whenever i run any package (includind CWM_superuser.zip i get an error saying Esignature failed. I tried reflashing the CWM but when i open odin i cant get it to show the phone and light up the com port box... any other ideas?
You can't flash the root from recovery zip either? If you haven't tried, that should reroot your phone.
flonker said:
You can't flash the root from recovery zip either? If you haven't tried, that should reroot your phone.
Click to expand...
Click to collapse
Nope gives me the same esignature failure
What about adb?
When you're in CWM recovery you should be able to disable signature verification.
coogrrr94 said:
So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me.
Click to expand...
Click to collapse
Hi. Can u be more specific how u did that. I want also regain my root
kanon104 said:
Hi. Can u be more specific how u did that. I want also regain my root
Click to expand...
Click to collapse
Boot into recovery> go to install zip from sdcard>click on toggle signature verification
That should disable it. Its on by default.
Sent from my SGH-I747 using xda app-developers app
Hostage XII said:
Boot into recovery> go to install zip from sdcard>click on toggle signature verification
That should disable it. Its on by default.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I just did the odin thing again and it worked. What Spring Galaxy means btw?
Ran into Same issue, but still had clockwork mod in reboot, so......
How to regain root if cwm is working is just to reflash team epics root recovery zip in recovery....thats it!!!
Walla
Im not the first to have this issue and not the last, may come to be very difficult in future, whos to say, but if it helps...thanks is appreciated!!
So question is, when we ill we be able to successfully root Android M?
Have tired with TWRP. get stuck on HTC One boot screen.
Had to flash stock ROM via stock recovery...
***
TWRP 2.8.7.0
SupersU 2.46 (also tried beta version 2.52 zip
You need to use latest SuperSU 2.65. Download
When TWRP want to install SuperSU check "Do not install" and reboot.
Hmm, I've done the above and it seemed to install correctly, but the SuperSU app which I installed from the zip is saying "no SU binary installed".
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Click to expand...
Click to collapse
Thanks, I've also tried the app store app, it says "no SU binary installed".
For me, I can't install SuperSU as system app. (not currently available in system-less root mode). And Twrp says I'm not rooted, asks to install
Try 2.64.zip no problems for me
Running 2.65
2.64 didn't work either, still get the same problem. Think I'll just try to install it the system way.
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
It worked well for me too:
http://forum.xda-developers.com/showpost.php?p=64493553&postcount=296:bien:
Gandalforce said:
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
Click to expand...
Click to collapse
MegaGalan said:
It worked well for me too[/url]
Click to expand...
Click to collapse
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
BenPope said:
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
Click to expand...
Click to collapse
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
sssssbarn said:
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
Click to expand...
Click to collapse
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
BenPope said:
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
sssssbarn said:
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
Click to expand...
Click to collapse
thanks for the files... fyi you transposed the numbers in the version of twrp. it is 2.8.7.1.
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Gandalforce said:
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Click to expand...
Click to collapse
I had problems with 2.66 as well. I reported it with a logcat and sticking with 2.65 for now
Same
Gandalforce said:
Same
Click to expand...
Click to collapse
Yeah same here.
Had to install TWRP twrp-2.8.7.1_CPTB-B1-hima and BETA-SuperSU-v2.65-20151226141550. then finally booted in to the OS.
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Your flashing 2.79 sr3 and TWRP rc1
mac796 said:
Your flashing 2.79 sr3 and TWRP rc1
Click to expand...
Click to collapse
I did.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Abbieru said:
I did.
Click to expand...
Click to collapse
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
mac796 said:
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
Click to expand...
Click to collapse
Yes it asks for the password. I don't use a custom ROM
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Have you used that su download before. Maybe you got corrupted download. I'm not on feb yet. Maybe that has something to do with it
Try sr2. Had the same on latest tipsy sr3 didn't work. Sr2 works.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Can you send a screen shot of what you are flashing? The actual files
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Last time I got in a jam I flashed boot image to a and b and that should bring your stock recovery back. Then boot TWRP again and install TWRP then boot to system once, then flash su. I think that's what I did.