(INFO Needed :) Nexus 6 and Andorid 6.0 - Nexus 6 Q&A, Help & Troubleshooting

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.

Related

Will Nexu 7 (2012) get Android KitKat ?

Hi,
Will Nexus 7 (2012) get Android updates in future ?
If yes then how long Google will keep on releasing updates for it ?
I am planning to buy one as its available at very low price.
Thanks.
Yes it already had kitkat
Sent from my GT-I9100 using Tapatalk 2
Still no OTA update yet though, so you'll have to flash it yourself
Sent from my Nexus 7 using xda app-developers app
YES.
Yes, it is running on my N7 2012 now - KRT16O or KitKat 4.4 was manually flashed/updated & rooted again with TWRP. A series of Apps updated via Play Store. Downloaded a 1.4MB patch/update - which should update it KRT16S "This software update ... improves performance and stability and fixes bugs." - with the prompt to "Restart & Install"
Interesting, my Nexus 5's build number is KRT16M and showing no newer update when I checked it just now.
go, get it!
kikloo said:
Hi,
Will Nexus 7 (2012) get Android updates in future ?
If yes then how long Google will keep on releasing updates for it ?
I am planning to buy one as its available at very low price.
Thanks.
Click to expand...
Click to collapse
It will surely get updates. If not OTA from Google, there are great Devs for this device who will support for long.
Btw Flipkart slashed price to 8499Rs for the 16GB one. Go, get one!

What's up with the lack of Nougat roms with this device?

I respectfully ask this question and have no intention to
offend any devs. I am currently planning to buy this phone and when
I looked at here to check on roms that I could use on my phone, I got a little overwhelmed by the lack of Nougat roms.
It is already almost 2017 and the roms are usualy lollipop or marshmallow. I expected at least to see Nougat roms.
Did the devs stopped supporting this device or about to?
drckml said:
I respectfully ask this question and have no intention to
offend any devs. I am currently planning to buy this phone and when
I looked at here to check on roms that I could use on my phone, I got a little overwhelmed by the lack of Nougat roms.
It is already almost 2017 and the roms are usualy lollipop or marshmallow. I expected at least to see Nougat roms.
Did the devs stopped supporting this device or about to?
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-14-1-t3495231. works for our variant too!
Dolemaine said:
http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-14-1-t3495231. works for our variant too!
Click to expand...
Click to collapse
yeah I am aware of the unofficial cm 14 rom but still, only one nougat rom.
I still expect more nougat rom since this is a popular phone
I read somewhere that this cm 14 rom has a lot of problems like not being able to receive and make calls. Heaven forbid if LTE with Tmobile sim even work on this rom. But correct me if i'm wrong.
I have been able to make calls with the latest build of the VZ rom. However this ROM is no longer under development since Cyanogenmod is dead. All the developers using cyanogenmod as their base are going to have to shift to something else or else they will be working with a stagnating code base. I'd expect a small period of little development for many ROMs while this shift takes place to directly using AOSP as their base or the spinoff of CM LineageOS to get up and running. As for the lack of Nougat ROMs at all. N has only been out since around Aug, and the note 4 isn't exactly a recent phone any longer. So you've got a dwindling user base with an even smaller base of developers that have the knowledge to build the ROMs still using the phone. In the end I wish the dev of that VZ Nougat ROM kept working on it. Likely all of the code fixes could be merged into LineageOS since it is the CyanogenMod code base
drckml said:
yeah I am aware of the unofficial cm 14 rom but still, only one nougat rom.
I still expect more nougat rom since this is a popular phone
I read somewhere that this cm 14 rom has a lot of problems like not being able to receive and make calls. Heaven forbid if LTE with Tmobile sim even work on this rom. But correct me if i'm wrong.
Click to expand...
Click to collapse
I use the 12/25 build as a daily driver. The only issues that affect me is: Camera(fixed with another app), Gallery(fixed with another app), sometimes screen wont wake up easy If you are on a long call.(this is rare for me). No VOLTE. Other than those things its a great rom.
Dolemaine said:
I use the 12/25 build as a daily driver. The only issues that affect me is: Camera(fixed with another app), Gallery(fixed with another app), sometimes screen wont wake up easy If you are on a long call.(this is rare for me). No VOLTE. Other than those things its a great rom.
Click to expand...
Click to collapse
I've tried installing the [ROM] [7.1.1] [UNOFFICIAL] CyanogenMod 14.1 ROM(Verizon) on my T-Mobile Galaxy Note 4 but am having issues with it once it reboots. The root seems to be lost and once I use SuperSU to install Root and the phone just boots in a loop. I'm guessing this has to do with the bootloader(Note4) vs Verizon. I'm not sure but could be wrong. Could someone please suggest a way to get my root on this Verizon Nougat ROM.
harryrasul said:
I've tried installing the [ROM] [7.1.1] [UNOFFICIAL] CyanogenMod 14.1 ROM(Verizon) on my T-Mobile Galaxy Note 4 but am having issues with it once it reboots. The root seems to be lost and once I use SuperSU to install Root and the phone just boots in a loop. I'm guessing this has to do with the bootloader(Note4) vs Verizon. I'm not sure but could be wrong. Could someone please suggest a way to get my root on this Verizon Nougat ROM.
Click to expand...
Click to collapse
Don't use supersu with this rom. I learned that it's more of a headache than not. Enable developer options. CM's Root access is in there. I'm on EPJ2 baseband. Also make sure you download the extra file in the OP (Something telephony, i can't remember). You need that If you ever restore a backup or you won't have data. This rom seems to be the most battery-friendly rom I've installed for this phone. Even tho I do miss Fast Charge...
Is there a TW based 7.0+ ROM for this phone?
Sent from my SM-N910T using XDA Premium HD app
Temetka said:
Is there a TW based 7.0+ ROM for this phone?
Sent from my SM-N910T using XDA Premium HD app
Click to expand...
Click to collapse
I think there will be no android 7.0+ touchwiz roms until samsung release official 7.0 for note 4.and sadly samsung already announced there will be no 7.0 for note 4.
http://dailysunknoxville.com/samsung-galaxy-note-4-dont-worry-about-nougat/920015758
Sent from my SM-N910T3 using XDA-Developers Legacy app
bobo2xtreme said:
http://dailysunknoxville.com/samsung-galaxy-note-4-dont-worry-about-nougat/920015758
Sent from my SM-N910T3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for the link, did you test this on the 910T ?
clsA said:
Thanks for the link, did you test this on the 910T ?
Click to expand...
Click to collapse
I haven't tested it. I figured it was base stuff on it and I don't like basic.
Sent from my SM-N910T3 using XDA-Developers Legacy app
this is the ORIGINAL development thread for that rom https://forum.xda-developers.com/note-4-verizon/development/emotionos-t3528639
its Emotion OS which is based on LineageOS (formerly Cyanogen Mod 14 aka CM 14 ). Its Nougat rom AOSP pretty much, it works fine on the N910T, ive tested and you can verify it works from the posts in that thread. You must be on a 910T Marshmallow based bootloader or the rom may not work correctly. verified working fine on EPJ2 bootloader.
So pretty much if you want it to work:
ODIN official N910TUVU2EPJ2 Samsung firmware
install recovery
flash EmotionOS from recovery
Trex888 said:
I think there will be no android 7.0+ touchwiz roms until samsung release official 7.0 for note 4.and sadly samsung already announced there will be no 7.0 for note 4.
Click to expand...
Click to collapse
We don't need official Nougat for Note 4 for that. Just wait until Nougat is completely released for S7/Edge, and there will probably be a S7 Nougat port to the N910F/FD/T/W8/V/P/G. Plus, we'll also have an S8/Edge port (I'm sure) and that will probably be Nougat, so don't get your hopes down.
I have Nougat on my Google Pixel XL.
It works great and custom AOSP/LineageOS ROM's are all rock solid/stable.
But with no sign of Xposed being available for Nougat anytime soon, I would not be in a rush to move to Nougat if I were ya'll.
As of today, it does not look good for Xposed to ever be fully released for Nougat.
And even if it were, you'd be looking at more time before all the GOOD xposed modules are updated to work with Nougat.
XeoNoX said:
this is the ORIGINAL development thread for that rom https://forum.xda-developers.com/note-4-verizon/development/emotionos-t3528639
its Emotion OS which is based on LineageOS (formerly Cyanogen Mod 14 aka CM 14 ). Its Nougat rom AOSP pretty much, it works fine on the N910T, ive tested and you can verify it works from the posts in that thread. You must be on a 910T Marshmallow based bootloader or the rom may not work correctly. verified working fine on EPJ2 bootloader.
So pretty much if you want it to work:
ODIN official N910TUVU2EPJ2 Samsung firmware
install recovery
flash EmotionOS from recovery
Click to expand...
Click to collapse
this is what I've been using for awhile now. solid for me. i could recommend it

Nexus 6 factory images

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...

Android 7.0 on T-Mobile

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?

Identifying the correct build number for Pixel 5...

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.

Categories

Resources