I installed the latest RUU, 8.?????, and a few days later my screen is stuck on the white Hboot screen. The down button doesn't work, only the up button whenever I use the up button to scroll down to "power down" it does nothing. I hold the power button until the screen turns black, the screen restarts itself about 10 seconds later back to being stuck on the hboot screen. The hboot screen has the "tampered" banner accross the top as well. Any ideas on how to fix this or do I now have a 200.00 paper weight?
When in hboot, why don't you try to install 182 again?
dudeluv said:
When in hboot, why don't you try to install 182 again?
Click to expand...
Click to collapse
whenever I plug the phone into the laptop...it doesn't recognize the phone anymore...which is strange.
djfrost40 said:
whenever I plug the phone into the laptop...it doesn't recognize the phone anymore...which is strange.
Click to expand...
Click to collapse
Are you in hboot or fastboot?
You need to be in fastboot to get device recoginzed. It should say fastboot usb at the top of screen.
scrosler said:
Are you in hboot or fastboot?
You need to be in fastboot to get device recoginzed. It should say fastboot usb at the top of screen.
Click to expand...
Click to collapse
its in hboot highlighted in blue, it won't let me put it into fastboot.
have you got help? have you fix your problem yet? now i'm having the same problem.
I didn't connect to my computer too, computer can't get the driver automatically.
any help?
install htc sync from HTC. it should install the correct fastboot driver so the ruu can see it.
epic bumps is epic
Related
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.
Power button on my HTC One S stopped working to I decided to fix it. I discharged the phone completely and opened the phone. I got to the switch and it fall apart from the motherboard so I soldered it in place. I dont know what could cause this, but now The phone doesnt want to boot. Its stuck on HTC logo with red warnings. Phone was running great on TrickDroid 9.1.0 before the discharge/opening. However Im able to enter bootloader. I can use fastboot usb ( I triend to flash different boot.img and recovery but it doesnt help. fastboot show flask OKAY but still, phone doesnt want to boot. When I choose recovery from hboot It will reboot into htc logo without warning, the status bar in the corner will pass 2 times and after 30sec it will just reboot into warning logo.
I have HBOOT 1.09.
Does anyone know what happend?
Discharging the phone is bad.This is a common issue, especially if youre using CWM.
If you are using CWM - change to TWRP.
Goatshocker said:
Discharging the phone is bad.This is a common issue, especially if youre using CWM.
If you are using CWM - change to TWRP.
Click to expand...
Click to collapse
Great advice cuz in my opinion 'TWRP' is way better interface but can you give him more detail and I'm sure in this case he would not mind being treated as a noob, I would but I'm not as good as you and Darknites lol :good:
I downloaded t-mobiles ruu and installed it in fastboot. everthing installed fine, updated radio and hboot. But still its looping on htc logo. hboot is 1.14 and is relocked. Any ideas?
krzysiek033 said:
I downloaded t-mobiles ruu and installed it in fastboot. everthing installed fine, updated radio and hboot. But still its looping on htc logo. hboot is 1.14 and is relocked. Any ideas?
Click to expand...
Click to collapse
Re check the power button, and are the touch keys blinking at anytime when you turn on the device?
ultraprimeomega said:
Re check the power button, and are the touch keys blinking at anytime when you turn on the device?
Click to expand...
Click to collapse
They blinking only if I hold the power button for few sec.
krzysiek033 said:
They blinking only if I hold the power button for few sec.
Click to expand...
Click to collapse
Its not good that its still looping after using a RUU but try factory reset or you can try just unlocking the bootloader and trying a custom rom.
Hi Guys
I'm in mildly troublesome waters and I was hoping that the people here would help me figure my way around a solution.
So about a week or so ago, my AT&T one XL (which is on CM10.1 stable) started behaving weirdly; the screen wouldn't turn on but all the touch functionality would still work as I was able to receive calls by just using my instincts on knowing where what should be. Now at that point, if I pressed different parts of the screen, it would turn on for a few seconds and then the screen would black out again. The buttons do light up.
But as of yesterday, my screen won't turn on no matter where I apply pressure to try to get it to turn on. The screen still works and I can randomly turn on 'Google Now' and and other stuff as long as I know where what is located on the screen.
I called in AT&T as my phone is still in warranty and they are sending a replacement. However, I'm now in a bit of a race-against-time to get my phone back to stock and hopefully even get rid of the *tampered* sign that shows up in fastboot. I was wondering what my options are to get this done at this stage as I'm not even able to tell when I'm in the fastboot mode. I'm worried that if I don't send it back with atleast stock settings then I'm liable to pay a replacement fee of 500$!
Also, does anyone have any experience with sending in a phone that was jailbroken and not running stock but still under warranty?
Any help/information would be great!
Thanks
Angadh
your screens cable is loose or damaged. is your phone s-off? do you recall if u had usb debugging enabled?
I was on 2.20 when I rooted the phone so I'm guessing that implies I didn't s-off. No recollection if I left usb debugging on, but I'd like to tihnk I did!
gadha007 said:
I was on 2.20 when I rooted the phone so I'm guessing that implies I didn't s-off. No recollection if I left usb debugging on, but I'd like to tihnk I did!
Click to expand...
Click to collapse
if usb debugging is on:
use adb to boot to blootloader then relock and ruu to 2.20 you would need to s-off to ruu to 3.18 or to spoof the relocked. tampered should disappear when you ruu.
exad said:
if usb debugging is on:
use adb to boot to blootloader then relock and ruu to 2.20 you would need to s-off to ruu to 3.18 or to spoof the relocked. tampered should disappear when you ruu.
Click to expand...
Click to collapse
Thanks for the info, exad.
So what I tried now was to use the hasoon all in one kit and clicked on the 'Boot into Bootloader' under commands. I got 'error: device not found'. That implies I'm not in USB debugging, right? So do I have any other options from here?
gadha007 said:
Thanks for the info, exad.
So what I tried now was to use the hasoon all in one kit and clicked on the 'Boot into Bootloader' under commands. I got 'error: device not found'. That implies I'm not in USB debugging, right? So do I have any other options from here?
Click to expand...
Click to collapse
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
exad said:
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
Click to expand...
Click to collapse
The phone just seems to boot back up to CM. Ican't tell if I'm doing something in fastboot that makes it go back into CM. Any other ideas? or indicators?
gadha007 said:
The phone just seems to boot back up to CM. Ican't tell if I'm doing something in fastboot that makes it go back into CM. Any other ideas? or indicators?
Click to expand...
Click to collapse
thats all ive got.
exad said:
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
Click to expand...
Click to collapse
Okay. So i was just messing up but after multiple attempts, I finally did it. Thanks for the help. You are awesome!
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Sv22 said:
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Click to expand...
Click to collapse
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on)
If you still can't see the screen while in bootloader, then your screen is dead.
exad said:
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on.
If you still can't see the screen while in bootloader, then your screen is dead.
Click to expand...
Click to collapse
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Sv22 said:
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Click to expand...
Click to collapse
ok.. did you try what I posted above?
exad said:
ok.. did you try what I posted above?
Click to expand...
Click to collapse
yes, but nothing. ADB show me list devices blank, fastboot no devices.....mmhhhh....I have no word. This morning was alive...
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Sv22 said:
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Click to expand...
Click to collapse
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
redpoint73 said:
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
Click to expand...
Click to collapse
my devices is s-on.
I hate this kind of situation. Very comic......
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.