5.1 update issues - Nexus 5 Q&A, Help & Troubleshooting

I apologize if this issue has already been addressed but Im beyond frustrated.
Since my OTA update to 5.1, my phone is completely crippled. It randomly powers off about 10 times a day (not a auto restart) and I have to power back up. It will also auto restart another 5 to 7 times a day, when it does this it will get stuck in a loop of trying to boot into the OS and restarting all over again. So it will display "Google" for about 2 seconds and then restart again. This is only stopped by holding down the power button. The best part about this happening is that the phone then thinks its the first time I have powered on since the 5.1 update and will initialize all of my apps, which takes about 5 to 10 min. I have had 5.1 for about a week or so and its been getting worse every day. More power off's and restarts each day.
I should note that I am with T-Mobile and my phone is not rooted. Bone stock
My phone is borderline unusable since the update. Please god somebody help me.........

Flash 5.1 factory images

beekay201 said:
Flash 5.1 factory images
Click to expand...
Click to collapse
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
Download the 5.1 stock image here: https://developers.google.com/android/nexus/images#hammerhead
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.

matt4321 said:
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.
Click to expand...
Click to collapse
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??

dafababa said:
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??
Click to expand...
Click to collapse
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.

matt4321 said:
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.
Click to expand...
Click to collapse
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1

dafababa said:
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1
Click to expand...
Click to collapse
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
OTA update ain't the same as a factory image.

beekay201 said:
OTA update ain't the same as a factory image.
Click to expand...
Click to collapse
I've flashed back to 5.0.1 and still have the problems. I'm going to assume its a power button issue.

chaose said:
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.
Click to expand...
Click to collapse
So like how hard?

Related

[Q] Random Reboots Since 4.4.3

Anyone else?
Fully stock? Do a factory reset from stock recovery.. Should fix it. If you're on a custom rom, do a clean flash. (wiping everything except data)
- Sent from an IceCold Hammerhead!
Thx for the advice.
But was wondering if anyone else is getting them.
I'm trying a few things to fix it as I never had a reboot since I owned the phone in November last year, until 4.4.3
At the moment I'm trying an older radio, but it's hard to pin since my last try of using a 4.4.2 kernel kept me up for 35 hours before it happened again.
got an rma replacement.. still happening
meangreenie said:
got an rma replacement.. still happening
Click to expand...
Click to collapse
Did you restore a nandroid on it or anything?
rootSU said:
Did you restore a nandroid on it or anything?
Click to expand...
Click to collapse
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
meangreenie said:
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
Click to expand...
Click to collapse
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
vin4yak said:
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
Click to expand...
Click to collapse
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
meangreenie said:
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
Click to expand...
Click to collapse
Perform a factory reset and see if it sorts things out??
I'm assuming you're stock, unrooted??
still suffering from this
i have noticed that if location is not set to off, it's much better, where it can run for over a week at time
as soon as i turn location off, I'm lucky to get much over 30 hours before it soft reboots
going back to 4.4 it is completely stable as it always was

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.

Galaxy S7 restarts randomly!

Hey, XDA-ers!
I got the Android Nougat 7.0 update for my Samsung Galaxy S7 SM-G930FD (DUOS) back in January if I remember correctly. And the update process went like how it normally does. But ever since I got the Nougat update, my phone restarts randomly for no reason. At first it used to restart when I click on the 'Recent Apps' button to switch between apps. When I tap on the button, the phone vibrates and restarts. The phone never over heated before this happens. During this, the phone used to restart 2-3 times a day. This went on for 2 months. Then now, the number of restarts reduced to 1-2 per day, but the problem still persists. And now, it restarts even when I don't touch the 'Recent Apps' button. So, if any of you has had a similar experience or if any of you could help me out Please share it here. It would be GREAT!
Also just one more thing- Any of you seen any DRASTIC or worse changes in battery life of your Galaxy S7 after the Android Nougat 7.0 update? Please share your thoughts here and do suggest how you solved the problem. (My battery drains so fast that I sometimes charge it twice a day. I don't even use my phone for half of the day because I'll be at school and still the battery drain is bad! )
Factory reset. Backup your data via kies and then reset it.
Change your battery
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Us3rNam3d said:
Factory reset. Backup your data via kies and then reset it.
Click to expand...
Click to collapse
Hey, man!
I already tried it like 3 times now. No luck!?
CurtisMJ said:
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Click to expand...
Click to collapse
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Hmm... and after the factory reset with no apps installed you are still rebooting?
Why dont you try to reflash your firmware via odin.
Download it from sammobile and reflash it.
AgentArjun56 said:
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Click to expand...
Click to collapse
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
CurtisMJ said:
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
Click to expand...
Click to collapse
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
GeekTN said:
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
Click to expand...
Click to collapse
If it's restarting due to the firmware bug then DQD7 will most definitely fix it. Beware of the emergency recovery though. Ive not used Smart Switch but the "initialization" part sounds like it would wipe the device, though that could fix any issues. Backup first, if you can.

Bad first experience

Has anyone else had any of these problems with their oneplus 6?
-files disappear after each reboot
-keyboard stops functioning on lock screen and I can't unlock the device
-apps randomly losing their data such as Snapchat/Instagram and I have to log back in
-can't use any other keyboard with a password since the device comes encrypted. My s7 used default keyboard before being decrypted.
I have factory reset at least 3-4 times since I have owned the device.
Oneplus customer support said in regards to my files being randomly deleted, "You should just backup your stuff with google drive". Is that really the solution? Just expect my files to be erased and have to recover from backup after each reboot? Most of the customer support people never understand my problems that I am trying to tell them and I can hardly understand them either. Sorry for ranting a bit. I was excited to get rid of my galaxy s7 and try something new that I was told has good rom support and little no bloat on stock ROM, but I've been very disappointed. I guess after seeing their customer support is partnered with Acer it makes sense.
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Pat123 said:
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Click to expand...
Click to collapse
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
user9340 said:
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
Click to expand...
Click to collapse
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
ramqashou said:
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
Click to expand...
Click to collapse
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
jabbermacy said:
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
Click to expand...
Click to collapse
DCIM, Downloads, whatever directory downloaded Spotify music goes to, Some screenshots would disappear, but not all. I turned on logs and am going to give it another week or so.
Lightbird said:
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
Click to expand...
Click to collapse
Should I just switch to Android P?
P is still beta with lots of bugs. Some have said it's stable enough for a daily driver but ymmv.
user9340 said:
Should I just switch to Android P?
Click to expand...
Click to collapse
No, too many bugs
user9340 said:
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Click to expand...
Click to collapse
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
iElvis said:
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
Click to expand...
Click to collapse
I think I just realized I may have done reset system settings instead of factory reset.

Question I just bought a Galaxy A22 5G, and it's having these issues.

The phone freezes and flickers
Reboots automatically at intervals for no reason at all
Did you have magisk installed?
FelipeHiroshi said:
Did you have magisk installed?
Click to expand...
Click to collapse
No. This happened right after the unboxing also. The screen pixelates and then rebooted. Til now the problem is there. But it's less frequent now. Please help me fix this
Uhum very weird try the easy first,factory reset and wipe cache,if din't work you can try flash another stock firmware via odin.
FelipeHiroshi said:
Uhum very weird try the easy first,factory reset and wipe cache,if din't work you can try flash another stock firmware via odin.
Click to expand...
Click to collapse
I already tried factory reset for like two times. Didn't help. Lemme try to flash another firmware and see if it resolves. Thanks
I also have the reboot issue. I don't have any other issues. My phone has the official firmware, I didn't flash any custom rom.
The problem first showed up for me a few days after the November firmware update.
MeDontWorry said:
I also have the reboot issue. I don't have any other issues. My phone has the official firmware, I didn't flash any custom rom.
The problem first showed up for me a few days after the November firmware update.
Click to expand...
Click to collapse
For me now all problems have subsided. I haven't encountered any problems since last week. I didn't even update. The problem just vanished. Thank goodness. Btw, keep an eye out for One UI 4 Android 12 update. It's fix most of the problems. And might bring new problems too lmao
Oh amazing!! I'm happy for you! I most certainly will, I'm looking forward to the update. The weirdness is that it only happens very occasionally! Like, in total I've encountered it less than 10 times I guess. It happened three days ago and again today (while I certainly use my phone a few hours a day).
MeDontWorry said:
Oh amazing!! I'm happy for you! I most certainly will, I'm looking forward to the update. The weirdness is that it only happens very occasionally! Like, in total I've encountered it less than 10 times I guess. It happened three days ago and again today (while I certainly use my phone a few hours a day).
Click to expand...
Click to collapse
Let's hope your phone also would get better soon. It's not like a software problem or anything. I don't know what kind of sorcery this is. Samsung must have put a spell on these phones
Haha thank you! I still hope that it's a random and weird software issue, so that it can be solved in the next update lol.

Categories

Resources