[HTC EVO 3D] hedgehog45ve:
Hi everyone.

Thanks to all of you who help us non-devs upgrade our phones to be so much better than they would be with just stock software and OS. I'm hoping that someone knows how to fix my phone. I have done a lot of reading, and don't intend to be like the bear in that neat animation, "Trying to give a, Phone Idiot, Support," about the noob who fried his phone and doesn't know what kind of phone he has, or what ROM he flashed.

I read several helpful posts, but am still not sure that I have the tools I need to fix this thing. The best lead so far looks to be deBricker's guide to un-brick a Galaxy S3. After some delayed sleep, I might be sane enough (back to about halfway again) to find the right files for my Evo 3d, and will give that approach a try. But I figured I'd post this in case someone out there sees from the data provided, that doing something similar to what deBricker's guide details for a Galaxy, will make things even worse for me. I would appreciate a lead on where to get the right files for my Evo 3d. I'm at least clued in enough to not try the files for the S3 in my Evo 3d. Oh, and I regularly do Nandroid backups. :)

I have a hard bricked HTC Evo 3d. It's likely my fault for installing something incorrectly, or something that isn't supposed to go on my phone, or for missing something that I should have done prior to installing. Other ROMs I've tried have worked well.

I installed MNRGS2JB108.zip, aka MidnightRomGS2JB, by xthedakmanx. It looked like it was a neat ROM worth trying. But, it was a bad decision, in my case! No blame to anyone (other than me), though. Responsibility is mine, but I sure would love to have someone be hero of the day and tell me how to fix it!

I ended up with NO MEANS OF LOADING OR FLASHING ANYTHING by a battery pull and volume down + power on. Plus, the phone won't even try to power up. In a darkened room, I can sometimes get, with a fully-charged battery, a super-dim, barely-detectable, red power light to light up.

Early on, I saw the not-uncommon QHSUSB_DLOAD on my Win7 laptop when I connected my phone via USB. After some frantic searching around, I got drivers to allow my laptop to now show it on the device manager under ports as "Qualcomm HS-USB QDLoader9000" on COM4. But that hardly lets me just open up a file explorer and fix things. :(

When I open a cmd box and try to use fastboot commands to flash and such, my laptop does see my phone, briefly (maybe 8 seconds or so, as others have mentioned in other threads), and while I have been able to successfully use some of the commands. Here's what I was able to do, and the information I was able to pull from my phone, in case it helps you guys to figure out what's wrong, and better still, how I can fix it. I think it might be better to give lots of info rather than leaving people playing 20 questions to understand my particular predicament. But, if the following copy-paste is superfluous and of little value after all, sorry about that.

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readcid

< waiting for device >

...

(bootloader) cid: 11111111

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkSbl1

(bootloader) sbl1 signature checking...

(bootloader) TZ_HTC_SVC_VERIFY_BOOTLOADER ret = 0

(bootloader) sbl1 verified successfully

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkHWSecurity

...

(bootloader) HW Security has been enabled !

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem keytest

...

(bootloader) start keypad testing ...

FAILED (status read failed (Too many links))

finished. total time: 8.402s

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap

...

(bootloader) Total free heap size: 536784792 Bytes (0x1FFEAF98)

(bootloader) Max. free heap segment size: 536760320 Bytes (0x1FFE5000)

(bootloader) Max. free NPC heap segment size: 536760320 Bytes (0x1FFE5000

(bootloader) )

OKAY [ 0.019s]

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap_test

...

(bootloader) ======heap_test (Ver: 1.0)======

(bootloader) heap_test <test_mode> <cyles> <break> <cache/non-cache> <ob

(bootloader) verse/reverse> <seed/pattern>

(bootloader) <test_mode> (0): Mix pattern mode -> heap_test 0 <cy

(bootloader) les> <break>

(bootloader) <test_mode> (1): Fix pattern mode -> heap_test 1 <cy

(bootloader) les> <break>

(bootloader) <test_mode> (2): Random pattern mode -> heap_test 2 <cy

(bootloader) les> <break>

(bootloader) <test_mode> (3): Assign seed mode -> heap_test 3 <cyles

(bootloader) > <break> <cache/non-cache> <obverse/reverse> <seed>

(bootloader) <test_mode> (4): Assign fix pattern mode -> heap_test 4 <cy

(bootloader) les> <break> <cache/non-cache> <obverse/reverse> <pattern>

(bootloader) <cyles> The number of testing cycle

(bootloader) <break> Command break off when RAM issue occurs 0:Not break

(bootloader) off 1:Break off when RAM issue occurs

(bootloader) <cache/non-cache> use cache or non-cache memory space 0:cac

(bootloader) he 1:non-cache

(bootloader) <obverse/reverse> assign the direction of scanning 0:obvers

(bootloader) e 1:reverse

(bootloader) <seed/pattern> seed to create random pattern for each byte

(bootloader) / pattern for every byte

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem enableqxdm 0

...

(bootloader) Start Verify: -1

(bootloader) Start Verify: -1

(bootloader) erase sector 130560 ~ 131071 (512)

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem gencheckpt

...

(bootloader) Start Verify: -1

(bootloader) Start Verify: -1

(bootloader) erase sector 130560 ~ 131071 (512)

(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!

(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990

(bootloader) TAG:Ramdisk OK

FAILED (status read failed (Too many links))

finished. total time: 8.495s

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem boot

...

(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!

(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990

(bootloader) TAG:Ramdisk OK

FAILED (status read failed (Too many links))

finished. total time: 8.580s

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readimei

...

(bootloader) imei: [my imei number was here]

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readsecureflag

...

(bootloader) secure_flag: -1

So at least the thing is showing something still inside my phone, and that it can be read. The trouble is, that I'm not able to get it to receive any changes:

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot flash recovery recovery-clockwo

rk-touch-5.8.0.1-shooter.img

< waiting for device >

sending 'recovery' (4128 KB)...

OKAY [ 0.566s]

writing 'recovery'...

FAILED (remote: not allowed)

finished. total time: 0.567s

C:\Users\Hedgehog\Desktop\RootEvo4GNew2>

That part about "FAILED (remote: not allowed)," is a little saddening, to say the least. :( And, I've been struggling and worrying about this, a lot longer than 0.567 second! If not for that "not allowed" error, things might be OK. So, is the deBricker's guide the approach to try next?

FWIW, I do have a broken but not bricked, Evo 3d (bad touch screen but probably good data files) that might help supply data files. Yeah, I ought to try pulling stuff off of it and beat the odds and fix it on my own, but I've been reading and tinkering for a couple of days already, and someone else might know just what to do, hence I am humbly asking for some pointers.

Again, sorry for the size of this post, and thanks for any help!