Chinese MSM8916 Device, "Could not mount system partition" Error in TWRP - Android Q&A, Help & Troubleshooting

Could not mount system partition.
Hi All,
I need some help, I'm building my own TWRP for my own device. It's a Chinese custom phone running msm8916, 1GO Ram and 8Go of storage.
My TWRP boots fine, adb shell prompt me a nice root shell, I have no error in dmesg or recovery logs
yet when SuperSu or I try to mount the system partition as RW it doesn't work. It's always mounted as RO (I use plain mount command to check)
I tried a lots of command including
Code:
#mount -o remount,rw -t ext4 /dev/block/bootdevice/by-name/system /system
#mount -o remount,rw /system
Click to expand...
Click to collapse
I don't have the kernel source code and use a prebuilt kernel extracted from the bootimage.
You can find my code here : github com/supercairos/android_device_doro_hero
If you have any idea why this is happening I would be very glad!
Best,
R.

When looking a dmesg it outputs :
<6>[ 14.757619] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 14.757638] SELinux: initialized (dev mmcblk0p22, type ext4), uses xattr
<3>[ 16.049825] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
<3>[ 16.049946] mmcblk0: timed out sending r/w cmd command, card status 0x400d
00
<3>[ 16.049951] mmcblk0: command error, retrying timeout
<3>[ 21.069858] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
<3>[ 21.069916] mmcblk0: timed out sending r/w cmd command, card status 0x400d
00
<3>[ 21.069921] mmcblk0: command error, retrying timeout
<3>[ 21.070127] mmc0: cache flush timeout
<3>[ 21.070153] mmc0: mmc_interrupt_hpi() failed (-22)
<3>[ 21.070158] mmcblk0: mmc_blk_issue_flush: restart mmc card
<3>[ 21.097327] mmcblk0: mmc_blk_issue_flush: notify flush error to upper laye
rs<3>[ 21.097337] end_request: I/O error, dev mmcblk0, sector 407568
<3>[ 21.097356] Aborting journal on device mmcblk0p22-8.
<3>[ 21.107997] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
<3>[ 21.108062] mmcblk0: timed out sending r/w cmd command, card status 0x400d
00
<3>[ 21.108067] mmcblk0: command error, retrying timeout
<2>[ 21.108167] EXT4-fs error (device mmcblk0p22): __ext4_journal_start_sb:62:
Detected aborted journal
<2>[ 21.108175] EXT4-fs (mmcblk0p22): Remounting filesystem read-only
<3>[ 21.108228] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
<3>[ 21.108295] mmcblk0: timed out sending r/w cmd command, card status 0x400d
00
<3>[ 21.108300] mmcblk0: command error, retrying timeout
<3>[ 31.138023] mmc0:cache disable operation timeout
<3>[ 31.138059] mmc0: mmc_interrupt_hpi() failed (-22)
<3>[ 31.138074] mmc0: mmc_host_runtime_suspend: suspend host failed: -110
<3>[ 34.268118] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
<3>[ 34.268201] mmcblk0: timed out sending r/w cmd command, card status 0x400d
00
<3>[ 34.268207] mmcblk0: command error, retrying timeout
Click to expand...
Click to collapse

Related

[Q] Mounting 2nd SD Card Partition

So I have a 32gb SD card and formatted it into a primary 5gb FAT partition that will be used for usb mass storage mode, and a second ext4 partition which I intend to store google music caches onto aswell as the camera DCIM folder (through mounts/symlinks), however I can't get the ext4 partition to mount in a writable state. Using the latest version of Neutrino ROM, so I don't think ext4 is the problem (haven't tested with ext3 yet).
tried:
mount -w /dev/block/mmcblk1p2 /sdcard/sd-ext4
and it mounts (can see the lost+found dir), but it is only readable.
however, when I do
mount -w /dev/block/mmcblk1p1 /sdcard/sd-ext4
it mounts the first partition on the SD card in read/write mode just fine.
Anyone know what I'm doing wrong?
Don't use -w, try -orw instead. Also check the output of dmesg right after you mount or maybe right after you try a write operation, there might be something useful there.
ravilov said:
Don't use -w, try -orw instead. Also check the output of dmesg right after you mount or maybe right after you try a write operation, there might be something useful there.
Click to expand...
Click to collapse
Tried that, still no luck. Nothing blatently obvious to point to a problem (that I can see), asides from a couple buffer overflows.
This is console output of dmesg before and after mounting
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# busybox dmesg | tail -f
<6>[ 136.137609] usb_ether_get_stats
<6>[ 138.597649] usb_ether_get_stats
<6>[ 138.598851] usb_ether_get_stats
<4>[ 138.851818]
<4>[ 138.851822] nvmap_open: pid=3998
<4>[ 140.687584] nvmap_open: pid=1949
<3>[ 144.027654] init: untracked pid 4246 exited
<3>[ 145.635534] evdev: event6-1787: buffer overflow
<6>[ 169.390446] kxtf9_irq_work_func: status=0x4
<3>[ 176.685803] evdev: event6-1787: buffer overflow
# mount -orw /dev/block/mmcblk1p2 /sdcard/sd-ext4
# busybox dmesg | tail -f
<4>[ 140.687584] nvmap_open: pid=1949
<3>[ 144.027654] init: untracked pid 4246 exited
<3>[ 145.635534] evdev: event6-1787: buffer overflow
<6>[ 169.390446] kxtf9_irq_work_func: status=0x4
<3>[ 176.685803] evdev: event6-1787: buffer overflow
<6>[ 198.451536] usb_ether_get_stats
<3>[ 214.295793] evdev: event6-1787: buffer overflow
<4>[ 252.753904]
<4>[ 252.753908] nvmap_open: pid=2750
<6>[ 258.848399] usb_ether_get_stats
And this was after trying to create a file
Code:
# busybox dmesg | tail -20
<6>[ 138.597649] usb_ether_get_stats
<6>[ 138.598851] usb_ether_get_stats
<4>[ 138.851818]
<4>[ 138.851822] nvmap_open: pid=3998
<4>[ 140.687584] nvmap_open: pid=1949
<3>[ 144.027654] init: untracked pid 4246 exited
<3>[ 145.635534] evdev: event6-1787: buffer overflow
<6>[ 169.390446] kxtf9_irq_work_func: status=0x4
<3>[ 176.685803] evdev: event6-1787: buffer overflow
<6>[ 198.451536] usb_ether_get_stats
<3>[ 214.295793] evdev: event6-1787: buffer overflow
<4>[ 252.753904]
<4>[ 252.753908] nvmap_open: pid=2750
<6>[ 258.848399] usb_ether_get_stats
<3>[ 264.185782] evdev: event6-1787: buffer overflow
<6>[ 286.976907] lm3532_button_brightness_set: button-backlight, 0x3f (63)
<6>[ 286.978071] lm3532_brightness_set: lcd-backlight, 0x3c(60), webtop=0
<6>[ 286.995619] lm3532_brightness_set: lcd-backlight, 0x39(57), webtop=0
<6>[ 287.015674] lm3532_brightness_set: lcd-backlight, 0x36(54), webtop=0
<6>[ 287.035543] lm3532_brightness_set: lcd-backlight, 0x33(51), webtop=0
Edit: I had done a clean boot before I tried all that too, here is the dmesg output from boot up to just past that point (I don't have 10 posts yet so can't hotlink) pastebin com/5PbQ6UBf
Solved the problem by changing permissions on the folder

[Q] Devlog partition corrupt - can be removed?

Hi all,
a friends Desire X took an unfortunate swim in a washing machine. Since then, it will hang with a black screen with backlight on about four times a week, mostly when it isn't actively used. /proc/last_kmsg contains:
Code:
[ 5105.131426] C0 mmc0: Deferred resume completed
[ 5110.136727] C0 mmc0: Starting deferred resume
[ 5120.175589] C0 mmc0: CMD5: Request timeout
[ 5120.175777] C0 mmc0: SDCC PWR is ON
[ 5120.176006] C0 mmc0: SDCC clks are ON, MCLK rate=144000
[ 5120.176322] C0 mmc0: SDCC irq is enabled
[ 5120.176497] C0 ===== SDCC-CORE: Register Dumps @phys_base=0xa0600000, @virt_base=0xcf824000 =====
[ 5120.176821] C0 Reg=0x00: 0x00000001, 0x00009100, 0x00010000, 0x00000c45
[ 5120.177142] C0 Reg=0x10: 0x00000005, 0x00001500, 0x0f5903ff, 0xffffffe7
[ 5120.177326] C0 Reg=0x20: 0x8a4040e2, 0x039396a0, 0x00001000, 0x00022008
[ 5120.177646] C0 Reg=0x30: 0x00000000, 0x00000400, 0x00000000, 0x008001ff
[ 5120.177826] C0 Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 5120.178146] C0 Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 5120.178466] C0 Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 5120.178649] C0 mmc0: got_dataend=0, prog_enable=1, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
[ 5120.178981] C0 mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
[ 5120.179422] C0 mmc0: Controller has been reinitialized
[ 5121.371397] C0 mmc0: Deferred resume Fail
[ 5121.372651] C0 mmc0: DMA channel flushed (0x80000004)
[ 5121.372836] C0 Flush data: 0000c003 11720000 00000000 00400040 003f003d 00008003
[ 5121.373254] C0 mmc0: Controller has been reinitialized
[ 5121.380404] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.386454] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.392637] C0 mmcblk0: error -110 sending status command, aborting
[ 5121.392831] C0 end_request: I/O error, dev mmcblk0, sector 5253328
[ 5121.393159] C0 Buffer I/O error on device mmcblk0p28, logical block 5402
[ 5121.393369] C0 EXT4-fs warning (device mmcblk0p28): ext4_end_bio:258: I/O error writing to inode 19 (offset 368640 size 4096 starting block 656667)
[ 5121.393879] C0 JBD2: Detected IO errors while flushing file data on mmcblk0p28-8
[ 5121.395007] C0 mmc0: DMA channel flushed (0x80000004)
[ 5121.395331] C0 Flush data: 0000c003 11720000 00000000 00400040 003f003d 00008003
[ 5121.395602] C0 mmc0: Controller has been reinitialized
[ 5121.402749] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.408804] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.414984] C0 mmcblk0: error -110 sending status command, aborting
[ 5121.415177] C0 end_request: I/O error, dev mmcblk0, sector 5218184
[ 5121.415514] C0 end_request: I/O error, dev mmcblk0, sector 5218192
[ 5121.415992] C0 Aborting journal on device mmcblk0p28-8.
[ 5121.416417] C0 EXT4-fs error (device mmcblk0p28) in ext4_reserve_inode_write:5645: Journal has aborted
[ 5121.418139] C0 mmc0: DMA channel flushed (0x80000004)
[ 5121.418334] C0 Flush data: 0000c003 11720000 00000000 00400040 003f003d 00008003
[ 5121.418767] C0 mmc0: Controller has been reinitialized
[ 5121.425804] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.431986] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.438059] C0 mmcblk0: error -110 sending status command, aborting
[ 5121.438246] C0 end_request: I/O error, dev mmcblk0, sector 5210960
[ 5121.438571] C0 Buffer I/O error on device mmcblk0p28, logical block 106
[ 5121.438751] C0 lost page write due to I/O error on mmcblk0p28
[ 5121.439099] C0 JBD2: I/O error detected when updating journal superblock for mmcblk0p28-8.
[ 5121.440251] C0 mmc0: DMA channel flushed (0x80000004)
[ 5121.440571] C0 Flush data: 0000c003 11720000 00000000 00400040 003f003d 00008003
[ 5121.440989] C0 mmc0: Controller has been reinitialized
[ 5121.447992] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.454177] C0 mmcblk0: error -110 sending status command, retrying
[ 5121.460227] C0 mmcblk0: error -110 sending status command, aborting
[ 5121.460551] C0 end_request: I/O error, dev mmcblk0, sector 5210112
[ 5121.460734] C0 Buffer I/O error on device mmcblk0p28, logical block 0
[ 5121.461052] C0 lost page write due to I/O error on mmcblk0p28
[ 5121.461262] C0 EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[ 5121.461581] C0 ext4_e2fsck
[ 5121.465612] C0 ext4_reboot: reboot to run e2fsck
[ 5121.465796] C0 Take CPU down - Begin
[ 5121.466106] C0 Take CPU down - End
[ 5121.467227] C0 [BATT][tps65200] TPS65200 shutdown
[ 5121.473664] C0 Restarting system with command 'oem-22'.
[ 5121.473859] C0 [K] msm_pm_restart: restart_reason 0x6f656d22, cmd oem-22
[ 5121.474474] C0 [K] @@@@@@@@@@@ msm_proc_comm end
[ 5121.474659] C0 [K] from msm_pm_restart
[ 5122.621554] C0 [RMT] rmt_storage_event_write_iovec_cb: write iovec callback received
[ 5122.622382] C0 [RMT] handle = 1
[ 5122.622822] C0 [RMT] sec_addr = 0, data_addr = 300000, num_sec = 6143
[ 5122.623612] C0 [RMT] sec_addr = 6143, data_addr = 5ffe00, num_sec = 1
[ 5122.624066] C0 [RMT] iovec transfer count = 2
[ 5122.624089] C0
[ 5122.625316] C0 [RMT] rmt_storage_ioctl: ioctl cmd -2140093951 return value 0
[ 5122.626584] C0 [RMT] rmt_storage_ioctl: wait for request ioctl
[ 5122.640087] C0 [RMT] handle_rmt_storage_call: Sending result=0x0
[ 5122.839952] C0 mmc0: DMA channel flushed (0x80000004)
[ 5122.840149] C0 Flush data: 0000c003 11720000 00000000 00400040 003f003d 00008003
[ 5122.840561] C0 mmc0: Controller has been reinitialized
[ 5122.848189] C0 mmcblk0: error -110 sending status command, retrying
[ 5122.854384] C0 mmcblk0: error -110 sending status command, retrying
[ 5122.860802] C0 mmcblk0: error -110 sending status command, aborting
[ 5122.861214] C0 end_request: I/O error, dev mmcblk0, sector 131073
[ 5122.861404] C0 Buffer I/O error on device mmcblk0p13, logical block 0
[ 5122.861724] C0 lost page write due to I/O error on mmcblk0p13
[ 5122.861972] C0 end_request: I/O error, dev mmcblk0, sector 131081
So it seems it gets an I/O error while writing to /dev/mmcblk0p28, which is devlog, AFAICT the internal logfile HTC uses for service requests. It then wants to reboot but crashes during reboot because the eMMC isn't responding at all anymore.
Now my question: Would it be possible to remove the devlog mount? I haven't tried yet since this might lead to a bootloop, and I wanted to ask here for experiences first. Any hints greatly appreciated, also maybe other approaches than removing devlog?

Random reboots caused by SD card I/O problems

My phone keeps randomly restarting for the last three months with ROM Slimbean 0.1 flashed. Usually the phone restarts, when the display is off, but sometimes it restarts out of blue.
After getting the kmsg log, found out, that it might be related with the SD card. The SD card itself is ok, verified with scandisk & the socket seems to be ok, as it always properly mounts after reboot.
Code:
[ 2230.608158] C0 mmc0: Controller has been reinitialized
[ 2230.615133] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.621089] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.627128] C0 mmcblk0: error -110 sending status command, aborting
[ 2230.627249] C0 end_request: I/O error, dev mmcblk0, sector 5250040
[ 2230.627456] C0 Buffer I/O error on device mmcblk0p28, logical block 4991
[ 2230.627593] C0 EXT4-fs warning (device mmcblk0p28): ext4_end_bio:258: I/O error writing to inode 30 (offset 258048 size 4096 starting block 656256)
[ 2230.628796] C0 mmc0: DMA channel flushed (0x80000004)
[ 2230.628909] C0 Flush data: 0000c003 11620000 00000000 00400040 003f003d 00008003
[ 2230.629176] C0 mmc0: Controller has been reinitialized
[ 2230.636071] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.642109] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.648058] C0 mmcblk0: error -110 sending status command, aborting
[ 2230.648266] C0 end_request: I/O error, dev mmcblk0, sector 5214360
[ 2230.648383] C0 end_request: I/O error, dev mmcblk0, sector 5214368
[ 2230.648621] C0 Aborting journal on device mmcblk0p28-8.
[ 2230.648794] C0 EXT4-fs error (device mmcblk0p28) in ext4_reserve_inode_write:5645: Journal has aborted
[ 2230.649924] C0 mmc0: DMA channel flushed (0x80000004)
[ 2230.650123] C0 Flush data: 0000c003 11620000 00000000 00400040 00400040 00000003
[ 2230.650321] C0 mmc0: Controller has been reinitialized
[ 2230.657301] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.663256] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.669294] C0 mmcblk0: error -110 sending status command, aborting
[ 2230.669411] C0 end_request: I/O error, dev mmcblk0, sector 728920
[ 2230.670531] C0 mmc0: DMA channel flushed (0x80000004)
[ 2230.670646] C0 Flush data: 0000c003 11620000 00000000 00400040 003f003d 00008003
[ 2230.670919] C0 mmc0: Controller has been reinitialized
[ 2230.677891] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.683848] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.689886] C0 mmcblk0: error -110 sending status command, aborting
[ 2230.689999] C0 end_request: I/O error, dev mmcblk0, sector 5210960
[ 2230.690199] C0 Buffer I/O error on device mmcblk0p28, logical block 106
[ 2230.690309] C0 lost page write due to I/O error on mmcblk0p28
[ 2230.690571] C0 JBD2: I/O error detected when updating journal superblock for mmcblk0p28-8.
[ 2230.692661] C0 mmc0: DMA channel flushed (0x80000004)
[ 2230.692886] C0 Flush data: 0000c003 11620000 00000000 00400040 003f003d 00008003
[ 2230.693361] C0 mmc0: Controller has been reinitialized
[ 2230.700399] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.706699] C0 mmcblk0: error -110 sending status command, retrying
[ 2230.712823] C0 mmcblk0: error -110 sending status command, aborting
[ 2230.713211] C0 end_request: I/O error, dev mmcblk0, sector 5210112
[ 2230.713431] C0 Buffer I/O error on device mmcblk0p28, logical block 0
[ 2230.713811] C0 lost page write due to I/O error on mmcblk0p28
[ 2230.714074] C0 EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[ 2230.714454] C0 ext4_e2fsck
[ 2230.715753] C0 mmc0: DMA channel flushed (0x80000004)
[ 2230.716143] C0 Flush data: 0000c003 11620000 00000000 00400040 003f003d 00008003
[ 2230.716459] C0 mmc0: Controller has been reinitialized
[ 2230.720488] C0 ext4_reboot: reboot to run e2fsck
[ 2230.720704] C0 Take CPU down - Begin
[ 2230.720914] C0 Take CPU down - End
[ 2230.722351] C0 [BATT][tps65200] TPS65200 shutdown
[ 2230.722848] C0 journal commit I/O error
[ 2230.724989] C0 Restarting system with command 'oem-22'.
I have Link2sd installed, most of my apps are linked to the second partition of the SD card.
Ist it always the same sector?
As an sd-card is extremely cheap, I would replace it to try it.
With scandisk you mean the crappy windows tool?
David.

Galaxy S3: Recovery error (E:Can't mount )

Internal storage corrupted?
Hello everyone! A few days ago I'm having problems with my phone.
Symptoms:
-Samsung stuck screen
-Recovery error (E:Can't mount )
-Mount error (/efs /system/cache/preload/data)
-Odin error (install new rom/pit/recovery)
-Download mode works very well (I think)
Explanation:
*Recovery Philz Touch 6
*External SD Card 32GB
Well I'm trying to solve this problem with the console adb, but to try to see these partitions only show me external sd card
adb shell
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30375936 mmcblk0
179 1 30374912 mmcblk0p1
Click to expand...
Click to collapse
~ # mount
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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/vold/179:1 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Click to expand...
Click to collapse
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 1.725478] c1 mmc0: Version ID 0x5342240a.
<6>[ 1.725728] c1 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 1.727225] c1 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 1.755861] c0 mmc0: cmd 52 response timeout error
<3>[ 1.756711] c0 mmc0: cmd 52 response timeout error
<3>[ 1.760759] c0 mmc0: cmd 8 response timeout error
<3>[ 1.761602] c0 mmc0: cmd 5 response timeout error
<3>[ 1.762431] c0 mmc0: cmd 5 response timeout error
<3>[ 1.763257] c0 mmc0: cmd 5 response timeout error
<3>[ 1.764083] c0 mmc0: cmd 5 response timeout error
<3>[ 1.764926] c0 mmc0: cmd 55 response timeout error
<3>[ 1.765768] c0 mmc0: cmd 55 response timeout error
<3>[ 1.766612] c0 mmc0: cmd 55 response timeout error
<3>[ 1.767454] c0 mmc0: cmd 55 response timeout error
<3>[ 1.786755] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 1.786787] c0 mmc0: VTU00M: 15010056545530304df730a53e52cfbd
<3>[ 1.834347] c0 mmc0: cmd 13 response timeout error
<6>[ 1.836295] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 1.837138] c0 mmc0: cmd 6 response timeout error
<3>[ 1.839016] c0 mmc0: cmd 6 response timeout error
<3>[ 1.840899] c0 mmc0: cmd 6 response timeout error
<3>[ 1.842767] c0 mmc0: cmd 6 response timeout error
<3>[ 1.845048] c1 mmc0: error -110 whilst initialising MMC card
Click to expand...
Click to collapse
From the download mode shows me the following
ODIN MODE
PRODUCT NAME: GT-I900
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Click to expand...
Click to collapse
Any idea? already tried many things and nothing works...
I am trying to install the ROM on the external SD card now, I think the internal memory is damaged.
In recovery mod 32GB sd cards not working and after the recovery cant reach the sd card.

Dead embedded MMC ? Can I recover some of the data ?

Hello,
my i9300 has been rebooting strangely in the past days, and this morning was stuck in boot loop. Unfortunately I didn't get to backup the last pictures I took. I am trying to find a way to get access to the data it might still hold.
I can enter recovery mode (works but sometimes requires several attemps). Once there it cannot read system partitions (and thus can't wipe cache).
I tried to remove battery / sdcard, hold power button for a long time, hold it with home + up as well
More info:
* kernel has some issues to access the root system
Code:
$ dmesg | grep mmc
<5>[ 0.000000] c0 Kernel command line: console=ram loglevel=4 bootmode=2 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] s3cfb.bootloaderfb=0x5ec00000 sysscope=0xff000000 lcdtype=96 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=144m oops=panic pmic_info=65 cordon=80682fa972fd0742b08c3ec03dbe74be connie=GT-I9300_OPEN_EUR_ca5a0240c80b887511e34b14c9d00c16 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=I9300XXUGND5 androidboot.serialno=4df1dd821ee57fd9 snd_soc_core.pmdown_time=1000
<6>[ 1.741101] c2 dw_mmc dw_mmc: clock source 0: sclk_dwmci (40000000 Hz)
<3>[ 1.741379] c2 mmc0: Version ID 0x5342240a.
<6>[ 1.741630] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 1.742124] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<6>[ 1.742616] c2 s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (88888888 Hz)
<6>[ 1.742906] c2 mmc1: vtf_2.8v regulator found
<3>[ 1.770850] c0 mmc0: cmd 52 response timeout error
<3>[ 1.771702] c0 mmc0: cmd 52 response timeout error
<3>[ 1.775742] c0 mmc0: cmd 8 response timeout error
<3>[ 1.776591] c0 mmc0: cmd 5 response timeout error
<3>[ 1.777420] c0 mmc0: cmd 5 response timeout error
<3>[ 1.778246] c0 mmc0: cmd 5 response timeout error
<3>[ 1.779073] c0 mmc0: cmd 5 response timeout error
<3>[ 1.779920] c0 mmc0: cmd 55 response timeout error
<3>[ 1.780767] c0 mmc0: cmd 55 response timeout error
<3>[ 1.781613] c0 mmc0: cmd 55 response timeout error
<3>[ 1.782463] c0 mmc0: cmd 55 response timeout error
<3>[ 1.801773] c1 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 1.801805] c1 mmc0: VTU00M: 15010056545530304df1dd821ee57fd9
<7>[ 1.848333] c0 Registered led device: mmc1::
<6>[ 1.848801] c0 mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 1.849085] c0 mmc1: card inserted.
<6>[ 1.849225] c0 s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (8888888 Hz)
<3>[ 1.849340] c0 mmc2: no vmmc regulator found
<7>[ 1.849600] c0 Registered led device: mmc2::
<6>[ 1.849898] c0 mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 1.883922] c0 mmc0: cmd 13 response timeout error
<6>[ 1.885069] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 1.885909] c0 mmc0: cmd 6 response timeout error
<3>[ 1.887775] c0 mmc0: cmd 6 response timeout error
<3>[ 1.889637] c0 mmc0: cmd 6 response timeout error
<3>[ 1.891500] c0 mmc0: cmd 6 response timeout error
<3>[ 1.892612] c0 mmc0: error -110 whilst initialising MMC card
<6>[ 1.920360] c0 mmc1: cmd 52 command timeout error
<6>[ 1.920726] c0 mmc1: cmd 52 command timeout error
<6>[ 1.924597] c0 mmc1: cmd 5 command timeout error
<6>[ 1.924932] c0 mmc1: cmd 5 command timeout error
<6>[ 1.925265] c0 mmc1: cmd 5 command timeout error
<6>[ 1.925601] c0 mmc1: cmd 5 command timeout error
<6>[ 2.149524] c0 mmc1: new high speed SDHC card at address aaaa
<6>[ 2.150146] c0 mmcblk0: mmc1:aaaa SU32G 29.7 GiB
<6>[ 2.151639] c0 mmcblk0: p1
* note that there are errors for both internal and external cards, but if I remove/readd the external card while booted:
Code:
<6>[ 554.482789] c0 mmc1: card removed.
<6>[ 554.483031] c0 mmc1: card inserted.
<6>[ 554.484051] c0 mmc1: card inserted.
<6>[ 554.484199] c0 mmc1: card removed.
<6>[ 554.484371] c0 mmc1: card removed.
<6>[ 554.484487] c0 mmc1: card removed.
<6>[ 554.680618] c0 mmc1: card aaaa removed
<6>[ 554.701931] c0 sdhci_set_ios : MMC Card OFF samsung-hsmmc
<6>[ 555.482722] c0 mmc1: card inserted.
<6>[ 555.482883] c0 mmc1: card removed.
<6>[ 555.483037] c0 mmc1: card inserted.
<6>[ 555.483154] c0 mmc1: card removed.
<6>[ 555.483279] c0 mmc1: card inserted.
<6>[ 555.483414] c0 mmc1: card removed.
<6>[ 555.483529] c0 mmc1: card inserted.
<6>[ 555.483649] c0 mmc1: card inserted.
<6>[ 555.483772] c0 mmc1: card removed.
<6>[ 555.483891] c0 mmc1: card inserted.
<6>[ 555.485434] c0 mmc1: card removed.
<6>[ 555.485614] c0 mmc1: card inserted.
<6>[ 555.486618] c0 mmc1: card inserted.
<6>[ 555.486961] c0 mmc1: card inserted.
<6>[ 555.487101] c0 mmc1: card inserted.
<6>[ 555.681309] c0 sdhci_set_ios : MMC Card ON samsung-hsmmc
<6>[ 555.710511] c0 mmc1: cmd 52 command timeout error
<6>[ 555.711030] c0 mmc1: cmd 52 command timeout error
<6>[ 555.715224] c0 mmc1: cmd 5 command timeout error
<6>[ 555.715679] c0 mmc1: cmd 5 command timeout error
<6>[ 555.716136] c0 mmc1: cmd 5 command timeout error
<6>[ 555.716587] c0 mmc1: cmd 5 command timeout error
<6>[ 555.915431] c3 mmc1: new high speed SDHC card at address aaaa
<6>[ 555.918560] c3 mmcblk0: mmc1:aaaa SU32G 29.7 GiB
<6>[ 555.923272] c3 mmcblk0: p1
<7>[ 557.842034] c3 SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts
~ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 425992 136 425856 0% /dev
tmpfs 425992 8 425984 0% /tmp
tmpfs 425992 0 425992 0% /storage
tmpfs 425992 0 425992 0% /mnt/secure
tmpfs 425992 0 425992 0% /mnt/fuse
/dev/block/vold/179:1
31154688 29870720 1283968 96% /storage/sdcard1
What are my options ?
* I've seen some people using JTAG software tools and soldering to reset the eMMC. E.g. http://forum.gsmhosting.com/vbb/f60...n7100-without-removing-emmc-pictures-1945278/ Are there a combination of these operations that might allow me to read without destroying the data ? I also read http://forum.xda-developers.com/galaxy-note-2/help/to-recover-data-corrupted-emmc-t3292290/page2 but was not 100% sure of how to use that.
* are there some soft solutions I should try before I do this ? Maybe reflashing recovery software? Some magic combinations I don't know ?
The phone has
* CWR v6.0.4.6
* BlissPop 3.6 (if I recall long time since I set it up it.)
Thanks anyone for their help.
Yes you can get the data from it, if it's hardware-dead then no, your best bet is JTAG, I'm sure it won't be too expensive
Sent from my HTC 10 using Tapatalk

Categories

Resources