[G2 and Desire Z General] demkantor:
What can i do to recover my phone already!

You are probably very frustrated right now, very understandable... please don't yell

at, or complain about, or blame your situation on those trying to help. No one is forcing

you to take the help given here and the last thing i want to hear is your complaints

about me/XDA/the world because your phone is toast and you need j-tag equipment.

Just wanted to get this out there, although its rare, don't blame others for your mistakes

or your misfortunes, thanks

Getting down to business...

Slowly lets work through the more obvious steps first, as simple as they seem to some,

it will fix most peoples problems. I will start by assuming you are rooted, those that

aren't i will add some more info....

What... well i said I'm starting slow. This is more for when a phone wont boot into

anything, no operating system, no recovery, no Hboot. If it does not, the first thing

to check is the battery. When you plug it in does the LED charge indicator come

on? Does the LED ever change to green? Have you tried different chargers? USBs?

Different batteries? It may be a hardware fault such as a bad USB port or charger.

I'm not going to spend more time on this case, but if you are finding yourself in this

situation, try a few things out first, if nothing works then feel free to post here and

I or some other helpful XDA member will attempt to troubleshoot more.

So your in a bootloop - rooted phones -

This is your phone gets past HTC/T-Mobile splash screen and gets stuck in the ROM's

boot animation. This tends to be most common issue for people new to android and

is very easily fixed. This may be caused by various things such as bad flash of the

ROM if its the first time booting into it. Maybe you adjusted DPI or overclocked too

much. Well, many possibilities, so first boot to recovery and wipe all (you will loose

personal info here) No matter the recovery you have (except stock) there are options

to wipe system, cache, dalvik, data. Do this, and while you are at it why not format

partitions, easy if in 4ext recovery. And for safe measure USE THIS SUPERWIPE

Or the AIO TOOL is proving to be great as well.

*If you would like you can always first try flashing the ROM or kernel first without

a wipe, or only wiping cache and dalvik, this may be a cure without loosing data*

After all this wiping and formatting we need to flash the ROM again. If you continually

have problems try a different ROM (something known stable) or a new download.

Every good ROM developer should have a MD5sum posted with their download. A

matching MD5sum will make sure what you flash will be what the developer uploaded

and didn't get corrupt when you downloaded it. GREAT MD5 TOOL FOR WINDOWS

And THIS ONE WILL ALSO CHECK SHA-1

If you are still getting a bootloop after all this then more info will be needed, post

here with your problem and all information you can give about your phone. Also if

you have ADB access then please post a logcat as well (pastebin or code wraps!)

This is written in code wraps, and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]
If you don't know how to post a logcat then you didn't read the first post!

If your not sure you are doing any of the above correctly feel free to ask for more

details otherwise see THIS GUIDE for a better understanding

Stuck in a bootloop - not rooted-

You will have far less opportunities to fix this with an non-rooted phone. The first

thing you may want to try is boot into safe mode (hold 's' button on keyboard while

powering on. If this works then you more than likely have a malicious app, try and

remove the most recently installed or most recently updated.

If this wont work then we'll need to boot into Hboot (volume down while powering

on) Then choose factory reset. You will loose all data (except whats on SD card,

or whats stored in the cloud) This will be like the day you first got your phone.

If that doesn't help the last thing you can try is to flash the latest RUU (ROM Utility

Update) from HTC.COM or other options HERE as well.

Not all phones are made equal...

If you have ADB access through recovery it may be helpful to know what eMMC

you have. There were two different chips made for the vision; SEM04G and M4G2DE,

the latter being a chip prone to failure by no fault of the user.

open a command prompt anywhere on computer and type

adb devices

if you see your serial # then you have access to ADB, if not more troubleshooting needed

now continue on

adb shell
dmesg | grep mmc0

if the output is something similar to this:

Then chances are your eMMC is fried, dead, and unrecoverable. :crying: sorry

To test which chip you have, again in CMD type

adb shell
cat /proc/kmsg | grep 'mmc0:0001'

you should see an output ending in something like

mmcblk0: mmc0:0001 SEM04G 2.17 GiB

or

mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Other methods

This may work better for those with a working phone wanting to check theirs:

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

-this can be done via ADB or terminal with a working phone without booting to recovery-

I am under the impression, but haven't yet confirmed that the M4G2E (bad) chip is

made by Samsung while the SEM04G (good) chip is made by Sandisk. No guarantee

but you may be able to check this via fastboot:

fastboot oem check_emmc_mid

this should display either Samsung or Sandisk - if anyone can confirm this i would

be very appreciative!

*pulling a logcat or checking what eMMC you have will not recover any part of

your phone, just give more info about your phone and potentially help with the

troubleshooting process

*lots more to come, hopefully today or tomorrow!