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.
Related
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
Suddenly after taking my phone out on a rainy day, my wifi stopped working. I am sure water never went it. I have tried multiple things to make it work like factory reset, changing the ROM to jelly bean and currently running the kernel 3.0.31-siyah-s2-v5.0, model GT-I9100 android version 4.1.2
Kindly Help.I am seeing the dmesg terminal logs as attached and snippet below.
<4>[ 104.060063] ## wifi_probe
<4>[ 104.060090] wifi_set_power = 1
<6>[ 104.060111] ------------------------------------------------
<6>[ 104.060145] ------------------------------------------------
<6>[ 104.060188] brcm_wlan_power Enter: power on
<6>[ 104.060215] gpio_table = [2]
<7>[ 104.060442] WLAN: GPIO_WLAN_EN = 1
<6>[ 104.094096] mif: link_pm_irq_handler: gpio [HWK] get [0]
<6>[ 104.120714] mif: link_pm_irq_handler: gpio [HWK] get [1]
<6>[ 104.170090] mif: usb_port_resume: 1283, 4
<6>[ 104.249999] EXT4-fs (mmcblk0p9): re-mounted. Opts: (null)
<4>[ 104.265090] wifi_set_carddetect = 1
<6>[ 104.265114] gpio_table = [6]
<6>[ 104.265343] Test logs pdev : c0ccd110 s3c_device_hsmmc3 c0ccd110
<6>[ 104.265378] Test logs notify_func = hsmmc3_notify_func: c083e75c
<6>[ 104.265416] mmc2: card inserted.
<6>[ 104.495446] mmc2: cmd 52 command timeout error
<6>[ 104.495936] mmc2: cmd 52 command timeout error
<6>[ 104.499846] mmc2: cmd 8 command timeout error
<4>[ 104.511333] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 104.513886] mmc2: queuing unknown CIS tuple 0x80 (6 bytes)
<6>[ 104.573970] mmc2: new high speed SDIO card at address 0001
<4>[ 104.785592] alloc static buf at e3a00000!
<4>[ 104.786022] dhdsdio_probe : no mutex held. set lock
<6>[ 105.007466] set_gps_uart_op: off
<6>[ 105.433663] EXT4-fs (mmcblk0p9): re-mounted. Opts: (null)
<6>[ 106.011099] mif: link_pm_irq_handler: gpio [HWK] get [0]
<6>[ 106.040827] mif: link_pm_irq_handler: gpio [HWK] get [1]
<6>[ 106.090112] mif: usb_port_resume: 1283, 4
<3>[ 106.158197] binder: release proc 13734, transaction 52072, not freed
<3>[ 106.158236] binder: release proc 13734, transaction 52103, not freed
<3>[ 106.296134] mmc2: cmd 53 data timeout error
<4>[ 106.296964] bcmsdh_sdmmc: Failed to Read word, Err: 0xffffff92F1 signature read
@0x18000000=0xffffffff
<3>[ 107.808869] mmc2: cmd 53 data timeout error
<4>[ 107.809040] bcmsdh_sdmmc: Failed to Read word, Err: 0xffffff92dhdsdio_probe_attach: si_attach
failed!
<4>[ 107.809193] dhdsdio_probe: dhdsdio_probe_attach failed
<4>[ 107.809284] dhdsdio_probe : the lock is released.
<4>[ 107.816772] dhd_module_init: sdio_register_driver fail
<4>[ 107.816919] bcmsdh_sdmmc: bcmsdh_sdmmc_remove Enter
<4>[ 107.824497] ## wifi_remove
<4>[ 107.824549] wifi_set_power = 0
<6>[ 107.824599] ------------------------------------------------
<6>[ 107.824676] ------------------------------------------------
<6>[ 107.824761] brcm_wlan_power Enter: power off
<6>[ 107.824828] gpio_table = [2]
<7>[ 107.824887] WLAN: GPIO_WLAN_EN = 0
<4>[ 107.925157] wifi_set_carddetect = 0
<6>[ 107.925225] gpio_table = [6]
<6>[ 107.925503] Test logs pdev : c0ccd110 s3c_device_hsmmc3 c0ccd110
<6>[ 107.925589] Test logs notify_func = hsmmc3_notify_func: c083e75c
<6>[ 107.925678] mmc2: card inserted.
<6>[ 107.965872] mif: link_pm_irq_handler: gpio [HWK] get [0]
<6>[ 107.995841] mif: link_pm_irq_handler: gpio [HWK] get [1]
<6>[ 108.045163] mif: usb_port_resume: 1283, 4
<6>[ 108.125196] mmc2: cmd 7 command timeout error
<6>[ 108.125256] mmc2: cmd 7 command timeout error
<6>[ 108.125307] mmc2: cmd 7 command timeout error
<6>[ 108.125356] mmc2: cmd 7 command timeout error
<6>[ 108.136243] mmc2: card 0001 removed
<6>[ 108.170596] mmc2: cmd 52 command timeout error
<6>[ 108.171186] mmc2: cmd 52 command timeout error
<6>[ 108.174766] mmc2: cmd 8 command timeout error
<6>[ 108.175114] mmc2: cmd 5 command timeout error
<6>[ 108.175443] mmc2: cmd 5 command timeout error
<6>[ 108.175773] mmc2: cmd 5 command timeout error
<6>[ 108.176101] mmc2: cmd 5 command timeout error
<6>[ 108.176500] mmc2: cmd 55 command timeout error
<6>[ 1
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
Hi All,
I've loved my Samsung Galaxy S3 I9300 and have been so happy with the Resurrection Remix Marshmallow ROM (ResurrectionRemix-M-v5.6.4-20160223-i9300.zip). Over the last few weeks, I'd notice the phone would have random problems but a re-install via full wipe would bring it back into working order. However, when I woke up this morning all I could get was the Samsung SIII boot logo, the recovery: TWRP v2.8.6.1 or the fastboot/download mode.
When the TWRP recovery is booted I discovered I can get a root shell via "adb shell" and that /data was empty and, in fact, all my filesystems are read only. I'm an old linux hand so I suspect my 16GB of internal Nand memory is getting a bit too long in the tooth... so I thought I'd "umount /data" try running "e2fsck -vf /dev/block/mmcblk0p12" on the /data device... and "/proc/kmsg" spurts out a steady stream of I/O errors:
<7>[ 1440.020301] c0 mshci: ===========================================
<3>[ 1440.020402] c0 brq->sbc.opcode=23,brq->cmd.opcode=25.
<3>[ 1440.020449] c0 brq->sbc.error=-110,brq->cmd.error=0, brq->stop.error=0,brq->data.error=0.
<3>[ 1440.020558] c0 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 1440.020628] c0 mmcblk0: command error, retrying timeout
<3>[ 1440.144001] c0 mmc0: cmd 23 response timeout error
<7>[ 1440.144050] c0 mshci: ============== REGISTER DUMP ==============
<7>[ 1440.144105] c0 mshci: MSHCI_CTRL: 0x00000010
<7>[ 1440.144147] c0 mshci: MSHCI_PWREN: 0x00000001
<7>[ 1440.144190] c0 mshci: MSHCI_CLKDIV: 0x00000001
<7>[ 1440.144232] c0 mshci: MSHCI_CLKSRC: 0x00000000
<7>[ 1440.144275] c0 mshci: MSHCI_CLKENA: 0x00000001
<7>[ 1440.144317] c0 mshci: MSHCI_TMOUT: 0xffffffff
<7>[ 1440.144360] c0 mshci: MSHCI_CTYPE: 0x00010000
<7>[ 1440.144402] c0 mshci: MSHCI_BLKSIZ: 0x00000200
<7>[ 1440.144445] c0 mshci: MSHCI_BYTCNT: 0x00001000
<7>[ 1440.144488] c0 mshci: MSHCI_INTMSK: 0x0000bfce
<7>[ 1440.144530] c0 mshci: MSHCI_CMDARG: 0x00000020
<7>[ 1440.144573] c0 mshci: MSHCI_CMD: 0x20002157
<7>[ 1440.144615] c0 mshci: MSHCI_MINTSTS: 0x00000000
<7>[ 1440.144658] c0 mshci: MSHCI_RINTSTS: 0x00000030
<7>[ 1440.144700] c0 mshci: MSHCI_STATUS: 0x00006906
<7>[ 1440.144743] c0 mshci: MSHCI_FIFOTH: 0x503f0040
<7>[ 1440.144786] c0 mshci: MSHCI_CDETECT: 0x00000001
<7>[ 1440.144828] c0 mshci: MSHCI_WRTPRT: 0x00000001
<7>[ 1440.144871] c0 mshci: MSHCI_GPIO: 0x00000000
<7>[ 1440.144913] c0 mshci: MSHCI_TCBCNT: 0x00000800
<7>[ 1440.144956] c0 mshci: MSHCI_TBBCNT: 0x00001000
<7>[ 1440.144999] c0 mshci: MSHCI_DEBNCE: 0x000fffff
<7>[ 1440.145041] c0 mshci: MSHCI_USRID: 0xffffffff
<7>[ 1440.145084] c0 mshci: MSHCI_VERID: 0x5342240a
<7>[ 1440.145127] c0 mshci: MSHCI_HCON: 0x00e424c1
<7>[ 1440.145169] c0 mshci: MSHCI_UHS_REG: 0x00010000
<7>[ 1440.145212] c0 mshci: MSHCI_BMOD: 0x00000582
<7>[ 1440.145254] c0 mshci: MSHCI_PLDMND: 0x00000000
<7>[ 1440.145297] c0 mshci: MSHCI_DBADDR: 0x6bc44000
<7>[ 1440.145340] c0 mshci: MSHCI_IDSTS: 0x00000000
<7>[ 1440.145382] c0 mshci: MSHCI_IDINTEN: 0x00000000
<7>[ 1440.145425] c0 mshci: MSHCI_DSCADDR: 0x6bc44000
<7>[ 1440.145467] c0 mshci: MSHCI_BUFADDR: 0x00000000
<7>[ 1440.145510] c0 mshci: MSHCI_WAKEUPCON: 0x00000000
<7>[ 1440.145553] c0 mshci: MSHCI_CLOCKCON: 0x00000000
<7>[ 1440.145595] c0 mshci: MSHCI_FIFODAT: 0x00000000
<7>[ 1440.145638] c0 mshci: ===========================================
<3>[ 1440.145808] c0 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
So, since my TWRP seems intact but my internal Nand memory appears hosed is there any way I can convince TWRP or any other bootloader/recovery to use my external SDCARD as a boot device instead ?
I note that there's a /init.rc which appears to define where ANDROID_ROOT and ANDROID_DATA come from:
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
mkdir /sdcard
mkdir /extSdCard
mkdir /system
mkdir /data
mkdir /cache
mkdir /preload
mkdir /efs
mount /tmp /tmp tmpfs
I'm not clear on where the content of / comes from... I seem to have lost everything in /system (except for an empty /system/bin)... / does seem to be writable but it does not persist reboots. Old favourites for partition information seem inconsistent: fdisk, df, mount and /proc/partitions.
Fdisk only sees one partition, presumably because it's got a gpt label that fdisk cannot understand:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Df only sees cache, external_sd and /efs:
# df -kh
Filesystem Size Used Available Use% Mounted on
tmpfs 416.5M 48.0K 416.4M 0% /dev
/dev/block/mmcblk0p8 1007.9M 17.3M 990.6M 2% /cache
/dev/block/mmcblk1p1 59.6G 39.2G 20.4G 66% /external_sd
/dev/block/mmcblk0p3 19.7M 9.2M 10.5M 47% /efs
Mount confirms "df":
# 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 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
However, /proc/partitions contradicts these:
# cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1048576 mmcblk0p8
179 9 1572864 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 12091392 mmcblk0p12
179 16 62521344 mmcblk1
179 17 62520320 mmcblk1p1
Suggesting that the kernel sees all the devices and partitions.
Any advice hugely appreciated... I realise I may out of luck and just have to resign myself to the fact that, while I have a working device and SD card, the fact that the internal Nand memory is hosed means it's time to let go. Or maybe there's another way to breath life into the Nand ?
Any thoughts, the more technical the better, hugely appreciated.
Cheers,
Doug
I think twrp is the problem.
The safest thing to do is flash a stock rom via odin and start over.
The risky choice is to find another known working recovery and see if that can mount the partitions.
At one time twrp borked and i thought id lost my trusty old s3 so i found and flashed the stock recovery and all worked fine. I don't recommend it by a long shot. It was a "its f**ked anyway" moment.
Sent from my HTC One M9 using Tapatalk
Hi Shivado,
Thanks so much for responding.
I spent all day trying to download a stock i9300 4.3 ROM... every one I could find failed to download... from a wide range of dodgy looking file sharing sites. I'll keep trying... maybe, if I can't find one, I'll try re-flashing the recovery.
Cheers,
Doug
dscoular said:
Hi Shivado,
Thanks so much for responding.
I spent all day trying to download a stock i9300 4.3 ROM... every one I could find failed to download... from a wide range of dodgy looking file sharing sites. I'll keep trying... maybe, if I can't find one, I'll try re-flashing the recovery.
Cheers,
Doug
Click to expand...
Click to collapse
This stuff is for international (btu) only
https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
Sent from my HTC One M9 using Tapatalk
Hi Shivado,
I tried flashing with ODIN and Heimdall... Odin just timed out trying to set up a connection... Heimdall started flashing the cache.img file but then failed after 68%:
bash-3.2$ sudo heimdall flash --CACHE cache.img \
--BOOT boot.img \
--SYSTEM system.img \
--RECOVERY recovery.img \
--RADIO modem.bin \
--HIDDEN hidden.img \
--BOOTLOADER sboot.bin \
--TZSW tz.img --verbose
> > > > > > > Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
PIT file download successful.
Uploading CACHE
68%
ERROR: Failed to unpack received packet.
I wonder if I can somehow boot off the external SD card instead ?
Any thoughts or suggestions hugely appreciated.
Cheers,
Doug
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