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 have a sony tablet s and it froozed in google chrome and never came back to life.
It's stuck in sony logo. I have the most recent firmware installed with condi tool with root.
Here's my recovery log:
Starting recovery on Sun May 18 01:09:57 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 01:43:14 JST 2012
ro.build.date.utc=1333989794
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build6
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_002
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=SYS_002-user 4.0.3 TISU0077 120410009 test-keys
ro.build.fingerprint=Sony/SYS_002/nbx03:4.0.3/TISU0077/120410009:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
drm.service.enabled=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx03_011-ota-121116066.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 121116066
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Starting recovery on Sun May 18 01:10:52 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
My region is Portugal, and i tried many firmware files out here, but in recovery none of them are installed.
Anyone has a clue what to do?
Thanks
:good:
Oi! Tens o firmwire de origem mas o honeycomb para a nossa maquina?pode resolver...nao encontro isso em lado nenhum e ja foi retirado dos servidores da sony
Sent from my ALCATEL ONE TOUCH 997D using XDA Free mobile app
This is odd: switched phone on this morning and it was stuck at the boot logo. I did a bit of digging around and it looks like the internal memory is corrupt because it is refusing to mount /data or /system.
I am ok doing a kies or odin recovery but before i do it would be nice (not essential) to recover some data. I can get into download and recovery and have tried to mount them manually but it didn't work.
Before I go for the full reset, an ideas on mounting /data?
cheers
m
ps. "boot" not "boo"!
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
ls /dev/block
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
cat fstab
/dev/block/mmcblk0p3 /efs ext4 rw
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p10 /preload ext4 rw
/external_sd vfat rw
/usb-otg vfat rw
mount -a
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
mount: mounting /dev/block/mmcblk0p9 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount: mounting /external_sd on vfat failed: No such file or directory
mount: mounting /usb-otg on vfat failed: No such file or directory
mount -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
Try this: http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Already have plenty of emergency firmwares as per OP - just wondering if it's possible to mount the partitions some other way. However, no worries: gave up and just reloaded one using odin. worked fine.