Related
I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)
Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app
killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.
This does not happen at all to me(using stock 5.1 with Franco Kernel).
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).
Your battery is dying, I've been getting the same problem until I replaced the battery today.
richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?
I've been getting the same issues on my N7 since updating.
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.
Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng
gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.
I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk
I'm planning to downgrade to MM due to the hideous Android OS and Android System battery draining. Getting hardly 2 hours of SOT with very light use. Anyway I know that I'll have to flash the factory image but there are a lot of model types and I don't know which to download. So how do I know the variant and is there a difference between them and is there a certain model famous for the battery drain bug while the others are working fine?
Ghand0ur said:
I'm planning to downgrade to MM due to the hideous Android OS and Android System battery draining. Getting hardly 2 hours of SOT with very light use. Anyway I know that I'll have to flash the factory image but there are a lot of model types and I don't know which to download. So how do I know the variant and is there a difference between them and is there a certain model famous for the battery drain bug while the others are working fine?
Click to expand...
Click to collapse
If you are going down to Marshmallow surely just go to the last version of MM
https://developers.google.com/android/images#angler
Grab - 6.0.1 (MTC20L)
I don't think battery drain was that much of an issue on MM but could be wrong, someone else may recommend a different build but i'd go with the last build. before nougat.
brichardson1991 said:
If you are going down to Marshmallow surely just go to the last version of MM
https://developers.google.com/android/images#angler
Grab - 6.0.1 (MTC20L)
I don't think battery drain was that much of an issue on MM but could be wrong, someone else may recommend a different build but i'd go with the last build. before nougat.
Click to expand...
Click to collapse
There have been rumors about a bricks while downgrading?
I am not rooted , no custom recovery, unlocked bootloader. So that should be okay right?
Can't see how bricking is possible. Unlock, flash, lock. Done a thousand times.
Skickat från min iPhone med Tapatalk
I downgraded using the listed build with no issues. Battery issues appear to be resolved too. Can't get over how poorly optimised 7.1.1 was.
Regards.
Sent from my Nexus 6P using Tapatalk
You will be fine use the instructions on the sticky by Heisenberg and just use the files from that zip of the build i mentioned.
Hey, guys.
I want to downgrade to MM too because of the same battery drain reason. I'm running the latest PureNexus 7.0
I was on RR before. I'm rooted, unlocked, latest TWRP. Can I just flash my old RR Rom and the MM vendor image?
Holy Hell... I come here periodically to check whether battery drain has been solved. One of the reasons I chose a Nexus for was to get timely security updates. Tying them to a sub-par version of the OS ends up negating the advantage for me. How can Google mess up battery so much, after all the talk about battery life improvements with Nougat?
gorman42 said:
Holy Hell... I come here periodically to check whether battery drain has been solved. One of the reasons I chose a Nexus for was to get timely security updates. Tying them to a sub-par version of the OS ends up negating the advantage for me. How can Google mess up battery so much, after all the talk about battery life improvements with Nougat?
Click to expand...
Click to collapse
They were to busy with the pixel to care about providing to Nexus owners.
On topic I used the above factory image to downgrade my completely stock, locked, and not rooted 6P without issues.
Sent from my Nexus 6P using Tapatalk
For the record, I just flashed the MM vendor image and RR rom via TWRP and everything booted just fine and is running smooth. Didn't have to flash the stock rom. I'll just leave this here in case there's someone else looking for a solution
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk
Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?
jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.
I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app
Bad news, and there isnt official answer from Google
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.
jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse
CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?
My Nexus 6P went in a bootloop recently.
It was shortly after I unlocked the bootloader and rooted the phone.
I tried everything I could (stock firmware 7.1, 7.0 and the oldest that was available) but nothing worked.
I still had warranty so I sent it back to webshop where I bought it.
Now I got my phone back and the note says 'Mainboard replaced'.
What I want to know:
- Can it be my fault the phone broke, I know the Nexus 6P has some issues concerning bootloops.
- Can I safely root again? Or would you not recommend it?
Thanks for your answers.
I have a backup phone, but I don't want to f*** my 6P up again.
Search for BLOD. You will answer your own question in no time. Lol No you are not to blame. It had or is happening to probably hundreds of phones by now. You will also see there are many different roms, 6&7, root or stock that have the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app
Rooting doesn't cause the boot loop of death. Flashing something sometimes triggers it (including flashing a normal OTA on pure stock) but it is almost certainly a hardware issue.
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow.
However, my security patch is from April 2016.
I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Sent from my Nexus 6P using xda premium
Lior84 said:
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow. However, my security patch is from April 2016. I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Click to expand...
Click to collapse
I respect your decision to stay with MM, but I think it is misguided. There are many improvements that come with installing N, including the security updates. Security updates are part of the OS update and are not available separately. If you want the benefits of the latest security updates, you have to install 7.1.2.
Right now I'm on latest stock rooted with franco kernel and there are no issues. Except there's no xposed support.
But updating to nougat comes with no issues, so u should try, make a backup and flash.
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
Nah, don't be afraid, I'm flashing everything with twrp, factory images too. No issues.
If by brick issue you are talking about the boot loop of death that's a hardware issue and it happens while you are on Marshmallow, Nougat or a custom Rom. If you are talking about something else as long as your bootloader is unlocked and OEM Unlock is enabled in developer options you should be able to recover in the unlikely event of a flash going bad. Whether to flash or not is a tradeoff. You get the latest features and security updates on Nougat but you can't use Xposed (if that's actually important to you) and you will almost certainly get worse battery life on the latest versions of Nougat than you are getting on Marshmallow. Google has goosed the stock kernel settings lately resulting in worse battery life and the operating system and screen using more battery than previously. The only way to avoid that and stay up to date is to flash a custom kernel or flash a custom Rom.
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Sent from my Nexus 6P using xda premium
Lior84 said:
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Click to expand...
Click to collapse
The bootloop issue has nothing to do with the os update. It is because of dodgy hardware. It can happen from a damaged and degraded battery. Updating to nougat doesn't cause the issue.