All my Pixels have been Google-branded. Over the years, there have been carrier-specific builds during some updates. I have seen it for Verizon and T-Mobile. I have used both the generic version and carrier-specific builds and they work fine in the Google-branded Pixels.
I am still curious, though, what is Google's intent for these carrier-specific builds? Should the Google-branded Pixel always run the generic build, or if I am using a Verizon SIM, I should use the Verizon-specific build?
My phone is rooted, so I never OTA.
The carrier specific builds usually have either different bootloader or radio images than the Google stock build. My guess as to why Google does this is that the carrier submitted their changes somewhat late in the cycle and Google doesn't want to risk rolling them out to everyone until they are sure it works as intended, since they usually go back to a single stock build the next month that includes the carrier specific items. As to which build to use my experience has been that a Google branded phone with a Verizon sim will try to take a Stock OTA if the difference is the bootloader and the Verizon OTA if it is the radio. I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image.
DougMG said:
I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image.
Click to expand...
Click to collapse
To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks.
snovvman said:
To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks.
Click to expand...
Click to collapse
Correct.
june 19?
I honestly don't think it matters. I didn't even notice that there was a Verizon version and was in a rush getting ready to leave work. I accidentally downloaded and flashed the Verizon version to my Google branded 3XL on AT&T and it's doing fine. I've had no issues.
Related
What is the latest build? I see all these builds and posts from the 18th saying this version or that. None match mine and i want to be sure before rooting since OTA will be gone at that point. I cleared google service framework and it is NOT rooted and the bootloader is locked, i will do all that once its on the latest version. It shows build JLS36C is this the latest as of Sept 20th?
jasunto said:
What is the latest build? I see all these builds and posts from the 18th saying this version or that. None match mine and i want to be sure before rooting since OTA will be gone at that point. I cleared google service framework and it is NOT rooted and the bootloader is locked, i will do all that once its on the latest version. It shows build JLS36C is this the latest as of Sept 20th?
Click to expand...
Click to collapse
JLS36C is the latest for the LTE variant.
Yeah took a while of googling and I figured it out. BTW the AT&T deal $100 bill credit isn't possible. Need two year contract and can't do that unless you buy device from AT&T and they don't sell. I just tried. Added to my family share plan anyway.
Sent from my HTC One using Tapatalk 4
Hey everyone
I have an M8 with me. GSM of course. It's S-OFF with an Unlocked bootloader.
Current CID is HTC__001
Current FW is 6.12.401.4
My Radio/baseband right now is 1.29.214500021.12G_20.72.4196t.01_F
Now for no reason at all, I want to convert to Developer Edition.
Questions:
1) Can I flash the Developer Edition RUU and then flash the radio from the .401 firmware to get LTE Band 3 (1800MHz) and Band 20 (800MHz)?
2) Is there a ZIP format RUU available for the Dev Edition? I hate using EXEs.
3) Does Developer need 0P6B120 or can I stay on 0P6B100?
4) Will I get OTAs on Dev Edition if I have a different radio than the Dev one?
1. Haven't seen reports of this exact combination being flashed. But in theory, it should work.
2. Not sure if I've seen zip format. Can't think of a thread, off hand. If I find one, I'll post it here.
3. You need to change to the proper MID (in this case 0P6B120). That goes for any official RUU.
4. Pretty sure that having a different radio will cause OTA to fail.
redpoint73 said:
1. Haven't seen reports of this exact combination being flashed. But in theory, it should work.
2. Not sure if I've seen zip format. Can't think of a thread, off hand. If I find one, I'll post it here.
3. You need to change to the proper MID (in this case 0P6B120). That goes for any official RUU.
4. Pretty sure that having a different radio will cause OTA to fail.
Click to expand...
Click to collapse
Would it be pointless then if I converted?
Considering I'd have to flash OTAs etc manually.
Also, do Dev edition devices get monthly security patches? Because the 401 firmware is on the December 2015 security patch.
And there aren't any new OTAs.
Sent from my Nexus 6
murtaza02 said:
Would it be pointless then if I converted?
Considering I'd have to flash OTAs etc manually.
Click to expand...
Click to collapse
Seems pointless to me, yes. The DE has been getting updated a bit faster than 401, but only by a few weeks (if I remember properly). And they are both pretty much unbranded ROMs.
Once you take OTA updates out of the equation, yes it seems pointless to convert to DE.
murtaza02 said:
Also, do Dev edition devices get monthly security patches? Because the 401 firmware is on the December 2015 security patch.
And there aren't any new OTAs.
Click to expand...
Click to collapse
No, the DE does not get monthly patches. I don't know of any HTC phone that got monthly patches. The last update for DE was last December, also.
redpoint73 said:
Seems pointless to me, yes. The DE has been getting updated a bit faster than 401, but only by a few weeks (if I remember properly). And they are both pretty much unbranded ROMs.
Once you take OTA updates out of the equation, yes it seems pointless to convert to DE.
No, the DE does not get monthly patches. I don't know of any HTC phone that got monthly patches. The last update for DE was last December, also.
Click to expand...
Click to collapse
So the only way to get recent security patches is to flash CM or GPE?
Do Sense based custom ROMs have the latest security patches or are they also stuck on December?
Sent from my Nexus 6
murtaza02 said:
So the only way to get recent security patches is to flash CM or GPE?
Do Sense based custom ROMs have the latest security patches or are they also stuck on December?
Click to expand...
Click to collapse
I'm not even sure GPE gets the monthly patches. Sense versions certainly don't.
I just got the OTA for 7.1.1 on my unlocked Pixel XL in the UK yesterday and the build number says NMF26Q. I cannot seem to find this build number anywhere, not even on the Google OTA listings (latest one there is NMF26O). Has anyone else received this as well?
I'm stock and unrooted.
Not surprised to hear this. The OTAs must not be unified across the 3 variants (Europe, Verizon, US/Other) as we've seen historically so far with the previous builds . The only differences are likely to be small things related to the carriers/telecoms of the particular region, like baseband changes, maybe VoLTE/Wifi Calling stuff, etc.
Wish Google would label the updates right for regions if they're gonna do this though.
Aaaand of course as I type this a check the wesbite actually does say "Europe" and "Verizon" in them
Roxas598 said:
Wish Google would label the updates right for regions if they're gonna do this though.
Aaaand of course as I type this a check the wesbite actually does say "Europe" and "Verizon" in them
Click to expand...
Click to collapse
I agree.
Not for the 7.1.1 version though. I only see the NMF26O build, and it's simply labeled as Dec 2016.
I also got a new update after flashing the one Google released and it's 800MB :S
srimany_sanket said:
I just got the OTA for 7.1.1 on my unlocked Pixel XL in the UK yesterday and the build number says NMF26Q. I cannot seem to find this build number anywhere, not even on the Google OTA listings (latest one there is NMF26O). Has anyone else received this as well?
I'm stock and unrooted.
Click to expand...
Click to collapse
Only one I can see anywhere is NMF26O, located here (factory image): https://developers.google.com/android/images
Roxas598 said:
I also got a new update after flashing the one Google released and it's 800MB :S
Click to expand...
Click to collapse
Who's your carrier?
Just had this in the UK on o2, was on the O version
Sent from my Google Pixel XL using XDA Labs
s1dest3pnate said:
Who's your carrier?
Click to expand...
Click to collapse
O2
Just got NMF26Q as well in the UK.
I adb side loaded the 26O the day before yesterday, and got 26Q the next day too. Also in the UK and on O2, although the handset is unlocked.
Back
Hi I am coming from G5 plus and sad to see no custom roms or developement for this device.....
mysterio619 said:
Hi I am coming from G5 plus and sad to see no custom roms or developement for this device.....
Click to expand...
Click to collapse
Because the device is ****ING BRAND NEW and not even available in the US unlocked yet.
twelfth said:
Because the device is ****ING BRAND NEW and not even available in the US unlocked yet.
Click to expand...
Click to collapse
It is, now.
pizza_pablo said:
It is, now.
Click to expand...
Click to collapse
Which was my point. It does seem a bit foolish to expect active development on a device that has yet to be released for another month.
twelfth said:
Which was my point. It does seem a bit foolish to expect active development on a device that has yet to be released for another month.
Click to expand...
Click to collapse
I agree.
I read that the official kernel was released, by lenovorola, so things should be happening, soon.
It has only been the Verizon version up until recently. In a few months as more people buy and developers buy, you'll see more activity here.
twelfth said:
Because the device is ****ING BRAND NEW and not even available in the US unlocked yet.
Click to expand...
Click to collapse
It's been available for the US for over a month. It was released 8/18 or 8/21, I can't remember which, but I remember it was that weekend.
Shouldn't we also see factory images for this thing too? I don't mind messing with it and poking around but I want a way to go back to stock if I screw something up.
KnightCrusader said:
It's been available for the US for over a month. It was released 8/18 or 8/21, I can't remember which, but I remember it was that weekend.
Shouldn't we also see factory images for this thing too? I don't mind messing with it and poking around but I want a way to go back to stock if I screw something up.
Click to expand...
Click to collapse
Look at the date of OP's post.
>> By mysterio619, Senior Member on 10th August 2017, 04:08 PM
He was asking for custom roms before the device was shipping from the factory.
Stock image is already available and has been posted in other threads. It was how I made my TWRP build for the Retus version of the Z2 Play.
They're available here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
twelfth said:
Look at the date of OP's post.
>> By mysterio619, Senior Member on 10th August 2017, 04:08 PM
He was asking for custom roms before the device was shipping from the factory.
Stock image is already available and has been posted in other threads. It was how I made my TWRP build for the Retus version of the Z2 Play.
They're available here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Click to expand...
Click to collapse
The only thing that I am confused about is... is the image the same for all the Z2 Play variants? I seen a bunch of them, from -01 to -07 (I'm not even sure what the US one is, I get mine on Wednesday).
KnightCrusader said:
The only thing that I am confused about is... is the image the same for all the Z2 Play variants? I seen a bunch of them, from -01 to -07 (I'm not even sure what the US one is, I get mine on Wednesday).
Click to expand...
Click to collapse
While the Z2 Play are all called "Albus" as a codename, the US is "Retus", Retail US variant of the Albus. (Settings > About Phone > Software Channel) There is an international variant, too, (Probably also called Retin like my Z Play is called) Someone built a TWRP based on an international image and it was incompatible with Retus, so I would not quickly assume that images are interchangeable until roms are built against a device tree (Like LineageOS keeps) with all the variant differences merged together into the kernel.
twelfth said:
While the Z2 Play are all called "Albus" as a codename, the US is "Retus", Retail US variant of the Albus. (Settings > About Phone > Software Channel) There is an international variant, too, (Probably also called Retin like my Z Play is called) Someone built a TWRP based on an international image and it was incompatible with Retus, so I would not quickly assume that images are interchangeable until roms are built against a device tree (Like LineageOS keeps) with all the variant differences merged together into the kernel.
Click to expand...
Click to collapse
Okay, so the stock image you linked isn't the one we need for Retus then? That's what I want to have as a fallback.
KnightCrusader said:
Okay, so the stock image you linked isn't the one we need for Retus then? That's what I want to have as a fallback.
Click to expand...
Click to collapse
What I linked is the stock image for Albus/Retus. With the Moto devices, it's typically Device Codename/Software Channel.
twelfth said:
What I linked is the stock image for Albus/Retus. With the Moto devices, it's typically Device Codename/Software Channel.
Click to expand...
Click to collapse
Okay then, I am downloading that so I have it when I get my phone so the festivities can commence. Thanks for the info.
twelfth said:
While the Z2 Play are all called "Albus" as a codename, the US is "Retus", Retail US variant of the Albus. (Settings > About Phone > Software Channel) There is an international variant, too, (Probably also called Retin like my Z Play is called) Someone built a TWRP based on an international image and it was incompatible with Retus, so I would not quickly assume that images are interchangeable until roms are built against a device tree (Like LineageOS keeps) with all the variant differences merged together into the kernel.
Click to expand...
Click to collapse
Albus is the device code name i.e. the hardware's code name. Retus, reteu, retca, retin etc are the software channels. So all variants of Z2 play will be called Albus (except maybe the Verizon locked ones or 3gb /4b ram variants or ones with/without nfc maybe called differently I don't know) whereas they will be on different software channels. I am assuming it is exactly the same for a particular hardware variant(for eg i have one with NFC and 4gb ram and all unlocked z2 play phones in all markets with 4gb ram and NFC will have same software) that is available unlocked in all markets of the world .
Edit: Posts I am basing my assumptions on:
https://forum.xda-developers.com/z2...-updates-questions-help-t3674133/post73819819
https://forum.xda-developers.com/z2...-updates-questions-help-t3674133/post73866594
08-10-2017 no devs for Z2 play :C
lsanchez93 said:
08-10-2017 no devs for Z2 play :C
Click to expand...
Click to collapse
10-20-2017 and same appears to be true...
:crying:
Actually, I'd be satisfied with our firmware avilable on Motorola's site and an official TWRP.
This is the first phone I haven't felt the need to have a custom ROM for absolutely nothing, it's just veeery stock with exactly the thingy majiggis I would install anyway, and also have the fortune that my carrier is the cleanest carrier of all, absolutely no bloatware whatsoever, only the radio "PRIP" service. Not saying it wouldn't be great to have some custom action, but not really having a hurry for it.
Not planning on rooting mine yet, but I'm curious, does the TWRP for Retus work on Retca (Canada) my variant has 3GB of ram and NFC
I'm close to being where a don't feel the need to root.
I miss battery bar with no battery icon and dark backgrounds, but I could probably live without.
What I can't live without is Dolby Atmos.
I'm just bit gushy about rooting, with no official TWRP and original firmware available from Motorola.
pizza_pablo said:
I miss battery bar with no battery icon and dark backgrounds, but I could probably live without.
.
Click to expand...
Click to collapse
You actually don't need root to do the battery stuff, you can do this with stock. Enable the hidden System UI Tuner (https://lifehacker.com/the-coolest-things-you-can-do-with-androids-hidden-syst-1773364942), then you can disable the battery icon.
Then just go grab one of the battery bar apps from the Play store. I use Power Bar (https://play.google.com/store/apps/details?id=com.etechtour.batterybar&hl=en)
Got a good deal on a moto z2 force (with 3 moto mod accessories, so had to snap it up) - From Vodafone UK
Question about Oreo updates on this phone. Does not exist yet as I believe it is down to the carrier and networks to finalise, test and release, hence the delays.
I am aware that there are quite a few oreo firmware for retail models. (Although none exist yet for XT1789-06?) I have already unlocked the bootloader and I wanted to update to the recent ones. What I am worried about is the IMEI baseband. Anyone had success with this specific model (06)?
There's root, su ,magisk and xposed on this thread thanks to enetec.
https://forum.xda-developers.com/z2...w-to-safely-blunlock-twrp-root-t3704596/page1
Have not seen any oreo related updates, I did read on another thread that the t-mobile Oreo update was pulled because it was having issues with calls I think so maybe our version they are having the same issues. Have not even found a flash all file for our device so one a bit hesitant about even trying any other Rom.
Official bootable and flashable twrp works on nougat. Sprint wasn't on Oreo until late Feb z so I have used the first iteration on my phone before the Oreo OTA. It will have decryption support which is advised compared to encryption not working. That's a huge security risk. I'd suggest using official twrp and magisk if you want root. That way you keep encryption.
thealgorithm said:
Got a good deal on a moto z2 force (with 3 moto mod accessories, so had to snap it up) - From Vodafone UK
Question about Oreo updates on this phone. Does not exist yet as I believe it is down to the carrier and networks to finalise, test and release, hence the delays.
I am aware that there are quite a few oreo firmware for retail models. (Although none exist yet for XT1789-06?) I have already unlocked the bootloader and I wanted to update to the recent ones. What I am worried about is the IMEI baseband. Anyone had success with this specific model (06)?
Click to expand...
Click to collapse
Hi there updated mine to Oreo with the file in this link https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL just follow the instructions in the link In post 2 on this thread, I'm pretty sure you can skip the unlocking bootloader (unless you want root as I do)
No, the above is no good for my carrier/phone (Vodaphone UK) Results in wifi and modem not working. Also 3 sparse files are missing. Used a US based USC Oreo rom and works perfectly now however
thealgorithm said:
No, the above is no good for my carrier/phone (Vodaphone UK) Results in wifi and modem not working. Also 3 sparse files are missing. Used a US based USC Oreo rom and works perfectly now however
Click to expand...
Click to collapse
I had the the wifi problem when i flashed twrp (but still had network), then flashed the rom in my last post I am also on the uk vodafone model. could you post a link to the rom you flashed please.
It was this one https://androidfilehost.com/?fid=962187416754473797
It did give error in regards to the bootloader writing (and timed out - so did not overwrite bootloader) - I already have bootloader unlocked and was on Nougat when I recieved the phone. After updating to oreo, however with the exception of the carrier logo during boot, I have found no issues whatsoever with this rom on a Vodafone XT1789-06 UK model device. I also uninstalled or disabled US based applications / carrier bloat.
Everything works fine (Moto mods, Wifi, network, camera, 3d acceleration) etc
(Note, ignore the fact that the download is from the MotoZ2 play folder, there was no new directory for Z2 Force according to the uploader)
Cheers for the link already had this file downloaded but didn't flash it as I noticed it was a us Version. there was a update at 19:30 on the link I posted but have not flashed it yet, no bloatware on this rom just plain stock and all mods work will flash the update sometime over the weekend and let you know how it goes.
I tried the newer version recently and same issue (no wifi or modem), so reverted back to USC version
Hello guys i also have the z2 force on UK Vodafone and looking for a 8.0 update. Did you guys find one that completely works? i dont want to unlock the bootloader or root (stops my bank app).
Any news on this please?
sc0use said:
Hello guys i also have the z2 force on UK Vodafone and looking for a 8.0 update. Did you guys find one that completely works? i dont want to unlock the bootloader or root (stops my bank app).
Click to expand...
Click to collapse
Unlocking bootloader doesn't stop Banking apps but root will, I have an unlocked bootloader and on the xt1789-06 Vodafone UK running stock ROM from the link I posted above got both nationwide and Barclays apps and both run fine if you flash the first n version it will do all the seamless updates, it just seems Vodafone are a bit slow at pushing them.