So, I decided to flash and use the only single rom that was posted in the development section. It was working great.
Today as I got into my car, and started driving, the screen went black. Battery was charged at the time to 80% or so.
I cannot get into fastboot, recovery etc.
Tried different combinations
Power vol +
Power vol -
power only
power vol - and vol up then plug cable
There is no vibration, sound, image. Nothing it was dead.
I get back home, throw it on the wireless charger and it boots up to the rom where I left off, no problem.
Rebooted to bootloader, flashed the latest december image just in case, rebooted fine. Then i went to turn the phone off regularly. Then it won't boot back on.
I tried to search if it was stuck on something like EDL and found nothing. The computer is not detecting anything when I plug it. I tried a few blind tests to run fastboot commands after different variations and no luck.
I tried to plug it in, and put it on the pixel charger stand again, and nothing is turning on. I took it off for a few minutes, put it back on and nothing.
I think it may be a case of checking the last flash-all log and all flashed on slot b, maybe that's the issue. I am trying to get back to fastboot with no luck!
Any advice on what's going on over there?
Mine did the same thing when I used a custom ROM. The screen went completely black and there seemed to be no response from the key combinations.
Thanks to a write up by CZ Eddie I held the Power and Vol - for about 25 seconds and saw the fastboot screen flash. I then did it again and the same thing happened with the fastboot screen flashing and disappearing. I just kept doing this key combination over and over and finally the fastboot screen stayed there. At that point I was able to flash the stock December patch. I was still having intermittent issues and had to do a clean instill (with the -w intact).
Thanks to CZ Eddie as I never would have persisted.
You can read his write up in the guides section under "[WARNING] Do not boot TWRP to inactive partition".
Hope this helps!
DIXZ06 said:
Mine did the same thing when I used a custom ROM. The screen went completely black and there seemed to be no response from the key combinations.
Thanks to a write up by CZ Eddie I held the Power and Vol - for about 25 seconds and saw the fastboot screen flash. I then did it again and the same thing happened with the fastboot screen flashing and disappearing. I just kept doing this key combination over and over and finally the fastboot screen stayed there. At that point I was able to flash the stock December patch. I was still having intermittent issues and had to do a clean instill (with the -w intact).
Thanks to CZ Eddie as I never would have persisted.
You can read his write up in the guides section under "[WARNING] Do not boot TWRP to inactive partition".
Hope this helps!
Click to expand...
Click to collapse
Thank you. I have tried, nothing is flashing and no response what so ever. I did read his post before I posted here.
How long before waiting each time for the combination do you remember?
It was always around 20 to 30 seconds.
Be patient and keep trying, you have nothing to lose. :good:
DIXZ06 said:
It was always around 20 to 30 seconds.
Be patient and keep trying, you have nothing to lose. :good:
Click to expand...
Click to collapse
Yeah, i've been trying, left on the charger overnight and no luck. tried about 300 times or something!
Hold vol+ and power for 60 seconds
AnierinB said:
Hold vol+ and power for 60 seconds
Click to expand...
Click to collapse
That totally didn't work
Hold power and both vol + and - at the same time.
matteosaeed said:
That totally didn't work
Click to expand...
Click to collapse
Oh well thought I'd suggest it as it works on some devices
AnierinB said:
Oh well thought I'd suggest it as it works on some devices
Click to expand...
Click to collapse
Thanks for suggesting. It seems like its totally out. I even tried the qualcomm driver just in case, and nothing is detected. This sucks!
Similar (but not identical) bricked Pixel XL 3
So as of an hour or two ago, I now own a completely bricked Pixel 3 XL.
I had not tried to root or sideload or do anything custom to it. It was working fine (today) and suddenly, wouldn't wake up out of sleep with either the power button or the fingerprint sensor. I've plugged it in using the charger and cable that came with it, no response in anyway. I've put it on the official wireless charger stand, where the light briefly comes on when doing so, but quickly turns off again. I've tried various combinations of holding buttons down for over 30 seconds each (power + voldown, power + volup, power + voldown + volup), but still nothing. I have let it charge for over 30 minutes, but still nothing. Plugging into my laptop has no response on either device.
I hadn't been notified about the December 2018 update as yet, but I suppose if that had started automatically downloading just before it bricked, even without actually installing it, that could have somehow caused the issue?
I also had a problem about 48 hours ago, for a period of around 18 hours, where every app would have its visible page/tab/screen refreshed by the OS at random intervals, (similar to what happens when the Play Store app is updating apps, after it installs the new version of each app). I have no idea if this could be related.
Anyone have any other suggestions of things to try? I'm obviously pretty unhappy about this, and weirdly it happened just as I was putting the device packaging away, thinking that everything would be fine with the phone, having already owned it for about a month.
One thing I haven't seen mentioned is when doing the button combinations you need to release the power button first once the fastboot screen pops up.
airmaxx23 said:
One thing I haven't seen mentioned is when doing the button combinations you need to release the power button first once the fastboot screen pops up.
Click to expand...
Click to collapse
Thanks but nothing comes up on my screen at all, whatever I hold down.
Went to bed last night with the Pixel 3 on the wireless charger, dead this morning. No charging light, no vibration, no power. I've let it charge for hours all day on different chargers, including the original. Called Verizon, they are sending a new one. I've tried all of the usual tricks, no luck.
jasonnt said:
Went to bed last night with the Pixel 3 on the wireless charger, dead this morning. No charging light, no vibration, no power. I've let it charge for hours all day on different chargers, including the original. Called Verizon, they are sending a new one. I've tried all of the usual tricks, no luck.
Click to expand...
Click to collapse
Pixel Stand or other wireless charger and if different, which one?
DIXZ06 said:
It was always around 20 to 30 seconds.
Be patient and keep trying, you have nothing to lose. :good:
Click to expand...
Click to collapse
Thanks man, I almost send back my Pixel 2 to RMA, but this returned fastboot so I can continue flashing.
Related
Hi,
I'm sorry if this has already been answered I just can't find it.
My Wildfire's screen froze a couple of times, then the last time I removed the battery and reinserted it.
When I tried to power back up I got the vibrate but nothing on the screen, so I repeated a couple of times with no luck.
I then tried the Hboot method (Hold vol - and power) and I got the Hboot on, but when I tried to navigate using the volume buttons nothing happened, so removed battery and tried to repeat, I couldn't get back to Hboot. I have only been able to get the Hboot screen that one time.
When I power up, I get 1 vibrate and nothing on screen.
When I hold volume + and power button, I get three vibrates and the green light comes on.
When I hold volume - and power I don't get any vibrates, unless I remove the volume - then the power button but still only one vibrate.
I've tried installing the CyanogenMod but no luck.
Is there anything that can be done to save my Wildfire?
Thanks in advance for any help!
Seems like you're in Qualcomm Diagnostic mode. Though I don't remember the solution, some Googling might help
Sent from my HTC One S using Tapatalk 2
Any help please
I've tried the method stated on this forum but with no luck.
Does anyone have a suggestion?
Thanks!
--- EDIT ---
So you wrote your question again in the "Wildfire S" (Marvel) Forums - in this case the much more important question would be: what phone are you talking about? A Wildfire (Buzz) or a "Wildfire S" (Marvel). Despite the name those have almost nothing in common - they are totally different devices
--- EDIT ---
I'll answer in this thread although you opened another one in Q&A.
You haven't been too specific with your problem but sometimes it helps to have all the details
So here we go:
a) did the phone work correct (besides the freezes) before you took out the battery?
b) is your WF rooted & s-off?
c) which ROM?
d)
When I hold volume + and power button, I get three vibrates and the green light comes on
Click to expand...
Click to collapse
does this happen when connected to PC or charger or not
e)
When I hold volume - and power I don't get any vibrates, unless I remove the volume
Click to expand...
Click to collapse
did you hold both at least 5-10 secs or so?
f)
I've tried installing the CyanogenMod but no luck
Click to expand...
Click to collapse
you mean after your problem occured? How did you do that?
Believe me: the more details you provide the more likely someone might have a solution or at least an idea what's going on
OK, sorry for the lack of info!
My phone is a Wildfire, not a WildfireS.
A: Yes, was working.
B: No, never needed to.
C: Not sure, never kept a record of it. It's one of the first models though if that helps.
D: This happens without USB cord attached. When the USB cord is attached I pull the battery and the green light stays on.
E: Yes, I've tried this for over 10secs before.
F: Yes, after blank screen. I installed on SD card and followed the directions. Bare in mind, I cant set Debug or the charge only setting.
Thanks!
stefan2519 said:
OK, sorry for the lack of info!
My phone is a Wildfire, not a WildfireS
Click to expand...
Click to collapse
ok, you should mention it in the Marvel forums, too, to avoid misunderstandings At least you're in the right forum here.
B: No, never needed to.
Click to expand...
Click to collapse
That's what I thought. In this case you won't be able to flash any other ROM - you could just do the usual upgrades by HTC
This doesn't sound to me to be a minor problem (but probably someone else might correct me here) - nevertheless - just to make sure: have you tried to do a hard factory reset following the HTC user guide?
- With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button (instead of holding it)
if this boots your phone up:
- Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
- Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
- Press VOLUME UP to start the factory reset
(errm and yes: this will delete all your user data, of course...)
Click to expand...
Click to collapse
But I assume you have done that anyway - did you try to connect your phone to the PC (HTC drivers installed, of course)?
How about charging - does the phone seem to behave normal - i.e. if you keep it from charging for a few hrs does it show the red LED for charging mode and the green one for being fully charged?
That's pretty much all I could suggest from scratch. - Hopefully someone else with a good idea will step in here :fingers-crossed:
OK, still have the Wildfire with the annoying blank screen.
Does anyone have any suggestions on a fix?
Thanks!
stefan2519 said:
OK, still have the Wildfire with the annoying blank screen.
Does anyone have any suggestions on a fix?
Thanks!
Click to expand...
Click to collapse
besides the suggestion of the Qualcomm diagnostic mode (no I don't know anything about that): did you try to power up without the sdcard, yet?
Furthermore I slightly remember that you could do a factory reset using a key combination - but I'm not sure about it.
Same goes for a RUU. Are you able to connect to the phone with the PC?
Really just random guessing - hard if no error messages appear...
Yes, tried with the SD card.
Because I can't see the screen I tried it loads of times, all with different combinations.
I can't get any vibrate from volume down + long hold power.
I will only get a vibrate from volume down + short hold power.
What would be ideal if there's a way to use ODIN PC to flash a new ROM, well that's what I think it is, faulty ROM?
Thanks!
stefan2519 said:
Yes, tried with the SD card.
Because I can't see the screen I tried it loads of times, all with different combinations.
I can't get any vibrate from volume down + long hold power.
I will only get a vibrate from volume down + short hold power.
What would be ideal if there's a way to use ODIN PC to flash a new ROM, well that's what I think it is, faulty ROM?
Thanks!
Click to expand...
Click to collapse
really hard to say as there's not a little information what's going on. What if just the screen is dead? have you tried to wait after boot and insert your pin after a while (I mean try to guess where the numbers might be) and call your number?
Why anyone want's to use ODIN on non-samsung?!
ODIN is purely just for SAMSUNG products
If you have warranty.. put it to service centre.. they will fix it
Need hard reset power off your phone press volume DOWN and power. YOU WILL FIX IT EASYLI.
Sent from my HTC Wildfire using xda premium
Hey there!
I'm bumping this because I have the same problem and creating a new thread seemed more bad to me.
Anyway, I'll start from the beginning.
I found out my battery was swollen 5 days ago. It's probably because of my charging habits. My battery life have shortened everyday this 5 days. Yesterday morning I wiped my battery stats to get a better battery life. When I was back home my phone's battery has depleted while I was listening to music.
I came to home, plugged my phone to charge and waited 15 mins to get it charged a bit to open. When I tried to open it, it vibrated but the "green htc text on white background" screen didn't come up. The screen wasn't working. I tried what is said before in this tried. Once I got managed to see the bootloader but the volume keys weren't working (as above) After some moments of rage, my brother offered to test the touch, I opened the phone, (as I dont have a PIN) we waited for some minutes and then he called me. I mimiced the answering gestured and boom, I could talk with my brother.
I bought a new screen as I think screen is broken. But it could be because mainboards screen part is damaged (probably because of my faulty battery, voltage wavings etc.) or something completely different.
Please guys help me. I can't buy a new phone atm so I have to fix this
zephyri-xr said:
Hey there!
I'm bumping this because I have the same problem and creating a new thread seemed more bad to me.
Anyway, I'll start from the beginning.
I found out my battery was swollen 5 days ago. It's probably because of my charging habits. My battery life have shortened everyday this 5 days. Yesterday morning I wiped my battery stats to get a better battery life. When I was back home my phone's battery has depleted while I was listening to music.
I came to home, plugged my phone to charge and waited 15 mins to get it charged a bit to open. When I tried to open it, it vibrated but the "green htc text on white background" screen didn't come up. The screen wasn't working. I tried what is said before in this tried. Once I got managed to see the bootloader but the volume keys weren't working (as above) After some moments of rage, my brother offered to test the touch, I opened the phone, (as I dont have a PIN) we waited for some minutes and then he called me. I mimiced the answering gestured and boom, I could talk with my brother.
I bought a new screen as I think screen is broken. But it could be because mainboards screen part is damaged (probably because of my faulty battery, voltage wavings etc.) or something completely different.
Please guys help me. I can't buy a new phone atm so I have to fix this
Click to expand...
Click to collapse
Ouch sounds like a rough one :/ OK so you have no visual, but do have touch and audio? Are you s-off or s-on? You could try to "blind feed" the rom.zip of a ruu to the bootloader to try restore it. But it may well be that your battery has killed the screen. Have you ordered a new battery?
tapped out from my sexy sensation XE
heavy_metal_man said:
Ouch sounds like a rough one :/ OK so you have no visual, but do have touch and audio? Are you s-off or s-on? You could try to "blind feed" the rom.zip of a ruu to the bootloader to try restore it. But it may well be that your battery has killed the screen. Have you ordered a new battery?
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
I'm S-OFF. I had it written in my old sig.
I too think that it was the battery that killed the screen. Ordered both a screen and a battery but they won't be coming before 20 days at least. Damn you China, why you have to be that far.
Anyhoo, I can't get to the bootloader anymore. Or I think I can't get it. I once managed to get it but volume buttons weren't working. After that in every try I couln't see the bootloader screen. But you're right. When I can't see the bootloader, it doesn't mean I don't get the screen. I could do it with a fellow's help. But only after a few days. I'm getting a surgery in 10 hours. Can't really care about my phone right now
zephyri-xr said:
I'm S-OFF. I had it written in my old sig.
I too think that it was the battery that killed the screen. Ordered both a screen and a battery but they won't be coming before 20 days at least. Damn you China, why you have to be that far.
Anyhoo, I can't get to the bootloader anymore. Or I think I can't get it. I once managed to get it but volume buttons weren't working. After that in every try I couln't see the bootloader screen. But you're right. When I can't see the bootloader, it doesn't mean I don't get the screen. I could do it with a fellow's help. But only after a few days. I'm getting a surgery in 10 hours. Can't really care about my phone right now
Click to expand...
Click to collapse
As always man look after your self, then your family and friends, then your tec
Damn china indeed well I believe I know the blind flash procedure so hit this thread when you are better and will will rock on
tapped out from my sexy sensation XE
heavy_metal_man said:
As always man look after your self, then your family and friends, then your tec
Damn china indeed well I believe I know the blind flash procedure so hit this thread when you are better and will will rock on
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
Hey I'm back
First I have to ask, do you get a vibration feedback when you are getting into bootloader by VolDown + Power buttons?
zephyri-xr said:
Hey I'm back
First I have to ask, do you get a vibration feedback when you are getting into bootloader by VolDown + Power buttons?
Click to expand...
Click to collapse
I don't think so :-\ it just depends. If its going to do it standardly then it will go once, if it goes 3 or 5 times your in trouble...
Tapped out from my sexy nexus 7
heavy_metal_man said:
I don't think so :-\ it just depends. If its going to do it standardly then it will go once, if it goes 3 or 5 times your in trouble...
Tapped out from my sexy nexus 7
Click to expand...
Click to collapse
I'm just not sure I can get into bootloader. When I Vol- + Power no vibration, no light on softkeys nothing.
There is no vibration when going to bootloader.
So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
djdoubt03 said:
So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
Click to expand...
Click to collapse
Sounds like your battery is dying. Might wanna look into getting a new one.
BWolf56 said:
Sounds like your battery is dying. Might wanna look into getting a new one.
Click to expand...
Click to collapse
Interesting, I have not had any issue with the battery. I'll look into it. Any way to test without using another battery?
Anything else it could be?
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Not that I know of I have only seen replacing it fixes it
Ive seen several people report that opening it up and jiggling the button can help, but when it does it is only temporary.
djdoubt03 said:
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Click to expand...
Click to collapse
It's fairly easy to replace. You can buy a button off ebay for fairly cheap and look on YouTube to replace it.
Sent from my SGH-I747M using XDA Free mobile app
I agree it sounds like a stuck power button. My experience with this problem first showed in a captivate of my moms. It was very bizarre tho. On stock ROM it would constantly do the vibrate, cycle, vibrate etc. On a custom ROM however, it has had zero problems with the power button. Maybe try that? Not a sure fire fix, just telling what happened with the Cappy. ☺
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
norbarb said:
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
Click to expand...
Click to collapse
That's actually fairly dangerous for your device. I would suggest an air duster if you think it's dirty.
I'm actually having the same problem. It just started his morning.
The phone won't boot normally. I get the kernel boot screen, sometimes a Samsung screen, and then it turns off. 2-3 seconds max.
I can get it into download mode, but after 3-4 seconds, it spontaneously shuts off.
Recovery mode (CWM) is completely stable. I can get in, make back ups, perform a key test, etc. When I run a key test, it shows that the power button is a little sensitive, but not crazy. If I jiggle it some (mostly back a little) it registers a key press, even if I'm not fully pressing it. If I do press it fully, sometimes it doesn't register.
If this is really a button issue, why is recovery stable? Even if I put the phone on a flat surface with nothing that could touch the button, the phone still doesn't stay in download mode (it just shuts off.) When I put the phone in recovery, place it on a flat surface, and perform the key test, the phone isn't registering a key touch.
I've tried 3 different batteries, kept the phone plugged in, popped the battery and held the power button to discharge everything, wiped the cache, wiped dalvik cache, and used CWM touch to reboot (and avoid the power button all together.)
The only think I can think of that's maybe different is that gapps was FC'ing more than normal this morning (before the phone crapped out.)
I'm running StockMOD ROM 4.4.2 R2 with the Ktoonsez Kernel for TouchWiz 4.4.2.
EDIT: Also, when it's plugged in, the LED doesn't light up. I'm not sure that it's actually charging. I do have a wall charger, so I can verify that the batteries I'm using are charged.
Try flashing a different rom from recovery to see if it still happens. Also try a factory reset. If you get as close to stock as possible and it still happens it raises the probability thst its hardware.
If you put the battery in and wait a few moments does it turn on by itself?
Band-aid
@DocHoliday77 I messed with the phone a little later tonight and recovery became unstable. I'm convinced it's a power button problem now. I think the internal mechanism gets stuck and that's the issue.
When I put the battery in, the phone does try to boot by itself.
I used the advice in this post: http://forum.xda-developers.com/showthread.php?p=53915864 and I was able to get up and running again. I opened the phone up, blew some compressed air on the button, tapped the flat side of the button lightly a few times with the end of my screwdriver, and put everything back together. I was able to get back into recovery, and then reboot normally.
I ordered a new power button and I plan on replacing it next week when it gets here, just to be on the safe side.
You guys at xda are life savers!
The booting up on its own after inserting the battery is a classic symptom of the power button going bad. Glad to hear you got it working for now, and that you are ordering a replacement. Everyone ive heard about getting it to work using any number of methods have always found it to only be a temporary solution.
Just a thought, in case it starts up again, maybe remove the plastic piece until you replace the switch. Hopefully that would help prevent it from getting accidentally pressed in your pocket or by bumping it into something. (You could probably still access it with a toothpick or something like that if needed)
I agree it's the power button. I just posted about my little experience on Google+
I tried seriously whacking it on the floor and everything. I wouldn't recommend that but I had no warranty and no funds for repair. Others had said that beating the crap out of it worked so I thought why not lol...
https://plus.google.com/116004961340303353216/posts/ig2ogLeUWJ8
Long story short, my beating it up didn't work but it did wake it up. It falling on the floor however, jarred whatever was stuck and it now works like a charm...good luck
Hey guys
I was super happy with my Australian Telstra M9 until an hour ago. I plugged it with 3% of battery in for charging and turned it off to speed the process up. When it was off the charging icon showed up just as usual. After a few hours I came back, unplugged the phone and it flashed 100% for a second. After that - nothing! It just won't turn on! I pressed every button and every possible combination of those. I plugged it back in for a bit and connected it to my laptop. But it's not even recognized. I googled for a bit but found no solution. I rooted the phone a couple of weeks ago but didn't do anything like that today. No updates, no new apps only some WhatsApp and 9gag.
What do you reckon? Is it bricked? Will I get a replacement and how long will that take? I have to leave Australia in 9 days so I'm quite on a schedule. -.-
Does anyone have any advice?!
Cheers Max
Edit: is there a chance to recover the data? I'm traveling and forgot to back anything up. Some of the data is quite important. And do you think I'll get into trouble because of the root?
No clue, try a different charger maybe.
I tried three different charges plus my laptop. Neither of them worked. Is there gonna be any way to rescue the data from the internal storage or will the just wipe it after they repaired it?
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
Hold power + volume up button will work in most cases.
TBH, don't really know what happened to you. Did you flash custom rom, recovery? or only root?
I didn't know that. I only new power + vol down. And I didn't hold it for a minute. I did nothing but flashing TWRP and root the stock rom. I didn't even change much with the root and only use it for titanium backup and adaway. That's why I was so baffled, when the phone suddenly "broke" because I didn't do anything unusual to it.
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
I'm glad you got your phone up and running. I know exactly how you feel, I had the same thing happen to me. I thought mine died when the screen went black after I flashed a kernel. Its always scary when the phone won't respond.
The phone was likely frozen. Power + Volume Up forces the phone to reboot after being held for a while. It could be some weird software issue due to the rooting and TWRP, but no one can say for sure. It might happen again but now you know how to reboot it If you really want to avoid the possibility of problems, you probably want to run stock and not root the phone or change bootloader... but what's the fun in that?
You're right no risk no fun. I'm actually waiting for cm so running stock is no option anyway
Thanks for saving me lots of headaches
FYI - I thought I had bricked mine as well - no flashing activity in a couple of weeks, all good chargers. Even made an appointment for repair.
Read the "hold power and vol up for a minute or two," and was like... nooooo... 10 seconds is the max you'd do that for... but tried it... bam, worked like a charm at ~45 seconds for me. Got into HTC FTM mode in which no option worked (reboot to bootloader, simlock, couple of others seemed to just pop immediately back to this weird non-download menu). Holding power for a while after that reset the device. Working now.
Thanks for the thread... been doing this for five years and this is the first no-charge no-response event I've had
lyall29 said:
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Click to expand...
Click to collapse
Worked like a champ, thanks a ton! :good:
Hi All,
About a week ago my M9 powered down while on charge and then wouldn't power on again. No response at all from the standard power button but only holding it for a few seconds at a time.
I knew the buttons to hold to enter bootloader and after several tries it powered on again.... It then ran for a couple of days with no issues.
Then a couple of days later had to power off the phone on a flight - same issue - wouldn't power on - dead.
It took several attempts to bring it back to life. I'm now in a position when every time I power off the phone it just doesn't want to come back on? Thought that it may have been a custom rom issue or a kernel issue - have tried changing both (painful experience by the way - having to wait for the phone to decide when its ready to wake up "when it feels like it after each new installation) but the problem is still there.
I have also found that entering bootloader using the power button and volume button isn't the only solution to "waking up" the phone. Just holding the power button for 10-60 seconds has the same effect - but it sometimes takes several attempts over several minutes - its very random.
Does anyone else have this recurring problem every time they power off? Does anyone on "stock" have the problem?
I'm starting to think that maybe its hardware rather than a software issue?
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Bricked M9
iElvis said:
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Click to expand...
Click to collapse
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
sausje85 said:
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
Click to expand...
Click to collapse
I am unaware of any way to do this if the phone wont turn on - it's dead.
aairlinepilot said:
I am unaware of any way to do this if the phone wont turn on - it's dead.
Click to expand...
Click to collapse
Ah you cannot even get it charged anymore?
I know HTC phones had an issue that when they are completely drained, they seem to be dead, even not charging or anything. Yet if you keep them in the charger, eventually they would show as charging and being able to turn on again.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Leave it in connected to the stock charger overnight and see if that helps. If not, you might have a hardware fault and need to return it for warranty service.
I too thank you most profusely!!
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
2x4 said:
i had this happen to my SO's stock/locked/unrooted Nexus 6P.
Plug it into a PC, wait a couple minutes, then press and hold the power button for like 1-2 minutes.
Click to expand...
Click to collapse
What is this supposed to do? Where did you hear about this solution? Just curious.
jgr208 said:
Today I was surfing the web and the phone locked up and restarted itself. Kept getting to the android screen with the red yellow and blue symbols then restarting. Left the phone alone to get back to work then the phone restarted finally went to use the phone and after about 3 mins froze up again. Now the phone won't get past the Google boot screen and if I want to try and power the phone on the power button has to be pressed in about 30secs to a minute of two.
Also i can't get into recovery mode reliably since if I select recovery the phone again freezes at the Google screen on reboot and never gets to recovery 9 out of 10 times other times I can get to recovery and then phone will then crash while in recovery or will allow me to use recovery long enough to wipe the cache and factory reset which neither has worked.
While Plugged into a charger and just sits there nothing on screen just a black screen.
Phone is on latest android unrooted and locked.
Click to expand...
Click to collapse
do RMA
PiousInquisitor said:
What is this supposed to do? Where did you hear about this solution? Just curious.
Click to expand...
Click to collapse
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
2x4 said:
read it on the nexus help forums i think. I was about to RMA the phone, so I'm glad i didn't have to. give it a try
Click to expand...
Click to collapse
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
PiousInquisitor said:
I don't have any issues. I was just curious. I've just never heard of a fix for any phone that requires a button press for more that like 30 seconds.
So what is the expected outcome? Does the phone just reboot and simply function correctly? Do you have a link to the forum post you read this in?
Click to expand...
Click to collapse
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
deanb1234 said:
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
Click to expand...
Click to collapse
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
2x4 said:
Sure.
Here is where I read about plugging it into a PC and then pressing the power button:
https://support.google.com/nexus/troubleshooter/3337561?hl=en#ts=3337942,3339328
That didn't work (15 seconds hold). Then I found this random post on XDA where someone said they held it for more than a minute, so i tried that.
not sure why this worked, but it did. probably held it for 45s to 1m and it booted normally after that. honestly not sure what happened or why this worked.
Click to expand...
Click to collapse
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
haha dang, i hope the Nexus 6P it helped me boot doesn't have this issue any more...
Apayah said:
do RMA
Click to expand...
Click to collapse
Already did. Trying any last ditch efforts to revive the phone oh well it was a good phone.
deanb1234 said:
I'm glad my old post helped! Just an update though, it did that a few more times and then eventually I had to have it RMA'ed as no amount of time would make it boot.
Click to expand...
Click to collapse
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
jgr208 said:
Yup same here. It can get to the boot menu but recovery only works 1/10 times and can't ever get through 54% of the boot log until it freezes and crashes.
Click to expand...
Click to collapse
Sounds like its time to RMA that bugger. Bummer.
PiousInquisitor said:
Sounds like its time to RMA that bugger. Bummer.
Click to expand...
Click to collapse
Yup new one is getting here today. Anyways, before old one is sent off I am curious to see if the battery is even charging when I connect to the charger. Anyone know if I can use a multi-meter to check this?
I have a Nokia 6.1 TA-1043. I have not unlocked the bootloader, and it runs the default operating system (Android One, probably Nokia flavoured). It has gotten slower over the years, and it had a period where it crashed every now and then (sudden reboot). Anyway , some days ago I decided to reboot the phone because it was slow, and it instantly shut off. After waiting probably 20 seconds without response, I decided to hold the power button down to force it. I don't remember exactly what I did, but after trying to again hold the button down to turn it on again, it vibrated as usual but the screen remained black. I then most likely tried holding volume + and power to force another reboot, unsuccessfully. I then tried holding volume - and power to enter download mode. It might have vibrated, or I might have touched the cable making me think it vibrated, but nothing happened. I pressed some random buttons after I think.
Now, the phone does seem to charge. It gets warm when I plug in the charger. I've searched for hours on different forums, and some people say that their phone was magically resurrected after the battery went completely flat after few days. I have tried plugging the phone a bit and testing every button combination (including volume +, volume - and power at the same time) for a few days now. It's dead.
The phone is also seemingly not recognised at all on my windows 10 PC. Haven't tried on Linux.
I have a few theories:
1. The phone simply hard bricked itself due to some hardware failure.
2. I bricked the phone by (blindly due to screen being blank) entering recovery mode and unknowingly factory resetting the phone and shutting it off mid process.
3. The battery is messed up? Some suggest deconnecting the battery. It would require the use of a heat gun to even open the phone though.
I've seen some people suggest entering EDL-mode either by shorting some pins or using a modified USB-cable. However, that would either require opening a phone that isn't supposed to be opened easily, or plugging a modified USB-cable into my computer, nether of which seem safe. I've also seen people mention that whatever needs to be flashed in EDL-mode must be signed by Nokia, which I can't do obviously haha.
It's probably time to move on right? Has someone managed to get a phone in that state to work again?
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
alprtewwqfr said:
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
Click to expand...
Click to collapse
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situation?
speedrocket2110 said:
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situations
Click to expand...
Click to collapse
I don't know because I'm not in that situation, but I had a similar one but only boot to download mode.