• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [RECOVERY][UPDATE: 11/30/2012] CWM Recovery 6.0.1.9 by b_randon14

Seeing that our phone is not abandoned by community, seeing this little updates like CWM, or themes on forgotten Stock, or Sharp Roms, not to mentioned bigger things like CM9 and Kernel updates make me believe that I will use Triumph for the next 10 years.
Thank you guys for the hard work.

Flashed it right away and re-flashed CM9 update 2. No issues so far.
 
  • Like
Reactions: g60madman
Upvote 0
Awesome. Did you leave the option to select backup type? DUP is the default and I do not want to use this incremental backup type. Hopefully once TAR is chosen the first time, CWM will write a small file to remember this selection. At least this is the way 6.0.1.5 works on my GNex. Most users will want to toggle the backup type to TAR the first time they use it. Thanks again! B_randon
 
Upvote 0
I restored a backup of Froyo Ics to use hdmi and while I was at it I installed this recovery.

When I finished, I restored Cm7 from backup and bootlooped. Tried multiple times.

Went back to cwm 504 and restored same back-up successfully.

Don't know what's up. Any ideas?

Colors?
I don't care at all, but the lime green selection w/ white letters is impossible to read... At least to me.

Thanks for all the work on this, b!
 
Upvote 0
Awesome. Did you leave the option to select backup type? DUP is the default and I do not want to use this incremental backup type. Hopefully once TAR is chosen the first time, CWM will write a small file to remember this selection. At least this is the way 6.0.1.5 works on my GNex. Most users will want to toggle the backup type to TAR the first time they use it. Thanks again! B_randon

Yeah that option is there and once you choose it, it sticks! It saves a file in the clockworkmod directory!
 
Upvote 0
I restored a backup of Froyo Ics to use hdmi and while I was at it I installed this recovery.

When I finished, I restored Cm7 from backup and bootlooped. Tried multiple times.

Went back to cwm 504 and restored same back-up successfully.

Don't know what's up. Any ideas?

Colors?
I don't care at all, but the lime green selection w/ white letters is impossible to read... At least to me.

Thanks for all the work on this, b!

Hmm that is odd. I have restored cm7 quite a few times testing things out. I'm hoping we wont run into issues with backups made with older recoveries.

And yeah I can understand that. I'm just partial to line green if you guys didn't catch on yet lol!
 
Upvote 0
Okay so I have added a ICS Blue and Red themed, the ICS Blue looks close to stock colors with a little tweaking, very easy on the eye, and the Red one is well a red themed one lol!

I also added a power select version as well. It is ICS Blue, but I mapped it so that the power button selects items. Right now I am looking into finding out how to enable to where it always shows the back menu item. I believe its by defining has no select button in the BoardConfig, but i'm not for sure. If anyone knows for sure let me know!

Hope everyone enjoys these new colors!
 
Upvote 0
This is awesome, so happy adb will work. I am in the middle of re-setting up my environment when I deleted the document I saved things like the adb udev rules for triumph and this just popped up when I tried to Google them.

Still seem to not be able to find the udev rules if anyone has them handy,lol.

What I do is Google udev android or something and there is a cm7 wiki page talking about how to make your udev file. And to get our vendor ids and stuff just hook your phone up and have advanced debugging on and type lsusb in the terminal on your desktop. It will list all USB devices and ours will be foxconn. Do the sane for recovery cause the ids are different.

Remember to restart udev again and unplug and plug the phone back in. Also if you want when I get back on my Linux box ill copy my udev rules and post them for easy access!!
 
  • Like
Reactions: Chairshot215
Upvote 0
Has anyone tried restoring a Froyo ROM to see if it will restore properly? I did two backup's, one with dup and one with tar, and I see the tar files are named correctly (ext3) as opposed to CWM 5.5.0.4 which gives them an ext4 extension. I found out the hard way that CWM 5.5.0.4 does not seem to restore Froyo backups properly, even when you rename the backups to ext3 and change the extensions in the md5 hash file.

I really do not want to have to install from scratch again while testing other ROM's.
 
Upvote 0
And yeah I can understand that. I'm just partial to line green if you guys didn't catch on yet lol!

Okay so I have added a ICS Blue and Red themed, the ICS Blue looks close to stock colors with a little tweaking, very easy on the eye, and the Red one is well a red themed one lol!

I'd like to express the opinion that the
 
Upvote 0
Yeah as long as the file names are right. See when restoring, cwm parses the ext3 or ext4 or whatever out of the filename in order to determine what to format the partition as. And on the old 5.5 recovery, the recovery.fstab defined system data and cache all as ext4 so even when backing up a stock rom in the recovery those partitions were mounted as ext4.

But I fixed that issue in this cwm build. I set system data and cache as auto so it mounts it as whatever the partition is formatted as. So on a stock rom it formats it all to ext3 and on cm it formats system to ext4 and the rest stay ext3 but get mounted as ext4 by cm7 when the rom loads.

In the old 5.0.2 recoveries, you could specify two filesystems in recovery.fstab and so we had ext4 and ext3 listed which is why we never had that problem before!!

Long story short, yes restoring a stock, or even sharp or x6 variant rom, will work with this cwm recovery.
 
  • Like
Reactions: Inc0gnit0
Upvote 0
It works very nice for cm9...finished restoring so quickly I thought for sure it didn't restore...but it booted and all was as I left it...only problem is I keep booting into recovery to find a near colorless recovery screen that I can't read...it has buggy lines running through it and just isn't right...about 1 in 10 boots into recovery it comes up with full color and looks great...I have used both the red and the ics blue neither working correctly...I used flash able files...could there be a problem with the flash able files...I flashed twrp and it works perfectly...any ideas
 
Upvote 0
What I do is Google udev android or something and there is a cm7 wiki page talking about how to make your udev file. And to get our vendor ids and stuff just hook your phone up and have advanced debugging on and type lsusb in the terminal on your desktop. It will list all USB devices and ours will be foxconn. Do the sane for recovery cause the ids are different.

Remember to restart udev again and unplug and plug the phone back in. Also if you want when I get back on my Linux box ill copy my udev rules and post them for easy access!!

Here is my udev code for the Triumph:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0489", ATTRS{idProduct}=="c000", MODE="0660", OWNER="brandon" #Triumph Normal Mode
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0489", ATTRS{idProduct}=="c002", MODE="0660", OWNER="brandon" #Triumph Recovery Mode

Change owner to whatever your username is on your linux machine!
 
  • Like
Reactions: Chairshot215
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones