[Galaxy S II Android Development] Troubadour666:
about android secure files in nandroid restore

Hi [MENTION=2376110]dorimanx[/MENTION],

i hope this "streamlined" last_log from my last recovery restore can help you to check trouble.

Blue lines are lines i cut

Red lines are the top and bottom of log

[COLOR="Red"]Starting recovery on Wed Sep 4 23:30:37 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.1.2-Siyah
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /emmc vfat /dev/block/mmcblk0p11 (null) 0
8 /sdcard auto /dev/block/mmcblk1p1 (null) 0
9 /secondrom_cache ext4 /mnt/.secondrom/.secondrom/cache.img (null) 104857600
10 /secondrom_data ext4 /mnt/.secondrom/.secondrom/data.img (null) 2147483648
11 /secondrom_system ext4 /dev/block/mmcblk0p12 (null) 0[/COLOR]

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"

ro.boot.serialno=0019cd7b0c308e
ro.serialno=0019cd7b0c308e
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=smdk4210
ro.revision=14
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1
init.svc.ueventd=running
ro.build.product=GT-I9100
ro.product.device=GT-I9100
init.svc.recovery=running
init.svc.adbd=restarting
service.adb.root=1

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
umount: can't umount /data: Invalid argument
umount: can't umount /system: Invalid argument
umount: can't umount /secondrom_system: Invalid argument
umount: can't umount /secondrom_data: Invalid argument
Checking MD5 sums...
boot.img: OK
cache.ext4.tar: OK
cache.ext4.tar.a: OK
data.ext4.tar: OK
data.ext4.tar.a: OK
data.ext4.tar.b: OK
recovery.img: OK
system.ext4.tar: OK
system.ext4.tar.a: OK
.android_secure.vfat.tar: OK
.android_secure.vfat.tar.a: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/NEATROMV49-2013-09-02.13.00.11//system.ext4.tar
Restoring system...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
.
.
[COLOR="Blue"]ALL FILES WERE LISTED HERE AND RESTORED[/COLOR]
.
.
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/NEATROMV49-2013-09-02.13.00.11//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
.
.

[COLOR="Blue"]ALL FILES WERE LISTED HERE AND RESTORED[/COLOR]
.
.

[COLOR="Red"]couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/NEATROMV49-2013-09-02.13.00.11//.android_secure.vfat.tar
Restoring .android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
mount: can't find /sdcard/.android_secure in /etc/fstab
Can't mount /sdcard/.android_secure!
umount: can't umount /data: Invalid argument
umount: can't umount /system: Invalid argument
umount: can't umount /secondrom_system: Invalid argument
umount: can't umount /secondrom_data: Invalid argument[/COLOR]

nandroid.md5 content :

87199e7f39e08d61bd32be9817d1b15e boot.img
d41d8cd98f00b204e9800998ecf8427e cache.ext4.tar
152f3fd25ad5f241e6d108e20b4072a3 cache.ext4.tar.a
d41d8cd98f00b204e9800998ecf8427e data.ext4.tar
ecda34bcf3b6e30b3888be2b1d32748f data.ext4.tar.a
2c8f3a0be932f9fca93e87d6388b93c1 data.ext4.tar.b
782bb145d389052c1d9b7a593357b2bb recovery.img
d41d8cd98f00b204e9800998ecf8427e system.ext4.tar
04ee9a9a745f325918b0772d1a989bd4 system.ext4.tar.a
d41d8cd98f00b204e9800998ecf8427e .android_secure.vfat.tar
dd6a3464f1f9cb0d37122d227afa8332 .android_secure.vfat.tar.a

Boot, system and data img and tar are well restored (fortunaly i like to say), but cache, recovery and .android_secure.vfat.tar never been restored since 8.35 and it's finaly not a pb , because it's better to have such a clean dalvik cache at 1rst boot ;)

I dont know if the loose recovery.img restoration is important in my case because my I9100 life is always powered by your kernel :)

i remember a post from you some days ago

http://xdaforums.com/showpost.php?p=44589643&postcount=25358

and as i always ear to you, i put this little trouble a side , and anw i use your kernel 8.38 , 8.39 and now 8.40 and all is fine here.

thanks