I know there are several different build versions for the 5.1 stock ROM:
(Sorry, can't post links yet) Factory Images on the Google Developers page; Nexus 6 builds on Pocketables
I've read and experienced conflicting reports regarding these versions. Apparently, you can flash any of these versions and your phone should work, although one version has the 98 radio and others have the 95...?
My phone was flashed and rooted with the LMY47I version, which I've read other people have no issue with. However, the existence of this "Backup" app (version 5.1 -eng.a21406.20150205.164937), other default differences (background, Fit app), and issues with Wi-Fi and cell service, all when compared to when I originally pulled it out of the box several months ago, makes me think that I somehow flashed a Verizon stock ROM instead of a Sprint one.
According to that second page:
AT&T -> LMY47D
Sprint -> LMY47D
T-Mobile -> LMY47M
Verizon -> LMY47E
Intl. -> LMY47D OR LMY47I
(Does anyone know what build version the Nexus 6 comes with if you get one through Project Fi?)
Can anyone confirm any of this? Should I re-flash with LMY47D?
chester_malone said:
I know there are several different build versions for the 5.1 stock ROM:
(Sorry, can't post links yet) Factory Images on the Google Developers page; Nexus 6 builds on Pocketables
I've read and experienced conflicting reports regarding these versions. Apparently, you can flash any of these versions and your phone should work, although one version has the 98 radio and others have the 95...?
My phone was flashed and rooted with the LMY47I version, which I've read other people have no issue with. However, the existence of this "Backup" app (version 5.1 -eng.a21406.20150205.164937), other default differences (background, Fit app), and issues with Wi-Fi and cell service, all when compared to when I originally pulled it out of the box several months ago, makes me think that I somehow flashed a Verizon stock ROM instead of a Sprint one.
According to that second page:
AT&T -> LMY47D
Sprint -> LMY47D
T-Mobile -> LMY47M
Verizon -> LMY47E
Intl. -> LMY47D OR LMY47I
(Does anyone know what build version the Nexus 6 comes with if you get one through Project Fi?)
Can anyone confirm any of this? Should I re-flash with LMY47D?
Click to expand...
Click to collapse
The backup app is included in all 5.1 builds. Just like SprintDM is included in all. I'm Sprint, on the I build and everything is fine. Have you ever used the Sprint data dialer reset code? Also, this update I received yesterday from Play Store helped a lot of my WiFi issues:
https://play.google.com/store/apps/details?id=com.google.android.apps.gcs
I would like to know as well as I am about to by one.
I can get from google play or Motorola or should I wait till I get a Fi invite to order that way?
Evolution_Freak said:
The backup app is included in all 5.1 builds. Just like SprintDM is included in all. I'm Sprint, on the I build and everything is fine. Have you ever used the Sprint data dialer reset code? Also, this update I received yesterday from Play Store helped a lot of my WiFi issues:
Click to expand...
Click to collapse
Hmm. That came preinstalled in my stock ROM. I notice that my Wi-Fi will not successfully automatically reconnect to a saved WAP. When I go to work, and when I come home. The status shows as "Authentication Issues". If I tap on it and connect, then it connects and remains. I had this same issue when I was running CM12.
I've flashed (fastboot) LMY47I a month or so ago on Sprint Shamu and all has been perfecto.
Shamu-unofficial Tesla rom-Hells Core-b3 kernel
Related
Hey all,
So I purchased a Nexus 6 from the playstore when it first was announced and had been using it on TMo's network. On Monday I received my Fi welcome package and sim card and ported my number over and began using project FI. For the most part everything has worked as it should. Today I got a system update notification. I thought I could then flash the 5.1.1 (For Project Fi ONLY) (LVY48C) files but once I did that my phone had a litany of errors stating that processes were not responding & had suddenly stopped. I knew that phones purchased from FI came with a different firmware, but I had assumed that since i was not using FI, I could flash over the same ones that came pre-shipped on those FI Nexus 6s. I was previously on LYZ28E for T-mobile. So, I am manually flashing back to LYZ28E as I type this (rebooted the bootloader and the phone is optimizing all of my apps). Should I then flash the new update, LYZ28J, for T-mo? I was under the assumption that since I had switched to Fi, I could flash that image but I was clearly mistaken. So just trying to figure out which files to flash moving forward.
I appreciate the help in advance!
AceKingNYC said:
Hey all,
So I purchased a Nexus 6 from the playstore when it first was announced and had been using it on TMo's network. On Monday I received my Fi welcome package and sim card and ported my number over and began using project FI. For the most part everything has worked as it should. Today I got a system update notification. I thought I could then flash the 5.1.1 (For Project Fi ONLY) (LVY48C) files but once I did that my phone had a litany of errors stating that processes were not responding & had suddenly stopped. I knew that phones purchased from FI came with a different firmware, but I had assumed that since i was not using FI, I could flash over the same ones that came pre-shipped on those FI Nexus 6s. I was previously on LYZ28E for T-mobile. So, I am manually flashing back to LYZ28E as I type this (rebooted the bootloader and the phone is optimizing all of my apps). Should I then flash the new update, LYZ28J, for T-mo? I was under the assumption that since I had switched to Fi, I could flash that image but I was clearly mistaken. So just trying to figure out which files to flash moving forward.
I appreciate the help in advance!
Click to expand...
Click to collapse
since you had a fi sim in your phone at the time, you were sent the right update. the update isnt determined by where you bought your phone, it is determined by what sim card you have in your phone. anyways, you probable recieved the update to fix the stagefright bug.
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
anyways, i sounds like your update just went bad, that happens, and often enought. reupdating usually fixes it(or flashing the factory image). flash LVY48C.
simms22 said:
since you had a fi sim in your phone at the time, you were sent the right update. the update isnt determined by where you bought your phone, it is determined by what sim card you have in your phone. anyways, you probable recieved the update to fix the stagefright bug.
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
anyways, i sounds like your update just went bad, that happens, and often enought. reupdating usually fixes it(or flashing the factory image). flash LVY48C.
Click to expand...
Click to collapse
Makes sense now that you put it that way. But, sInce I now have a notification for an update, just a bit confused as to what I now have to download and flash to get the latest OTA and notification off my phone
AceKingNYC said:
Makes sense now that you put it that way. But, sInce I now have a notification for an update, just a bit confused as to what I now have to download and flash to get the latest OTA and notification off my phone
Click to expand...
Click to collapse
thats probably the update to fix stagefright. i dont see a fi factory image for thst up yet. theres a tmo version up, and a generic version up.
simms22 said:
thats probably the update to fix stagefright. i dont see a fi factory image for thst up yet. theres a tmo version up, and a generic version up.
Click to expand...
Click to collapse
it wouldnt be 5.1.1 (For Project Fi ONLY) (LVY48E) ? i appreciate your help with this btw
AceKingNYC said:
it wouldnt be 5.1.1 (For Project Fi ONLY) (LVY48E) ? i appreciate your help with this btw
Click to expand...
Click to collapse
it is. it wasnt up their when i checked earlier, but it is there now
simms22 said:
it is. it wasnt up their when i checked earlier, but it is there now
Click to expand...
Click to collapse
you know google is a sneaky mofo
so just so im clear on this and don't flash the wrong damn image again lol. I am currently on 5.1.1 (For T-Mobile ONLY) (LYZ28E) - but using a FI sim card...i should flash 5.1.1 (For Project Fi ONLY) (LVY48E) OR 5.1.1 (For T-Mobile ONLY) (LYZ28J)?? WHen i check my firmware version it states LYZ28E
and where in BK you from? I'm on the other side of the Williamsburg bridge, Lower East Side area!
AceKingNYC said:
you know google is a sneaky mofo
so just so im clear on this and don't flash the wrong damn image again lol. I am currently on 5.1.1 (For T-Mobile ONLY) (LYZ28E) - but using a FI sim card...i should flash 5.1.1 (For Project Fi ONLY) (LVY48E) OR 5.1.1 (For T-Mobile ONLY) (LYZ28J)?? WHen i check my firmware version it states LYZ28E
and where in BK you from? I'm on the other side of the Williamsburg bridge, Lower East Side area!
Click to expand...
Click to collapse
it doesnt matter what you are on now, when flashing a factory image. it will clear your partitions as it flashes them again. you have the fi simcard, you want to flash for fi only LVY48EE.
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
None as of now.
Downloads:
Current version
Custom rom with new build.prop by yahya1054:
Download
AGISCI said:
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
Some people are experiencing an issue where it says they are roaming.
Downloads:
Main download
Mirror 1
Click to expand...
Click to collapse
What the difference between this rom and 1095 MM Rom
kaktusmaier125 said:
What the difference between this rom and 1095 MM Rom
Click to expand...
Click to collapse
This one has support for verizon cdma. It is only useful for people who use verizon service.
Sent from my XT1095 using Tapatalk
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
donslade said:
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
Click to expand...
Click to collapse
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Thanks for the update. I had notice that it did say retla in the system version. Need to pay attention to the baseband info.. Based on that I don't need to upload the About Phone screens then.
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
RamAir02 said:
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
It's a stock rom, gapps are in it already.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
has this new version been uploaded yet?
Legacystar said:
has this new version been uploaded yet?
Click to expand...
Click to collapse
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
AGISCI said:
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
awesome, thank you. any idea what he did to fix the roaming issue?
Legacystar said:
awesome, thank you. any idea what he did to fix the roaming issue?
Click to expand...
Click to collapse
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
AGISCI said:
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
might have been the verizon apn app
Alright, sorry for the long delay. My internet is messed up right now. I started the upload last night and left it running. I woke up to a failed upload message. I started it again and it took 5 hours to upload... anyway, I have updated the first post with the link to the new version. Please try it out and let us know if you have issues with roaming still.
I have had the roaming issue since I installed the original MM posted a few days ago but even though the R is showing by 4g it still allows me to access data through 4g. Hope I am not going to incur the financial wrath of big red. lol. I was reading this forum using it. Anyway, I want to say thanks for those putting in the work to try and figure this out and support a stock MM rom for the xt1096. I will test the new version as soon as I get it downloaded and report back if the roaming issue persists for me.
I have updated to the latest version of stock MM offered on first post and can confirm that the R roaming symbol is gone. I have rebooted several times and finished setting my phone up how I want it. The only issue I had during the process of installing and setting up this version of MM is that upon rebooting the first 2 times I had a pop up saying "Unfortunately, Verizon Login has stopped."
I rebooted into twrp and installed reinstalled the root and su zips and upon reboot the pop up went away. I guess I was wrong to assume that the order for installing the zips were 1)root boot for 1095, 2)Super SU and 3) MM Rom. After reading that in order it makes more sense to load the Rom then the root and su zips. Oh well, all is well that ends well.
Has anyone figured out how to bypass the wifi setup screen during setup?
Wrong forum.
i just loaded the new version and still getting the roaming. also having the verizon app crash on startup.
To skip WiFi setup, put sim card in on welcome screen so after boot put sim,
also roaming is gone for me but I just get data, no voice on some reboots voice aval even when it says out of service same last build.
Roaming was an issue older build new build fixed, voice still wonky for me
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Klownicle said:
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Click to expand...
Click to collapse
I don't know of any reason why you can't just download the NBD91P image from here and flash each partition manually from the bootloader using fastboot, or download the NBD91P OTA image from here and flash it following the instructions on that page. I haven't heard or read anything at all that the stock factory image won't work on a T-Mobile Nexus 6.
Edit: If you haven't manually flashed an image before I have always used the instructions under "Method 2 : (Long, but works always)" on this page.
I would just load the OTA. There isn't any issues with it on t-mobile. was running the stock ROM for awhile. Now testing out CM14.1
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
ozzmanj1 said:
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Dopemusic89 said:
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Click to expand...
Click to collapse
I've never had any issues. My wife and nephew and older brother all have nexus 6 phones with nitro installed and have had zero issues on Tmo. Off hand have you checked your APN settings? Have you tried a fresh clean install? When I do a clean install I go and wipe, data, system, cache, etc, but leave internal storage alone. I know it gets wiped on install but I do it anyways to be sure. Other then checking APN settings and or fresh install I am stumped why anyone should be having issues. Sorry I can't give more insight. I guess the other issue could be your radio ....May want to look into flashing a different radio to see how it fares
Edit -. Link for flashable radios
http://forum.xda-developers.com/showthread.php?t=3066052
Hope any of these suggestions help
Sent from my Nexus 6 using XDA-Developers mobile app
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Note10.1Dude said:
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Click to expand...
Click to collapse
What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.
voyageurs60 said:
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Click to expand...
Click to collapse
I just posted this same response in a separate, but similar thread.
It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.
I have build number NBD92G. No issues for me; I took it as an OTA. It has baseband MDM9625_104670.31.05.42R. T-mo did not push a May security update that I am aware of; I hope that indicates they are trying to validate a 7.1.1.
So, T-mobile is still on 92G for the last 3 months without security update. With the rumors of 7.1 being pushed again, anybody seeing anything? We will be EOL in October for security updates, and I plan to side-load the final one if T-mobile doesn't push it, but I do think they should be doing their job and letting our phones take the latest updates.
My Nexus 6 received 7.0 update notification and I would like to wait for 7.1 to upgrade together. But yesterday the 7.0 notification suddenly gone, I've manually check the update but the system said my phone already get the latest update. Then I've checked the version of my Nexus 6, it is MOB31H, I don't remember whether I have the November update. Now I have few questions and hope someone can help me.
1. Why the 7.0 update notification suddenly gone?
2. I've checked the Full OTA images, the Nov update contains MMB31C and MOB31K, If I would like to manually apply the update, which one should I use? (My Nexus 6 is international version XT1103)
3. If i manually apply the the Full OTA Images on Nov update by adb sideload, will all the data being erased and need to re-config and reinstall all apps?
Thanks so much in advance for your help.
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Strephon Alkhalikoi said:
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Click to expand...
Click to collapse
Thanks so much for your help, I think I mis-type the model, XT1100 international should be correct.
I've just sideloaded the version MOB31K successfully and will wait for the 7.1 fix on the speaker phone echo problem before upgrade to 7.1.
Please don't mind to ask one more question, i guess the MMB31C and MOB31K is for US and International model respectively. On version Nougat, no different on XT1103 and XT1100, one version for both model?
Thanks so much again for your help.
Or you could sideload NBD91X, which is Nougat without the speakerphone problem.
@mega23mac: MMB31C is for CDMA devices in the US, if I recall correctly. As @dahawthorne points out, you could install a 7.0 OTA, but if you don't need the speakerphone, the 7.1 OTA works just fine. Google should have it patched for next month's security update.
My T-Mobile Nexus 6 still has 6.0.1 and I am not looking to upgrade to Nougat 7.xxx. What I am trying to do is install the security updates. The last OTA was from November 5, 2016. Why is T-Mobile not sending these out? Do I have to root my phone to download and install? Help would be appreciated. Thanks Dan
Strange. I had a 6.0.1 February security update from T-mobile. I got the 7.0 update with the March patch earlier this month, which was probably the end of the 6.0.1 patches. You can sideload the February patch from the OTA site, but don't expect any more.
Ota 7.1.1 havoc with Radios.
I finally attempted to sideload 7.1.1 N6F26U - cell data has been horrible. I am on T-Mobile. What 7.0 or 6.0.1 I think has the most security packages that I should install. BTW N6F26U broke Android Pay which makes me sad. Thanks in Advance.
What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates (thru April 2017) was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.
voyageurs60 said:
Data reception is still degraded significantly, am now thinking there is a problem with the tower.
Click to expand...
Click to collapse
Sorry, I haven't read through this thread. It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.