Develop Bugs

[Q] HTC Desire Z brick? Model ID Incorrect..

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

[Q] [Hlep]Can only use the CM9 Rom. others stuck at HTC page

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.

[Q] sd-ext remounted as read-only on connectivity changes

Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.

Need some HELP! Possible corrupt partitions?

Hey everyone, today I started having some really horrible problems with my G2. It started when I woke up and noticed that the phone was powered OFF, which was not normal. Pressing the power button was unable to turn it on, but pulling the battery worked fine.
Everything was normal for a couple hours, but then I began getting random freezes. At least they seemed random, but I was able to reproduce it fairly consistently by turning the screen off and then on a few moments later.
Ok I thought, haven't wiped in a while (Currently on Mimicry 1.4 using 4EXT recovery), so in I went to the Superwipe. Flashing the Superwipe failed. This is the error I see (and have NEVER seen before)
E:Error in /sdcard/SuperWipeG2+ext4.zip
(Status 1)
Installation aborted
So I just went in and did a basic wipe everything and reinstall the ROM, unfortunately this leads to just a white HTC screen.
Flash a Nandroid? Nope, below is the error I see
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error while formatting /system!
I feel like somehow my file system got corrupted, but unlike using Odin with the Vibrant I'm unsure how to fix this on the Vision. Anybody?

If you're in recovery, hook the phone up to your computer and run these two commands:
adb shell
dmesg | grep mmc0
if you see something like:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Then it means your internal memory (emmc) is fried/dead.
You can do the following two commands:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
To see if you have the 'good batch' SEM04G chip, or if you were yet another victim of the faulty 'bad batch' of M4G2DE chips

kbeezie said:
If you're in recovery, hook the phone up to your computer and run these two commands:
adb shell
dmesg | grep mmc0
if you see something like:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Then it means your internal memory (emmc) is fried/dead.
You can do the following two commands:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
To see if you have the 'good batch' SEM04G chip, or if you were yet another victim of the faulty 'bad batch' of M4G2DE chips
Click to expand...
Click to collapse
Thanks for helping out. This is what I get with your first command.
<3>[ 7.968688] mmc0: No card detect facilities available
<6>[ 7.969268] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.969512] mmc0: Platform slot type: MMC
<6>[ 7.969665] mmc0: 4 bit data mode disabled
<6>[ 7.969909] mmc0: 8 bit data mode enabled
<6>[ 7.970031] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.970275] mmc0: Slot eject status = 0
<6>[ 7.970428] mmc0: Power save feature enable = 1
<6>[ 7.970550] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0fffb000
<6>[ 7.970825] mmc0: DM cmd busaddr 0x0fffb000, cmdptr busaddr 0x0fffb300
<6>[ 8.136444] mmc0: new high speed MMC card at address 0001
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
And with your second
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
Looking good I think?

Nospin said:
Thanks for helping out. This is what I get with your first command.
<3>[ 7.968688] mmc0: No card detect facilities available
<6>[ 7.969268] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.969512] mmc0: Platform slot type: MMC
<6>[ 7.969665] mmc0: 4 bit data mode disabled
<6>[ 7.969909] mmc0: 8 bit data mode enabled
<6>[ 7.970031] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.970275] mmc0: Slot eject status = 0
<6>[ 7.970428] mmc0: Power save feature enable = 1
<6>[ 7.970550] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0fffb000
<6>[ 7.970825] mmc0: DM cmd busaddr 0x0fffb000, cmdptr busaddr 0x0fffb300
<6>[ 8.136444] mmc0: new high speed MMC card at address 0001
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
And with your second
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
Looking good I think?
Click to expand...
Click to collapse
So looks like the internal memory isn't fried.
Which recovery are you using? clockworkmod or 4EXT Touch Recovery (I much prefer the latter, but you're probably using CWM if you have to use that superwipe zip).

4EXT Touch, I just use the superwipe zip out of habit.
What would you suggest I do to wipe the slate clean? It certainly seems like something is corrupted. When trying a Wipe Data/Factory Reset in 4EXT I get this.
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
So it seems mmcblk0p25 through 27 are all failing out.

Since you're using 4EXT, I recommend repartitioning your phone to see if that fixes it. If not, then hopefully you just have a bad download and redownloading the ROM can fix it.
Sent from Spaceball One.

Nada.
After full wipes of everything (including the SD card) I did manage to get rid of the mmcblk errors for a time (they came back, usually after a reboot or too many actions in recovery). After flashing Mimicry I do manage to get past the HTC screen, but I get an endless boot animation. Pulling the battery during an endless animation prompts a normal startup (including the "Android is Upgrading" dialog), but it begins the endless boot animation again after completion.
Ughhhhh. I feel like my salvation is in adb, but i'm just not very familiar with the commands that might solve this....
Edit- whoa whoa whoa, we may have something here. Give me a few.
Edit- I managed to achieve the "Welcome" screen of Mimicry. But I got a barrage of process.acore/Calender/Contacts/Googleeverything force closes.Then it froze.
Edit- And I may have full boot. Going to let it sit for 10 minutes before I attempt anything. What scares me is I never determined the cause of this.....

if your still having problems and the above didn't fix anything do the following.
boot to recovery and reformat everything to ext4 (execpt the fat32 partition of sd card)
try flashing a stable rom again
if problem still persists then I suggest booting into fastboot and flash your spl again (assuming you have eng s-off)
fastboot devices
(if you see yours continue)
fastboot -w
fastboot flash bootloader XXX.img
fastboot reboot bootloader
(of course rename the XXX to whatever you have image named, have it in the same folder as fastboot.exe)
now boot to recovery, you may need to reformat recovery, go for it, now flash rom of choice
hope your phone is working without all this but if not the above should do the trick
Sent from my HTC Vision using xda premium

Nospin said:
Hey everyone, today I started having some really horrible problems with my G2. It started when I woke up and noticed that the phone was powered OFF, which was not normal. Pressing the power button was unable to turn it on, but pulling the battery worked fine.
Everything was normal for a couple hours, but then I began getting random freezes. At least they seemed random, but I was able to reproduce it fairly consistently by turning the screen off and then on a few moments later.
Ok I thought, haven't wiped in a while (Currently on Mimicry 1.4 using 4EXT recovery), so in I went to the Superwipe. Flashing the Superwipe failed. This is the error I see (and have NEVER seen before)
E:Error in /sdcard/SuperWipeG2+ext4.zip
(Status 1)
Installation aborted
So I just went in and did a basic wipe everything and reinstall the ROM, unfortunately this leads to just a white HTC screen.
Flash a Nandroid? Nope, below is the error I see
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error while formatting /system!
I feel like somehow my file system got corrupted, but unlike using Odin with the Vibrant I'm unsure how to fix this on the Vision. Anybody?
Click to expand...
Click to collapse
Try flashing a ROM that formats your partitions for you try ICS "Blackout" it makes it easier

hey ! i have the exact same problem! did u manage to fix ur phone ? how?
*fingers crossed*

I'm having the same problem. Whenever I try to reboot phone it goes to htc, reboots and goes to htc, then boots into recovery. Can't get past it.
I've tried connecting the phone via usb but it won't show up under adb devices.
I've wiped the phone and re-partitioned sd card.
Will be trying a different rom and seeing if that helps.
Any help other than that?
Edit: Flashed MIUI v4_2_8_10__VISION_CLEAN and phone booted fine. Must've been the TrickDroid rom I was trying to flash.

did any one tried this? any progress?

error in /sdcard/superwipeg2+ext4.zip (status 1)
For this error in ClockWork Recovery I did this:
CHANGE OPTION: "toggle script asserts" then the wipe script on my T-Mobile HTC Vision G2 acting correctly like it should and rebooted correctly instead of throwing the error above.
Hope this helps!

[Q] Desire Z (Tmobile G2) Help do I have eMMC problem noted in this forum, HELP!

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!