Database Users

New Factory Image is available for download. LMY48I

http://www.droid-life.com/2015/08/0...mages-arrive-for-nexus-4-5-6-7-2013-9-and-10/

This opens a number of issues for me.
Between those who said they don't like the performance of Lollipop on razor/razorg and those who said that some of the Lollipop OTAs bricked their devices, I decided to stay on KitKat. And with M coming soon, I am hoping to just sit Lollipop out (and that they will make factory images for M available for razorg!)
But it seems Google isn't back-porting security fixes to KitKat, so if I want to stay secure, I'm going to be forced to update to Lollipop, if not for stagefright, then for some other issue in the near future.
Apart from MMS, do we know what the other potential exploit vectors of the stagefright bug are?
Sent from my LG-H815

In regards to performance, my Nexus 7 has never run better since the Lollipop updates. I don't take OTA's though. I run rooted stock, with a custom kernel so that I can slightly overclock the GPU to 450MHz, and the CPU to 1.7GHz, giving me real Snapdragon 600 performance, instead of the underclocked "S4 Pro" speed the Nexus 7 uses by default.
Sent using Tapatalk

I'm glad to hear it's doing well for you. Perhaps I'll just flash the latest Lollipop image on it and see.
Sent from my LG-H815

New bootloader in LMY48I
When I saw there was a new bootloader, I hesitated. I was afraid it would be locked and have to be unlocked, wiping my N7. But I backed up, plunged ahead, flashed (with WugFresh's Nexus Root Toolkit (NRT) 2.0.5) the new bootloader, then boot.img, system.img, and cache.img. The updated bootloader was still unlocked and I didn't lose my data! I rooted via NRT and all is well. An uneventful update. Hope this helps.

^The bootloader is the same since 5.1. MD5: 2bcd3097abcc6923b2a3e5f6035e3b18
System, boot and recovery.img changed. I just flashed system and boot. No problems. And twrp since flashing only system and boot images somehow the stock recovery appears. I definitely didn't flash the stock recovery...

Lollipop is **** if u are a gamer even on latest releases (playing games other than Candy Crush) . if u don't play games like Vainglory, Minion Rush, Spiderman Unlimited, etc. then u can flash Lollipop (if u are on stock KK and u flash the factory image of Lollipop, then it is impossible to brick your device. If u upgrade from KK to LP using the OTA then u have a chance of bricking the device). If u are like me and u care about the FLO/DEB performance and want to play certain resource demanding games, then go with a KK ROM like Mahdi 2.9 Final and apply a Lollipop theme and u will almost not see any difference in terms of UI.
Sent from my Nexus 7 using Tapatalk

having mixed feelings about this new update, installed it and the official zimperium stagefright detector still said I was vulnerable to ALL exploits while another app said I was not vulnerable at all! Don't know what to believe though...
Anyone else still "vulnerable" after this update?

Maybe I'm missing something, but why is stagefright even a concern on the Nexus 7?
Sent using Tapatalk

just lou said:
Maybe I'm missing something, but why is stagefright even a concern on the Nexus 7?
Sent using Tapatalk
Click to expand...
Click to collapse
It doesn't only come from MMS but also from browsers like chrome, stock browser, .... which is pretty much a bigger threat than MMS as not everyone knows your phone number but everyone can put there nice little virus on the internet and when accessed they would have full control of our tablets!

noahvt said:
It doesn't only come from MMS but also from browsers like chrome, stock browser, .... which is pretty much a bigger threat than MMS as not everyone knows your phone number but everyone can put there nice little virus on the internet and when accessed they would have full control of our tablets!
Click to expand...
Click to collapse
OK. Thanks. I thought it was only a MMS threat.

Software Update 143.49MB Details

ALERT: Patch for critical security vulnerability ('Stagefright')
- Device stability improvements, bug fixes.
- New and/ or enhanced features.
- Further improvements to performance.
To get the best from your device, please keep your phone up to date and regularly check for software updates
* After updating. you will not be able to downgrade to the old software because of updates to the security policy.

Just updated the wife's Note 4 and it is NOT N910T3UVU1DOFC (5.1.1) like the Internet says. < http://www.ibtimes.com/android-511-...ng-galaxy-note-4-t-mobile-how-install-2039649 > Just a patch for N910TUVU1COG2 (5.0.1).
Just fyi

Downloading now. Wonder what the new/enhanced features are?

thegreatone3 said:
Downloading now. Wonder what the new/enhanced features are?
Click to expand...
Click to collapse
Probably Stagefright fix

Yep, just the patch. Also you can go back to an older version of Android. I thought this patch messed up my SD card and Odin'd back without a problem. Turns out my SD card was just bad.
Sent from my SM-N910T using XDA Free mobile app

Updated to new patch, battery life gotten really bad since update this morning.
Sent from my iPad using Tapatalk

Can I upgrade this security patch running a non touchwiz ROM on my note 4?

I posted this test after I updated to this build, I hope another update is on the way soon if this is what we're getting after their latest update.

Haven't gotten anything yet.. I will let it OTA itself

note4 guy said:
Updated to new patch, battery life gotten really bad since update this morning.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
You will usually get less than normal battery life after an update. This is normal for Android.

What is the best course of updating if I'm rooted and on a custom TW rom?

Unconfirmed, not exactly why or how but my gf's N4 has been suffering from poor signal and loss. This update has seemingly corrected those issues. I haven't done it on mine but I'm optimistic because I've been having similar issues. They just say "bug fixes" so not sure exactly what that is. Obviously the Stagefright is one of those but there may also be tweaks and corrections here and there. I'd be curious to know if anyone else has been having those issues and whether or not this update fixes them.
Also confirming its not 5.1.1

I used a different app to test and it said I was not vulnerable.
Sent from my SM-N910T using XDA Free mobile app

dkb218 said:
You will usually get less than normal battery life after an update. This is normal for Android.
Click to expand...
Click to collapse
You can also boot up into recovery and wipe cash partition which will sometimes help, this is what I did when updating from 4.4 to 5.0 it helped.

I did try a few other apps to test stagefright and one said no and two said it was vulnerable, the best process to update which has never failed me is Odin to full stock, root it flash recovery and flash what you want from there, I've tried every way there is to sneak an update but that's the sure fire way to make sure everything is in order and gives the best outcome.

Downgrade to Marshmallow , Which model?

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

Downgrade to Marshmallow to avoid bootloop?

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?

About downgrading and

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~