Android OS Forum banner

[RECOVERY][3-2-12]ClockworkMod Recovery

139K views 96 replies 46 participants last post by  Pesach Ben Schlomo  
#1 · (Edited by Moderator)
Previously, we had CWM 4.x for the Charge, and I attempted a while ago to update it to CWM 5.x and that didn't work. I just tried again and it worked this time doing the same thing as before. Not completely sure what changed to make it work, but I'm not complaining. Enjoy and let me know if there are any issues. I did some quick testing and didn't see anything wrong, but I can only test so much.

Button Mapping
Vol Up / Home - Go up
Vol Dn / Menu - Go Down
Back - Go Back
Power / Search - Select Item

Flashing Tips
Use the rear USB Ports on your computer if possible, and without a USB extension cable.
When in Download mode with the battery out, put the battery back in and uncheck Auto-Reboot in Odin. When done flashing, remove the battery and USB cable, put the battery back in and reboot - credit to jami2976

Known Issues
CWM Getting over-written by stock recovery - Flash a custom kernel or delete /system/etc/install-recovery.sh
Failed to mount /sdcard error(s) - Perform the following commands with ADB:
Code:
adb shell<br />
umount /sdcard<br />
rm -f /sdcard<br />
mkdir /sdcard<br />
exit
Type each line in and press enter. Do not skip a line, or you may loose data
Image
It seems to have worked for anyone that tested and had this issue.

Download
0817
 
#8 · (Edited by Moderator)
imnuts, thanks for this and all your hard work.

I had to revert to stock ep4d which is now setup and I'm as happy with it as I can be with the unrooted stock ROM. I'd like to now install Infinity but would love a path back to my current setup. Can I flash this CWR and create a b/u (Nandroid?) before I install superuser or delete /system/etc/install-recovery.sh and if so would it get me a way back to where I am right now? I assume once I root and ROM I could restore with the CWR installed and then when I rebooted /system/etc/install-recovery.sh would be back and it would replace CWR with stock recovery?

Is my thinking any good on this?

Thanks again
 
#9 ·
If you have the EP4D radios and are happy with them, here is the path you should take to get to install Infinity:

-ODIN CWR
-if you want, I believe that it is possible for you to make a backup here, but I might me wrong (stock might wright over CWR on boot, but I honestly don't remember. It will be obvious if CWR is overwritten though
Image
)
-Place the Infinity zip on your SD card
-Reboot into CWR (power + home + vol up)
-flash the zipped Infinity.
-Profit.

Let me know how it goes
Image
 
#12 · (Edited by Moderator)
Maybe this is normal for the different versions of CWM, but tonight while using one ROM I decided to restore back to another using from a backup I had made using the 4.0.1.4 version and it boot looped. I was able to restore the phone using a backup made in version 5 though.

late night update - flashed back the older 4.0.1.04 CWM and was able to cleanly restore my older backups. I think that confirms that 5 will not restore backups made from the last 4 version.
 
#17 ·
How is backup/restore in this version?

Why did the backup functionality change? I looked at the backup that it made and it makes a TAR file of all of your phone's files. Are there any consequences to using this method as versus what looked like images created by the dd command?
 
#22 ·
I had a major problem yesterday restoring a nand backup. Using this recovery, I made a backup. I was coming from full stock ep4, rooted, and self-debloated. I then flashed the 12/11 infinity-tsm-ext rom. I found some temporary turnoffs (which I'll discuss in another thread) and decided to revert. The first time I tried to restore the backup, it failed at the rfs format step. I suspected this had something to do with the ext4 formatting that was done when I flashed the rom. So then I flashed the stock ep4 image to get everything back to the way it should be. When I tried to restore again, it failed at the same point. I tried a second time (reflash stock and start over), and again failure.

could my backup have been bad?
 
#25 ·
imnuts said:
It does have a .md5 at the end
Image
Basically what I'm saying is that every file I've ever flashed with Odin has had .tar.md5 at the end of the file name. The latest cwm ends in just .tar and it threw me for a loop. I wanted to make sure that was correct before flashing this on my phone. Thanks.
 
#26 ·
Money Mike said:
Basically what I'm saying is that every file I've ever flashed with Odin has had .tar.md5 at the end of the file name. The latest cwm ends in just .tar and it threw me for a loop. I wanted to make sure that was correct before flashing this on my phone. Thanks.
Somebody correct me if I'm wrong, but Odin checks if a file is able to be flashed before it actually does the flash. Regargless of extension.
.tar.md5 is just a naming convention but not a requirement.
 
#28 ·
I had an odd issue with the restore feature last night. For some reason when it began the system portion of the restore it suddenly said it could not mount system - and this issue persisted across several re-entries into CWM (and across CWM versions - at least the 4.0.1.4 that I flashed after the problem occurred) when trying to flash anything. Perhaps there was an issue when backing up the system partition, as I've had no issues with restore and this version of CWM prior to this incident. That being said, a re-ODIN to EP4D fixed everything just fine, and the advanced restore - data function worked great. Just thought I'd report the oddity.
 
#31 ·
I have found, like many others, that while being on Infinity ROM formatted to EXT4 and booting into CWM results in the dreaded wipe of data.

Flashing over latest Infinity EP4 ROM.... Booted fine.
Rebooting into recovery via shutdown menu.
I like the light blue of 5.0.2.7.
Rebooting to see if wipe issue persists.
The Samsung Galaxy S II splash screen still seems weird to me
and, Survey Says: I still have all my data!!!

Yay and thanks Imnuts for keeping the Charge alive.