Database Info

[Q] Another bricked Desire S

I've searched the forums but i wasn't able to find a solution to my problem.. so i'm forced to start another thread for another bricked DS..
So.. i was installing a customROM today(Virtuous 2.37) in recovery mode.. everything seemed initialy ok but the phone freezeed in a bootloop.. i was stupid and i've removed the battery.. and since then my phone is dead..
If i press the power buton it vibrates 7times.. and the screen remains black..
If i pull out the battery and press again the power button, same thing..
If i connect the phone to usb nothing happens, no led is turning any color
ADB doesn't work, it says: "device not found"
Fastboot doesn't work, it says: "waiting for device"
Power + vol up/down doesn't do anything..
So.. please help.. is it dead for good?

I'm sry to say that, but it looks like yours is one of a few devices where the emmc chip is really fried.
But otherwise cause of this your lucky and could give it back for warranty and get a new or repaired one

Won't they observe that the device is S-Offed?

nothing_ro said:
Won't they observe that the device is S-Offed?
Click to expand...
Click to collapse
How they should if there's no access^^
But some others with your problem told that they got warranty cause it's a true hardware failure and has nothing to do with the software.
And amidabuddha told that common sense is replace not repair (what could mean that the whole device will be replaced or the emmc chip in your device).
So i think there should be no real problems

@poster
jst send it back to htc and request for a replacement
am sure they will do that cos we hv seen some guys dat it happened to n it was replaced
good luck n becareful next time
cheers

lynxnoon said:
@poster
jst send it back to htc and request for a replacement
am sure they will do that cos we hv seen some guys dat it happened to n it was replaced
good luck n becareful next time
cheers
Click to expand...
Click to collapse
Best of luck.
Hope they dont notice the s-off and you get a replacement...

I had same problem and sent for replacement.they told me that they are going to change the motherboard,but they don't have stocks for it and I need to wait for quite some time,,,

Do tell us if you get it replaced by the hTC....

I fried my eMMC chip by pulling my battery while getting impatient while installing a ROM. And HTC repaired my device under warranty and never questioned or mentioned anything about the device been s-off.
Sent from my HTC Desire S using XDA App

First, thank you for the feedback/advices.
Second, i just got my phone back from the service, they have replaced the pcb(or at least that's what they told me).

need help with bricked phone

I just wanted to use revolutionary to root my phone, but nothing happened. After that the phone just rebooted and then turned off. Now I can't turn it on and it even doesn't charge!
help please

Your phone is not brick, can you still boot into HBOOT? Volume down key and press hold power button.
Sent from my HTC Sensation 4G using XDA Premium App

no, it seems completely dead. Even when I connect it to the charger the charging light doesn't turn on!

did you have cwm installed on your phone already and if so what version

remove battery.. then try powering the phone.. if nothing happens.. follow this thread...
http://forum.xda-developers.com/showthread.php?t=1198585
and if still nothing happens..then I would say that it's bricked...

william1985 said:
did you have cwm installed on your phone already and if so what version
Click to expand...
Click to collapse
I don't have CWM, because the problem happened when I tried to root it!

Quakeworld said:
remove battery.. then try powering the phone.. if nothing happens.. follow this thread...
http://forum.xda-developers.com/showthread.php?t=1198585
and if still nothing happens..then I would say that it's bricked...
Click to expand...
Click to collapse
I tried another battery but it didn't work

at least someone tell me if I can return it or report it as lost phone? I am on tmobile

"make sure" there is no way to boot on then just bring back to T-mobile to get a new one; Just say "I got no cure" "whatever they asked.

kai2314 said:
"make sure" there is no way to boot on then just bring back to T-mobile to get a new one; Just say "I got no cure" "whatever they asked.
Click to expand...
Click to collapse
it wont boot, is there anyway they can read any logs or something from the phone memory to see what happened?

mzangui said:
it wont boot, is there anyway they can read any logs or something from the phone memory to see what happened?
Click to expand...
Click to collapse
Same happened to me (exactly) and after being advised by network provider rang HTC repairs, phone picked up next day, returned to me repaired 6 days later, no charge, hassle at all!

My Sensation is dead, bricked, won't charge or turn on

I tried flashing my unlocked Orange Sensation and now it does not show any sign of life: I can't turn it on, no light from the LED indicator when charging it.
I removed the battery several time and put it back then tried power it on without any luck, here what I did before:
I followed this tutorial and S-OFF,installed ClockworkMod Recovery, and rooted it all successfully.
After that I tried flashing if using Sensation_3.32.401.5_deodexed from this thread, but the phone kept restarting showing HTC logo screen.
Then I read that I need to super-cid my phone since it was from Orange. I did that using Auto Super-Cid Script By Pavelol v3, again the phone kept restarting showing HTC logo screen.
Finally, I successfully installed Firmware from 3.32.401.x & 3.32.401.10x RUU in this thread, then reboot, BAM phone is dead!
I don't know what I did wrong, but it should not kill my phone!
I looked at previous threads but there is no clear cause or solution.
Help me pleeeeez

SilverDove said:
I tried flashing my unlocked Orange Sensation and now it does not show any sign of life: I can't turn it on, no light from the LED indicator when charging it.
I removed the battery several time and put it back then tried power it on without any luck, here what I did before:
I followed this tutorial and S-OFF,installed ClockworkMod Recovery, and rooted it all successfully.
After that I tried flashing if using Sensation_3.32.401.5_deodexed from this thread, but the phone kept restarting showing HTC logo screen.
Then I read that I need to super-cid my phone since it was from Orange. I did that using Auto Super-Cid Script By Pavelol v3, again the phone kept restarting showing HTC logo screen.
Finally, I successfully installed Firmware from 3.32.401.x & 3.32.401.10x RUU in this thread, then reboot, BAM phone is dead!
I don't know what I did wrong, but it should not kill my phone!
I looked at previous threads but there is no clear cause or solution.
Help me pleeeeez
Click to expand...
Click to collapse
Well, you certainly bricked your phone by installing the ROM before upgrading the firmware or superCID your phone..
First of all, there's no need to superCID just because you are on Orange, you could have downloaded the suitable firmware from mike's thread. Then again you should have done it before trying to install the ROM. That's what you probably have done wrong.
Now as per the solution, refer to the following threads..I guess they will help you
http://forum.xda-developers.com/showthread.php?t=1600324&highlight=bricked+sensation
http://forum.xda-developers.com/showthread.php?t=1542555

I would try that if the phone would power on
My problem now is that the phone can't be turned on. I press the power button nothing happens, I connect it to the charger but charging LED not lighting.
I connect it to my PC but it can not detect the phone at all because it is not turned on.

SilverDove said:
My problem now is that the phone can't be turned on. I press the power button nothing happens, I connect it to the charger but charging LED not lighting.
I connect it to my PC but it can not detect the phone at all because it is not turned on.
Click to expand...
Click to collapse
Can you load recovery or bootloader by pressing power and volume button?
Sent from my HTC Sensation using xda premium

No
I can't since it can't turn on!

SilverDove said:
I can't since it can't turn on!
Click to expand...
Click to collapse
You don't need to be able to fully turn your phone on in order to access the recovery and bootloader. Charge the phone for a while, even if no LED is showing. Reflash the 3.32 firmware if you can access the bootloader. Flash VI through recovery. Observe.
Sent from my HTC Sensation Z710e using Tapatalk 2

I charged the phone with no LED indicating its being charged, pressed the power button and nothing happened. The phone can't be powered at all.

I think you need to take it to repair shop, to un-break it they need to replace a part on your htc using JTAG.
This will cost you alot of money.

SilverDove said:
I charged the phone with no LED indicating its being charged, pressed the power button and nothing happened. The phone can't be powered at all.
Click to expand...
Click to collapse
Remove battery, replace battery, hold volume - and press power, this is how you enter bootloader. Does this work?
Sent from my HTC Sensation 4G with Beats Audio using xda premium

Already did that
I've already removed the battery and replaced it many times without any luck.

Try to take to a local HTC repair center. If You have any kind of proof of purchase, they have to repair it under warranty according to the IMEI no.
I succesfully got my phone back in this way. Just don't tell them what You did, only that it won't turn on.
Good luck!

I will take it to HTC repair center, unfortunately I lost its papers so I'll have to pay for the repair

I had the same problem...phone won't turn on and unresponsive. Not sure if it's ROM related....it happened after I installed the new revolution ROM...but everything seem to go fine and was able to boot to the new ROM...then when using for call it had a long beep tone and just turned off and never turned on again.
So I am waiting for repair from HTC as well...hopefully they will replace it as well. Do you think yours is a hardware problem? I am glad they replaced yours even it was rooted.. I am hoping they can't turn on and had no choice and way to know it was roooted!

newr said:
I had the same problem...phone won't turn on and unresponsive. Not sure if it's ROM related....it happened after I installed the new revolution ROM...but everything seem to go fine and was able to boot to the new ROM...then when using for call it had a long beep tone and just turned off and never turned on again.
So I am waiting for repair from HTC as well...hopefully they will replace it as well. Do you think yours is a hardware problem? I am glad they replaced yours even it was rooted.. I am hoping they can't turn on and had no choice and way to know it was roooted!
Click to expand...
Click to collapse
Indeed! Same hapened to me. It was mainboard failure. They couldn't turn it on.
Bad side it has latest stock rom with HBOOT 1.27.0000, and still no way to unlock bootloader, rooting and S-OFF.

HTC repair center says that the motherboard need to be changed and it will cost me about 235$! I found out while searching that many experience this problem.
I tried to find a replacement but almost all my search result is about the upper PCB with motherboard flex cable which is leftover of people buying motherboards.
HTC has problems with motherboards with several models also.
I hate HTC, I will not buy any HTC again.

try contact your dealer, and ask if he can find the tickets?

Hey man, try jumpstarting your phone by taking out the battery and plugging it in the wall, try turning it on while it is directly connected?

This is a know issue. You have hard bricked your device. I did it too. If you have warranty, there is no way HTC can detect a modified device and they will replace the motherboard for you like they did for me, free of charge. If you don't have warranty thankfully there is now a relatively simple way to fix this:
Just follow this guide:
http://forum.xda-developers.com/showthread.php?t=1522351

Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
My case is that I've installed a ROM before updating the firmware, anyway I have tried it and it won't work with me.

Anybody can explain this to me?
I don't know how flashing a ROM before upgrading the firmware can damage my motherboard ! Anybody can explain this to me?
I did many crazy things with Samsung and Huawei and those never hurt the hardware

Am i bricked...

While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?

goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?

Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)

It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.

If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!

With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app

The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.

goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE

If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?

enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk

I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)

Unlocking Bootloader - Do I Have a Brick?

Hi all,
I got my AT&T HTC One X today. 1.85. I rooted it successfully and went about unlocking the bootloader following these instructions:
http://forum.xda-developers.com/showthread.php?t=1671396
I got to the point where you exchange the original boot file for the original. When I used the command "adb reboot bootloader" to boot into the bootloader screen my phone went black and has not worked since. No combination of button holding over any amount of time has caused any sort of reaction. Although, oddly enough, holding down the power button makes my computer alternate between the "device connected" and "device disconnected" sounds, so I guess it's not completely dead? ADB doesn't detect the phone at any time.
I think that I screwed up with the hex editing, which explains why it's not starting up - I might have destroyed one of the files it uses to boot. Is there any way to put the original file back, or do I have a brick? Thanks in advance.

KR_Badonkadonk said:
Hi all,
I got my AT&T HTC One X today. 1.85. I rooted it successfully and went about unlocking the bootloader following these instructions:
http://forum.xda-developers.com/showthread.php?t=1671396
I got to the point where you exchange the original boot file for the original. When I used the command "adb reboot bootloader" to boot into the bootloader screen my phone went black and has not worked since. No combination of button holding over any amount of time has caused any sort of reaction. Although, oddly enough, holding down the power button makes my computer alternate between the "device connected" and "device disconnected" sounds, so I guess it's not completely dead? ADB doesn't detect the phone at any time.
I think that I screwed up with the hex editing, which explains why it's not starting up - I might have destroyed one of the files it uses to boot. Is there any way to put the original file back, or do I have a brick? Thanks in advance.
Click to expand...
Click to collapse
I bricked mine the same way. Does it show a light when plugged into a charger? If not it's a bricked up bricky brick. Sorry

gunnyman said:
I bricked mine the same way. Does it show a light when plugged into a charger? If not it's a bricked up bricky brick. Sorry
Click to expand...
Click to collapse
Nope, no light.
Well...crap.

KR_Badonkadonk said:
Nope, no light.
Well...crap.
Click to expand...
Click to collapse
again I'm sorry. I feel your pain. The exact thing happened to me.

If by boot replacing boot thing you are referring to mmcblk0p4, that means you did not edit it correctly and sent it to the phone or sent it to the wrong partition(unlikely). Hex editing should always be done with EXTREME care, and if your not 100% sure u did it right you can always find someone here that can check it or do the edit for you uf needed. Sorry about the brick, that really sucks!
---------- Post added at 05:08 PM ---------- Previous post was at 05:03 PM ----------
Btw, if you just bought it, bring it back and tell them after charging it last night you woke up to THIS.
(Then listen to a couple posts accusing you of making phones too expensive, and being responsible for your actions)
You learned a important lesson here, and I''ll chip in my $0.0001 to getcha back up and running again:beer: