I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
moleary04 said:
I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
Click to expand...
Click to collapse
One of these may help you out:
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1547695
moleary04 said:
I have an Evo 3D on Sprint that I had downgraded to 1.4 s-off and I was running the AOKP milestone 5 rom with 4ext recovery. So yesterday I got a new 32 GB sd card to replace the 8GB one that came with the phone. I copied the data on the old SD card to my computer, powered off the phone and swapped sd cards, then booted back into android. I went to storage settings and erased the SD card, and I got a notification saying the SD card was blank or had an unrecognized file format. So I figured I would boot into recovery and see if there were any format options for the SD card to make sure it had the right file format. So I chose to reboot into recovery from the power menu, and instead of booting into recovery, the phone just turned off.
So now I can't turn the phone on and I've tried all the things I've already found here to get it back. I tried pulling the battery for a few minutes, tried doing the option to power on while holding down the camera button, and tried hooking it up to the computer only to be shown "qhsusb_dload" as the device, so I'm pretty sure it is bricked. I also don't think I can use the unbricking project since I think that is only for s-on devices.
Has anyone recovered from a brick like this? Do I have any options to resurrect my phone or is it completely dead? For repairs, I don't have insurance on my phone and I'm not going to take it into a Sprint store and lie about what happened. I'll own up to my mistake if I have to. Has anyone had a brick repaired by Sprint, and if so, how much did it cost? I figure my options are to have Sprint fix my phone, which might cost me a bit, or maybe now might be a good time for me to break my contract with Sprint and look at the unlocked Galaxy Nexus so I don't have to hack my phone to get the AOSP experience for ICS.
Thanks in advance for any helpful advice or suggestions, and hopefully I can get this thing figured out one way or another.
Click to expand...
Click to collapse
Or, you can try this one:
http://forum.xda-developers.com/showthread.php?t=1648703
freeza said:
One of these may help you out:
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1547695
Click to expand...
Click to collapse
Thanks for these links. I wasn't sure if the unbricking project would be helpful since it says it is only for devices that were bricked by turning s-on and I didn't even think about using Unknownforce's method. I'll give both a shot when I get home.
tgruendler said:
Or, you can try this one:
http://forum.xda-developers.com/showthread.php?t=1648703
Click to expand...
Click to collapse
I thought about posting this there, but I figured this was more of a broad subject and not really a specific question so I put it here instead. If it needs to be moved then that is fine with me.
I couldn't get either Unknownforce's or the unbricking tool to recognize my device. I guess this means my options for getting this thing going are severely limited. I'll be contacting Sprint tomorrow to see what they can do and I'll probably start exploring the option of selling this thing for as much as I can get to help pay to break my contract with Sprint.
Hey XDA,
After i updated my HTC Desire s's rom to BlindICE 7.0 from 6.0 (No factory reset) the phone kept coming up with the boot animation after i unlock my SD card. The boot animation would disappear though, but almost as if it had done a hot restart. I would then have to unlock the SD card again, and the same thing would happened. This happened a couple of times, and i disconnected it from my computer (I had the phone connected from earlier where i send the rom) and suddenly, the phone froze. Now i cant get in any contact with the phone. ADB earlier said the device was offline, but after i disconnected the phone from the PC, and connected it again, the device wont show up at all
So my question is, are there any way to restart the phone without pulling the battery? As i said earlier, ADB is not working. I could let all the power run out, but i would really love if there was a faster way, and not sure if it would be just as bad as if i pulled the battery.
I know i should post this in the Desire s's forums, but the Q&A section of the forum is not very active. If this is against any forum rules, you may delete this
EDIT: Fixed =)
So long story short I have this thunderbolt that is not working any longer. All of this happened over a year ago so I am vague on what I did to get the phone in its currently ruined state. It was rooted with the stock image and after trying to put a CM rom on it that didn't work I mistakenly booted into the phones recovery instead of clock work.
I now get a security warning and it is now s-on. If i do a recovery or factory reset it just boots back into the bootloader. Attached is an image of what is current on the screen when I power it on. I can't get ADB working on this pc but my spare rig has it working in OSX. ADB does not display the device. I have a way to get files onto the sd card but I am still kinda new to all of this stuff and just looking for some help. So where do I proceed from here?
I am going out of my mind.
So the phone just literally booted into my rooted rom. So now the question is, how do I get rid of the security warning and get s-off permanently?
At my end.
After a long day of trying to fix this thing and crawling all over the internet reading different posts I officially don't have a damn clue as to how to fix this. I am pretty sure the bootloader is corrupted and seeing as the phone is so old now it's really hard to find working links to downloads for this device.
Hello all,
I've searched the forums for quite awhile now and couldn't find anything to help solve my problem ,so I'm biting the bullet and creating a thread.
Earlier on this evening my phone randomly rebooted and I ended up stuck on the splash screen for 15+ minutes. I tried a battery pull but again got
stuck on the splash screen after turning the phone on. I'm able to get into Hboot and Fastboot but can't get into recovery , factory reset , clear storage , etc. Every time I try one of those options , the phone just freezes up. I'm not able to relock the bootloader and flash an RUU because I can't get into the phone to turn on my USB debugging , so my laptop won't even recognize my phone when it's plugged in. As of now , I'm at a bit of a standstill. I'm on Telus , S-ON, Rooted , running Speedrom 9. Any help would be greatly appreciated. Thank you for your time.
Gary
Hello,
First of all, I just created an account to get help with a phone I have. I cannot seem to fix it, I contacted HTC support and the only option left is to return it to them for a fee to fix.
Details:
SIM unlocked AT&T HTC one m9
Issue:
After trying to update to marshmallow using the ruu 3.38.502.12 which is for AT&T phones, my phone is now bricked. There was an issue in the middle of updating, so my phone tried to revert back to the old recovery. During this step my phone glitched out and rebooted itself, now its stuck in a boot loop with no indication of a recovery or any OS.
I tried to redo the ruu update and I get an error saying my battery level is less than the % required, yet my phone screen is showing 100% battery.
I also tried placing the .zip file on a SD card and using "download" boot method to flash the rom "I get error saying no OS present"
I also tried fastboot but my phone isn't picked up by fastboot and sticks at waiting for device.
Any method that requires me to turn on debugging mode is useless because I cannot access the OS to turn this on.
Anyone have any other suggestions then what I've tried? Or is the only thing I can do is send it back to HTC and hope they can reflash the phone?
Thanks to all for the help,