[HTC EVO 3D] snake3276120:
Latest update:

I went to Rogers, and the girl suspect that my phone is broken due to physical damage because there are some scratch on my phone. She send the phone back to HTC for diagnosing. It will take 10 - 15 business days. I'm wondering if HTC will find out that I have su and superuser inside T.T

----------------------------------------------------------------------------------------------------------------------------

I bricked my phone. I'll tell you guys what I've done.

When I get my new Evo 3d GSM, the revolutionary for GSM was not released yet.

I used the one for CDMA (HBoot 1.40) to turn my phone to s-off, and yea, it worked. You guys must be blaming me, saying why did you do so? Because at the time when I was rooting my phone, revolutionary did not support GSM yet.

I flashed the recovery at bootloader using fastboot ******* .....

I flashed a root (su/superuser) to my phone. I used the su in this thread

http://xdaforums.com/showthread.php?t=1218969

Yea, that means I have the correct HTC driver and android SDK.

and yea, it's rooted. Everything was totally fine until today...

I saw there's a thread about rooting GSM using new revolutionary which supports GSM.

The thread is http://xdaforums.com/showthread.php?t=1247392

I thought maybe I should turn s-on, and use the revolutionary for GSM (HBoot 1.49.0007) to make it s-off "properly".

I followed most of the the steps on that thread.

Step 1. Download applicable rom from this thread: http://xdaforums.com/show....php?t=1208485

Step 2. Flash rom from attached thread.

I skipped the first and 2nd step, cuz I did not flash my rom to a customer one. I just uninstalled some rogers apps and htc logger. I don't skipping these 2 steps caused the problem at the beginning. But now I think it may caused the problem, because my phone is still in root state!

Step 3. Download and extract android SDK (Already have it)

Step 4. Connect phone in USB debug mode

Step 5. Open an elevated command prompt and cd to the extracted tools folder (Powershell ftw!)

Step 6. type "adb reboot bootloader"

Step 7. type "fastboot oem writesecureflag 3"

Step 8. type "fastboot reboot-bootloader"

Thats it! Bricked!

What's the situation:

I cannot turn it on by any means...The red LED is not on even when I connect it to a charger or my PC.

What I've tried:

---Remove the battery, wait for 10 mins, put the battery back and try to power on,doesn't work.

---Connect to PC, adb and fastboot can't find the device

---Device manager complains "QHSUSB_DLOAD" is not working properly(with a exclamatory mark on the icon). I tried to search this issue, but it seems that none of the similar problems (Device manager complains "QHSUSB_DLOAD") are solved. I also tried to install some driver to let my PC recognize the device (which makes QHSUSB_DLOAD's icon without the exclamatory mark), but adb and fastboot still can't recognize the device.

Please help! Thanks a lot in advance!

Also there is one more question, Rogers gave me a one year's warranty, I bought this phone Aug 2011. My phone is still in warrant, but do they replace my phone due to this kind of problem? I don't know if they can boot up my phone, they'll see s-on or s-off.

Sorry about my broken English, I'm not an arts student :P