[RECOVERY][CWM][6.0.3.2] Sk8's CWM Touch Recovery v15.0.2 (05/15/13) - One (M7) Original Android Development

Another port of my custom recovery.
For the aroma file manager option to work you have to flash the zip at least once as the zip file will put aroma in the correct place on your sdcard.
Download ------> cwm6032touch_v15.0.2_m7.zip
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
htc-msm8960 for their device tree
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
Code:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Code:
v15.0.0
- updated to latest cwm source
- added HTC One into the group
Code:
v15.0.1
- fix zip file
[/CODE]
Current Version:
v15.0.2
- update to latest cwm official changes
Click to expand...
Click to collapse
How touch works:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.

---

Sounds great - keeping the backup size low is very useful especially when all of the roms are 900+ MBs. I wish there was an easy way to move / still use my TWRP backups.

---

Thanks... Testing it out now...
Sent from my HTC One using xda app-developers app

---

Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated

---

johnblundon said:
Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated
Click to expand...
Click to collapse
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?

---

sk8erwitskil said:
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?
Click to expand...
Click to collapse
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide

---

Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.

---

johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
can you do a:
Code:
fastboot boot recovery.img
scotty2hotty1125 said:
Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.
Click to expand...
Click to collapse
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.

---

sk8erwitskil said:
can you do a:
Code:
fastboot boot recovery.img
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.
Click to expand...
Click to collapse
The script is to flash boot.img aswell. A bit of a typo!

---

backfromthestorm said:
The script is to flash boot.img aswell. A bit of a typo!
Click to expand...
Click to collapse
so youre saying you were flashing boot and recovery?

---

sk8erwitskil said:
so youre saying you were flashing boot and recovery?
Click to expand...
Click to collapse
No, just look at the script in the zip. It's all wrong.

---

backfromthestorm said:
No, just look at the script in the zip. It's all wrong.
Click to expand...
Click to collapse
ah youre right. thanks for catching that! i just typed the wrong name so it wasnt flashing anything haha. fixed it now

---

thanks a lot
great recovery with no aroma installer issue

---

Still don't think it will flash anyway, unless s-off, though you could try dd'ing it like how we flash the boot partition now if the straight flash won't do it.

---

@sk8erwitskil
Hey which kernel you using for this?

---

johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
Boot into phone and go into settings and disable fast boot and you should boot into recovery fine.

---

Thanks I'll try right now
WORKED PERFECTLY!!! THANKS SOOOO MUCH!!!

---

Flyhalf205 said:
@sk8erwitskil
Hey which kernel you using for this?
Click to expand...
Click to collapse
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.

---

sk8erwitskil said:
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.
Click to expand...
Click to collapse
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?

---

Flyhalf205 said:
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?
Click to expand...
Click to collapse
yah im using the same kernel then. are the aroma issues proven to be kernel related? and i think the person that mentioned aroma was referring to the fact that the installer wasnt build with aroma so they didnt have to deal with that when installing this recovery.