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.
Related
Does anyone know why a zip might flash though rom manager but not through the bootloader recovery?
spdwiz18 said:
Does anyone know why a zip might flash though rom manager but not through the bootloader recovery?
Click to expand...
Click to collapse
ClockworkMod supports unsigned zips, while stock recovery doesn’t
NVMENOR said:
ClockworkMod supports unsigned zips, while stock recovery doesn’t
Click to expand...
Click to collapse
Thank you, but i know this.
i guess better explanation would help.
my problem is that i have cwm 3.0.24 installed throught the bootloader so i :
hold vol - up and power- this taked me to bootloader i use vol down to go to recovery and power to execute. it takes me to cmw 3.0.2.4 like it should. There are no errors.
i choose install zip from sd card and choose zip and it goes through the install. i reboot and what i flashed is not there.
BUT: if i flash through rom manager which uses cmw 3.0.2.4 it installs just fine.
Any one have any ideas
spdwiz18 said:
...i choose install zip from sd card and choose zip and it goes through the install. i reboot and what i flashed is not there....
Click to expand...
Click to collapse
Only happened to me once when I tried to install super user app, and that was because I forgot to mount the system partition before flashing the update. Maybe it is the same situation, but I have never used rom manager app, I flash directly from recovery.
NVMENOR said:
Only happened to me once when I tried to install super user app, and that was because I forgot to mount the system partition before flashing the update. Maybe it is the same situation, but I have never used rom manager app, I flash directly from recovery.
Click to expand...
Click to collapse
i will check it out and report back. thank you for your quick reply
First of all, yes, this question has been asked, but in different forums for different phones.
I would like to know how to upgrade my clockwork recovery from 5.0.8.0 to the newest version. Is it just a matter of flashing a zip from sd IN recovery?
Thanks!
Download rom manager from the market. It will update recovery to the latest version.
keithgrobertson said:
First of all, yes, this question has been asked, but in different forums for different phones.
I would like to know how to upgrade my clockwork recovery from 5.0.8.0 to the newest version. Is it just a matter of flashing a zip from sd IN recovery?
Thanks!
Click to expand...
Click to collapse
Install ROM MANAGER from Market , and select the first option on that...
it will download and update the CWM Recovery.
mathrania said:
Install ROM MANAGER from Market , and select the first option on that...
it will download and update the CWM Recovery.
Click to expand...
Click to collapse
Thanks. I started Rom Manager, and it said I don't have root acheived, which I do. SuperUser did not ask for a request from this app... So I ignore that warning, and choose flash clockworkmod recovery, and it downloads, but says it cannot complete the request.
Edit:
I found a download for 5.0.2.0 img file that I can just flash on HBOOT. Thanks guys.
keithgrobertson said:
Thanks. I started Rom Manager, and it said I don't have root acheived, which I do. SuperUser did not ask for a request from this app... So I ignore that warning, and choose flash clockworkmod recovery, and it downloads, but says it cannot complete the request.
Edit:
I found a download for 5.0.2.0 img file that I can just flash on HBOOT. Thanks guys.
Click to expand...
Click to collapse
Yes you need to be rooted inorder to use ROM Manager properly.
Don't use ROM Manager, it's ****. Best way is to use fastboot and do it manually
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
I'm using TWRP recovery right now I just wanted to know how I can install CMW over TWRP
why would you do that? cmw is known for having issues on this device
however, to answer your question, the easy way is thru rom manager
lostassassin said:
I'm using TWRP recovery right now I just wanted to know how I can install CMW over TWRP
Click to expand...
Click to collapse
I have GooManager. You can flash recoveries from there. You can also use Flash GUI bull****. (It sucks)
from what I know goo manager flash twrp; rom manager flash cwmr
850RPM said:
from what I know goo manager flash twrp; rom manager flash cwmr
Click to expand...
Click to collapse
Yeah I think that's right. But why would you ever want to switch from TWRP?
I'd use fastboot to flash a new recovery. It's easy to do and the most recent twrp versions have issues. Goo manager only flashes the newest version afaik.
Sent from my HTC One S using xda app
I didn't know CMW had problems ill just stick to TWRP
if i wanna change to cm download the file
fastboot your device
go into cmd promt
type in fastboot flash recovery RECOVERYNAMEGOESHERE.img
and your done
also remember the recoveryfile has to be in the adb/fastboot folder on your pc.
you can use hasoons A1O tool also (flash custom, then locate the file)
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...