yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] casonswag:
im trying to flash the latest factory image with fasboot and it went through fine just when i boot up and try to login my account it sign in using one of the owners accounts for this device?? why it keep saying that the password is correct i cant get past this and get into the rom
[Nexus 6  General] NOSTALGIA:
let me ask you guys. the ota zip contains the extractable boot image right?? but the factory image is the full rom that u cant extract with winrar or winzip?? if you extract the full stock tar file it will just give you one file right??? so noob with these nexuses
[Nexus 6  General] xdatastic:
OTA contains the patch for each partition. The extracted contents are not of much use other than patching unmodified partitions.

The factory image contains a full image file for each partition. Boot, System, Userdata, Radio, etc etc.
[Nexus 6  General] NOSTALGIA:
so basically the ota contains the extractable boot.img,system,radio etc? and the factory image contains it in a whole tar file?

cant give more than 8 thanks per day... ill give u one once its gonna be available again
[Nexus 6  General] kapsama:
Hi I hope I'm not violating a rule by asking in this thread but I had a question.

I got my Nexus 6 in early 2015 rooted it and removed encryption and never updated from the LRX210 5.0 firmware.

I've been meaning to do a OTA update but they failed due to root. I did a factory reset from the stock recovery but it still failed.

I guess I have to do a manual update, but it seems there are a total of 8 updates for my T-Mobile Nexus 6.

My question is, do I need to flash each of those updates from LRX210 to LRX22C to LMY47M etc to MRA58N or can I skip a few along the way?

Thanks for any help.
[Nexus 6  General] xdatastic:
No, the OTA contains only partial images. They are not complete, just a Delta of the changes.

The factory one is a tar, which when fully extracted contains the individual images.

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

You need to flash the latest factory images to update. The OTAs won't work if you have modified any system files.
[Nexus 6  General] NOSTALGIA:
i was able to skip from 5.1 to 5.1.1 without following the sequence... just flashed it using wugs toolkit

---------- Post added at 07:59 AM ---------- Previous post was at 07:59 AM ----------

that was what i was trying to mean.

thank you so much
[Nexus 6  General] cammykool:
my dad took the november update on LP. LYZ28N anyone see a lyz28n to M ota zip?
[Nexus 6  General] oldblue910:
As of right now, we're missing six OTA links for the current cycle. Check the first post, and if you'd be willing to flash back to some of these builds to try and snag OTA links, it'd be greatly appreciated!
[Nexus 6  General] oldblue910:
Thanks to [MENTION=1912818]jrparker99[/MENTION], we now have the T-Mobile November security update, LMY48N from LMY48M. If y'all can help on any of the other missing OTAs in the first post, please do so!
[Nexus 6  General] oldblue910:
Can one of you who is running MRA58R (Verizon) tell me what the baseband and bootloader versions are?
[Nexus 6  General] xdatastic:
Same as MRA58N

71.15

22.05.27R
[Nexus 6  General] oldblue910:
Thanks!
[Nexus 6  General] TokedUp:
Articles linked on G+ suggest 6.0.1 is inbound pretty soon!
[Nexus 6  General] boomerbubba:
T-Mobile has finally cleared Marshmallow for release. But reportedly there is a new build, MRA58X, for that release.

As of this writing, MRA58X does not yet exist on Google's factory image page.
[Nexus 6  General] oldblue910:
Alright, y'all know the drill. Let's get some URLs!
[Nexus 6  General] DA6030:
T-Mobile's Des is reporting MRA58X, but the official support docs report MRA58K is dropping Nov 20. I suspect MRA58X might be Dec 1 security patch (and Des might already have that on his personal device), but if Des is the only primary source (everyone else is just quoting him) reporting this build, and no corresponding Nexus Factory image, I think we're just looking for MRA58K from LYZ28N.

https://support.t-mobile.com/docs/DOC-18109
[Nexus 6  General] BRKotucs:
Keeping a close eye on this one... https://plus.google.com/113661675996996733286/posts/bpWgjSrPXYP

EDIT
[Nexus 6  General] rasengan82:
Looks like the radio was updated.
[Nexus 6  General] oldblue910:
Hopefully we can get a URL soon!
[Nexus 6  General] Fresh50:
Buddy of mine just checked and received the update. He was not on marshmallow prior to installing update. Upgraded from lollipop to marshmallow.
[Nexus 6  General] MysticKing32:
Wonder why its not on the factory image page?
[Nexus 6  General] blueyes:
Why doesn't someone download the update, then copy it before updating. Have to be rooted but I did it on flo. Believe it went to data/local and was called update.zip. just a thought.

Official Team Bliss Flo, Deb, v400, v410, vk810, shamu-odexed Maintainer
[Nexus 6  General] oldblue910:
Yeah you'll likely need to be on LYZ28N to get the update as T-Mobile never officially approved MRA58K as far as I know.
[Nexus 6  General] jcsww:
I'd say, expect it sometime during the middle of next week. T-Mobile factory images seems to be some of the slowest to hit the factory image page.
[Nexus 6  General] xdatastic:
MRA58K was listed on T-Mobile site on 11th Oct 2015, but was removed shortly after. I happened to grab a screenshot at the time. Dunno if it ever OTA'd to their devices tho.
[Nexus 6  General] chrisram88:
Nice, new radio!
[Nexus 6  General] oldblue910:
So do I have a volunteer to flash back to LYZ28N and get a URL?
[Nexus 6  General] imkain:
Question

If I was to volunteer for this... How would I retrieve the OTA link, as I have never done this before.
[Nexus 6  General] oldblue910:
While the OTA is downloading, get the logcat using adb or do it by sending yourself a bug report via Developer Options. The URL is in there. You have to have a T-Mobile SIM and be on LYZ28N.
[Nexus 6  General] imkain:
Here is the Twitter response from T-Mobile

If you go to Des' Twitter feed he answered this question and basically stated something to the effect of...

If you are on MRA58K you will receive OTA MRA58X without an issue.

Best regards,

Stephen
[Nexus 6  General] oldblue910:
Okay. Thanks! So, we're going to need two OTAs then...LYZ28N > MRA58X and MRA58K > MRA58X
[Nexus 6  General] frontlyna:
Did you revert back to 5.1.1 to grab update?
[Nexus 6  General] oldblue910:
I would but I don't own a Nexus 6.
[Nexus 6  General] frontlyna:
What's the point of this post then?
[Nexus 6  General] nnorton44:
So will this be a newer build then MRA58R?
[Nexus 6  General] imkain:
This is T-Mobile's version that contains the fix for WiFi calling issues, and radio updates.
[Nexus 6  General] oldblue910:
MRA58N is international, MRA58R is for Verizon, and MRA58X is for T-Mobile.
[Nexus 6  General] nnorton44:
Hmm I had thought MRA58R was the latest with November security update, I'm running it on a T-Mobile SIM and have band 12, volte, wifi calling, etc.
[Nexus 6  General] oldblue910:
Yes, but that's because you flashed it manually. It'll work with all those features, but that build was only released to devices as an OTA if they had a Verizon SIM. All builds work with all carriers regardless.
[Nexus 6  General] nnorton44:
Thanks for the clarification!
[Nexus 6  General] drawde40599:
He said he thinks so but he was going to ask his tech team. AKA he didn't know ....

I seriously doubt there going to update from a marshmallow build they didn't support
[Nexus 6  General] imkain:
Hmm

Since the updates are controlled by Google...they don't have a choice...since the Nexus phone line up is controlled above all by Google and not by the carriers.
[Nexus 6  General] imkain:
Here is another message from T-Mobile

[MENTION=459599]DBT[/MENTION]othei 58K will update via OTA to 58X
[Nexus 6  General] BigDig:
58N will update to X also
[Nexus 6  General] ethanhunt123:
Do you mean immediately? or like... in the future the plan is to ota N to X
[Nexus 6  General] GilmourD3:
I hope cuz I just sideloaded from K to N. I'd like X. That sounds wrong... LOL
[Nexus 6  General] ethanhunt123:
So you currently have Fi on N? And you don't see an OTA?
[Nexus 6  General] GilmourD3:
Sorry for the confusion. I'm on an Amazon-purchased N6 on VZW.

OTAs took me up to LYA48T, then I got impatient and sideloaded K. Then R came out but I realized there was no path from K to R so I sideloaded N when that file popped up in this thread so I'm closer to current.
[Nexus 6  General] Xyth:
I'm currently on build N on my FI Nexus 6. I got it ota when I swaped sim cards to FI. No ota yet.
[Nexus 6  General] imkain:
Question...

Did you happen to get the OTA link?
[Nexus 6  General] BRKotucs:
No! This was someone else. It was posted on G+.

I will post the link here if I get the update.
[Nexus 6  General] imkain:
Ah...

Ah...okay...but I just read something that disturbs me...

Here is what T-Mobile states...which is stupid since it violates Google's Nexus phone update strategy.

Check the software version

To check the current software version, follow these steps:

From the Home screen, tap Settings.

Tap About phone.

View the Build number below.

Software version	Status

MRA58X

Your software is up to date. There are no updates available.

This document will be updated if and when new software is available.

LYZ28K

LYZ28J

LYZ28E

LRX22C

LRX210

LNX07M

Your phone can update to build number MRA58X:

Review the Requirements to update

Starting November 20, you may be prompted to update automatically (OTA).

To update now, see how to download the update below.

If the update fails, see: Software update troubleshooting.

Other versions

Your device has non-T-Mobile software, and it is unsupported. The manufacturer and T-Mobile cannot update your software.

Requirements to update

To be able to update to the current software version, the below requirements must be met:

LYZ28k

50% or higher battery life

Data connection

Available space (File size is 698 MB)
[Nexus 6  General] BRKotucs:
I know! I was just reading it too. Really odd.. Doesn't make any sense at all.
[Nexus 6  General] chrisram88:
Do you think it's due to band 12 and wifi calling? Since it's a tmo build only?
[Nexus 6  General] oldblue910:
The Nexus 6 already supports B12 and WiFi calling.
[Nexus 6  General] Winesnob:
Project Fi started pushing the same build yesterday. AFAIK the T-Mobile delay was primarily due to problems with WiFi calling.

Nexus 6 supports band 12, but the email from Fi stated that Marshmallow support for band 12 is not in this release, but will come "soon".
[Nexus 6  General] MysticKing32:
How come on the factory image page next to MRA58R it doesn't say Verizon? Like the lollipop builds did?
[Nexus 6  General] oldblue910:
Because someone forgot to add it. haha Those labels have been added after the fact in the past. But that doesn't change anything. No device in the world that we know of ever got MRA58R legitimately (meaning via OTA) unless it had a Verizon SIM in it. Everyone else got N or, in the case of T-Mobile, X. If you find a Nexus 6 that has MRA58R on it, it either had a Verizon SIM when it got the OTA, or it was flashed manually. Simple as that.
[Nexus 6  General] Drozd75:
I'm on Fi, and was on MRA58N.

I pulled my sim card and flashed back to LYZ28K to ensure I was on a T-Mobile specific build (trying to double down on getting MRA58X). Did a pre and post flash factory reset.

I got a series of OTAs in quick succession....

They went:

From LYZ28K> LYZ28M> MRA58K> MRA58N... And that's where it stopped, right where I started....
[Nexus 6  General] donnyp1:
I'm on LYZ28M, I'm curious to when it comes now
[Nexus 6  General] Tickie:
I'm on Fi, and was on LVY48I, never got an update at all from the release of MM. I flashed MRA58K yesterday and quickly got a OTA to MRA58N. This has been out for a while also. I wonder what the build number will be for Fi after getting an email the day before I flashed to 58K saying they just started OTA for MM. Crazy here is the comments I am speaking of.

https://productforums.google.com/forum/#!topic/project-fi/X2RbiNRNtDY ( Note the day of posting. )
[Nexus 6  General] depassp:
MRA58X from LVY48I

FINALLY got my Nexus 6 on Project Fi to update to MRA58X by first flashing LVY48I.

Here's the OTA link:

https://android.googleapis.com/pack...ed-shamu-MRA58X-from-LVY48I-new-timestamp.zip
[Nexus 6  General] Winesnob:
If you're on Fi, why did you roll back to a T-Mo build?
[Nexus 6  General] pandacookie:
Hi. What can be done with this zip?
[Nexus 6  General] oldblue910:
We still need a few OTAs. Would someone on Project Fi mind flashing back to LVY48H and trying to snag the URL for the LVY48I OTA? Also, if someone on Sprint could try flashing back to LMY48T and seeing if you get an OTA to LMY48X, that would be awesome too. Need to get these URLs before the Marshmallow flood gates are open wide
[Nexus 6  General] Tickie:
LVY48I is a Project Fi build.
[Nexus 6  General] Winesnob:
Use the adb sideload function in stock recovery to update from LVY48I to MRA58X. Or you can wait for OTA to deliver itself normally.

---------- Post added at 11:06 AM ---------- Previous post was at 11:06 AM ----------

Right. And...
[Nexus 6  General] RobertoIsRad:
Nice! Thank you, I'm flashing it right now
[Nexus 6  General] pandacookie:
Figured it out! Thank you.

Believe it or not, in all the time I've used and tinkered with these phones, I've never used ADB sideload. You know what they say about learning something new every day. :)
[Nexus 6  General] xdatastic:
Please could you post the contents of build.prop of mra58x?
[Nexus 6  General] oldblue910:
Thank you! First post updated! Can someone PLEASE flash back to LMY48H and get an OTA to LMY48I so we can have the URL for that? Our time to get that is running short.
[Nexus 6  General] depassp:
I sat at LMY48HH for a long time but it never came. Instead I got updated to MRA58N
[Nexus 6  General] oldblue910:
Are you on Project Fi?
[Nexus 6  General] depassp:
Yes I am on Project Fi. Apparently T-Mobile is getting MRA58X too but from LYZ28K (source: https://support.t-mobile.com/docs/DOC-18109).
[Nexus 6  General] frontlyna:
Is the radio image inside the modem.patch folder, and then if I take out the modem.patch and rename to modem.img can I flash with adb?
[Nexus 6  General] xdatastic:
Highly unlikely. It is most probably just a patch file. I'd wait til Google publishes the images tomorrow.
[Nexus 6  General] nnorton44:
I got MRA58X by flashing LVY48I then sideloading the MRA58X from LVY48I OTA :good:
[Nexus 6  General] TokedUp:
So X is safe to sideload on ProFi?
[Nexus 6  General] nnorton44:
I'm on T-Mobile but didn't have any trouble sideloading it over the ProFi firmware.
[Nexus 6  General] TokedUp:
uh oh what happened [MENTION=3209971]cam30era[/MENTION]?
[Nexus 6  General] goochbun2:
well i downloaded LVY48I and used wug till it was done with the recovery push. then after that booted to recovery and sideload adb this file and bam thanks guys
[Nexus 6  General] najoor:
Can someone with a rooted t mobile branded nexus 6 share the contents of the /oem directory please?
[Nexus 6  General] Tickie:
Thanks, I used NRT to load factory LVY48I, then sideloaded ... worked like a champ... thanks for the link!:good::good:
[Nexus 6  General] TokedUp:
My problem is I'm on the MRA58N build so I can't use that X OTA link. Or can I? Do I have to be on 48I?
[Nexus 6  General] nnorton44:
I think you have to downgrade to 48I and then sideload the OTA. This will require a factory reset, I didn't mind because my device is backed up and it redownloaded all my apps as soon as I put in my Google account info.

May be a different process with wug or NRT.
[Nexus 6  General] jchl97:
I have an unlocked version flashed to MRA58K, only after which did I start using Fi. When I saw the OTA from 58K to 58N I sideloaded that. I guess I won't be updated to 58X in this case. I'll just wait for the 6.0.1 and Dec. security updates.
[Nexus 6  General] SamsungAdmire:
So is this the ota for ProFi or TMobile, or is it for both?

Can I flash this from MRA58N?
[Nexus 6  General] lainemac:
There is no OTA(at the moment) to go from the D build to the M build.
[Nexus 6  General] oldblue910:
And there may not be one, as devices were never intended to go officially from D to M. No device with a T-Mobile USA SIM card was ever offered the LMY47D OTA, so the assumption is that everyone OTAing should be doing so from LRX22C or LRX21O. Google might be nice and sneak out an LMY47D > LMY47M OTA, but don't bank on it.
[Nexus 6  General] TheSopranos16:
I'm on Verizon and the D build. From Reading this thread, there is no upgrade path to E or M? Those of us on D are stuck for the moment.

And since I'm completely stock locked and unrooted, I can't flash the full image without losing all my data right?
[Nexus 6  General] VivaErBetis:
At least an OTA from E to M is confirmed:

https://mobile.twitter.com/TMobileHelp/status/579035245871292416

But nothing about D to M...

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

Yes, in your situation data loss is inevitable.
[Nexus 6  General] x_x1_x:
Is the OTA zip file comes officially from google? Where can I find it?

In google developer site, I can download Factory Image only!!
[Nexus 6  General] oldblue910:
T-Mobile is wrong. The only devices that ever saw E were ones that were sold new from Verizon. Plus, E has a newer radio (.98) than the one with D and M (.95). There's no reason for an E > M OTA to exist.
[Nexus 6  General] oldblue910:
So, now I'm starting to wonder if maybe there WILL be an update to LMY47E for existing devices with Verizon SIM cards. I did some playing around this morning with D, E, and M and I think I found out why E (Verizon's build) has a newer radio than the one D and M use. Apparently the .95 radio that comes with D and M doesn't properly recognize VoLTE on Verizon. Neither of those ROMs gave me the ability to enable "Enhanced 4G LTE Mode," but as soon as I flashed the E build with the newer .98 radio, it worked fine. So...that's a pretty major feature for 5.1 and because of that, I'd now be surprised if we don't see all devices with Verizon SIM's updated to LMY47E soon.

If anyone has a Nexus 6 that was NOT purchased from Verizon but has a Verizon SIM in it, please keep your device on 5.0.1 for the next week or so if you can and see if you get an OTA to 5.1/LMY47E. If you do, please get the filename before you update. Likewise, if anyone has an unlocked bootloader and wouldn't mind flashing back to LRX22C for a bit and waiting for an update, that'd be cool too.

Thanks!
[Nexus 6  General] mwalt2:
VoLTE worked fine for me on D using Verizon. You definitely don't need E to have it work on Verizon.
[Nexus 6  General] VivaErBetis:
Or, if you are rooted, just follow the instructions of this post:

http://xdaforums.com/nexus-6/general/to-ota-filename-installed-ota-to-lmy47m-t3059902

Following these instructions It's not necessary to reflash or to stay in LRX22C while you are using a newer version. Just change build.prop to LRX22C data, as shown in the instructions, and wait for the OTA (you can leave build.prop changed to LRX22C all the time that you want cause it doesn't affects any other apps, AFAIK).
[Nexus 6  General] oldblue910:
Weird. I couldn't get it to work on D or M no matter what I did.
[Nexus 6  General] bloodiedwraith:
Yeah same here - Motorola purchased Nexus 6 on VZW with D and can use VoLTE and simultaneous talk/data no problems whatsoever. I wonder if VZW will push out LMY47E to those of us who sideloaded the LMY47D OTA.

I haven't had a need to root the Nexus 6 (and I've rooted everything I've owned from the Motorola Droid and on) and I don't really feel like having to unlock the bootloader and flash the LMY47E image if I don't have to.
[Nexus 6  General] oldblue910:
Yeah I stand corrected.
[Nexus 6  General] x_x1_x:
No Answer?
[Nexus 6  General] xdatastic:
See the very first post of this thread. All the OTAs come from Google.
[Nexus 6  General] xdatastic:
[MENTION=3423169]oldblue910[/MENTION] FYI there is build LMY47I rolling out to Australian Nexus 6 right now. Another build to confuse everyone :)

I don't yet have the OTA URL, but here is the build.prop for a user who received it:

#

PRODUCT_OEM_PROPERTIES

#

import /oem/oem.prop ro.config.ringtone

import /oem/oem.prop ro.config.notification_sound

import /oem/oem.prop ro.config.alarm_alert

import /oem/oem.prop ro.config.wallpaper

import /oem/oem.prop ro.config.wallpaper_component

import /oem/oem.prop ro.oem.*

import /oem/oem.prop oem.*

begin build properties

autogenerated by buildinfo.sh

ro.build.id=LMY47I

ro.build.display.id=LMY47I

ro.build.version.incremental=1767468

ro.build.version.sdk=22

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=5.1

ro.build.date=Wed Mar 4 04:20:25 UTC 2015

ro.build.date.utc=1425442825

ro.build.type=user

ro.build.user=android-build

ro.build.host=vpak24.mtv.corp.google.com

ro.build.tags=release-keys

ro.build.flavor=shamu-user

ro.product.model=Nexus 6

ro.product.brand=google

ro.product.name=shamu

ro.product.device=shamu

ro.product.board=shamu

ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

use ro.product.cpu.abilist instead.

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.cpu.abilist=armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.product.manufacturer=motorola

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=msm8084

ro.build.product is obsolete; use ro.product.device

ro.build.product=shamu

Do not try to parse description, fingerprint, or thumbprint

ro.build.description=shamu-user 5.1 LMY47I 1767468 release-keys

ro.build.fingerprint=google/shamu/shamu:5.1/LMY47I/1767468:user/release-keys

ro.build.characteristics=nosdcard

end build properties
[Nexus 6  General] VivaErBetis:
The party never ends, uh!
[Nexus 6  General] xdatastic:
The radio version for LMY47I is

MDM9625_104446.01.02.95R
[Nexus 6  General] VivaErBetis:
Bootloader? 71.08?

Thank you.
[Nexus 6  General] xdatastic:
Sorry, not sure. I imagine it will be same as all the other LMY47 builds. Will check later.
[Nexus 6  General] About20ninj45:
I'm on lmy47d and I can use voice and data just fine even simultaneously. I'm on a corporate line, non vzw device
[Nexus 6  General] renny083:
MRA58X from LYZ28N (T-Mobile)

Here is the ota zip for T-mobile Only.

MRA58X from LYZ28N ota link is here https://android.googleapis.com/packages/ota/google_shamu_shamu/78b3a4779b678ec64638db3568d72b1de33bd63a.signed-shamu-MRA58X-from-LYZ28N-new-timestamp.zip

*In order to side load this ota successfully, you must be on the LYZ28N factory image.
[Nexus 6  General] oldblue910:
As a reminder, there are still two URLs in the first post that we don't have yet. If you can help, please do!
[Nexus 6  General] TokedUp:
So I guess I have to wait for an OTA file that's MRA58N to X or whatever the file path from N will be on Fi
[Nexus 6  General] WhammyDroid:
Me too though I am hoping the system images get posted.
[Nexus 6  General] SmartBrother90:
i flashed stock LYZ28N boot, recovery, radio and system image. when i try sideloading the update, i keep getting this error EMMC:/dev/block/platform/msm_sdcc . 1/by-name/modem unexpected content
[Nexus 6  General] imkain:
Hey

This will not work if you are already on Marshmallow. I attempted it already and it gave me the error that the fingerprint did not match what was required. No worries. I will just wait for the new Developer image to come out...or a real OTA that will update Marshmallow to Marshmallow T-Mobile edition ;). Also keep your eyes peeled, 6.0.1 has been seen in the wild as of this morning.

http://www.androidauthority.com/android-6-0-1-is-landing-on-some-android-one-devices-657099/

Check it out.
[Nexus 6  General] depassp:
You cannot flash this from MRA58N. It's from LVY48I, which, according to google's nexus images ( https://developers.google.com/android/nexus/images?hl=en#shamu ) is Project Fi only

It's my understanding than in marshmallow, the builds are supposed to be unified (no more carrier-specific) so I expect the end result of this upgrade will look the same as T-Mobile's MRA58X. Just the upgrade path is unique to ProFi