Have a New Pixel 6 (unlocked) I bought on PrimeDay. Currently on Xfinity which is Verizon MVNO. Do I install the Verizon VMNO image because I am using that carrier or do I install the regular image (non-Verizon) because it's not a Verizon phone? Also on a side note, some images are labeled as "softbank," "EMEA" and "APAC,"what do these refer to?
Thank you in advance
@Bad Bimr
12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)
Why?
The factory/OTA image are based on the carrier not the Manufacturer.
Pixel 6 Guide
Which Factory/OTA image should I Use?
Homeboy76 said:
@Bad Bimr
12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)
Why?
The factory/OTA image are based on the carrier not the Manufacturer.
Pixel 6 Guide
Which Factory/OTA image should I Use?
Click to expand...
Click to collapse
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
I actually installed the Verizon/MVNO software. Bootloader is still unlocked. Phone seems to work OK but it's only been a day. When the August build comes out I may try the non Verizon build, best yet maybe I will call google and ask them, not that they would know.
Strephon Alkhalikoi said:
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
Click to expand...
Click to collapse
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone.
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Homeboy76 said:
@Bad Bimr
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone.
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Click to expand...
Click to collapse
Except for the fact an unlocked device always downloads the unlocked update if you let the P6 update itself. Now, you may be totally on point about being able to use either image, but given Verizon's penchant for f**kery, why take the risk?
Strephon Alkhalikoi said:
Except for the fact an unlocked device always downloads the unlocked update if you let the P6 update itself. Now, you may be totally on point about being able to use either image, but given Verizon's penchant for f**kery, why take the risk?
Click to expand...
Click to collapse
I didn't know Google phones with unlocked bootloader's that take automatic updates always receive the Global OTA image because I do not take automatic updates.
If it is true all Google Pixel unlocked bootloader phones that receive automatic updates download the Global OTA image. I think people with Google Pixel phones that do not take the automatic updates should use the Global Factory/OTA image.
Strephon Alkhalikoi said:
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
Click to expand...
Click to collapse
Installing a Verizon factory image or OTA on a non-Verizon model Pixel won't lead to a locked bootloader.
Lughnasadh said:
Installing a Verizon factory image or OTA on a non-Verizon model Pixel won't lead to a locked bootloader.
Click to expand...
Click to collapse
I admit to not having tried it myself. I still wouldn't risk it however, even though in this case "Verizon" applies to that variant of P6 and isn't a sign of Verizon digging its grubby paws into the system.
I simply feel it is better to be safe here than sorry.
EMEA - Europe - Middle East Asia
APAC - Asia - Pacific
Homeboy76 said:
@Bad Bimr
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone: 12.1.0 (SQ3A.220705.004, Jul 2022)
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Click to expand...
Click to collapse
It all comes down which model you have, install according to that.
Check in About phone -> Regulatory labels
Cheers
Tom
Related
According to spectrumgateway.com/compatible-phones , the Moto E 4G LTE (2nd Gen) XT1527 is band 12 compatible. Can the XT1528 be made band 12 somehow, or is there a physical hardware difference between the devices?
What I gathered reading around here.
* Firmware images are available for T-Mo 1527. However I read that only the 5.02 firmware has band 12 working
* The bootloader is locked on the verizon device
Someone suggested that it might be possible to use part of the 5.02 firmware files for the radio for the 5.1 firmware, to enable band 12, but so far one person claimed that it did not work. . Looking at the number of views this thread has gotten, it appears there is a lot of interest in getting band 12 working on the verizon handset. If any of my statements are not correct, or otherwise, feel free to correct me
Verified the bootloader is locked on my 1528: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
* If it was not the case, then it might be possible to flash a firmware which enables band 12. Then we need a way to unlock the bootloader to enable band 12.
discord said:
What I gathered reading around here.
* Firmware images are available for T-Mo 1527. However I read that only the 5.02 firmware has band 12 working
* The bootloader is locked on the verizon device
Someone suggested that it might be possible to use part of the 5.02 firmware files for the radio for the 5.1 firmware, to enable band 12, but so far one person claimed that it did not work. . Looking at the number of views this thread has gotten, it appears there is a lot of interest in getting band 12 working on the verizon handset. If any of my statements are not correct, or otherwise, feel free to correct me
Click to expand...
Click to collapse
Hi All, I have unlock ATT version, then switch to T mobile service (flash T mobile firmware). Now I switch to Sprint firmware. HOwever My ATT ver didn't have the band 25 and 26. Only have band 41. Sprint needs all 3 for better connection. Is there away to unlock 25 and 26 band?
Unlock S9 plus vers and other have all bands
sweetboy02125 said:
Hi All, I have unlock ATT version, then switch to T mobile service (flash T mobile firmware). Now I switch to Sprint firmware. HOwever My ATT ver didn't have the band 25 and 26. Only have band 41. Sprint needs all 3 for better connection. Is there away to unlock 25 and 26 band?
Unlock S9 plus vers and other have all bands
Click to expand...
Click to collapse
The G965U and G965U1 are identical hardware wise and all support the same bands. What differentiates the G965U from the G965U1 is the that the G965U1 has the unlocked firmware (non carrier branded if that term makes more sense).
The only thing that differentiates one G965U from another G965U is the firmware. The firmware determines what bands are available as well as custom carrier settings/apps/configurations that is installed. For example if you properly flash the firmware for the Sprint G965U onto the AT&T G965U then it will have all the bands (and sprint customization/bloat) that the Sprint G965U version has.
To give you an example I have the sprint version, flashed it to the unlocked firmware, flashed to AT&T firmware and then finally to T-mobile. I didn't flash it in that order, that is just the different kinds of firmwares I have had on that phone.
Across the different firmware versions all necessary and needed bands were active and working just fine.
scottusa2008 said:
The G965U and G965U1 are identical hardware wise and all support the same bands. What differentiates the G965U from the G965U1 is the that the G965U1 has the unlocked firmware (non carrier branded if that term makes more sense).
The only thing that differentiates one G965U from another G965U is the firmware. The firmware determines what bands are available as well as custom carrier settings/apps/configurations that is installed. For example if you properly flash the firmware for the Sprint G965U onto the AT&T G965U then it will have all the bands (and sprint customization/bloat) that the Sprint G965U version has.
To give you an example I have the sprint version, flashed it to the unlocked firmware, flashed to AT&T firmware and then finally to T-mobile. I didn't flash it in that order, that is just the different kinds of firmwares I have had on that phone.
Across the different firmware versions all necessary and needed bands were active and working just fine.
Click to expand...
Click to collapse
Yes, i put in Sprint Sim on the phone then the phone auto removed the Tmobile apps and installed bunch of Sprint apps. I checked the specs for ATT ver and only see band 41 avail online. After Sprint firmware installed, I check again *#0011# and only see band 41. I was too assumed everything should be identical both S9 plus U or U1 but there must me something got block by ATT and carrier firmwares still can't unlock it.
sweetboy02125 said:
Yes, i put in Sprint Sim on the phone then the phone auto removed the Tmobile apps and installed bunch of Sprint apps. I checked the specs for ATT ver and only see band 41 avail online. After Sprint firmware installed, I check again *#0011# and only see band 41. I was too assumed everything should be identical both S9 plus U or U1 but there must me something got block by ATT and carrier firmwares still can't unlock it.
Click to expand...
Click to collapse
Did you flash the sprint firmware onto the at&t phone you have or did you just insert the sim card and let the phone apply the settings for the sim card?
If you did the latter (specifically just changing the sim card) this doesn't give you any of the carrier specific tweaks/customizations that can be found on the carrier firmware. For thse tweaks/customizations you need to flash the firmware for the carrier branded phone. So your better connection desire will most likely be a sprint firmware specific thing and not found on the at&t firmware.
Also looking up what the at&t branded phone supports and the sprint branded phone supports won't help much. It will only tell you what the two phones are configured to do for the carrier the phone is branded for. Those specs It do not tell you what the hardware can do (or that the hardware is the same whether it be the unlocked version from Samsung, the sprint branded one you buy from sprint or the at&t branded one purchased through at&t).
scottusa2008 said:
Did you flash the sprint firmware onto the at&t phone you have or did you just insert the sim card and let the phone apply the settings for the sim card?
If you did the latter (specifically just changing the sim card) this doesn't give you any of the carrier specific tweaks/customizations that can be found on the carrier firmware. For thse tweaks/customizations you need to flash the firmware for the carrier branded phone. So your better connection desire will most likely be a sprint firmware specific thing and not found on the at&t firmware.
Also looking up what the at&t branded phone supports and the sprint branded phone supports won't help much. It will only tell you what the two phones are configured to do for the carrier the phone is branded for. Those specs It do not tell you what the hardware can do (or that the hardware is the same whether it be the unlocked version from Samsung, the sprint branded one you buy from sprint or the at&t branded one purchased through at&t).
Click to expand...
Click to collapse
This makes sense. I'll will try to flash Sprint firmware on top right now. The reason I said tweaks/customization applied because the whole UI "Settings" of the change completely changed from Tmobile Pie to Sprint Pie (more buttons, header rename...) so I assume tweaks/customizations already applied when Sprint Simcard did its own things
Also I thought the base S9 Pie for U ver all the same. Only when you put the Carrier simcard in then they download their all carrier settings (Not in this case?
sweetboy02125 said:
This makes sense. I'll will try to flash Sprint firmware on top right now. The reason I said tweaks/customization applied because the whole UI "Settings" of the change completely changed from Tmobile Pie to Sprint Pie (more buttons, header rename...) so I assume tweaks/customizations already applied when Sprint Simcard did its own things
Also I thought the base S9 Pie for U ver all the same. Only when you put the Carrier simcard in then they download their all carrier settings (Not in this case?
Click to expand...
Click to collapse
Carrier settings (APN, MMS/SMS settings, PRL, Roaming lists and related) are not quite the same when it comes to bands being enabled/disabled or carrier tweaks/customizations. Also I don't know if the base for the s9+ contains all the full carrier customizations/tweaks or not when it comes to android pie. If I had to guess I would say it probably comes with a somewhat generic one size fits all configuration... Perhaps along the lines of what the U1 firmware has.
Though I would presume that the base does not have all the carrier customizations/tweaks because the carriers release android pie at different times.
As an example (for illustrative purposes to explain my presumption) AT&T releases the new update before T-mobile does. T-mobile releases the update before Verizon does. Because Verizon would have been the last to release the update both AT&T and T-Mobile would not have any of the additions Verizon would have made.
When flashing the sprint firmware onto the AT&T phone you have you may need to flash the U1 firmware first, do a factory data reset and then flash the G965U firmware for sprint. Someone else might have some insight if this is still applicable for Android Pie, but when I flashed from sprint to t-mobile using the Oreo firmware that is the process I had to go through.
scottusa2008 said:
Carrier settings (APN, MMS/SMS settings, PRL, Roaming lists and related) are not quite the same when it comes to bands being enabled/disabled or carrier tweaks/customizations. Also I don't know if the base for the s9+ contains all the full carrier customizations/tweaks or not when it comes to android pie. If I had to guess I would say it probably comes with a somewhat generic one size fits all configuration... Perhaps along the lines of what the U1 firmware has.
Though I would presume that the base does not have all the carrier customizations/tweaks because the carriers release android pie at different times.
As an example (for illustrative purposes to explain my presumption) AT&T releases the new update before T-mobile does. T-mobile releases the update before Verizon does. Because Verizon would have been the last to release the update both AT&T and T-Mobile would not have any of the additions Verizon would have made.
When flashing the sprint firmware onto the AT&T phone you have you may need to flash the U1 firmware first, do a factory data reset and then flash the G965U firmware for sprint. Someone else might have some insight if this is still applicable for Android Pie, but when I flashed from sprint to t-mobile using the Oreo firmware that is the process I had to go through.
Click to expand...
Click to collapse
I would debate on the example (for illustrative purposes to explain my presumption) you had above, I don't think carriers are related. I would think Google/Samsung (Google may give the base to Samsung first then Samsung distribute to each carrier) give each carrier the base then each carrier goes customize their own settings with their own times to release to us.
Yes the correct way to flash to U1 then flash back to be clean (I guess And I did that when switch from ATT to Tmobile) But i have to much to setup again, so may just dirty flash Sprint now
PS: Still can't find the Sprint Pie in Sammobile website. Only Verizon and Tmobile and Generic ver
scottusa2008 said:
Did you flash the sprint firmware onto the at&t phone you have or did you just insert the sim card and let the phone apply the settings for the sim card?
If you did the latter (specifically just changing the sim card) this doesn't give you any of the carrier specific tweaks/customizations that can be found on the carrier firmware. For thse tweaks/customizations you need to flash the firmware for the carrier branded phone. So your better connection desire will most likely be a sprint firmware specific thing and not found on the at&t firmware.
Also looking up what the at&t branded phone supports and the sprint branded phone supports won't help much. It will only tell you what the two phones are configured to do for the carrier the phone is branded for. Those specs It do not tell you what the hardware can do (or that the hardware is the same whether it be the unlocked version from Samsung, the sprint branded one you buy from sprint or the at&t branded one purchased through at&t).
Click to expand...
Click to collapse
Shouldn't have to flash the phone should install the firmware as soon as you install the Sim card
Sent from my SM-G965U1 using Tapatalk
---------- Post added at 02:25 PM ---------- Previous post was at 02:24 PM ----------
sweetboy02125 said:
Hi All, I have unlock ATT version, then switch to T mobile service (flash T mobile firmware). Now I switch to Sprint firmware. HOwever My ATT ver didn't have the band 25 and 26. Only have band 41. Sprint needs all 3 for better connection. Is there away to unlock 25 and 26 band?
Unlock S9 plus vers and other have all bands
Click to expand...
Click to collapse
All models are the same. Their just blocked in att firmware same goes for vzws B13. Your phone will install the firmware when you put in the sim card
Sent from my SM-G965U1 using Tapatalk
tengen31 said:
Shouldn't have to flash the phone should install the firmware as soon as you install the Sim card
Sent from my SM-G965U1 using Tapatalk
---------- Post added at 02:25 PM ---------- Previous post was at 02:24 PM ----------
All models are the same. Their just blocked in att firmware same goes for vzws B13. Your phone will install the firmware when you put in the sim card
Sent from my SM-G965U1 using Tapatalk
Click to expand...
Click to collapse
You are right, I saw 25 and 26 now. Sim card will download and unlock the band needed
sweetboy02125 said:
You are right, I saw 25 and 26 now. Sim card will download and unlock the band needed
Click to expand...
Click to collapse
Yep. My S8 did it,so does my S9+
Sent from my SM-G965U1 using Tapatalk
I am not sure if this would work or not and I haven't done this for a while. I might have the wrong service code or the menu option may have changed with android pie. So if I do someone feel free to correct it.
Note - if you see a message like RAT access/menu isnt allowed (or something like this) power off the phone, take the sim card out and power the phone on without the sim card in it. The process should work then.
*Open the phone app and enter ##DATA# (##3282#)
*Choose edit and if prompted enter a total of siix zeros as the MSL
*Select LTE to edit the active bands
From there you can enable or disable bands. If the band isn't listed you simply cant just add it. I would suggest flashing the carrier firmware as this would have it enabled.
Also I do believe that there are carrier customization/tweaks that may only be on the firmware from the carrier. Swapping the sim may change a few apps, change a few menu items and apply settings from the sim card onto the phone. It also may apply some (or perhaps most) carrier settings. I have not seen anything that gives me cause to believe that it applies all the carrier customization/tweaks.
If that were the case why did my g96u1 (or sprint g965u) firmware not show video calling or get provisioned for it, but flashing the tmobile firmware allowed for the feature to be enabled and provisioned. Also on the tmobile firmware I have had better signal retention and strength (not the signal bars, actual signal strength measurements on the phone) then with the unlocked firmware (or the original firmware that was on the phone with the tmobile sim).
If swapping the sim installs the tmobile firmware then that should have been all it took and I could continue to use the unlocked firmware, but this was not the case. The only features that were enabled were (outside of menu changes and app additions) VoLTE and WiFi calling. Now if this alone indicates carrier firmware specific features/tweaks/customizations can only reside on carrier firmware, then how could one declare it wouldn't also effect what bands are enabled/disabled. Like I said I haven't seen anything that says otherwise, but from what I have seen first hand there are somethings that are apparently only on the carrier's firmware that is not available on the others.
I've had my Pixel 6 for less than a month, bought it in Canada and updated in November to SD1A.210817.037, then rooted with Magisk. All is fine.
Now, I'm in Mexico with it, on Telcel, and the December updates have come out, but I have no idea which one to flash. Does anyone know?
The options are:
12.0.0 (SQ1D.211205.016.A1, Dec 2021)
12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers) *** I'm pretty confident it's not this one***
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)
I'm thinking that it's the first option, but I'm not sure...
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers) <--- I used this since T-Mobile is a US carrier
Probably for you, your best option is to flash the first option
I'm asking myself the same question. I've a Canadian model too. Once I bought it I flashed "12.0.0 (SD1A.210817.019.C2, Oct 2021, T-Mobile (US), USCC, Google Fi, CA, & TW carriers)" with magisk. I didn't even update to the November one because I wasn't sure, but I would like to do this one and see if that solve some bugs that I have. I just would like to be sure about the first option (which would make sence).
basily said:
I've had my Pixel 6 for less than a month, bought it in Canada and updated in November to SD1A.210817.037, then rooted with Magisk. All is fine.
Now, I'm in Mexico with it, on Telcel, and the December updates have come out, but I have no idea which one to flash. Does anyone know?
The options are:
12.0.0 (SQ1D.211205.016.A1, Dec 2021)
12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers) *** I'm pretty confident it's not this one***
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)
I'm thinking that it's the first option, but I'm not sure...
Click to expand...
Click to collapse
I'm from Monterrey, currently using Telcel and AT&T. I already flashed the dec update, go for the 1st one (12.0.0 (SQ1D.211205.016.A1, Dec 2021)).
=)
Kimbaroth said:
I'm from Monterrey, currently using Telcel and AT&T. I already flashed the dec update, go for the 1st one (12.0.0 (SQ1D.211205.016.A1, Dec 2021)).
=)
Click to expand...
Click to collapse
Thank you friend
sorry y'all. Im in California, bought my P6P unlocked from Google directly. Should I use the 1st one (or the US carrier one (3rd)?
Thanks very much!
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
AliasGprime said:
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
Click to expand...
Click to collapse
Can you link to said post, please?
I know that the right thing to do is to wait, but... well... ok, I'll wait :-|
basily said:
Can you link to said post, please?
I know that the right thing to do is to wait, but... well... ok, I'll wait :-|
Click to expand...
Click to collapse
Sure, it's a post that explain how to update without losing root.
Method to upgrade every month, without wiping data and retaining root
Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling...
forum.xda-developers.com
But most recent posts says they wont keep root after the update. Saw the same reports on a Telegram and a discord server.
I'm wondering the same thing as well. I'm running Mint Mobile (T-Mobile MVNO) on an Unlocked P6P in the US. I assume the US Carriers is the one I need to flash but I'm not positive.
I'm getting corrupted data and stuck on google screen can anyone assist?
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
I have not put a SIM in it yet, but it is in Europe.
Why did it not update to the A4 (EMEA Carriers) version ?, which is supposed to be for UK, IE, FR, DE.
And which EMEA carriers are we talking about, only from these countries: UK, IE, FR, DE, or also other from Europe ?
I wonder if I can install the A4 full OTA package over the A1 version ?
Vio281 said:
I'm getting corrupted data and stuck on google screen can anyone assist?
Click to expand...
Click to collapse
You'll find some colleagues here:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
andreipaval said:
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
Click to expand...
Click to collapse
Check the support page again -- it's been updated and now says the 016.A1 version is the global unlocked version. I was told something similar by a Google chat rep through the in-phone support function.
You're on the right build.
I'm in the US. Google is telling me I can be either on SQ1D.211205.016.A1 or SQ1D.211205.017. Doesn't seem like a reliable answer. I have an unlocked P6P and I'm on Verizon. Did anyone get a clear answer?
This is nuts.
Why would Google not have one image that adapts to the carrier in-play? After all, folk can change carriers/regions during the life of their phone. What happens then? The phone doesn't work properly until it somehow figures out it needs a different image and then somehow flips to it?
What about if you temporarily travel to a different region and roam onto a different operator? Is your phone not 'right for that region' and doesn't work properly?
So do these different images relate to different hardware variances of the phone?
lpkallia said:
I'm in the US. Google is telling me I can be either on SQ1D.211205.016.A1 or SQ1D.211205.017. Doesn't seem like a reliable answer. I have an unlocked P6P and I'm on Verizon. Did anyone get a clear answer?
Click to expand...
Click to collapse
I don't think anyone knows at this point. There are some major issues with network connectivity some are blaming on the December update and some are saying ongoing from previous builds. I'm in the latter group. They will have to come out with a new update sooner rather than later since this is widespread across the globe.
AliasGprime said:
I think I'm gona wait a little bit more before updating. On another post many said that they lost root and magisk doesn't seem to work on the new update at the current state.
Click to expand...
Click to collapse
Magisk is running perfect on the december update. And no problems with 4G ,, I did a clean install on de December update.
Used the A1 version and no problems at all.
andreipaval said:
Does anyone know what is the difference between 12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)
and the A1 version ?
I have a Pixel 6 bought from the German Google Store and it received the December update, but it automatically installed the A1 version, which the support page says is for Canada.
I have not put a SIM in it yet, but it is in Europe.
Why did it not update to the A4 (EMEA Carriers) version ?, which is supposed to be for UK, IE, FR, DE.
And which EMEA carriers are we talking about, only from these countries: UK, IE, FR, DE, or also other from Europe ?
I wonder if I can install the A4 full OTA package over the A1 version ?
Click to expand...
Click to collapse
Hmm, looks interesting. i have a spare Nexus device, so i can easily try it.
ok i've successfully updated SQ1D.211205.016.A4 (EMEA) over SQ1D.211205.016.A1 (global) using full ota. Storeage remains intact. Sim works (Spusu / Austria / Sub carrier using Hutchison Drei Austria).
But upgrading to SQ1D.211205.017 failed with "Build newer than timestamp 1638904347 but package has timestamp 1638280743 and downgrade not allowed". The same if you try to revert back to .A1 Image, so you have to unlock the bootloader and reflash the stock image. Of Course, all data will be lost.
sakerhetz said:
Magisk is running perfect on the december update. And no problems with 4G ,, I did a clean install on de December update.
Used the A1 version and no problems at all.
Click to expand...
Click to collapse
Yeah, I did it yesterday too. i was waiting for a Magisk-Alpha update before, which we got yesterday. I need this one specially for Denylist to work without zygisk.
Hello, looking for some help to see if anyone can help me find the firmware of my A526U specifically for AT&T? I have moved my phone over from TMobile where I purchased it from, and am looking to re-flash it to AT&T. Was working fine for a few months, now I'm no longer able to make or receive calls.
After inserting the new AT&T SIM card, the TMobile splash screen still shows up. The Service Provider software version reflects TMobile still as well and I'm concerned that for whatever reason the phone did not fully update after inserting the new SIM. I spent 2 hours on the phone with AT&T support after the store said they couldn't help me. Pulled the SIM card out, restarted phone, put it back in, reset network settings etc. I've searched sammobile and I cannot find the AT&T firmware, only TMobile, Sprint, and TMK. I would sincerely be greateful please if anyone could help me by pointing me in the right direction for the firmware for this model phone.
AT&T doesn't make their firmware available publicly - for any device. I have a source who can get me Samsung firmware for any USA device - even AT&T. But he charges me for each one
I appreciate the quick response! Is there any option I have here? Could I try flashing a "U1" firmware to his phone then? He's currently on A526USQS4CVA6. I actually found your other post as I was also working on my note 10 plus - https://forum.xda-developers.com/t/n975u-and-n975u1-firmware-links-here.3957648/. If I'm reading that correctly, I should be able to correct? If so, how can I tell if the version I'm downloading is "downgrading the bootloader"
aschaffer35 said:
I appreciate the quick response! Is there any option I have here? Could I try flashing a "U1" firmware to his phone then? He's currently on A526USQS4CVA6. I actually found your other post as I was also working on my note 10 plus - https://forum.xda-developers.com/t/n975u-and-n975u1-firmware-links-here.3957648/. If I'm reading that correctly, I should be able to correct? If so, how can I tell if the version I'm downloading is "downgrading the bootloader"
Click to expand...
Click to collapse
1. Yes, you can try flashing U1 if you want
2. You can't "downgrade the bootloader" - Odin won't let you.
3. In A526USQS4CVA6, "4" is the position of the bootloader level/revision/binary. Make sure that whatever U1 firmware you download also has a 4 in that spot and you'll be fine. (Or just get the firmware from Frija or one of the other similar firmware download tools, because those throw you whatever the newest version is automatically)
iBowToAndroid said:
1. Yes, you can try flashing U1 if you want
2. You can't "downgrade the bootloader" - Odin won't let you.
3. In A526USQS4CVA6, "4" is the position of the bootloader level/revision/binary. Make sure that whatever U1 firmware you download also has a 4 in that spot and you'll be fine. (Or just get the firmware from Frija or one of the other similar firmware download tools, because those throw you whatever the newest version is automatically)
Click to expand...
Click to collapse
Thank you very much sir! I shall give this a go this weekend! You guys rock!
My AT&T N10+ N975U is running on Pie. It transitioned seamlessly with no changes made on my end. It was already using 4G VoLTE though. Same sim card.
I would contact AT&T advanced tech support as there may be an easier way.
4G VoLTE needs to be enabled in hidden settings.
blackhawk said:
My AT&T N10+ N975U is running on Pie. It transitioned seamlessly with no changes made on my end. It was already using 4G VoLTE though. Same sim card.
I would contact AT&T advanced tech support as there may be an easier way.
4G VoLTE needs to be enabled in hidden settings.
Click to expand...
Click to collapse
Your AT&T phone? So it's originally an AT&T model that you're still using with them? That's not the same situation that the OP is in
iBowToAndroid said:
Your AT&T phone? So it's originally an AT&T model that you're still using with them? That's not the same situation that the OP is in
Click to expand...
Click to collapse
The U is the AT&T variant vs the U1 which is the unlocked variant, correct?
blackhawk said:
The U is the AT&T variant vs the U1 which is the unlocked variant, correct?
Click to expand...
Click to collapse
Yup. But OP has a T-Mobile model that they moved to AT&T. There's also no guarantee that a Note 10+ will work the exact same way as an A52. You're also running 3 year old firmware, while OP is fully updated.
So i don't see the correlation.
iBowToAndroid said:
Yup. But OP has a T-Mobile model that they moved to AT&T. There's also no guarantee that a Note 10+ will work the exact same way as an A52. You're also running 3 year old firmware, while OP is fully updated.
So i don't see the correlation.
Click to expand...
Click to collapse
The old firmware works fine on 4G VoLTE... that's likely not the issue. What is the issue is it wasn't running on 4G VoLTE so it's likely the settings and sim card need updating not the firmware.
Hi All, thought I would provide an update... After spending hours on the phone with AT&T support this week and being frustrated with the AT&T store, I decided to proceed forward with flashing the U1 version. What started this all was last week my son could no longer make or receive calls on his AT&T A52 phone (we ported it from TMobile September 2021). The store and AT&T advanced tech support said there were issues with people's BYOD devices, even though the A526U and A526U1 shows on the supported devices list. The store rep said he's been getting people in left and right that can't make or receive calls, and all they can do is upsell customers to an AT&T branded phone.
SO... my son's phone was on A526USQS4CVA6. Startup screen showed TMobile still, even with the AT&T SIM card in it. I proceed to flash the A526U1OYM4CVB2_ATT that I found from Sammobile. Was hoping someone had just the "U" version but I couldn't find this anywhere. When doing the flash, I used the Home_CSC file (I had to download a patched version of ODIN as it was stuck as setting up connection) and when it finished it would just keep going back to the download screen on the phone and I freaked out. I did some more research and decided to flash again using CSC instead of Home.CSC (I did a backup using smart switch on my PC luckily). This WORKED! I'm guessing because the software version he was on was different than what I was trying to flash too so maybe this is why I needed the CSC for a clean flash (there was no user data file that downloaded from SAMMOBILE).
Now, calls are working on my son's phone again! AND his service provider software version now reflects ATT vs TMB! Man this has been one heck of a journey lol. I've seen numerous forums on google of people having the same trouble with me, their BYOD devices not working. Seems a flash of U1 worked for me, so hopefully this helps others out there!
I'm just collecting some info
What are all of the different models for the OnePlus Nord N200 5G?
The codename of the device is "dre".
DE2118 is the T-Mobile model when you buy through them (or Metro, I think).
I think DE2117 is the unlocked USA model? I'm not completely sure what the difference is between it and the DE2118.
DE17AA is apparently the global unlocked model.
Are there other models?
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
DE2117 is OEM unlocked USA. It's SIM unlocked / carrier unlocked and bootloader unlocked.
DE2118 is SIM locked / carrier locked to T-mobile or Metro-by-T-mobile. Some have reported that a DE2118 purchased from T-mobile or Metro also accepts Mint mobile (without needing to SIM unlock). It's possible they may also accept other MVNOs that use the T-Mobile network.
DE2118 is bootloader locked, "OEM unlocking" is off and greyed-out, not toggle-able. It becomes an option after the phone is SIM unlocked. Many have also been able to enable OEM unlocking with a bypass, using adb shell pm uninstall --user 0 com.qualcomm.qti.uim which a debloater script will also do for you. OnePlus might "fix" this loophole at some point. But if they do we can probably reverse it by downgrading.
I understand the DE2118 you get from either T-mobile or Metro loads the appropriate branded apps based on which SIM it first sees.
The different models are also listed in this guide Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
dre is the general device codename, but you may also see dre9 (DE2117) or dre8t (DE2118).
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform. [1] [2]
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
Click to expand...
Click to collapse
I believe DE18CB is just from the build number. You have that actually in the Model field? Here's a picture of it in the build number, with in the Model field showing DE2118.
Lots of extremely helpful hints. I already knew most of them from reading today, but thanks!
That notes daboross/oneplus_dre8t_dre9_holi_notes link was perfect. That's what I was assembling for myself.
blueberry.sky said:
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform
Click to expand...
Click to collapse
Ahha! Now that's new to me. I had seen it in fastboot and was wondering about it. Thanks!
Further reading seems to confirm my previous assumption that there are only three models, but sometimes people are refering to software versions in the model numbers, which might just be part of the file names for those releases/recoveries.
I've seen the "DE17AA" model also referred to as "DE2117AA". I don't know which is true or what the best nomenclature is, since I don't actually have one of these international unlocked models.
"DE17AA" I believe is just from software build numbers. And not a model number. DE17AA seems to be in the build numbers intended for the DE2117 model. Whereas DE18CB is in build numbers intended for the DE2118 model.
OnePlus Nord N200
Contribute to OnePlusOSS/OpenSourceReleases development by creating an account on GitHub.
github.com
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
Click to expand...
Click to collapse
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Sprunglicious said:
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Click to expand...
Click to collapse
How do you convert DE2118 to DE2117
Tranken587 said:
How do you convert DE2118 to DE2117
Click to expand...
Click to collapse
Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
CHANGELOG: Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware. Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first. There are THREE firmware versions for the N200...
forum.xda-developers.com