Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
cool1007 said:
Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
Click to expand...
Click to collapse
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the "Nexus 5 Battery Replacement howto" from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Necrosis
works for me too
elfarto said:
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Click to expand...
Click to collapse
i had some similar experience this morning, phone wont turn on, no charging notifications nothing, and i followed ur instructions and its works fine now, no idea how it happens, but when i open the back i got some burning smell too, anyway the device is working fine now!
anyways thanks
Related
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Sad for you, mine opinion is it might related to hardware issues. Hope some pros may come up and help you here.
Flash stock firmware from fastboot
ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Follow this guide and everything will be good
Tried flashing but nothing happens
I have tried flashing it too. When it fastboot mode, I see that all the processes are running as intended and once the flash is complete and my phone starts with Moto G, guess what - I see the same old wallpaper and lock screen. It means phone is not flashed .
amolgosavi said:
Flash stock firmware from fastboot
Click to expand...
Click to collapse
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Will trying flashing after 2 weeks of phone phones processes has stopped
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
robm123 said:
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Click to expand...
Click to collapse
Tried flashing and nothing happens again.
This is crazy!
I do not rely service centers anymore and I can flash myself.
Techies - please help.
ashu388866 said:
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
Click to expand...
Click to collapse
I'm similar situation. Only my daughter's Moto G (android 4.4.4) was not physically damaged.
After sreen unlocking the phone shows errors "Unfortanately [everything] has stopped working".
I flashed stock recovery many times but it does't help.
And one more thing: if the phone is connected to the PC it is possible to run fastboot commands, but the phone filesystem is not accesible.
Is this a hardware problem?
P.s. Sorry for my english
ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Flash the stock rom via fastboot dat could fix the problem:good:
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
OK so my mother dropped her phone in the toilet and it died basically. I left it to dry then tried it again. It came on but the battery said 0% and it powered back off. When I plugged it in the icon came up and said 99% but it wouldn't come on without being plugged in so I assume it fried the battery when it got wet with power in it. I tried to reset it by holding the buttons but then it got stuck in download mode and wouldn't start up anymore for some reason, so I tried installing TWRP which failed. I assume with no battery power the device is just losing power and causing it to fail. So basically now I'm stuck on a screen when I plug it in that just says it needs to be recovered.
I took it apart but managed to damage the screen (like an idiot) so I bought a new screen. Basically she didn't want to lose the pictures from the phone so I have a new battery ordered to try power the board and at least get the data from it if it has a charging problem before replacing the board. I'm hoping it's only the battery that's damaged but I doubt she'd be that lucky. If it does need a new board then I'll get her one but I was just hoping to at least get the data back if possible.
Anyway my whole point is since it's not starting up, if I flash TWRP the data is encrypted and inaccessible right? Is there even a way to use a HOME_CSC or something or is the data just done for?
EDIT: As far as I'm aware it was just on the latest stock ROM before doing anything.
Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])
Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.
Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway
Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...
Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.
CaptainFedora, did you solve the problem? I have the same issue...
Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.
Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.