Develop Bugs

CDMA Desire: What version of Clockworkmod recovery

Hi all,
I'm sort of new to this. I've been using clockworkmod recover for a while now. Mostly to back up and restore. I want to try to load the stable CM7 rom or maybe some other rom that supports A2sd+ but I saw that at least CM7 recommends a newer version of ClockworkMod Recovery.
Right now I have 2.5.0.9. It's also the one that shows up in Rom Manager.
But I've seen here and other forums that people are now unto 3.0.0.5 and even beyond (I saw 3.0.2.4 on the CM forum)
So my question is what is the latest version of ClorkworkMod for the CDMA desire and how do I get it?
I saw an article on addictivetips.com that suggested renaming the new version to the name of the old one (2.5.0.9) and placing in in the Rom Manager folder on the SD and then flashing from Rom Manager thus fulling it into flashing a newer version.
Some, forums have guides on how to do that using adb and yet others have it as a zip file that can be flashed from the hboot.
Whats the best and I guest simplest way to get the new version.

Did you actually run into trouble with your current CWM trying to setup CM7?
The wiki states no problem using the version you currently have - 2.5.0.9.
If you do want to upgrade, you should follow this post.

foalsrock said:
If you do want to upgrade, you should follow this post.
Click to expand...
Click to collapse
Yep. thats exactly the forum I was referring to when I mentioned 3.0.2.4
Although I was not able to flash it using the PB99IMG.zip. Probably should ask there about that.
I did flash CM7 but,
here is what's weird: I tried the method where you fool the rom manager into flashing a newer recover outlined here.
Got the 3.0.2.4, but then when I went back into the Rom manager and hit reboot into recovery, it boots me into 2.5.0.9.
If I just press the power button, select reboot, and reboot into recovery I get 3.0.2.4. It's like I have two recovery images loaded.
I wiped the phone restored my nandroid backup of the stock rom I get 2.5.09.
Wipe again, as always everything data, cache, and dalvik. Load CM7 again. And the same thing two recoveries depending on how I reboot into it.

P.S.
1. Happy Passover, חג שמח.
2. forgot to say: if I power down and boot into Hboot with vol down + power and then go into recovery I get into 3.0.2.4

Do you happen to have your phone S-OFF?
If so, a simple solution might be to flash the 3.0.2.4 recovery .img file using "fastboot flash recovery xxx.img" @ hboot.
But you shouldn't S-OFF just for this as I'm not sure it'll actually resolve what you're experiencing.
It's a pretty odd situation and I think I better not give you advice which could potentially worsen it.
I'd seek help in the thread linked in the CM forums or hope that someone else might notice this post.
חג שמח! =)

foalsrock said:
Do you happen to have your phone S-OFF?
If so, a simple solution might be to flash the 3.0.2.4 recovery .img file using "fastboot flash recovery xxx.img" @ hboot.
Click to expand...
Click to collapse
I do have S-OFF, how would I flash this in Hboot?

Zhenya13 said:
I do have S-OFF, how would I flash this in Hboot?
Click to expand...
Click to collapse
This is assuming you have the Android SDK all set up on your computer (if not, read through the wiki).
Boot into the bootloader, type "fastboot devices". If you see your device listed - continue flashing by typing "fastboot flash recovery <filename>.img"

foalsrock said:
This is assuming you have the Android SDK all set up on your computer (if not, read through the wiki).
Boot into the bootloader, type "fastboot devices". If you see your device listed - continue flashing by typing "fastboot flash recovery <filename>.img"
Click to expand...
Click to collapse
Where should I put the img file? just to the root of the SD card?
תודה רבה

You should have the recovery .img file on your pc when flashing via fastboot

[Q] Problems flashing CWM after AlphaRevX

Hi,
Recently I turned my Wildfire S-Off with AlphaRevX. After Rooting with SuperOneClick I tried to install CWM 2.5.0.7 with Rom-Manager.
Rom-Manager itself told me everything went right. I tried to boot to Recovery, BUT:
Just got a Red Punctuation mark and after pressing Vol Up it said "Command not found in /Recovery/ "
Is this a known problem?
I think I can try to flash CWM via fastboot, but i'm not sure if I should do that.
The big question is: Are there any known problems with CWM 2.5.0.7 and HBOOT 1.01.00002 (don't know, but I think thats my version) after flashing via Fastboot?
Will it be possible to use Rom-Manager to install Roms?
Thx
BBsan

The same here.

How are you trying to access Recovery Mode? If you use the conventional Vol Down + Power, it will not work, and, as such, can only be accessed when you select Reboot into Recovery from within ROM Manager.
Anyway, Getting CWM from ROM Manager is more like a "temporary / secondary" way to get it. It is recommended to use Fastboot to write a Recovery directly to the NAND. Using it will not have any issues (Did it personally).
Lastly, your HBoot will be 6.01, after using AlphaRev X. There will be no issues using v2.5.0.7. The problem is, you will not be able to install Gingerbread ROMs, and, if you install v3.x.x.x, you will not be able to install Sense Froyo ROMs and Radios. Hence, the recommended technique is to Flash a Clockworkmod 3.x via Fastboot (ie in your NAND), and, Flash Clockworkmod again, but via ROM Manager to get 2.x. So, you have both,

Okay thx alot, I'll try tonight.
What Version does unrevoked flash by default?
I've got a second wildfire with old HBOOT and was able to flash CM7 without any problems via Rom-Manager.

Interesting.. Though I personally keep ROM Managers CWM as a Secondary one, more so, because one needs both 2.x and 3.x these days.
ROM Manager flashes 2.5.0.7 by default, although you can change it if you need to.

Hmm okay So I'll try and post if I succeeded
EDIT:
OK everything now worked fine THX for help!
EDIT2:
I was able to install CM 7 with 2.5.0.7!

[Q] Problem with CWM 5.0.2.0 stable installation.

Actually, I got no place to post my question. So, I thought of starting a new thread.
I have installed CyanogenMod 7 on my HTC buzz by downgrading its stock rom as it suffered a OTA update before. I guess you guys r well aware about the process.
During the downgrade, my phone got Revolutionary CWM 4.x.x.x by default. In fact, I have flashed CM7 using revolutionary.
Now, CM7 comes with ROM Manager built-in and I tried to install CWM 5.0.2.0 recovery right form the GUI. The update.zip was downloaded. I could update it manually form my recovery options.
But, it was not stable. Each time I boot into recovery, Revolutionary CWM shows up, instead of CWM 5.0.2.0. To use it again, I have update the package each and every time.
Is is quite normal? Or, I am missing something? Plz help with advice.:crying:

I did this via Rom manager. Not through Recovery.
YNWA

ChandanRoy said:
Actually, I got no place to post my question. So, I thought of starting a new thread.
I have installed CyanogenMod 7 on my HTC buzz by downgrading its stock rom as it suffered a OTA update before. I guess you guys r well aware about the process.
During the downgrade, my phone got Revolutionary CWM 4.x.x.x by default. In fact, I have flashed CM7 using revolutionary.
Now, CM7 comes with ROM Manager built-in and I tried to install CWM 5.0.2.0 recovery right form the GUI. The update.zip was downloaded. I could update it manually form my recovery options.
But, it was not stable. Each time I boot into recovery, Revolutionary CWM shows up, instead of CWM 5.0.2.0. To use it again, I have update the package each and every time.
Is is quite normal? Or, I am missing something? Plz help with advice.:crying:
Click to expand...
Click to collapse
Yes this is normal for ROM manager as using ROM manager is only giving you a temp recovery over your stock ( in your case revolutionary cwm ) to get the cwm 5.0.2.0 you want you need to get either a PC49IMG.zip version of the cwm and use the boot loader method, use ADB/Fast boot method or use the terminal emulator method.
Tutorials are all over the wildfire thread and so are the necessary files etc.
Sent from my Nexus 4

That what u have to flash is temporary.
For permanent recovery, copy the recovery onto your pc.
Turn on the willy in hboot mode, goto fastboot connect usb
Type fastboot flash recovery name.zip
here name is the name of recovery zip AS IT IS.

[Q] can't boot into CM , can't update bootloader

I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance

You're in the wrong forum, this is the HTC One XL/at&t One X forum. I'll ask for this to be moved to the correct device forum for you.
Sent from my Evita

your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904

nogotaclue said:
your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
omg, i feel so stupid that i did this.. thank you very much! i now flashed TWRP and it worked, I'm waiting till the battery charges and i'll install CM again, but looks like it gonna work this time.
thanks again, that link was really helpful.:good:

Ok, don't forget to use the right cm, not the version you used previously
Sent from my HTC One X using XDA Premium 4 mobile app

xulube said:
I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance
Click to expand...
Click to collapse
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.

okhughes said:
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.
Click to expand...
Click to collapse
he doesn't need to start from scratch, he knows how to do it. the problem was he was in the wrong forum. did you even read the thread?

Restoring from Android stock recovery

Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?

Strangiato said:
Yo. (sorry if this thread is already on the board, I couldn't see it after a quick check)
So, I've hit upon quite a snag while trying to update my custom ROM (Android Revolution HD). I made a rookie error of installing this without installing the new firmware.zip first , but I was able to flash the correct firmware.zip (my phone if S-OFF, CID = 02__001). However, after this, my phone went into Android stock recovery <3e> after being in a bootloop, even though I'd already had TWRP installed. Also, ADB on my computer no longer recognises my phone, so I can't flash an img on it; the only option I can now see is to find a zip which I can install from the stock recovery via my SD card, but I can't seem to find one which the stock recovery will let me install.
Anyone have any ideas?
Click to expand...
Click to collapse
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2

nkk71 said:
the stock recovery can be easily replaced by going to bootloader/FASTBOOT USB, and
Code:
fastboot flash recovery <name of twrp>.img
so that's easy, but it sounds to me like you flashed a firmware pulled from an OTA, which could have a potential problem:
If you didnt flash "OTA firmwares" incrementally, then you may have missed updates.... ie firmwares pulled from OTAs are incremental, because they expect all previous updates to already there, flashing the "latest" does not mean you actually have all the firmware updates
I recommend using "Combined" "NoWipe" firmwares, such as the ones found here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
(^^ those also happen to include TWRP, but you can still reflash a newer version using above fastboot command)
this is what a firmware flash would look like: http://forum.xda-developers.com/showpost.php?p=60259359&postcount=2
Click to expand...
Click to collapse
Thanks for this info and links to the relevant threads, btw.
My biggest problem was that my computer wouldn't find my phone, so I couldn't use fastboot, but now for some reason, using the HTC One Toolkit that was in the post you linked me to, my computer can now see it. I've hit another snag, though, whereby I'm just after flashing the newest version of TWRP, but now for some reason, it didn't seem to install correctly, as the phone has booted into recovery mode, according to my computer, but is stuck on the opening screen with the pink "Entering Recovery..." message on the top. Also, my computer can't seem to touch it now, as even though the toolkit finds it and sees it in recovery mode, any time I try to reboot it or do any other command, the program crashes. I've no idea what's happened, unfortunately :/

Update: after fiddling around with the HTC Toolkit, I was eventually able to boot my phone into bootloader which, from there, I could install what I needed, so my problem's been resolved. Thanks again for your help, as those links proved very useful.

Glad everything worked out.
By the way:
Strangiato said:
but is stuck on the opening screen with the pink "Entering Recovery..." message on the top.
Click to expand...
Click to collapse
^^ is usually caused by using a new version of TWRP with old firmware