partitions of sony tablet s - Sony Tablet S

note:this is a study log,i'am not sure if blow is all right:cyclops:
Code:
major minor #blocks dev format name mount note
179 1 2048 mmcblk0p1 ext2 CF /configs
179 2 393216 mmcblk0p2 ext4 A0 /system system.img flash here
179 3 393216 mmcblk0p3 ext4 A1 /system backup system?
179 4 524288 mmcblk0p4 ext4 CC /cache
179 5 2048 mmcblk0p5 ???? MC /misc can't mount
179 6 49152 mmcblk0p6 ???? UP /staging hidden.img flash here
179 7 1024 mmcblk0p7 ???? BF /blflags can't mount
179 8 393216 mmcblk0p8 ext4 DP /datapp manel mount
179 9 16384 mmcblk0p9 ext4 LG /log
179 10 4194304 mmcblk0p10 ext4 UA /data
179 11 9368576 mmcblk0p11 vfat SC /sdcard
here mmcblk0 is first mmc-block device,that is inner storage
mmcblk0p1 is first partition of mmcblk0
block size is 1 KB,so block count 2048 means size is 2MB
there are 2 system partition(p2,p3),p2 is main system partition,if something wrong with p2,system will use p3 for backup.
my tablet first boot will stop at sony logo(use p2),2nd boot will ok(use p3)
if i flash ics,it will flash to p2,and can't use in forst boot,but after wipe,it will back to 3.2.1 again,then next boot to ics....
??system rember what system used in blflag(p7)+0xC.
(in updater-script read_index("/blflags") and code in update-binary)
if the byte is 0,use p2,else use p3,my is 1
content of p7:all zero but 0x03C -- 0x1FB is 0xFF,and
Code:
0x0C:1
0x14:1
0x1fC:0xD2A7AA14
0x1000:BL_VERSION_INFO\0
0x1010:_BL\0 0x00000008
0x1020:_RM\0 0x0000001E
0x1030:_LX\0 0x07334EFF
0x1040:_E1\0 0x00000009
a wipe data will format partition:
data,cache,log,staging
when flash rom,system.img flash to p2 or p3,hidden.img flash to p6
condi's double flash roms flash both to p2 and p3
some cmd:
get partion list
Code:
cat /proc/partitions
p3,p6,p8 is only use in update-script,but you can mout it by cmd
Code:
mount -t ext4 /dev/block/mmcblk0p3 /dir-name
p5,p7,format is unknow,mount fail,but you can dump it's data by cmd
Code:
cat /dev/block/mmcblk0p3 /some-name.bin
or
Code:
dd if=/dev/block/mmcblk0p3 of=/some-name.bin
in theory,you can restore partition by dd cmd,but it's very dangers!
you can check what system you use by cmd mount
Code:
# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[COLOR="Red"]/dev/block/mmcblk0p3 /system ext4 rw,relatime,barrier=1,data=ordered 0 0[/COLOR]
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0
0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatim
e,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remoun
t-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-
ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=rem
ount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
View attachment partitions.7z

---

Have anyone treis to flip this blaflags partition flag which tells which partition to reboot from? It could allow more versatile flashing...

---

According to Chainfire's floating performance monitor application the Disk I/O is mmcblk0.
Sent from my Nexus 4 using xda app-developers app

---

Where is the kernel? In the system partition, because i can´t see a boot partition in your list...

---

Partitionator said:
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Click to expand...
Click to collapse
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery

---

lopezk38 said:
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
Click to expand...
Click to collapse
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..

---

;45311156 said:
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
Click to expand...
Click to collapse
Robin, we need you to join the Sony Tablet Bootloader Discussion on Google Hangouts, can you PM me with your email with the subject "STBD"?
Sent from my Nexus 4 using Tapatalk 4