This is CWM Recovery v6.0.1.2 Beta. It needs some testing and some feedback. I haven't tested every new option yet but the basics seem to work fine. I factory reset and installed 3 ROMs with no problems: Sharp Ver8, My GB ROM, and CM10. I have also restored some very old backups of CM7 and froyo. Let me know how it goes.
Thanks to b_randon14 for the updater.script to make it a flashable zip.
Installation(custom recovery):
1. Copy to SD card
2. Boot into recovery (Vol +,Vol-, power)
3. Install zip from sdcard > choose zip from sdcard
4. Select CWM Recovery v6.0.1.2 Triumph - BSydz.zip
5. Reboot
Installation(Stock recovery):
1. Extract zip file on to PC
2. Boot into Download Mode (Vol-, power)
3. Plug in usb cable
4. Browse to the image folder in the mobile partition
5. Replace the recovery.img file in the image folder with the one you just extracted
6. Unplug cable
7. Pull battery
8. Restart phone.
Controls:
Volume up -------> Up
Volume down ----> Down
Menu -------------> Select
Back -------------> Back
NOTE: Issue with creating backups as ext4 filesystem, will cause issues with some Froyo ROMs. Workaround: If you run into this you can just change the file names in the backup from ext4 to ext3 and also change the names in the md5 file. There is no need to redo any of the md5 checksums.
NOTE: There is one initial error, but no ill affects: E:Can't mount /cache/recovery/command
This is CWM Recovery v6.0.1.2 It needs some testing and some feedback. I haven't tested every new option yet but the basics seem to work fine. I factory reset and installed 3 ROMs with no problems: Sharp Ver8, My GB ROM, and CM10. I have also restored some very old backups of CM7 and froyo. Let me know how it goes.
Installation(custom recovery):
1. Copy to SD card
2. Boot into recovery (Vol +,Vol-, power)
3. Install zip from sdcard > choose zip from sdcard
4. Select CWM Recovery v6.0.1.2 Triumph - BSydz.zip
5. Reboot
Installation(Stock recovery):
1. Extract zip file on to PC
2. Boot into Download Mode (Vol-, power)
3. Plug in usb cable
4. Browse to the image folder in the mobile partition
5. Replace the recovery.img file in the image folder with the one you just extracted
6. Unplug cable
7. Pull battery
8. Restart phone.
Thanks to b_randon14 for the updater.script to make it a flashable zip.
There is one initial error: E:Can't mount /cache/recovery/command
Do I really need to upgrade from the cwm i have? Is there an issue?
Quote:
Originally Posted by Urfreaky
What's the difference between this one and the old recovery?
I'll have to check out the CWM change log, I'll update the OP as soon as I do. This has an updated UI and also some extended options throughout the menus. I've only had it installed for a couple hours, so give it some time, check it out for yourselves. I would never release something I have not tested, just beware that there might be a few issues with the extended options. All of the basic wipe, install and restore functions work, and the wipe especially seems to be much faster now.
The Following User Says Thank You to BSydz For This Useful Post:
I'll have to check out the CWM change log, I'll update the OP as soon as I do. This has an updated UI and also some extended options throughout the menus. I've only had it installed for a couple hours, so give it some time, check it out for yourselves. I would never release something I have not tested, just beware that there might be a few issues with the extended options. All of the basic wipe, install and restore functions work, and the wipe especially seems to be much faster now.
Faster is always better . I noticed since i switched from the OV that the recovery process takes longer than it did on the OV for sure. I will watch this thread and upgrade when several people have tested and all the bugs are worked out!
And they added the dedupe feature for backups and restores which helps save space and speed up backup and restores because it makes blobs of all the files and uses a sha256 checksum and so it checks to see if the file has changed and only backups up files that have changed.
The only thing I'm having problem is that the way the recovery.fstab is wrote on the cm10 tree it only lists ext4 as the filesystem which is fine for most but I liked how on older recoveries it listed a fs type 2 so you could list ext3. What this causes is it makes all backups list as an ext4 backup so when you restore it, it formats the partitions to ext4 which can cause problems in a stock kernel that mounts everything as ext3.
I finally got my box to build the recovery but I modified the recovery.fstab trying to get it to backup as ext3 on the stock rom and completely borked the recovery lol!! It wouldn't mount anything because of the malformed recovery.fstab.
You may also notice that the partition sdcard option is no longer on the advanced menu as well as power off. I got the partition sdvard to show up by Modding the extendedcommands.c file and I'm going to try to get the power off option back.
And ideally I would like to try to get USB mass storage working and get it to backup and restore the /hidden and hidden/data partitions and potentially the brat partition containg the bootloaders and recovery.
I guess if I can find some dev time I'm going to play around with cwm 6 for a while.
I like the way cwm 6 looks and feels though. Its a much better built recovery! Kudos to bsydz for building this!!
Its all a matter of choice. Twrp was a little too wonky for me I just like cwm better. But yeah I'm not sure if adb works on this build it not. If it don't that is another thing I wanna work on getting lined out!
The only thing I'm having problem is that the way the recovery.fstab is wrote on the cm10 tree it only lists ext4 as the filesystem which is fine for most but I liked how on older recoveries it listed a fs type 2 so you could list ext3. What this causes is it makes all backups list as an ext4 backup so when you restore it, it formats the partitions to ext4 which can cause problems in a stock kernel that mounts everything as ext3.
I finally got my box to build the recovery but I modified the recovery.fstab trying to get it to backup as ext3 on the stock rom and completely borked the recovery lol!! It wouldn't mount anything because of the malformed recovery.fstab.
You may also notice that the partition sdcard option is no longer on the advanced menu as well as power off. I got the partition sdvard to show up by Modding the extendedcommands.c file and I'm going to try to get the power off option back.
I can confirm that it sets the backups as ext4 and gets stuck at logo after restore on froyo roms. I'll see what i can do.
EDIT: I got the power off option and almost have the ext4 issue resolved, but I'll have to finish up tomorrow.
Last edited by BSydz; September 14th, 2012 at 10:42 PM.
The Following 2 Users Say Thank You to BSydz For This Useful Post:
Do you got your sources up on github for your recovery?
Not yet, I'll push the whole CM10 code once I get a few things worked out. I wouldn't mind collaborating with this, I can send you the modified files, I don't like putting unfinished stuff out to the public. Get at me if you have any ideas.
EDIT: Sorry I had just woke up.
Last edited by BSydz; September 15th, 2012 at 08:10 AM.
Device(s): Nexus 4
Galaxy Nexus
EVO V 4G
Viewsonic GTab
Carrier: Not Provided
Thanks: 11
Thanked 8 Times in 5 Posts
Quote:
Originally Posted by b_randon14
And they added the dedupe feature for backups and restores which helps save space and speed up backup and restores because it makes blobs of all the files and uses a sha256 checksum and so it checks to see if the file has changed and only backups up files that have changed.
I think it is fantastic we are getting an update to the new version of CWM for our MT's. I'm also using the Touch version of 6013 on my GNex. Just wanted to say that many people who are using version 6 do not like the new default backup method which uses blob files. The first time you use it, it will create a blob folder under CWM and fill it with many HUNDREDS of small files there. Yes, it is faster on subsequent backups, but the blob folder can quickly get out of hand and become several GB's. Due to the number of files, it is IMPOSSIBLY slow to transfer back to a PC, and you have to transfer both the blob folder and the individual backup folders at the same time because they are dependent on one another. Another issue folks are having is with switching ROMS. If you switch to a different ROM(s), all the blobs and backups will not work for the new ROM. You have to move off the old backups to the PC, and then start over for the new ROM.
The reason I bring this up is that in 6013 there is a new backup method TOGGLE people should know about. Not sure if it is included in this version of 6012. You can toggle back and forth from the default *.DUP backups (blobs) to the old *.TAR type everyone is famililar with. Using the TAR method allows you to quickly archive backups on your PC and switch freely between ROMs. This is just a heads up for those who are trying v. 6.x for the first time. You want to make sure you have the toggle in your version, and you will probably NOT want to use the default method. If you are interested, I have included a link to Koush's blog. It's way down toward the bottom, but he talks about making the toggle in response to user requests.
You may also want to consider looking at the "touch" version of CWM if this is not too difficult to implement vs. the current standard version. Hope this is helpful, and when I get some time, I will flash this to one of my MT's and report back.
Ok, so I found a way to get around the ext4 issue. I have included instructions in the OP.
Issue with creating backups as ext4 filesystem, will cause issues with some Froyo ROMs.
Workaround: If you run into this you can just change the file names in the backup from ext4 to ext3 and also change the names in the md5 file. There is no need to redo any of the md5 checksums.
Yeah I had to do tar with a backup I had made using cwm 5.5 on the stock rom renaming them. Like I said I'm gonna work with the fstab and see if I can't get a smarter recovery that can choose which filesystem to mount as!
So, after searching for many hours, I can not find a way to build the touch recovery. So, I used the online tool to make this for testing. This is just a test, there is no way to really modify the build process, so this is as is, and won't be updated. I just figured a few people might wanna try this out.
Controls:
Menu --------> Down
Home -------> Up
Back --------> Back
Search ------> Select
Vol up -------> Up
Vol down ----> Down
Power -------> Select
And they added the dedupe feature for backups and restores which helps save space and speed up backup and restores because it makes blobs of all the files and uses a sha256 checksum and so it checks to see if the file has changed and only backups up files that have changed.
The only thing I'm having problem is that the way the recovery.fstab is wrote on the cm10 tree it only lists ext4 as the filesystem which is fine for most but I liked how on older recoveries it listed a fs type 2 so you could list ext3. What this causes is it makes all backups list as an ext4 backup so when you restore it, it formats the partitions to ext4 which can cause problems in a stock kernel that mounts everything as ext3.
I finally got my box to build the recovery but I modified the recovery.fstab trying to get it to backup as ext3 on the stock rom and completely borked the recovery lol!! It wouldn't mount anything because of the malformed recovery.fstab.
You may also notice that the partition sdcard option is no longer on the advanced menu as well as power off. I got the partition sdvard to show up by Modding the extendedcommands.c file and I'm going to try to get the power off option back.
And ideally I would like to try to get USB mass storage working and get it to backup and restore the /hidden and hidden/data partitions and potentially the brat partition containg the bootloaders and recovery.
I guess if I can find some dev time I'm going to play around with cwm 6 for a while.
I like the way cwm 6 looks and feels though. Its a much better built recovery! Kudos to bsydz for building this!!
So, I found a pretty cool way to get around the recovery.fstab ext4 issue. After trying every filesystem I could think of, emmc, mtd, yaffs, etc., I was stuck. So, I was like what the hell, I replaced ext4 with auto and everything mounts and I just made a backup, just need to do some more testing. I wish we could just put auto in more things and have it work!
The Following 2 Users Say Thank You to BSydz For This Useful Post:
So, after searching for many hours, I can not find a way to build the touch recovery. So, I used the online tool to make this for testing. This is just a test, there is no way to really modify the build process, so this is as is, and won't be updated. I just figured a few people might wanna try this out.
Controls:
Menu --------> Down
Home -------> Up
Back --------> Back
Search ------> Select
Vol up -------> Up
Vol down ----> Down
Power -------> Select
I flashed this and its working pretty good. It seems to be fully functional. The only problem is that you can double click sometimes because it is super sensitive to your touch. If you careful though, its not a problem.
The Following User Says Thank You to RobertsDF For This Useful Post:
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
This upgrade is nice. Although most people don't care about what Recovery version they're using (heck most Android users don't know their OS version or care about it) but it seems to be a bit more stable than before. Great job brother! This this hauls serious butt. I was getting sick of the old clockworkmods getting slow, freezing and rebooting during a backup, and not giving proper progress. Touch is not really needed, I'm so used to the old way of doing things, and plus since the Triumph's keys are so touchy and often stop working for no reason, I have better confidence in the volume keys.
The Following User Says Thank You to MikeRL For This Useful Post:
So, I found a pretty cool way to get around the recovery.fstab ext4 issue. After trying every filesystem I could think of, emmc, mtd, yaffs, etc., I was stuck. So, I was like what the hell, I replaced ext4 with auto and everything mounts and I just made a backup, just need to do some more testing. I wish we could just put auto in more things and have it work!
So in the fstab just have the filesystem as auto? Wow that makes so much sense lol! That is awesome thanks bsydz! And what did you do to get the power off menu back on?
The Following User Says Thank You to b_randon14 For This Useful Post:
So in the fstab just have the filesystem as auto? Wow that makes so much sense lol! That is awesome thanks bsydz! And what did you do to get the power off menu back on?
Well the auto doesn't exactly work like I wanted, it will backup cm10 but throws an error can't mount /system when I try to back up sharp ROM, but it will mount system in mounts. I am thinking ext3 would be best for cache and data since all ROMS except your stock ROM only format /system and all would work with ext3.
As for the power off, just add "power off" under "advanced" in char* MENU_ITEMS, in default_recovery_ui.c.
Code:
char* MENU_ITEMS[] = { "reboot system now",
"install zip from sdcard",
"wipe data/factory reset",
"wipe cache partition",
"backup and restore",
"mounts and storage",
"advanced",
"power off",
NULL };
Also, it seems that 6.0.1.3 has the format SD option available, I saw it, but I ran so many test builds that I don't remember which one or with what settings.
But, I found out how to get the other X6 variant kernels to read our baseband, also I found why the new kernel would not work unless you flash the nb0. So I ended up "bricking" my dev phone, for the umpteenth time, kinda, I'll get it back like I always do. But now that I know these things I am going to try to make a modified nb0 with the correct info and new kernel to see if I can get it to boot. Plus, I want to build a kernel for cm7 with the source from the Mi410, with those changes. So much I want to do and no time to do it, I wish I knew how to code, it would speed things up quite a bit.
Last edited by BSydz; September 16th, 2012 at 05:00 PM.
The Following User Says Thank You to BSydz For This Useful Post:
i havent tried it yet but i was using cwm 5.5.0.4 and having the same issue with a sharp restore. i am sure the filename fix will fix it, thanks for that and the new cwm.
The Following User Says Thank You to mattbodin For This Useful Post:
When I wipe data/factory reset, the wipe completes but I do get the error
Code:
E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2
Should this be expected?
That is more than likely because you don't have a second partition for android on your SD card. If you have one you don't get that error, but if you don't, you get the error. mmcblk1 is the SD and mmcblk0 is the internal phone storage. It is just trying to wipe everything, that may be there. Hope this answers your question.
The Following User Says Thank You to BSydz For This Useful Post:
So in the fstab just have the filesystem as auto? Wow that makes so much sense lol! That is awesome thanks bsydz! And what did you do to get the power off menu back on?
I just had an idea. Have you tried adding multiple lines for the partitions yet? Like, run two lines, one for system ext4 and one for system ext3. I'll try it when I get a chance. Just ran through my head and didn't want to forget.
I'm not sure. I know in old cwm's you could specify two seperate filesysem types in the recovery.fstab. look at the fstab in the cm7 source!
Yeah, I have tried that and, like you said, it shot out a bunch of errors and couldn't mount most of the partitions. I tried to edit it like that to no end, adding the fstype 2. I am saying add a whole new line, I'm not by my linux box right now, but like this:
Ill try that when I get a chance. Did you jjust copy over the fstab like in cwm 5 because I think all the NULLS are throwing it off when it tries to parse the partition information.
Ill try that when I get a chance. Did you jjust copy over the fstab like in cwm 5 because I think all the NULLS are throwing it off when it tries to parse the partition information.
I prefer editing to copying, and I edited it in every way possible, NULL, no NULL, every fs I could think of, it would throw an error any way I tried other than just like the template. Even with the online tool, I tried the fstype 2 fstab, just in case the automated process had some extra options. I even posted on Koush's google+, to see if he could add it back in.
Dang. I wonder why took out that feature. Ill try to compare where the old recovery parses the fstab information at and see what all changed.
I tried editing it back in but it didn't work, but I don't fully understand the code yet to be able to work everything in. Hopefully you will have better luck. I think it was roots.c and .h.
Yeah I found in roots.c where it parses the fstab. Its in a function called like create volume tables it something. I got it to build after replacing that whole function with the old one and using our cm7 fstab and I even made ext3 fstype 1 and ext4 as fstype 2 and it still backs up as ext4. I'm gonna play with it some more and see what I can do. I've also got some ideas on how to get it to backup more partitions such as /hidden and maybe even the vfat mobile partition. I know you can add them in the fstab but that doesn't make it back it up, you have to tell it to look for those partitions in nandroid.c in the backup and restore functions. I'm gonna play around with it some more though!
EDIT: I pushed the changes where I replaced the nee cwm6.0 fstab parsing function in roots.c with the old one from.cwm5.0! Its on my github!
The Following User Says Thank You to b_randon14 For This Useful Post:
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
I'm currently having serious issues here. I have no clue why, as my recovery was working fine at this version for about a week. Anyhow, now I always get reboots in the middle of a backup. I cannot backup my install at all. Does anybody have any suggestions of what to do next? I've tried reflashing my recovery, but to no avail. Someone please assist!
I'm currently having serious issues here. I have no clue why, as my recovery was working fine at this version for about a week. Anyhow, now I always get reboots in the middle of a backup. I cannot backup my install at all. Does anybody have any suggestions of what to do next? I've tried reflashing my recovery, but to no avail. Someone please assist!
I had an issue with the SD getting corrupted from the new backup system while it was cleaning up. I deleted a few unneeded backups from testing, and it hung while it was cleaning up. I popped the card in the pc and scanned the disk and all the errors were in the clockworkmod folder. Things still need to be ironed out, I'm still working on this. My brake line broke on my car, so I have been under my car all day and then it started raining so I have to finish that before I go back to work. CWM v6 implemented a lot of new code when it comes to backups, b_randon is also working on some of the issues, as well as me. Hopefully we can get a very solid recovery for us to use. In the mean time, bear with me, and keep reporting any issues that you might have.
The Following 2 Users Say Thank You to BSydz For This Useful Post:
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
Thanks, brother! I was about to throw my phone across the room, as I thought these issues were unsolvable, but thanks for answering me! Plus I was so worried about getting this sorted out that I overworried since I wanted to get it sorted out so I could return to my work. Anyhow, I'll check the SD card for errors and hang in for a while as I report errors. I have patience, but I guess my patience snapped for once. Sorry about that.
Last edited by MikeRL; September 22nd, 2012 at 06:48 PM.
The Following User Says Thank You to MikeRL For This Useful Post:
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 188 Times in 125 Posts
I know you guys have literally broken your backs on this recovery, but perhaps we should mark it as beta or experimental? The menus get garbled up when I go to change the backup format. Also, despite working perfectly for a week, after about a week I get a reboot and freeze on every backup I do. I know you all are busy, but this doesn't quite seem release quality yet. I know a lot of hard work went into this, but perhaps we should put a warning about these issues in the initial post? First tend to your busy lives, and we can eventually mark this as stable. It's just that so much has changed with how ClockworkMod does backups from 5x to 6x that many interesting bugs seem to have arrived. I'm busy myself, but I will continue to report bugs, and if you need log files, let me know.
The Following User Says Thank You to MikeRL For This Useful Post:
I have used cwm 6 with success it is faster than the older versions. For me it backed up about 90 seconds faster and restored about 90 seconds faster. I was able to install starship triumph but did not have success with the MTDEV 7.2 ROM. I had to use 5.0.2.6 in order to installed the MTSEV 7.2 ROM.
The Following User Says Thank You to connorallen For This Useful Post:
I agree with everyone who says this was productive. I installed it the other day, and it's much better and faster. *round of applause* Thank you very much for your contribute.
The Following User Says Thank You to Dimensions For This Useful Post:
Hey bsydz, I have got cwm to successfully backup the /hidden/and /hidden/data partitions. I haven't tried the restore yet but it should function as well. Now I'm working on having it backup the mobile partition so that all the recovery and boot information can be backed up!!
I've been playing around with the fstab trying to get it to work like on cwm 5.0 but its not working it still recognizes everything as ext4. For now I'm using auto for system data and cache but I'm trying to figure it out! But so far I've got it pretty good lol!
Hopefully this isn't too old to bump up. Have you tried to backup and recover with this? I tried the main recovery and your 5.x version of recovery and both just made my phone boot loop. (Had plans to wipe anyways so it's all good)
Tried the fix permissions without luck. SO just asking about the luck you guys had with this before I go and update/test.
5Likes
CWM Recovery v6.0.1.2 Beta for the Triumph
So, I was like what the hell, I replaced ext4 with auto and everything mounts and I just made a backup, just need to do some more testing. I wish we could just put auto in more things and have it work! 
Have you tried adding multiple lines for the partitions yet? Like, run two lines, one for system ext4 and one for system ext3. I'll try it when I get a chance. Just ran through my head and didn't want to forget.
