I have following problems with my Nexus 5 16 GB (unlocked, not rooted and everything stock)
1. It keeps rebooting occasionally (more often than I would count as normal) without any apparent reason.
2. Whenever I receive OTA update it fails to complete showing "Error" on while updating.
3. Tried factory resetting several times to no avail all symptoms remain the same.
4. Could not go to recovery mode. It shows a red triangle with exclamation mark.
5. Flashed stock images from Google.
6. Worked fine for few days (seldom reboots, though) and could go to recovery mode.
7. Now recovery is again corrupted. Cannot go to recovery mode and it keeps rebooting every now and then.
I don't know if it is a hardware problem or software. I need to sell this phone but want to be fair so need to exactly what is the problem and what could be a possible solution to perspective buyer.
Thanks for long post. Any help is much appreciated.
shahidhussain said:
I have following problems with my Nexus 5 16 GB (unlocked, not rooted and everything stock)
1. It keeps rebooting occasionally (more often than I would count as normal) without any apparent reason.
2. Whenever I receive OTA update it fails to complete showing "Error" on while updating.
3. Tried factory resetting several times to no avail all symptoms remain the same.
4. Could not go to recovery mode. It shows a red triangle with exclamation mark.
5. Flashed stock images from Google.
6. Worked fine for few days (seldom reboots, though) and could go to recovery mode.
7. Now recovery is again corrupted. Cannot go to recovery mode and it keeps rebooting every now and then.
I don't know if it is a hardware problem or software. I need to sell this phone but want to be fair so need to exactly what is the problem and what could be a possible solution to perspective buyer.
Thanks for long post. Any help is much appreciated.
Click to expand...
Click to collapse
You only have one issue here which is rebooting. If you flashed stock without restoring data /installing apps and it still reboots, send it for repair.
Sent from my Nexus 5 using Tapatalk
rootSU said:
You only have one issue here which is rebooting. If you flashed stock without restoring data /installing apps and it still reboots, send it for repair.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I flashed everything stock (without keep any data/apps) and it still reboots. Initially I checked by entering into recovery mode and all was OK but now a red triangle. So it is a hardware problem
Thanks for your quick reply
Stock recovery always has that symbol
Sent from my Nexus 5 using Tapatalk
got the same problem since 4.4.3 came out, even got a replacement phone that does the same.. symptom a soft reboot, occasionally hard, every one or two days.
running 4.4 or 4.4.1/2 the problem disappears
only thing i found that helps is turning location on and having mobile settings to allow 3g.. i can go for up to a week like this before a reboot.. my personal settings of 2g only and location off makes it worse for some unknown reason.
I have a nexus 5 running android lollipop with franco kernel. I tried to switch off the device by clicking on the turn off button, but somehow the device randomly reboots. According to a few forums I should try and wipe cache which I did and still the phone refuses to work properly. I tried to factory reset my device but then the phone refused to boot into recovery and rebooted again. After sending ADB commands too it refused to boot into bootloader mode. The factory reset button on the device also was not able to wipe it. I am really worried since my nexus 5 just ran out of warranty a week ago. Is there any solution? I appreciate any help I could get.
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.
I am currently unable to boot my Nexus 5 running 5.1.1, I will try to explain in-detail:
Device: Nexus 5
Stock ROM and Stock recovery, Non rooted.
What happened:
1. Updated from 5.0 to 5.1.1 through OTA, phone ended up in continuous reboot
2. Visited customer care service and I was advised to replace mother board. Price of replacing motherboard is higher than the sale value of the device, hence chose not to.
3. Googled "How to solve bootloop issues on Nexus 5" and went through several articles
4. Decided to try and wipe cache
5. Rebooted to recovery, tried wiping cache partition
Error Faced: E:\ Unable to mount cache
6. Tried unlocking bootloader to flash TWRP and try wiping
After performing the command fastboot oem unlock the status is shown as Unlocked and after rebooting it sadly goes back to locked state.
7. Tried flashing cache.img from the latest source, didnt help as well
Used Nexus Root Tool Kit by wugfresh (I believe) and proceeded with the Stuck on bootloop option, but still the device was stuck in boot animation for over 2 hours and 15 mins..
Current State:
1. Device boots past the Google logo and remains in four dot boot animation forever.
Any help regarding how to fix this is appreciated. Thank you for all the help
I've seen another thread, probably in this forum, which says that if the bootloader relocks itself on reboot then it means that it's a fried chip, so it looks as if the advice to replace the motherboard is correct. Sorry...
Cheapest way to solve the issue would be to buy a used nexus 5 with a working motherboard and smashed screen. I did this for 4 nexus 5 phones.
Hello,
So here it how it goes:
My N5 freezes suddenly and shortly after it goes into a bootloop ( stuck at Google logo ). And from there on, the only thing I can do is just go into the bootloader.
If I go to recovery mode I can see that I get "msm_sdcc.1/by-name/misc no such directory" or something like that.
The only thing that helps make this issue dissapear is performing an oem unlock in fastboot mode, but this is not a good solution since this is the 2nd time it has happened to me in the past 3 months.
What do you guys suggest I should check/do to prevent this issue from ever happening?
Thanks!
Does the bootloader relock itself at reboot? If it does, the emmc chip is going or gone.
@audit13
The bootloader doesn't relock itself. It remains unlocked even after reboot.
I just unlock it to perform this "trick" that helps me get out of the bootloop. ( also after unlocking it, I perform a fastboot oem lock, done this both times ).
Also, don't know if it is related, when i go into recovery mode i get the android with an X or an ! (forgot which one) which is most probably due to files missing.
The screen with the dead android is normal. No need to relock the bootloader in my opinion.
Have your tried flashing a completely stock rom, including th userdata.img file to see if that solves the issue?
@audit13 Wanted to keep the stock rom with which it had come. Also doesn't an update ( from L to M for example) change the rom completely?
An ota update will move the phone to the latest of the current version (e.g. 5.0 to 5.01). The the ota will move from LP to mm.
Personally, I prefer mm.
So.. The phone did it again today, same behavior, same result ( bootloop out of nowhere ). This time I performed a complete new install of the OS ( wipe cache, factory reset + reflashed a factory image).
At this moment the phone is working as usual and now I will wait and see if the issue reoccurs (hope not).
If someone else has any other ideas an how to prevent or read some logs from the phone ( even if I performed an oem unlock ) please reply.