Related
Hi everyone,
I have a Asian build HTC Desire Z from Singapore. I have previously prem-root the phone. Today i tried to flash the rom to the new Bulletproof MIUI rom but after flashing it using the latest Clockworkmod Recovery, the phone keep restarting after the MIUI start screen.
I went back to Clockworkmod Recovery and realises there is a problem mounting the "/cache", "/system" etc.. Here's some of the info i manage to see..
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 20:10:38
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
I read in some thread to use a PC10IMG.zip to restore back the original rom. I tried to flash this using Clockworkmod Recovery. And the next reboot i got a new problem:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
After a while, i got this:
Model ID Incorrect!
Update Fail!
Press <POWER> to reboot.
Can some kind soul please advise me what i can do now? I am really lost..
Try taking the PC10IMG off of your SD card and then boot into recovery and install CM7 or something, just to see if that works
My best guess would be this: The PC10IMG was applied, but you cannot apply it again, however you can`t get past bootloader if you have a PC10IMG on your SD card so see if you can get into clockwork again if you take it off
my guess is that your emmc chip is fried... excuse me for i am a pessimist
———————————————
sent from a phone... 'nuf said
btw... justin bieber sucks
———————————————
Thanks for your suggestion, noneabove..
I removed PC10IMG from my SD and is now able to go back into CWM.. i tried to restore to one of my backups for my previous rom.. but i got this:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while formatting /system!
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
What's wrong? What else can i do now?
gallen23 said:
Thanks for your suggestion, noneabove..
I removed PC10IMG from my SD and is now able to go back into CWM.. i tried to restore to one of my backups for my previous rom.. but i got this:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while formatting /system!
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
What's wrong? What else can i do now?
Click to expand...
Click to collapse
hmm that's rather worrisome.. What version of CWM are you currently running and do you remember which one you were running when you fist did the backup ?
I was using CWM 5.0.2.7 now and during my backup..
Hm ...try to flash a different rom (not restoring a backup). Hopefully your emmc chip isn't fried...
Sent from my HTC Vision using XDA App
How do i know whether my eMMC chip is fried? If it is, can i do anything to salvage the phone?
I have tried use Fastboot USB to push a recovery.img into the phone but i get an error:
"FAILED: remote not allowed"
I cant seem to get adb to connect to my phone. Only Fastboot was able to connect the phone.
someone pls help...
gallen23 said:
How do i know whether my eMMC chip is fried? If it is, can i do anything to salvage the phone?
I have tried use Fastboot USB to push a recovery.img into the phone but i get an error:
"FAILED: remote not allowed"
I cant seem to get adb to connect to my phone. Only Fastboot was able to connect the phone.
someone pls help...
Click to expand...
Click to collapse
See if you can put a rom zip directly on the sd card by putting it into a computer and then flash it on the phone through CWM
Thanks for your suggestion, noneabove.. <br />
<br />
I removed PC10IMG from my SD and is now able to go back into CWM.. i tried to restore to one of my backups for my previous rom.. but i got this:<br />
<br />
Checking MD5 sums...<br />
Erasing boot before restore...<br />
Restoring boot image...<br />
Restoring system...<br />
Error while formatting /system!<br />
E: Can't mount /cache/recovery/log<br />
E: Can't open /cache/recovery/log<br />
E: Can't mount /cache/recovery/last_log<br />
E: Can't open /cache/recovery/last_log<br />
<br />
What's wrong? What else can i do now?
Click to expand...
Click to collapse
I'm afraid this means that your emmc is fried. I suggest going to the #g2root irc channel and they will be able to confirm it for you.
Sadly there is nothing that can be done apart from sending it in to HTC for a warranty repair.
Sent from my HTC Desire S using Tapatalk
cjward23 said:
I'm afraid this means that your emmc is fried. I suggest going to the #g2root irc channel and they will be able to confirm it for you.
Sadly there is nothing that can be done apart from sending it in to HTC for a warranty repair.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I think he's right. Sorry man!
I managed to get adb to work and tried to use "dmesg | grep mmc0" to see if my eMMC is fried. I got the following... anyone understand what its means?
C:\android-sdk\platform-tools\CWM Recovery>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.230957] mmc0: No card detect facilities available
<6>[ 7.231536] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.231781] mmc0: Platform slot type: MMC
<6>[ 7.231933] mmc0: 4 bit data mode disabled
<6>[ 7.232055] mmc0: 8 bit data mode enabled
<6>[ 7.232330] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.232482] mmc0: Slot eject status = 0
<6>[ 7.232727] mmc0: Power save feature enable = 1
<6>[ 7.232849] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2a538000
<6>[ 7.233123] mmc0: DM cmd busaddr 0x2a538000, cmdptr busaddr 0x2a538300
<6>[ 7.386810] mmc0: new high speed MMC card at address 0001
<6>[ 7.388244] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 8.616973] mmc0: Failed to get card ready i = 111615
<6>[ 8.617218] mmc0: reinit card
<4>[ 8.617340] mmc0: Starting deferred resume
<6>[ 10.657073] mmc0: Deferred resume failed
<3>[ 10.994812] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.995239] mmc0: Controller has been reset
<6>[ 10.995544] mmc0: Worked around bug 1535304
<3>[ 10.997039] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.997467] mmc0: Controller has been reset
<6>[ 10.997680] mmc0: Worked around bug 1535304
<6>[ 11.004547] mmc0: reinit card
<4>[ 11.004669] mmc0: Starting deferred resume
<6>[ 13.037139] mmc0: Deferred resume failed
<3>[ 13.134613] mmc0: DMA channel flushed (0x80000004)
<6>[ 13.135070] mmc0: Controller has been reset
<6>[ 13.135253] mmc0: Worked around bug 1535304
<3>[ 13.136749] mmc0: DMA channel flushed (0x80000004)
<6>[ 13.137176] mmc0: Controller has been reset
<6>[ 13.137481] mmc0: Worked around bug 1535304
<6>[ 13.144287] mmc0: reinit card
<4>[ 13.144409] mmc0: Starting deferred resume
<6>[ 15.177154] mmc0: Deferred resume failed
<3>[ 15.348083] mmc0: DMA channel flushed (0x80000004)
<6>[ 15.348510] mmc0: Controller has been reset
<6>[ 15.348693] mmc0: Worked around bug 1535304
<3>[ 15.350311] mmc0: DMA channel flushed (0x80000004)
<6>[ 15.350738] mmc0: Controller has been reset
<6>[ 15.350921] mmc0: Worked around bug 1535304
<6>[ 15.357757] mmc0: reinit card
<4>[ 15.358001] mmc0: Starting deferred resume
<6>[ 17.397155] mmc0: Deferred resume failed
~ #
Sorry to say, but the
mmc0: Deferred resume failed
means its fried.
Youu'll have to get a replacement, nothing you can do about it.
-Nipqer
still here... and i feel like i'm invisible... i say things that i'm sure about it.... that exact same thing happened to my friend... and i spoke to #g2root and after some tests... my friend's emmc chip is fried...
btw, i was the first one to inform you... lol
———————————————
sent from a phone... 'nuf said
btw... justin bieber sucks
———————————————
Thanks guys.. i was still hoping for a miracle..
I thought you need a goldcard to flash stock rom if the CID is incorrect
I thought you need a goldcard to flash stock rom if the CID is incorrect
It's the emmc chip
Sent from my SAMSUNG-SGH-T989 using xda premium
My inc2 is always at the htc face, i have tried the RUU, with the USB, and also tried the rom.zip to TF card,with the PG32IMG.zip.
but they did not work.
I can go into the hboot and recovery.
it is s-off.
and now what else can I do.
thanks!!!!!!!!!
[update] i just found that i can only use the cm9 rom.
http://forum.xda-developers.com/showthread.php?t=1561816
so, what the difference of CM9 and others?
Go into recovery.. wipe all data and then flash a rom...
Sent from my Incredible 2 using Tapatalk 2
THE PG32IMG has to be installed from the bootloader. make sure it doesn.t have two zips on it : power down phone hold power button and volume down at same time to get bootloader and if the zip on ROOT of sd card is ok it will pick it up and install it.
what rom are you running now
i have tried a few roms, and today i use the PG32IMG.zip from the forum
this link. http://forum.xda-developers.com/showthread.php?t=1599767
it still does not work.
i am very very puzzle...
i have tried "dmesg | grep mmc0" on adb shell
will u tell me sth from the following information?
<3>[ 10.749847] mmc0: No card detect facilities available
<6>[ 10.750488] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.750640] mmc0: Platform slot type: MMC
<6>[ 10.750762] mmc0: 4 bit data mode disabled
<6>[ 10.751007] mmc0: 8 bit data mode enabled
<6>[ 10.751159] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.751403] mmc0: Slot eject status = 0
<6>[ 10.751525] mmc0: Power save feature enable = 1
<6>[ 10.751647] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x2a4b0000
<6>[ 10.751953] mmc0: DM cmd busaddr 0x2a4b0000, cmdptr busaddr 0x2a4b0300
<4>[ 10.864257] mmc0: high speed mode max_dtr = 50000000
<4>[ 10.864593] mmc0: host does not support reading read-only switch. assuming
write-enable.
<6>[ 10.864807] mmc0: new high speed SDHC card at address aaaa
<6>[ 10.865875] mmcblk0: mmc0:aaaa SE04G 3.69 GiB
Does recovery say anything when you try to install roms?
Sent from here
i can flash all the roms of IC2.
and i also can change different kinds of recoveries.
the rec works well.
anyone can help me ?
i have no idea for a few days already.
thanks .
Maybe your partitions are ext4? Try converting back to ext3
Sent from my Xoom using XDA Premium HD app
Use 4ext recovery man... it auto converts it
Sent from my Incredible 2 using Tapatalk 2
it should not be the matter of filesystem.
i have changed Ext3 and ext4 for a try , it didn't work.
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)
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, 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!