My phone was running CM12.1 (a week old build). Obviously rooted and runs TWRP.
I texted someone and left my phone with the screen turned off for about an hour. When I tried turning on again, nothing happens. The battery was about 80% the last time I used it.
Things I've tried to get it to work:
1. Charging it with the wall charger. [Nothing happens. LED doesn't turn on, phone doesn't turn on]
2. Plugging it into my PC. [PC doesn't read it. LED/Screen unresponsive]
3. Tried vol down key + power to boot into the bootloader. [No response]
4. Tried vol down key + power, then plugged it into my PC without leaving the buttons and waited for a minute. [No response]
Can anyone explain what the hell went wrong with this? I just use my phone for calls/browsing/texting. Didn't overclock anything. It's been rooted since day 1 (2 years back), and I last installed the CM rom a week ago so it wasn't due to a bad flash.
Related
Hi, so I've been doing a fair bit of reading, but I've not really found anything thats exactly like my issue.
So I got the Nexus 4 yesterday, today I've been using it for probably 3 hours, it was charged overnight last night to 100% and was still at about 65% when the phone randomly rebooted, no force close or anything. So it attempted to boot back up, showed the Google logo and then the nexus X, before going to a black screen.
From here I can't turn it back on, I've tried:
Power - up to 60 seconds
Power + Vol Up - up to 30 seconds
Power + Both Vol - up to 60 seconds
I then plugged it in to the wall (using the charger provided), there is no sign of life still, no battery charging screen, no flashing red led.
If I hold down the power button, while the phone is on charge, I do get the flashing red led.
Is this a case of leaving it to charge and assuming the battery is completely drained, or should I be contacting Google to start an RMA?
Should probably say, as I've only had it a day, no root, no custom rom, everything stock and on 4.2.2
Thanks.
Hey everyone,
I don't know what happened wrong with my interaction with AQUOS, but the phone appears to be bricked.
Here's what happened.
Bought my phone from Boost, successfully switched carrier to Ting
Have been using the phone for more than a month without any problems at all
Yesterday, I left the phone without charging and it fully discharged
I plugged it to charge and came back to turn it on after a few hours later. This is when I noticed it wouldn't turn on.
I tried a couple things: holding the power button for a long time, and a hard reset (volume down button + power button). But the results were the same.
The screen doesn't turn on. While holding the power button or power + volume button, the only feedback from the phone is a series of prolonged vibrations (~10 seconds) separated by a brief pause (~1 second).
Have anyone experienced this problem?
Any advice/insight into this problem would be greatly appreciated.
I've had similiar issues with tablets where it completely drained and wouldn't charge via USB. At most it'd just give off a single vibrate and then die before even flicking on the screen. Try this, plug a USB cable in for a full 24hours before you hit the power button. Then give it a try. If it pops on to the screen where its charging after that let it get a full charge before fully powering on. Hope this helps and also hope its not due to the switch to ting.
Best of luck
PHONE OFF
This could be due to a bad usb connection. some usb when broke will actually discharge your phone or tablet so try to use a different usb. PLZ POST BACK IF THAT DIDNT WORK I HAVE MORE SOLUTIONS
Hello.
This is a long shot, but i'm going to ask it anyway...
Some years ago I owned a Droid/Milestone 2, that decided to die apparently.
After a bit of searching, I decided to purchase the XT1058 I currently use and forgot about the droid.
But I've found it again lying around, and tried to start it with no success...
On its finals days, if for some reason you needed to reboot the phone, it would take some minutes for it to power up again. Once it was up and running, it was just fine.
Until some day, minutes became hours, hours into days, and the phone never worked again. While it was in this state, nothing appeared on the screen.
It was just dead... And then, after a minute or so, after pressing the power button, it would boot up and everything would be ok.... until the next reboot at least...
Now, if I connect it to the USB port, the white led on the side stays on. It's not recognized by windows nor RSD, but if you leave it like that, Windows makes the sound of an USB device connection, a few seconds pass and the sound of usb desconnection appears. So there seems to be a bit of life (not much)
I cannot charge the battery because when I connect the charger, white led by the charging port is not on.
It only stays on if I remove the jack just a bit, so it's not fully seated. I do not think it's battery related since when it died I tried different batteries...
Holding the power button does not do anything...
Question is, do you see any hope on this enterprise?. Idea would be to have this as a backup...
Or should I just throw it away?.
Thanks in advance.
Hi Guys,
Before i move on, my phone literary died today, and randomly, managed to get it back to life.
Let me explain my case first.
I have a Samsung A3 2015 (SM-A300FU) which i have constantly updated with new builds, and lately am on a custom rom (with modem and BL updated). Obviously, rooted, custom recovery, custom kernel.
This setup was perfect so far, no issues, at least nothing majorly resetting my phone or ending on a shutdown.
Today i made it at work with 0% battery, plugged it on my charger, and left it to charge until 46%. Turned it on (yes, i charged with phone off), browsed a bit...and just as i was to hit the power button for sleep, the phone got unresponsive and just powered down. I initially thought that somehow an app in the background is delaying things so i even left it see if it recovers, just to see that the phone completely died.
By DEAD, i mean:
1. It wouldn't cold-reset with Vol Down + Power Button.
2. It wouldn't power on obviously.
3. No download mode...how could it work, if the above two didnt work.
4. No what so ever detection in USB from Windows, no qualcomboot or whatever that boot mode is.
I literary left it in the charger for half an hour, no signs of charging, no heat, nothing. Took it out, tried whatever not method with what ever amount of time required to hold whatever button, nothing worked.
For weird reasons, i thought LET'S CONNECT THE CHARGER, WHILE I AM ACTUALLY HOLDING VOL DOWN + POWER BUTTON, AND VOILA, IT BOOTED.
I booted successfully, to find out that the battery is at 0%.
It is impossible to discharge 46% that fast, so the only possible explanation is that it never charged to begin with. What powered it down, probably the same reason, no juice.
To all the HARD BRICKED lads here, can you try the above in BOLD AND RED?
To mods, feel free to axe the thread if things dont get as expected.
You dont know what a hard brick is. What you encountered wasnt it.
Mind you mate, input needed, it is literary the first words of the subject.
Try to correct, and not belittle, and try at least to elaborate.
Hi guys,
I recently had to replace my Essential Phone display (for a second time!). The first replacement few months ago went fine and I was able to boot normally.
Now I replaced the screen again (old replacement broken too), I was able to boot the phone after I installed the display - to test it and all was fine. I then normally shut down the phone.
I glued the screen into the phone and let it sit on the charger for 1 hour, now I try to boot and nothing happens...
Without the charging cable connected I can't start the phone - I tried holding the power + volume down, power + volume up, power + volume up and down, nothing really happens.
When I connect the phone to the charger it boots to "powered by android", show's the charging screen for a few seconds (at about 80%, even though I let the phone discharge before replacing the screen).
Now i'm stuck, I guess I will leave the phone at the charger for at-least 10-20 hours and see what happens.... I was wondering if anyone had similar problems?
Hopefull
I'm having the very same issue here, have you found a fix for it?