188 replies to this topic

[Snap.IT]

bladebuddy, on 04 September 2012 - 04:26 PM, said:

Just spotted my mistake I seem to have a different version on to the the one on page 1, checked the sum of the wrong file, noticed my error and flashed the version I should of done in the fireplace and I still have the same problem.
Do you think flashing an older version of cwm the reflashing this will work sorry for the messup.

I can't reproduce the problem. Can you plug the phone to your computer and do an "adb pull /tmp/* ." and attatch the files to a post?

The way you install the recovery doesn't make any difference.

Edited by Snap.IT, 05 September 2012 - 04:51 AM.

[n1729]

@Snap.IT
One suggestion, is it possible to add an option like advanced backup where we can select what to backup. Might be helpful with your loop install project , as sometimes when switching to other rom it stuck on logo. So we have to restore from backup, instead we can only make backup of boot in place of full and only restore boot image and reboot into desired rom. Save SD space and less time consuming.
Just an idea and keep up the good work.

Edited by n1729, 05 September 2012 - 08:08 AM.

[Snap.IT]

n1729, on 05 September 2012 - 08:05 AM, said:

@Snap.IT
One suggestion, is it possible to add an option like advanced backup where we can select what to backup. Might be helpful with your loop install project , as sometimes when switching to other rom it stuck on logo. So we have to restore from backup, instead we can only make backup of boot in place of full and only restore boot image and reboot into desired rom. Save SD space and less time consuming.
Just an idea and keep up the good work.

I'll look into a solution for that when i get home in a few days.

[d_borghi]

beautiful release, but there isn't the "create partition" option ?!?!?!?
why?

[vNa5h]

This may not be related to cwm..

but why does cm7/gb roms stay too long in the splash screen than ics jb roms
it takes almost 10-15 secs
wheres in ics/jb its 2-5 sec and then moves to the boot animation

[targetbsp]

targetbsp, on 20 August 2012 - 09:42 AM, said:

Well, I've technically spent 36 hours trying to restore my sd-ext.   Not this particular recoveries fault.  I think there's something not quite right with CWM6 and sd ext and I'm still trying to narrow down what exactly.  Maybe when moving certain things (app data or dalvik or something) and or having multiple different roms both using sd ext.  Somewhere, something isn't quite right.

Switching to ext2 seemed to solve this.  The problem seems to be restoring a CM10 backup with ext 4 to a previously used ext4 partition.
Restoring Cm7 and ext4 is fine
Restoring CM10 and ext2 is fine
Restoring CM10 and ext4 is fine only if you delete and remake the partition (format isn't enough!)

[rwalton159]

Its been a while since I was in the forums and I am using Swedish Snow 2.3.5.

Is this worth putting on my blade and does youtube, camera and gps work ok?

Thank you
Richard

[targetbsp]

This is a replacement recovery and won't have any effect with regards to what works and doesn't work in your rom.

As recoveries go - it's great.  Whether it's worth putting on depends mostly on how often you use recovery i guess?  if you don't frequently backup, restore or switch roms then it won't be of much interest to you.

[rwalton159]

targetbsp, on 12 September 2012 - 05:44 PM, said:

This is a replacement recovery and won't have any effect with regards to what works and doesn't work in your rom.

As recoveries go - it's great.  Whether it's worth putting on depends mostly on how often you use recovery i guess?  if you don't frequently backup, restore or switch roms then it won't be of much interest to you.

Thank you

[Majkl007]

briliant work, thanks very much ;-)

[vNa5h]

Snap.IT, on 30 August 2012 - 03:26 PM, said:

New version of 6.0.1.2 testing.

Lowered brightness (set to 100 out of 255) and tweaked performance:

Fastboot flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.img
MD5: 343b410308bb80eeaccb2058dbf5e34c

Recovery flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.zip
MD5: 86f484657f79512afb7a6e63f073bb2c

I guess this is stable enough to be called stable...

[vNa5h]

Snap.IT, on 30 August 2012 - 03:26 PM, said:

New version of 6.0.1.2 testing.

Lowered brightness (set to 100 out of 255) and tweaked performance:

Fastboot flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.img
MD5: 343b410308bb80eeaccb2058dbf5e34c

Recovery flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.zip
MD5: 86f484657f79512afb7a6e63f073bb2c

I guess this is stable enough now to be called stable...

[gerhardo]

Minor issue: Advanced - Show Logs
You get back to the menu before being able to see the log.
Using the 6.0.1.2 version quoted in vNa5h post.

An issue related to the post below, not an issue caused by this recovery.

targetbsp, on 12 September 2012 - 02:27 PM, said:

Switching to ext2 seemed to solve this.  The problem seems to be restoring a CM10 backup with ext 4 to a previously used ext4 partition.
Restoring Cm7 and ext4 is fine
Restoring CM10 and ext2 is fine
Restoring CM10 and ext4 is fine only if you delete and remake the partition (format isn't enough!)

I have had a similar problem related to 6.0.1.2, even if it is the not touch version, by KonstaT.

I have a 8GB SanDisk card with a 7.5GB FAT32 and 512MB ext4 partition. The ext4 partition is currently not used (but I want to use it after updating to CM10...)
After updating to 6.0.1.2 I did a backup and updated to CM10. Did not change any partitions.
After startup, CM10 cannot read the card. There is no option to mount the card.
The sdcard will also not not be seen if plugin in to the SD card slot in the PC. A separate SD card reader mostly works.
I have tried reformatting the fat32 partition from recovery (non-touch and touch) and the PC, no change. sd-ext cannot be formatted (non-touch and touch).

I assumed the (almost new) sd card mysteriously broke when updating to CM10, but it may be something with CWM?

Edit: The card works again in the Blade, after removing and recreating the partitions in Linux. I have used CWM Touch 6.0.1.1 as recommended by Snap.IT below, seem to be working fine.
Edit2: The "log issue" also occurs for me with 6.0.1.1, there are a bunch of error messages hidden by the menu. Seem to be related to the path.

Edited by gerhardo, 07 October 2012 - 01:00 PM.

[Snap.IT]

There is a problem with 6.0.1.2 (and it is still there in the two following versions) which is why i haven't moved it to stable yet.

I recommend sticking with last known stable.

[Buffalo Soldier]

Does anybody know why do I get this error:

Installing update...
symlink: some symlinks failed
E:Error in /sdcard/cm-10-20120927-KonstaKANG-blade.zip
(Status 7)
Installation aborted.

This happens only with JB roms (I tried Burstlam's CM10 too), but not with CM9 and SS-RLS7.
I'm on CWM Touch 6.0.1.2, but I also tried going back to normal 6.0.1.0 and it's the same.
Thanks...

Edit: Solved, just followed the right wipe procedure and everything went fine.


Format > System
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik

Edited by Buffalo Soldier, 10 October 2012 - 12:57 PM.

[Snap.IT]

FOR TESTING PURPOSES ONLY!

It will not backup properly and usb storage doesn't work.

Testing version 6.0.1.5:

I've tested everything on it without any hickups, problems with previous versions (6.0.1.2 6.0.1.3 6.0.1.4) backup and sometimes hangups is solved in this one.

It includes a new menu item named "install zip from sideload" which can be used for installing a zip from your computer using "adb sideload 'path/to/zip'". It requires a newer adb, version 1.0.29 or higher.

Fastboot flashable: recovery-clockwork-6.0.1.5-touch-blade-Snap.IT-testing.img
MD5: 076f9671339b0d3c2d825a4e0311d209

Flashable via recovery: recovery-clockwork-6.0.1.5-touch-blade-Snap.IT-testing.zip
MD5: 5719f10a32040e5f5451be117bbd3a83

Edited by Snap.IT, 18 October 2012 - 08:15 PM.

[mitchde]

Snap.IT, on 16 October 2012 - 11:30 PM, said:

Testing version 6.0.1.5:

I've tested everything on it without any hickups, problems with previous versions (6.0.1.2 6.0.1.3 6.0.1.4) backup and sometimes hangups is solved in this one.

It includes a new menu item named "install zip from sideload" which can be used for installing a zip from your computer using "adb sideload 'path/to/zip'". It requires a newer adb, version 1.0.29 or higher.

Fastboot flashable: recovery-clockwork-6.0.1.5-touch-blade-Snap.IT-testing.img
MD5: 076f9671339b0d3c2d825a4e0311d209

Flashable via recovery: recovery-clockwork-6.0.1.5-touch-blade-Snap.IT-testing.zip
MD5: 5719f10a32040e5f5451be117bbd3a83

MANY THANKS for dev updates of that great backup/restore tool!
Installed and tested (after longer use of V 1.1).
Backup process runs and backuped.  without problems.
Difference to V11:
No comment about backuping sdext ?! All versions before also backuped (and restored) my sdext (Apps there).
No MD5 checksum comment at end of backup.
No backup advance graphics /infos (shows how far the backup is) - no problem if missed - speeds up backup
I reinstalled V11 and made again backup to check if sd-ext get backuped or it would also not backup - but sd-ext got backuped well.

The sd-ext backup/restore is really needful and amazing - after an full wipe i went back to exact same rom state (with all LINk2SD apps) after an resore with V11.
I would miss sd-ext backup/restore in future.
Or does no comment about sd-ext backup doesnt mean it wasnt backuped?

Edited by mitchde, 17 October 2012 - 10:21 AM.

[Snap.IT]

mitchde, on 17 October 2012 - 10:02 AM, said:

MANY THANKS for dev updates of that great backup/restore tool!
Installed and tested (after longer use of V 1.1).
Backup process runs and backuped.  without problems.
Difference to V11:
No comment about backuping sdext ?! All versions before also backuped (and restored) my sdext (Apps there).
No MD5 checksum comment at end of backup.
No backup advance graphics /infos (shows how far the backup is) - no problem if missed - speeds up backup
I reinstalled V11 and made again backup to check if sd-ext get backuped or it would also not backup - but sd-ext got backuped well.

The sd-ext backup/restore is really needful and amazing - after an full wipe i went back to exact same rom state (with all LINk2SD apps) after an resore with V11.
I would miss sd-ext backup/restore in future.
Or does no comment about sd-ext backup doesnt mean it wasnt backuped?

I'll look into it when i get home and get back to you in this thread.

[sej7278]

sd-ext (ext4) backup isn't working for me with 6.0.1.5 testing, it was with 6.0.1.2 testing, actually it seems to get through data then start .android_secure and crashes

going back to 6.0.1.2 testing works.

Edited by sej7278, 18 October 2012 - 07:45 AM.

[sej7278]

mitchde, on 17 October 2012 - 10:02 AM, said:

No MD5 checksum comment at end of backup.
No backup advance graphics /infos (shows how far the backup is) - no problem if missed - speeds up backup
I reinstalled V11 and made again backup to check if sd-ext get backuped or it would also not backup - but sd-ext got backuped well.

if you had no md5sum or sdext backup then i suspect yours is crashing at the same point as mine (after data) meaning the backup isn't finished, it just doesn't error. do you have .android_secure or cache?