I have a Nexus 6 directly from Motorola running on Verizon that I've unlocked and flashed with the latest factory images from Google, but I was wondering what build number I would be on (which of the LRX or LMY builds?) if I had just let it take OTAs. Thanks!
Herohtar said:
I have a Nexus 6 directly from Motorola running on Verizon that I've unlocked and flashed with the latest factory images from Google, but I was wondering what build number I would be on (which of the LRX or LMY builds?) if I had just let it take OTAs. Thanks!
Click to expand...
Click to collapse
LMY47E
Related
I have a Nexus 6 on Build LYM47Z. For Marshmallow, its using build MRA58K.
I'm in the UK and use Vodafone. Will there be any implications if I was install the build manually? like compatibility, phone frequencies etc
Thanks
Nope. Flash away...
Willzy12h said:
I have a Nexus 6 on Build LYM47Z. For Marshmallow, its using build MRA58K.
I'm in the UK and use Vodafone. Will there be any implications if I was install the build manually? like compatibility, phone frequencies etc
Thanks
Click to expand...
Click to collapse
This build works on every Nexus 6 in the world. Though it is recommended Project Fi users do not use it.
I was looking at the Nexus 6 factory images. It looks like it jumps from 6.0 to 7.1.1, then back to 6.0, then 7.1.1......is this an error or were the 7.1.1 beta builds ?
Also is Google still making factory images for the Nexus 6 ? I thought that development was over for it, but I am pleased to see not so.
Take a look at the "shamu" section: https://developers.google.com/android/images
It's all there.
EDIT: I think you are affirming that =P Yes, we're going to receive security updates from now on. 7.1.1 is the final Android version.
Google is releasing three builds per month. One build for android 6.0, one for android 7.0 and one for android 7.1.1
Development was over at android 7.1.1 And all build has security patches only.
Correct, I was just confirming that the security updates were being rolled out. Then after Nov that's it huh ? Only custom development ? This is my first Nexus where development will stop /
mikeprius said:
Correct, I was just confirming that the security updates were being rolled out. Then after Nov that's it huh ? Only custom development ? This is my first Nexus where development will stop /
Click to expand...
Click to collapse
Well, every Nexus get software updates from Google during 2 years.
Seeing all the ROMs in development/original development, the Nexus 6 is far from being dead... :good:
Cheers...
My phone is build NBD92G (Verizon build) and doesn't seem to be pulling down 7.1.1..
What build is best to use for Fi? Would it be better to use the generic build?
Also, is it safe to sideload an OTA for the generic N6 (N6F27I) instead of the Verizon specific (N8I11B) OTA, or should I use the full image to switch away from Verizon code?
My N6P [stock on Fi] is running 7.1.2, build N2G48B. I assume this is the latest Fi has pushed out, I have not had an update in a few weeks. Still on the July5th security patch.
bigwavedave25 said:
My N6P [stock on Fi] is running 7.1.2, build N2G48B. I assume this is the latest Fi has pushed out, I have not had an update in a few weeks. Still on the July5th security patch.
Click to expand...
Click to collapse
Thanks. Mine is a 6, not 6P.
I am using N6F27I on Project FI with no problems.
sac164 said:
I am using N6F27I on Project FI with no problems.
Click to expand...
Click to collapse
Thanks.
Also, sideload of the OTA was successful.
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I'm on t-mobile and have used all the lastest img from google web site without an issue.
Currently I'm on Dark rom 8/27 build with the latest radio 05.45R and still havent had an issue. you should be good to go if you update with factory img.
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I ran a 7.1.2 custom rom on tmo for a long time and no issues. Currently running an 8.0 custom rom on tmo and also no issues at all
adm1jtg said:
I ran a 7.1.2 custom rom on tmo for a long time and no issues. Currently running an 8.0 custom rom on tmo and also no issues at all
Click to expand...
Click to collapse
may i ask which Oreo rom you are running?
SynisterWolf said:
may i ask which Oreo rom you are running?
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/development/8-0-0r4-s-x-aosp-rom-r3ds-t3670056
SynisterWolf said:
I'm on t-mobile and have used all the lastest img from google web site without an issue.
Currently I'm on Dark rom 8/27 build with the latest radio 05.45R and still havent had an issue. you should be good to go if you update with factory img.
Click to expand...
Click to collapse
Did you get the OTA update or did you flash it? Also, how's your connectivity? I had bad experience in the past after updating. Thanks!
I'm on 7.1.2 Pure Nexus (N6) and just made the jump from Sprint today. My number was ported by T-Mobile within 2 hours and the service is MUCH better. As a bonus, I can now call and use data simultaneously. Not possible on Sprint.
I've been a sprint customer since the early 1990s. That just goes to show how stupid I am ?
7.0 (Build NBD92G) is the current T-mobile supported build (but they sure don't say that anywhere on their website). T-mobile pushed that build several months ago to users on stock devices. I figure T-mobile has EOLed the Nexus 6 6 months before Google did, so plan to side-load the final 7.1 build when it drops next month.
Replicant82 said:
Hi folks! If you're on T-Mobile and run Nougat 7.0, can you tell me how your device perform? It seems that 7.0 wasn't tested by T-Mobile so I'm bit concerned about issues once I make the jump. Please let me know. Thank you
Click to expand...
Click to collapse
I just bought a new unlocked Nexus 6 from Amazon. I would not have intentionally updated past the OS officially supported by T-Mobile, but during the setup, I accidentally upgraded it to Nougat 7.1.1. So far it is working great. This is the first Google phone I have ever used, and I like not having all the Samsung apps that I never use. It may be my imagination, but it seems to be running better than the Note 4 I was using.
FarmerCharlie said:
I just bought a new unlocked Nexus 6 from Amazon. I would not have intentionally updated past the OS officially supported by T-Mobile, but during the setup, I accidentally upgraded it to Nougat 7.1.1. So far it is working great. This is the first Google phone I have ever used, and I like not having all the Samsung apps that I never use. It may be my imagination, but it seems to be running better than the Note 4 I was using.
Click to expand...
Click to collapse
This could be because Samsung has their own custom ui overlay "touchwiz" its been known to cause lag especially when the device is older and the software is back ported.
T-mo users, have you tried the latest 7.1.1? Since we just got the last update, I'm about to side-load. Any known issues on T-mo? I assume N6F27M is the one to go with?
How can you find out what version of the phone you have? I purchased a used Google brand (or so I thought) P5 this spring and I thought I flashed the Feb 21 A11 RQ1"A".210205.004 build (certain I did because that's the build I have downloaded). I did this before I ever installed my Verizon SIM card. I have been struggling with connectivity issues for a while now, and another XDA member suggested that I reflash the radios from that build. Sounds like a good idea, but when I just looked at the build number on the phone its a RQ1"D" build number. I never downloaded that version, so three questions:
1, Could the phone change the build number when I installed the Verizon SIM card? If so, which radio flash would be the correct one? The Google version or the Verizon version?
2. What can I check on the phone to determine what version of the hardware I have? I had the bootloader unlock option available when I got the phone, so I thought it was a Google phone. Are there other clues as to the hardware version?
3, Generally, if you are using a Google phone with a Verizon SIM in it, do you use Google builds or Verizon builds?
Thanks in advance
Settings > About phone > Android version
Or
Settings > About phone -- Build number is on the bottom
When I first bought the phone (Google unlocked) I was using Verizon.
I'm now on AT&T, however the build used remain the same.
I'll link the latest factory images for Pixel 5
Android 12
Android 13
andybones said:
Settings > About phone > Android version
Or
Settings > About phone -- Build number is on the bottom
When I first bought the phone (Google unlocked) I was using Verizon.
I'm now on AT&T, however the build used remain the same.
I'll link the latest factory images for Pixel 5
Android 12
Android 13
Click to expand...
Click to collapse
Thanks for your response. Something odd seems to be going on here. I found the phones hardware to be GD1YQ in the Regulatory Labels tab, so is not the Japan or Global model. So I know I did not download and flash the Verizon build, but yet the phone says the version is the "D" (Verizon) build. I am not sure whether to flash the radios out of the Verizon version or the Google version of the update. I do not want a brick, so I am confused as to how to move forward.
But, if there is no specifically Verizon version hardware, why is there two different updates? It should not matter which version you use, right? Especially if the hardware is unlocked and the only difference is the sim card...
What am I missing here?
amajamar said:
Thanks for your response. Something odd seems to be going on here. I found the phones hardware to be GD1YQ in the Regulatory Labels tab, so is not the Japan or Global model. So I know I did not download and flash the Verizon build, but yet the phone says the version is the "D" (Verizon) build. I am not sure whether to flash the radios out of the Verizon version or the Google version of the update. I do not want a brick, so I am confused as to how to move forward.
But, if there is no specifically Verizon version hardware, why is there two different updates? It should not matter which version you use, right? Especially if the hardware is unlocked and the only difference is the sim card...
What am I missing here?
Click to expand...
Click to collapse
Mine is GD1YQ as well..
I'd just download either of the 2 links I Linked above, depending of if you want A12 or A13.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
andybones said:
Mine is GD1YQ as well..
I'd just download either of the 2 links I Linked above, depending of if you want A12 or A13.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
I'm still using A11, actually. I can get the downloads, but just not sure which one I should use.
amajamar said:
I'm still using A11, actually. I can get the downloads, but just not sure which one I should use.
Click to expand...
Click to collapse
This is as simple as I can possibly make it for you...
Android 11.0.0 (RQ3A.211001.001, Oct 2021
Android 12.1.0 (SQ3A.220705.003.A1, Jul 2022)
Android 13.0.0 (TP1A.220624.014, Aug 2022)
Depending on if you want to stay on Android 11, upgrade to Android 12 or latest Android 13.. these are the links for the Pixel 5 - Redfin
I personally suggest you upgrade to Android 12, and wait for more releases of Android 13, before upgrading to it.
Choice is yours obviously.