Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datę, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.
Hello everyone sorry for this new thread and but I wanted to make sure I give more information on a fresh thread so I can hopefully fix this issue.
The issue I'm having is: When Hotspot is enabled on my Mate 8 Device, the 4G connection does not work on the device itself. However, anyone connected to the hotspot that I enabled has internet access via my Mate 8. Both cannot work simultaneously, only one or the other. This started 3 days ago.
What I did to perhaps cause the issue:
I rooted the factory ROM and changed something with the "Disable Service" app. I diabled the FusedLocation service. I rebooted then it was stuck on bootloop
I proceeded to wipe the phone on TWRP and installed a B180 ROM(Basic, stock international room - rooted) - Problem with Wifi Hotspot persists.
I thought it was the ROM's issue so I upgraded to B320 OEM ROM via 'dload' method - Problem Persists
Installed TWRP 3.0.2 and flashed another L29 B3xx ROM - Problem persists.
every time I installed a new ROM I wiped everything off the phone before I did so.
I'm absolutely stumped.
Please see the image i attached to my findings on my phone.
As you can see when Hot Spot is on, the 4G is "disconnected" and does not get an IP address.
Image Link
https://drive.google.com/file/d/0B-rbvYjlRN26bC1rbkpZYUc0dDA/view?usp=sharing
Any help is greatly appreciated again. Thank you for your time!
Eddie
Hi, I have the exact same issue, I am using a completely stock phone, with stock recovery and not rooted.
Have you found a fix to this problem?
Thanks.
HI,
My OPO 64GB sandstone Black is experiencing Bootloop everytime it heats up, then i turn it off for 5 minutes to make it cool. After that, it works fine. I bought it about 8 months ago. A month ago, I upgraded it to CM13 official. About 15 days ago, it suddenly went bootloop. Then i checked and found that it was softbricked. Then I did some homework and unlocked the bootloader and downgrade it to Kitkat CM11, but lost all of my data. Finally it came back to life, but the bootloop comes everytime it heats up till now.
I have some question and also asking for a solution to overcome this problem. Questions are listed below
1. What is the suitable solution for this problem?
2. Does my device have any hardware issue or is it just software related problem?
3. Will my device work like before, if i somehow find a solution or its the type of problem which keeps coming back?
Please help me regarding this issue. Thanks in advance.
Try flashing this: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
P.S. You will lose your data
Pm me have gone through this thing
KuranKaname said:
Try flashing this: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
P.S. You will lose your data
Click to expand...
Click to collapse
Thanks for the suggestion mate and i tried the whole process and installed it. But the same problem of heating issue still exist and the phone goes bootloop. Any other way to fix this.
Thanks in advance.
arnisaha said:
HI,
My OPO 64GB sandstone Black is experiencing Bootloop everytime it heats up, then i turn it off for 5 minutes to make it cool. After that, it works fine. I bought it about 8 months ago. A month ago, I upgraded it to CM13 official. About 15 days ago, it suddenly went bootloop. Then i checked and found that it was softbricked. Then I did some homework and unlocked the bootloader and downgrade it to Kitkat CM11, but lost all of my data. Finally it came back to life, but the bootloop comes everytime it heats up till now.
I have some question and also asking for a solution to overcome this problem. Questions are listed below
1. What is the suitable solution for this problem?
2. Does my device have any hardware issue or is it just software related problem?
3. Will my device work like before, if i somehow find a solution or its the type of problem which keeps coming back?
Please help me regarding this issue. Thanks in advance.
Click to expand...
Click to collapse
Hi, have you tried to undervolting the cpu? This might help you to keep it cold
You only have to flash a kernel which let you customize volting values
And If the problem persist try to clean flash the latest oxygen os (It has the latest drivers so maybe it works).
Try this: Install Kernel Adiutor, underclock cpu to 1728 Mhz, Undervolt (if possible) by -50 global, and enable everything in Thermal
I have the same issue. Is there any solution?
So, I rooted my S7. It worked fine. One day, randomly out of no where it bootlooped (Google play services crashed. I restarted phone and it bootlooped. )
I have not made a single system modification other then rooting it. Didn't mod anything or mess with system files, and I had barely even been using the phone when it happened.
So I unrooted it (The phone still gave me the "Custom" symbol though) and Just now-- It randomly restarted. I didn't restart it. it just did it by itself. And it came into a bootloop. I don't understand why. What can I do to fix this?
MORE SPECIFICALLY: By Bootloop, I mean it stays on the T-Mobile screen and vibrates every minute or so and does not do anything (I even left it alone for ~ 30minutes and it never got past this screen)
Factory resetting the phone fix's it, but I don't want to factory reset my $400 phone every week! I don't understand how I could fix this either.
What method did you use to unroot? Did you flash stock firmware with odin?
sparky2029 said:
What method did you use to unroot? Did you flash stock firmware with odin?
Click to expand...
Click to collapse
All I did pretty much was flash stock s7 firmware. (More specifically boot.img)
Originally couldn't find a stock s7 image then I just used one I already had and it worked fine
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Just now noticed wat your problem is sorry for being late so yes to fix the bootloop refladh stock firm and when you go through all the root steps install xposed (yes it's possible it's insane on how they got it to work but it's possible I've done with my self)after getting xposed installed through flash fire go to xposed and get xtouchwiz something it's a blue gear install that And it will set your system status as official
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Here's a quick explanations of wat i think it is it's becuz you've ether heavenly been modding the phone or if your phone status is custom then that's the problem I had with mine after asking around someone gave me the fix i put it in the other comment hope this fixes your issue it worked for me 2 months of no bootloop I switched to 7.0 vzw beta so I lost root
Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks