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

[b_randon14]

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!

 

[thangfish]

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.

Haven't seen this screen condition in ages.

 

[jamesd1085]

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

 

[Cyta]

B_randon14 killing it as always. Awesome.

 

[thangfish]

Has anyone noticed that backups made with this are friggin huge? Almost twice as big... And that's after wiping cache and dalvik.

 

[bluetec]

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?

Has anyone noticed that backups made with this are friggin huge? Almost twice as big... And that's after wiping cache and dalvik.

 

[thangfish]

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.

 

[thangfish]

Ok, my mistake!
I took the time to do a comparison between 6015 and 5504 and the backup was only 100mb larger, which is completely understandable.

Seems my ROM installation has grown considerably since I last checked.

 

[b_randon14]

They should only be about 60mb bigger because it backs up hidden hidden/data and the mobile partition!

 

[rebel69ization]

b_randon ics cwm is EXCELLENT! Thank You

 

[mattbodin]

Is the blobs folder a temp folder?

 

[b_randon14]

Is the blobs folder a temp folder?

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!

 

[jamesd1085]

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

 

[mattbodin]

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?

 

[b_randon14]

So if I don't have any dedupe backups I can delete the folder?

Yeah if you change it to tar backups, the blobs folder is not used!

 

[MikeRL]

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.

 

[mattbodin]

i havent had a problem

 

[BSydz]

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.

Sharp235_defconfig.zip

 

[RolaAddict]

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?

 

[b_randon14]

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!!

 

[RolaAddict]

Any update on this?

 

[MikeRL]

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.

 

[oki doki]

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.

Edit: Nevermind, I answered my own question. I found the stock rom and boot partition here.
http://forum.xda-developers.com/showthread.php?t=1260816

 

[realdreams]

don't use this to install [ROM] MTDEV-CM7 build 2012-12-28, it causes all kinds of problems....
home button not working, no market.......

 

[MikeRL]

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.