Hey guys
a friend of mine tried to charge his TD from his PS3's USB port. Sadly, this has ment that the screen will now not work at all - completley dead. The phone however, does appear to be working properly but there is no way to confirm this (i.e. it will vibrate etc and make various sounds). It also doesn't seem to respond when plugged in to a PC's USB port.
I've tried a hard reset but this doesn't seem to do anything....
Any ideas?
I charge it off the PS3 all the time; it's only a standard-power USB port so it's not the problem, it's your phone.
Try the following:
- Remove the battery and drain residual power by holding the power button for a few seconds. Leave for a few minutes.
- Plug in to an AC power source, wait 30 seconds, and try turning it on.
- Try going into bootloader (hold vol. down on boot). If you get there, reflash a stock ROM (including radio) and try again.
- Do you feel the vibration on power up? If not, the screen is not the problem.
- If it is the screen, wait until you know it is turned on, then put light pressure in various places on and around the screen. If it flickers at any point, it's a hardware problem.
- If you really can't get anything done, you'll have to take it to a repair shop and get a diagnosis or call HTC / your provider / your insurer.
All the best
Hello guys,
I don't know if anyone have seen this problem but anyway here it is:
A friend of mine gave me his ace 2 that have a totally broken software, this means the phone is not turning on, neither entering download or safe mode. When the phone is plugged into the power outlet there is no battery that appears on the screen. NOTHING at all. When I plug the phone into the PC and press the power on button, the phone does nothing but the PC make this beep sound (when a USB is inserted) and then directly after 2-3 second it makes another beep sound (when USB is removed) and take note that on those 2-3 seconds I did nothing, I just tried to turn the phone on and NOTHING happens. When I retry to press the power button again I can also hear the beeps sounds but still nothing on the screen. I tried to press it for the 3rd time, the same thing happened. Tried to enter download mode, it the same, beep sound then nothing.
When I tried to ask him what have he done he told me that something appeared on the screen (wipe, reset, something similar) and he just clicked yes and ok for everything.
I guess the problem is either that the battery is down and it needs to be changed, or that he completely reset the flash memory of the phone.
Any solution guys? Please help and thanks.
Remove the battery for few seconds and reinsert..
Then try to enter the Download mode...
If it is not working still, then, sorry to say, I think the phone is hard bricked..
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Have you held power and volume down for 14 seconds?
vincent.lorentz said:
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Click to expand...
Click to collapse
How long have you had it plugged in? It sounds like the battery is empty.
Try to leave it on the charger for a couple of hours.
If it does not boot by pressing the power button, you can try to boot bootloader by pressing volume down and power at the same time.
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
vincent.lorentz said:
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
Click to expand...
Click to collapse
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Golf c said:
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
vincent.lorentz said:
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
Click to expand...
Click to collapse
Your screen may be black, but there is a small chance your still in the bootloader. I have read that other people have recovered from a black screen. I still think its worth a try to connect to a PC and see if the factory image flashes after holding power and volume down and after vibration. Those vibrations have meaning.
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
vincent.lorentz said:
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
Click to expand...
Click to collapse
I thought there might be a small chance. At least you will get a new phone. Best of luck.
I hate to tell you this but I had the same issue with a 32 GB 5 inch pixel...It was dead...Everything you have said is what happened with mine.
What happened was the slot the phone was trying to boot into had no bootloader or it was a bad flash...Either way, the slot didn't have a bootloader on it when it tried to boot and that black screen is the result...Google sent me a new one and all was well and they will do the same for you.
This is why I don't trust OTA updates...I manually flash everything and I'm sure to flash the bootloader to both slots anytime I update my phone...Good way to keep this from happening again....Best of luck man
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Thank you very much for your kind support, guys.
Your explanations is very interesting. This means that the strategy implemented for the bootloader itself is not very safe. I would be interested in knowing how such a faulty flash can happen and what are the possible reasons behind. Is there a procedure that can increase the chances for a successful flash by doing some things before the OTA update is allowed to be installed?
xocomaox said:
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Click to expand...
Click to collapse
Believe me, I pressed the button for a very long while also (hours) by blocking the button in such a was that the phone boots up until the battery is discharged. So also such an extreme tray was made. The only consequence was the red light flashing.
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
droidan said:
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
Click to expand...
Click to collapse
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
5.1 said:
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
Click to expand...
Click to collapse
Yes. Bad OTA Flash.
Hold 30secs still nothing.
droidan said:
Yes. Bad OTA Flash.
Hold 30secs still nothing.
Click to expand...
Click to collapse
RMA is your only option so
I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...
olm3ca said:
I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...
Click to expand...
Click to collapse
my device is for the most part of the time in qualcomm mode, but I managed to have access to the phone 3 days ago, installing apps & stuff, worked perfectly well until I had
the bad idea to try to charge it through the charger instead of charging it through my computer...
how I've done it?
I used the power reboot technic :
1) pressing the power button for 1 minute
2) doing nothing for some seconds
3) pressing the power button again for 1 minute
4) connecting the phone to the charger, the red light flashed
5) the battery icon appeared soon after
6) waiting for complete charge, phone rebooting
it worked once, so I suppose it can work again. fingers crossed.
So… I bricked my Sony Xperia XA2 Ultra while trying to install TWRP 3.5.2. Bootloader is unlocked.
Here’s what the phone doesn’t do:
· Doesn’t turn on
· Doesn’t vibrate when power is pressed
· Doesn’t vibrate when power is pressed for a long time
· Doesn’t vibrate when power+vol down is pressed for a long time
· Doesn’t vibrate when power+vol up is pressed for a long time
· Doesn’t light up any LED when connected to a wall charger
· Doesn’t light up any LED when connected to a PC
· Doesn’t light up any LED when connected to a PC with vol up pressed
· Doesn’t light up any LED when connected to a PC with vol down pressed
But here’s what it still does, so at least there’s still hope it may resurrect from the dead:
· It is recognized when connected to a PC as “Other devices / QUSB_BULK”
· It is recognized when connected to a PC with vol down pressed as “Other devices / QUSB_BULK”
· It is recognized when connected to a PC with vol up pressed as “Other devices / QUSB_BULK” but only for a few seconds, and then it disconnects. So at the very least the device “knows” it should be doing something differently when connected with vol up pressed
So it does seem to still hold a chance.
Can you help me out? Thanks in advance!
Are you still struggling?
I often run into this behaviour (I have an XA2 H3113).
Things that work for me.
1. Hold down the three buttons Power+camera+volume_up at the same time without the USB cable plugged in and keep it held, it has taken 30 seconds sometimes to force the reboot.
2. You also say you can 'see' your device on your PC, but don't give much more than that - I am using Linux to manage my phone so I suspect this isn't what you are doing based on your description, anyway you can still download the 'SDK' for windows and try to run 'adb' commands
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
In my Linux case, assuming that I can see my phone
adb devices
You can then force a reboot to the 'recovery' partition to factory reset everything.
adb reboot recovery.
Failing all that I would consider making sure that there is a charge on your battery and that the cable you are using is good enough (some of my USB C cable that I have lying about have proven unreliable when connnecting and/or charging my phone - they are not all the same!), finally I have also found on my Dell Laptop that the USB port that I connect to matters! I have 3 of them on the motherboard and I have found, for no reason that I have bothered to research, that if I use the two on the right-hand side of the laptop, then I sometimes can run adb commands and sometimes I cannot but if I use the one on the left hand side (with the same cables) it never fails.
Your description about being recognised but only for a few seconds does sound like the PC's Cable/ USB connection is unreliable or that you are running at nearly zero battery (you also said you get no lights which IS unusual). If you haven't already, just let the thing charge for an hour or so and see if it really is just a symptom of a low power in the battery.
Sorry that you are having these problems. I often think I have bricked my XA2 (I fiddle about with thing all the time) and have had numerous issues of LineageOS spinning on boot or not being able to get past the Sony flash screen, but usually one of the two things above gets me out of it and into the 'factory reset' mode and that always seems to work.
Good luck!
Hi there! Still struggling.
1. Nothing happens when Power + Vol up + Camera buttons are pressed for 45 seconds without the USB cable plugged in
2. adb commands are not working (they were up until the failed TWRP installation)
3. Battery was charged to 94% when the failed TWRP installation occurred (I see no way of making sure it is now charged). The cable and USB port I’m using are the exact same I was using during the failed TWRP installation.
4. Being recognized only for a few seconds is a characteristic of the mode I’m trying to enter, thus not cable/USB connection related
5. I have left the phone charging for a full night (and no, the charging LED didn’t show up)
Thanks
Any news on the topic? Same situation here.
Hi guys, just got my Xperia XA2 from China after 2.5 months wait. Is a good phone. But did a giagantic software update over Wi-fi and after tapping Restart my new phone is fried. I tried ALL the steps in the first message above of this thread. Need to know should I get a replacement or is this going to happen again so should go for a different phone? Thanks.