Database Users

CWM Problems

UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up

RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra

jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.

RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra

raffica, what version of CWM worked for you?

MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.

Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes

superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...

nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App

Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.

jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.

lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1

i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.

jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App

miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.

My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!

RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App

miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?

[Q] HELP I have PROBLEM WITH MYTOUCH 4G rooted with virtuous fusion ROM

Hi i have a MyTouch 4G rooted with Virtuous Fusion ROM. Everything was working until when I tried to install Miui Music Player on it. I did adb push but after doing it when i unplugged the phone from my computer several Force Close came up then i rebooted my phone then the MYTOUCH Tmobile logo start up screen came then the HTC logo came then my phone will shut down. I tried to start my phone again the same thing happen. I did Hboot and tried recovery from there but it didnt work. I tried Factory Reset but it failed. I go to clockwork recovery mode if i do backup and restore or factory reset nothing happens. Does it mean my phone is gone? Is there anything i can do to fix it? Please anybody help

Try going into recovery again and just reflash fusion again.

coupetastic-droid said:
Try going into recovery again and just reflash fusion again.
Click to expand...
Click to collapse
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore

pching999 said:
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore
Click to expand...
Click to collapse
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong

tjlawson09 said:
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong
Click to expand...
Click to collapse
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work

pching999 said:
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work
Click to expand...
Click to collapse
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img

TeeJay3800 said:
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom

pching999 said:
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom
Click to expand...
Click to collapse
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.

TeeJay3800 said:
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.
Click to expand...
Click to collapse
Hi im having problem with data connection 3G/4G (H) before i was getting H most of the time but now its 3G most of the time. Can you help me how to fix this. Also do you know what version of Miui Music Player is best for Mytouch 4G running on Virtuous Fusion ROM. I like the one with graphic equalizer when playing songs. Can you suggest something and how to install it
Thanks

CWM and TWRP

Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?

Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb

If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal

ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.

Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually

Mine was gone when i unrooting the device
Sent from my Nexus 4

EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?

Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4

That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium

Urgent help PLEASE!

I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.

Rizy7 said:
I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Click to expand...
Click to collapse
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.

simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?

Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.

Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.

username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
I used adb to push a file but I cant see it

thank god it worked

simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
gee2012 said:
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Click to expand...
Click to collapse
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
Thanks for your help guys

[Q] Going from Safestrap to CWM?

So a while back I went through the process to root my phone and went with safestrap. Now it appears the new roms aren't compatible with safestrap (is it because of 4.3 gapps?).
How would I go about switching over to CWM? Is there anything fancy? Is there a guide? Any help appreciated.
Thank You.

Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium

Leraeniesh said:
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yes unlocked. I will look it up. Thanks.

I believe you can also use backups made in Safestrap in TWRP (/data/ only)
Sent from my XT907 using xda premium

You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.

So I am getting the "cannot load cwm.img" on the command prompt.
cwm.img is in the same folder as fastboot and adb.
not sure what is up. Currently searching for solution....
EDIT: Typed full path. Seems to have worked....

RikRong said:
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
Click to expand...
Click to collapse
Booted back into safestrap. I'm assuming this is why?

jagsfan82 said:
Booted back into safestrap. I'm assuming this is why?
Click to expand...
Click to collapse
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.

RikRong said:
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
Click to expand...
Click to collapse
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now

jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?

jagsfan82 said:
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
Click to expand...
Click to collapse
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.

jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium

Leraeniesh said:
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw

RikRong said:
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
Click to expand...
Click to collapse
My first thought is I need to strip down the system.. maybe i didn't wipe something properly or what have you.

jagsfan82 said:
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
Click to expand...
Click to collapse
Yeah unfortunately there's no command to boot recovery from fastboot.
You can try running "fastboot reboot" while holding the volume buttons right after flashing cwm. That should do the trick. It should boot to the boot selection menu, then you can choose to boot to recovery.
Also, thought you killed yourself when I read your other post...
fastboot boot cwm.img is one argument away from a very, very bad day... If you put "flash" before boot, you'd be in trouble... Lol
Maybe I should write up a root app that will rename install-recovery.sh... That's not a bad idea...
Sent from my XT907 using Tapatalk

I always just power down the phone after flashing recovery and then manually reboot into recovery.

And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk

sloosecannon said:
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Haha, nice.

RikRong said:
Haha, nice.
Click to expand...
Click to collapse
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk

sloosecannon said:
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Installed on phone. Says found but disabled. Tried flashing cwm.img and rebooting into recovery. Still goes straight to OS...
Enable install-recovery doesn't work
this all seems very straightforward of a process that should be working...
Do I need to try wiping everything down as bare as possible?
Is this the process that works for others? Take safestrapped, rooted, bootloader unlock device on an old pre-bootloader-unlocked rom. Uninstall safestrap. Flash cwm.img using fastboot comand. Boot into recovery. Then you should be in CWM?