Related
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Roach2010 said:
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Click to expand...
Click to collapse
My device had this issue, but with the 3/25(?) firmware (it came from overseas -- Taiwan). I basically thought I had a brick, but yesterday I used not-quite-pristine US system.img via a nandroid backup, and it brought it back to life. Still working, 18 hours later (and with the latest OTA update).
If you still have cwm / nandroid access, PM me and I'll post up the system.img that I used to fix my issue, yesterday. It was basically an image I found on Android Central, and I yaff2'd it and added my own md5sum so that nandroid could recognize it. My ongoing concern is that the permissions could be all screwy and softlinks could be broken. But, given the choice of that versus a bricked tablet, I could live with broken softlinks.
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Fisken said:
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Click to expand...
Click to collapse
Same here. Touchscreen stopped responding while playing that game, but that happened even before the OTA.
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
jonnyktyler said:
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
Click to expand...
Click to collapse
Hold the power button for 10-12 seconds to force power it off. Release button. Wait a couple seconds. Power on as normal (a 5-6 second hold down of the power button). If still no joy... you're screwed perhaps.
ok thanks a lot holding the power button down for a long time did force it to turn off, now it's working again.
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Narwhal73 said:
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Click to expand...
Click to collapse
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
echui2014 said:
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
Click to expand...
Click to collapse
Would that require unlocking my boot loader though? I don't want to void my warranty, especially considering I did nothing to the phone and it's currently unresponsive.
I am not sure - but my guess is that bootloader needs to be unlocked to install custom recovery to "recover" & backup userdata before flashing the entire original stock firmware; that's usually the first step we see in all those modding guide in different forums online.
How to get into safe mode
www[dot]youtube[dot]com/watch?v=NSHzoSEx8xY
** I am unable to post outside url yet.**
I suppose you can also contact motorola support to see if they can help you recover your data before getting the phone fixed or replaced under their warranty program.
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.