Develop Bugs

[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.

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!

[Q] soft bricked or hardware fried?

hello dear all desire users, I've got this desire hd of my friend and it keeps boot looping, in the recovery i get
E:can't mount /cache/recover/command
E:can't mount /cache/recover/log
E:can't mount /cache/recover/last_log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/last_log
I have tried flashing RUU on fastboot but it didn't help and i have read a thread of other device about this internal card fried thingy then i have done my adb shell lookup and heres the output
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 6.260070] mmc0: No card detect facilities available
<6>[ 6.260803] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.260955] mmc0: Platform slot type: MMC
<6>[ 6.261199] mmc0: 4 bit data mode disabled
<6>[ 6.261352] mmc0: 8 bit data mode enabled
<6>[ 6.261474] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.261718] mmc0: Slot eject status = 0
<6>[ 6.261871] mmc0: Power save feature enable = 1
<6>[ 6.262115] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2aa2f000
<6>[ 6.262268] mmc0: DM cmd busaddr 0x2aa2f000, cmdptr busaddr 0x2aa2f300
<3>[ 6.384063] mmc0: unrecognised CSD structure version 0
<3>[ 6.384246] mmc0: error -22 whilst initialising MMC card
~ #
can someone verify this output and let me know if its dead or can be fixed? a helpful link will be a great help, thanks in advance and sorry for my bad English....

[Q] Desire Z stuck at HTC logo, also at factory reset

phone started rebooting then stuck.
Desire Z is stuck at HTC logo when power on
stuck at factory reset from hboot
stuck at wipe data/factory reset from cwm
error when opening cwm cant open /cache/recovery/log
error when install zip from sdcard
stuck at wipe data command from adb
stuck at fastbooting cwm.img
HBOOT menu
***UNLOCKED***
VISION PVT SHIP S-OFF
HBOOT-0.85.0015
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
Dec 20 2011, 16:21:13
Recovery: clockworkMod Recovery v5.8.1.0
ran this command and getting the results cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
so emmc chip is ok
any more ideas, or am i missing something??
Regards

zabroadcast said:
phone started rebooting then stuck.
Desire Z is stuck at HTC logo when power on
stuck at factory reset from hboot
stuck at wipe data/factory reset from cwm
error when opening cwm cant open /cache/recovery/log
error when install zip from sdcard
stuck at wipe data command from adb
stuck at fastbooting cwm.img
HBOOT menu
***UNLOCKED***
VISION PVT SHIP S-OFF
HBOOT-0.85.0015
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
Dec 20 2011, 16:21:13
Recovery: clockworkMod Recovery v5.8.1.0
ran this command and getting the results cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
so emmc chip is ok
any more ideas, or am i missing something??
Regards
Click to expand...
Click to collapse
no one's having any idea???

When this situation happens either you have some corrupt partitions or your emmc is fried, if its just a corrupt partition you can try an reformat to fix, nothing can be done if the chip is bad
You'll find more info in the second post here
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
When this situation happens either you have some corrupt partitions or your emmc is fried, if its just a corrupt partition you can try an reformat to fix, nothing can be done if the chip is bad
You'll find more info in the second post here
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for replying
tried fastboot erase system -w but permission error
tried ALL IN ONE Wipe Tool , its formatting from format but nullifying tool is not working,
Supe Handy SuperWipe Tool installs but nothing happens after that.
Is there a way to know that emmc is fried or not?

Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
great, i will look into PC10IMG.zip
what i did for now is according to
http://forum.xda-developers.com/showthread.php?t=1572924
under
Testing for a fried ROM:
i ran
Code:
adb shell
dmesg | grep mmc0
and i am getting
~ # dmesg | grep mmc0
<3>[ 4.305236] mmc0: No card detect facilities available
<6>[ 4.305847] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.305999] mmc0: Platform slot type: MMC
<6>[ 4.306121] mmc0: 4 bit data mode disabled
<6>[ 4.306365] mmc0: 8 bit data mode enabled
<6>[ 4.306518] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.306762] mmc0: Slot eject status = 0
<6>[ 4.306915] mmc0: Power save feature enable = 1
<6>[ 4.307037] mmc0: DM non-cached buffer at ff817000, dma_addr 0x2ae32000
<6>[ 4.307281] mmc0: DM cmd busaddr 0x2ae32000, cmdptr busaddr 0x2ae32300
<6>[ 4.463348] mmc0: new high speed MMC card at address 0001
<6>[ 4.464660] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 5.832824] mmc0: Failed to get card ready i = 122095
<6>[ 5.833068] mmc0: reinit card
<4>[ 5.833190] mmc0: Starting deferred resume
<6>[ 7.873016] mmc0: Deferred resume failed
<3>[ 8.078094] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.079254] mmc0: Controller has been reset
<6>[ 8.080017] mmc0: Worked around bug 1535304
<3>[ 8.082550] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.083679] mmc0: Controller has been reset
<6>[ 8.084442] mmc0: Worked around bug 1535304
<6>[ 8.093109] mmc0: reinit card
<4>[ 8.093475] mmc0: Starting deferred resume
<6>[ 10.132995] mmc0: Deferred resume failed
<3>[ 10.245178] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.245971] mmc0: Controller has been reset
<6>[ 10.246520] mmc0: Worked around bug 1535304
<3>[ 10.248535] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.249359] mmc0: Controller has been reset
<6>[ 10.249664] mmc0: Worked around bug 1535304
<6>[ 10.257629] mmc0: reinit card
<4>[ 10.257873] mmc0: Starting deferred resume
<6>[ 12.292999] mmc0: Deferred resume failed
<3>[ 12.526947] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.527374] mmc0: Controller has been reset
<6>[ 12.527587] mmc0: Worked around bug 1535304
<3>[ 12.529083] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.529510] mmc0: Controller has been reset
<6>[ 12.529815] mmc0: Worked around bug 1535304
<6>[ 12.537475] mmc0: reinit card
<4>[ 12.537719] mmc0: Starting deferred resume
<6>[ 14.572998] mmc0: Deferred resume failed
Click to expand...
Click to collapse
so mmc is not fried...... i will check this samsung one and let you know.
Regards

demkantor said:
Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got an android running up form [GUIDE] Booting an Android System when only Recovery is at your disposal but this is not the solution, so can i do anything while i am at it. If emmc is not fried then why cant i reformat it and skip the bad partation.

STATUS
the PC10IMG.zip was stuck at updating.....
downloading another rom from sd
[GUIDE][KANG] Android Boot-From-SD w/ GAPPs and Play Store
Click to expand...
Click to collapse
but the download link was broken, found another link from google at
HTML:
http://inclu.net:82/HTC/DesireZ/
wifi does not work when boot form recovery, but amazingly
HTML:
[CODE]fastboot boot boot.img[/CODE]
is working and wifi was working....
but other commands are not working ......

you are limited to the fastboot commands available being you have a shipped bootloader,
you can try to get into an adb shell and run
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
to see if this will reformat for you
also
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
will tell you what chip you have, SEM04G being the 'bad' one

Results of the commands are pasted
mke2fs /dev/block/mmcblk0p25
Click to expand...
Click to collapse
Code:
~# mke2fs /dev/block/mmcblk0p25
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
35760 inodes, 142847 blocks
7142 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=146800640
5 block groups
32768 blocks per group, 32768 fragments per group
7152 inodes per group
Superblock backups stored on blocks:
32768, 98304
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs /dev/block/mmcblk0p26
Click to expand...
Click to collapse
Code:
~ # mke2fs /dev/block/mmcblk0p26
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
75200 inodes, 300799 blocks
15039 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=310378496
10 block groups
32768 blocks per group, 32768 fragments per group
7520 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs /dev/block/mmcblk0p27
Click to expand...
Click to collapse
Code:
~ # mke2fs /dev/block/mmcblk0p27
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p27 is apparently in use by the system; will not make a filesystem here!
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Click to expand...
Click to collapse
Code:
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
M4G2DE