yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] lawrencegs:
Here you go: https://www.dropbox.com/s/e4jzexge8yn8a2v/system_nexus6_lnx07m.zip?dl=0
[Nexus 6  General] TheManii:
We still need a proper dump of LNX07M,

[REQ]Dump of the preinstalled rom

You can do so from within TWRP: Nexus 6 Gets Official TWRP Custom Recovery

Unlock your bootloader, boot up (NOT FLASH) twrp, and do the steps in the 1st link for a good dump.
[Nexus 6  General] lawrencegs:
Sorry I've already updated mine now...
[Nexus 6  General] jlsat:
Where is the LVY48E link?
[Nexus 6  General] VivaErBetis:
Here is the link:

https://drive.google.com/open?id=0B8cYrKb6cTtOTDk2RnhMRkRCUjg

The original Google link isn't discovered yet.
[Nexus 6  General] Milamber:
Do we know what fixes are contained in this new ota?
[Nexus 6  General] nedd1:
This is a noob question and I hope people don't get annoyed with me asking here. I have been using HTC's all my Android life, but have just swapped to Nexus 6.

I took it out of the box, updated to latest firmware, unlocked bootloader, rooted and flashed recovery.

Now I am wondering when Google release a new version how do I upgrade, obviously OTAs won't work but will there be somewhere I can get a copy of the OTA (or the latest firmware) and flash using TWRP? If this is the case can I dirty flash that over stock or do I need to clean install?

Thanks in advance.
[Nexus 6  General] Milamber:
I was going to sideload via Wugg Nexus Tool Kit, sideload requires a zip file and the file from google is a tgz, is it ok to extract the "shamu-lmy48i-factory-230e50fe" file and zip it, so Wugg's Nexus Kit will see the file to sideload??
[Nexus 6  General] Onlyunless:
https://android.googleapis.com/pack...amu-ota-LVY48E-from-LVY48C-superblock-fix.zip

I just received this OTA on my Project Fi Nexus 6.
[Nexus 6  General] jlsat:
Me too. So how do we update if we are rooted and don't want to lose data?
[Nexus 6  General] biggiestuff:
I'm on T-mobile and just got the prompt to update. I'm rooted but how do you pull the OTA before I update so others can have it?
[Nexus 6  General] oldblue910:
Check logcat. Use adb, and type adb logcat > logcat.txt

Then after about 20 seconds or so, hit Ctrl-C, then open logcat.txt and search it for ".zip" (without the quotes). Post what it says here.
[Nexus 6  General] biggiestuff:
the logcat is still being built. I open it from time to time to search for zip but get nothing. i tried looking for LYZ28J. Could being encrypted slow down the process?

---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------

Here is the link for LYZ28J for t-mobile i got from the bug report

https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
[Nexus 6  General] Onlyunless:
The command should actually be

adb logcat -d > log.txt

just adb logcat will be streaming the current logs as they are created. The -d flag will dump logcat's history. If the file had downloaded before you tried to grab it, it would be in the history.
[Nexus 6  General] oldblue910:
:good: Good point.
[Nexus 6  General] housry23:
You will have to download the factory image and flash system, boot and recovery images(if you have a custom recovery). That should allow you to take the OTA. Or, you can just wait for a stock rooted version of the Rom. Or you can wait for Google to update the factory images page and flash system and boot from the factory image and then reroot.
[Nexus 6  General] cinco312:
Wait for Google to update the factory image page (Be prepared to wait) once downloaded, extract it and open up flash-all.bat in notepad and remove "-w"

from the code on the bottom. Save and then flash without losing data.
[Nexus 6  General] Scottatron:
Ok, I just got the update for LMY47Z > LMY48I. I haven't applied or anything yet. If someone can tell me how to obtain the information, happy to assist.
[Nexus 6  General] xdatastic:
Enable Developer Options (tap on Build Number lots of times), then enable Bug Reporting in Developer Options, send yourself the bug report to your email. Then check the email for the bug report. Inside the txt file bug report should be a long URL ending in .zip
[Nexus 6  General] Scottatron:
Ok, trying this now. Standby...

---------- Post added at 10:34 AM ---------- Previous post was at 10:28 AM ----------

We have lift off:

OTA link for LMY48I from LMY47Z below.

https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip
[Nexus 6  General] oldblue910:
Thanks to [MENTION=2828095]Onlyunless[/MENTION], [MENTION=2147991]biggiestuff[/MENTION], and [MENTION=4388258]Scottatron[/MENTION], we now have all the Nexus 6 stagefright fix OTAs. Thank you, gentlemen. Much appreciated!
[Nexus 6  General] BLONDMAN:
see this;

link LMY47Z from LMY47I - https://android.googleapis.com/packa...superblock.zip (Oceania)
[Nexus 6  General] VivaErBetis:
It means that the person who gives the link receives the ota in Oceania, not that the ota is only for Oceania.
[Nexus 6  General] :
This isn't a support thread for OTA questions.

Please post your questions here:

http://xdaforums.com/showthread.php?t=2992919

Thanks! :)
[Nexus 6  General] BLONDMAN:
plz see this link:http://www.randomphantasmagoria.com/firmware/nexus-6/shamu/

thank you so much.
[Nexus 6  General] stevexyz0:
As the link you posted shows and all other available information confirms, 47I was for Oceania and 47Z and 48I are both for widespread international and US use. The 47I to 47Z update you cited earlier was labeled Oceania because it would be useful to Oceania customers coming from 47I to the worldwide standard 47Z build. It does not mean that 47Z is a build exclusively for Oceania.

Regardless, everybody worldwide should now be on 48I to get the Stagefright security fix, except t-mobile USA and project fi which have their own Stagefright fix builds.
[Nexus 6  General] bkircher:
Hey all

I dont know if this would fit here or not, but I recently flashed to 6.0 and am on build MPA44G, but now there is a newer build out, I guess its a small update from what Ive read but its build is MPA44I, as of now there isnt an ota from G to I. Ive read that I can just take the system, recovery, and boot image files and flash them individually, if I do that, I will continue to get future ota updates right? I just am unsure since its not a full ota that I would be doing. I dont really want to flash the whole new software since I just got up and running again.

Any suggestions would be helpful.
[Nexus 6  General] teinwhite:
Just don't flash userdata and you should be good to go.
[Nexus 6  General] TokedUp:
Well here we go again! Please post the URL Fi users! Need that new build!
[Nexus 6  General] pcrussell50:
Stupid question time... Apologies in advance... But what is differ about the URL, than simply flashing the image when it comes up in the Google developers site?

-Pete
[Nexus 6  General] xdatastic:
Applying the OTA doesn't wipe your data if your bootloader is still locked.
[Nexus 6  General] pcrussell50:
Thanks mate
[Nexus 6  General] TokedUp:
Some of us just want to sideload the OTA instead of flashing the full image. U dont need to be rooted to sideload.

BTW the ProFi build # ends in 'F'. Keep ur eyes peeled!
[Nexus 6  General] marstein:
Didn't change the content, sorry for the late answer. That's also why I don't remember the filename. Next time...
[Nexus 6  General] jcsww:
You can flash the factory image without flashing the User Data and upon reboot, just wipe the cache and don't factory reset and you should be fine.
[Nexus 6  General] TokedUp:
Yeah but sideloading the OTA is really easy
[Nexus 6  General] boomerbubba:
Piecing together information from various online sources, it looks like the three OTAs to capture (one for each of the current Android forks) are these:

LMY48I to LMY48M. (Main Android build)

LYZ28J to LYZ28K. (T-Mobile build)

LVY48E to LVY48F. (Project Fi-specific build)
[Nexus 6  General] TokedUp:
I'm F5ing the **** out of this thread lol!
[Nexus 6  General] efrant:
The end result is the same. However, there are some differences:

An OTA update will work with the bootloader being locked. Flashing the factory image will not.

To flash an OTA update, you need to be 100% stock (i.e., stock ROM, stock boot image (kernel/ramdisk), stock recovery, no, root, etc.). To flash a factory image, you do not need to be stock (nor do you need root as was implied earlier by someone).

Both are able to retain your data/settings/apps if you so desire.

Flashing the factory images is generally faster than waiting for the OTA update to patch the files on your device.

The OTA update generally comes out before the factory images get posted.
[Nexus 6  General] openbook:
Need lmy48m from lmy48i OTA zip
[Nexus 6  General] TokedUp:
We're all waiting man. Get in line
[Nexus 6  General] carboncache:
I'm on AT&T with an unlocked N6 running LMY48I, and I'm assuming this OTA is gonna be at least AT&T friendly if not also fine for other non-Fi and non-Tmo users. Can I still logcat if I'm waiting on WiFi to download the file, will the link be ready to pull now?
[Nexus 6  General] carboncache:
The answer was yes. OTA link for LMY48I to LMY48M:

https://android.googleapis.com/pack....signed-shamu-LMY48M-from-LMY48I.4458964f.zip
[Nexus 6  General] jj14:
I'm stock rooted with T-Mo - on LYZ28J, and just got notification about system update. Happy to share the URL, but not sure how to pull it. (I've never used logcat)

Edit: https://android.googleapis.com/pack....signed-shamu-LYZ28K-from-LYZ28J.2888e222.zip

Thanks [MENTION=3953440]anonchalantsigh[/MENTION]
[Nexus 6  General] carboncache:
I didn't use logcat either. I went to developer options, enabled the bug report in power button menu option, waited for it to generate the report (5-ish minutes), and just went into the file generated to approximately the time the OTA was ready.

The link itself was pretty obvious when you find it. You could probably CTRL+F to find it searching for the build number or 24-hour timestamp (I used 14:12 local time here). It was somewhere in the middle of the file, a long beast of a *.txt file.

Sent from my Nexus 6 using Spacestar Ordering

---------- Post added at 05:07 PM ---------- Previous post was at 04:26 PM ----------

You're welcome! Now we're both ready for the big 6.0 URL hunt later this fall.

Sent from my Nexus 6 using Spacestar Ordering
[Nexus 6  General] jj14:
Since I'm rooted, I can't take OTA anyway... looks like the factory image is out now, so I'll flash the system image from there. Just thought I'd share this for folks that might need it :)
[Nexus 6  General] ALUOp:
Thank you very much, mate!
[Nexus 6  General] TokedUp:
Need that Fi OTA! Fiending right now lol
[Nexus 6  General] RMarkwald:
Bootloader and Radio is the same from 48E. I just downloaded the factory image, booted to bootloader, and flashed the zip file. All app data and /sdcard was fine, as I omitted the -w flag. Running 48F now without issue:

fastboot update image-shamu-lvy48f.zip
[Nexus 6  General] TokedUp:
Dude I'm not rooted or UBL. Went over this already. Need to side load OTA.
[Nexus 6  General] Jozen:
Picked up the Nexus 6 with the great Amazon deal. I have updated my phone and I am sitting at LMY48M but I am a T-Mobile user. So I do not see a wi-fi calling option anywhere. Should I try sideloading one of the LYZ T-Mobile versions?
[Nexus 6  General] jcsww:
I would either wait the few weeks to see if there is a carrier specific M build for T-Mobile to flash or download the latest T-Mobile image directly from Google and flash it.
[Nexus 6  General] Jozen:
Surviving without wifi calling for a few weeks will be rough. I'll see how long I can hold out before rooting and flashing. Thanks for the advice.
[Nexus 6  General] boomerbubba:
Please take this discussion elsewhere, to the Nexus 6 Q&A Forum. This is a reference thread for collecting links to OTA files, and folks are checking it for that purpose. Your little problem does not even have anything to do with OTAs.
[Nexus 6  General] TokedUp:
Awfully quiet in here....
[Nexus 6  General] peter_g:
Project Fi: LVY48E to LVY48F ota

Can't post the link, but the file name is:

URL:

https:// android.googleapis.com/ packages/ ota/ google_shamu_shamu/

2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
[Nexus 6  General] TokedUp:
SO how can I get the OTA file from that URL?
[Nexus 6  General] xdatastic:
Here ya go:

https://android.googleapis.com/pack....signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
[Nexus 6  General] edwaine:
This is for global right?
[Nexus 6  General] xdatastic:
Yes
[Nexus 6  General] bluh5d:
I keep getting error in Side Load Package
[Nexus 6  General] xdatastic:
There's a thread for that:

http://xdaforums.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
[Nexus 6  General] Str8gahbidge:
Just got this ota notification. I'm already running build in pic...any what build it is? I'm rooted so will push the images manually so I can keep root once I can get a downloaded img
[Nexus 6  General] bigtimejdub:
LMY48M?

---------- Post added at 05:20 PM ---------- Previous post was at 05:20 PM ----------

I see that version on the Google Factory Images page, but doesn't say what it applies to.
[Nexus 6  General] Str8gahbidge:
Yes that's it
[Nexus 6  General] birnard:
Ditto on OTA notice today

I'm running LMY48I which is the build listed as current for device on Sprint on this thread, so I'm wondering what this new OTA fixes. It appears to be still 5.1.1 so might just be bug fix.

New build is I think, LMY48M. Any idea how important the fixes are? I'm rooted so I cannot just install the OTA, I'll have to flash factory images. Thanks.
[Nexus 6  General] boomerbubba:
This is Google's security OTA. They are now being issued monthly.
[Nexus 6  General] Onlyunless:
https://android.googleapis.com/pack....signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip

New OTA on my Project Fi Nexus 6.

Edit: Noticed peter_g got it here before me. Just didn't realize since the first post wasn't updated.
[Nexus 6  General] HankStorm:
Just got a notification for an update on Verizon. I am on LMY48I right now. I am not unlocked or rooted. Is there a way for me to get the download link if it's still needed?
[Nexus 6  General] xdatastic:
Enable Developer Options, take bug report and send to yourself. Then search the bug report for the link ending in .zip
[Nexus 6  General] HankStorm:
Well that sounds easy enough except that the "Take bug report" item in Developer Options is disabled.
[Nexus 6  General] xdatastic:
Sorry, Enable ADB Debugging and it should enable bug reporting
[Nexus 6  General] HankStorm:
Same URL for Verizon

https://android.googleapis.com/pack....signed-shamu-LMY48M-from-LMY48I.4458964f.zip
[Nexus 6  General] oldblue910:
Thank you to [MENTION=869935]jj14[/MENTION], [MENTION=3953440]anonchalantsigh[/MENTION], and [MENTION=2828095]Onlyunless[/MENTION] for the links. The first post has been updated!
[Nexus 6  General] caecusscius:
I tried going from LMY48I to M and it doesn't take... I used NRT to sideload it and it seems successful but afterwards I'm still on LMY48I and the OTA keeps coming back.
[Nexus 6  General] ggrx3:
Same here
[Nexus 6  General] titancow:
I tried sideloading the Verizon OTA LMY48M-from-LMY48I.4458964f.zip in TWRP and I keep getting an "error executing updater binary in zip" message, any suggestions? This is after flashing the stock LMY48I system.img in fastboot. Does the boot.img need to be flashed as well?
[Nexus 6  General] jlvlawrence:
You need to be completely stock to sideload an OTA.
[Nexus 6  General] oldblue910:
Marshmallow OTAs are rolling out. If anyone gets MRA58K appears to be the worldwide OTA. At this stage, we have no indication as to whether or not there will be a T-Mobile- or Project Fi-specific build. We'll need OTAs from LMY48M, LYZ28K, and LVY48F. Please post URLs here when you get them!
[Nexus 6  General] TokedUp:
Can't wait! Gonna be F5 this thread all day
[Nexus 6  General] DA6030:
Looks to me like there are five (LMY48T, LYZ28M, LVY48H, LMY48W, MRA58K) new builds rolling out today, so there could be many new OTA permutations.

I would assume some carriers have not yet greenlit Marshmallow (due to new radios, or any number of reasons), and so are going to get Stagefright 2.0 security patches before getting upgraded to Marshmallow.
[Nexus 6  General] oldblue910:
You're right. These are probably step OTAs to get them ready for Marshmallow. This actually gives me hope that MRA58K might be a unified build for all regions and carriers.
[Nexus 6  General] oldblue910:
Okay guys, we've got a BUNCH of OTAs we're going to need:

LYZ28K -> LYZ28M (T-Mobile USA)

LVY48F -> LVY48H (Project Fi)

LMY48M -> LMY48T (International)

LMY48M -> LMY48W (Possibly a region-specific OTA, Oceania perhaps)

LYZ28M -> MRA58K (T-Mobile USA)

LVY48H -> MRA58K (Project Fi)

LMY48T -> MRA58K (International)

LMY48W -> MRA58K (Possibly region-specific)
[Nexus 6  General] DA6030:
Yea, totally agreed. What puzzles me is that even some non-mobile devices (e.g., volantis) got multiple builds today, where carrier testing clearly doesn't apply. My only other hypothesis is that Google's new "monthly security patches" policy applies to older versions of the OS as well (in the same way CyanogenMod is still building CM11 snapshots for big security patches, even for devices with a stable CM12.1) - I suppose if LMY48T includes the new "Security Patch Level" menu item in Settings->About that will be a tip-off.
[Nexus 6  General] boomerbubba:
I think the 5.1.1 builds have got to involve the October security updates for each of the three Lollipop forks. The curious thing is that there are four, not three. Maybe after the security patches are applied, the next OTA would be to a unified 51.1. build, followed by a single OTA from that to MRA58K?
[Nexus 6  General] seshaz:
Works fine on my project fi with WiFi calling and all
[Nexus 6  General] seshaz:
Project fi Android m
[Nexus 6  General] seshaz:
Just flashed the image from Google and all is good in this world
[Nexus 6  General] jcsww:
T-Mobile's Marshmellow OTA will be available in the next week, according to this article.
[Nexus 6  General] oldblue910:
Did you get the OTA or did you do a factory image?
[Nexus 6  General] seshaz:
Factory image from today
[Nexus 6  General] boomerbubba:
Meanwhile, the official OTA path at Project Fi is going one step at a time. Today they announced that they are pushing out an interim security update for Lollipop.

https://productforums.google.com/forum/#!topic/project-fi/I2Gd-TtAxzA;context-place=forum/project-fi
[Nexus 6  General] oldblue910:
Yep. LVY48H. That will be the build that gets updated to Marshmallow.
[Nexus 6  General] TokedUp:
oh great now I gotta wait even longer for 6.0.
[Nexus 6  General] seshaz:
Don't see why you'd need to wait the image available today works fine. Have not found a single thing not working with project FI
[Nexus 6  General] boomerbubba:
T-Mobile's support page makes it look like their OTA will jump straight to MRA58K from LYZ28K. Which implies that they would skip LYZ28M? Or maybe they would just queue up two updates sequentially?
[Nexus 6  General] oldblue910:
I guess we'll find out as soon as someone on LYZ28K and a T-Mobile SIM card gets the OTA notification on their phone.
[Nexus 6  General] westers035:
How long do the OTA's usually take once the images are released?
[Nexus 6  General] oldblue910:
Because there are a lot of people, myself included, who have zero interest in root and unlocked bootloaders. In order for those people to flash images, they'd have to unlock their bootloaders (which seriously lessens security on a device) and lose all their data. For a lot of people, an update just isn't that important. And for those people, this thread exists so we can catalog OTA updates.
[Nexus 6  General] oldblue910:
It really depends. The rollouts are staged, so some people get the OTA the same day that the factory images go out, others won't get it for a few weeks. That's why this thread exists. The minute someone gets the OTA file, we can all sideload it manually.
[Nexus 6  General] AuroEdge:
Usually between a couple of days and a few weeks afterwards. I received the first OTA for the Verizon branded Nexus 6 a week after the first Verizon OTA was sent out.
[Nexus 6  General] fiergna:
found the security patch

https://android.googleapis.com/pack...397fd39fa.signed-shamu-LMY48T-from-LMY48M.zip
[Nexus 6  General] boomerbubba:
Thanks. It looks like that page you linked to at droicsec.org lists all three security patches, one for each of the Lollipop forks.
[Nexus 6  General] oldblue910:
Okay guys, I've added the three security OTAs that droidsec.org provided. Thanks to all who sent that link in. As of now, we're still in need of five OTA URLs:

LMY48M -> LMY48W

LMY48T -> MRA58K

LMY48W -> MRA58K

LVY48H -> MRA58K

LYZ28M -> MRA58K

If anyone gets these URLs, please post them here!
[Nexus 6  General] DA6030:
Verizon

Verizon has updated their software updates page to reflect an OTA approved October 5

Nexus 6 last updated 10/05/2015

Nexus 7 last updated 10/05/2015

Changelog for Nexus 6 update:

Android security patches

Kudos to them for greenlighting either LMY48T or LMY48W on release day, although sounds like they are holding back Marshmallow for the time being.
[Nexus 6  General] oldblue910:
For them, that probably means the N7 LTE will get LMY48U and the Nexus 6 will get LMY48W.
[Nexus 6  General] boomerbubba:
How do we know for sure that those are the OTA paths? What we have been told is that the builds are supposed to end up unified in Marshmallow, presumably on MRA58K. There are three forks in Lollipop, and we think we have the security update for each of them.

The odd duck is LMY48W, whose prefix suggests that it is the next step in the fork of the main Nexus builds. But why does this build exist?

Perhaps the path will be to unify each of the three forks first within Lollipop on LMY48W, then update LMY48W once to MRA58K.
[Nexus 6  General] oldblue910:
Okay so:

Yes, we have three forks in Lollipop.

We know International will be MRA58K. T-Mobile has also said on their support page that their build is MRA58K, so that eliminates two forks right there. There's no real reason to think that Project Fi will have its own Marshmallow build as it has to be a pain in the ass for Google to maintain so many different builds. It's possible that it might, but until that can be proven, I'm going to assume that Marshmallow is unifying everything into one build.

Yesterday, Verizon updated the Nexus 6 support page yesterday to announce a new "security update." This is, in all likelihood, the "odd duck" LMY48W build. Nexus 6s with Verizon SIMs will probably get this update while we wait out the carrier's approval process.

For further evidence that Verizon is getting its own build, let's jump to the Nexus 7 2013 for a minute. There was no October security update for the WiFi-only model. Instead it went straight from LMY48M (September security update) -> MRA58K. That said, the LTE model is a different story. There is an update straight from LMY48P (September security update) -> MRA58K, however there's also an odd duck build, LMY48U. There were only two US carriers who sold the N7 LTE. One is T-Mobile who, as with the Nexus 6, have said that their build is MRA58K. The second is Verizon, who updated their support docs yesterday to announce a new "security update." So, presumably, that LMY48U build on the Nexus 7 LTE is for Verizon.

That would mean that both Nexus devices that Verizon sanctions, the Nexus 7 LTE and Nexus 6, will be getting builds LMY48U and LMY48W, respecitively, while the Marshmallow approval process plays out. In the end, since we all know what ridiculous sticklers VZW are about updates, it makes sense that they'd be getting their own October Lollipop security builds separate from everyone else while Marshmallow goes under scrutiny. Sad, but true.