Database Users

Clockworkmod Recovery 3.2.0.0

Saw this posted in the Nexus S Development forum and wasn't sure if people are checking both so I thought this post was appropriate.
CWM has been update to v3.2.0.0
I just flashed it and all seems to be working OK. Head over to the link below and just make sure you grab the NS4G one.
http://forum.xda-developers.com/showthread.php?t=988686

Its layout is different than the normal Clockwork, but I find it more useful.

Thanks for bringing this to the frontline
Sent from my Nexus S 4G using XDA Premium App

No problem, figured it would be more noticed here from the 4G users. I did notice the layout difference as well. I like that its less cluttered and more organized... just my .02 anyway

Is there a zip that I can flash thru recovery? Or what's the easiest way to flash this. When I had an evo and amon ra I could upgrade the recovery thru a zip, is that possible?
Sent from my Nexus S 4G using XDA Premium App

use fastboot like you did when you rooted.

NYYFan325 said:
Saw this posted in the Nexus S Development forum and wasn't sure if people are checking both so I thought this post was appropriate.
CWM has been update to v3.2.0.0
I just flashed it and all seems to be working OK. Head over to the link below and just make sure you grab the NS4G one.
http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
This link takes you to the mod'd version. Do you have the link to the official version? If you are running this mod'd version, Rom Manager will not accept it as official and will want to install the official version. Rom Manager does not show 3.2.0.0 in its interface as of yet.
EDIT: Here is the link to the official Koush site. For our phone, 3.1.0.1 is the only release.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html

I've never used ROM manager so I really can't comment on it "seeing" the recovery. Pretty sure the only thing modified is the colors, nothing more.

NYYFan325 said:
I've never used ROM manager so I really can't comment on it "seeing" the recovery. Pretty sure the only thing modified is the colors, nothing more.
Click to expand...
Click to collapse
Colors and layout are different. Rom Manager is developed by Koush and works together with the recovery. So, if you do use rom manager, it does not recognise the mod'd version as official and you will not be able to do things like download roms and extras through Rom manager. .
No Biggie, just thought people should know before they download this and find out there rom manager does not function fully until they install the official clockwork recovery again.

ROM Manager seems to be working just fine for me

mbh87 said:
ROM Manager seems to be working just fine for me
Click to expand...
Click to collapse
So, with this mod version installed, Rom Manager (by Clockwork) is not telling you that you have to install Clockwork Recovery to be able to perform that function?
Interesting, did that to me on the last version of the mod (3.1.0.1) Maybe they changed the mod to function with the Clockwork Rom Manager.
I will install and see.
EDIT: OK, seems to work fine with Rom Manager. The last Mod did not. I had to reinstall the official clockwork Recovery. Well That Just Shows Me, Hu. Sorry for the alarm. (the sky is falling, the sky is falling)

anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature

shabbypenguin said:
anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature
Click to expand...
Click to collapse
All 3.X recoveries are edify. Koush and most other devs have completely moved away from amend scripts for updates/flashable zips. amend was around since cupcake if I recall correctly.
Sent from my SCH-I500 using XDA Premium App

shabbypenguin said:
anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature
Click to expand...
Click to collapse
Installed one of Net's kernels just to be sure before posting this... no problems at all

sunder74 said:
All 3.X recoveries are edify. Koush and most other devs have completely moved away from amend scripts for updates/flashable zips. amend was around since cupcake if I recall correctly.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
perhaps i wasnt making myself clear enough.
assert(getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g" || getprop("ro.product.board") == "crespo4g");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
Click to expand...
Click to collapse
thats from the updater script that cm7 uses, if when it does getprop it finds anything but the crespo4g, it will fail. flashing the crespo recovery could have undesired effects.
like i stated tho, only if the dev chose to use that feature

Is this strictly a crespo recovery? I was under the impression from the post that there were 2 different recoveries uploaded, one for the ns and one for the 4g. If you find out that this doesnt work I can edit the post title to state not to flash...

my apologies didnt know there was a 4g version, just thought everyone was going willy nilly with the nexus s version

shabbypenguin said:
my apologies didnt know there was a 4g version, just thought everyone was going willy nilly with the nexus s version
Click to expand...
Click to collapse
Silly penguin, gotta click links first!

So are the different colors for just style or do they signify something?
sent from my sexy nexy 4 gizzle!

chewbz said:
So are the different colors for just style or do they signify something?
sent from my sexy nexy 4 gizzle!
Click to expand...
Click to collapse
Just personal preference... no difference otherwise

Acer Recovery Intaller 2.99beta1 (A100/A101/A200/A500/A501)

This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: f0a03b50e08faa09e8d49e7224b0cd0f
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
EDIT: A number of users have been confused by the red outlined banner at the bottom. This banner replaced the links to my other apps a few versions back (2.7 something). The presence of that banner does not mean you've lost your premium license. The next beta will probably display a thank you banner instead of the one shown now if the premium features have already been purchased.
EDIT: V2.99beta3 is available at the link above. Much of the underlying code was changed and needed much testing. I believe it is pretty stable now. It supports TWRP 2.1.1!

For me (future changelog)

Euclid's Brother said:
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: eb8302db485aa47df6f342698db6b820
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
Click to expand...
Click to collapse
Looks Awesome I purchased this as as soon as walked out of bestbuy 8month ago this app has come a long way I just want to thank you for all you work its really a great app!
Sent from my Inspire 4G using Tapatalk

I will make custom rom for A100 , give me some time.
Just been very busy.
EDIT
Full A100 custom rom is in A100 section

Euclid's Brother said:
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: eb8302db485aa47df6f342698db6b820
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
Click to expand...
Click to collapse
Can I install it on top of the market version or Should I uninstall that first?

I think you probably can, but have not tried it. Give it a shot and let us know. Worst case is that it will say you have to uninstall the previous version.
Sent from my SPH-D710 using Tapatalk

anikiup said:
Can I install it on top of the market version
Click to expand...
Click to collapse
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?

elborak said:
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?
Click to expand...
Click to collapse
Unfortunately, it does not. I will add recognition to my app for TWRP, but it will not work with the premium features unless the dev add support for extendedcommand.

elborak said:
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?
Click to expand...
Click to collapse
Extended command actions are locked down to clockwork mod based recoveries. There is a key need to use that function. But there are other apps that work with twrp that basically do the extended command goodies.
Sent from my Iconia A500 using Tapatalk 2

^ In what way are they "locked down" to CWM?

@pimpmaneaton
In which version of CWM did they lock it down? It works fine in thor's 1.7, and in hbwelches version that was built for the A200 (can't remember which version he based it on).
It also works on fine on my Sprint Epic Touch 4G using a custom built CWM (not from ROM Manager). I created a test script myself and it ran fine. That was based on 5.0.2.4 I believe. I have 5.0.2.8 installed now, i'll try it again with that one and see.
extendedcommand support really isn't much more than looking for the file and executing it like any edify script. package_extract type commands shouldn't be allowed, since it's not part of a package, but things like ui_print, format, run_program, install_zip, set_permission, symlink, etc.. shouldn't be too hard to do.
I've been trying to find more info on how Open Recovery Script works. To see if i can use that.

installed fine on top of v2.74 -paid version - couple root beers on their way 0158-3554-2226-2151-1639

Euclid's Brother said:
I've been trying to find more info on how Open Recovery Script works. To see if i can use that.
Click to expand...
Click to collapse
If you find some interesting documentation/websites, would you mind sharing them here?
Although i would prefer normal extendedcommand support in twrp because seen the comments on review.cyanogenmod there is no change open recovery script will get merger to cwm. Besides that, if I understood it correctly, extendedcommand is not limited at all to rommanager. Kouch just changed his licence statement in the code to stipulate that.
Taptalked u see

If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.

Euclid's Brother said:
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
Click to expand...
Click to collapse
I just tried it, works fine although i had to read the op here again to realize i needed to put the recovery image in the correct directory. A small embedded browser would be nice. Or at least a help function/about under the overflow menu.
I used it to flash thor 1.7 cwm over twrp, without auto reboot to recovery. I have used the free market function only once before so i can't really tell you the differences/improvements.
Acer A500 btw.
Taptalked u see

Euclid's Brother said:
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
Click to expand...
Click to collapse
I'm use bêta 2.99 . I've tested 3 time full backup . 2 on 3 are working without problème. 1 time,reboot to recovery and reboot système without backup.
I've thor 1.7 cwm with flexreaper R11.
Your app are perfect.
Thanks
Sent from my A500 using Tapatalk 2

just installed and upgraded from thor 1.3.4 to 1.7...updating and flashed fine, rebooted into recovery and everything went perfect...thanks so much!

Zatta said:
I just tried it, works fine although i had to read the op here again to realize i needed to put the recovery image in the correct directory. A small embedded browser would be nice. Or at least a help function/about under the overflow menu.
I used it to flash thor 1.7 cwm over twrp, without auto reboot to recovery. I have used the free market function only once before so i can't really tell you the differences/improvements.
Acer A500 btw.
Taptalked u see
Click to expand...
Click to collapse
I forgot to this mention in the OP. To install a recovery that's not automatically downloaded by the app, you place it in the root of your external sdcard and name it "recovery.img" (just like the old version). HOWEVER, if you don't have an external sdcard, then it looks in /sdcard/.AcerRecoveryInstaller instead.
I'm going to work on this more for beta2 and have it able to use multiple custom images. So you can have one or more additional recovery images instead of just "recovery.img"

micky387 said:
I'm use bêta 2.99 . I've tested 3 time full backup . 2 on 3 are working without problème. 1 time,reboot to recovery and reboot système without backup.
I've thor 1.7 cwm with flexreaper R11.
Your app are perfect.
Thanks
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I guess it's possible, for whatever reason, the sdcard didn't mount that one time. If that happens again, please PM me the file located at /cache/recovery/last_log after it boots back into android.
Thanks!

ok.
Your app is fantastic so i've purchas the premium version .
Thanks
Best regards
Envoyé depuis mon A500 avec Tapatalk

CWM touch edition for i9001

As I use "CWM touch" since some time and have no problems,
I like to offer the single post of czobor (http://forum.xda-developers.com/showpost.php?p=29258457&postcount=1573) as new thread.
The download link was: http://d-h.st/users/czobor
If there is already a new version of CWM as touch edition available it would be nice to post it here.
Experiences are always helpful to post.
The touch edition works for backups and restores of GB and ICS.

I think it's a good idea but you should've told czobor to open it. You know, for problems in this recovery instead of reporting it in CM9 thread
Sent from my S+ using XDA premium

OmarPlus said:
I think it's a good idea but you should've told czobor to open it. You know, for problems in this recovery instead of reporting it in CM9 thread
Sent from my S+ using XDA premium
Click to expand...
Click to collapse
Have informed czobor by pm before opening.
If there are any problems, please write it here for CWM touch.
I think it is better to read it at this point than distributed in different threads and places.
I only know that some people do not like the new style of backup in the file system of CWM6.
With the touch edition itself it is more secure to handle menus than without, because of "double click events"
which can not happen so often here.

Well my problem is :
It reads internal sd as external and vice versa. So if you backup to external it'll backup to internal and so on.. Also with installing zips.
Sent from my S+ using XDA premium

CWM 6.0.1.2
The new version or ClockworkMod is available for download, the download link is the same (http://d-h.st/users/czobor).
The non touch version is arco's one, but the touch one is mine. They're CWM flashable.
Enjoy!
Edit: Thread moved: http://forum.xda-developers.com/showthread.php?t=1843825

could someone provide an alternate download for cwm6012 touch? because i'm being unable to download it... it stops at 80 - 90 %...

czobor said:
CWM 6.0.1.2
The new version or ClockworkMod is available for download, the download link is the same (http://d-h.st/users/czobor).
The non touch version is arco's one, but the touch one is mine. They're CWM flashable.
Enjoy!
Click to expand...
Click to collapse
thanks czobor.
Just installed and works fine.

This is not development - it is discussion/Q&A. Moving this to the General section

Version 6.0.1.5 works well, or problems such as the 1.4?

[RECOVERY] ClockworkMod 6.0.1.9 [crespo]

Hey folks,
I am sharing the latest CWM recovery images; CWM 6.0.1.9, while the one available in ROM Manager is 6.0.1.0
To be straight, I used Koush's Recovery Builder to build these latest recovery images in both, touch & non-touch variants. And so I do not take any credit, all of it to Koush. Also, I didn't publish a thread for this in development section since I didn't perform any development on this. :angel:
Downloads
ClockworkMod 6.0.1.9 Touch Recovery
ClockworkMod 6.0.1.9 Non-Touch Recovery
Click to expand...
Click to collapse
How to build on your own?
Visit the Recovery Builder
Click on the "Existing Devices" tab.
Now under the Existing Devices dropdown, select "crespo".
Tick "Touch Recovery" option if you desire for the touch variant, otherwise do not touch it.
Now click on the blue colored "Build" tab.
The page will then prompt you with a reference build ID, take note of it.
Now continue to build server.
Look for the corresponding build ID.
Once its done, click on it.
You can now download your "recovery.img" build.
How to flash?
For those who know already know how to flash recovery via fastboot, type this for flashing touch recovery:
Code:
fastboot flash recovery cwm-crespo-6.0.1.9-touch.img
and for non-touch, type:
Code:
fastboot flash recovery cwm-crespo-6.0.1.9-touch.img
If you are new to flashing via fastboot then, you shall visit my guide for simplified and step-to-step instructions.

Flashable zip please?

USB mount working?
I built it myself, but USB Mount didn't worked.

Can you please provide a changelog?

I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium

903tex said:
I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
You dont need to wipe battery stats, thats myth bull****.
Sent from SpeedMachine i9023

sidnoit22 said:
Flashable zip please?
Click to expand...
Click to collapse
I doubt its stability yet,
Articudos said:
USB mount working?
I built it myself, but USB Mount didn't worked.
Click to expand...
Click to collapse
Yes, its not functional.
903tex said:
I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I don't think that they took it out since its present in N4. Must be a building error.
To sum up, I will ask a mod to close this thread.

alen1901 said:
You dont need to wipe battery stats, thats myth bull****.
Sent from SpeedMachine i9023
Click to expand...
Click to collapse
I agree to that

DJBhardwaj said:
I agree to that
Click to expand...
Click to collapse
Well guess it times for a new battery....
Sent from my Nexus S 4G using xda premium

Is CWM Recovery v6.0.3.3 available for N4?

I can see this version has been made available to some other devices, like the N7, but I can't find any version for the N4, anyone know if it's available yet?

You can get it here from the CWM builder:
http://jenkins.cyanogenmod.com/job/recovery/32462/artifact/archive/recovery.img

Ok, I'd like to know how Jenkins works (appreciated you sent me a link though). How do I find the recovery for a specific device, all I see is what appears to be md5 sums

http://builder.clockworkmod.com/
Click on existing device, choose mako and touch recovery and it builds CWM for the mako uing the latest code. If there is already one built it gives the link (like above)

EddyOS said:
http://builder.clockworkmod.com/
Click on existing device, choose mako and touch recovery and it builds CWM for the mako uing the latest code. If there is already one built it gives the link (like above)
Click to expand...
Click to collapse
Much appreciated! :good: