[RECOVERY][UPDATE: 11/30/2012] CWM Recovery 6.0.1.9 by b_randon14
CWM Recovery v6.0.1.9 by b_randon14!
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these directions.
* YOU are choosing to make these modificiations, and if you point your finger at
* me for messing up your device, I will laugh at you.
*/
I have went through and modified much of the CWM code to make it more appropriate for our device.
Features:
*Base code taken from CWM 6.0.1.9 and will be kept up-to-date as best as possible
*Added backing up of /hidden, /hidden/data partitions that are used in the stock Triumph ROM's
*Added backing up of /mobile partition, also know as the download mode partition, image partition, vfat, or bootloader partition. It's where the recovery, splash image and bootloader information is stored at.
*Removed option of formatting the /mobile partition through CWM to prevent mishaps like in the old 4.x recoveries we had where people would format the /fat partition, causing phone to be unbootable.
*Removed default restore of /mobile partition. I did this mainly to prevent any mishaps such as a bad restore causing corruption to that partition, and also minimizing writes to that partition to prolong its life
*ADB debugging works perfectly. **If you are using Linux, don't forget to add a udev rule for the recovery mode of adb as well**
*Removed log errors of not being able to mount /cache/recovery/command and so fourth. As far as I can tell, everything functions as it should, and I know cache gets mounted, as well as the log files functions as they should to
*Added support for ext3 or ext4 on /system, /data/, and /cache so no more boot lockups when restoring a stock ROM!!
*Cleaned up the recovery overlay images, and tweaked the CWM theme a bit. It's lime green!
Change Log:
11/30/2012 - Switched to CM7 kernel base for the recovery. Hopefully this will cause less lockups and issues for people. Updated CWM base code to latest commits, should help with dedupe style backups. They still need more testing, if it reboots doing a dedupe backup, just use tar.
10/28/2012 - Reverted USB mass storage code back to currrent 6.0.1.5 version. Added ICS Blue and Red themed CWM recoveries. Added Power Select version of CWM 6.0.1.5
10/26/2012 - Initial release of CWM Recovery v6.0.1.5
Issues:
*Currently the only issue I have found with this recovery is not being able to mount USB mass storage through recovery. This is my main focus to fix right now
Installation:
Either download the recovery.img and install through download mode, or download the CWM flashable zip and flash through an existing CWM recovery.
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 the CWM 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
**The Power Select version is for those of you whose capacitive buttons don't work that great. You use the volume keys to navigate, and the power button to select items. And it shows a go back menu item at the bottom so you don't have to use the capacitive buttons at all!
Controls:
Volume up -------> Up
Volume down ----> Down
Menu -------------> Select
Back -------------> Back
If you encounter any issues using this recovery, please post in this thread so I can work to resolve them. Please note that I am already aware of the USB mass storage issue and this is what I am working to fix at the moment!
As always, I am not responsible for any damage inflicted upon your phone, or data loss, from using any mod found on this forum!!!
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 189 Times in 125 Posts
Can you make one with the regular light blue theme? I find this recovery to be awesome, but it's a bit odd for me to see it in yellow green. If it's a pain to do that, don't do it.
__________________
Be a pal and sign up for Dropbox with this URL (if you haven't already got an account) It will assist me and you by giving us both an extra 500MB space. Useful for all the uploads I share with you guys.
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.
Device(s): Nexus 4
Galaxy Nexus
EVO V 4G
Viewsonic GTab
Carrier: Not Provided
Thanks: 11
Thanked 8 Times in 5 Posts
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
And I'm thinking stock looking, maybe cyan, red, maybe even one for the girls, and then a sweet mtdev themed version!!
The MTDEV theme is a must...lol...they have 180'd the triumph in a matter of a few months...we all have a reason to love our triumphs now...full op ics is only steps away!
The MTDEV theme is a must...lol...they have 180'd the triumph in a matter of a few months...we all have a reason to love our triumphs now...full op ics is only steps away!
Don't forget b_randon is part of Team MTDEV He is just the quite developer in the back of the room mixing up the wicked kernel potions
I know hes part of mtdev...im hopin that you guys figure this kernel out...and that it will make the triumph so nice he wont wanna jump to straight talk...we know you have been busy lately b-randon but you and all of mtdev have been crucial to the distance made in fixing the triumph
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!
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!
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.
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!!
Thanks for the color options b_randon. I'm using the blue variation now but you might want to think about making the highlighted text on the lime green version black instead of white so it's easier to read :-)
The Following User Says Thank You to Inc0gnit0 For This Useful Post:
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.
And yeah I can understand that. I'm just partial to line green if you guys didn't catch on yet lol!
Quote:
Originally Posted by b_randon14
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 “ICS Blue” ought to be the default. “Easy on the eyes” is important, especially on a small screen, and especially for a cranky old man like me whose eyes aren't what they were when they were younger. (Though I think that even when my eyes were at their prime, I still would have found your “Lime green” scheme to be harsh and uncomfortable.)
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.
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
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!!
I just re uploaded a new power select version to my drop box. The only change I did was make it to always show the go back menu item at the bottom of every menu so that you don't have to use the capacitive buttons at all to navigate through the recovery. The zip name is the same so if you have already downloaded it, redownload it and install it. I tested it out and it works great.
As for the weird colors, I have never experienced this at all using these recoveries. And I installed mine using a zip so maybe it was a bad download. But it defiantly should not be doing this!
The Following User Says Thank You to b_randon14 For This Useful Post:
I get this some too.. It's the old washed out screen thing like stock ROM used to do occasionally. If it comes up like that, I go to reload recovery, under advanced (I know it's hard to read in this condition) and it usually comes back rendered correctly.
Yeah that works...its weird though...usually first boot is Color faded second boot is almost pure white and cannot be seen while third time is always the charm...like clockwork...lol
Device(s): Nexus 4
Galaxy Nexus
EVO V 4G
Viewsonic GTab
Carrier: Not Provided
Thanks: 11
Thanked 8 Times in 5 Posts
Did you toggle the backup type to .tar? The .dup backup can be huge, especially the first one. Good idea to wipe cache/dalvik to save space. Why didn't I think of that earlier?
Quote:
Originally Posted by thangfish
Has anyone noticed that backups made with this are friggin huge? Almost twice as big... And that's after wiping cache and dalvik.
Did you toggle the backup type to .tar? The .dup backup can be huge, especially the first one. Good idea to wipe cache/dalvik to save space. Why didn't I think of that earlier?
yeah, I did... found out that appextractor can't read the backups either.
and yeah, wiping first can save 100-200 mb... well it used to anyway.
If you have the default backup type set to dedupe it is an essential part of the backup. Its where it store information and prices of the backup. See dedupe style backups check to see what has changed and only backs up what's changed. It uses the prices in the blobs folder to check all that. I recommend changing to tar format backups as they are simpler and like the old style!
The Following User Says Thank You to b_randon14 For This Useful Post:
Still getting the whitewashed screen constantly...tried mtdev unroot to make sure all the symlinks were intact...used all 4 versions and applied by flashing and using PC...all versions the same...all older cwm versions work fine and twrp...I don't get it...any chance on you guys updating twrp to run like this one...I love twrps UI but the reliability of this cwm is the best I have seen so far...ever since last update I have not had any failed restores
If you have the default backup type set to dedupe it is an essential part of the backup. Its where it store information and prices of the backup. See dedupe style backups check to see what has changed and only backs up what's changed. It uses the prices in the blobs folder to check all that. I recommend changing to tar format backups as they are simpler and like the old style!
So if I don't have any dedupe backups I can delete the folder?
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 189 Times in 125 Posts
Know you're busy with all these recoveries, but I still seem to get reboot when doing backups. b_randon14, can you look into this? Is anyone else experiencing this issue? Otherwise, great job man! Something tells me these issues were bound to happen with a phone that has no relative with official CyanogenMod support, or recoveries. Plus CWM 6 was such a big change from the older ones. Please fix these reboots when you have time.
Last edited by MikeRL; November 9th, 2012 at 10:19 AM.
What's up Brandon? I have been flashing nb0s again, and while I was on Sharp 2.3.5, I had to use tjstyles recovery, because of the kernel. While I was messing around I figured I would see if usb would mount, and it did. I personally have never seen the usb mount in recovery, so this is my first proof that it can work. I know it is a different kernel and the recovery is built from the kernel but I just wanted to let you know. I believe it was 5.0.2.7 but I have refreshed my phone to stock since, so it's not there anymore. I know that most of the X6 recoveries worked on our phone, just different button setups, so I am gonna take a look and see if any of them will mount the SD.
I also pulled a kernel config from the stock Sharp 2.3.5 kernel which I believe is 2.6.35.7. Plus, I found a 2.6.38.6 kernel that has our camera driver, it is the highest version that I have seen that still has the mt9m111 driver. And it is different, I still have to see if it will work in our kernel to see if it works. I know you are not working on kernels at this time but just thought I would put it out there.
What's up Brandon? I have been flashing nb0s again, and while I was on Sharp 2.3.5, I had to use tjstyles recovery, because of the kernel. While I was messing around I figured I would see if usb would mount, and it did. I personally have never seen the usb mount in recovery, so this is my first proof that it can work.
Do you have a link to that recovery and would the USB mounting work on a CM9 Triumph?
I have updated the CWM to v 6.0.1.9, you can view the CyanogenMod recovery repository for more in depth changes. The important one is a buffer overflow fix for dedupe backups, which I am hoping will help with reboots during dedupe backups.
I also changed the kernel I used from the cm9 one to the cm7 one that has been used in most previous recoveries. Hope that will eliminate some of the issues.
USB storage still doesn't work on this. I am working on it!!
The Following 3 Users Say 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 189 Times in 125 Posts
Re: [RECOVERY][UPDATE: 11/30/2012] CWM Recovery 6.0.1.9 by b_randon14
I doubt highly that this has already been put to the side. Currently, USB storage needs some tweaks to work in recovery, and a new CWM may already be nearing release. It's probably best to wait until post 6.0.2.3 and then an update will probably come out. Plus, the current one works for me. There are also some Triumph specific bugs that need to be patched.
Does anyone have a backup of the hidden/ and the hidden/data partitions that I could have? Also a backup of the stock mobile partition? That would help me so much.
Device(s): LG Nexus 4, Asus Nexus 7, Motorola Triumph, & LG Optimus V - All Hacked & Running CyanogenMod!
Carrier: T-Mobile USA
Thanks: 221
Thanked 189 Times in 125 Posts
I am running that on the Triumph for testing purposes with that recovery, and have had no problems. Please redownload and reflash MTDEV CM7, and also reinstall the recovery. Have you forgotten to flash GAPPs (that is needed for the Market to work) and the home button has issues on every single ROM I've used, from stock to CM9. I think it's yet another Triumph hardware fault. The Triumph's hardware is definitely a piece of something, but custom ROMs definitely help. Not all the issues can be resolved with software changes alone, though. Update: I heard it through the grapevine that an update us brewing. But it will not fix USB mounting, that is going to be a massive task, if it's even possible, but some bug fixes will come soon. It's not going to be like when we went from CWM 5.5 to 6.0, but expect some minor patches. Barely any commits from Koush on this one. Most stuff must be working I guess. I do believe some of the errors went away on my Nexus 7 when I upgraded to 6.0.2.7, though. Minor annoyance errors. I have experienced nothing with the current recovery that was a serious bug. We have an update brewing, but everyone at MTDEV has a life unfortunately, so no ETA. Any question of an ETA will be redirected to /dev/null. Sorry b_randon14 if I stole your thunder.
Last edited by MikeRL; January 16th, 2013 at 09:20 AM.
28Likes
[RECOVERY][UPDATE: 11/30/2012] CWM Recovery 6.0.1.9 by b_randon14
He is just the quite developer in the back of the room mixing up the wicked kernel potions 
