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
Hi, I was using cyanogenmod 10.1 with encryption. After I updated to 10.2 nigthly build, the camera app says that could not access storage, f-droid stopped to work and every other app had the same problem.
I read a lot of topics here and did this:
- Flashed new CMW,
- Flashed new rom (cm 10.1, android 4.2.1);
- Tried other sd card;
- In CMW tried to mount & format emmc (error)
It still doesn't recognize my internal sd. And now I don't know what to do... :crying:
Here's my fstab
Code:
[email protected]:/ # cat fstab.smdk4210
cat fstab.smdk4210
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:11,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
/devices/platform/s3c_otghcd/usb /storage/usbdisk0 auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p11 /emmc auto defaults recoveryonly
/dev/block/mmcblk1p1 /sdcard auto defaults recoveryonly
Code:
[email protected]:/ # cat fstab.goldfish
cat fstab.goldfish
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/devices/platform/goldfish_mmc.0 /storage/sdcard vfat defaults voldmanaged=sdcard:auto
[email protected]:/ #
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 395.3M 48.0K 395.2M 4096
/storage 395.3M 0.0K 395.3M 4096
/mnt/secure 395.3M 0.0K 395.3M 4096
/mnt/asec 395.3M 0.0K 395.3M 4096
/mnt/obb 395.3M 0.0K 395.3M 4096
/mnt/fuse 395.3M 0.0K 395.3M 4096
/system 503.9M 287.4M 216.5M 4096
/cache 98.4M 53.5M 44.9M 4096
/efs 19.7M 8.2M 11.5M 4096
/data 2.0G 41.6M 1.9G 4096
/preload 503.9M 8.4M 495.6M 4096
/storage/sdcard1 14.6G 1.2G 13.4G 8192
Hi,
I had an encrypted I9100 on Cyanogenmod 9. After a factory reset I installed Cyanogemod 10.1. Everything runs smoothly, but about 12gb of my internal sd space was misplaced during the installation and is now missing. Only 2 gb is currently available. /sdcard cannot be mounted, something about /sdcard/android_secure
I ran some commands in adb, and the space is still there, but it needs to be replaced / repartitioned somehow, and I have no idea how to do so.
Would anyone happen to know a way to redeem this space?
Thanks.
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 395.6M 48.0K 395.6M 0% /dev
/dev/block/mmcblk0p7 98.4M 87.0M 11.4M 88% /cache
~ # mount /data
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 395.6M 48.0K 395.6M 0% /dev
/dev/block/mmcblk0p7 98.4M 87.0M 11.4M 88% /cache
/dev/block/mmcblk0p10
2.0G 366.4M 1.6G 18% /data
du -hs *
4.0K NVM0
0 NVM1
4.0K NVM13
0 NVM2
84.0K NVM3
0 NVM5
0 NVM6
115.9M app
44.8M app-asec
50.4M app-lib
4.0K app-private
20.0K backup
44.3M dalvik-cache
73.4M data
8.0K data-private
4.0K dontpanic
20.0K drm
4.0K gps
32.0K local
4.0K log
4.0K lost+found
12.0K media
132.0K misc
24.0K property
4.0K pxtmpdir
4.0K radio
4.0K resource-cache
4.0K security
8.0K ssh
2.2M system
4.0K user
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 102400 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 2097152 mmcblk0p10
259 3 12066816 mmcblk0p11
259 4 524288 mmcblk0p12
179 8 1985024 mmcblk1
179 9 1983619 mmcblk1p1
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/efs ext4 /dev/block/mmcblk0p1
/cache ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p10
/preload ext4 /dev/block/mmcblk0p12
/emmc auto /dev/block/mmcblk0p11
/sdcard auto /dev/block/mmcblk1p1 /dev/block/mmcblk1
mount /sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
/data # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr
,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,relatime,user_xattr,barrier=1,data=
ordered)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)
Test to Format the System, data and cach in cwm and flash them ur cm again. No nandroid,. Complete new
Gesendet von meinem Xperia SP
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
joke19 said:
Test to Format the System, data and cache in cwm and flash then ur cm again. No nandroid,. Complete new
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
Gesendet von meinem Xperia SP
Thanks for answering joke19. Unfortunately, it doesn't work. I've tried factory reset in clockworkmod, as well as folder by folder format. I've also tried to install different version of cyanogenmod 10. All works well, but the space is still missing
Problem solved! Thanks for the help. Solution was to re-partition using the stock .pit file in Odin.
I'm getting this error while doing mka -j8 bacon:
Code:
File "/home/tanujboy/android/cyanogenmod-12.1/build/tools/releasetools/common.py", line 259, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/dev/block/mmcblk0p22 /system ext4"
build/core/Makefile:1498: recipe for target '/home/tanujboy/android/cyanogenmod-12.1/out/target/product/black/obj/PACKAGING/target_files_intermediates/cm_black-target_files-5fb2ce1c7f.zip' failed
make: *** [/home/tanujboy/android/cyanogenmod-12.1/out/target/product/black/obj/PACKAGING/target_files_intermediates/cm_black-target_files-5fb2ce1c7f.zip] Error 1
make: Leaving directory '/home/tanujboy/android/cyanogenmod-12.1'
Can someone help me out and tell me how to fix this?
This is my recovery.fstab BTW:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4
/dev/block/mmcblk0p29 /data ext4
/dev/block/mmcblk0p23 /cache ext4
/dev/block/mmcblk0p24 /persist ext4
/dev/block/mmcblk0p20 /boot emmc
/dev/block/mmcblk0p21 /recovery emmc
/dev/block/mmcblk0p25 /misc emmc
/dev/block/mmcblk1p1 /dev/block/mmcblk1 /external_sd vfat flags=display="Micro SDcard";storage;wipeingui;removable
/dev/block/sda1 /dev/block/sda /usb-otg vfat flags=removable;storage;display=USB-OTG
See this: https://github.com/CyanogenMod/android_build/blob/cm-12.1/tools/releasetools/common.py#L222
Try this:
Code:
/dev/block/mmcblk0p22 /system ext4 ro,barrier=1