yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z General] Nipqer:
if you select recovery from hboot (or fastboot, can't remember which) and get into recovery, adb should work from there, but it wont work from hboot.

-Nipqer
[G2 and Desire Z General] jan_axhell:
When you say "Recovery" you mean the HBoot/Fastboot sub-menu called Recovery, don't you? Because I can't reach CWM Recovery at all.

BTW, I've done what you suggest, but ADB can't find any device (while Fastboot does). I have tried to install PDANet drivers, but no change, I am stuck in the HBoot/Fastboot menu. I have tried "fastboot flash recovery [with CWM path]", but it says it has no permission to write.

C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)...
OKAY [ 0.766s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.766s

VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot

Also tried RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe

but it waits for Bootloader, then says it can't connect to the phone, despite the fact that fastboot does connect.

EDIT: Since my father has the same exact model, but unrooted and untouched in any way, can it be of any use, like copying the bootloader or similar hacking?
[G2 and Desire Z General] arnoldl:
Same problem over here..

can't mount /cache/recovery/command

can't mount /cache/recovery/log

When i try to format from recovery i get a error formatting on cache , system and data

1) Do you have a G2 or a DZ?

DZ

2) Which ROM was last running on your device?

insertcoin 1.4

3) Do you have the ENG HBOOT installed?

no , don't think so.

4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?

No , everything from cwm

vision pvt ship s-off

hboot-0.85.005

microp-0425

radio-26.03.02.26_m

eMMC-boot

cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name

M4G2DE

mount /dev/block/mmcblk0p27 /cache

mount: mounting /dev/block/mmcblk0p27 on /cache failed: Invalid argument

cat /proc/kmsg | grep mmc0

<3>[ 7.504852] mmc0: No card detect facilities available

<6>[ 7.505462] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8

<6>[ 7.505615] mmc0: Platform slot type: MMC

<6>[ 7.505859] mmc0: 4 bit data mode disabled

<6>[ 7.505981] mmc0: 8 bit data mode enabled

<6>[ 7.506103] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz

<6>[ 7.506347] mmc0: Slot eject status = 0

<6>[ 7.506469] mmc0: Power save feature enable = 1

<6>[ 7.506713] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb8d000

<6>[ 7.506866] mmc0: DM cmd busaddr 0x0bb8d000, cmdptr busaddr 0x0bb8d300

<6>[ 7.662872] mmc0: new high speed MMC card at address 0001

<6>[ 7.664733] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

<3>[ 9.003112] mmc0: failed to get card ready

<6>[ 9.003234] mmc0: reinit card

<4>[ 9.003387] mmc0: Starting deferred resume

<6>[ 11.043243] mmc0: Deferred resume failed

<3>[ 12.796569] mmc0: DMA channel flushed (0x80000004)

<6>[ 12.796997] mmc0: Controller has been reset

<6>[ 12.797332] mmc0: Worked around bug 1535304

<3>[ 12.798706] mmc0: DMA channel flushed (0x80000004)

<6>[ 12.799133] mmc0: Controller has been reset

<6>[ 12.799346] mmc0: Worked around bug 1535304

<6>[ 12.806213] mmc0: reinit card

Hardware failure or can it be solved..

I know my way with adb, and develop in android apps...but not very good with linux..

So any help is welcome , i promise to keep around and report back :-)

Greetings , arnold
[G2 and Desire Z General] Nipqer:
Yeah it's a hardware issue. As far as I know, there's nothing you can do now except send it in to get replaced.

I know some people have tried everything, even talking to the radio directly but there's nothing that can be done. Yet.

-Nipqer
[G2 and Desire Z General] arnoldl:
hmm. to bad..

how can i revert to s-on and stock recovery , before returning it..

gfree -r part7backup....... gives an error and so does misc_version -s

thanks
[G2 and Desire Z General] guhl99:
Hi !

How do you think you can write configuration information to an emmc-chip that has an hardware issue to be not writable anymore ?

(Correct answer - not at all)

You can only send it in as it is (all people that I know who did it got the hardware replaced)

Have fun - Guhl
[G2 and Desire Z General] arnoldl:
Haha , u made my question sound very stuppid :-)

I was under the impression that some partitions didn't work at all...and not a general write failure..

Will send it in.

Thanks.
[G2 and Desire Z General] theSpam:
It is possible that this issue is affecting devices other than the DZ/G2:

Glacier - http://xdaforums.com/showthread.php?t=1081243

Thunderbolt - http://xdaforums.com/showthread.php?t=1098363
[G2 and Desire Z General] Lokospl:
Same issue here.. Bricked my phone.

Here's my story http://xdaforums.com/showthread.php?t=1111119

1) Do you have a G2 or a DZ?

DZ

2) Which ROM was last running on your device?

Insertcoin 1.4

3) Do you have the ENG HBOOT installed?

I don't know..

4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?

No, always from recovery
[G2 and Desire Z General] guhl99:
Hi !

Thanks for the detailed documentation of your problem.

As you probably already know, it is a hardware issue with your emmc-chip.

And unfortunately you can not write to the chip anymore (by no means).

So this also implies that you can not make it appear stock because you can not change any config information or rom.

Just return it as it is. Up to now everybody got his brick replaced on warranty.

Have - fun Guhl
[G2 and Desire Z General] Tendou:
No problem, I want to help myself and the community on fixing this problem, I tried to be as detailed as possible.

If there's any devs out there who wants me to work with them trying a fix, let me know, I'm on IRC as of now.
[G2 and Desire Z General] vascocn81pa:
Hi to all!

For two days I had the hard goal to update DZ.

I have had all the issues mentioned in this post.

I read all thread, and the other linked in first post, including a similar post from CM forum.

I solved the issue following this procedure.

--

1) Do you have a G2 or a DZ?

DZ

2) Which ROM was last running on your device?

Insert Coin 1.5

3) Do you have the ENG HBOOT installed?

Eng S-OFF 0.84.2000

4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?

First time i installed in root procedure, then i upgrade with rom manager.

--

1) First of all i've downloaded from cm7 wiki:

-enginering hboot "vision.hboot-0.84.2000"

-recovery "cwm 3024"

-radio "26.08.04.30"

2) then i dowloaded from xda this: AndroidFlasher1.8.0 so i reflashed all of three file mentioned : hboot, cwm, radio.

3) in fastboot mode i give cmd.exe fastboot erase boot.

4) i boot in bootloader mode and made a factory reset.

5) no more errors in cwm recovery, so i wipe all manually and not with zip files as full-wipe1.3 or similar.

6) install rom Virtuos 1.25 - install complete without errors ( before, i have ever error no.1 or error no.7 , and cwm cant erase boot, and cant mount cache, etc, i had all error before doing this procedure)

the result of this, is bootloop, i repeat point 5 (full wipe manual) and point 6 (install rom) for about three or four time, every time without error, with the result of bootloop, but at four trial IT WORKS PERFECTLY :D:D:D
[G2 and Desire Z General] nonione:
whatttt cant believe you made it! :) this is such great news for a lot of people!!! thanks a lot for sharing
[G2 and Desire Z General] vascocn81pa:
:D

Thanks, I hope this solution could work on other device. Maybe it could be only luck.

Anyway, this procedure born here. I made a mix of all my readings.

I think the problems are the errors returned by cwm, i tried to flash hboot, radio and cwm but the errors coming ever, so i read about android flasher, so i try, and it works better than adb and fastboot, anyway android flasher works with fastboot usb, so i dont know why it works when if i use cmd.exe it didnt work.

Than I have had problems of erasing boot through cwm, so i solved using fastboot. I have had problems formatting in recovery, solved using hboot factory reset... And so on. I only use other ways to do what i cant do right in cwm. Then i have had no errors in recovery, but bootloops, so i think if i have no error, there is no reason for not working. And I wiped and flashed again and again, then it works.. :D

Anyway i did what i wrote in this order, and finally work. I hope this can working fine for all of you.

I have DZ from Paris, FR, bought a months ago, i dont know about hardware if it is different model by model, f.e. i have not qwerty keybord but azerty keybord. :eek:
[G2 and Desire Z General] jan_axhell:
Congrats vascocn81pa!

Anyone else tried his method and succeeded? I've sent my DZ to assistance more than 3 weeks ago and they seem totally retard (gave them infos from this thread, which they ignored/did not understand -> multi-brand outsourced assistance, you know), so if it really works "as a standard procedure", I'll get it back and fix it on my own. It's off guarantee, so I will save a lot of money and time.
[G2 and Desire Z General] xsteven77x:
Just wanted to say I got a replacement yesterday that had froyo. It had that error as soon as I went into the stock recovery five min after turning the phone on. Was able to gfree it and everything else like normal, running CM now.
[G2 and Desire Z General] guhl99:
Hi!

Sorry to say this, but I don't believe that you had the same error. There are several other problems that show the same symptom that cwm can't mount or format cache (or other partitions). These can be cured by reflashing hboot (or the complete PC10IMG.zip) or also by manually repairing the partition table.

If you really have the problem that this thread is about then nothing can write to the emmc anymore and there is no way to flash anything.

You did not post the name of the emmc chip or if you had the emmc initialization errors in the kernel messages when booting into recovery (there is info about how to retrieve both in this thread).

So don't get me wrong but I think you are raising false hopes.

Have fun - Guhl
[G2 and Desire Z General] vascocn81pa:
I understand what you want to say me. Referring to thread title (.. recovery command) I had this error and many others, I retrieved many error in root procedure also with gfree and they refers to emmc. I had many emmc errors, but, as i said in my post, maybe i have had only luck. Anyway I cant flash original rom from bootloader. I cant flash anything, I dont know why I had solved this. I try and try and try again, and I reported what I have done.

I hope this can work for others, but, really I dont know if it is possible. I hope so :)

About what chip this DZ has, I can ask my friend to give me the phone again and then i will post them.
[G2 and Desire Z General] shuka325:
Another Recovery Error

Not sure if this is exactly on topic but wanted to post without making another thread. I have checked and do have the "good" chip so haven't been too worried. I had flashed several nightlies and was wanting a clean wipe so I wiped via fastboot.

Fastboot erase userdata

Fastboot erase cache

Then went into recovery and was greeted with this.

E:Cant mount /userdata/recovery/command

E:cant mount /userdata/recovery/ log

E:cant open /userdata/ recovery/log

E:cant mount /userdata/recovery/ last_log

E:cant open /userdata/recovery/ last_log

E:Cant mount /cache/recovery/command

E:cant mount /cache/recovery/ log

E:cant open /cache/ recovery/log

E:cant mount /cache/recovery/ last_log

E:cant open /cache/recovery/ last_log

Was of course very concerned after reading all the threads that have been written regarding this topic. Fortunately, i was able to flash SuperWipeG2 and i guess it repartitioned data and cache for me and was able to flash the ROM and been running for a while with no issues.

Guess, i just wanted to know if fastboot corrupted the files or if it is common to get that after a fastboot wipe? Thanks!!
[G2 and Desire Z General] oc3rulz:
I successfully fixed a friends phone with post #12!! I really appreciate all the hard work that people did finding this temp fix.

I got a call from a buddy that I rooted his myTouch 4G for, saying his phone was stuck on the HTC screen. So I went into recovery and got the dreaded:

E:cant mount /cache/recovery/ log

E:cant open /cache/ recovery/log

E:cant mount /cache/recovery/ last_log

E:cant open /cache/recovery/ last_log

so I found this and attempted the fix several times. I am so glad I had put the engineering bootloader on for him so I could update his CWM Recovery and run ADB through it.

I had to run it several times as it failed the first 5-6 times. I would run the command to make the new cache partition and then after it failed I would reboot into recovery anyhow, then it finally loaded with no errors. I then immediately flashed the newest CM nightly and GAPPS, then rebooted and to my amazement it worked.

I also checked and he had the bad eMMC, not the Sandisk version. Again really appreciate the hard work that everyone on this site puts in to help a fellow modder in need.

John
[G2 and Desire Z General] harshit_ps:
oc3rulz, let us know your emmc type
[G2 and Desire Z General] oc3rulz:
his was the M4G2DE eMMC, the bad one. On the myTouch 4G
[G2 and Desire Z General] Nipqer:
Maybe you got lucky and the emmc did not break, despite being the bad kind, just the partition tables being corrupted or something.

Cause if the emmc really broke, then there would be no way to fix it.

-Nipqer
[G2 and Desire Z General] oc3rulz:
Trust me, I got that "reint" deffered start message. It came up everytime. Then I rebooted that last time and it came back. Maybe his eMMC hadn't completely failed at that point, but I most certainly had that reint output
[G2 and Desire Z General] jjbat87:
hey did anybody here get a replacement for there bad eMMC G2 ?
[G2 and Desire Z General] arnoldl:
yes , my desire z got a replaced mainboard due to this same error.
[G2 and Desire Z General] Kevin001111:
My brother was running cm7 on his current G2 and decided to flash virtuous Unity, after installing the required Desire Z H-Boot my brother had some errors in the blank area of ROM manager. This happened immediately after rebooting into recovery after flashing the Desire Z H-Boot PC10IMG.zip from the virtuous site. the errors were something along the line of "E: can't open /recovery logs" and "E: can't open /last_recoverylogs" (don't have the errors in front of me and had to guess.) This problem I believe is purely faulty hardware. Luckily, my brothers phone still booted and is working fine. But, my first experience with this emmc problem was with my own phone, but mine just happen to become an insta-brick... I was pissed. But as long as I can't boot into it, neither can HTC, so I sent in my phone and got a replacement. and as soon as I got it I used adb and made sure I didn't have the serial number of the faulty chip. Hope this information helps!
[G2 and Desire Z General] jjbat87:
what do i tell to the tmobile representatives to get a replacement ? my phone is rooted and is bricked
[G2 and Desire Z General] xsteven77x:
I would just say u restarted your phone and it wouldn't boot. Now no matter what you do you can't get any sign of life from it and your totally clueless as to how it happened.
[G2 and Desire Z General] guhl99:
Hi !

This is unrelated. When you flash the Desire Z hboot to the G2 or the G2 hboot to the DZ this error has to happen.

The reason for that is that the Desire Z has a different partition layout than the G2 so after the reboot the cache partition is not where it used to be. So before you reformat it it can not be read.

So your brother is not lucky at all, it's just the normal expected behavior.

Have fun - Guhl
[G2 and Desire Z General] jan_axhell:
I have to confirm that vascocn81pa's method does not work with my DZ. AndroidFlasher simply refuses to flash anything, writing is always "denied". Being unable to pass that first step, I'm stuck at the HBOOT/FATSBOOT menu with no escape. :-/

C:\android-sdk-windows\platform-tools>@echo off
cd data\
taskkill /F /IM adb.exe
ESITO POSITIVO: Il processo "adb.exe" con il PID 1280 è stato terminato.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot.exe flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.172s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.172s
fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 3.000s]
finished. total time: 3.000s
fastboot.exe erase cache
< waiting for device >
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Del hboot.img
fastboot.exe flash recovery recovery.img
sending 'recovery' (4466 KB)...
OKAY [ 1.016s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.016s
fastboot.exe boot recovery.img
downloading 'boot.img'...
OKAY [ 0.750s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.750s
Del recovery.img
fastboot.exe flash radio radio.img
sending 'radio' (24832 KB)...
OKAY [ 4.094s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 4.094s
Del radio.img
fastboot.exe reboot
rebooting...
finished. total time: 3.000s
[G2 and Desire Z General] Fiber:
Same boat here..

I've already opened mine so no warranty for me anymore (stupid me)..

I didn't think this was a hardware problem.. I just used SuperWipe to clean my phone's memory and it stopped working after that, can't get it to flash radio/rom.. whatever..

It's strange that it would just fail with flashing a new rom.. Guess it was almost failing anyway..
[G2 and Desire Z General] GrandfatherJesus:
After reading this and many other threads extensively..I decided to send back the phone and get another on warranty. :(
[G2 and Desire Z General] therealdigitalchris:
For the record:

I have the same problem, G2, eMMC M4G2DE.

Probably going to call TMo and try to get a replacement.
[G2 and Desire Z General] Trialsin:
Just had this happen to me after flashing Virtuous Unity on my 3 month old Desire S.

Oh how I wish I'd just left it alone!
[G2 and Desire Z General] Nipqer:
Even if you left it alone it would've broken.

Flashing new roms does not trigger it, it just happens.

Mine broke while downloading Angry Birds.

-Nipqer
[G2 and Desire Z General] Trialsin:
Funny, I was downloading Angry Birds too! :confused:
[G2 and Desire Z General] jan_axhell:
I've got a new DZ. It is a 1.82.405.1 / 2.2.1

Now, what are the minimum actions I should do to determine what chip it has on board? Just rooting and checking from ADB?

Will the 1.72 rooting guide be ok for 1.82 too?

Can I still revert to unrooted if I don't do anything else than checking the chip?

In case it is an MT4GDE, I suppose rooting(*) it's not recommended and I'm forced to stay with stock rom to avoid warranty problems, right?

(*) leaving it rooted AND flashed with custom rom waiting for the brick

In case it is an SEM04G, will my previous nandroid backup (Virtuous) be ok on my new DZ after root?
[G2 and Desire Z General] Nipqer:
You only need temp-root to check the name of the chip I think. So just running psneuter and then the command they gave earlier in this thread to find the name should work.

If its the 'bad' chip it might break in the next hour, or it might never break. It's entirely random, and rooting does not affect it. There are cases of unrooted phones with this issue.

Most people have had no issues getting a warranty replacement with root/s-off.

As for the nandroid working on your phone, I'm not sure. Don't see why it wouldn't.

-Nipqer
[G2 and Desire Z General] jan_axhell:
Thanks Nipqer, I didn't think about the temp-root, I will study how to do that.

EDIT: well it seems temp-root is the first part of the perm-root procedure: but I must downgrade to 1.34 -> how can I revert back to 1.82? I read there is a more recent OTA around that prevents perm-root, how can I avoid to update to that when I am 1.34?

I know brick is unrelated to rooting, but I was afraid of being bricked while rooted and void warranty. Maybe some guy has been lucky getting a replacement with S-OFF, but that's not something that's sure to happen and I can't rely on luck. ;-)

About nandroid backup, I asked because if the chip is different there may be some stuff in the OS written differently, I don't know, some routine triggering a different set of instructions, things like that.
[G2 and Desire Z General] Trialsin:
These are some the results I get from my Desire S, not that I know what any of it means :(

~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
M4G2DE
~ # dir
dir
/sbin/sh: dir: not found
~ # mount /dev/block/mmcblk0
mount /dev/block/mmcblk0
mount: can't find /dev/block/mmcblk0 in /etc/fstab
~ # path
path
/sbin/sh: path: not found
~ # mount /dev/block/mmcblk0p27 /cache
mount /dev/block/mmcblk0p27 /cache
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Invalid argument
~ # fdisk -1 /dev/block/mmcblk0
fdisk -1 /dev/block/mmcblk0
unknown option -- 1BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi
-call binary.

Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK

Change partition table

Options:
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS

-S SECTORS

~ #
[G2 and Desire Z General] Nipqer:
If you just want to find out the name of the chip, you can just use psneuter to give you a basic temp-root. For a full root you have to downgrade to 1.34, but if you flash a custom rom you won't get OTA notifications.

If you want to get another stock rom, check out shipped-roms.com

-Nipqer
[G2 and Desire Z General] jan_axhell:
There was no need to temp-root, just launch a couple of commands from ADB with DZ in HTCsync mode:

C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
SH16VRT00681 device

C:\android-sdk-windows\platform-tools>adb shell
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
[B]M4G2DE[/B]

So it seems I am out of luck and got another BAD one. :-(
[G2 and Desire Z General] timhesselmans:
Problem not just for gfree users...

Just wanted to let you all know that this issue isn't just happening to people who rooted using gfree. I downgraded and rooted using this method: http://xdaforums.com/showthread.php?t=905261. I'm going to send it back to HTC and hope they will replace it... I just hope HTC NL is as nice as the places where they just repair it... I''m worried because in Holland, HTC doesn''t repair the phones themselves, but they let anther company do it for them... I sent my phone back to HTC about a month ago, because I made the biggest mistake I ever made; I pulled out the battery because my phone was crashing, but didn't realize it was charging... After that, my phone didn't do anything and my SD card was fried... But they fixed it, no questions asked so hoping they'll just fix it this time too...

1) Do you have a G2 or a DZ?

DZ

2) Which ROM was last running on your device?

Virutuous Unity 1.31

3) Do you have the ENG HBOOT installed?

No

4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?

Yeah I flashed Virutous Unity 1.31 and the patch for it to lower the CPU. My '' chip-fail'' happened when I tried to restore the data from my backup which I made because I had to reflash my ROM as it was freezing all the time.