HOW TO: Recover a Diamond that won't get past the boot screen! (Instructions)

[Glossman]

Originally Posted by indagroove

Huh? It's usually a rom issue, and occasionally a flashing issue. Some bad or conflicting oems sometimes cause this issue. I have had this problem with a Tobey kitchen, and deslected an oem and all was good.

That makes perfect sense, but what would make it intermittent?

[Zeddicus]

When it happened to me, it seemed that it only went haywire after syncing with my computer.....Just some FYI

[THUNDER02]

was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.

[JAChavez99]

Originally Posted by Glossman

Thank you. And sorry if I reacted a bit strongly, but I've been putting a lot of time into this lately, and I take it personally when my ROM causes a headache for someone. I get a little touchy when I *perceive* that someone is rubbing it in.

I just want to help the user recover as soon as possible, you know?

So, no hard feelings, okay?

On to business! The kitchen I used for the build did incorporate G'reloc, and it ran when I built my Production ROMs. What I'm wondering is how this manifests itself after multiple reflashes, but not after 1 or 2. Almost everyone (including myself) who has experienced this issue has never seen it after a single reflash from the same ROM type. This makes it really hard to troubleshoot.

Opinions?

Thanks again for your help Glossman, you sure did help me have a quick recovery!

I experienced exactly what you said, intermittent issue, even on the same ROM. After I fixed today's problem, I flashed back to your ROM and have had no worries. The first time this happened to me was on Calcu's ROM, so I can't say it wouldn't have happened had I flashed it again, but it seems highly unlikely.

[indagroove]

If you guys are having that much trouble, I suspect your issue is one of the following:

1. A problem with your phone hardware
2. A problem with the rom
3. A problem with the computer hardware you use to flash with

I've flashed my Diamond about 50 times in the last month, and the only time I couldn't boot was when I did the bonehead maneuver of forgetting an oemdriver folder.

[BlackOceaN]

THIS POST WORRY ME BUT I CHOP AND CUT ROM LIKE BUTTER .

So i am able to set up very quickly..

Originally Posted by indagroove

If you guys are having that much trouble, I suspect your issue is one of the following:

1. A problem with your phone hardware
2. A problem with the rom
3. A problem with the computer hardware you use to flash with

I've flashed my Diamond about 50 times in the last month, and the only time I couldn't boot was when I did the bonehead maneuver of forgetting an oemdriver folder.

[momo123]

i need help asap

i have my htc diamond and unlocked it

then tried installing w mobile 6.5 with manilla but then it
ruined my phone

its always stuck on the diamond screen then restarts

i tried the methods for reflashinf roms such as shine on 2.4 and others but no success

a rom that might save my ass is juicy or mighty rom, but cant find anywhere on the web

any help and instructions is greatly appreciated since this is only 2 days old.

[tobeychris]

You're welcome

[tobeychris]

Use mtty task 32, task 36 to find out

[justinchow19]

so kind of u,thank u very much!