Database Info

Where to get old version of ClockworkMod Recovery?

I have a rooted (unRevoked/Virtuous) Inc. and need to downgrade my ClockworkMod Recovery version so I can install some of the Virtuous goodies that are unavailable to me because of the whole Amend/Edify stuff. I need to downgrade to a version before 3.0 and can't seem to find one that works for me.
I found this site: http://mirrorbrain.cyanogenmod.com/cm/recoveries/, and tried a couple of the ones for the Inc., but none of them seemed to work.
Can someone point me in the right direction for this? Thanks!

I got it now. Found a link on another post to Inc. Recoveries | doug piston, used that zip and it worked. It took a bit of finagling to get ROM Manager to recognize it, but I eventually got it and am able to install the "goodies".

Updating ROM with CWM just reverts to menu?

Hey,
I'm trying to install the [ROM] Team Tiamat Xoom Rom 2.2.2 - Moray [9/10/11].
I've got CWM installed (version recovery-Tiamat-R4c-100611-1150-cwm.img but also tried latest version from ROM Manager).
Each time i try to install the .zip it get's to opening package and then just exits to the CWM menu?
It's probably a common thing, but couldn't find anything from a search? Anyone got any ideas?

This has been covered many times so take the time to do a search.

Muffycheeks said:
This has been covered many times so take the time to do a search.
Click to expand...
Click to collapse
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.

kar200 said:
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
Click to expand...
Click to collapse
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.

okantomi said:
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
Click to expand...
Click to collapse
I just ralised tnat my sd card was screwed (very old 1gb i found lying around). The files on the pc were fine.
I used a different card and now typing from a custom rom! All good.
K.
Sent from my Xoom using xda premium

[Q] HELP - Just can't get into Recovery!

Hi everybody,
after endless nights and days of experimenting and crying I ask for your help.
My Aim: rooting my HTC One S C2.
So here is my story:
In my first attempt I unlocked my bootloader and tried to put a Custom Recovery on my phone. It failed. I got always stuck at the HTC screen with the red writing underneath the logo ("This build is for ...").
I then found out that I need the superboot.bat to root my phone.
So I proceeded to re-lock my phone and put a RUU on it to get back to the original Recovery.
All went well, so I unlocked my phone again via htcdev.com.
After that I tried to run the superboot.bat but again I am stuck at the HTC screen with the red writing!
I know that this screen should only appear for a few seconds and the phone should go into recovery but I am always stuck endless in this screen. To get out of it I have to soft reset my phone.
So I am not able to root it.
In a video I saw that on other phones the HTC screen with red writing has some kind of a "loading bar" on the upper right which appears after trying to access the recovery.
Well this bar doesn't even appear on my phone
Please help me I really don't know what to do further

same issue here, so subscribing to thread!

If you can get to download mode try to flash stock firmware with Odin. Search for a guide on youtube.
--------------------------------------------
Sent from my GT-S5830 running ImaGinary ICS.
Thank if it helped.It's there for a reason

Ähm isn't Odin for Samsung devices?
This is about HTC... Or does it work for both?

i recommend reading through this guide to rooting the one s. i've rooted quite a few phones using this method and it has worked flawlessly every time
http://forum.xda-developers.com/showthread.php?t=1583427

@HidaKureku - thats where i've got stuck; end of part two.
the recovery image seems to flash fine (both of them), and i've done the CWM recovery multiple times (some sites sugest that it works on the second attempt).
try to boot to recovery, and as per the OP it just sits there saying that it's for "This build is for HTC use only..." or whatever it says. no further. I've left it for 10mins in this state have have to power it off.
i have found that when i boot back to the UK retail ROM, it comes up with an error and wants to send it to HTC (i haven't yet been able to grab the error though).
has anyone sucessfully flashed recovery with the hboot 9.02.0001 image? i've seen a post on modaco with a user having the same problems as in this thread....

are you sure you're model has the S4 processor? if not, try this thread
http://forum.xda-developers.com/showthread.php?t=1785777&highlight=twrp

looks like i'm on the s3 version! twrp2 doesn't work either - same issue. (using openrecovery-twrp-2.2.2.0-ville.img)
seems the UK is one of these 'select' countries.
anyway - even an S3 compatible recovery isnt working....
I hope in not threadjacking here. @OP - if im intruding let me know and i'll create my own thread

No you are not intruding as I have exactley the same problem as you!
I'm glad that I'm not the only one I started to think I'm doing something completely wrong.
It's like the stock recovery is damaged even with the RUU version.
I just cannot get past this screen with the red warning!
My HTC One S is kind of new (about 3 weeks old). Maybe something changed with new models?

good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way

Yes!!!
That's it!!
Thank you so much
You made my day
Thread can be marked as solved!

now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly

HidaKureku said:
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
Click to expand...
Click to collapse
Thanks for the heads up, although that JB ROM in your sig says S4 in the title (thats about as far as i got )
@Schlengge - glad your sorted too i didnt even realise i was on s3 untill tonight; i thought all UK HOS's were s4's - seems not.

yeah XD i went back and looked at it and realized i got it confused with one rom i saw that was supposedly compatible with both processors (which struck me as odd) but there are a few roms out there for the s3, sadly not as many as for the s4, but you should be able to find one you're happy with. best of luck

veehexx said:
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Click to expand...
Click to collapse
well, thanks for that advice. It is kinda confusing to find a recovery for c2 version of the ONE S, cause any other recovery will not work with it. The twrp-team should definatly add the link to that on their website.

[Q] i535 - Custom Recoveries Cannot Mount Anything!

UPDATE: See post #5 for the fix. It's really simple!
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.

jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
It should work. Once latest version of casual is done try upgrading to latest version of whichever recovery you are gonna use. All the recoveries in casual are out of date and may just need to reflash recovery. Sounds like gonna use AOSP base so might as well stick with CWM as that is what you are going to end up with and what the AOSP devs support. While on TW can try upgrading it also as it the dev preferred recovery on TW. Shouldn't be the Mac if everything is actually unlocked, rooted and is flashing a recovery.

prdog1 said:
While on TW can try upgrading it also as it the dev preferred recovery on TW.
Click to expand...
Click to collapse
Can you please clarify this particular thought for me? I understood everything else.

jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
You must have a newer GS3, the newer devices (made within the past few months) have a higher revision internal card reader that breaks some recoveries. (I know because I flashed a sprint gs3 that had the same exact issue).
The fix for this is to have a recovery built with the fix in it, which is upstream in the cm-10.2 kernel, but not in any official recoveries yet.
Let me see if I can find the exact commit for you... I know invisiblek fixed it
EDIT: heres the sprint thread of info (DO NOT FLASH THE FILES THO THEY WILL MESS UP THE VZW GS3)
http://forum.xda-developers.com/showthread.php?t=2391616&page=31

I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!

jmsclbwmn said:
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
Click to expand...
Click to collapse
Oh man! Thanks for posting how you got it to work. I've been trying to figure out what to do for almost 2 days.
I would of probably still be googling away if I hadn't found this. Thanks!

[Q] Updated Root Method? Help appreciated!

I just received a "new" Photon Q thanks to a warranty swap from Motorola. When I got my 1st Photon Q last year, I used this thread to root the thing...
http://forum.xda-developers.com/showthread.php?t=1856480
That thread is ancient, though, and some of the links don't work.
I've been searching and searching... and I'm stuck. This is my 2nd day of searching, so I'm resorting to a new thread.
The phone is unlocked thanks to Motorola's unlocking tool.
I finally found & downloaded the 6.0.1.3 recovery from here:
http://clockworkmod.com/rommanager
Following the directions that are pretty uniform across the 'net, I keep getting errors. Is this file/image no longer good? Is there another way to gain root access? I'm not particularly interested in installing ROMs (not opposed to it, it's just not my main goal at this point.) I just want Root access so I can do a few minor tweaks.
Thanks to anyone who can help... this wasn't nearly this difficult the last time I did it!

Try TWRP, it auto-root's the device after flashing recovery.
Use this version until the official is updated.

arrrghhh said:
Try TWRP, it auto-root's the device after flashing recovery.
Use this version until the official is updated.
Click to expand...
Click to collapse
Thanks for the fast reply!
So, I just download that & use it as the recovery image, right? As in, I use that instead of the 6.0.1.3 file from CWM that isn't working...
Sorry... not necessarily a noob, but it's been a long time since I've fooled with any of this.

roopull said:
Thanks for the fast reply!
So, I just download that & use it as the recovery image, right? As in, I use that instead of the 6.0.1.3 file from CWM that isn't working...
Sorry... not necessarily a noob, but it's been a long time since I've fooled with any of this.
Click to expand...
Click to collapse
No worries. TWRP has directions on how to flash on their page.
http://teamw.in/project/twrp2/137
I just use the fastboot method myself. Just use that "test" image I linked earlier - or if you want official, use 2.6.3.1. I'm working to get the official updated, but it's been difficult coordinating with the TWRP team... especially since the device is now in so much limbo. I can tell you the test image works great, I'm still using it.

arrrghhh said:
No worries. TWRP has directions on how to flash on their page.
http://teamw.in/project/twrp2/137
I just use the fastboot method myself. Just use that "test" image I linked earlier - or if you want official, use 2.6.3.1. I'm working to get the official updated, but it's been difficult coordinating with the TWRP team... especially since the device is now in so much limbo. I can tell you the test image works great, I'm still using it.
Click to expand...
Click to collapse
Just sent you a tiny thank you via PayPal... I'm rooted. Let the tinkering begin. Ha!:laugh: