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!
Hello, everyone,
Yesterday while browsing, my phone freezed. After restart, it went to bootloop.
I was using CWM+ Maclaw's CM11 (not the latest).
I reflashed my rom, but Gapps kept FC.
I reflashed Gapps (2 different builds)- same FC's.
At some point I managed to boot OK without Gapps.
I tried formatting data/dalvik- no change.
After some more digging- I messed up ( formatted system, modemfs,cache,data...)..
Now I can only boot into CWM and into Recovery.
When in Recovery, the following message appears:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open/cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open/cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open/cache/recovery/last_install
I tried to flash stock rom using Odin (with/without PIT); other CWM, TWRP with no luck. No matter if it's the green PASS, or blue RESET at the end .
I have ADB, I've used it in the past...
I think I've checked my emmc with adb- here's the code (I don't know what/where to look at?)
dmesg | grep mmc0
<6>[ 1.252746] mmci-pl18x sdi2: mmc0: PL180 manf 80 rev4 a
,-1 (pio)
<3>[ 1.288299] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.288726] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.311920] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<3>[ 1.312316] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.312713] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313110] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313476] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313873] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.314270] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.314666] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.315063] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<6>[ 1.471466] mmc0: new high speed DDR MMC card at addres
<6>[ 1.472473] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
<6>[ 1.472778] mmcblk0boot0: mmc0:0001 SEM04G partition 1
<6>[ 1.473022] mmcblk0boot1: mmc0:0001 SEM04G partition 2
<3>[ 2.545837] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 2.647064] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.748718] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.850280] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.951568] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.052856] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.154174] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.255462] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.356811] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.501464] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 3.602722] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.703857] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.921295] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 4.022216] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 4.123413] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 5.686920] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 5.788208] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 5.889678] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.116516] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 6.217834] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.319305] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.593414] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 6.694732] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.796325] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.063079] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 7.164337] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.266326] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.591979] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 7.693298] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.795074] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 8.061920] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 8.163146] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 8.265136] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
I used this link, and I'm not quite sure I did it right...
Any suggestions ? Is it hardware or there is still hope? The fact that I can access Recovery and DL mode plus ADB still sees my phone is encouraging, right?
Did you try to flash russian "repair rom" with odin? It makes repart in semi-hopeless situations..it differs from newer odin roms, that is.
Thank you for your reply.
Never heard of it. I'll give it a try after work.
As far as I can understand, my partition is messed up, my emmc seems to be OK, but I can't flash any rom ( custom or original ), or any recovery...
p.s. Which one is the "russian rom" ? Is it stock SER rom, or some kind of MODDED Rom?
Is it MG2 ?
I tried MB4 - Passed in Odin, but without any change. Still on bootloop, still with CWM recovery.
Next is MG2... Same.
I'll try to downgrade to GB, it's the last thing I can think of.
Any help is much appreciated.
p.p.s TWRP instal with ODIN- no change, still on CW
Sir, here's the thing(i hope, that link's providing proper rom I am talking about..):
http://d-h.st/AZN
(resumable source)
If this will not work, i'd be worried.
You need to carefully add EVERYTHING to odin.
If it works, you need to - flash any jb you want, then update.zip(temp cwm) and do what you want, you are saved.
I did many stupid things with my machine, and this rom was always an lantern in the dark.
Thing is, that "russian rom" has unique set of files, that seem to heal any ace2 issues after problematic flashes.
Imho, every ace2 user should keep this rom on HDD(day, when it's gone is closer, and closer...keep it on your laptops/desktops, guys).
Downloading... I tried couple of LK6's (one with 1 file, and one with the CODE, PIT and CSC files).
Odin 1.85 states "pass" , while 3.09 stays on RESET!.
It's like the phone rejects anything I'm trying to flash.
I'm going to try with ODIN 1.85;1.86 and 3.09.
Edit: Still on bootloop. .
Any other ideas, guys ?
In desperate move, I can try to change the size of the partitions with adb...
p.s. I have trouble finding stock recovery.img to push with adb... Can anyone help ?
grundio said:
Downloading... I tried couple of LK6's (one with 1 file, and one with the CODE, PIT and CSC files).
Odin 1.85 states "pass" , while 3.09 stays on RESET!.
It's like the phone rejects anything I'm trying to flash.
I'm going to try with ODIN 1.85;1.86 and 3.09.
Edit: Still on bootloop. .
Any other ideas, guys ?
In desperate move, I can try to change the size of the partitions with adb...
p.s. I have trouble finding stock recovery.img to push with adb... Can anyone help ?
Click to expand...
Click to collapse
So, you did not use my advice? Ok, have a luck.
xo.en said:
So, you did not use my advice? Ok, have a luck.
Click to expand...
Click to collapse
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
grundio said:
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
Click to expand...
Click to collapse
Wipe data in recovery..
E: oh i didn't see 3 part. But still try :/
I can wipe only /boot in recovery. Wipe data;cache;system;partition commands results in error or just with "Formatting.." and blank progress bar.
I am searching recovery.img to flash with adb. If i try to flash recovery in CWM, the screen blinks couple of times and nothing happens.
grundio said:
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
Click to expand...
Click to collapse
Now, this is weird...you may try to manually mess with partitions
http://forum.xda-developers.com/showthread.php?t=2596521
then flash sth with odin(it will repart machine again, so it may fix your problem then).
Btw, it does not matter, if russian rom is not starting, flash newer one after flashing russian.
Thanks for your reply. I've looked at the same thread in your link and I'll try it.
I'll try with flashing newer rom after the LK6 too. It's that corrupted CWM recovery that's stuck in the memory that grinds my gears.
I'm still trying to figure out why this happened... I'll post results in couple of days.
Ok, I'm currently trying to repartition the Ace 2...
In the process I get the following error:
print
Error: /dev/block/mmcblk0: unrecognised disk label
The same error with "rm" command...
I think I'm starting to give up on my Ace 2... Everything I tried is a deadend.
Hm-m.. That's strange...
I can install Temp CWM 6.0.2.8 (the screen blinks couple of times and it loads). The problem is I still can't mount anything. But it's working smoother than 6.0.4.8 (which I want to get rid of).
Now, I'm searching for .zip TWRP recovery (or even stock recovery .zip) to flash. I tried several types of kernels, but with no luck (the screen freezes/is loading on "Installing zip..." and nothing happens), it still can't mount/format anything in the menu.
Any thoughts ?
Dead...
Well, my Ace 2 is completely dead now (no signs of life at all) - no dw/recovery mode, the battery is not charging.
I feel bad for the phone, I really liked it.
Thank's for the help, guys. I appreciate it :good:
Hi,
recently my Note 2 just died spontaneously. It was running as normal, suddenly it was off and instead of booting, it just hangs infinitely at the "Galaxy Note 2"-bootlogo.
I can still boot to recovery and download mode.
adb analysis shows this:
Code:
~ # dmesg | grep mmc0
<3>[ 2.034803] c2 mmc0: Version ID 0x5342240a.
<6>[ 2.035079] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.036574] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.065840] c0 mmc0: cmd 52 response timeout error
<3>[ 2.066686] c0 mmc0: cmd 52 response timeout error
<3>[ 2.070765] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071614] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072445] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073280] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074116] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074978] c0 mmc0: cmd 55 response timeout error
<3>[ 2.075840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.076699] c0 mmc0: cmd 55 response timeout error
<3>[ 2.077558] c0 mmc0: cmd 55 response timeout error
<3>[ 2.096727] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.096757] c0 mmc0: VTU00M: 15010056545530304df1e7ae5fd88fbf
<3>[ 2.179611] c0 mmc0: cmd 13 response timeout error
<6>[ 2.179697] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 2.180533] c0 mmc0: cmd 6 response timeout error
<3>[ 2.181359] c0 mmc0: cmd 6 response timeout error
<3>[ 2.182182] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183006] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183052] c0 mmc0: error -110 whilst initialising MMC card
Code:
~ # cat /proc/partitions
major minor #blocks name
Code:
~ # ls /dev/block
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
I was running CWM recovery and resurrection remix 5.6.9 (marshmallow). The flash of this ROM was maybe a week ago.
Recovery log is attached
Code:
mount: mounting /dev/block/mmcblk0p12 on /cache failed: no such file or directory
Does this mean that my eMMC is dead? Sudden death syndrome? Download mode still shows the device name. I'm wondering why I can still boot to recovery.
xkawer said:
Hi,
recently my Note 2 just died spontaneously. It was running as normal, suddenly it was off and instead of booting, it just hangs infinitely at the "Galaxy Note 2"-bootlogo.
I can still boot to recovery and download mode.
adb analysis shows this:
Code:
~ # dmesg | grep mmc0
<3>[ 2.034803] c2 mmc0: Version ID 0x5342240a.
<6>[ 2.035079] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.036574] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.065840] c0 mmc0: cmd 52 response timeout error
<3>[ 2.066686] c0 mmc0: cmd 52 response timeout error
<3>[ 2.070765] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071614] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072445] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073280] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074116] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074978] c0 mmc0: cmd 55 response timeout error
<3>[ 2.075840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.076699] c0 mmc0: cmd 55 response timeout error
<3>[ 2.077558] c0 mmc0: cmd 55 response timeout error
<3>[ 2.096727] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.096757] c0 mmc0: VTU00M: 15010056545530304df1e7ae5fd88fbf
<3>[ 2.179611] c0 mmc0: cmd 13 response timeout error
<6>[ 2.179697] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 2.180533] c0 mmc0: cmd 6 response timeout error
<3>[ 2.181359] c0 mmc0: cmd 6 response timeout error
<3>[ 2.182182] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183006] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183052] c0 mmc0: error -110 whilst initialising MMC card
Code:
~ # cat /proc/partitions
major minor #blocks name
Code:
~ # ls /dev/block
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
I was running CWM recovery and resurrection remix 5.6.9 (marshmallow). The flash of this ROM was maybe a week ago.
Recovery log is attached
Code:
mount: mounting /dev/block/mmcblk0p12 on /cache failed: no such file or directory
Does this mean that my eMMC is dead? Sudden death syndrome? Download mode still shows the device name. I'm wondering why I can still boot to recovery.
Click to expand...
Click to collapse
Have a look to this thread
http://forum.xda-developers.com/showthread.php?t=2501951
dr.harsh said:
Have a look to this thread
http://forum.xda-developers.com/showthread.php?t=2501951
Click to expand...
Click to collapse
Unfortunately, I can't access the drive on my PC. When I click on "mount system/cache/data/..." I just get "Error mounting /system/...". When I click "mount USB storage", nothing happens. The phone gets listed as "Universal Serial Bus devices/GT-N7100" in Device Manager, but explorer doesn't show it as a drive. The Samsung USB driver is installed, odin also detects it in download mode.
I'll try if I can flash stock with odin, should I try repartition with pit?
Flashing stock without repartition fails:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)