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.
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.
The subject pretty much says it all. Now that we have S-Off again (yay, way to go developers) which would you use and why, CWM or TWRP? Pros? Cons?
twolostminds said:
The subject pretty much says it all. Now that we have S-Off again (yay, way to go developers) which would you use and why, CWM or TWRP? Pros? Cons?
Click to expand...
Click to collapse
I've used both CWM and TWRP pretty extensively over the last few years but I have settled on TWRP just because I like the layout and ease of use. So far I haven't ran into anything that didn't play nice with either one, so for me its an aesthetic choice.
I've only used TWRP once. A lot of people are using it these days because of the theming options and it being faster than CWM but I've read too many reports about various flashes not working properly with it. Stability trumps coolness for me so I'm sticking with CWM.
I've used TWRP since I got my rezound way back when and have used it since then there where some issues fliashing kitkat when it first came out. Philz is a nice recovery too.
Sent from my HTC6500LVW using Tapatalk
Santods twrp is the best.
I wanted to chime in here: I've used both on my HTC one for Verizon and I seem to have a problem with both. After using JCase's root app and successfully getting s-off, I'm not able to get either recoveries to flash the superuser apk so that I can sustain root access. This is preventing me from flashing any rom. I know that a bunch of other people on this forum were able to get their roms flashed on so I was wondering if it's something I've done wrong, or just incompatibility with these 2 recoveries?
Steps I took:
1) installed JCase's weaksauce app, rebooted
2) obtained root, downloaded SU from market
3) proceeded with firewater to obtain s-off (successful)
4) installed clockwork recovery via fastboot.
5) proceeded to install superuser, unsuccessful.
6) rebooted phone, uninstalled SU (from 1st installation prior to s-off)
7) attempted to reinstall SU from Clockwork - fail.
8) flashed TWRP recovery, attempted to install SU, failed.
Not sure if there are other recoveries that I should be trying?
Thanks for the help!
Bobert360 said:
I wanted to chime in here: I've used both on my HTC one for Verizon and I seem to have a problem with both. After using JCase's root app and successfully getting s-off, I'm not able to get either recoveries to flash the superuser apk so that I can sustain root access. This is preventing me from flashing any rom. I know that a bunch of other people on this forum were able to get their roms flashed on so I was wondering if it's something I've done wrong, or just incompatibility with these 2 recoveries?
Steps I took:
1) installed JCase's weaksauce app, rebooted
2) obtained root, downloaded SU from market
3) proceeded with firewater to obtain s-off (successful)
4) installed clockwork recovery via fastboot.
5) proceeded to install superuser, unsuccessful.
6) rebooted phone, uninstalled SU (from 1st installation prior to s-off)
7) attempted to reinstall SU from Clockwork - fail.
8) flashed TWRP recovery, attempted to install SU, failed.
Not sure if there are other recoveries that I should be trying?
Thanks for the help!
Click to expand...
Click to collapse
Are you sure you obtained S-Off? One S-Off is complete, uninstall weaksauce, and flash recovery via fastboot (makes sure your using the latest cwm or TWP. I used this one http://forum.xda-developers.com/showthread.php?t=2416431
Boot into recovery and flash SU. Worked like a champ for me.
dcorrea said:
Are you sure you obtained S-Off? One S-Off is complete, uninstall weaksauce, and flash recovery via fastboot (makes sure your using the latest cwm or TWP. I used this one http://forum.xda-developers.com/showthread.php?t=2416431
Boot into recovery and flash SU. Worked like a champ for me.
Click to expand...
Click to collapse
Thank you so much for your response. Yup, when I hold down the power and volume down button, my hboot says Unlocked at the top (which I believe to be the status of my bootloader) and S-Off.
I flashed recovery via fastboot, and tried what I believe to be the latest versions of both Clockwork and TWRP. I'll check out the link you sent again and will post results.
Question for you, after you uninstalled the weaksauce app, you left SU installed, correct? So the process would be uninstall weaksauce, reboot to fastboot mode, flash recovery, flash rom?
Thanks again!
Bobert360 said:
Thank you so much for your response. Yup, when I hold down the power and volume down button, my hboot says Unlocked at the top (which I believe to be the status of my bootloader) and S-Off.
I flashed recovery via fastboot, and tried what I believe to be the latest versions of both Clockwork and TWRP. I'll check out the link you sent again and will post results.
Question for you, after you uninstalled the weaksauce app, you left SU installed, correct? So the process would be uninstall weaksauce, reboot to fastboot mode, flash recovery, flash rom?
Thanks again!
Click to expand...
Click to collapse
Yep that's what I did. I flashed superuser before flashing the rom though. What error do you get when you try to flash superuser?
Oh wait, I just read your initial post. Youre not trying to flash an .apk through recovery right? You should be flashing a .zip file in recovery.
You don't have to flash super user to flash a Rom either bro as long as you have custom recovery you can flash wahat ever Rom you want ?
Sent from my HTC6500LVW using Tapatalk
coachcrey said:
You don't have to flash super user to flash a Rom either bro as long as you have custom recovery you can flash wahat ever Rom you want ?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yep, just to clarify I originally flashed superuser because I kept the stock rom, but I quickly went to the debloated rom the next day. But Coach is right, you don't need superuser to flash the rom.
Philz touch is by far the most user friendly. Lots of customization options. Its based on cwm but is much better.
Sent from my HTC6500LVW using Tapatalk
I had cwm corrupt all my backups I had. Since then I ran twrp. As far as Rom issues people seems to have outdated twrp version or something about the Rom. When I had a Rom fail to flash while in recovery I would reboot recovery and would then flash just fine
Sent from my HTC6525LVW using Tapatalk
Twrp all the way. Its faster at backup and restore, and themeable.
I had really good luck with TWRP 2.6.3.4 but when I upgraded to 2.7.0.1 suddenly backups failed. Never got an answer back on why that was happening, so I switched to Phiz and haven't had a problem with it yet so I'm gonna stick with it for now.
Philz Touch Advanced CWM is the best recovery, hands down. Try it. You will see.
ccarr313 said:
Philz Touch Advanced CWM is the best recovery, hands down. Try it. You will see.
Click to expand...
Click to collapse
I tried it and wasn't impressed. Every process seemed to take forever to do. With latest twrp I can do a backup in under a min.
Sent from my HTC6500LVW using Tapatalk
Going with TWRP. It's always just worked for me.
Sent from my HTCM8
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.
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
You ALREADY HAVE root with CM-SU. To enable it, just go to developer option and give root permissions to app. Some SuperSU's versions are incompatible afaik. CM-SU preinstalled is just fine.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Meneldur said:
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Click to expand...
Click to collapse
Have you try this method http://forum.xda-developers.com/lg-g2/general/bump-supersu-t3273251
CustomPatcherScript_Bump.zip + UPDATE-SuperSU-v2.65-20151226141550.zip
But it's also can cause reboot loop
Do backup before doing flash that script
That worked fine with my D855 32Gb + CM13