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?
Related
so i was planning on doing this today, but then obviously when 6.0 comes out i can't take the OTA because of custom recovery so I'd have to wait for someone to make a flashable rom.
so what's everyone else doing? should I root now and enjoy it, or wait for 6.0 then root? no timetable from moto yet
Sent from my Moto X Pure Edition
Ota is not the only way pretty sure we will have images or someone grab ota and post zip
Sent from my XT1575 using Tapatalk
I'm waiting but mainly cuz I like this phone stock and I'm in no rush. Also I don't want to set everything back up so I will let marshmallow back it all up for me
You can always flash the stock ROM and take the OTA or wait a short time for a flashable version.
Bangin' on my unlocked/rooted
Moto X Pure
With a phone like this there is always going to be a way to install the latest update. Who cares about OTA.
Thread moved to Q&A
Cheers,
Baja
spotmark said:
With a phone like this there is always going to be a way to install the latest update. Who cares about OTA.
Click to expand...
Click to collapse
nah i know, like i do with my nexus 7 (haven't touched stock android in a while since my note 4 and samsung tabs, so i really don't remember)
so you guys think there's gonna be some good dev to atleast get a flashable 6.0 out? might as well just do it. just wanted to see the general opinion
I would do it now. Unlocking the boot loader will wipe your phone. Like someone said above a flashable zip should be available soon after the OTA touches down.
---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------
jayochs said:
nah i know, like i do with my nexus 7 (haven't touched stock android in a while since my note 4 and samsung tabs, so i really don't remember)
so you guys think there's gonna be some good dev to atleast get a flashable 6.0 out? might as well just do it. just wanted to see the general opinion
Click to expand...
Click to collapse
To be honest it doesn't take much skill to do. I'm sure we have plenty of people already here who know how
sweet. alrgiht just did it! woo rooty goodness.
I wonder when we will get marshmallow ota or rom based. Seems like zero development on this device which kind of sucks. I just want some omni or beanstalk. Not sure if the dev area is waiting on source or how a that works but I figured by now we'd have something to flash.
Sent from my XT1575
cyris69 said:
I wonder when we will get marshmallow ota or rom based. Seems like zero development on this device which kind of sucks. I just want some omni or beanstalk. Not sure if the dev area is waiting on source or how a that works but I figured by now we'd have something to flash.
Sent from my XT1575
Click to expand...
Click to collapse
I thought they are simply waiting for the kernel source
cyris69 said:
I wonder when we will get marshmallow ota or rom based. Seems like zero development on this device which kind of sucks. I just want some omni or beanstalk. Not sure if the dev area is waiting on source or how a that works but I figured by now we'd have something to flash.
Sent from my XT1575
Click to expand...
Click to collapse
many people got their devices not to long ago this isn't nexus remember I am just waiting patiently
cyris69 said:
I wonder when we will get marshmallow ota or rom based. Seems like zero development on this device which kind of sucks. I just want some omni or beanstalk. Not sure if the dev area is waiting on source or how a that works but I figured by now we'd have something to flash.
Sent from my XT1575
Click to expand...
Click to collapse
When device trees are completed with no major bugs, expect many ROMs and kernels ? (should be very soon)
Hashbang173 said:
When device trees are completed with no major bugs, expect many ROMs and kernels (should be very soon)
Click to expand...
Click to collapse
Good to hear, not bashing devs cuz I know I sure can't make a rom and appreciate the hard work that goes into it. I figured it was a source reason. Is that something moto needs to release or someone has to snag from the devices. I haven't flashed anything since the note 2 was release so just a little over eager I guess that and hearing people say devs might not be super keen here with the nexus coming soon.
LOL @ "zero development". This phone hasn't even been available for 3 weeks yet. If you ordered one on day one, you were lucky to get one 2 weeks ago.
Bangin' on my unlocked/rooted
Moto X Pure
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
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Real1minshen said:
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Click to expand...
Click to collapse
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
jhs39 said:
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
Click to expand...
Click to collapse
Thank you~
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.
What ROM's are people running on their Verizon LG V20? Im getting ready to root mine and go through that process. Looking over the ROM's though and they seem to be lacking. Back in the day we had tons of options, now we have a handful on XDA. Are there ROM's people are running that arent listed?
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Ashalinia said:
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Click to expand...
Click to collapse
Ive been trying to find screenshots as Im pretty particular on my OS. I used to love MIUI when it was around.
Lineage for ls997 is horrible I'm using emotion build 4-16
pbedard said:
Lineage for ls997 is horrible I'm using emotion build 4-16
Click to expand...
Click to collapse
Why is it horrible? And why is Emotion better?
Depend on what device u using
pbedard said:
Depend on what device u using
Click to expand...
Click to collapse
That's true for anything. Just going out on a limb here, I'm guessing since we are in the LG V20 forum its safe to assume we are using that device.
Next time come prepared with proof of your claim. With no proof and bold claims you sound like a fool.
as Android goes further the ROM field is super small now KK had the biggest amount of ROMS not a lot of this model I have this version too we have RR DU is coming down the line Lineage WETA AOKP Here is a list of ROMS https://www.androidfilehost.com/?w=search&s=us996&type=files
I have a ls997 and im running Paranoid Android.
I have a vs995 and I'm running XOSP ?
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
mirrin said:
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
Click to expand...
Click to collapse
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
mkfryan said:
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
Click to expand...
Click to collapse
that is what i tried first but the rom was not rooted...
Gre thanks
mirrin said:
that is what i tried first but the rom was not rooted...
Click to expand...
Click to collapse
Did you flash supersu or magisk? Not all roms come rooted...
None I had issues getting it to work had issues booting found weta it worked it has a janky root but it worked and Pokemon go worked and I don't even get the static lines on the screen...
BroeknOs to be
Currently I'm running stock OS on LightningZap! kernel (still in beta, but looking like I'll have a release soon).
I have gotten BrokenOs running quite well and smoothly. But lacking the second screen is what's holding me back.
On LG V20 AT&T (H910), btw...