Hi all .. I have a phone but nothing appears on the screen and when I connect the phone to the charger shows the sign of the charger until the green sign appears, which means full battery .. What do these things show? Is the screen damaged or motherboard problem ? Please Help
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
Jnoubileb said:
when I connect the phone to the charger shows the sign of the charger
Click to expand...
Click to collapse
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
redpoint73 said:
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
Click to expand...
Click to collapse
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Jnoubileb said:
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Click to expand...
Click to collapse
I gave another suggestion about holding the power/vol buttons. I have no idea if you tried, and if so, whether there was any change.
Reading the files on internal storage to me, means the phone is booted to OS. So I agree that it appears the phone is on, but screen is either not working, or somehow darkened all the way.
What is the history of this device, and did anything happen before the current condition? Did it just happen spontaneously, or did you drop it or try to open it to fix anything? Try to install anything? Is the phone modified at all (TWRP, root, etc.) or basically still stock? Even if it happened spontaneously, did it happen when you were using it (and if so, what were you doing exactly)? Or just picked it up and it was this way?
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Jnoubileb said:
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Click to expand...
Click to collapse
Do you have debugging turned on? Know how to use adb?
i think is on before the problem appear
Jnoubileb said:
i think is on before the problem appear
Click to expand...
Click to collapse
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
redpoint73 said:
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
Click to expand...
Click to collapse
the phone now on mtp mode
C:\WINDOWS\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
3a55e345 unauthorized
So it looks like adb is connecting. I think it is saying "unauthorized" since the phone's screen is trying to prompt you to authorize adb commands (which you obviously can't see or respond to). But it is obtaining the device's ID code. Which by the way, is unique to your device. So I would advise to remove it from your previous post. Don't know if it is dangerous for other folks to have this, but better safe than sorry. Simply telling us that an ID code was returned, would have been sufficient.
Moral of the story, I am thinking the phone is booted to OS, just the screen is not displaying anything. Screen may be broken, as you somewhat were guessing from your top post. I suppose there is a possibility it may be some software fault. You can try to eliminate this as the cause, by possibly booting to bootloader, which should allow fastboot access, then flash a stock recovery image. Although it may be tricky without seeing the display. Since if you need to see the display, or select anything during the process (don't recall if you do or not), you are out of luck.
Although I tend to think this is a hardware issue. Screen may be malfunctioning. Or it may be as simple as a loose connector.
Related
My one wont charge or boot. I had it in a pocket in my uniform all day. I only noticed it stop working when I was leaving at the end of the day. I have a black screen and no amount of holding down power or volume keys will do anything. It wont hard reset and I cannot get to the bootloader. I dont get the charging light when I plug it into the computer or charger, however it does get pretty hot as if it is charging. I didnt do any serious software modding to it as I only unlocked the bootloader, installed twrp, and installed ARHD 9.4. Not sure what to do. Any help would be greatly appreciated.
leetlikeawping said:
My one wont charge or boot. I had it in a pocket in my uniform all day. I only noticed it stop working when I was leaving at the end of the day. I have a black screen and no amount of holding down power or volume keys will do anything. It wont hard reset and I cannot get to the bootloader. I dont get the charging light when I plug it into the computer or charger, however it does get pretty hot as if it is charging. I didnt do any serious software modding to it as I only unlocked the bootloader, installed twrp, and installed ARHD 9.4. Not sure what to do. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like the device is "on" but it's locked up with the screen off. When you're holding down the PWR + VOL DOWN button(for at least ~10-15seconds), are you in a brightly lit room or can you shine at light at the sensor? I know it sounds nuts, but there seems to be some safeguard on HTC's part that it will check the light sensor before rebooting in case the buttons get pushed in your pockets.
Alternatively, plug it into your computer and use ADB(or the All in One Toolkit) to issue the "adb reboot recovery" command.
unremarked said:
Sounds like the device is "on" but it's locked up with the screen off. When you're holding down the PWR + VOL DOWN button(for at least ~10-15seconds), are you in a brightly lit room or can you shine at light at the sensor? I know it sounds nuts, but there seems to be some safeguard on HTC's part that it will check the light sensor before rebooting in case the buttons get pushed in your pockets.
Alternatively, plug it into your computer and use ADB(or the All in One Toolkit) to issue the "adb reboot recovery" command.
Click to expand...
Click to collapse
So i tried it in a very lit room but still nothing. I tried adb before but my computer is not even seeing the device. "adb devices" shows nothing and its not a driver issue because I am running linux and I was able to fastboot and adb this device before.
I was thinking the same thing that its kinda frozen. I never thought that not being able to access the battery would be an issue but in this situation it would be extremly helpfull. Maybe all I can do is wait until I am sure the battery is dead and try and charge it and see if the charging light comes on. This really sucks...
leetlikeawping said:
So i tried it in a very lit room but still nothing. I tried adb before but my computer is not even seeing the device. "adb devices" shows nothing and its not a driver issue because I am running linux and I was able to fastboot and adb this device before.
I was thinking the same thing that its kinda frozen. I never thought that not being able to access the battery would be an issue but in this situation it would be extremly helpfull. Maybe all I can do is wait until I am sure the battery is dead and try and charge it and see if the charging light comes on. This really sucks...
Click to expand...
Click to collapse
I just had this happen to me and I followed these instructions and held it closer to the light and it came back on.
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
michal_alton said:
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
Click to expand...
Click to collapse
Send a picture of the bootloader while I find the drivers you need
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though). Just now i've seen a vodafone logo for a very short second when I connected to pc from charger. But phone rebooted again just after.
HTC_Phone said:
Send a picture of the bootloader while I find the drivers you need
Click to expand...
Click to collapse
edit. downloaded drivers (4.8) but that didn't change anything and windows still doesn't pick up device.
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
michal_alton said:
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though).
Click to expand...
Click to collapse
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
michal_alton said:
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
Click to expand...
Click to collapse
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
I think i know what it is. Power button stuck and keeps restarting device. Although i can feel pressing it, this is what it looks like.
nkk71 said:
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
Click to expand...
Click to collapse
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
michal_alton said:
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
Click to expand...
Click to collapse
Good luck mate, but definitely sounds like the power button is stuck
It's been fixed under warranty by HTC. They replaced motherboard on mine HTC. So all good
Hey everyone,
So my friend’s HTC One was having some troubles, he said out of no where it got stuck in the ‘TAMPERED’ screen and he didn’t know what to do. Now he definitely didn’t try to root it or anything like that, it is completely stock. So yesterday he gave me the phone so I could take a look at it. The battery was dead when I got it so I plugged it in and got the red notification light to say it’s charging. A little while later I attempted to turn it on, surely enough I was shown the ‘tampered, locked, security warning etc.’ screen. So I wasn’t really sure what to do from there, I tried to see if I could get into the recovery mode but it just seemed to power down. I booted back up and went to the restore factory settings option, it showed me a progress bar for a bit but powered down again. Now it appears to be bricked… When I plug it in I don’t get the red notification light anymore and I’ve tried holding vol down + power again and again to no avail. I also tried the bright light trick.
If anyone has any ideas on what I could try next I would really appreciate any help at all.
Thanks guys.
the tampered screen wont appear out of nowhere, he must have tried a custom recovery, kernel or something.
IINexusII said:
the tampered screen wont appear out of nowhere, he must have tried a custom recovery, kernel or something.
Click to expand...
Click to collapse
From a bit of googling around I saw some people that let their phones' batteries die completely flat and were faced with the tampered screen when they turned it on again so I guess this is what happened to my friend. I'm sure he didn't try anything custom.
Here are two examples:
http://support.t-mobile.com/thread/60279
http://forum.xda-developers.com/showthread.php?t=2433477
What happens when its plugged the PC. Does it show up at all or does it show QHSUSB_DLOAD. If it does show that, then it is bricked and only a motherboard replacement will bring it back to life. If not then charge the phone for 24 hours. dont mess with it, then holding POWER + VOLDOWN (phone under a bright light,) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot or you may at least get into bootloader.
you may need to try 2 or 3 times, to get it to work.
bored_stupid said:
What happens when its plugged the PC. Does it show up at all or does it show QHSUSB_DLOAD. If it does show that, then it is bricked and only a motherboard replacement will bring it back to life. If not then charge the phone for 24 hours. dont mess with it, then holding POWER + VOLDOWN (phone under a bright light,) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot or you may at least get into bootloader.
you may need to try 2 or 3 times, to get it to work.
Click to expand...
Click to collapse
How can I check for QHSUSB_DLOAD? Install the HTC Sync and HTC drives then adb devices or something?
RoBz18 said:
How can I check for QHSUSB_DLOAD? Install the HTC Sync and HTC drives then adb devices or something?
Click to expand...
Click to collapse
You must have HTC drivers installed anyway. Download and run HTC sync and let it complete. then just uninstall HTC Sync. The drivers will remain.
You must also have adb and fastboot setup on your PC. I take it you are set up for those
bored_stupid said:
You must have HTC drivers installed anyway. Download and run HTC sync and let it complete. then just uninstall HTC Sync. The drivers will remain.
You must also have adb and fastboot setup on your PC. I take it you are set up for those
Click to expand...
Click to collapse
Ok so i got the drivers, adb and fastboot installed. I plugged in the phone and in device manager it is showing QHSUSB_DLOAD under other devices. So for sure now this thing needs a motherboard replacement? Have you ever heard of a phone getting bricked from the restore to factory settings option? Seems a bit strange to me.
I just called my friend to double check with him that he didn't try anything custom...he had no idea what I was talking about so it's definitely all stock here. Why on earth would a factory restore cause a brick? Would I be right in saying that HTC should replace this for free...?
There is no factory restore option. Only factory reset.
Keep out plugged in over night and then tomorrow keep trying to power on with a bright light. It should turn up
sent from my mobile device
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
vessk0 said:
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
Click to expand...
Click to collapse
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Didgesteve said:
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Click to expand...
Click to collapse
Yes, nothing happens...
I can only put it in fastboot mode (blue LED on black screen), while it's connected to the PC.
Well If fastboot works then this shouldn't really be much of a problem , simply fastboot flash any kernel with a custom recovery and flash a ROM. If that doesn't work then you might be facing a hardware issue and the best course of action would be to send it in for repair
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
Can you detect it via ADB? Go to adb ( found in Android SDK ), open command window there and type fastboot devices, something should come up ( Assuming you have the fastboot drivers installed ) You can also use flashtool if you don't have the SDK Installed but install drivers first
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
I think your drivers have not been installed correctly. It is a bit of a hassle in Windows 10 since you need to disable driver signature verification. I successfully installed the drivers from Flashtool after doing this.
i have the same problem but....
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
williamzerner said:
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
Click to expand...
Click to collapse
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
M1chiel said:
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
Click to expand...
Click to collapse
When i try to charge my phone the phone does the same thing.... means the phone boots upto the sony logo red led glows up and the the phone restats ... this repeats forever unless battery runs out...
So, I let a friend of mine use my old M7 in order to repartition/format an sd card (using an OTG adapter). Came back with phone completely dead. I do suspect he ended up partitioning or formatting one of the system partitions in there (possibly the bootloader?) phone was rooted so...
Anyway, situation is as follows: Phone looks dead. Long pressing the power button does nothing, no vibration, no keys light up, no screen comes on.
BUT, when connecting it to the computer I get the usb connection sound on my Windows 10. If I long press the power button for ~10 seconds, i do get the usb disconnection sound, followed again by the usb connection sound. So "something" is alive in there. Also, power+vol down button does reboot the phone.
However there's no way to access recovery, bootloader, adb/fastboot, or even flash a RUU.
It isn't even charging when I plug it in, no red led.
Anything else I could try before giving up?
Thank you.
akpe said:
So, I let a friend of mine use my old M7 in order to repartition/format an sd card (using an OTG adapter). Came back with phone completely dead. I do suspect he ended up partitioning or formatting one of the system partitions in there (possibly the bootloader?) phone was rooted so...
Anyway, situation is as follows: Phone looks dead. Long pressing the power button does nothing, no vibration, no keys light up, no screen comes on.
BUT, when connecting it to the computer I get the usb connection sound on my Windows 10. If I long press the power button for ~10 seconds, i do get the usb disconnection sound, followed again by the usb connection sound. So "something" is alive in there. Also, power+vol down button does reboot the phone.
However there's no way to access recovery, bootloader, adb/fastboot, or even flash a RUU.
It isn't even charging when I plug it in, no red led.
Anything else I could try before giving up?
Thank you.
Click to expand...
Click to collapse
When you here that USB sound when connecting to your pc, go to the windows device manager and look for devices in the usb section. Is the phone showing as "QHSUSB_DLOAD" or simply "HTC Phone" ?
alray said:
When you here that USB sound when connecting to your pc, go to the windows device manager and look for devices in the usb section. Is the phone showing as "QHSUSB_DLOAD" or simply "HTC Phone" ?
Click to expand...
Click to collapse
Hey, thanks for the reply, sorry for the delay. Yeah, it shows something similar to QHSUSB_DLOAD. Looked it up a bit, guess it's completely borked.
akpe said:
Hey, thanks for the reply, sorry for the delay. Yeah, it shows something similar to QHSUSB_DLOAD. Looked it up a bit, guess it's completely borked.
Click to expand...
Click to collapse
Yep sounds like your phone is in Qualcomm download mode. Usually this can happens for 2 reasons.
1- Hardware failure
2- Bad firmware flash
this thread can help: https://forum.xda-developers.com/showthread.php?t=2770684
Hard to tell since we don't know what your friend exactly did or what was used from that usb-otg drive.
A phone shop that can connect to your phone using jtag/riff could maybe fix it but doesn't worth the $$ asked for a 2013 phone, imo.
alray said:
Yep sounds like your phone is in Qualcomm download mode. Usually this can happens for 2 reasons.
1- Hardware failure
2- Bad firmware flash
this thread can help: https://forum.xda-developers.com/showthread.php?t=2770684
Hard to tell since we don't know what your friend exactly did or what was used from that usb-otg drive.
A phone shop that can connect to your phone using jtag/riff could maybe fix it but doesn't worth the $$ asked for a 2013 phone, imo.
Click to expand...
Click to collapse
As far as he told me, he just used an app to try to format the otg drive, multiple times, and after a reboot phone died. He couldn't remember which app he used, but since phone was rooted, I can only guess he actually tried to format some system partition.
I will give the unbricking project a go, need to find a linux machine first. I really know jack about linux, but I guess it's no harm trying it Thank you!