TeamWin Recovery Project

[lerkin]

I have interesting situation with that recover:
First, I backed up only sd-ext (I have fat32 for link2sd), it backed up without any md5 errors.
After that I backed up system (without errors);
data (...Generating data md5...sh: cd: line 1: can't cd to ces.xml....Done....Verifying data md5...sh: cd: line 1: can't cd to ces.xml....MD5 Error: cd ces.xml && md5sum -c data.win.md5...)

android.secure (...Backing up .android_secure. tar: ./ces.xmland-sec.win: file is the archive; skipping....Done....Generating .android_secure md5...sh: cd: line 1: can't cd to ces.xml....Done....Verifying .android_secure md5...sh: cd: line 1: can't cd to ces.xml
....MD5 Error: cd ces.xml && md5sum -c and-sec.win.md5...Done.)

sd-ext (Generating sd-ext md5...sh: cd: line 1: can't cd to ces.xml....Done....Verifying sd-ext md5...sh: cd: line 1: can't cd to ces.xml....MD5 Error: cd ces.xml && md5sum -c sd-ext.win.md5...

Can provide the whole log.
Is where any solution?

have same md5 errors with ext4 second partition.
may it be because of link2sd incompatibility?

 

[dr.notor]

2011-08-21 v1.0.3.7
- Google backup now doesnt create 0kb files and works correctly

Yeah, all good now, LOL.

 

[Omnichron]

Can it be flashed over CWM?

 

[sweetnsour]

Can it be flashed over CWM?

http://forum.xda-developers.com/showpost.php?p=16663434&postcount=3

 

[dr.notor]

@kbzona: There really is something very broken with /data backup. I cannot back it up no matter what. All other partitions work just fine, /data always crashes on md5 creation and goes back to menu.

...Generating data md5...
sh: cd: line 1: can't cd to 08101EDF16C4E65D895AB45144A0E4D41.xml
....Done.
...Verifying data md5...
sh: cd: line 1: can't cd to 08101EDF16C4E65D895AB45144A0E4D41.xml
....MD5 Error: cd 08101EDF16C4E65D895AB45144A0E4D41.xml && md5sum -c data.win.md5
Starting recovery on Wed Aug 24 18:12:25 2011
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /boot mtd boot (null)
  2 /cache yaffs2 cache (null)
  3 /data yaffs2 userdata (null)
  4 /misc mtd misc (null)
  5 /recovery mtd recovery (null)
  6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
  7 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
  8 /system yaffs2 system (null)

I:Set boot command "boot-recovery"
Command: "/sbin/recovery"

...Generating data md5...
sh: cd: line 1: can't cd to 08101EDF16C4E65D895AB45144A0E4D41.xml
....Done.
...Verifying data md5...
sh: cd: line 1: can't cd to 08101EDF16C4E65D895AB45144A0E4D41.xml
....MD5 Error: cd 08101EDF16C4E65D895AB45144A0E4D41.xml && md5sum -c data.win.md5
Starting recovery on Wed Aug 24 18:23:28 2011
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /boot mtd boot (null)
  2 /cache yaffs2 cache (null)
  3 /data yaffs2 userdata (null)
  4 /misc mtd misc (null)
  5 /recovery mtd recovery (null)
  6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
  7 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
  8 /system yaffs2 system (null)

I:Set boot command "boot-recovery"
Command: "/sbin/recovery"

There was no such problem in previous versions (my last backup is 4 days old, worked without problems.

 

[Omnichron]

http://forum.xda-developers.com/showpost.php?p=16663434&postcount=3

Thanx! Being the adventurous type I went ahead and flashed it over the old rec. Works perfect!

 

[Omnichron]

How do I theme it? dl link for themes?

 

[dr.notor]

You choose a theme in settings menu. Do not download anything.

 

[kbzona]

@kbzona: There really is something very broken with /data backup. I cannot back it up no matter what. All other partitions work just fine, /data always crashes on md5 creation and goes back to menu.
There was no such problem in previous versions (my last backup is 4 days old, worked without problems.

Mmm, im having the same problem, tried to install an old version and even v1.0.3.1 cant backup anymore LOL....
This is very weird, maybe v1.0.3.7 screwed something that we are not seeing
Tried every version i've compiled and no go...
Well i'll need to investigate more thoroughly as soon as possible

ps: could you confirm that you have the same behaviour even in this older version

 

[jobankler]

will it work on the LG phoenix too?

 

[dr.notor]

Mmm, im having the same problem, tried to install an old version and even v1.0.3.1 cant backup anymore LOL....
This is very weird, maybe v1.0.3.7 screwed something that we are not seeing
Tried every version i've compiled and no go...
Well i'll need to investigate more thoroughly as soon as possible

ps: could you confirm that you have the same behaviour even in this older version

Tested with 1.0.3.5 and 1.0.3.2 - no dice. (Also, someone above reported the same with .android_secure).

I do not really understand WTH does it try to cd to some whackynonexistent.xml folder when doing md5sum?!

EDIT: I flashed AmonRa - no issue with /data backup, CWM 4.0.1.5 - also no issue with that. Also, the backup made via TWRP actually looks OK and complete, if you create the md5 manually, you can restore it just fine. WTF.

 

[kbzona]

Tested with 1.0.3.5 and 1.0.3.2 - no dice. (Also, someone above reported the same with .android_secure).

I do not really understand WTH does it try to cd to some whackynonexistent.xml folder when doing md5sum?!

EDIT: I flashed AmonRa - no issue with /data backup, CWM 4.0.1.5 - also no issue with that. Also, the backup made via TWRP actually looks OK and complete, if you create the md5 manually, you can restore it just fine. WTF.

Well problem solved, BTW, CWM and AmonRA handles md5 a little bit differently and ( perhaps in a more inefficient way) that why ti works... Anyway now its working it was a matter of a too long string thing...

*Download updated on the first page*

 

[ghost_141]

Well problem solved, BTW, CWM and AmonRA handles md5 a little bit differently and ( perhaps in a more inefficient way) that why ti works... Anyway now its working it was a matter of a too long string thing...

I installed TWRP-ThunderG-v1.0.3.8.zip, but the recovery menu appears TWRP-ThunderG-v1.0.3.7.

 

[DaXmax]

Well problem solved, BTW, CWM and AmonRA handles md5 a little bit differently and ( perhaps in a more inefficient way) that why ti works... Anyway now its working it was a matter of a too long string thing...

Receive ur pm earlier... Btw, actually i have no probs with dat... An again, u forgot to change the version number..

Sent from LGE Secret phone using tapatalk app... >DA×<

 

[dr.notor]

Well problem solved, BTW, CWM and AmonRA handles md5 a little bit differently and ( perhaps in a more inefficient way) that why ti works... Anyway now its working it was a matter of a too long string thing...

Yeah, works now.

 

[kbzona]

Receive ur pm earlier... Btw, actually i have no probs with dat... An again, u forgot to change the version number..

Sent from LGE Secret phone using tapatalk app... >DA×<

I installed TWRP-ThunderG-v1.0.3.8.zip, but the recovery menu appears TWRP-ThunderG-v1.0.3.7.

Ooops yeah sry forgot that, i'll change it as soon as i get home

 

[kbzona]

There you go!

2011-08-25 v1.0.3.8
- Now md5 generates correctly (no more backup md5 errors, specially for "data" backups!)
- More code cleaning
- changed version string to v1.0.3.8

Download:
---------------------

TWRP-ThunderG-v1.0.3.8.zip

 

[Jaani]

@kbzona
thanxxx for the porting..I just replaced CMW with this..its looking nice..the only thing i wish from this is that it do not screw the DT a2sd script when updating kernel(usually get hang on red LG logo) & sometimes when rebooted normally..can u add option am/pm in clock???

 

[dr.notor]

@kbzona
thanxxx for the porting..I just replaced CMW with this..its looking nice..the only thing i wish from this is that it do not screw the DT a2sd script when updating kernel(usually get hang on red LG logo)

I am afraid that has nothing do with kernel flashing or this recovery and everything to do with using the reboot recovery option in power menu resulting in unclean reboot and subsequent fsck. Simply do not use that.

 

[Bec de Xorbin]

Very nice, but seems quite slow compared to AmonRa.