Database Info

Is this bricked magic???

Ok, so this is all I can get from my HTC Magic 32A.
It doesn't matter what key combination I press, it is always the same.
So I would like to know is there anyway to fix it?
I tried all known solutions, like applying recovery from sdcard, adb etc.
nothing is possible, because phone is not entering fastboot nor recovery.
But it keeps turning on so there MUST be a solution.
Here is video of what I get when I try to turn it on.
youtube.com/watch?v=TBciNMhoAs8
one more thing that I get is blue led when i press trackball and power button. but no screen turning on...

You haven't told us what you did before getting this...

OK...I got this when tried to upgrade radio and spl...
from then till now i got only this screen...

What have you done?
Have you flashed the radio BEFORE the SPL? Any errors?
BTW that image could be the RUU screen (not sure as I have never updated my phone in that way)

Well don't know what was the 1st thing done, cause my friend did it, and i am trying to fix it. he was trying to upgrade radio to 6.35 and spl to 1.76
so any suggestions?

elegos said:
What have you done?
Have you flashed the radio BEFORE the SPL? Any errors?
BTW that image could be the RUU screen (not sure as I have never updated my phone in that way)
Click to expand...
Click to collapse
Isnt the RUU screen because thats similar to the fastboot one.

So what is this screen?
Any chance to boot up again?

going back to the blue LED when you press trackball, that is the radio bootloader, so ive been told.

yes i know that, but there is no chance to do anything with usb cable.
maybe only with some serial cable an disassembling (opening phone to the parts). and I don't know how to do it, don't have serial cable....etc...

Anybody, anything?

ok...so i took my htc magic to service, and they told me that they'll try to flash it from linux and reprogramme evrything...
still waiting...

Me too,
Anybody have a new idea?
I upgrade radio 2_22_19_26I from recovery (RA Sapphire 1.6.2), then my phone can't access bootloader, recovery console....
Only HTC Magic logo display on screen always.

can you enter fast boot? (back and power buttons)

damjand said:
can you enter fast boot? (back and power buttons)
Click to expand...
Click to collapse
No, I can't enter fast boot, and recovery. HTC Magic logo always appear.

have you tried to flash recovery via adb?
or maybe you should try with goldcard...

Computer not recognize my phone, I can't do anything from computer (adb and fastboot).
What is goldcard? Can you show me?

Does any of you have the blue led??

damjand said:
ok...so i took my htc magic to service, and they told me that they'll try to flash it from linux and reprogramme evrything...
still waiting...
Click to expand...
Click to collapse
Do they were able to fix it?

i am still waiting for my phone...called today, it is still in que for fixing...
this is explanation for goldcard
http://forum.xda-developers.com/showthread.php?t=572683
i have blue led when i press trackball and power...
read somewhere it is kinda a radioloader!?

ronni.rasmussen said:
Does any of you have the blue led??
Click to expand...
Click to collapse
Yes, I press trackball and power button, the blue led is on.
I hope you have a solution.

[Q] I can't turn on my HTC Sensation XE. WHAT TO DO??

Hey i know this thread has similar to others but i'm hopeful i could find something helpful to fix my htc sensation xe..
[Q] I can't turn on my HTC Sensation XE. WHAT TO DO??
ok i tried to charge it for 5hrs but when i tried to oepn it.. i can't turn it on and the led light is always being delayed when i remove the charger..
i dont know what to do..
my previous rom is Ordroid 9.0.0 and i decided to flash another rom to Ordroid 15.0.0 i think i am so NOOOb. that i think that rom i currently installed is for HTC One x but i know it worked fine when i restore a system backup that is )rdroid 9.0.0 and i ended up the Bluetooth error that when you turn it on or some apps turned it on.. it causes a bootloop process.. and trying to drain my battery and when my phone doesnt want to open.. then i realize some process of flashing my rom is wrong.. and i need someone help! i tried everything at some thread ive seen.. but i know my pc doesnt recognize until it opens or power on for bootloader..
sharing this.. that issue "the bluetooth bootloop error.. i get rid of that when it restarts and my phone turned on i tried to be fast and tried to unticked the bluetooth switch and succesful not thinking to turn it on again but when i tried or eventually try to open the Car App.. it opens the bluetooth and boom it restarts again and i cant catch taht swith to turn again.. and it boots always.. and my battery drains.. nad my phone overheats i think and.. it happens!
my thought:
do i need to j-tag it.. actually i dont know that process.. my phone i miss it so much!.. i am such a noob.
--sorry for my wrong english and grammar!

When you connect the phone to the PC, if you can get it to say QHSUSB_DLOAD, then you can try the HTC sensation unbricking project: http://forum.xda-developers.com/showthread.php?p=23078349
Generally, flashing ROMs for other phones will result in a brick... So I guess you learned your lesson the hard way.
By the way, can you boot into bootloader at all? (Remove battery, insert battery, volume down +power button)
If you can boot into bootloader, then you have hope.
Also, do you remember if your phone was s-off before this happened?
Sent from my Ouya

perform a full wipe from recovery and then restore your nandroid

rzr86 said:
perform a full wipe from recovery and then restore your nandroid
Click to expand...
Click to collapse
Hold volume down and power button to enter the bootloader. Then choose the recovery option with the volume buttons and press power to confirm. When the recovery didn't load press volume up and power. Now you are in the recovery. Do a backup and wipe to factory settings.

AndroidSupporter318 said:
When you connect the phone to the PC, if you can get it to say QHSUSB_DLOAD, then you can try the HTC sensation unbricking project: http://forum.xda-developers.com/showthread.php?p=23078349
Generally, flashing ROMs for other phones will result in a brick... So I guess you learned your lesson the hard way.
By the way, can you boot into bootloader at all? (Remove battery, insert battery, volume down +power button)
If you can boot into bootloader, then you have hope.
Also, do you remember if your phone was s-off before this happened?
Sent from my Ouya
Click to expand...
Click to collapse
I can't power it on so.. i'm not able to boot it to bootloader. beacuse i know my phone is not powering on... it charges like the led blinks 5 times and it turns on. but its not. im S-ON and.. i dont know what is S-OFF
thanks for the help

Does your PC detect your phone when you plug it in?
Sent from my Ouya

AndroidSupporter318 said:
Does your PC detect your phone when you plug it in?
Sent from my Ouya
Click to expand...
Click to collapse
Sure did it happens to read my phone but it didnt installed the device correctly so it doesnt work

Do you have the latest drivers on your PC? What about adb and fast boot on your PC?
Sent from my Ouya

AndroidSupporter318 said:
Do you have the latest drivers on your PC? What about adb and fast boot on your PC?
Sent from my Ouya
Click to expand...
Click to collapse
yeas.. and what happens if i have latest driver. my phone was not able to read it through pc

Can you boot into bootloader and connect the cable to the PC? What do you see when you go to fast boot mode?
Sent from my Ouya

[Q] Stuck with bootloop no bootloader access :/

Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:

First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita

timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.

if you are SOFF u can go for RUU?

Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:

sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!

Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.

Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita

timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.

I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita

timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really

Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita

Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL

You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita

timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help

If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app

exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.

sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone

[Q] HTC One S bricked?

After flashing cm-11-20140930-NIGHTLY-ville using recovery-clockwork-6.0.4.8-ville I get "HTC quietly brilliant" logo for a couple of seconds and a black screen. Same problem when holding vol- and pwr (soft buttons are blinking, but no LED indicator).
I tried reinstalling rom using fastboot, but <adb device> shows no device. Probably because there is no USB driver on the phone, since I've wiped it in recovery. Reinstalling HTC Sync manager and some HTC drivers packs didn't help.
Thankful for any idea!

Try to get to the bootloader and post what's written. As it seems alive it should work.
I guess you're S-ON and you didn't flash the kernel with fastboot.

kdd998 said:
Try to get to the bootloader and post what's written. As it seems alive it should work.
Click to expand...
Click to collapse
I cannot get into the bootloader. I mean, I can't see it because my screen is all black.
I guess you're S-ON and you didn't flash the kernel with fastboot.
Click to expand...
Click to collapse
I forgot to check is it S-OFF or S-ON I flashed the ROM with CWM.

Try to hold power during 15 seconds with volume down pressed. It should go into bootloader. If you can't get there I'd be surprised...

Dude, it worked! :good: I bought today some plastic LG sh*t, because I've been without phone for a week :crying: Just came from work and checked Your reply and tried vol- and pwr (but I did this a dozens of times in last couple of days and the only thing that happened is 5x blinks of soft buttons)
Is it possible that my Volume- button isn't working well (I've noticed that sometimes needs pressing harder or twice) or I am just stupid?

Yes the volume down button can be a little tricky. I don't know how to go to the bootloader if you don't have a running OS neither volume down working.

[Q] HTC one m8 hardbricked can't access any thing

I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.

Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know

DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go

piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.

M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset

piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.

Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please

rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.

It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.

rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?

Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..