Root Help! S-OFF gone terribly wrong?

[joshua8790]

Well... I tried S-OFFing my EVO V. Same tools I used before. Now this time......


It won't turn on. It is accepted as a USB device, but juopunutbear wants me to install drivers for it and then connect it. I tried removing the battery and reconnecting it, powering it on, and still no luck. Is there anything I can do before I have to assume it's dead and revive one of my old VM phones?

Please help.

Edit: after leaving the EVO plugged in, it keeps disconnecting and connecting itself. Still no luck of revival. Anyone know of this happening?

 

[Prinny]

Do you see the logo for the program when your phone boots?

 

[fogle7]

Pull out the battery try to boot into fastboot, then type in "ControlBear -f" in cmd

 

[joshua8790]

Thanks for the suggestions... Well

I can't get it into fastboot. Controlbear says that I need to reconnect the device or install drivers.

Welp. I tried the unbricking project too from xda. That can't even detect the phone.

Note to self: Do not try S-OFFing when it's late, or you're gonna have a bad time.

 

[OverByter]

Have you been to the unlimited io channel on irc?

 

[joshua8790]

I did. We determined it's bricked. I've done the process 2 times (different phones), and guess 3rd times a charm.

We also tried the unbricking solution too. That didn't work either. It wouldn't even recognize the device and when I was on Windows, it just kept playing the eject/insert sound when I had it plugged in.

Late Night S-OFFs
Don't try this at home

So yeah, watch out guys, there actually is the possibility of bricking your phone to an irreversible state.