Root [Recovery] CWM-Green w/BacksideUpdater Auto-Install

[JerryScript]

Updated 05022012!
​

Introducing CWM Green Recovery

Download CWM-Green-recovery-05022012.img here
md5sum e3963b7709fe23c2ae5667e318e50d96

A ClockworkMod 5.0.2.8 based recovery for the Optimus V
With extended support for automatic installation of ROM packages
Via the BacksideUpdater

See Details of CWM-Green and the BacksideUpdater Auto-Install Here

Do Not Flash A Radio With This Recovery!​

The radio updates are known to be dangerous and can/will brick your phone!​

BacksideUpdater Auto-Install
Note- This video is of V2.2, will make one of V3.3 soon

Why another recovery?
Current recoveries for the Optimus V have some built in support for automatic installation of OTA and update packages. This has never been utilized by ROM developers for the OV, and I hope to change that by making the process a little less scary for everyone. Together with the BacksideUpdater, you can now quickly and effortlessly install ROM updates!

What's different?
--For manual usage by rebooting into recovery, I've added the ability to wipe cache and dalvik cache together.
(will be adding option to format boot+system+data as well)
--For automatic installation, I've added the ability to wipe cache and dalvik cache together, and enabled
the text-gui during the auto-install process so you can see what is happening.
--Based off IHO recovery source, with fix for UMS (Universal Mass Storage), so you can mount your sdcard in recovery
--Home key is the select now, no more messing with that two-stage camera key (always worried it would break)

--And of course I made it Green

Installation Instructions:
1-- Download CWM-Green-recovery-05022012.img to your sdcard
2-- Open Terminal emulator (available in the Play Store)
3-- Type the following two lines:

su
flash_image recovery /sdcard/CWM-Green-Recovery-05022012.img

Note- change /sdcard to where you put the zip file, ex: /sdcard/download/CWM-Green-Recovery-05022012.zip

Note to ROM devs - The link to details has the info for including the BacksideUpdater in your ROM, to make the upgrade process simple and worry free for your users, regardless of their technical abilities!

Thanks to Koush for the original CWM code base, Blarf for help in fixing the UMS bug in IHO, nijel for hitting me over the head with a brick, the CM team, the AOSP team, BobZhome, mrg666, tdm, LeslieAnn, Whyzor, gannon, tvall, and a whole lot more!

​

 

[flowingsphere]

Great work Jerry, tested and works well on my newer screen. Just an FYI that Flash GUI expects the filename to contain recovery in all lower case letters and will not work otherwise. Have to either rename the file or use flash_image from the terminal.

 

[CmplxAdSys]

When I downloaded, I got a 4 MB file with a .txt extention: Download CWM-Green-Recovery-04172012.txt

Is this correct?

(FYI: I always have to click the "try again" button on Mediafire when I attempt to download on my phone: the first click never initiates a download)

 

[brotherswing]

Runs great on my first gen V (but you already knew that ) but I have three questions.
1) I noticed you gave it a BACKside style version number, does that mean we should look forward to regular updates?
2) If so, will the BACKside updater handle that as well? That would be a very nice feature.
3) I'm starting to itch, is there anything that I can do about that green? (Like grab the source and compile my own or something like that?)

::Edit:: What's the MD5 for this?

 

[brotherswing]

When I downloaded, I got a 4 MB file with a .txt extention: Download CWM-Green-Recovery-04172012.txt

Is this correct?

(FYI: I always have to click the "try again" button on Mediafire when I attempt to download on my phone: the first click never initiates a download)

rename it to .img, then it should flash just fine.

 

[CmplxAdSys]

rename it to .img, then it should flash just fine.

That worked. Thanks!

 

[brotherswing]

You're welcome.

 

[JerryScript]

Runs great on my first gen V (but you already knew that ) but I have three questions.
1) I noticed you gave it a BACKside style version number, does that mean we should look forward to regular updates?
2) If so, will the BACKside updater handle that as well? That would be a very nice feature.
3) I'm starting to itch, is there anything that I can do about that green? (Like grab the source and compile my own or something like that?)

::Edit:: What's the MD5 for this?

1) Yes, there will be some updates, but not as many as BACKside gets
2) The newest version of BacksideUpdater shows the lastest CWM-Green-Recovery at the bottom of the Show All Versions list (press menu-key)
3) The source is available at my git, /bootable/recovery, check the history for the easiest way to find where I changed the colors. Here's the steps to build (requires a full IHO build environment):

cd andriod/WORKING_DIRECTORY
. build/envsetup.sh
lunch (choose vm670-eng)
make recoveryimage

::md5sum:: f75b2f33e3fa376f59af4d3602f41bf0

 

[JerryScript]

When I downloaded, I got a 4 MB file with a .txt extention: Download CWM-Green-Recovery-04172012.txt

Is this correct?

(FYI: I always have to click the "try again" button on Mediafire when I attempt to download on my phone: the first click never initiates a download)

Sometimes phone browsers or the websites they are downloading from change the file extension to txt to prevent the browser from opening a .img file as an image.

I have added a check for that situation in the BacksideUpdater V3.2, and it will automatically convert the file extension from .txt to .img when you download it. So long as you use the BacksideUpdater in the future, this shouldn't be an issue anylonger.

 

[brotherswing]

You blow my mind sometimes, Jerry! Awesome job as always!

 

[sammyz]

Link is Temporarily unavailable, was gonna try with my optimus m, I'm sure I'll get fastboot if I flash it, but I'm gonna try anyways....there is GNM recovery that is universal with a lot of the optimus phones....so who knows if it does or not

 

[sammyz]

Your recovery actually boots on the Optimus M!! but the buttons aren't mapped correctly, all I can do is press Volume Down to go up....Menu button goes back, Home button goes back...Back button does nothing, search button does nothing, Camera button does nothing, Volume Up does nothing, Power button does what it's supposed to (change to the ROM Manager logo and hide menu).

 

[quacles]

If I already flashed the radio update would I be good to install this?

 

[JerryScript]

If I already flashed the radio update would I be good to install this?

Yes, using this after you have aleady flashed the radio is fine, just don't use it to flash the radio itself.

 

[m0bstr]

thanks for this awesome recovery!!!!!!

 

[quacles]

Brilliant recovery, amazing work as always JerryScript.

 

[JerryScript]

Your recovery actually boots on the Optimus M!! but the buttons aren't mapped correctly, all I can do is press Volume Down to go up....Menu button goes back, Home button goes back...Back button does nothing, search button does nothing, Camera button does nothing, Volume Up does nothing, Power button does what it's supposed to (change to the ROM Manager logo and hide menu).

So you are using BobZhome's kernel for the M? If so, I should be able to build a version of CWM-Green with proper button mapping for you. I'll need to know the kernel you are using so I can ask Bob for the correct zImage, and I'll need to know the partition sizes on your phone. Please open terminal and type in the following command and post the output here (should be able to do it with ADB if that's easier to C&P):

su
cat /proc/mtd

 

[sammyz]

So you are using BobZhome's kernel for the M? If so, I should be able to build a version of CWM-Green with proper button mapping for you. I'll need to know the kernel you are using so I can ask Bob for the correct zImage, and I'll need to know the partition sizes on your phone. Please open terminal and type in the following command and post the output here (should be able to do it with ADB if that's easier to C&P):

su
cat /proc/mtd

Yes I use BobZhome's kernel for all my ported ROMs.
Here:

$ export PATH=/data/local/bin:$PATH
$ su#su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04340000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 0bd00000 00020000 "system"
mtd6: 0c900000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
#

 

[JerryScript]

Yes I use BobZhome's kernel for all my ported ROMs.
Here:

$ export PATH=/data/local/bin:$PATH
$ su#su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04340000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 0bd00000 00020000 "system"
mtd6: 0c900000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
#

Looks like you have everything needed to make CWM-Green-Recovery for the M.

PM me so we can set up a time mon-tues to get on chat and work this out.

Till then, if you know anyone with a rooted stock OM, have them run the same command above, so we can be sure the original partitions match.

 

[sammyz]

Looks like you have everything needed to make CWM-Green-Recovery for the M.

PM me so we can set up a time mon-tues to get on chat and work this out.

Till then, if you know anyone with a rooted stock OM, have them run the same command above, so we can be sure the original partitions match.

I'm actually on stock right now, I was testing a new root method that someone else made, it failed, but hey you don't need to be rooted to run that command

$ export PATH=/data/local/bin:$PATH
$ cat proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04340000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 0bd00000 00020000 "system"
mtd6: 0c900000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
$

 

[AndyOpie150]

I have used this recovery to make a backup, flash the backup, flash an update, flash a backup that was made from another recovery, flash a ROM that was not signed with signature verification turned off, and used this recovery with the new BACKside updater v3.2 with auto installer to install a ROM (flashed back to an older ROM). Everything worked flawlessly.
Will work on the partitioning option,mount SD card option, and anything else I forgot to checkout next.

 

[brotherswing]

I've found a problem with the recovery. I was trying to flash tdm's AOKP alpha 8, and got the "assert failed getprop ro.product.device" error. I tried twice, toggling assert both times, same error. Tried CM9 alpha 8 and got the same result. Both had matching md5's so the downloads were okay. Flashed bobz back on it, the AOKP flashed fine. Just thought you'd want to know.

 

[brotherswing]

After playing with AOKP for about an hour, I went to restore my nandroid but it failed with an error about system img not found. I was able to restore my nandroid of 0401, use the Backside updater to flash your recovery again, then I was able to restore my nandroid of 0417, and all is good. Again, just felt this information would be useful to you.

 

[sammyz]

I've found a problem with the recovery. I was trying to flash tdm's AOKP alpha 8, and got the "assert failed getprop ro.product.device" error. I tried twice, toggling assert both times, same error. Tried CM9 alpha 8 and got the same result. Both had matching md5's so the downloads were okay. Flashed bobz back on it, the AOKP flashed fine. Just thought you'd want to know.

Open up the zip and go to /META-INF/com/(bottom folder)/(bottom folder)/ updater-script and open the updater-script with notepad
Delete the line near the beginning that says "assert.....................;" delete all in the quotes including the ";"

"..." stands for whatever it says xD

 

[brotherswing]

I'd found that solution as well, it was just easier for me to switch recoveries and back.