6.0.1 build OLDER than 6.0? - Nexus 6P Q&A, Help & Troubleshooting

Anyone notice the build number for 6.0.1 (ends in M) is OLDER than the build number for 6.0 (ends in N)?
Any ideas why?
Sent from my Nexus 6P using Tapatalk

chrisexv6 said:
Anyone notice the build number for 6.0.1 (ends in M) is OLDER than the build number for 6.0 (ends in N)?
Any ideas why?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not 100% sure what happened there, but it's most likely because they'd already nearly completed and named the 6.0.1 update, and then had to push out the MMB29N build to fix the major problems Telstra users in Australia were facing first. MMB29M is definitely the latest build and incorporates the fixes (radio, etc) contained in the MMB29N build.

It sort of makes me wonder if that has anything to do with the radio issues on 6.0.1
Sent from my Nexus 6P using Tapatalk

chrisexv6 said:
It sort of makes me wonder if that has anything to do with the radio issues on 6.0.1
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I haven't noticed any radio issues. What's happening?

Lots of people reporting issues with long times to get LTE, delayed or broken LTE to 3g switch over, etc.
Some people have had success rolling back to the older radio as a workaround. Google has it as an official issue but no fix in sight yet

Heisenberg said:
I haven't noticed any radio issues. What's happening?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/lte-issues-6-0-1-radio-canadian-carriers-t3267270

chrisexv6 said:
Lots of people reporting issues with long times to get LTE, delayed or broken LTE to 3g switch over, etc.
Some people have had success rolling back to the older radio as a workaround. Google has it as an official issue but no fix in sight yet
Click to expand...
Click to collapse
billycar11 said:
http://forum.xda-developers.com/nexus-6p/help/lte-issues-6-0-1-radio-canadian-carriers-t3267270
Click to expand...
Click to collapse
Hmm, that's very similar to what was happening for Telstra users before Google fixed it with the MMB29N and MMB29M updates.

Heisenberg said:
Hmm, that's very similar to what was happening for Telstra users before Google fixed it with the MMB29N and MMB29M updates.
Click to expand...
Click to collapse
Yeah it's almost like they "built" the radio for 6.0.1 from an outdated base or they provided the wrong one for certain regions.
But not everyone has reported issues and still some have no success flashing back to the older radio

Related

MDB08L & MDB08M 6P images

Has anyone flashed either, and if so, what did it break/fix?
I JUST saw these posted today.
https://developers.google.com/android/nexus/images?hl=en
chevycam94 said:
Has anyone flashed either, and if so, what did it break/fix?
I JUST saw these posted today.
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
Where is the one with the K at the end? I think maybe the decryption process is different per image as each image has their own stock kernel (boot.img) with decryption.
it's just above those with l and m
https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
November security update
deeproot said:
https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
November security update
Click to expand...
Click to collapse
But why two updates in one day? I'd assume M is the one we should flash?
kingmikel said:
But why two updates in one day? I'd assume M is the one we should flash?
Click to expand...
Click to collapse
According to this article-yes: http://www.androidpolice.com/2015/1...-makes-factory-images-available-for-download/
I'm receiving my 6P Thursday, but all the guides I see for unlocking and decrypting are for 08K. After I get my 6P to 08K unlocked and decrypted, can I still take these updates?
MDB08L Root Tutorial?
How can I root my nexus 6p with the build number, MDB08L? I just got the November update. I have been trying to root ever since I got this phone but I can't find a solid tutorial, because of my build number changing. Does any one have a good link?
I manually flashed M update last night before rooting it and I had to decrypt the rom so that root could work. All fine now.
sbrennan013 said:
How can I root my nexus 6p with the build number, MDB08L? I just got the November update. I have been trying to root ever since I got this phone but I can't find a solid tutorial, because of my build number changing. Does any one have a good link?
Click to expand...
Click to collapse
I used this to unlock, root and install TWRP. I had the same build as you.
SKIPSOFT TOOLKIT
I guess I bit off more then I can chew... I'm really new to rooting and I really want to get in to it. But all I only ever rooted my old nexus 5 and that was extremely simple lol. This new nexus 6p to me feels like you need experience and I don't want to brick my phone. The different build numbers hesitate me. Videos make it a lot simpler for me so I can follow step by step and see what is supposed to happen.
sbrennan013 said:
How can I root my nexus 6p with the build number, MDB08L? I just got the November update. I have been trying to root ever since I got this phone but I can't find a solid tutorial, because of my build number changing. Does any one have a good link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Make sure you flash Chainfires boot.bin and install SuperSU zip in TWRP. Dont say yes if you exit TWRP and it asks you to install root.
Question: What is the big difference between L and M? BTW, my N6P automatically updated to L. So I'm not sure if what Android Police says is right or not.
Seiga said:
Question: What is the big difference between L and M? BTW, my N6P automatically updated to L. So I'm not sure if what Android Police says is right or not.
Click to expand...
Click to collapse
Not sure what the difference is (most likely the monthly security updates but thats pure assumption) but i was able to unlock and root on build M with the same instructions as the K build
enigma4321 said:
Not sure what the difference is (most likely the monthly security updates but thats pure assumption) but i was able to unlock and root on build M with the same instructions as the K build
Click to expand...
Click to collapse
They're both November updates. That's the thing. So I'm curious to wondering what is the big difference between the two.
Seiga said:
They're both November updates. That's the thing. So I'm curious to wondering what is the big difference between the two.
Click to expand...
Click to collapse
Wish I could tell you. I don't see any changes personally
I think I saw a changelog somewhere where it looked like maybe a new wlan driver and a security update
Sent from a 128th Legion Stormtrooper 6P
Seiga said:
Question: What is the big difference between L and M? BTW, my N6P automatically updated to L. So I'm not sure if what Android Police says is right or not.
Click to expand...
Click to collapse
Seiga said:
They're both November updates. That's the thing. So I'm curious to wondering what is the big difference between the two.
Click to expand...
Click to collapse
[hfm] said:
I think I saw a changelog somewhere where it looked like maybe a new wlan driver and a security update
Sent from a 128th Legion Stormtrooper 6P
Click to expand...
Click to collapse
That was the question/concern I have as well. I just got my 6P two days ago and the November security update was pushed to my device. However it shows I'm on the L build and not the M build. How long does it take for an OTA to be pushed to your device? I would assume if M is newer than my phone should get it? It's just weird that I have the most up to date security patch but not the most up to date factory image and IDK why that is. Thanks.
Not every update is for every phone region. If we haven't gotten an 08M OTA there's a reason.
Sent from a 128th Legion Stormtrooper 6P
Saying then if on L build won't get the M? If that's the case if on L shouldn't consider flashing M images?

Skip 6.0.1 update for now?

Just received a new 6P today. It is asking me if I want to update to 6.01. have read some bad reports for this update. Should I skip it for now?
read bad reports where?
Noooo!!! 6.0.1 fixes a lot of bugs in 6.0
Soulfly3 said:
read bad reports where?
Click to expand...
Click to collapse
No new Emojis after 6.01 update
http://forums.androidcentral.com/nexus-6p/623084-no-new-emojis-after-6-01-update.html
LTE issues on 6.0.1 update
http://forums.androidcentral.com/nexus-6p/620036-lte-issues-6-0-1-update.html
6.0.1 battery drain?
http://forums.androidcentral.com/nexus-6p/621841-6-0-1-battery-drain.html
6.0.1 Bluetooth issue fix?
http://forum.xda-developers.com/nexus-6p/help/6-0-1-bluetooth-issue-fix-t3280636
I updated mine and everything seems fine...Howevber I've only had my phone for 11 days so I can't really tell you if the phone is running better or not....but I think it runs great!!
My signal strength dropped and that LTE issue is annoying AF
You could make a full backup of 6.0 then update to 6.0.1 and see how it goes. I for one am still on 6.0 because I am affected by the LTE issue.
Go for the update. If you notice any of the problems downgrade. Its quite strange but not all users are effected.
None of this issues, but I'm spinning a custom rom...
galaxys said:
None of this issues, but I'm spinning a custom rom...
Click to expand...
Click to collapse
What rom are you using? im considering flashing a custom rom.
I'm having no issues with 6.0.1 at all. It depends on your personal usage and you should try it yourself. With a backup there is no problem to return to 6.0 if you should spot issues. Personally I would definitely update, just because of the security updates...
Regards,
HRodMusic said:
My signal strength dropped and that LTE issue is annoying AF
Click to expand...
Click to collapse
I think this is accounting for my increased battery between 6.0.0 and 6.0.1
JoKe_42 said:
I'm having no issues with 6.0.1 at all. It depends on your personal usage and you should try it yourself. With a backup there is no problem to return to 6.0 if you should spot issues. Personally I would definitely update, just because of the security updates...
Regards,
Click to expand...
Click to collapse
If I update, do I need to be rooted to go back if I want to return to 6.0?
l_stevens said:
If I update, do I need to be rooted to go back if I want to return to 6.0?
Click to expand...
Click to collapse
I believe you just need your bootloader unlocked, and you can flash the original system package and be back to 6.0.
HRodMusic said:
My signal strength dropped and that LTE issue is annoying AF
Click to expand...
Click to collapse
the radio didn't change, so how did that happen
l_stevens said:
If I update, do I need to be rooted to go back if I want to return to 6.0?
Click to expand...
Click to collapse
You don't need to be rooted, unlock the bootloader and create a backup using TWRP. The tutorial for this can be found in the general section of the Nexus6P forum .
Regards,
HRodMusic said:
What rom are you using? im considering flashing a custom rom.
Click to expand...
Click to collapse
I'm on Chroma's latest which is very Solid and Stable. But there are some other sweet ones as well...
JoKe_42 said:
You don't need to be rooted, unlock the bootloader and create a backup using TWRP. The tutorial for this can be found in the general section of the Nexus6P forum .
Regards,
Click to expand...
Click to collapse
I'm new/never done an unlock. Does only unlocking (not rooting) affect Android Pay?
Does unlocking burn the 6P "fuse"?
l_stevens said:
I'm new/never done an unlock. Does only unlocking (not rooting) affect Android Pay?
Does unlocking burn the 6P "fuse"?
Click to expand...
Click to collapse
No and No
l_stevens said:
I'm new/never done an unlock. Does only unlocking (not rooting) affect Android Pay?
Does unlocking burn the 6P "fuse"?
Click to expand...
Click to collapse
Android Pay is not affected by unlocking the bootloader (or using systemless root). But unlocking will cause your phone to be wiped, so you should save important data manually.
The QFuse is not affected by unlocking the bootloader either, but it is popped by default during the fabrication process. There once was a thread about this somewhere here.
Regards,

24.11.24 es march security level

My girlfriend's XT1092 got the update to the version in the title yesterday. Meanwhile, my UK XT1092 still is to receive it.
Anyone else here got it?
mELIANTE said:
My girlfriend's XT1092 got the update to the version in the title yesterday. Meanwhile, my UK XT1092 still is to receive it.
Anyone else here got it?
Click to expand...
Click to collapse
so they are actually giving security patches ? damn that's awesome.
Yesterday recieved
PD: i have screenshots in HTCmania
XXFURIUSXX said:
Yesterday recieved
PD: i have screenshots in HTCmania
Click to expand...
Click to collapse
Is it still 6.0 or have they upgraded to 6.0.1 ?
Still shows as 6.0 but should have parity with 6.0.1
mELIANTE said:
Still shows as 6.0 but should have parity with 6.0.1
Click to expand...
Click to collapse
But the long-press copy/paste menu lag would still be there. Meh
(edit: ...actually, is it still there?)
not new emojis, its only security...
XXFURIUSXX said:
not new emojis, its only security...
Click to expand...
Click to collapse
Do you have the zip file for the update? I would love to see what all came with it...
Edit: Here are the pictures that he uploaded on HTCMania, I had to use Google Translate in order to gain access
kokotron said:
But the long-press copy/paste menu lag would still be there. Meh
(edit: ...actually, is it still there?)
Click to expand...
Click to collapse
I'd also like to know, if the lag is still there in stock 6.0
The whole reason why I am running CM 13 nightlies on custom kernel as daily driver..
thousandecibels said:
I'd also like to know, if the lag is still there in stock 6.0
The whole reason why I am running CM 13 nightlies on custom kernel as daily driver..
Click to expand...
Click to collapse
It is just a security update, they didn't make any changes other than fix vulnerabilities.
Sent from my XT1095 using Tapatalk
Rolling out now it seems. https://motorola-global-portal.cust...prod_answer_detail/a_id/110303/p/30,6720,9197
Guess this means no 6.0.1 update like the X Play and Moto G 2015 now getting. Shame as hopped the bluetooth issue would be resolved
rsocon said:
Rolling out now it seems.
Guess this means no 6.0.1 update like the X Play and Moto G 2015 now getting. Shame as hopped the bluetooth issue would be resolved
Click to expand...
Click to collapse
I'm still not seeing it on Pure Edition XT1095 in US/AT&T.
Is that release page specific to a certain Moto X 2nd gen variant?
Edit: Did you receive it? If yes, where?
I'm in the UK and no sign here.
The link seems to go to the US Moto website so I guess its related to there.
rct12345 said:
I'm still not seeing it on Pure Edition XT1095 in US/AT&T.
Is that release page specific to a certain Moto X 2nd gen variant?
Edit: Did you receive it? If yes, where?
Click to expand...
Click to collapse
It's the xt1092 from spain.
Sent from my XT1095 using Tapatalk
Been more than 15 days... still no sign of this update for my XT1095.
Sucks to see 'Android security patch level: November 1, 2015'
rct12345 said:
Been more than 15 days... still no sign of this update for my XT1095.
Sucks to see 'Android security patch level: November 1, 2015'
Click to expand...
Click to collapse
It's a mind thing. If you really want, you can flash Nexus Experience rom, best thing to happen to Moto X in a while.
thousandecibels said:
It's a mind thing. If you really want, you can flash Nexus Experience rom, best thing to happen to Moto X in a while.
Click to expand...
Click to collapse
Can't... Need a stock unrooted device for my work emails.
Don't want to make this into a Moto bashing rant (next time I'm buying a nexus!), so will just wait for the update.
rct12345 said:
Can't... Need a stock unrooted device for my work emails.
Don't want to make this into a Moto bashing rant (next time I'm buying a nexus!), so will just wait for the update.
Click to expand...
Click to collapse
Can't blame you. I myself hate where Lenovo is taking Moto.
Could you tell me the Build Number, please? I'm gonna try to find a fastboot image of it ...
XT1092_VICTARA_RETES_6.0_MPE24.49-24_cid7_CFC
XT1092_VICTARA_ORAEU_6.0_MPE24.49-24_cid7_CFC
Both with March Security Patch.

Cell sig problem

I have a 64gig 6P on T-Mobile. I don’t know when the issue started, I use the phone as part of the digits program, but the cell signal is constantly dropping. It rotates through LTE, 3G, H then drops and starts over again in a few min. My S7 sitting next to it stays on LTE with no issue.
I thought it was a digits program beta issue so swapped sim cards. Did not help
I was on the android beta program, so took the device off and did a full reset with no additional apps installed. Did not help.
I did a search on the forum and the only advise I can find is to flash an older radio, but I haven’t read anywhere that this helped.
Has anyone found a way to fix this?
Phone is currently stock, non rooted, on 7.1.1 with march update and warranty just expired...
Thanks
gbaz1 said:
I have a 64gig 6P on T-Mobile. I don’t know when the issue started, I use the phone as part of the digits program, but the cell signal is constantly dropping. It rotates through LTE, 3G, H then drops and starts over again in a few min. My S7 sitting next to it stays on LTE with no issue.
I thought it was a digits program beta issue so swapped sim cards. Did not help
I was on the android beta program, so took the device off and did a full reset with no additional apps installed. Did not help.
I did a search on the forum and the only advise I can find is to flash an older radio, but I haven’t read anywhere that this helped.
Has anyone found a way to fix this?
Phone is currently stock, non rooted, on 7.1.1 with march update and warranty just expired...
Thanks
Click to expand...
Click to collapse
Have you tried a different radio?
sting5566 said:
Have you tried a different radio?
Click to expand...
Click to collapse
No, I have not seen anyone say that it has actually solved the problem.
gbaz1 said:
No, I have not seen anyone say that it has actually solved the problem.
Click to expand...
Click to collapse
What radio are you currently on?
sting5566 said:
What radio are you currently on?
Click to expand...
Click to collapse
Whatever the stock one is for 7.1.1 on the march 5th security update.
gbaz1 said:
Whatever the stock one is for 7.1.1 on the march 5th security update.
Click to expand...
Click to collapse
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
sting5566 said:
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
Click to expand...
Click to collapse
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
gbaz1 said:
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
Click to expand...
Click to collapse
You can use fastboot to flash the radio.
gbaz1 said:
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
Click to expand...
Click to collapse
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
v12xke said:
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
Click to expand...
Click to collapse
Where did you find 3.81 radio?
sting5566 said:
Where did you find 3.81 radio?
Click to expand...
Click to collapse
Both a new radio and bootloader came with the new 7.1.2 image, but it is also available in General. There is a dedicated thread there. If you don't intend on updating to 7.1.2, I'd suggest you download both the baseband (03.81) and bootloader (03.67) and fastboot flash them. If you don't like it, you just flash back.
v12xke said:
Both a new radio and bootloader came with the new 7.1.2 image, but it is also available in General. There is a dedicated thread there. If you don't intend on updating to 7.1.2, I'd suggest you download both the baseband (03.81) and bootloader (03.67) and fastboot flash them. If you don't like it, you just flash back.
Click to expand...
Click to collapse
Downloading now and I might ty out the radio, thanks.
I'm having the same problem on a different carrier. It just started recently. Flashing an older radio did not fix the problem for me.
I loaded 7.1.2 with the new 3.81 but it's doing the same thing.
sting5566 said:
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
Click to expand...
Click to collapse
v12xke said:
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
Click to expand...
Click to collapse
I'll see if anyone with a different carrier will let me use their sim.
Question have you updated carrier services in the play store?
tnerb123 said:
Question have you updated carrier services in the play store?
Click to expand...
Click to collapse
Yep, everything is updated. Taking off the beta program again to try. Turns out my warranty runs out in April. So going to try to have it fixed under warranty...
Huawei is going to repair or replace it under warranty. I'll post on if this fixed the issue in a week or two.
Guys I am having the same issue. My Nexus 6P went out of warranty this Feb. I flashed 3.72, 3.75 and 3.79 but the issue still persists. I am on AT&T. Has anyone had any success with the newest Radio?
pronoyc said:
Guys I am having the same issue. My Nexus 6P went out of warranty this Feb. I flashed 3.72, 3.75 and 3.79 but the issue still persists. I am on AT&T. Has anyone had any success with the newest Radio?
Click to expand...
Click to collapse
No, but it only takes a minute to try it out. If it doesn't work for you, just flash back to the radio that matches your bootloader. Like many have said the answer is not going to be a different radio.

April security patch is available

build number N6F26Y
https://developers.google.com/android/ota
french screenshot
For the record:
- New Baseband version
- New Bootloader version
Also two new 7.0 April images loaded. NBD92F and NBD92G. Anyone know the difference in these two?
Sent from my Nexus 6 using XDA-Developers Legacy app
mhirsh said:
Also two new 7.0 April images loaded. NBD92F and NBD92G. Anyone know the difference in these two?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm guessing one is AT&T only like some of the previous images, but not sure which is which.
What changes does this new security patch have?
Sent from my Nexus 6 using XDA Labs
https://source.android.com/security/bulletin/2017-04-01.html
it's strange that we only have the 2017-04-01 patch and not the 2017-04-05... we usually have 201#-##-05 security level
Candy[MAN] said:
For the record:
- New Baseband version
- New Bootloader version
Click to expand...
Click to collapse
I know how to flash these. But if we are using a custom rom and kernel should we wait until they are on the April patch level before doing so?
Visi0nofExcellence2 said:
I know how to flash these. But if we are using a custom rom and kernel should we wait until they are on the April patch level before doing so?
Click to expand...
Click to collapse
Nah, radio & b/l aren't tied to the rom, and both are backward compatible.
mhirsh said:
Also two new 7.0 April images loaded. NBD92F and NBD92G. Anyone know the difference in these two?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I wonder why they are still maintaining 7.0 when there is 7.1.1 out there
pv24 said:
I wonder why they are still maintaining 7.0 when there is 7.1.1 out there
Click to expand...
Click to collapse
Most likely that 7.0 was the last version to fully support 32 bit devices. Yes 7.1.1 works but it starts moving the code base to a 64 bit base which as seen causes issues for us on 32 bit devices.
works great, no bt or speakerphone issues for me
My phone has always been stock and never rooted. Since yesterday that I updated to the 7.1.1 April, I have not seen any lag or throttle that my nexus 6 had on all Nougat roms (7.0 Nov and 7.1.1Jan, Feb or Mar). Finally!!
Cool! Will probably flash it tonight! Thanks for the heads up!
Did it yesterday in Am. All good so far
Never mind
pv24 said:
I wonder why they are still maintaining 7.0 when there is 7.1.1 out there
Click to expand...
Click to collapse
Because none of the US carriers have rolled 7.1 to phones on their systems.
zelendel said:
Most likely that 7.0 was the last version to fully support 32 bit devices. Yes 7.1.1 works but it starts moving the code base to a 64 bit base which as seen causes issues for us on 32 bit devices.
Click to expand...
Click to collapse
Could be, but the nexus player, while it is a 64bit chip, is running 32bit flavor of android. And has the O dev preview.
T-moblie just pushed NBD92G to my phone (Android 7.0).
For some reason, I no longer recieve OTAs. I clean flashed the Feb 7.1.1 and haven't received an update ever since.

Categories

Resources