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.
Related
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.
http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.
lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.
stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.
I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.
1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.
Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?
Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.
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.
My mum's stock N6 is stuck at the 7.0 build with November 2016 security patch, NBD91P. No OTA update has arrived since then. So,
1) Can I directly adb sideload the latest full OTA file, N6F26Y, over NBD91P as I notice that there are different streams of build in the latest months, i.e. 6.0.1 (can ignore), 7.0.0 and 7.1.1?
2) Do I need to apply the updates monthly, i.e. Nov build->Dec build->Jan build->Feb build etc?
3) What is the consequence of sideloading the wrong build (there are some ATT-only builds)?
Thanks in advance!
lamchungning said:
My mum's stock N6 is stuck at the 7.0 build with November 2016 security patch, NBD91P. No OTA update has arrived since then. So,
1) Can I directly adb sideload the latest full OTA file, N6F26Y, over NBD91P as I notice that there are different streams of build in the latest months, i.e. 6.0.1 (can ignore), 7.0.0 and 7.1.1?
2) Do I need to apply the updates monthly, i.e. Nov build->Dec build->Jan build->Feb build etc?
3) What is the consequence of sideloading the wrong build (there are some ATT-only builds)?
Thanks in advance!
Click to expand...
Click to collapse
Hello,
1 + 2 - You can go ahead and sideload latest whatever you want. It's not an incremental update, it's a full one. Just sideload N6F26Y...
3 - ATT build likely contain, either specific software or Radio. If you don't use ATT network, you'll want to flash the other one.
Cheers...
If you flash an ATT only build then most likely you won't be able to call and send/receive sms, unless you use an ATT SIM.
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
hawkerpaul said:
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
Click to expand...
Click to collapse
According to the Google Pixel Community Forum this is going to be fixed automatically by the Global December build.