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)
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
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
So in my attemts to in stall CM 11 (http://forum.xda-developers.com/showthread.php?t=2570965) I have ruined mt tablet.
This is what I did.
1.Flashed TWRP 2.6.3.0 via (http://teamw.in/project/twrp2/97) I down loaded that latest .blob file and flashed with fastboot.
2. booted into TWRP
3. nothing would mount.... shutdown.
4. booted into my curent PAC Rom 4.3
5. Rebooted straight into recovery from the rom (I thing this is what screwed the pooch)
6. Boots into TWRP and only into TWRP but nothing is mounted. I cant get into fastboot to install the old recovery and 2.6 doesnt see any drives.
Any help would be great!
bucket81 said:
So in my attemts to in stall CM 11 (http://forum.xda-developers.com/showthread.php?t=2570965) I have ruined mt tablet.
This is what I did.
1.Flashed TWRP 2.6.3.0 via (http://teamw.in/project/twrp2/97) I down loaded that latest .blob file and flashed with fastboot.
2. booted into TWRP
3. nothing would mount.... shutdown.
4. booted into my curent PAC Rom 4.3
5. Rebooted straight into recovery from the rom (I thing this is what screwed the pooch)
6. Boots into TWRP and only into TWRP but nothing is mounted. I cant get into fastboot to install the old recovery and 2.6 doesnt see any drives.
Any help would be great!
Click to expand...
Click to collapse
To install CM11, you need the TWRP posted in the guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
cmendonc2 said:
To install CM11, you need the TWRP posted in the guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
Thanks but I cant get into Fastboot to flash that version. Is there a way I can use the flashable zip? I cant mount anything in my curent version of TWRP.
bucket81 said:
Thanks but I cant get into Fastboot to flash that version. Is there a way I can use the flashable zip? I cant mount anything in my curent version of TWRP.
Click to expand...
Click to collapse
You can try. You must be on 10.6.1.15 or above to flash the kitkat zip though.
cmendonc2 said:
You can try. You must be on 10.6.1.15 or above to flash the kitkat zip though.
Click to expand...
Click to collapse
Is there a TF300T NVflash recovery tutorial? Like what commands I need and files. I was looking at this (http://forum.xda-developers.com/showthread.php?t=1927818) it doesn't have the right files I don't think.
I have this (https://drive.google.com/#folders/0B2Gy5tiu1Omoa2FjQzBzWWhpWjg)
but no idea how to use it..... and its been a while so I don't really remember NVFlash.
bucket81 said:
Is there a TF300T NVflash recovery tutorial? Like what commands I need and files. I was looking at this (http://forum.xda-developers.com/showthread.php?t=1927818) it doesn't have the right files I don't think.
I have this (https://drive.google.com/#folders/0B2Gy5tiu1Omoa2FjQzBzWWhpWjg)
but no idea how to use it..... and its been a while so I don't really remember NVFlash.
Click to expand...
Click to collapse
Try:
Code:
nvflash --create
This will repartition and format everything back to stock. I think you will have to flash the stock ROM after that but I'm not sure how?
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'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.