I am rooted, and unlocked, but when I use EZ-Recovery to flash the TWRP recovery image, it only stays until the phone is rebooted. Is this how it is supposed to work?
Basically if I open EZ-Recovery and flash TWRP then reboot to recovery its fine. After I reboot FROM TWRP back into Android, the recovery is back to stock.
JAYNO20 said:
I am rooted, and unlocked, but when I use EZ-Recovery to flash the TWRP recovery image, it only stays until the phone is rebooted. Is this how it is supposed to work?
Basically if I open EZ-Recovery and flash TWRP then reboot to recovery its fine. After I reboot FROM TWRP back into Android, the recovery is back to stock.
Click to expand...
Click to collapse
I was having the same problem I just installed goomanager and installer TWRP from there and it stuck.
Tap'n
techgov8 said:
I was having the same problem I just installed goomanager and installer TWRP from there and it stuck.
Tap'n
Click to expand...
Click to collapse
That worked! Thanks a ton! I thought I was the only one having this problem.
JAYNO20 said:
That worked! Thanks a ton! I thought I was the only one having this problem.
Click to expand...
Click to collapse
I used cwm for a while and finally made the switch to twrp I like the gui a little better with the touch screen
Tap'n
Related
Long story short ..I already had EZ Recovery 2.2 installed but then I had to flash my phone & i ended up installing Team Win's Recovery UNOFFICIAL-2.2.2.1
So I was wondering is there any way to uninstall TWRP? or should I just get rid of EZ instead
Thanks
projektHAZE said:
Long story short ..I already had EZ Recovery 2.2 installed but then I had to flash my phone & i ended up installing Team Win's Recovery UNOFFICIAL-2.2.2.1
So I was wondering is there any way to uninstall TWRP? or should I just get rid of EZ instead
Thanks
Click to expand...
Click to collapse
EZ Recovery is only an app. Flash whatever recovery you want and it will replace your current recovery.
prdog1 said:
EZ Recovery is only an app. Flash whatever recovery you want and it will replace your current recovery.
Click to expand...
Click to collapse
Thanks! much appreciated
How do I convert from CWM to TWRP properly?
I searched around and it seems that I should just be able to use goomanager and install open recovery script. I do that, I see it download TWRP and then it says recovery installed, but when I reboot recovery, it still takes me to CWM.
If I go into ROM Manager, it looks like both recoveries are installed and then clicked to use TWRP and it still booted in CWM.
Then I used ROM Installer to install TWRP and now it reboots into TWRP when I reboot into recovery.
But, when I go into ROM Manager, it still says that CWM is installed. Do I need to get rid of that? If so, how?
I would try this. Odin to CWM, uninstall ROM Manager, and then use Goomanager to update to TWRP.
sfobrien said:
I would try this. Odin to CWM, uninstall ROM Manager, and then use Goomanager to update to TWRP.
Click to expand...
Click to collapse
Not exactly sure what Odin to CWM means. Odin is software on my PC? Will that be destructive in any way? Right now, it does all seem like it's working fine except that ROM Manager sees CWM there too.
Any other ideas?
Install flashify from the play store.
Download your recovery .img of choice.
Flash .img using flashify, reboot to recovery.
GideonX said:
Install flashify from the play store.
Download your recovery .img of choice.
Flash .img using flashify, reboot to recovery.
Click to expand...
Click to collapse
I don't think I need that. I have TWRP installed and it boots to it, but ROM Manager says that CWM is also installed. Is it really there? Do I need to get rid of it and if so, how?
lexluthor said:
I don't think I need that. I have TWRP installed and it boots to it, but ROM Manager says that CWM is also installed. Is it really there? Do I need to get rid of it and if so, how?
Click to expand...
Click to collapse
If you reboot to recovery, what recovery does it take you to?
If it's TWRP, disregard the notice from Rom Manager.
GideonX said:
If you reboot to recovery, what recovery does it take you to?
If it's TWRP, disregard the notice from Rom Manager.
Click to expand...
Click to collapse
TWRP.
Ok, I'll just ignore that then.
lexluthor said:
TWRP.
Ok, I'll just ignore that then.
Click to expand...
Click to collapse
Uninstall Rom Manager while you're at it.
lexluthor said:
Not exactly sure what Odin to CWM means. Odin is software on my PC? Will that be destructive in any way? Right now, it does all seem like it's working fine except that ROM Manager sees CWM there too.
Any other ideas?
Click to expand...
Click to collapse
I meant install CWM with Odin. Uninstall ROM Manager first.
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Bump
Sent from my HTC One M8!
U WOT M8?
AP26322 said:
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Click to expand...
Click to collapse
Have you tried pushing back the stock recovery and then doing a factory reset?
droidkevlar said:
Have you tried pushing back the stock recovery and then doing a factory reset?
Click to expand...
Click to collapse
I have not. Where can I find the stock recovery?
AP26322 said:
I have not. Where can I find the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
droidkevlar said:
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
Click to expand...
Click to collapse
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
http://forum.xda-developers.com/showthread.php?t=2708291
Try it.
AP26322 said:
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
Click to expand...
Click to collapse
NP
I've been running TWRP 2.6.0.0 but it doesn't seem to be working with some of the newer roms. It seems difficult to update TWRP these days. GooManager throws an HTTP error at start up and when trying to update the recovery it claims it can find one for my device. The fastboot usb method doesn't work well in 8.1. Would you recommend moving to another recovery?
fredrick255 said:
I've been running TWRP 2.6.0.0 but it doesn't seem to be working with some of the newer roms. It seems difficult to update TWRP these days. GooManager throws an HTTP error at start up and when trying to update the recovery it claims it can find one for my device. The fastboot usb method doesn't work well in 8.1. Would you recommend moving to another recovery?
Click to expand...
Click to collapse
Download the free 4ext recovery updater app and flash latest recovery using the app. No need for fastboot
http://4ext.net/
jmcclue said:
Download the free 4ext recovery updater app and flash latest recovery using the app. No need for fastboot
http://4ext.net/
Click to expand...
Click to collapse
That worked great thanks! Painless install!
fredrick255 said:
That worked great thanks! Painless install!
Click to expand...
Click to collapse
I have a sensation XE, i would highly recomend the 4EXT recovery as well. However i think the only issue i have ever come across it was when i selected "auto reboot" when using a kernal update with the aroma installer. As long as i leave it unticked, i can perform updates without any boot issues on startup.
This afternoon I applied OTA 3.1 to my Shield Tablet, and reinstalled CWM and flashed supersu. My tablet booted correctly but I don't have root. If I open the SuperSU app, I get "there is no SU binary installed and SuperSU cannot install it. This is a problem!" anyone know how to fix this?
Thanks
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
sixstringedmatt said:
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Aventura5 said:
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Click to expand...
Click to collapse
I'm having the same problem.
Im also with the same problem, on 3.0 i used kingroot, but with 3.1 doesnt work also.
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
King root 4.5 works to root easily
Got it rooted again
I finally got it rooted again.
1) Put supersu.zip on to sd card.
2) Flashed TWRP with ADB fastboot.
3) Rebooted into recovery.
4) Flashed supersu.zip from the sd card.
5) Rebooted
After that it was finally rooted again. Hope this helps anybody else who has this problem.
Unfortunately though since I got my tablet when it first came out I have a recalled one. This will be my 4th RMA. LOL
danjull said:
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
Click to expand...
Click to collapse
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
EDIT: This worked and now CWM sticks, but i still get the SU binary not installed error.
Aventura5 said:
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
Click to expand...
Click to collapse
No. It restores stock recovery on first reboot.
Kingroot worked for me guys
What I don't understand is how the zip can install the SuperSU app as a system app, but not install the SU binary. Is it possible to manually copy the Su binary to my device? I have root access in recovery mode.
Dose anyone have any idea why this happens?
It works now with the new version of supersu
Is there a guide for rooting the shield from 3.0 and up? Thanks.
tecnoworld said:
Is there a guide for rooting the shield from 3.0 and up? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
tecnoworld said:
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
Click to expand...
Click to collapse
It dose say for 2.0, but it should work on everything. This is the "real" way, other methods are hacks that work only on certain versions. I prefer this method, it gives you the most insurance against damage, but you could always just use kingo root. Also, versions 2.x and 3.x are both lollipop.
Aventura5 said:
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Click to expand...
Click to collapse
Just out of curiosity, doesn't fastboot boot (image of recovery) just boot into the recovery and not flash it?
From previous experience, to reflash recovery you need something like flash_image or a way to write the image on the recovery partition... Correct me if I'm wrong...