1) I enabled true dual boot, but from system1 i can still see folders of apps which i have installed in system2 and viceversa (photos for example are mixed in the same folder) Is it normal ? I think data partitions should be completely separated...
You're mixing meanings. "data" usually refers to a partition mounted as /data. On this partitition, the user apps are stored (together with their settings) and this partition is not usually accessible to a user (unless with escalated privileges).
"sdcard" or "internal storage" is what you probably refer to and yes, this partition is shared between the two systems. It usually works fine (I guess majority of users would want to have their photos and music collection just once on the sdcard, wouldn't they?), in other cases it is worse:
- e.g. some apps store some of their user data on the sdcard, too - e.g. TitaniumBackup, podcasts apps, and lot of others. Usually, this is not a problem since I use the same apps from both systems.
- Apps 2 SD move some of the apps to the sdcard (are these those asec containers?): this might be a problem, because it is like sharing /data partition between the two systems: better avoid it.
Hence, you have to be a bit carefull and better not use different versions of apps in the two systems simultaneously.
2) Nandroid backup is separated for partition1 and partition2 or does it contains both the partitions ?
The former is true. You can restore any backup to any system, they are not specifically marked as "System1" or "System2".
3) There is a way to backup and restore also the recovery ?
CWM does not backup many partitions, recovery seems to be included though.
This is the list of partitions:
Code:
$ adb shell cat /proc/partitions
major minor #blocks name by-name
179 0 30535680 mmcblk0
179 1 87040 mmcblk0p1 modem
179 2 87040 mmcblk0p2 modem1
179 3 512 mmcblk0p3 sbl1
179 4 512 mmcblk0p4 sbl2
179 5 1024 mmcblk0p5 sbl3
179 6 1024 mmcblk0p6 rpm
179 7 1024 mmcblk0p7 tz
179 8 512 mmcblk0p8 DDR
179 9 4096 mmcblk0p9 aboot
179 10 1024 mmcblk0p10 misc
179 11 2920 mmcblk0p11 logo
179 12 780 mmcblk0p12 m9kefs1
179 13 780 mmcblk0p13 m9kefs2
179 14 1 mmcblk0p14 m9kefsc
179 15 8302 mmcblk0p15 bk1
179 16 780 mmcblk0p16 m9kefs3
179 17 64756 mmcblk0p17 bk2
179 18 15360 mmcblk0p18 boot
179 19 15360 mmcblk0p19 boot1
179 20 15360 mmcblk0p20 recovery
179 21 11264 mmcblk0p21 bk3
179 22 8192 mmcblk0p22 persist
179 23 524288 mmcblk0p23 system
179 24 524288 mmcblk0p24 system1
179 25 393216 mmcblk0p25 cache
179 26 3670016 mmcblk0p26 userdata
179 27 25096175 mmcblk0p27 storage
And this is what the files in sdcard/clockworkmod backup directory are:
Code:
boot.img
cache.ext4.tar.gz
cache.ext4.tar.gz.a
data.ext4.tar.gz
data.ext4.tar.gz.a
recovery.img
system.ext4.tar.gz
system.ext4.tar.gz.a
.android_secure.ext4.tar.gz
.android_secure.ext4.tar.gz.a
Some ROMS (MIUI, WIUI) flash also the contents of "modem" (and possibly other partititions like "boot"), while some other (CM11) do not. Thus you need to think a bit what CWM can restore and what not.
Regarding recovery backup & restore: you can do pretty much the same by flashing the recovery zip again (the few user settings are stored in "sdcard"/clockworkmod/.* files anyway).