Database Info

[Q] Sensation stopped working completly

First off, i'm not bad with computers, but apparently not so great either.
Also tried searching, but I couldn't find it.
Then my question.
I tried to unroot my phone and followed this guide of the unlocker.
downloaded a RUU (after a lot of searching for mirrors) and I think it didn't work properly.
Either way, I continued with the guide doing the following in the cmd on windows
adb reboot-bootloader
fastboot oem writesecureflag 3
fastboot reboot-bootloader
now, my phone doesn't do anything anymore. Doesn't charge (or atleast the LED does not turn on) can't turn the phone on, nothing. I checked the SD card and that is still all in tact.
Is there any way to let my phone work again?
I would really appreciate the help!
Phone specifications
HTC Sensation (3g)
Vodafone NL Carrier.

If you remove the sd card and the battery, than after some seconds re enter just the battery and try to turn it on, does the htc logo come up? Does the screen turn on?
Sent from my HTC Sensation using XDA

Did not work, unfortunately

if it doesnt even charge sounds like it bricked...

Did the RUU flash ok? Got any errors?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

It did not i found out later

So battery taken out and let sit for a few seconds and still nothing..sounds disturbing. try putting the battery back in and press the power button and the volume down together at the same time for a few seconds.. anything?

I"m having the same issue with mine. S-Off, root and CID all went perfect. Went into clockwork, installed/ran the superwipe program, flashed the AHDRev ROM successfuly, then installed the 'bricked' kernel. Also went successfully.
Then popped battery, then nothing. LED flashes to indicate charging, but phone refuses to boot. Popped battery up to 10 minutes, also tried whilst on charger
Nothing in fastboot cmd prompt either

TristanSchaaf said:
It did not i found out later
Click to expand...
Click to collapse
Did you also use clockworkmod or 4ext?
I wonder if that's the pattern
ARHD specifically ask for 4ext in the guide.
Sent from my HTC Sensation using XDA

Believe it or not but batteries dying or defective can result in the same issues I'm seeing. My sensation had to have a battery replacement before. Led indicator stays orange and black screen occurs. I don't know if that's what the problem is and it can be a handful of different things. Sorry to hear about your phones. Hope you get it up and running again
Sent from my HTC Sensation 4G using Xparent Cyan Tapatalk

[q] htc one x 1 week brick, help please!

Firstly hello to everyone
I have a terminal free HTC one X bought one two weeks ago that will not start, I summarize a bit.
- On the second day of having it root, change firmware and put Jellybean 4.1 Htc one x 8.50 maximus.
From day one it was hard to load, if you were using the battery was up maybe 3 or 4% in a very short time and lasted Rom both the original and this
After 4 days of being hung root is about 2 or 3 times and had to turn it off, it was hard on.
Being root and seeing that the symptoms I thought it was the battery, I proceeded to change it and still the same, will not start, when it does after insisting often connected to usb cable original (after many attempts) by pressing power + volume - enters the menu but hangs after a while if you use it or install a Rom. No to that is the problem, if the firmware or hardware problem.
No red led charging or pc usb original charger or usb. I checked with a tester consumption and 1.6 W when brand power and volume pulse at 10 seconds up to 1.8 W and down again to 1.6 w
In this moment my htc is a brick..
Someone could give me some advice before sending it to repair and gatarme money? thanks

Firstly, questions belong in the Q&A section.
Secondly you can RUU back to factory setup and see if it works correctly then. If it does then you can reroot and install custom Rom again.
Sent from my Venom 1

I think maximus rom is for the international one x. If yours is an att one x and you put an international ROM on it its bricked and more than likely is unfixable
Sent from my One X using xda app-developers app

Yea maximus is a international rom ur hosed
And this should have been put in the q&a section
I guess the topic in all caps escaped your eyes
Sent from my HTC One XL using Tapatalk 2

Its not clear, were you ever able to boot into Maximus? If so, you have the international (Tegra3) One X, and are in the wrong forum. Otherwise you flashed a ROM for the wrong device.
Try charging (use wall charger, not USB) for several hours. If no charge light still, you're screwed.

can you still boot into bootloader?

[Q] Bricked one s

Hi mates
I bricked my HTC One S. It was running on ViperS rom long time but i want it flash back to stock rom but i didnt find any new tmo de rom and old didn't work. So i changed cid to supercid. Installed stock EU RUU without problems. Ota update worked after it so i updated it 2 times and next update was to 4.1 that was what i needed but after download during installation something happend, I wasn't watching on screen. I saw only how display turned off and now its good brick . Black screen without, connection to pc its only making conect and dc sound for 30secs in windows( same sound when i disconnect usb device). Neither led don't turn on after connecting to charger.
Any ideas? how to flash BL to mainboard? I reaed about some company which is flashing it. Do u know where is it or have some contact?

Have you checked out this thread?
http://forum.xda-developers.com/showthread.php?t=1990043
[TUT] Downgrade/Unbrick Ville S4
Sent from my HTC One S using Tapatalk 2

droidmakespwn said:
Have you checked out this thread?
http://forum.xda-developers.com/showthread.php?t=1990043
[TUT] Downgrade/Unbrick Ville S4
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
No, it can't help me coz phone is dead i cant turn it or connect with pc adb says no devices found

adb is weird.
Whenever I think my phone is dead (when I do something stupid), I first hold down the power button for five to six second, and see if I get the blinking lights at the bottom of the screen. If nothing, I plug the phone to charge (to make sure it hasn't died. I leave it there for a good hours. Then try the power again. If I don't get anything after that, then I'm positive that I've bricked it.

firefiber said:
adb is weird.
Whenever I think my phone is dead (when I do something stupid), I first hold down the power button for five to six second, and see if I get the blinking lights at the bottom of the screen. If nothing, I plug the phone to charge (to make sure it hasn't died. I leave it there for a good hours. Then try the power again. If I don't get anything after that, then I'm positive that I've bricked it.
Click to expand...
Click to collapse
No he really has bricked because of having SuperCID and doing the JB OTA.

Holy crap, I was actually going to do that. Whoops.

firefiber said:
Holy crap, I was actually going to do that. Whoops.
Click to expand...
Click to collapse
Ya I would just wait in till it comes out for your CID.

Random drops to QHSUSB_DLOAD

For about a month now my phone has been randomly restarting into qhsusb_dload.
I flashed the international ICJ, bricked my phone, sent it away for repairs. I sent it to mobiletechvideos, they repaired the brick and gave me s-off.
After the repairs it worked fine for ~1 month.
Now, the phone will almost always boot to qhsusb, though I can get it to boot into the rom/recovery/bootloader.
I've tried changing roms and even hboot versions but I'm too inexperienced to track down the problem.

I'm confused as to your problem... qhusb_dload is a complete brick, yet you say that you can fix it?
Sent from my evita

I'm just as confused as you.
My phone will spontaneously shut down, no lights or anything. When I plug it in and check device manager I see the qhsusb_dload.
But then after I give it some time and fondle the buttons just right it reboots and I'm back to my bootloader.
I can boot into a rom but it usually doesn't last very long (~1hour) before I get a reboot.
The phone isn't always completely bricked...just sometimes?

It is possible to enter that mode without bricking. Typically holding volume up instead of volume down which goes in to recovery, when booting.
How often does it happen?
Sent from my One X using xda app-developers app

It happens about half the time when at boot it and then frequently at rom startup. I've never had any trouble booting into recovery or the bootloader, and it does seem more frequent when the battery is under 40% (but that just may be me.)
I'd say it's down 75% of the time.

Is your phone s-off?
Sent from my One X using xda app-developers app

Yes, but I paid to have it done so I don't know how it was s-offed

So long as its soff in the boot loader that's all that matters. Its a pain in the ass but I would ruu and stay stock to see if it keeps happening.
Sent from my One X using xda app-developers app

Ran the RUU, now my phone won't boot to a rom. I can still get to the bootloader and the recovery though. All I get is a boot loop to the htc white screen if I let it do it's thing.

Ruu and stay stock for a while to see if it keeps happening while stock.
Sent from my One X using xda app-developers app

Bricked my phone?

So I was trying to revert back to stock on my One X. I flashed stock recovery, re locked the phone and then downloaded the newest update from HTC's website. Everything went according to plan until the update finished and my phone no longer worked. It appears to turn on based on when i plug it into my computer it makes the "hey you plugged in a USB device" sound and when I long hold the power button it makes the disconnect sound. There is no display whatsoever.
What I have tried.
- Cannot boot into recovery
- Cannot get adb to recognize my device
- Cannot get fastboot to recognize my device
- Charged with HTC power brick and cable for 24 hours to validate it wasn't dead. No charge light while charging
Seems unlikely, but does anyone have any idea? Thanks in advance!

Sounds like a hardware problem, if the display/charge light don't turn on at all :S

Doesn't sound like hardware at all to me, sounds like user error. What ROM were you on when you flashed the OTA?
Sent from my Evita

If you were SuperCID, S-on, and tried to flash the Jellybean update, you are bricked, per my PSA sticky at the top of General. If this is the case, time to JTAG.
Sent from my HTC One XL using xda app-developers app