[G2 and Desire Z General] demkantor:
YES PLEASE POST QUESTIONS IN THIS THREAD RATHER THAN CREATING YOUR OWN "PLEASE HELP MY BRICK" THREAD

PLEASE READ AND RESEARCH FIRST AND THEN IF YOU MUST POST GIVE AS MUCH INFO AS POSSIBLE!​

Why am i making this thread? Aren't there already tons of them?

Exactly!

There are a couple a week and many times the old threads have already answered

all the questions needed to recover the brick, or explain why it cant be. So I'm here

to alleviate the clutter and hopefully help people more quickly.

Let's try to define a "brick"

People seem to say there is a "hard brick" and a "soft brick," to me that's just nonsense.

A brick is a brick. when you have no access to your recovery or your bootloader

then you have a brick. This is your phone wont turn on and it cant be recovered without j-tag equipment. (not for a novice)

Now you have no more than a brick on hand, or a pretty paperweight. What most

people have is a "soft brick" which really isn't a brick rather a phone that isn't

working as it should, but still a completely recoverable phone. A phone that doesn't

boot is just that, not a soft brick as it should be easy to fix and not to be used

as a paperweight. But i'll stop quibbling about the terms now as at least we

have an understanding.

A couple things first:

I implore you to read through a few threads on this as oh so many answers are there.

These are just a few from the last month or so!

HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE

As apparent as it may seem to those who frequent this forum, clutter only lessens

the experience here. Many never read the forum rules or listen to the mods. I'm

not trying to be a **** here, but we do need to at least attempt to keep the threads

clean. I understand that there is a lot to sift through but i can assure everyone

that questions will be answered faster and more clear to those who at least attempt

to do a little homework... rant over, let's fix those bricks!

So your phone wont boot...

you will need to know a few things about your phone as will the people helping you.

Let's make a list of needed information...

Different methods of rooting can give a different outcome. Importantly having true

radio s-off or not, and with some methods (visionary) that could cause a brick in itself.

If you cant remember how you rooted thats fine, information given here will help.

If you can, then chances are your phone can be fixed. If you don't know how to

get into these modes - simple way is to power on while holding volume down.

This is the bootloader (also known as Hboot or SPL - secondary program loader)

View attachment 1470618 Here is an example of the screen

The important information to take out of here is the engineering DZ Hboot, radio

secure flags removed (s-off) and the 26.13.04.19_M radio (commonly .19 radio)

You can see it is in fastboot mode (in red) and to scroll up and down through the

options you use the volume rocker, selecting an option with the power button.

if you choose bootloader the screen will look like this:

View attachment 1470630

Obviously some bootloaders will read different depending on radio, Hboot version,

including shipped verse engineering, s-on/off, etc. And I believe without an ENG

Hboot you don't get the system info option.

Please realize the more information the better, give everything but personal info,

really just the IMEI in the *SYSTEM INFO* option. (which really isn't all that personal) This leads to:

If you don't know, check!

This may be anything to i was updating angry birds to i tried turning it on and it

wouldn't. If your answer is i dropped it in the toilet and just plugged it into an outlet

to dry, i cant help you to much...

If you're not sure how to pull a logcat HEREare some quick pointers. You will need the Android

SDK, and ADB.exe download in platform tools. THIS GUIDE will help setting up

fastboot and ADB, both are very helpful and needed tools for Android users

Pulling a logcat

Once you have ADB up and running open a command prompt (Linux and OSX users

will have different steps) where ADB.exe is located on PC by holding shift and right-

clicking in the folder > choose open command here. In CMD type:

adb devices

if you see your serial number then proceed, if not we need to troubleshoot.

adb logcat > logcat.txt

this will create a text file in the directory CMD is in named logcat.txt, you can name

the .txt what you'd like by changing the logcat.txt to whatever, maybe output.txt

now to stop it just hit (Ctrl + c) the control key and c key at the same time. Now

upload it to XDA, or put in code wraps, or post the link to the pastebin.

This is written in code wraps and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]

***Please provide as much of this information as you can in your first post!***