In a nutsell: when I plug the charger in (wall), after a while red led starts blinking, after a longer while phone turns on all by itself and starts booting up, <CM loading animation>, homescreen shows up and pretty much immediately phone goes off. During the one second of homescreen battery status seems to be 0%. This is then repeated for as long as the phone is plugged in and between the attempts to boot up manages to recharge a miniscule amount of power.
Problem has it roots in when I dropped the phone, backcover came off and battery was displaced. After that, phone booted correctly and worked, but battery status was stuck at 51%, which I didn't notice until the phone forced a shutdown (I think this happened the safe/soft shutdown way).
phone: Sony Ericsson Xperia pro (MK16i)
rom: CM-based LegacyXperia
So, now I can do these things:
- the continuous rebooting loop while plugged in
- boot to CWM recovery
- sometimes (and if I plug it into USB port), I get the battery charing icon (standard CM one?) which is what is supposed to come instead of automatic boot up (?). Usually at first it shows two yellow bars, quickly changing to one blue bar. Red led stays on (does not blink), so everything looks ok... until after a while the phone again goes off. If left plugged in, boot loop commences soon.
The phone can barely keep itself on while in CWM recovery menu for a couple of minutes maybe. Full wipe is going to the be last resort because I don't know how I'm able to take backups with so limited uptime.
I have tried:
- wiping cache & dalvik cache, since I can get to CWM recovery.
- I've googled a lot about this and one left-field suggestion was that the power button may be stuck (that thread was about entirely different phone). I guess that would make sense because I did drop the phone.
- removing the battery and kept it removed for several minutes. Also tried the trick of plugging the phone in first and then installing the battery.
I'd say that your power button is stuck, you should try another ROM however.
I would try a different rom
wirelesscord said:
In a nutsell: when I plug the charger in (wall), after a while red led starts blinking, after a longer while phone turns on all by itself and starts booting up, <CM loading animation>, homescreen shows up and pretty much immediately phone goes off. During the one second of homescreen battery status seems to be 0%. This is then repeated for as long as the phone is plugged in and between the attempts to boot up manages to recharge a miniscule amount of power.
Problem has it roots in when I dropped the phone, backcover came off and battery was displaced. After that, phone booted correctly and worked, but battery status was stuck at 51%, which I didn't notice until the phone forced a shutdown (I think this happened the safe/soft shutdown way).
phone: Sony Ericsson Xperia pro (MK16i)
rom: CM-based LegacyXperia
So, now I can do these things:
- the continuous rebooting loop while plugged in
- boot to CWM recovery
- sometimes (and if I plug it into USB port), I get the battery loading icon which is what is supposed to come instead of automatic boot up (?). At first it shows two yellow bars, quickly changing to one blue bar. Red led stays on (does not blink), so everything looks ok... until after a while the phone again goes off. If left plugged in, boot loop commences soon.
The phone can barely keep itself on while in CWM recovery menu for a couple of minutes maybe. Full wipe is going to the be last resort because I don't know how I'm able to take backups with so limited uptime.
I have tried:
- wiping cache & dalvik cache, since I can get to CWM recovery.
- I've googled a lot about this and one left-field suggestion was that the power button may be stuck (that thread was about entirely different phone). I guess that would make sense because I did drop the phone.
- removing the battery and kept it removed for several minutes. Also tried the trick of plugging the phone in first and then installing the battery.
Click to expand...
Click to collapse
if you confirmed the power button not stuck, i would say either, the phone has some internal damage from being dropped, or the battery has been damaged.
of the 2, i would guess battery damage, but this is just my opinion.
Daniel120201 said:
I'd say that your power button is stuck, you should try another ROM however.
Click to expand...
Click to collapse
ArYaNsH said:
I would try a different rom
Click to expand...
Click to collapse
It's going to be a bit risky because like I said, even in CWM menu it has barely enough juice for a minute or two and USB port is going to give even less power :/ The rom itself is ok (CM11 + added support for these ancient models, because the official one dropped them).
bweN diorD said:
if you confirmed the power button not stuck, i would say either, the phone has some internal damage from being dropped, or the battery has been damaged.
of the 2, i would guess battery damage, but this is just my opinion.
Click to expand...
Click to collapse
The stuck button: at least the phone can be turned off by the button, also key tester in CWM recognizes it. I would also lean towards battery damage or at least some kind of a miscommunication between it and the phone which makes the phone think it is not empty when in reality it is.
About the dropping: after that it booted and worked correctly, because I specifically tested that sound, camera etc. still worked, I did not see anything weird other than the battery % being stuck and used it until the battery emptied.
I can manage to use fastboot at least. I don't know if this a related issue, but I can't seem to get it return any values for battery information.
fastboot devices shows the device, but e.g.
Code:
fastboot getvar all
all:
finished. total time: 0.001s
Output should be something like this: http://pastebin.com/4vv9g7Hg
Won't return anything for battery-status and battery-voltage either.
but these work:
Code:
fastboot getvar version
version: 0.3
finished. total time: 0.003s
fastboot getvar version-bootloader
version-bootloader: Sony Ericsson S1Boot Fastboot emulation CRH1099189_R9A029
finished. total time: 0.010s
fastboot getvar version-baseband
version-baseband: 1243-7775_4.1.B.0.587
finished. total time: 0.007s
And probably many others I didn't test. a) commands/variables not supported b) battery/something so messed up that won't return anything?
I found this script which is supposed to slowwwwly recharge the battery in fastboot mode:
http://lesterhein.com/how-to-charge-your-android-phone-battery-in-hboot/
but of course it won't return any battery-voltage value either and secondly, after it does this cycle a few times, the phone shuts off.
Problem solved for now: one of the battery connector pins was bent inside because of the drop, the middle one (googled example pic) so I never noticed it. I simply pulled it back and phone has now returned from the dead, charges properly and seems to hold the charge too.
That for sure explains everything.
Related
Hello,
I’ve got a One S (S4 version) that’s driving me crazy. Can you help me please?
I bought this phone second hand – hoping that I could fix it up and give it to my mum for her birthday. It looks immaculate, but it was sold because the previous owner couldn’t get it out of a boot loop.
When I received the phone, the first thing I did was to hook it up to the charger. As soon as the charger was connected, the charging LED came on, but then after about 5 seconds (without pressing the power button), the device turned its self on and begin rebooting at the “Quietly Brilliant” screen. It wasn’t the usual “Quietly Brilliant” screen though… There was a progress bar in the top right hand corner, indicating that it was trying to flash something. The progress bar went from 0-100% twice, then after a pause of about 20 seconds – it rebooted again. This process would repeat endlessly
After a lot of messing around, I managed to get into the bootloader. The status was “Tampered – Relocked”. At this point, I downloaded and flash the latest RUU (2.31). However, even though the RUU flashed successfully, it still boot loops. The only difference is that the “Quietly Brilliant” screen no longer has the progress bar in the top right corner (it’s just the normal boot screen now).
After this, I unlocked the bootloader via HTCDev and flashed CWM recovery. The flash was successful , but trying to access recovery also fails. It just sits on a screen with the “for development purposes only” warning for a few seconds, then reboots and follows the same boot loop sequence as before.
Does anyone know whether I’m wasting my time on the phone? At this point I’m very worried about flashing things, because I never know how much juice is left in the battery. If I hook up the charger, the charging LED does come on, but only for a matter of seconds. After 5-10 seconds, the charge LED goes out and the device automatically fires up into a boot loop. It’s impossible to power down the device when it’s connected to the charger. It will turn its self back on again! The best I can do is to leave the phone sat in the bootloader, but there is no indication that it’s charging (no LED).
:crying:
I've just read over my last message and I think the clue is in the way this thing turns on by its self when connected to power. I bet some water has got into the phone and caused a mess inside. I think it might be time to get the screwdrivers out.
Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance
Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger
Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.
http://i.imgur.com/3XYLngJ.png
kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?
Yes
Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.
I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now
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.
Hello
I'm having problem with my Nexus 5 .
It started when I wanted to replace the battery. I have been replacing it in another nexus 5, done it gently, with plastic tools. And that's what happened - constant boot loop. Only thing that appear are battery charging image and white Google text, restart and over and over... nothing more (android colorful text/logo) doesn't appear.
Firstly I've read that it might be a problem with a power button, that it's stuck inside and making these constant loops. I tried to gently make a taps and flicks on the phone but it wasn't helpful. I accessed motherboard, took it off and checked the button, it seemed fine. But I took it to a mobile service place, and they replaced the button. But that didn't help.
I can't power it on when it's not connected to the charger or PC. It doesn't even start looping when not connected via cable to anything. On the bootloader screen I can go up and down using volume keys, but when i try to access "Recovery menu" it turns off and start looping. Even trying to use "power off" option makes it loop.
So I flashed it using factory image from google: 6.0.1 (M4B30Z, Dec 2016) (hammerhead-m4b30z-factory-625c027b).
I did it manually, on bootloader screen, entering all these fastboot commands. one by one. Everything seemed fine, all flashed with success. Already was happy! But after rebooting, it's still bootlooping
I installed TWRP recovery img to it, (successfully), and tried to access recovery menu, but also started looping.
I don't know what to do anymore. I've read so many threads and I think everywhere problem disappeared after successful flashing. I tried also this method:
https://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 But after flashing to 4.4.4 firmware, it was bootlooping..
Since it doesn't even react to power button on both batteries, is there some bigger hardware problem with a motherboard? A battery connector socket on motherboard is broken or something?
krystian-92 said:
Hello
I'm having problem with my Nexus 5 .
It started when I wanted to replace the battery. I have been replacing it in another nexus 5, done it gently, with plastic tools. And that's what happened - constant boot loop. Only thing that appear are battery charging image and white Google text, restart and over and over... nothing more (android colorful text/logo) doesn't appear.
Firstly I've read that it might be a problem with a power button, that it's stuck inside and making these constant loops. I tried to gently make a taps and flicks on the phone but it wasn't helpful. I accessed motherboard, took it off and checked the button, it seemed fine. But I took it to a mobile service place, and they replaced the button. But that didn't help.
I can't power it on when it's not connected to the charger or PC. It doesn't even start looping when not connected via cable to anything. On the bootloader screen I can go up and down using volume keys, but when i try to access "Recovery menu" it turns off and start looping. Even trying to use "power off" option makes it loop.
So I flashed it using factory image from google: 6.0.1 (M4B30Z, Dec 2016) (hammerhead-m4b30z-factory-625c027b).
I did it manually, on bootloader screen, entering all these fastboot commands. one by one. Everything seemed fine, all flashed with success. Already was happy! But after rebooting, it's still bootlooping
I installed TWRP recovery img to it, (successfully), and tried to access recovery menu, but also started looping.
I don't know what to do anymore. I've read so many threads and I think everywhere problem disappeared after successful flashing. I tried also this method:
https://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 But after flashing to 4.4.4 firmware, it was bootlooping..
Since it doesn't even react to power button on both batteries, is there some bigger hardware problem with a motherboard? A battery connector socket on motherboard is broken or something?
Click to expand...
Click to collapse
Have you tried putting the original battery back in it? Does it not correctly only when plugged in to a charger cable? Idk how but it seems either something bad happened to your emmc or there's something not plugged in correctly to the motherboard and something may have happened to whatever piece(s) that is. I'd just take everything out and put it back together, I had to do that when I replaced my screen, it's a pain in the ass but it worked again. Hopefully I could help you, or even give u a clue as to what it is
Try flashing 4.4.2 or an older stock ROM.
Aurey24 said:
Have you tried putting the original battery back in it? Does it not correctly only when plugged in to a charger cable? Idk how but it seems either something bad happened to your emmc or there's something not plugged in correctly to the motherboard and something may have happened to whatever piece(s) that is. I'd just take everything out and put it back together, I had to do that when I replaced my screen, it's a pain in the ass but it worked again. Hopefully I could help you, or even give u a clue as to what it is
Click to expand...
Click to collapse
I did it now. On both batteries it doesn't even power on. Only on a cable plugged it it starts bootlooping, when disconnecting, it powers off.
I checked all the connectors and sockets on mainboard, especially the one connecting battery and they doesn't seem anyhow broken (but I'm not any tech specialist so..)
audit13 said:
Try flashing 4.4.2 or an older stock ROM.
Click to expand...
Click to collapse
I used now 4.4 (KRT16M). No result, still boot looping
Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates