Database Info

[Q] Help!! Phone dont boot up

Ok, here's the problem.... I am flashing the rom of "hellmonger rc2" at the middle of flashing my suddenly got battery empty.....after that i charged it for a hour and i notice that only the buttons has light....there's nothing in the screen even i pressed the lock button....i removed the battery....then while pressing "power button + volume up" nothing come's up.....i also tried the bootloader option....its also not working....i tried my best!
Please understand this......sorry for my bad english

Buy one of this:
http://www.dealextreme.com/p/univer...r-moto-droid-milestone-us-plug-100-240v-43097
I had same problem with battery. After going below 5% it got into something like "charge loop", so I asked my friend to lend me his universal charger and then I bought the one I linked you, just in any case if that happen again.

archer88 said:
Ok, here's the problem.... I am flashing the rom of "hellmonger rc2" at the middle of flashing my suddenly got battery empty.....after that i charged it for a hour and i notice that only the buttons has light....there's nothing in the screen even i pressed the lock button....i removed the battery....then while pressing "power button + volume up" nothing come's up.....i also tried the bootloader option....its also not working....i tried my best!
Please understand this......sorry for my bad english
Click to expand...
Click to collapse
try just leaving the phone in the wall charger, should be good enoght to load the bootloader after one hour.

hellmonger said:
try just leaving the phone in the wall charger, should be good enoght to load the bootloader after one hour.
Click to expand...
Click to collapse
When the phone goes full-retard mode*, it charges and then auto-boots and drains faster than it charges. It's the damnedest thing when it happens. You can't keep it from booting when it's decided it wants to so you have to sit there and yank the battery every time it starts trying to boot.
*Motorola has a patent pending on full-retard mode. Google needs it to fend off Apple.

Mioze7Ae said:
When the phone goes full-retard mode*, it charges and then auto-boots and drains faster than it charges. It's the damnedest thing when it happens. You can't keep it from booting when it's decided it wants to so you have to sit there and yank the battery every time it starts trying to boot.
*Motorola has a patent pending on full-retard mode. Google needs it to fend off Apple.
Click to expand...
Click to collapse
LOL OMFG thats a good one man

um, youd prolly be better off just charging it up, booting into bootloader and reflashing the sbf appropriate for you

I already did that....its just showing a kid peeing on the motorola logo then bootloop again...

Had s similar problem (blackscreen while usage, then stuck on bootloop even after flashing stock SFBs) .. i fixed it by doing .. nothing. Just leaving the battery out of the phone a few days (one night was not enough!)

Ok! I got into the bootloader! But it said "battery low cannot program' but i charged almost 8 hours! With the buttons with light everytime i plug in the wall charger!

archer88 said:
Ok! I got into the bootloader! But it said "battery low cannot program' but i charged almost 8 hours! With the buttons with light everytime i plug in the wall charger!
Click to expand...
Click to collapse
u have really activated the retard mode*, meaning the phone will boot up while charging and the bootloop is sucking the battery dry.
2 Solutions: Pull the battery, everytime the phone boots. I did that for 1-2 hours and it was not enough ....
2nd solution: buy an external battery charger

archer88 said:
Ok! I got into the bootloader! But it said "battery low cannot program' but i charged almost 8 hours! With the buttons with light everytime i plug in the wall charger!
Click to expand...
Click to collapse
If you can get it to the point of Calvin Pissing and then boot loop, then the problem could be just that you need to Wipe Dalvik and cache partions and reset.
But I see now the problem is that you don't have enough juice. Try turning the phone off completely and then pull battery for a 15 mins or so. Then put battery in and plug in but do not turn it on. A battery icon will appear with charge amount. See it if goes up or down after about an hour. Think that if you can get it to 30-40% it should be enough to boot up and then wipe.
50% is the usual base amount for sbf flashing though, so might want to wait for that. If you haven't already flashed the SBF and have a working ROM in there already, stay on it and try the above. Would hate for you to wipe everything, including OR and Root, if it is only a charge issue and not the ROM itself. Check cords and plugs too.

thanks mate!! but im here in SAUDI ARABIA i have different card (

I've never had to resort to this yet, but:
http://forum.xda-developers.com/showthread.php?t=892026
This phone is just really, really, unbelievably stupid sometimes. If it thinks it's supposed to boot with minimal power, the only way to stop it is to do a proper shutdown (requires you boot successfully first or get into adb and run "reboot -p") or yank and replace the battery--that usually gives you about 15min before it will try to boot again. I used to just constantly wait and yank the battery whenever it started to boot. I got tired of that and got a second battery and wall charger pretty cheap online ($5 total, genuine Motorola). The bottom four leds on with a black screen is a tell-tale sign of full-retard mode.

are there any solutions? i cant do this myself ..... but thanks man for your help!

Mioze7Ae said:
I've never had to resort to this yet, but:
http://forum.xda-developers.com/showthread.php?t=892026
This phone is just really, really, unbelievably stupid sometimes. If it thinks it's supposed to boot with minimal power, the only way to stop it is to do a proper shutdown (requires you boot successfully first or get into adb and run "reboot -p") or yank and replace the battery--that usually gives you about 15min before it will try to boot again. I used to just constantly wait and yank the battery whenever it started to boot. I got tired of that and got a second battery and wall charger pretty cheap online ($5 total, genuine Motorola). The bottom four leds on with a black screen is a tell-tale sign of full-retard mode.
Click to expand...
Click to collapse
I did this once
It work fine
You just connect 2 of the 4 wire in an usb cable (you have to sacrifice a cable)
I gonna search a little more you have better pics with a droid i think
but you have to remove the battery. i don t know if you have too but it s less dangerous (the battery can t explode) and it s much more easy to connect the wires

I did this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You just connect the red to the + and the black to the - You do your Macgiver so that don t move (i use scotchtape but you can see he is using wire...)
Really easy (more than it s look like)
I just don t touch the phone during the whole flash progress
But i read that you can charge the battery directly by connecting the wire on it (the same red + black -) you charge it during 30minutes and you have enough to flash
You can see it in the pic in the bottom left
But I don t test this trick i recommend to use the first one...

archer88 said:
are there any solutions? i cant do this myself ..... but thanks man for your help!
Click to expand...
Click to collapse
And do worry it can be scarry but you can make it (Ok really really scarry but it would be fine...)
I did it with out a problem and i never do any electronic stuff or anything like this
Just take your time to stick the wire and let it like this don t try to return it (anyway you will see in rsdlite if it boot or not)

i did it man! i did it! thank you very much! you are an expert! i followed your instructions and it worked! thank you very much!

archer88 said:
i did it man! i did it! thank you very much! you are an expert! i followed your instructions and it worked! thank you very much!
Click to expand...
Click to collapse
Happy to help !
And how do you do??? My method or the charging battery method?
And what do you use to stick the wire scotchtape or something else?

[Q] How to debug Infuse restarting randomly?

Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.

It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium

psal217050 said:
It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hmmm, the power button seems to work alright. But if the power button is always pressed, I shouldn't be able to press it again and make it function properly, right? All the functions of the power button seem to be doing OK, i.e. menus pop up and it puts the phone to sleep mode, etc.
Is there anything more I can check to confirm that it is not the power button?

Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern

mccloud35 said:
Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern
Click to expand...
Click to collapse
Try to get a logcat using aLogcat from the marketplace.

mccloud35 said:
Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.
Click to expand...
Click to collapse
I have the exact same problem. Please let me know what you and people come up with.
Battery drops at least 4 or 5% after those random reboots.
I put liquid smooth JB on the infuse and was able to reduce the reboots to maybe 1 or 2 a day but the battery drain is still insane. from full to empty in 7 hours (but the battery usage says 17hrs, so please dont be confused, its really only 7hrs), texting, checking emails but nothing else. no music, or gps or anything that it intense.
The battery usage shows a constant battery drain, everything is at either 5 or 10% usage, except the screen which is at 42 - 60%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?

I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??

mccloud35 said:
I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??
Click to expand...
Click to collapse
I ordered a new battery and hope that this will fix the problem, if anyone knows anything else please let me know. the battery is only 1 year old.

I had similar symptom (reboot followed by battery indicating lower) once when I had applied too much undervoltage applied.

I've had the same things happen with my phone.
1) the huge drops in battery isn't an actual drop. 99% of the time if you don't plug in a charger the battery will start 'charging' on it's own until it gets to the right amount.
2) just because the power button works doesn't mean there isn't something wrong. The infuse is notorious for messed up power buttons. There is a thread around here somewhere about fixing it. I've not done it because I managed to get things under control.
3) I've noticed that the reboots seem to occur more frequently when a large number of apps ( popular or not) are installed, or apps that are resource intensive. For instance I bought minecraft because my daughter has become adducted to it. Sometimes its fine other times it freezes and reboots. My solution is to only keep apps I use on my phone. I will most likely uninstall minecract until a later date.
4) For me smaller ROMs work better. The current slimrom works the best for me. Also finding time to remember to reboot my phone once a day no matter how it is running helps.
I'm down to a reboot every one or two days now. Unless I try to play minecraft. I blame those damn creepers. Good luck!
Sent from my SGH-I997 using xda app-developers app

OK so my reboots were because of my power button, I sent it in to mobiletech and they repaired it.
Now it's fixed and I have not had a single reboot.
Sent from my SGH-T999 using xda premium

Glad to hear that. Thanks for sharing your results.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

[Q] What could be my issue?

A week ago Tuesday, my TF101 (B40) and dock (B90) were working fine. I charged them up and then put them in a carry bag for a weekend trip (still docked). I never used it on the trip or the following week. This morning I tried to power it on and it wouldn't; I figured it was a dead battery. Still docked, I plugged it in and the light was solid red on the dock (not blinking red which it usually does when depleted). After over an hour, I still cannot power on my tablet. I now have the tablet plugged directly into the wall, no dock, but I thought I'd post to get some ideas in case that doesn't revive it. If it was all the way dead, how long would it likely take to charge enough to come on? Is there a way to see if there's something else? Unfortunately for me, I have some data on it that isn't on the microSD; is there any way to even get in a state to copy the files off as a USB drive or something?
It's unrooted, stock Honeycomb (I never upgraded because I use Flash in the stock browser for Amazon Prime).

Gig103 said:
A week ago Tuesday, my TF101 (B40) and dock (B90) were working fine. I charged them up and then put them in a carry bag for a weekend trip (still docked). I never used it on the trip or the following week. This morning I tried to power it on and it wouldn't; I figured it was a dead battery. Still docked, I plugged it in and the light was solid red on the dock (not blinking red which it usually does when depleted). After over an hour, I still cannot power on my tablet. I now have the tablet plugged directly into the wall, no dock, but I thought I'd post to get some ideas in case that doesn't revive it. If it was all the way dead, how long would it likely take to charge enough to come on? Is there a way to see if there's something else? Unfortunately for me, I have some data on it that isn't on the microSD; is there any way to even get in a state to copy the files off as a USB drive or something?
It's unrooted, stock Honeycomb (I never upgraded because I use Flash in the stock browser for Amazon Prime).
Click to expand...
Click to collapse
Have you tried holding the power button for like 10 seconds, it could have just locked up holding it does a reset a bit like taking the battery out and putting it back in.
Also I believe in between the headphone jack and the HDMI there is a little hole, might be worth having a Google but I think that is another reset type button.
Even if the batt is completely dead it only needs to be plugged in for 5 secs for your to be able to switch it on with the power still in.

So it's been an hour and a half and it still won't power on, even holding it down for 30 seconds, and also doing a Volume Down + Power for 30 seconds. I'm trying to get a full charge on the dock now to make sure it isn't my charger or cable, and then I am hoping that re-docking will supply enough power to bring it on.
Edit: The dock now has a full charge, indicated with a green LED. The tablet is docked in and won't power up.

Gig103 said:
So it's been an hour and a half and it still won't power on, even holding it down for 30 seconds, and also doing a Volume Down + Power for 30 seconds. I'm trying to get a full charge on the dock now to make sure it isn't my charger or cable, and then I am hoping that re-docking will supply enough power to bring it on.
Edit: The dock now has a full charge, indicated with a green LED. The tablet is docked in and won't power up.
Click to expand...
Click to collapse
Actually, it might be working..
Try plugging it into a TV or another screen via HDMI cable..
I had a similar problem with mine, where I thought it was a power thing but infact it was a dead touch screen..
I actually did a complete flash back to stock via this method and sent it back for repair.
Lucky for me it still had the little sticker on the bottom of it and they replaced free of charge..
Sent from my Transformer TF101 using Tapatalk 2

dgcruzing said:
Actually,
Try plugging it into a TV or another screen via HDMI cable..
thought it was a power thing but infact it was a dead touch screen..
Click to expand...
Click to collapse
^^ This.
Otherwise I would completely kill the battery on the tablet, then try to recharge it via dock or direct cable, you may want to hold the power button for 30+secs to attempt to get it working, and see if your computer will detect it in APX mode via cable.. (Power + Vol up, no image will show) Then try reflashing it.
ToD

Thanks for responses so far. It now is recognized by Windows and I was able to get my data off, thankfully. I can't find my HDMI cable but I will try that soon to confirm it as a display issue.
Is there any chance it got a corrupted load from something OTA (I was still on Android 3.x) and is stuck in APX mode? It is a stock device but I read that APX-mode doesn't show you anything on the screen (like Fastboot does on my phone).

Gig103 said:
Thanks for responses so far. It now is recognized by Windows and I was able to get my data off, thankfully. I can't find my HDMI cable but I will try that soon to confirm it as a display issue.
Is there any chance it got a corrupted load from something OTA (I was still on Android 3.x) and is stuck in APX mode? It is a stock device but I read that APX-mode doesn't show you anything on the screen (like Fastboot does on my phone).
Click to expand...
Click to collapse
If its recognized by windows normally its not stuck in apx mode (windows detects "apx" mode, and you cant openly transfer files in apx) im assuming your not covered by warranty, you could pull it apart (easy to do) and see if anythings out of place, e.g loose connections, possibly even the battery connection but top priority is getting a hdmi connection going to see if its just the display or more.

there is a good youtube video that i used to confirm that i had touchscreen death.
its a tear down video and shows how to push the touch connector back into position as this seems to slide off
on a few devices, thus you lose touch screen.. check the q&a thread as i have posted a link to the video a few months ago..
Sent from my Transformer TF101 using Tapatalk 2

^^ This, they are well known for pulling their own display cable out of place when they receive a knock, the ribbon cable is wrapped around the battery so when you knock it, the battery shifts and pulls the ribbon cable out of its socket, fairly easy fix once you get the back off and find the cable
Full teardown video here
https://www.youtube.com/watch?v=k-6dKsGJ4VY
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks to everyone who responded! I confirmed via HDMI that the tablet is working and the touch interface is active. I'll tear it down this weekend and put that cable back in!

So I'm bumping my old thread, because despite my good intentions in March I didn't try to open it up until a few weeks ago, and then the cable looked properly seated. I still disconnected and reconnected it to make sure and the tablet display still doesn't work.
Is there a chance I did something wrong or could it just be a bad display or other circuit board? I checked and via HDMI the touch interface still works. I don't want to give up on it because a repair or even buying a different TF101 off eBay is cheaper than a TF700+new dock.

MOTO G won't charge.

Hey guys! So I was using my Moto G at about 55% charge when I locked the screen. Came back and found it turned off. I thought it was very strange as it couldn't have turned off due to the battery. But as I tried to turn it on again it showed no response. Plugged my Samsung charger in (5v-0.7A) and the battery icon came up with "0%" beneath it. So I let it charge. Checked about an hour late, it was still at 0%. Holding down the power button didn't work. Tried the VOL DOWN+POWER button combination too, didn't work. Nothing's working. This has been going on since the last 5 days. Today I plugged in the original charger and the LED light blinked a lot at first. Then the icon came up and then the screen turned off, and the LED light is constantly blinking like normal. This gives me a bit of hope. But the button combinations still do not work.
So, can anyone please help me out? I still haven't tried the freezer option. Will that work? Is it safe?
Also, this is my daily driver. I can't return this phone nor can I claim any warranty. I need this phone and will do everything to get it back to its old self.
Hope I can get it back to its working condition with the help of the amazing people here on xda
Thank you!

drag00n619 said:
Hey guys! So I was using my Moto G at about 55% charge when I locked the screen. Came back and found it turned off. I thought it was very strange as it couldn't have turned off due to the battery. But as I tried to turn it on again it showed no response. Plugged my Samsung charger in (5v-0.7A) and the battery icon came up with "0%" beneath it. So I let it charge. Checked about an hour late, it was still at 0%. Holding down the power button didn't work. Tried the VOL DOWN+POWER button combination too, didn't work. Nothing's working. This has been going on since the last 5 days. Today I plugged in the original charger and the LED light blinked a lot at first. Then the icon came up and then the screen turned off, and the LED light is constantly blinking like normal. This gives me a bit of hope. But the button combinations still do not work.
So, can anyone please help me out? I still haven't tried the freezer option. Will that work? Is it safe?
Also, this is my daily driver. I can't return this phone nor can I claim any warranty. I need this phone and will do everything to get it back to its old self.
Hope I can get it back to its working condition with the help of the amazing people here on xda
Thank you!
Click to expand...
Click to collapse
And some things I forgot to mention: The phone is totally stock, running KitKat 4.4.4. It's the XT1033. And the original charger's output rating is: 5V-500mA.

drag00n619 said:
And some things I forgot to mention: The phone is totally stock, running KitKat 4.4.4. It's the XT1033. And the original charger's output rating is: 5V-500mA.
Click to expand...
Click to collapse
It's a known battery bug, sometimes happens... I resolved using the Motorola AC/DC original charger, just leaving it connected for 2 hours then I long pressed the power button (for about 10-15 seconds) until I saw the battery icon. If this doesn't work you could try to open (carefully) your device with a screwdriver, unplug the battery (very easy, you will find a tutorial on YouTube), wait 5 min, plug it again and reassemble it.

oversleeper said:
It's a known battery bug, sometimes happens... I resolved using the Motorola AC/DC original charger, just leaving it connected for 2 hours then I long pressed the power button (for about 10-15 seconds) until I saw the battery icon. If this doesn't work you could try to open (carefully) your device with a screwdriver, unplug the battery (very easy, you will find a tutorial on YouTube), wait 5 min, plug it again and reassemble it.
Click to expand...
Click to collapse
Yea, its charging continuously since an hour now and the LED light is blinking. Will try what you just suggested and will give an update.

drag00n619 said:
Yea, its charging continuously since an hour now and the LED light is blinking. Will try what you just suggested and will give an update.
Click to expand...
Click to collapse
Is this cable the same you have used to charge before? Its weird but some cables will not charge my moto G, even tho I can charge other devices with them

I've been having this issue today as well.
I am Rooted, bootloader unlocked, and running custom ROMs. XT1031CDMA Boost Model
If I leave on charger it just keeps looping to the white 0% screen then vibrates and trys again, endlessly.
[even to the point of being dangerously hot]
one thing that finally worked for me was this.
I already found out if you hold Vol Down while plugging in , then releasing Vol Down, will quickly take you to fastboot screen [haven't seen this mentioned before]
So I would start with that and choose recovery, which would fail because there was not enough battery charge.
I found that if I unplugged the charger and plugged it back in before it vibrated it finally came up to the black screen with the colored 1% charging screen and now it is taking a charge again.
Which you can verify the charging percentage by pressing the Vol Down button
It took me several attempts to get this right, so just keep trying to unplug/plug during the time after you have chosen to boot to recovery from fastboot mode.
[[also there may have been a Vol Down button press needed too. I am trying to remember all the things and I was trying a lot of different combinations to get it to charge again, so please let me know if that ultimately does or does not work]]
.

3RAN7ON said:
Is this cable the same you have used to charge before? Its weird but some cables will not charge my moto G, even tho I can charge other devices with them
Click to expand...
Click to collapse
Using the Samsung charger, it just shows the 0% and the battery icon. But when I use the original Motorola charger, the white notification light starts blinking. Don't know how this happens. But the light gives me hope that the system is actually working and nothing is wrong with that. But why does the light blink only when I plug in the original charger?

hhp_211 said:
I've been having this issue today as well.
I am Rooted, bootloader unlocked, and running custom ROMs. XT1031CDMA Boost Model
If I leave on charger it just keeps looping to the white 0% screen then vibrates and trys again, endlessly.
[even to the point of being dangerously hot]
one thing that finally worked for me was this.
I already found out if you hold Vol Down while plugging in , then releasing Vol Down, will quickly take you to fastboot screen [haven't seen this mentioned before]
So I would start with that and choose recovery, which would fail because there was not enough battery charge.
I found that if I unplugged the charger and plugged it back in before it vibrated it finally came up to the black screen with the colored 1% charging screen and now it is taking a charge again.
Which you can verify the charging percentage by pressing the Vol Down button
It took me several attempts to get this right, so just keep trying to unplug/plug during the time after you have chosen to boot to recovery from fastboot mode.
[[also there may have been a Vol Down button press needed too. I am trying to remember all the things and I was trying a lot of different combinations to get it to charge again, so please let me know if that ultimately does or does not work]]
.
Click to expand...
Click to collapse
The thing is that as soon as I unplug, it turns off because there's absolutely no charge. The fastboot mode also shows "Battery Low".
So when I select recovery it immediately goes to the 0% battery icon screen. Still, I'll keep on trying your method.
What I am trying to figure out now, is that why both different chargers show different behaviour of the phone? Like, using the Samsung one, when I select recovery it goes to the battery icon and using thd original charger it goes to a black screen and the notification light starts blinking. Do you know anything about it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

drag00n619 said:
The thing is that as soon as I unplug, it turns off because there's absolutely no charge. The fastboot mode also shows "Battery Low".
So when I select recovery it immediately goes to the 0% battery icon screen. Still, I'll keep on trying your method.
What I am trying to figure out now, is that why both different chargers show different behaviour of the phone? Like, using the Samsung ons, when I select recovery it goes to the battery icon and using thd original charger it goes to a black screen answer the notification light starts blinking. Do you know anything about it?
Click to expand...
Click to collapse
I don't know a ton about it, just been battling with various stares of battery issues...
1st time I have had it no not accept a charge though...
""The thing is that as soon as I unplug, it turns off because there's absolutely no charge. The fastboot mode also shows "Battery Low".
So when I select recovery it immediately goes to the 0% battery icon screen.""
that is exactly what mine was doing...
don't you get a vibration in between when you select recovery and when the white 0% screen comes on?
.

hhp_211 said:
I don't know a ton about it, just been battling with various stares of battery issues...
1st time I have had it no not accept a charge though...
""The thing is that as soon as I unplug, it turns off because there's absolutely no charge. The fastboot mode also shows "Battery Low".
So when I select recovery it immediately goes to the 0% battery icon screen.""
that is exactly what mine was doing...
don't you get a vibration in between when you select recovery and when the white 0% screen comes on?
.
Click to expand...
Click to collapse
No, I don't get any vibration :/

Ok, can anyone tell me why my notification light blinks when I pkug in my original charger? It's definitely not charging so then what is it indicating?

drag00n619 said:
No, I don't get any vibration :/
Click to expand...
Click to collapse
I feel sure thats how I was doing it
plug charger into phone
VOL DOWN+POWER button combination for 2:00 + minutes
then release,
phone enters fastboot mode, shows "low Battery'
press 'vol down' to recovery
press 'vol'up' to proceed
wait for fastboot screen to turn off
quickly unplug charger and re-plug in charger
.
as far as I know it flashes the white led when it has shutdown because of low battery
I believe you have to perform the
VOL DOWN+POWER button combination for 2:00 + minutes
to get phone out of the 'state' it is on to be able to accept charging mode again
.

hhp_211 said:
I feel sure thats how I was doing it
plug charger into phone
VOL DOWN+POWER button combination for 2:00 + minutes
then release,
phone enters fastboot mode, shows "low Battery'
press 'vol down' to recovery
press 'vol'up' to proceed
wait for fastboot screen to turn off
quickly unplug charger and re-plug in charger
.
as far as I know it flashes the white led when it has shutdown because of low battery
I believe you have to perform the
VOL DOWN+POWER button combination for 2:00 + minutes
to get phone out of the 'state' it is on to be able to accept charging mode again
.
Click to expand...
Click to collapse
So, I tried it again.
Got to the fastboot mode but as soon as I select recovery, it goes back to the 0% screen. There's even no vibration. I only get time to turn the switch on and off directly from the wall.
But I'll keep on trying it and hopefully it will work.
Also, this is the system that is stopping the battery from getting charged, right?

drag00n619 said:
So, I tried it again.
Got to the fastboot mode but as soon as I select recovery, it goes back to the 0% screen. There's even no vibration. I only get time to turn the switch on and off directly from the wall.
But I'll keep on trying it and hopefully it will work.
Also, this is the system that is stopping the battery from getting charged, right?
Click to expand...
Click to collapse
I only get time to turn the switch on and off directly from the wall.
Click to expand...
Click to collapse
just unplug from bottom of device as quickly after you tap the vol up button, then plug right back in

The battery software bug on the G is well known over at Moto- although your case puts a new twist on it If you haven't already, check out the forums at their website. The Moto engineers, devs, and other employees regularly cruise those threads and even respond occasionally. Point being, because it is a well known issue, if you can't get some assistance, they will replace your device with their warranty exchange service. I had to do that with my first G and it took less than 48 hrs to get my new phone to me. free. YES it was a rooted and unlocked phone I was exchanging for a brand new device. Because we have to email Moto to get the unlock code, I has apprehensive that the customer service rep would know that mine was UL and tell me I'm SOL. But no, Moto is cool like that. They didn't ask any of those questions and I didn't volunteer the info! So when my new phone came, I UL that & restored a nandroid and have been good to go. That was like 5 months ago.
I tell you all this to say, cheer up my friend! there is light at the end of the tunnel. Talk to Moto.

hhp_211 said:
just unplug from bottom of device as quickly after you tap the vol up button, then plug right back in
Click to expand...
Click to collapse
Still nothing
One thing I did notice was that, using the original charger, when I select Recovery using the power button it shows a black screen for some time and then goes to the 0% screen. And if I select it with the Vol UP button, it immediately goes to the 0% screen.

3RAN7ON said:
The battery software bug on the G is well known over at Moto- although your case puts a new twist on it If you haven't already, check out the forums at their website. The Moto engineers, devs, and other employees regularly cruise those threads and even respond occasionally. Point being, because it is a well known issue, if you can't get some assistance, they will replace your device with their warranty exchange service. I had to do that with my first G and it took less than 48 hrs to get my new phone to me. free. YES it was a rooted and unlocked phone I was exchanging for a brand new device. Because we have to email Moto to get the unlock code, I has apprehensive that the customer service rep would know that mine was UL and tell me I'm SOL. But no, Moto is cool like that. They didn't ask any of those questions and I didn't volunteer the info! So when my new phone came, I UL that & restored a nandroid and have been good to go. That was like 5 months ago.
I tell you all this to say, cheer up my friend! there is light at the end of the tunnel. Talk to Moto.
Click to expand...
Click to collapse
Thank you! Yes, I hope too that they are able to replace it but there isn't any kind of customer service centre or any kind of official support in Pakistan by Moto.
But I did read once in a forum that Moto asked the guy to ship the phone to them and once they received it, they sent him a new one.
And they really should replace it since it's under warranty and it's a pretty common bug

drag00n619 said:
Thank you! Yes, I hope too that they are able to replace it but there isn't any kind of customer service centre or any kind of official support in Pakistan by Moto.
But I did read once in a forum that Moto asked the guy to ship the phone to them and once they received it, they sent him a new one.
And they really should replace it since it's under warranty and it's a pretty common bug
Click to expand...
Click to collapse
I didn't talk to anyone on the phone or go to a service center, I used the live chat with a representative feature on their website to initiate the return.
The way that it worked for me, is that after I notified them, they Fedex'd me the new device. They also included inside that shipment an envelope that had a new pre-paid Fedex shipping label on it. So all I had to do was put my old phone in that envelope and drop it off at fedex and it went back to Moto. It didn't cost me a penny

drag00n619 said:
Still nothing
One thing I did notice was that, using the original charger, when I select Recovery using the power button it shows a black screen for some time and then goes to the 0% screen. And if I select it with the Vol UP button, it immediately goes to the 0% screen.
Click to expand...
Click to collapse
Well maybe you will have some luck at some time.
I do know that when in fastboot that the vol up is the (select) or (enter) function.
Using the power button only tries to reboot.
---------- Post added at 10:34 PM ---------- Previous post was at 10:11 PM ----------
I would look at getting to the battery as mentioned earlier.
It takes either a t4 or t5 torx screwdriver and remove the about 10 screws and the cover so you can disconnect to battery.

3RAN7ON said:
I didn't talk to anyone on the phone or go to a service center, I used the live chat with a representative feature on their website to initiate the return.
The way that it worked for me, is that after I notified them, they Fedex'd me the new device. They also included inside that shipment an envelope that had a new pre-paid Fedex shipping label on it. So all I had to do was put my old phone in that envelope and drop it off at fedex and it went back to Moto. It didn't cost me a penny
Click to expand...
Click to collapse
Ok, so I did a live chat session and when they asked for my location, they said that this live chat is for support in the USA only. She redirected me to some forums. Went through the forums and everyone suggested the vol down+power button combination. Went to the Indian page where they just had a pdf of their customer service centers in India.
Long story short, no chance of replacement.
I am thinking about letting it sit without plugging in the charger for about 24 hours and then plugging in the original charger for 24 hours. Hopefully that should work.

5.1.1 Update / Phone shuts off automatically

Can someone please help me. After the 5.1.1 OTA update my phone randomly shuts off (like pulling the plug off an appliance). I already did the factory reset and it still has this problem.

I have the same problem, and the only way to switch it back on, is to plug it in the charger, wait for the battery icon to appear, and then try to switch it on.
It shut off twice while I was using the camera, and I thought it was caused by the HDR+ bug, but it also happened twice later, while idle in my pocket.
Anyone else seen this?
Android 5.1.1, stock, Rooted.
Sent using Tapatalk.

Same
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.

igimmi said:
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
Click to expand...
Click to collapse
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.

kted said:
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
Click to expand...
Click to collapse
Are you running 5.1.1?
I'm afraid to update my wife's Nexus 4 to 5.1.1.

Damn 5.1.1

I had no issues with 5.1.1, so you all probably should just flash factory images through fastboot.

I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.

kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
I wonder if we have to wait for an official bug fix from Android.

I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties

HEY!!!
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
igimmi said:
I wonder if we have to wait for an official bug fix from Android.
Click to expand...
Click to collapse
tesla45 said:
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
Click to expand...
Click to collapse
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.

beekay201 said:
HEY!!!
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
Click to expand...
Click to collapse
The thing is it started all of a sudden, a week ago...
Sent using Tapatalk.

I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.

GripR said:
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
Click to expand...
Click to collapse
Safe mode didn't work for me.

My problem is not the same, it seems.
It happens one in every two times I take a photo with HDR+.
The phone switches off instantly, and the only way to switch it on again, is to plug it into a charger.
Sent using Tapatalk.

Safe mode didn't work...

I have the same issue.
Started like a week ago while came back from M preview to cataclysm. Was very frustrating and made a clean install of stock, reboot continued, more accurately it seems like a reboot with the Google logo, and then it turns off.
Happens with and without xposed.
What I have noticed though is that it happens much much less when WiFi is off.

Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... ?)
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk

strainhunter said:
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... )
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
I also think it's the battery. I will be be changing the battery soon. if there is any improvements after that I will provide update.

So today, my phone kept dying when the battery was around 40%. So I said screw it and got the battery replaced.
The old battery (on the right) looked bloated compared to the new one. The battery could have been the cause of all our problems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}