I have had my refurbished HTC Vision for about three weeks and it hadn't had any problems. Then yesterday, I rebooted it and now the sdcard doesn't work. Not just that it doesn't mount, rather there is not even a /dev/block/mmcblk1 device.
Here is what I tried:
* Boot into ClockworkMod, and run adb shell. Still no /dev/block/mmcblk1.
* Boot into fastboot and run "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig".
* Per some random instructions on the net, I held vol-up and power, then pulled the battery after the phone vibrated. Then I held vol-up, vol-down, power and did the same. Then the fastboot commands again.
* Bent the sdcard port's pins out a bit with tweezers.
* SDcard works in computer (Linux).
* Tried another card that has nothing but a vfat partition.
Nothing works! There are some errors in dmesg:
Code:
$ dmesg |grep mmc
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT09LR200858 androidboot.bootloader=0.76.2000 no_console_suspend=1 console=null
<6>[ 2.532989] vision: vision_init_mmc
<3>[ 3.267822] mmc0: No card detect facilities available
<6>[ 3.268341] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 3.268615] mmc0: Platform slot type: MMC
<6>[ 3.268737] mmc0: 4 bit data mode disabled
<6>[ 3.269012] mmc0: 8 bit data mode enabled
<6>[ 3.269134] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.269378] mmc0: Slot eject status = 0
<6>[ 3.269531] mmc0: Power save feature enable = 1
<6>[ 3.269653] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2b774000
<6>[ 3.269927] mmc0: DM cmd busaddr 0x2b774000, cmdptr busaddr 0x2b774300
<6>[ 3.270751] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 3.270996] mmc1: Platform slot type: N/A
<6>[ 3.271148] mmc1: 4 bit data mode enabled
<6>[ 3.271392] mmc1: 8 bit data mode disabled
<6>[ 3.271514] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.271789] mmc1: Slot eject status = 1
<6>[ 3.271911] mmc1: Power save feature enable = 1
<6>[ 3.272064] mmc1: DM non-cached buffer at ffa0d000, dma_addr 0x2b777000
<6>[ 3.272308] mmc1: DM cmd busaddr 0x2b777000, cmdptr busaddr 0x2b777300
<6>[ 3.273468] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 3.273712] mmc2: Platform slot type: SD
<6>[ 3.273834] mmc2: 4 bit data mode enabled
<6>[ 3.273986] mmc2: 8 bit data mode disabled
<6>[ 3.274230] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.274353] mmc2: Slot eject status = 0
<6>[ 3.274658] mmc2: Power save feature enable = 1
<6>[ 3.274810] mmc2: DM non-cached buffer at ffa0e000, dma_addr 0x2b778000
<6>[ 3.275054] mmc2: DM cmd busaddr 0x2b778000, cmdptr busaddr 0x2b778300
<6>[ 3.275207] mmc2: Polling status mode enabled
<6>[ 3.425598] mmc0: new high speed MMC card at address 0001
<6>[ 3.427093] mmcblk0: mmc0:0001 SEM04G 2.09 GiB
<6>[ 3.428100] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<6>[ 3.569030] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 3.703063] mmc2: high speed mode max_dtr = 50000000
<4>[ 3.703491] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.703643] mmc2: new high speed SDHC card at address 0001
<6>[ 3.704498] mmcblk1: mmc2:0001 00000 7.41 GiB
<6>[ 3.705291] mmcblk1: p1
<4>[ 4.648254] EXT4-fs (mmcblk0p26): warning: maximal mount count reached, running e2fsck is recommended
<7>[ 4.651062] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24790
<7>[ 4.655670] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24741
<6>[ 4.657012] EXT4-fs (mmcblk0p26): 2 orphan inodes deleted
<6>[ 4.657379] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 4.703216] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
<4>[ 4.758331] EXT4-fs (mmcblk0p27): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.760345] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 4.762298] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 4.886474] EXT4-fs (mmcblk0p28): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.888580] EXT4-fs (mmcblk0p28): recovery complete
<6>[ 4.890563] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: barrier=1
<7>[ 20.824981] mmc1: card_present 1
<6>[ 20.825134] mmc1: Slot status change detected (0 -> 1)
<7>[ 23.383300] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 23.383331] mmc1: new high speed SDIO card at address 0001
<3>[ 38.746368] mmc2: Data CRC error
<6>[ 38.746978] mmc2: Controller has been reset
<3>[ 38.747467] mmcblk1: error -84 transferring data, sector 2080, nr 1, card status 0x900
<6>[ 38.747619] mmc2: reinit card
<4>[ 38.747863] mmc2: Starting deferred resume
<3>[ 38.814849] mmc2: Data CRC error
<6>[ 38.815521] mmc2: Controller has been reset
<3>[ 38.815856] mmc2: Re-init card rc = -84 (retries = 5)
<3>[ 38.997650] mmc2: Data CRC error
<6>[ 38.998291] mmc2: Controller has been reset
<3>[ 39.001403] mmc2: Re-init card rc = -84 (retries = 4)
<3>[ 39.200927] mmc2: Data CRC error
<6>[ 39.201507] mmc2: Controller has been reset
<3>[ 39.201721] mmc2: Re-init card rc = -84 (retries = 3)
<3>[ 39.384826] mmc2: Data CRC error
<6>[ 39.385406] mmc2: Controller has been reset
<3>[ 39.385650] mmc2: Re-init card rc = -84 (retries = 2)
<3>[ 39.583618] mmc2: Data CRC error
<6>[ 39.584228] mmc2: Controller has been reset
<3>[ 39.584472] mmc2: Re-init card rc = -84 (retries = 1)
<6>[ 39.666137] mmc2: Deferred resume failed
<6>[ 39.666412] mmc: reinit failed, remove card
<6>[ 39.666625] mmc2: remove card
<3>[ 39.666778] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.667053] Buffer I/O error on device mmcblk1p1, logical block 32
<4>[ 39.667205] lost page write due to I/O error on mmcblk1p1
<3>[ 39.667480] mmc_blk_issue_rq failed!!
<6>[ 39.667633] mmc2: mmc_remove_sd_card
<6>[ 39.667907] mmc2: card 0001 removed
<3>[ 39.670318] mmcblk1: error -123 sending status comand
<3>[ 39.670471] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.670867] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.671783] mmc_blk_issue_rq failed!!
<3>[ 39.671966] mmcblk1: error -123 sending read command, response 0x0
<4>[ 39.672210] mmcblk1: retrying using single block read
<3>[ 39.672332] mmcblk1: error -123 sending status comand
<3>[ 39.672607] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.672882] end_request: I/O error, dev mmcblk1, sector 32378
<3>[ 39.673126] end_request: I/O error, dev mmcblk1, sector 32379
<3>[ 39.673278] end_request: I/O error, dev mmcblk1, sector 32380
<3>[ 39.673522] end_request: I/O error, dev mmcblk1, sector 32381
<3>[ 39.673675] end_request: I/O error, dev mmcblk1, sector 32382
<3>[ 39.673919] end_request: I/O error, dev mmcblk1, sector 32383
<3>[ 39.674072] end_request: I/O error, dev mmcblk1, sector 32384
<3>[ 39.674316] end_request: I/O error, dev mmcblk1, sector 32385
<3>[ 39.674499] mmc_blk_issue_rq failed!!
<3>[ 39.674774] mmcblk1: error -123 sending status comand
<3>[ 39.674926] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.675292] end_request: I/O error, dev mmcblk1, sector 32378
... and so on. In this run, I see that at least briefly the kernel could read the mmcblk1 partition table (although there still was not /dev/block/mmcblk1). However, most of the time it can't and just gives the CRC errors.
Is this a hardware or software problem. Any suggestions? Thanks.
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
worked!
demkantor said:
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Worked, thanks!!! The CRC errors made me suspect hardware, but I wanted someone else to say it before I tore the thing open. I've always had bad luck tearing these things apart (only junk phones in the past), but I bought a cheapo disassembly kit a while back which has helped greatly with popping the case off. And thankfully I only had to get to about step three of the instructions before the ribbon cable was accessible!
Related
Anyone else have a problem with USB host mode and copying big files?
If so, can we fix this?
I have tried formatting my drive in FAT32,NTFS, and ext2. But the result is always the same, the drive dies if I copy a file bigger than 30 or 40 MB. I have tried stock, Faux123, and francoKernel as well.
The drive doesn't die at a specific MB each time, but it is generally around 30 MB but sometimes makes it to 80 or even 140 MB one time. I am trying to off-load some 700MB movies.
Here is the kernel message error:
<6>[ 1920.842529] max17040 4-0036: online = 1 vcell = 3547500 soc = 22 status = 3 health = 1 temp = 370 charger status = 0
<3>[ 1926.574005] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.594299] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.649810] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1927.740753] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
<6>[ 1927.773895] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
<6>[ 1927.938781] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
<3>[ 1968.389251] L3 CUSTOM SRESP error with SOURCEMM2 info=0x84
<4>[ 1968.389434] ------------[ cut here ]------------
<4>[ 1968.389739] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 l3_interrupt_handler+0x31c/0x360()
<4>[ 1968.390045] L3 custom sresp error
<4>[ 1968.390197] Modules linked in:
<4>[ 1968.390686] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1968.390991] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 1968.391326] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0074898>] (l3_interrupt_handler+0x31c/0x360)
<4>[ 1968.391632] [<c0074898>] (l3_interrupt_handler+0x31c/0x360) from [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178)
<4>[ 1968.391967] [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178) from [<c00d4760>] (handle_irq_event+0x3c/0x5c)
<4>[ 1968.392150] [<c00d4760>] (handle_irq_event+0x3c/0x5c) from [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164)
<4>[ 1968.392456] [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164) from [<c00d3f50>] (generic_handle_irq+0x2c/0x40)
<4>[ 1968.392791] [<c00d3f50>] (generic_handle_irq+0x2c/0x40) from [<c004904c>] (asm_do_IRQ+0x4c/0xac)
<4>[ 1968.393096] [<c004904c>] (asm_do_IRQ+0x4c/0xac) from [<c004eb08>] (__irq_svc+0x48/0xe4)
<4>[ 1968.393402] Exception stack(0xc0799f28 to 0xc0799f70)
<4>[ 1968.393554] 9f20: c0799f70 3b9aca00 4c534d85 000001ca 4c4bda2c 000001ca
<4>[ 1968.393859] 9f40: 000003ff c1192210 8000406a 412fc09a 00000000 00000000 00000000 c0799f70
<4>[ 1968.394042] 9f60: c007c690 c0068380 00000013 ffffffff
<4>[ 1968.394348] [<c004eb08>] (__irq_svc+0x48/0xe4) from [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4)
<4>[ 1968.394683] [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4) from [<c03af838>] (cpuidle_idle_call+0x94/0x118)
<4>[ 1968.394989] [<c03af838>] (cpuidle_idle_call+0x94/0x118) from [<c0050538>] (cpu_idle+0xbc/0xfc)
<4>[ 1968.395172] [<c0050538>] (cpu_idle+0xbc/0xfc) from [<c00088ac>] (start_kernel+0x298/0x2e8)
<4>[ 1968.395477] [<c00088ac>] (start_kernel+0x298/0x2e8) from [<80008040>] (0x80008040)
<4>[ 1968.395782] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 1968.396087] ---[ end trace 33de6ebe35ad56b6 ]---
<6>[ 1970.874023] max17040 4-0036: online = 1 vcell = 3532500 soc = 22 status = 3 health = 1 temp = 380 charger status = 0
<6>[ 1993.138793] usb 1-1: reset high speed USB device number 2 using musb-hdrc
<6>[ 2000.347503] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<6>[ 2000.347717] usb 1-1: USB disconnect, device number 2
<4>[ 2000.350708] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2000.351989] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2001.361236] max17040 4-0036: online = 1 vcell = 3585000 soc = 21 status = 2 health = 1 temp = 380 charger status = 0
<6>[ 2003.287322] sd 0:0:0:0: Device offlined - not ready after error recovery
<6>[ 2003.287597] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287628] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287658] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.287689] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
<3>[ 2003.287719] end_request: I/O error, dev sda, sector 63
<3>[ 2003.287750] Buffer I/O error on device sda1, logical block 0
<4>[ 2003.287780] lost page write due to I/O error on sda1
<6>[ 2003.289154] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.289459] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 21 e7 00 00 08 00
<3>[ 2003.291625] end_request: I/O error, dev sda, sector 8679
<3>[ 2003.291778] Buffer I/O error on device sda1, logical block 1077
<4>[ 2003.292114] EXT4-fs warning (device sda1): ext4_end_bio:258: I/O error writing to inode 13 (offset 217088 size 4096 starting block 1085)
<3>[ 2003.297576] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.297851] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.299560] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.299743] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.300415] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.300720] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301116] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.301391] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301727] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.302032] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.302398] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.302703] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.303802] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.304168] EXT4-fs error (device sda1): ext4_free_branches:4377: inode #13: block 536: comm libestool.so: Read failure
<3>[ 2003.305358] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.305755] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.306365] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.306518] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.336242] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.336364] EXT4-fs error (device sda1): ext4_find_entry:934: inode #2: comm libestool.so: reading directory lblock 0
<3>[ 2003.411834] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.412017] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm ngs.android.pop: unable to read itable block
<2>[ 2003.412414] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.412567] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2008.311859] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.312194] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm bdi-default: unable to read itable block
<3>[ 2008.313110] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.313415] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm bdi-default: unable to read itable block
<6>[ 2025.582702] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2026.233337] usb 1-1: new high speed USB device number 3 using musb-hdrc
<3>[ 2026.388244] usb 1-1: device v090c p6200 is not supported
<6>[ 2026.388427] usb 1-1: New USB device found, idVendor=090c, idProduct=6200
<6>[ 2026.388763] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2026.389068] usb 1-1: Product: Generic USB2.0 card
<6>[ 2026.389221] usb 1-1: Manufacturer: Silicon Motion, Inc.
<6>[ 2026.389373] usb 1-1: SerialNumber: 12345678901234567890
<6>[ 2026.392089] scsi1 : usb-storage 1-1:1.0
<6>[ 2030.177124] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2030.180053] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2030.181335] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2031.197509] max17040 4-0036: online = 1 vcell = 3600000 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<6>[ 2034.948303] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2035.182495] usb 1-1: USB disconnect, device number 3
<6>[ 2045.606109] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2045.609100] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2045.610321] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2046.627288] max17040 4-0036: online = 1 vcell = 3602500 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<4>[ 2048.832824] ------------[ cut here ]------------
<4>[ 2048.832916] WARNING: at drivers/usb/musb/musb_host.c:125 musb_h_tx_flush_fifo+0x78/0x84()
<4>[ 2048.833068] Could not flush host TX2 fifo: csr: 2003
<4>[ 2048.833160] Modules linked in:
<4>[ 2048.833404] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 2048.833526] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 2048.833679] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84)
<4>[ 2048.833862] [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84) from [<c0367724>] (musb_cleanup_urb+0xb0/0xd4)
<4>[ 2048.834014] [<c0367724>] (musb_cleanup_urb+0xb0/0xd4) from [<c0367990>] (musb_urb_dequeue+0xfc/0x13c)
<4>[ 2048.834167] [<c0367990>] (musb_urb_dequeue+0xfc/0x13c) from [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac)
<4>[ 2048.834350] [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac) from [<c035d938>] (usb_stor_stop_transport+0x48/0x60)
<4>[ 2048.834442] [<c035d938>] (usb_stor_stop_transport+0x48/0x60) from [<c035c36c>] (command_abort+0x80/0x84)
<4>[ 2048.834564] [<c035c36c>] (command_abort+0x80/0x84) from [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c)
<4>[ 2048.834716] [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c) from [<c00b227c>] (kthread+0x80/0x88)
<4>[ 2048.834899] [<c00b227c>] (kthread+0x80/0x88) from [<c0050148>] (kernel_thread_exit+0x0/0x8)
<4>[ 2048.835052] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 2048.835144] ---[ end trace 33de6ebe35ad56b7 ]---
<6>[ 2048.837768] scsi 1:0:0:0: Device offlined - not ready after error recovery
I found a thread on TI site for the OMAP4460 that discusses an error like mine but the signature is not the same, seems there they were having a problem with the the TCP/IP stack becoming corrupted because the processor was allocating memory too fast. Something like that is happening here. All I really know is it has to do with the handling of the L3 cache.
I think this may have to do with the cpu trying to idle when it should not.
What kind of drive are you using? If its a portable usb hard drive then this could be a power issue.
It's not a portable HD, just usb sd card reader.
With further investigation I have found that the problem might stem from the x-loader being mismatched to the kernel, which is part of the bootloader.
I tried different bootloaders, but none made a difference.
Finally, I tried a different USB OTG cable, a slightly more expensive one, and it worked.
Background:
My Samsung Galaxy S died, so I am using my backup rooted G2 with CM7.
After the Market downloaded all of my apps onto the G2 (this failed for a bunch of apps and had to be restarted a few times to complete), the phone started to freeze randomly.
Today it just boots to the HTC logo.
Recovery fails and complains about /cache and /data not found.
Through some troubleshooting, I found that those are mounted on /dev/block/mmcblk0p#
Any attempt to read that block device throws I/O errors.
I was able to confim that my SD card is /dev/block/mmcblk1 and can mount that and access the files on it.
Thought the emcc was dead but:
fastboot oem check_emmc_mid
... INFOManufacturer ID, MID=15
INFOeMMC should be samsung
OKAY
Notice that is says SAMSUNG (hmmm.. does it somehow think it is the Galazy S phone?)
Questions:
- Is this phone dead?
- Should the check_emmcc against an HTC phone report Samsung?
- There does not seem to be any mmcblk0, (I assume, from the hundreds of articles I've read so far, that this would be the SDCard), so how can I tell the system to use mmcblk1?
- Can I change /etc/fstab to point to new partitions that I would create on SDCard (mmcblk1p#)
- Any other ideas?
Thanks in advance.
The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
demkantor said:
The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
@demkantor : Thanks for the quick reply (wish my filters had't junked the notification). I will give this a try and report back here.
demkantor said:
The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That was quite a bit to go through and I learned a whole lot. Thanks.
From what I've been able to gather, seems I have a fried chip (hmm, sounds tasty).
I didn't find any articles, however, on running the OS from the SD.
Just in case, here is all the system info I gathered along the way. Perhaps you can confirm that my chip is indeed dead and determine if this is capable of running off the SD or maybe I missed something.
Code:
~ # dmesg | grep mmc0
<3>[ 4.308654] mmc0: No card detect facilities available
<6>[ 4.309295] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
<6>[ 4.309417] mmc0: Platform slot type: MMC
<6>[ 4.309661] mmc0: 4 bit data mode disabled
<6>[ 4.309783] mmc0: 8 bit data mode enabled
<6>[ 4.309936] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.310180] mmc0: Slot eject status = 0
<6>[ 4.310302] mmc0: Power save feature enable = 1
<6>[ 4.310546] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb6d000
<6>[ 4.310668] mmc0: DM cmd busaddr 0x0bb6d000, cmdptr busaddr 0x0bb6d300
<6>[ 4.466278] mmc0: new high speed MMC card at address 0001
<6>[ 4.468261] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 5.746704] mmc0: failed to get card ready
<6>[ 5.746826] mmc0: reinit card
<4>[ 5.746978] mmc0: Starting deferred resume
<6>[ 7.786712] mmc0: Deferred resume failed
<3>[ 7.885559] mmc0: DMA channel flushed (0x80000004)
<6>[ 7.885986] mmc0: Controller has been reset
<6>[ 7.886169] mmc0: Worked around bug 1535304
<3>[ 7.887542] mmc0: DMA channel flushed (0x80000004)
<6>[ 7.887969] mmc0: Controller has been reset
<6>[ 7.888153] mmc0: Worked around bug 1535304
<6>[ 7.895080] mmc0: reinit card
<4>[ 7.895202] mmc0: Starting deferred resume
<6>[ 9.926788] mmc0: Deferred resume failed
<3>[ 10.075073] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.075500] mmc0: Controller has been reset
<6>[ 10.075714] mmc0: Worked around bug 1535304
<3>[ 10.077087] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.077514] mmc0: Controller has been reset
<6>[ 10.077697] mmc0: Worked around bug 1535304
<6>[ 10.084564] mmc0: reinit card
<4>[ 10.084686] mmc0: Starting deferred resume
<6>[ 12.116760] mmc0: Deferred resume failed
<3>[ 12.119018] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.119445] mmc0: Controller has been reset
<6>[ 12.119659] mmc0: Worked around bug 1535304
<3>[ 12.121032] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.121490] mmc0: Controller has been reset
<6>[ 12.121795] mmc0: Worked around bug 1535304
<6>[ 12.128601] mmc0: reinit card
<4>[ 12.128723] mmc0: Starting deferred resume
<6>[ 14.166809] mmc0: Deferred resume failed
<3>[ 14.279052] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.279510] mmc0: Controller has been reset
<6>[ 14.279785] mmc0: Worked around bug 1535304
<3>[ 14.281036] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.281463] mmc0: Controller has been reset
<6>[ 14.281768] mmc0: Worked around bug 1535304
<6>[ 14.288574] mmc0: reinit card
<4>[ 14.288696] mmc0: Starting deferred resume
<6>[ 16.326751] mmc0: Deferred resume failed
<3>[ 16.328826] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.329254] mmc0: Controller has been reset
<6>[ 16.329559] mmc0: Worked around bug 1535304
<3>[ 16.330810] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.331237] mmc0: Controller has been reset
<6>[ 16.331542] mmc0: Worked around bug 1535304
<6>[ 16.338348] mmc0: reinit card
<4>[ 16.338470] mmc0: Starting deferred resume
<6>[ 18.376800] mmc0: Deferred resume failed
<3>[ 18.586914] mmc0: DMA channel flushed (0x80000004)
<6>[ 18.588073] mmc0: Controller has been reset
<6>[ 18.588836] mmc0: Worked around bug 1535304
<3>[ 18.590942] mmc0: DMA channel flushed (0x80000004)
<6>[ 18.592102] mmc0: Controller has been reset
<6>[ 18.592559] mmc0: Worked around bug 1535304
<6>[ 18.601043] mmc0: reinit card
<4>[ 18.601715] mmc0: Starting deferred resume
<6>[ 20.636810] mmc0: Deferred resume failed
<3>[ 20.640533] mmc0: DMA channel flushed (0x80000004)
<6>[ 20.641998] mmc0: Controller has been reset
<6>[ 20.642425] mmc0: Worked around bug 1535304
<3>[ 20.644561] mmc0: DMA channel flushed (0x80000004)
<6>[ 20.645721] mmc0: Controller has been reset
<6>[ 20.646148] mmc0: Worked around bug 1535304
<6>[ 20.654327] mmc0: reinit card
<4>[ 20.654998] mmc0: Starting deferred resume
<6>[ 22.686828] mmc0: Deferred resume failed
+++
# cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0\:0001/name
M4G2DE (confirmed that this is the bad Samsung chip)
+++
[email protected]:~$ fastboot devices
SH12RRXXXXXX fastboot
+++
[email protected]:~/Downloads/G2$ fastboot flash recovery recovery.zip
sending 'recovery' (5333 KB)... FAILED (status malformed (1 bytes))
+++
VISION PVT ENG S-OFF
HBOOT-0.76.200 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010,16:51:01
SYSTEM INFO
SN-SH12RRXXXXX
LCD-SO
TOUCH PANEL-ATMELC12_10aaT
Commit-977d3036
OS Ver.-1.22.531.8
CID-11111111
eMMC-samsung 2091MB 4284415sectors
Read up on this
www.thinkthinkdo.com/trac/project1/wiki/boot_sdcard
And this
http://forum.xda-developers.com/showthread.php?p=29940580
Sent from my HTC Vision using xda premium
demkantor said:
Read up on this
www.thinkthinkdo.com/trac/project1/wiki/boot_sdcard
And this
http://forum.xda-developers.com/showthread.php?p=29940580
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am probably restating the obvious, but I just want to go on the record here:
You Totally ROCK!!!!!!
It's alive! Now to see if I can get a copy kbeezie's CM7 UPDATE.zip. (OK, so I am greedy)
Hello, I am asking for help. I am new to this forum.
I have a T-Mobile G2 (HTC Vision Z equiv) that I was given by a friend. He rooted it and put CyanogenMod on it.
Two days ago, the phone rebooted of its own, and stayed stuck at the HTC white screen.
I did take the battery out and reinserted it in order to reboot the phone ( I have read several forum threads here about eMMc and battery problems resulting from battery removal, fwtw)
I am asking for assistance to determine if I can restore this phone, if its suffering the eMMC problem that has been noted in this forum, etc. I'm okay with the command line, new to Android hacking, so please keep your comments light.
On my laptop, I am running Linux Mint Nadia 14, I have the Android SDK installed and Oracle Java latest as well. I can bring the phone, plugged in via USB<-->MicroUSB cable, up in Android Debug Bridge, and see its serial number with ./adb devices, as long as my udev and the adb server are started in the right order
I can, using VOL-DOWN and POWER, get to HBOOT. Here is the headers:
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
and below, I have:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I can then get the phone to RECOVERY,
ClockWorkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recover/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Now, on my laptop, from the platform-tools directory, I can issue:
platform-tools # ./adb devices
List of devices attached
SH12SR201118 recovery
and I can enter adb-shell:
platform-tools # ./adb shell
~ # ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.vision.rc
emmc sd-ext
etc sdcard
Now the disturbing bits begin, that make me suspect the fried eMMc.
According to /etc/fstab, which when cat'd, yields:
/etc # cat fstab
/dev/block/mmcblk0p27 /cache auto rw
/dev/block/mmcblk0p26 /data auto rw
/dev/block/mmcblk0p25 /system auto rw
/dev/block/mmcblk1p1 /sdcard vfat rw
So is it correct that on my internal eMMC, that is /dev/block/mmcblk0p27 for /cache, ...0p26 for /data, etc?
fdisk is unable to give me any information about /dev/block/mmcblk0:
/etc # /sbin/fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': I/O error
while fdisk is fine to give me information about my sdcard (mmcblk1, according to fstab cat'd above):
/etc # /sbin/fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 2001 MB, 2001731584 bytes
42 heads, 41 sectors/track, 2270 cylinders
Units = cylinders of 1722 * 512 = 881664 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 2271 1954751+ 6 FAT16
Okay, xda folks, what should my next steps be?
thank you very very much,
Forrest :cyclops:
And...where should I go in xda to find actual help?
40 views of this message....and not a single reply? Where do I go for help?
http://forum.xda-developers.com/showthread.php?p=43195539
Sent from my Nexus 4 using Tapatalk 2
That's an information repository for sure, but...
demkantor, you posted a link to your gold mine of information http://forum.xda-developers.com/showthread.php?p=43195539. that's wonderful.
I will use the eMMC testing tips at http://forum.xda-developers.com/showthread.php?t=1983163. Remember that I posted a fairly complete description in my post of my situation....
Does this mean I have a fried eMMC? Looks like it. could someone verify?
Using the procedures on the page http://forum.xda-developers.com/showthread.php?t=1983163, i found the following:
In ADB shell, grepping for the eMMC yields this:
~ # dmesg | grep mmc0
<3>[ 4.904113] mmc0: No card detect facilities available
<6>[ 4.904663] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
<6>[ 4.904907] mmc0: Platform slot type: MMC
<6>[ 4.905059] mmc0: 4 bit data mode disabled
<6>[ 4.905273] mmc0: 8 bit data mode enabled
<6>[ 4.905426] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.905670] mmc0: Slot eject status = 0
<6>[ 4.905792] mmc0: Power save feature enable = 1
<6>[ 4.905914] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb9a000
<6>[ 4.906158] mmc0: DM cmd busaddr 0x0bb9a000, cmdptr busaddr 0x0bb9a300
<6>[ 5.065429] mmc0: new high speed MMC card at address 0001
<6>[ 5.067108] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 6.364196] mmc0: failed to get card ready
<6>[ 6.364440] mmc0: reinit card
<4>[ 6.364562] mmc0: Starting deferred resume
<6>[ 8.404327] mmc0: Deferred resume failed
<3>[ 8.510040] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.511199] mmc0: Controller has been reset
<6>[ 8.511962] mmc0: Worked around bug 1535304
<3>[ 8.514099] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.515228] mmc0: Controller has been reset
<6>[ 8.515655] mmc0: Worked around bug 1535304
<6>[ 8.524291] mmc0: reinit card
<4>[ 8.524963] mmc0: Starting deferred resume
<6>[ 10.564331] mmc0: Deferred resume failed
<3>[ 10.715789] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.716217] mmc0: Controller has been reset
<6>[ 10.716430] mmc0: Worked around bug 1535304
<3>[ 10.717803] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.718200] mmc0: Controller has been reset
<6>[ 10.718414] mmc0: Worked around bug 1535304
<6>[ 10.725219] mmc0: reinit card
<4>[ 10.725433] mmc0: Starting deferred resume
<6>[ 12.764282] mmc0: Deferred resume failed
<3>[ 12.766510] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.766967] mmc0: Controller has been reset
<6>[ 12.767181] mmc0: Worked around bug 1535304
<3>[ 12.768585] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.769042] mmc0: Controller has been reset
<6>[ 12.769226] mmc0: Worked around bug 1535304
<6>[ 12.776184] mmc0: reinit card
<4>[ 12.776306] mmc0: Starting deferred resume
<6>[ 14.814331] mmc0: Deferred resume failed
<3>[ 14.936950] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.937408] mmc0: Controller has been reset
<6>[ 14.937622] mmc0: Worked around bug 1535304
<3>[ 14.938964] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.939422] mmc0: Controller has been reset
<6>[ 14.939727] mmc0: Worked around bug 1535304
<6>[ 14.946594] mmc0: reinit card
<4>[ 14.946716] mmc0: Starting deferred resume
<6>[ 16.984283] mmc0: Deferred resume failed
<3>[ 16.986480] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.986938] mmc0: Controller has been reset
<6>[ 16.987152] mmc0: Worked around bug 1535304
<3>[ 16.988525] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.988983] mmc0: Controller has been reset
<6>[ 16.989257] mmc0: Worked around bug 1535304
<6>[ 16.996093] mmc0: reinit card
<4>[ 16.996215] mmc0: Starting deferred resume
<6>[ 19.034301] mmc0: Deferred resume failed
<3>[ 19.175415] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.175872] mmc0: Controller has been reset
<6>[ 19.176208] mmc0: Worked around bug 1535304
<3>[ 19.177459] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.177917] mmc0: Controller has been reset
<6>[ 19.178222] mmc0: Worked around bug 1535304
<6>[ 19.185028] mmc0: reinit card
<4>[ 19.185180] mmc0: Starting deferred resume
<6>[ 21.224273] mmc0: Deferred resume failed
<3>[ 21.226348] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.226806] mmc0: Controller has been reset
<6>[ 21.227111] mmc0: Worked around bug 1535304
<3>[ 21.228393] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.228942] mmc0: Controller has been reset
<6>[ 21.229156] mmc0: Worked around bug 1535304
<6>[ 21.235961] mmc0: reinit card
<4>[ 21.236083] mmc0: Starting deferred resume
<6>[ 23.274291] mmc0: Deferred resume failed
Perhaps I should have posted in General?
I am reading the thread at http://forum.xda-developers.com/showthread.php?t=1039504&page=3, which appears to be in General, about fried eMMCs in the Desire.
If anyone reading this can verify that my phone indeed has that condition (fried eMMC), thanks!
Hello.
So - I bought this phone about ~8/9 months ago (in april 2014). I installed Cyanogenmod 11 by Maclaw twice, but there were problems with stability, so in August I decided to install AOSP by salvo (slv96).
Since then, everything was okay, until the middle of January (this year), when the phone... just restarted. It did not surprise me, because it restarted couple of times before. Unfortunately, it happend again - twice - so I started looking for possible causes. I noticed that the phone can boot normally, I can even use it for some time, but when I want to change something on it, it restarts, probably getting a kernel panic.
I tried to delete all data, or "triple wipe", but after that phone still had untouched ROM, just like it was before. Nothing was removed. So I downloaded Samsung Kies, because I tried to install an "original ROM", but Kies only shows the message "Connecting" and nothing more happens.
Next time I tried the ADB, I reset the flash counter by command:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
then I checked "what happens when I write the command dmesg | grep mmc*", which results in something like this:
Code:
[email protected]:/ # dmesg | grep mmc*
dmesg | grep mmc*
<7>[ 0.000000] Normal zone: 1248 pages used for memmap
<7>[ 0.000000] HighMem zone: 286 pages used for memmap
<5>[ 0.000000] Kernel command line: cachepolicy=writealloc mpcore_wdt.mpcore_margin=359 root=/dev/ram0 rw rootwait crash_reboot=yes crash_dump=no init=initconsole='null' [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] vmalloc=264M jig_smd=0 lpm_boot=0 checksum_pass=1 checksum_done=1 sec_debug.enable=0 sec_debug.enable_user=0 androidboot.serialno=473700e240071108 board_id=12 startup_graphics=1 logo. lcdtype=8 sbl_copy=1
<6>[ 0.000000] Console: colour dummy device 80x30
<6>[ 0.322540] print_constraints: dummy:
<6>[ 0.343658] print_constraints: db8500-sva-mmdsp:
<7>[ 0.343688] regulator regulator.9: regulator-db8500-sva-mmdsp-probed
<6>[ 0.343872] print_constraints: db8500-sva-mmdsp-ret:
<7>[ 0.343902] regulator regulator.10: regulator-db8500-sva-mmdsp-ret-probed
<6>[ 0.344329] print_constraints: db8500-sia-mmdsp:
<7>[ 0.344360] regulator regulator.12: regulator-db8500-sia-mmdsp-probed
<6>[ 0.344543] print_constraints: db8500-sia-mmdsp-ret:
<7>[ 0.344604] regulator regulator.13: regulator-db8500-sia-mmdsp-ret-probed
<6>[ 0.772735] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>[ 1.227233] bt404_ts_device 3-0020: send reset command
<6>[ 1.255004] mmci-pl18x sdi2: mmc0: PL180 manf 80 rev4 at 0x80005000 irq 73,-1 (pio)
<6>[ 1.255096] mmci-pl18x sdi2: DMA channels RX dma0chan16, TX dma0chan17
<4>[ 1.298492] mmci-pl18x sdi0: Provided ocr_mask/setpower will not be used (using regulator instead)
<3>[ 1.298645] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<6>[ 1.298950] mmci-pl18x sdi0: mmc1: PL180 manf 80 rev4 at 0x80126000 irq 92,-1 (pio)
<3>[ 1.298980] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<6>[ 1.299072] mmci-pl18x sdi0: DMA channels RX dma0chan18, TX dma0chan19
<3>[ 1.322021] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<3>[ 1.322357] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.322662] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.322967] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.323303] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.323608] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.323913] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.324249] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.324554] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<6>[ 1.368377] mmci-pl18x sdi1: mmc2: PL180 manf 80 rev4 at 0x80118000 irq 82,-1 (pio)
<6>[ 1.368438] mmci-pl18x sdi1: DMA channels RX dma0chan20, TX dma0chan21
<6>[ 1.471282] mmc0: new high speed DDR MMC card at address 0001
<6>[ 1.471771] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
<6>[ 1.471954] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
<6>[ 1.472137] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
<6>[ 1.477600] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17
<6>[ 1.484130] mmcblk0boot1: unknown partition table
<6>[ 1.487213] mmcblk0boot0: unknown partition table
<3>[ 1.487823] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.488159] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.511444] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.511779] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.512084] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.512390] mmc1: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<4>[ 1.548614] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 1.548614] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073f9c4>] (warn_slowpath_fmt+0x40/0x48)
<6>[ 1.588836] mmio_probe
<6>[ 1.589508] mmio_camera mmio_camera: MMIO driver initialized with minor=42
<6>[ 1.589538] mmio_camera mmio_camera: system_rev 7, NCP6914 Camera Sub-PMIC
<7>[ 1.595886] mmio_cam_power_pin_control pin : 2 , state 1
<7>[ 1.596466] mmio_cam_power_pin_control pin : 2 , state 0
<4>[ 1.624908] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 1.624908] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073f9c4>] (warn_slowpath_fmt+0x40/0x48)
<6>[ 1.636779] asoc: snd-soc-dummy-dai <-> ux500-msp-i2s.0 mapping ok
<4>[ 1.668792] mmc1: host does not support reading read-only switch. assuming write-enable.
<6>[ 1.700103] mmc1: new high speed SDHC card at address 0007
<6>[ 1.700683] mmcblk1: mmc1:0007 SD8GB 7.21 GiB
<6>[ 1.702301] mmcblk1: p1
<6>[ 2.112426] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: errors=panic
<6>[ 2.246673] EXT4-fs (mmcblk0p2): recovery complete
<6>[ 2.247863] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.299285] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p2
<6>[ 2.491821] e2fsck: /dev/block/mmcblk0p2: recovering journal
<6>[ 2.491882] e2fsck: /system/bin/e2fsck: unable to set superblock flags on/dev/block/mmcblk0p2
<6>[ 2.581146] EXT4-fs (mmcblk0p2): recovery complete
<6>[ 2.583099] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.625762] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 2.626617] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.669433] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p4
<6>[ 2.741790] e2fsck: /dev/block/mmcblk0p4: recovering journal
<6>[ 2.741851] e2fsck: /system/bin/e2fsck: unable to set superblock flags on/dev/block/mmcblk0p4
<6>[ 2.781799] EXT4-fs (mmcblk0p4): recovery complete
<6>[ 2.782684] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.803741] EXT4-fs (mmcblk0p7): recovery complete
<6>[ 2.804870] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 2.849517] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p7
<6>[ 2.897705] e2fsck: /dev/block/mmcblk0p7: recovering journal
<6>[ 2.897766] e2fsck: /system/bin/e2fsck: unable to set superblock flags on /dev/block/mmcblk0p7
<6>[ 2.912231] EXT4-fs (mmcblk0p7): recovery complete
<6>[ 2.913024] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: journal_async_commit,errors=panic
<6>[ 2.920623] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: errors=panic
<7>[ 3.355377] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 41301
<7>[ 3.362243] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 40447
<7>[ 3.367767] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64030
<7>[ 3.367858] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64025
<7>[ 3.370513] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 56153
<7>[ 3.374267] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 8012
<6>[ 3.374481] EXT4-fs (mmcblk0p5): 6 orphan inodes deleted
<6>[ 3.374511] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 3.398315] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
<6>[ 3.449951] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p5
<6>[ 3.850677] e2fsck: /dev/block/mmcblk0p5: recovering journal
<6>[ 3.850738] e2fsck: /system/bin/e2fsck: unable to set superblock flags on /dev/block/mmcblk0p5
<7>[ 4.324157] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 41301
<7>[ 4.331481] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 40447
<7>[ 4.337310] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64030
<7>[ 4.337463] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 64025
<7>[ 4.340911] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 56153
<7>[ 4.344512] EXT4-fs (mmcblk0p5): ext4_orphan_cleanup: deleting unreferenced inode 8012
<6>[ 4.344940] EXT4-fs (mmcblk0p5): 6 orphan inodes deleted
<6>[ 4.344970] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 4.365631] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,journal_async_commit,errors=panic
<3>[ 6.199615] u8500_shrm shrm_bus: common receive with l2 header 210 failed
<4>[ 6.279571] [<c0d7bb08>] (dump_stack+0x20/0x24) from [<c073f974>] (warn_slowpath_common+0x64/0x74)
<4>[ 6.279602] [<c073f974>] (warn_slowpath_common+0x64/0x74) from [<c073fa40>] (warn_slowpath_null+0x2c/0x34)
<3>[ 21.941711] end_request: I/O error, dev mmcblk0, sector 3078528
<3>[ 32.071746] end_request: I/O error, dev mmcblk0, sector 3321888
<3>[ 32.073638] end_request: I/O error, dev mmcblk0, sector 3322784
<3>[ 34.127593] end_request: I/O error, dev mmcblk0, sector 2155520
<3>[ 34.253173] end_request: I/O error, dev mmcblk0, sector 3083136
<3>[ 34.792480] end_request: I/O error, dev mmcblk0, sector 1544704
<3>[ 35.217437] end_request: I/O error, dev mmcblk0, sector 3074040
<3>[ 35.709747] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 35.710083] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 35.734436] mmc2: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<6>[ 35.811065] mmc2: new high speed SDIO card at address 0001
<3>[ 36.042938] end_request: I/O error, dev mmcblk0, sector 3071560
<4>[ 36.340393] sdio_reset_comm():
<4>[ 38.452423] Unknown PRIVATE command WLS_BATCHING GET - ignored
<4>[ 38.453887] Unknown PRIVATE command WLS_BATCHING STOP - ignored
<3>[ 44.364715] end_request: I/O error, dev mmcblk0, sector 3689008
<3>[ 44.548583] end_request: I/O error, dev mmcblk0, sector 3724064
<3>[ 62.210357] end_request: I/O error, dev mmcblk0, sector 3716120
<3>[ 62.472076] end_request: I/O error, dev mmcblk0, sector 3690320
<3>[ 62.775665] end_request: I/O error, dev mmcblk0, sector 3716184
<3>[ 75.980651] end_request: I/O error, dev mmcblk0, sector 3724512
<3>[ 82.332397] end_request: I/O error, dev mmcblk0, sector 2794080
<3>[ 84.947631] end_request: I/O error, dev mmcblk0, sector 3876768
<3>[ 84.949829] end_request: I/O error, dev mmcblk0, sector 3875328
<3>[ 84.959594] end_request: I/O error, dev mmcblk0, sector 3869184
<3>[ 84.960906] end_request: I/O error, dev mmcblk0, sector 3866992
<3>[ 84.962799] end_request: I/O error, dev mmcblk0, sector 3871616
<3>[ 84.965332] end_request: I/O error, dev mmcblk0, sector 3866848
<3>[ 84.967163] end_request: I/O error, dev mmcblk0, sector 3866944
<3>[ 84.969177] end_request: I/O error, dev mmcblk0, sector 3870088
<3>[ 84.971954] end_request: I/O error, dev mmcblk0, sector 3878192
<3>[ 84.973846] end_request: I/O error, dev mmcblk0, sector 3877888
<3>[ 84.991668] end_request: I/O error, dev mmcblk0, sector 3867520
<3>[ 84.993743] end_request: I/O error, dev mmcblk0, sector 3871424
<3>[ 84.998046] end_request: I/O error, dev mmcblk0, sector 3886120
<3>[ 85.004394] end_request: I/O error, dev mmcblk0, sector 3866016
<3>[ 100.235717] end_request: I/O error, dev mmcblk0, sector 3716664
<3>[ 100.686798] end_request: I/O error, dev mmcblk0, sector 3716728
<3>[ 107.611114] end_request: I/O error, dev mmcblk0, sector 3723728
<3>[ 116.956024] end_request: I/O error, dev mmcblk0, sector 3725024
<3>[ 117.235870] end_request: I/O error, dev mmcblk0, sector 3716960
<3>[ 117.372741] end_request: I/O error, dev mmcblk0, sector 3725088
<3>[ 123.722656] end_request: I/O error, dev mmcblk0, sector 3717024
<3>[ 123.910125] end_request: I/O error, dev mmcblk0, sector 3079640
<3>[ 128.908752] end_request: I/O error, dev mmcblk0, sector 3079712
<3>[ 129.095489] end_request: I/O error, dev mmcblk0, sector 3079776
<3>[ 129.182556] end_request: I/O error, dev mmcblk0, sector 3079840
<3>[ 129.626342] end_request: I/O error, dev mmcblk0, sector 1546240
<3>[ 132.953887] end_request: I/O error, dev mmcblk0, sector 3725248
<3>[ 132.995880] end_request: I/O error, dev mmcblk0, sector 3079680
<3>[ 133.043151] end_request: I/O error, dev mmcblk0, sector 3079744
<3>[ 133.115478] end_request: I/O error, dev mmcblk0, sector 3079808
<3>[ 146.493164] end_request: I/O error, dev mmcblk0, sector 3079976
<3>[ 156.772979] end_request: I/O error, dev mmcblk0, sector 3085152
<3>[ 189.913391] end_request: I/O error, dev mmcblk0, sector 2504704
<3>[ 223.977478] end_request: I/O error, dev mmcblk0, sector 2798968
<3>[ 455.043640] end_request: I/O error, dev mmcblk0, sector 3410928
<3>[ 455.045532] end_request: I/O error, dev mmcblk0, sector 3417352
<3>[ 455.047393] end_request: I/O error, dev mmcblk0, sector 3451248
<3>[ 455.049499] end_request: I/O error, dev mmcblk0, sector 3362560
<3>[ 455.051147] end_request: I/O error, dev mmcblk0, sector 3343104
<3>[ 455.053039] end_request: I/O error, dev mmcblk0, sector 3481160
<3>[ 455.055145] end_request: I/O error, dev mmcblk0, sector 3341440
<4>[ 1770.800903] Unknown PRIVATE command WLS_BATCHING GET - ignored
<4>[ 1770.802154] Unknown PRIVATE command WLS_BATCHING STOP - ignored
<3>[ 1806.052703] end_request: I/O error, dev mmcblk0, sector 3716824
[email protected]:/ # dmesg | grep mmc* > wat.txt
dmesg | grep mmc* > wat.txt
sh: can't create wat.txt: Read-only file system
write: Broken pipe
I even tried to clear the internal flash memory from Linux Ubuntu by unmounting internal memory card in CWM Recovery and mounting it as Linux drive, but when I excecuted
Code:
dd if=/dev/zero of/dev/sdb1
and waited for ~2 hours, unmounted drive in Linux and mounted it back in Recovery, nothing happend. It still shows than at sdcard is AOSP.
What I can do with this phone? I have no warranty anymore, because the original system worked very poorly and even if I wanted to - I can't install it, because Samsung Kies does not recognise the phone. Is there any step-by-step tutorial about wiping contents of internal memory card and installing Android on sd card?
Did you try odin?
Yes, I tried ~week ago 4 times. Twice with version 3.10 and twice with Odin 3 v1.85. Installing stock ROM has not helped, I still have AOSP.
But how? There was an error in odin ot what?
Sent from my C1905 using XDA Free mobile app
There was no error, Odin just "stated" that everything was installed correctly, but when I reboot the phone, it still got unchanged AOSP ROM.
Hi All,
Anybody could help me coz got a bit of problem here.
Rom: stock GB 2.3.5 I8150XXKI8
It seems that everything is read-only except the external SD. After reboot, revert back to previous state.
Unable to go to recovery mode.
Done many success flashing in download mode ( flash stock,recovery) though and nothing. it just revert back to the previous state
Reformat usb storage also does not work.
Alot of apps force close.
Long pause at the samsung w logo.
mmcblk0p17 and mmcblk0p27 seems to have an error from below dmesg output.
Needs to confirm with anyone.
Thanks.
<3>[ 3.161895] init: MOUNT NAME /dev/block/mmcblk0p15
<3>[ 3.161925] init: SEC_DEVENC ***[/dev/block/mmcblk0p15][0]
<6>[ 3.181334] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1
<3>[ 3.181395] init: MOUNT NAME /dev/block/mmcblk0p12
<3>[ 3.181426] init: SEC_DEVENC ***[/dev/block/mmcblk0p12][0]
<6>[ 3.186003] EXT4-fs (mmcblk0p12): barriers disabled
<6>[ 3.202056] EXT4-fs (mmcblk0p12): recovery complete
<6>[ 3.202697] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: barrier=0
<3>[ 3.202758] init: MOUNT NAME /dev/block/mmcblk0p16
<3>[ 3.202758] init: SEC_DEVENC ***[/dev/block/mmcblk0p16][0]
<6>[ 3.205413] EXT4-fs (mmcblk0p16): barriers disabled
<3>[ 3.215056] init: [boot time] finish coldboot
<6>[ 3.216735] EXT4-fs (mmcblk0p16): recovery complete
<6>[ 3.217314] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: barrier=0
<4>[ 3.220519] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.221129] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.238127] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.238738] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.248168] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.249205] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.258544] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.259154] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.271483] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.271514] mmc2: new high speed SDHC card at address 1234
<6>[ 3.271605] sdio_al mmc2:1234: Probing..
<6>[ 3.271605] sdio_al mmc2:1234: Not an SDIO card
<6>[ 3.271941] mmcblk1: mmc2:1234 SA16G 14.6 GiB
<6>[ 3.272124] mmcblk1: p1
<4>[ 3.276579] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.277220] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<3>[ 3.278319] init: [disk_config] :::: /dev/block/mmcblk0p27 (ext4)(opt (null)):::::
<3>[ 3.278349] init: internal_storage : ext_identify open
<3>[ 3.278380] init: internal_storage : ext_identify lseek
<3>[ 3.279234] init: internal_storage : ext_identify open
<3>[ 3.279265] init: internal_storage : ext_identify lseek
<3>[ 3.279295] init: MOUNT NAME /dev/block/mmcblk0p27
<3>[ 3.279326] init: SEC_DEVENC ***[/dev/block/mmcblk0p27][0]
<3>[ 3.279357] init: failed that mount s:'/dev/block/mmcblk0p27', t:'/efs', f:ext4 ,op null) (Device or resource busy)
<3>[ 3.279418] init: [disk_config] :::: /dev/block/mmcblk0p17 (ext4)(opt (null)):::::
<3>[ 3.279448] init: internal_storage : ext_identify open
<3>[ 3.279479] init: internal_storage : ext_identify lseek
<3>[ 3.280852] init: internal_storage : ext_identify open
<3>[ 3.280882] init: internal_storage : ext_identify lseek
<3>[ 3.282439] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p17 (ext4):::::
<3>[ 3.282836] init: [disk_config] DEVENC : not mormal [0]
<3>[ 3.282836] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 3.644621] mmc1 data status (0x8)
<3>[ 3.644652] mmc1: Data timeout opcode = 0x12
<3>[ 3.644682] mmc1: DMA channel flushed (0x80000004)
<3>[ 3.644682] Flush data: 0000c003 4f713000 00000000 00200040 00290028 00002003
<4>[ 3.645018] mmcblk0: retrying using single block read
<3>[ 4.017912] init: SEC_DEVENC check crypt status
<3>[ 4.017973] init: MOUNT NAME /dev/block/mmcblk0p17
<3>[ 4.017973] init: SEC_DEVENC ***[/dev/block/mmcblk0p17][1]
<3>[ 4.017973] init: SEC_DEVENC checkCrypt main
<3>[ 4.316953] mmc1 data status (0x8)
<3>[ 4.316953] mmc1: Data timeout opcode = 0x12
<3>[ 4.316984] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.316984] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.317320] mmcblk0: retrying using single block read
<3>[ 4.519804] mmc1 data status (0x8)
<3>[ 4.519834] mmc1: Data timeout opcode = 0x12
<3>[ 4.519865] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.519865] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.520170] mmcblk0: retrying using single block read
<3>[ 4.727903] mmc1 data status (0x8)
<3>[ 4.727903] mmc1: Data timeout opcode = 0x12
<3>[ 4.727934] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.727934] Flush data: 0000c003 4f713000 00000000 00200040 04690468 00002003
<4>[ 4.728300] mmcblk0: retrying using single block read
<3>[ 5.135984] mmc1 data status (0x8)
<3>[ 5.136015] mmc1: Data timeout opcode = 0x12
<3>[ 5.136045] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.136045] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 5.136381] mmcblk0: retrying using single block read
<4>[ 5.233640] EXT4-fs (mmcblk0p17): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.234983] EXT4-fs (mmcblk0p17): recovery complete
<6>[ 5.235959] EXT4-fs (mmcblk0p17): mounted filesystem with ordered data mode. Opts: errors=continue
<3>[ 5.236020] init: SEC_DEVENC uncrypted parition mounted
<4>[ 5.237577] param_init !
<3>[ 5.237729] init: [boot time] processing action 0x3b6d8 (post-fs)
<3>[ 5.237760] init: [disk_config] :::: /dev/block/mmcblk0p28 (vfat)(opt (null)):::::
<3>[ 5.240323] init: oem_name (android )
<3>[ 5.244382] init: oem_name (android )
<3>[ 5.244474] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p28 (vfat):::::
<3>[ 5.244901] init: [disk_config] DEVENC : not mormal [0]
<3>[ 5.244932] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 5.599302] mmc1 data status (0x8)
<3>[ 5.599302] mmc1: Data timeout opcode = 0x12
<3>[ 5.599332] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.599332] Flush data: 0000c003 4f713000 00000000 00200040 02690268 00002003
<4>[ 5.599698] mmcblk0: retrying using single block read
<3>[ 6.010587] mmc1 data status (0x8)
<3>[ 6.010587] mmc1: Data timeout opcode = 0x12
<3>[ 6.010617] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.010617] Flush data: 0000c003 4f713000 00000000 00200040 02790278 00002003
<4>[ 6.010984] mmcblk0: retrying using single block read
<3>[ 6.435544] mmc1 data status (0x8)
<3>[ 6.435544] mmc1: Data timeout opcode = 0x12
<3>[ 6.435574] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.435574] Flush data: 0000c003 4f713000 00000000 00200040 01b901b8 00002003
<4>[ 6.435910] mmcblk0: retrying using single block read
<3>[ 6.638852] mmc1 data status (0x8)
<3>[ 6.638883] mmc1: Data timeout opcode = 0x12
<3>[ 6.638883] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.638913] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 6.639249] mmcblk0: retrying using single block read
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
ozgurakman said:
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
Click to expand...
Click to collapse
Hi,
Thanks for the reply and good for you ozgurakman coz able to go to recovery mode. But I'm unable to go to recovery mode to repair the system though. Press the 3 recovery buttons. and just a screen flicker. It seem that my recovery corrupt also. Even after I reflash the recovery block only, still nada.
It seem that I'm running out options though. Anybody?
Did you tried to install cwm?
ozgurakman said:
Did you tried to install cwm?
Click to expand...
Click to collapse
yup also trying that one. also using the dd command in case the odin not working.
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
ozgurakman said:
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
Click to expand...
Click to collapse
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
zaffrullah said:
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
Click to expand...
Click to collapse
If I helped you, please press to thanks button
Last advise: try to different Odin version, different ops, different Rom.
Select to wipe everything.