Database Info

[Q] Nexus 5 Firmware update problem

Hi all, I'm experiencing a problem with my nexus 5 at the moment.
I was using it until the battery got to 1%, then I turned off the screen and plugged it into the charger. But apparantly I was too late because the phone was turned off, so I turned it on.
After the google logo a firmware update screen appears. At the top it says Firmware Update, and below an USB-logo it says: "Do not unplug the USB connection until the progress is complete". Below that there's a progress bar, and below that there's a square/box with 'B1' in it.
I have no idea why my phone wants to update. I'm running 4.4.2 completely stock android, not rooted. No images of ROMs or stuff like that anywhere on my phone. It's still on 0%, and has been for the last 20 minutes. (at first I thought it might be waiting for a minimal battery charge to perform the update but you'd think it would be enough by now).
Does anyone know what this is or how to fix this?
I'll see if I can revive my old phone to make a picture of the screen

Roolio said:
Hi all, I'm experiencing a problem with my nexus 5 at the moment.
I was using it until the battery got to 1%, then I turned off the screen and plugged it into the charger. But apparantly I was too late because the phone was turned off, so I turned it on.
After the google logo a firmware update screen appears. At the top it says Firmware Update, and below an USB-logo it says: "Do not unplug the USB connection until the progress is complete". Below that there's a progress bar, and below that there's a square/box with 'B1' in it.
I have no idea why my phone wants to update. I'm running 4.4.2 completely stock android, not rooted. No images of ROMs or stuff like that anywhere on my phone. It's still on 0%, and has been for the last 20 minutes. (at first I thought it might be waiting for a minimal battery charge to perform the update but you'd think it would be enough by now).
Does anyone know what this is or how to fix this?
I'll see if I can revive my old phone to make a picture of the screen
Click to expand...
Click to collapse
The phone is plugged in the PC or the wall plug?

abaaaabbbb63 said:
The phone is plugged in the PC or the wall plug?
Click to expand...
Click to collapse
Wall plug.

Roolio said:
Wall plug.
Click to expand...
Click to collapse
Try restarting the phone. The low battery might have caused the update screen to appear. The wall plug is not a USB connection.

abaaaabbbb63 said:
Try restarting the phone. The low battery might have caused the update screen to appear. The wall plug is not a USB connection.
Click to expand...
Click to collapse
I'm scared to do it because that screen specifically says not to do it. But I don't think I have a choice in the matter, because it's still stuck on that screen. I'll be reporting back with good news I hope.

Ok what I did is keep the phone plugged in, and held the power button for 5-10 seconds. It rebooted normally, so I can use my phone again.
Thanks for you help!

Roolio said:
Ok what I did is keep the phone plugged in, and held the power button for 5-10 seconds. It rebooted normally, so I can use my phone again.
Thanks for you help!
Click to expand...
Click to collapse
Your phone went to download mode. It is used for flash firmwares with lg flashtool
Sent from my Nexus 5 using xda app-developers app

bitdomo said:
Your phone went to download mode. It is used for flash firmwares with lg flashtool
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I wonder why that happened though. Did I accidentally hold a button while powering on the phone? Or just a random glitch..

Roolio said:
I wonder why that happened though. Did I accidentally hold a button while powering on the phone? Or just a random glitch..
Click to expand...
Click to collapse
Haha yeah, same thing just happened to me. I has holding the power button to turn it on, but hit the up volume by accident too and it initiated the Firmware Update mode, just as you described.

right
Roolio said:
Ok what I did is keep the phone plugged in, and held the power button for 5-10 seconds. It rebooted normally, so I can use my phone again.
Thanks for you help!
Click to expand...
Click to collapse
i did the same way and it works
我是是长按电源+声音，然后就自动关机-开启，然后就正常进入系统了。

Reporting
Reporting same issue and 10 sec. power key pressing , solved the poblem.

errors
id upgrade to 4.4.4 dont go past it seems lilipop has alot bugs and up u update u have alot double apps installed even after formating the cache and data reset full firmware updates need to clean it up but even then still has probs just not as bad wish the updates would hurry

HolyHoundz said:
id upgrade to 4.4.4 dont go past it seems lilipop has alot bugs and up u update u have alot double apps installed even after formating the cache and data reset full firmware updates need to clean it up but even then still has probs just not as bad wish the updates would hurry
Click to expand...
Click to collapse
Why. Did. You. Post. Here.
This thread is a no-activity, year old thread.
I have no issues running Lollipop today.

scared
Roolio said:
I'm scared to do it because that screen specifically says not to do it. But I don't think I have a choice in the matter, because it's still stuck on that screen. I'll be reporting back with good news I hope.
Click to expand...
Click to collapse
I have done all that but it just gets stuck on the black background with Google on it.

My phone did the same thing, and it said keep connected to power so i unplugged it and then tried holding the power button but nothing happened. eventually my phone died again and now when i plug it in the little notification light is flashing red. what do i do?

The red flashing light is a dead battery. Recharge it.

Roolio said:
Ok what I did is keep the phone plugged in, and held the power button for 5-10 seconds. It rebooted normally, so I can use my phone again.
Thanks for you help!
Click to expand...
Click to collapse
this happens to my nexus 5x after downgrade from N to MM. thank you buddy

Roolio said:
Hi all, I'm experiencing a problem with my nexus 5 at the moment.
I was using it until the battery got to 1%, then I turned off the screen and plugged it into the charger. But apparantly I was too late because the phone was turned off, so I turned it on.
After the google logo a firmware update screen appears. At the top it says Firmware Update, and below an USB-logo it says: "Do not unplug the USB connection until the progress is complete". Below that there's a progress bar, and below that there's a square/box with 'B1' in it.
I have no idea why my phone wants to update. I'm running 4.4.2 completely stock android, not rooted. No images of ROMs or stuff like that anywhere on my phone. It's still on 0%, and has been for the last 20 minutes. (at first I thought it might be waiting for a minimal battery charge to perform the update but you'd think it would be enough by now).
Does anyone know what this is or how to fix this?
I'll see if I can revive my old phone to make a picture of the screen
Click to expand...
Click to collapse
if it was in update mode and it shut down you will have to flash the ota full firmware install to fix it remember to format all then format data again after install to clean it up then u should be good

The same issue with no clue so far!
Hi, I'm getting the same problem .
But it didn't work even after trying all the tips you all already mentioned in the comments. I don't know what to do ! Should I flash an ota again ? and about my data I have inside the current version ? any tips to restore them ?
Thanks

hi everyone i need your help i mistake firmware for my phone nexus x5 h791 it is 16 GB but i was flash to 32 GB after died

[Q] Scary Experience With HTC One M8

As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?

ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.

Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.

I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.

question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.

Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.

Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.

hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.

In my mind, this validates my decision to go over to the CM11 nightlies and never look back.

Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app

I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.

I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk

It isn't necessary to hold both volume keys, just volume up and power.

Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.

andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.

This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.

This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app

Sounds like SOD.

[Q] Nexus 5 constantly rebooting at 'Google'

Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
http://youtu.be/FEixpssggCY

What if you boot it pressing vol up + vol down + power?
Sent from my Nexus 5 using XDA Premium 4 mobile app

J.Diogo said:
What if you boot it pressing vol up + vol down + power?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If on battery, then the phone does nothing. If plugged in to charger and the key combination is tried then the phone keeps on doing as shown in the video.

Don't know what's going on.
Try doing that but with the phone connected to a PC that has adb and fastboot installed.
Sent from my Nexus 5 using XDA Premium 4 mobile app

I would leave the phone plugged in for an hour and don't touch it. Then try.
Trust me.

1ManWolfePack said:
I would leave the phone plugged in for an hour and don't touch it. Then try.
Trust me.
Click to expand...
Click to collapse
Tried that already. No change. Any other ideas?

steelbreeze said:
Tried that already. No change. Any other ideas?
Click to expand...
Click to collapse
You have a fauilty or a stucked power key.
If it is just stucked then you can unstuck it by abusing the power key or taking the phone apart.
If it is fauilty then you have to claim your warranty.
If you disassemble the phone you will void your warranty

bitdomo said:
You have a fauilty or a stucked power key.
If it is just stucked then you can unstuck it by abusing the power key or taking the phone apart.
If it is fauilty then you have to claim your warranty.
If you disassemble the phone you will void your warranty
Click to expand...
Click to collapse
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.

steelbreeze said:
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.
Click to expand...
Click to collapse
Then you have to visit that local repairer guy pay him to replace the power key again or pay LG to replace the mother board.

steelbreeze said:
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.
Click to expand...
Click to collapse
Yeah the repair guy you dealt with must have fixed the button short-term but in doing so inadvertently caused it to short out. Meaning it needs to go back to a repair shop (better one) and cross your fingers that it didn't short out more important components

bitdomo said:
Then you have to visit that local repairer guy pay him to replace the power key again or pay LG to replace the mother board.
Click to expand...
Click to collapse
kbroh said:
Yeah the repair guy you dealt with must have fixed the button short-term but in doing so inadvertently caused it to short out. Meaning it needs to go back to a repair shop (better one) and cross your fingers that it didn't short out more important components
Click to expand...
Click to collapse
Okie. Will take the phone to LG tomorrow or over the weekend.
Guys please clear my one doubt. If it's the stuck power button, what does it have to do with the phone not doing anything when on battery but decides to go till 'Google' when plugged in?

steelbreeze said:
Okie. Will take the phone to LG tomorrow or over the weekend.
Guys please clear my one doubt. If it's the stuck power button, what does it have to do with the phone not doing anything when on battery but decides to go till 'Google' when plugged in?
Click to expand...
Click to collapse
My phone behaves the same way if I constantly press the power button

steelbreeze said:
Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
Did you get it fixed? I have the same issue and I've tried many ways to bring it back to life. My last step will be taking it to the tech support, because I live in Brazil, and I'm pretty sure they will charge me expensively as hell.
Click to expand...
Click to collapse

hebert_hrs said:
steelbreeze said:
Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
Did you get it fixed? I have the same issue and I've tried many ways to bring it back to life. My last step will be taking it to the tech support, because I live in Brazil, and I'm pretty sure they will charge me expensively as hell.
Click to expand...
Click to collapse
I'm in the same boat, unfortuantely i'm at a loss in what to do, i'm going to send it back to Google and await a replacement, meanwhile i'll get my hands on some cheap old phone for now.
Click to expand...
Click to collapse

Had my Nexus 5 for about a few month now, and have loved it till this morning, it decided to just shut off (full battery too) and i tried to turn it on and it is now just constantly starting up to the "Google" splash screen then shutting off.
Sometimes it gets to the the 4 color circles then shuts off.
I want to enter into recovery mode, but I have no time to click recovery mode as it reboots frequently
One thing i noticed when it did boot up was the power button seems to be extremely sensitive and volatile

I had this same problem.. It constantly rebooted and wouldn't let me get into recovery.. Every time I plugged in the charger it would reboot also. You have to let the battery completely drain.. I gave it a couple weeks.. then tried it again and it worked.

Found a solution
Well same thing started to happening with me yesterday after installing android L's developers' preview in my nexus 5. It worked well for first 4-5 hours but then after terminating a phone call when I put it back to my pocket problem started. I searched many forums for solution then I decided to re-install from image. I connected my phone to My PC (Which had driver installed & fastBoot setup) dramatically my phone started working well. And I detached my phone from PC. So I thought it might solved because after supplying charging. But after 3-4 hours it started again so I directly plugged in to electric socket but it kept on rebooting. Then I turned on my PC and attached my nexus 5 with it. Again it started dramatically.
Still I don't know the exact reason behind it. But good new is my phone is still working since last 16 hours... But I took care of not to launch some apps listed risky for developer's preview. So I thing some incompatible app launch may be a reason... but still its only "may be"
---------- Post added at 05:46 AM ---------- Previous post was at 05:42 AM ----------
dueltothedeath said:
I had this same problem.. It constantly rebooted and wouldn't let me get into recovery.. Every time I plugged in the charger it would reboot also. You have to let the battery completely drain.. I gave it a couple weeks.. then tried it again and it worked.
Click to expand...
Click to collapse
If it happens again try what I just answered and let us know if it worked for you? So we can come to know if solution was nexus 5 specific or android L specific. Also mention the OS version, please.

hbb20 said:
Well same thing started to happening with me yesterday after installing android L's developers' preview in my nexus 5. It worked well for first 4-5 hours but then after terminating a phone call when I put it back to my pocket problem started. I searched many forums for solution then I decided to re-install from image. I connected my phone to My PC (Which had driver installed & fastBoot setup) dramatically my phone started working well. And I detached my phone from PC. So I thought it might solved because after supplying charging. But after 3-4 hours it started again so I directly plugged in to electric socket but it kept on rebooting. Then I turned on my PC and attached my nexus 5 with it. Again it started dramatically.
Still I don't know the exact reason behind it. But good new is my phone is still working since last 16 hours... But I took care of not to launch some apps listed risky for developer's preview. So I thing some incompatible app launch may be a reason... but still its only "may be"
---------- Post added at 05:46 AM ---------- Previous post was at 05:42 AM ----------
If it happens again try what I just answered and let us know if it worked for you? So we can come to know if solution was nexus 5 specific or android L specific. Also mention the OS version, please.
Click to expand...
Click to collapse
Thats very strange..since it started happening to me since yesterday. I managed to flash it again (and that i suppose should have cleared everything) but problem persists. Ill now try to restore factory image.

same thing happened with me one month ago............tried everything except opening it up and finally i got it replaced.................you cannot fix it on ur own take it to a service center asap........thank me if this helps!!

ironclad1911 said:
same thing happened with me one month ago............tried everything except opening it up and finally i got it replaced.................you cannot fix it on ur own take it to a service center asap........thank me if this helps!!
Click to expand...
Click to collapse
Thanks. I restored it to the original nexus 5 build - but nothing seems to fix the problem. will reach out to service center.

Phone does not power fully becuase it thinks it has no battery.

I have a Idol 3 6045, and the weirdest thing keeps happening. For some odd reason, whenever i try to turn it on, i get to the alcatel screen, then the phone thinks it has no battery and shuts off, when in fact, the battery is full.
I have tried the following to no avail:
reflashing via mobile upgrade q
draining the battery completely and then leaving it plug in over night to recharge
wiping cache via recovery
factory reset
Also, when the phone has some battery, and is plugged in, it goes into bootloop cycle where the phone turns on, goes to the battery symbol screen and then turns off, over and over again. I know the batter can hold a charge, so i am confused as to why the phone just turns off during the boot process thinking its dead.
Any ideas? btw, the phone is sadly bootlocked and does not have a custom recovery.

monbat said:
I have a Idol 3 6045, and the weirdest thing keeps happening. For some odd reason, whenever i try to turn it on, i get to the alcatel screen, then the phone thinks it has no battery and shuts off, when in fact, the battery is full.
I have tried the following to no avail:
reflashing via mobile upgrade q
draining the battery completely and then leaving it plug in over night to recharge
wiping cache via recovery
factory reset
Also, when the phone has some battery, and is plugged in, it goes into bootloop cycle where the phone turns on, goes to the battery symbol screen and then turns off, over and over again. I know the batter can hold a charge, so i am confused as to why the phone just turns off during the boot process thinking its dead.
Any ideas? btw, the phone is sadly bootlocked and does not have a custom recovery.[/
Bump, my sons phone is doing the exact same thing. I managed to take it apart and when I hold the battery connection it boots fine. I put some thick tape on it to maintain pressure and reassembled and it worked for a few days but is now doing the same thing again. Anyone else have any ideas?
Click to expand...
Click to collapse

monbat said:
I have a Idol 3 6045, and the weirdest thing keeps happening. For some odd reason, whenever i try to turn it on, i get to the alcatel screen, then the phone thinks it has no battery and shuts off, when in fact, the battery is full.
I have tried the following to no avail:
reflashing via mobile upgrade q
draining the battery completely and then leaving it plug in over night to recharge
wiping cache via recovery
factory reset
Also, when the phone has some battery, and is plugged in, it goes into bootloop cycle where the phone turns on, goes to the battery symbol screen and then turns off, over and over again. I know the batter can hold a charge, so i am confused as to why the phone just turns off during the boot process thinking its dead.
Any ideas? btw, the phone is sadly bootlocked and does not have a custom recovery.
Click to expand...
Click to collapse
Send it in to Alcatel http://alcatel.finetw.com Myself and another gentleman are having the same issue as can be read a few posts back. There is no home remedy and Alcatel repair is the only option I have found. Still awaiting my device to return.

joefloater said:
monbat said:
I have a Idol 3 6045, and the weirdest thing keeps happening. For some odd reason, whenever i try to turn it on, i get to the alcatel screen, then the phone thinks it has no battery and shuts off, when in fact, the battery is full.
I have tried the following to no avail:
reflashing via mobile upgrade q
draining the battery completely and then leaving it plug in over night to recharge
wiping cache via recovery
factory reset
Also, when the phone has some battery, and is plugged in, it goes into bootloop cycle where the phone turns on, goes to the battery symbol screen and then turns off, over and over again. I know the batter can hold a charge, so i am confused as to why the phone just turns off during the boot process thinking its dead.
Any ideas? btw, the phone is sadly bootlocked and does not have a custom recovery.[/
Bump, my sons phone is doing the exact same thing. I managed to take it apart and when I hold the battery connection it boots fine. I put some thick tape on it to maintain pressure and reassembled and it worked for a few days but is now doing the same thing again. Anyone else have any ideas?
Click to expand...
Click to collapse
Update: My device has been returned to me in full functional order. Alcatel was very good to deal with.
Click to expand...
Click to collapse

FlubbleWubble said:
joefloater said:
Update: My device has been returned to me in full functional order. Alcatel was very good to deal with.
Click to expand...
Click to collapse
Its been awhile since this post, but I've recently encountered this issue. May I ask how fast was the RMA process? How often does the finetw site update your RMA process once they receive your phone?
Click to expand...
Click to collapse

Try this
(You will erase everything)
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076

EcoVerse said:
FlubbleWubble said:
Its been awhile since this post, but I've recently encountered this issue. May I ask how fast was the RMA process? How often does the finetw site update your RMA process once they receive your phone?
Click to expand...
Click to collapse
I got the phone back in 7 days. Granted I live near their repair center
Click to expand...
Click to collapse

FlubbleWubble said:
EcoVerse said:
I got the phone back in 7 days. Granted I live near their repair center
Click to expand...
Click to collapse
Thank you for pointing out this site. I'm trying to get my idol 3 fixed too. I started filling out information, but i don't know what to choose for model. Can you help me out?
Click to expand...
Click to collapse

10st said:
FlubbleWubble said:
Thank you for pointing out this site. I'm trying to get my idol 3 fixed too. I started filling out information, but i don't know what to choose for model. Can you help me out?
Click to expand...
Click to collapse
Sure. The model you're looking for is OT6045i. I don't think it matters the variant OT6045i should cover them all (assuming you have the 5.5 inch Idol 3) For your date code just leave it blank. Go through those steps and print the RMA sheet they give you in the end. After printing I wrote the purchase date in the date code slot( probably doesn't matter) . Once you have your sheet just ship that RMA sheet with your phone to the address the give you. I believe it's in Richardson, Texas
Click to expand...
Click to collapse

Thank you so much. I Hope they will be able to fix it. Best of luck to OP too.

10st said:
Thank you so much. I Hope they will be able to fix it. Best of luck to OP too.
Click to expand...
Click to collapse
No problem brother. They were pretty decent to deal with. Best of luck to you. Also may I ask when you purchased your device? Me and another gentlemen believe that there's a ad batch of Idol 3's out there as three of us with the issue purchased them at about the same time.

FlubbleWubble said:
No problem brother. They were pretty decent to deal with. Best of luck to you. Also may I ask when you purchased your device? Me and another gentlemen believe that there's a ad batch of Idol 3's out there as three of us with the issue purchased them at about the same time.
Click to expand...
Click to collapse
I bought my phone used a month after the release. The original owner says he bought it in the month of June, and I bought it on July the 22th.

10st said:
FlubbleWubble said:
Thank you for pointing out this site. I'm trying to get my idol 3 fixed too. I started filling out information, but i don't know what to choose for model. Can you help me out?
Click to expand...
Click to collapse
10st said:
I bought my phone used a month after the release. The original owner says he bought it in the month of June, and I bought it on July the 22th.
Click to expand...
Click to collapse
Hmmm odd. That falls completely out of line of what I've observed. I made the observation that many of the devices with this issue were purchased in December 2015. Guess it's been an issue the lifespan of the phone
Click to expand...
Click to collapse

Pixel randomly shuts off. need to hold Power for 30 seconds to start. any fix?

My pixel randomly throughout the day turns off spontaneously and the only way to start​ it is to hold the power button for almost 30s. Anyone have this problem and know of a fix? It's really frustrating

I'm running RR with Franco but I tried this with purenexus and ElementalX and still had the same problem. It doesn't have to do with roms also I clean flash every time

Its done that to me twice in the 3 months

PunishedSnake said:
Its done that to me twice in the 3 months
Click to expand...
Click to collapse
Happens to me almost 2-3x a day

trizzv said:
Happens to me almost 2-3x a day
Click to expand...
Click to collapse
Ouch get a replacement

trizzv said:
Happens to me almost 2-3x a day
Click to expand...
Click to collapse
What does the battery stat show? The Nexus 6P has that issue right now where the device just shuts off and you have to hold the power button to start it, or plug it in and wait a few minutes before it will start. Some people have had this happen right when it comes off the charger. I've had it happen to 7 Nexus 6P...RMA!

trizzv said:
My pixel randomly throughout the day turns off spontaneously and the only way to start​ it is to hold the power button for almost 30s. Anyone have this problem and know of a fix? It's really frustrating
Click to expand...
Click to collapse
This is the first android phone I have ever owned that I haven't rooted and flashed.
I had this problem start with my first pixel and about 10 days later the device failed completely (would only boot to bootloader). Same thing happened with the replacement.
Third device seems to be working fine so far.

Did you ever try booting in safe mode to see if it happens. It very well could be a third party app causing the phone to crash and reboot. If it happens in safe mode it is probably an underlying hardware issue.

Jaggar345 said:
Did you ever try booting in safe mode to see if it happens. It very well could be a third party app causing the phone to crash and reboot. If it happens in safe mode it is probably an underlying hardware issue.
Click to expand...
Click to collapse
No but I will. How long should I keep it in safe mode?
I actually unrooted my phone (meaning didn't flash supersu) and haven't experienced it anymore....Idk if that's the issue tho will keep testing over the next few days before sending it back

Jammol said:
What does the battery stat show? The Nexus 6P has that issue right now where the device just shuts off and you have to hold the power button to start it, or plug it in and wait a few minutes before it will start. Some people have had this happen right when it comes off the charger. I've had it happen to 7 Nexus 6P...RMA!
Click to expand...
Click to collapse
Has a solution been found to this?

My pixel XL does this when I'm watching videos. Doesn't matter if it's using YouTube, Google photos, chrome, etc... It happens randomly and sometimes doesn't happen all day. But, the only time it happens is when a video is playing. And it happens in safe mode too. I bought the phone off eBay, no warranty and don't have money ATM to replace or repair it. I'm just sol I guess.