getting ready to buy a deep sea blue note 8 from best buy unlocked version. Just wondering how quickly they get the OTA updates. Do carriers push them out first before the unlocked models? also if I buy the unlocked and flash the carrier firmware via "carrier flash thread" will my device receive the OTA updates from the carrier or do they need to be side loaded?
I purchased the unlocked model and it's still on the August security patches and have not received a single update since I bought it in early September.
Pretty sure the carrier versions are also on the August security patch.
Sent from my Pixel 2 XL using Tapatalk
I am confused about which factory image I should use. I have unlocked Pixel 4 XL and I am using it on T-Mobile. I have 007.A3 Nov 2019 on the phone now. Should I use the 011 image because I'm on T-Mobile or should I use 012.A1 because I have the unlocked version? Thanks.
10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi)
10.0.0 (QQ1B.191205.012.A1, Dec 2019)
cg87 said:
I am confused about which factory image I should use. I have unlocked Pixel 4 XL and I am using it on T-Mobile. I have 007.A3 Nov 2019 on the phone now. Should I use the 011 image because I'm on T-Mobile or should I use 012.A1 because I have the unlocked version? Thanks.
10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi)
10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Click to expand...
Click to collapse
https://support.google.com/pixelphone/thread/21769134?hl=en :good:
Badger50 said:
https://support.google.com/pixelphone/thread/21769134?hl=en :good:
Click to expand...
Click to collapse
I read that page but it didn't really answered my question. My unlocked Pixel 4 has the "All other carriers" 007.A3. Should I update to the "All other carriers" 012.A1 or should I update to the T-Mobile 011 version? Does anyone know what's the difference between the 2?
I have the same problem, I don't know which one I should use. I have the unlocked version from the Google Store. I am also on the T-mobile Network. Anyone have any clues to which? I am on the 007.A3 Nov build. Does anyone know what the differences are?
pinoyz said:
I have the same problem, I don't know which one I should use. I have the unlocked version from the Google Store. I am also on the T-mobile Network. Anyone have any clues to which? I am on the 007.A3 Nov build. Does anyone know what the differences are?
Click to expand...
Click to collapse
Use the build for your current carrier. There is no special or different build for an unlocked phone from the Google store. In your case you would use T-Mobile, Fi, EMEA: QQ1B.191205.011. I jumped early before the correction was issued and grabbed 191205.012.A1 which is working fine on T-Mobile. I don't plan on flashing again until next month.
The OTA Images download page lists two images.
One normal one, and one "KDDI only".
What exactly is KDDI? My take from Googling it is that it's some Provider.
The device I got came with said "KDDI only" Image on it (Build Number ends with ...021.A1), and VoLTE and VoWiFi aren't working, and I somehow suspect it might be the wrong image.
Makes me wonder if I can just sideload the non-KDDI OTA image to fix it? Anyone happens to have any insight there?
Edit: Just sideloading the non-KDDI OTA image does not work. Downgrade-Prevention kicks in.
Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.
Dilbert83 said:
Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.
Click to expand...
Click to collapse
https://gadgets.ndtv.com/mobiles/ne...ges-published-android-developers-site-2311265
KDDI network subscribers in Japan
Hey there from Germany. I pre-ordered mine direct from Google and it was delivered from UK to Germany.
Mine also has the KDDI firmware preinstalled
Same here in france, tried to install magisk with the kddi boot img and it didnt worked
I also have the 021.A1 ROM on my Pixel in Germany, I rooted with the boot image from the international 020 build however - that worked fine, and I also pass SafetyNet on basic attestation with the HideProps module. @SOSODU13016 what issues did you have exactly? Did the root not get applied when booting up? Or did your device simply not boot?
The root did not applied ?, but booting was fine
SOSODU13016 said:
The root did not applied , but booting was fine
Click to expand...
Click to collapse
Try to patch the boot image yourself in Magisk Manager, and flash it another time. It also took two tries for me for some reason until Magisk finally was installed. I've also read from others that they had to reboot multiple times.
https://forum.xda-developers.com/newreply.php?do=newreply&p=83752561
Click to expand...
Click to collapse
I'm confused, how do i know if i choose the wrong boot.img ? will i enter in a bootloop ? i'll try to patch myself with the kddi version since i'm on the 021.A1
EDIT : Ok i used my own boot.img patched with magisk based on the 021.A1 boot.img from google and it worked. Thanks everyone !
My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Sent from my Pixel 5 using Tapatalk
thesebastian said:
My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Click to expand...
Click to collapse
Same here but bought from Carphone Warehouse.
I'm in France, bought it from the google store, I've a kddi image too. So I don't think it's related to an oper
I've been using the Pixel 5 since Monday, but this morning I should restart my phone for a system update.
It was on version RD1A.200810.020, Oct 2020
and now RD1A.200810.021.A1, Oct 2020, KDDI only
I live in Germany and the phone also comes from Ireland.
The update process seems to be bugged.
Hi,
I've actually sent an email to the Google support regarding this topic, enquiring if it is normal for a phone purchased on the French Google Store to have a Japanese carrier variant pre-installed.
For now the request has gone through 3 different departments at Google as none of them feel sufficiently qualified to answer the question.
I'll let you know if I get any real feedback.
Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.
klopsknoedel said:
Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.
Click to expand...
Click to collapse
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (https://www.youtube.com/watch?v=1Aadgx7fDUQ)
cheptii said:
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (
)
Click to expand...
Click to collapse
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.
LuMe96 said:
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.
Click to expand...
Click to collapse
I didn't notice any difference. But I am sure that the global versions will be updated before the carrier specific versions.
lol, that's kinda strange.
You guys bought the Pixel 5 from EU Google store and got Japanese carrier-based firmware while I bought the Pixel 5 from Google Store Japan and got normal variant firmware.
Google changed the description with the November-Update today and it seems that they've mixed it up previously.
So the current regional versions are:
RD1A.200810.020, Oct 2020, AU & JP carriers
RD1A.200810.020.A1, Oct 2020, KDDI only
RD1A.200810.021.A1, Oct 2020, EU carriers
RD1A.200810.021.B3, Oct 2020, Verizon
RD1A.200810.022.A4, Oct 2020 (global?)
RD1A.201105.003, Nov 2020, JP carriers
RD1A.201105.003.A1, Nov 2020, AU carriers
RD1A.201105.003.B1, Nov 2020, EU carriers
RD1A.201105.003.C1, Nov 2020 (global?)
Anyway. As said, I bought my Pixel 5 from the german google store and not from a german carriers store. So I expect to be on "RD1A.201105.003.C1" instead my phone updated to "RD1A.201105.003.B1".
Still confusing but at least the "KDDI only" - discussion is solved. I guess. ?
I am a little confused regarding which of the firmware files are appropriate for the US (ATT) Pixel 5 ? I have an unlocked Pixel 5 and want to be able to flash firmware when it is released - I think it is the last file in the list, but want to make sure I don't flash the wrong file.
See Image below for a list of the available November Firmware for Pixel 5 from Google - which one should I use? (does it matter?)the fourth one listed? Or does it really matter?
View attachment 5131019
The 4th one is the one I have. I'm in the US, ATT.
RD1A. 201105. 003. C1
https://support.google.com/pixelphone/thread/80591482?hl=en
US variants rolls out this Monday 11/9
Ramone360 said:
https://support.google.com/pixelphone/thread/80591482?hl=en
US variants rolls out this Monday 11/9
Click to expand...
Click to collapse
I'm US and got mine on the 2nd. On my 4xl I often never received notification that there was an update and had to manually do it. The process sucks but I understand the reasoning.
Last one is the one you have to flash it.
Supposedly a Verizon specific build is coming out tomorrow.
Hello,
I bought a new PIXEL 4XL on the net and I have 2 questions:
- On the box there is an ESIM code so it is not a verizon. but my OEM is grayed out
- there is a service that runs: "MY VERIZON SERVICE"
Hello,
solved, it's a Virezon, and as I updated it with the November version of android 12, I can't unlock it with depixel8
wiko59 said:
Hello,
solved, it's a Virezon, and as I updated it with the November version of android 12, I can't unlock it with depixel8
Click to expand...
Click to collapse
hey!
I have a AT&T locked Pixel 4 XL as well, but I created a thread and we are worrking to unlock the bootloader.
I already manage to unlock the phone in the way you can use any sim with it , but the bootlaoder is still locked.
Here is the link of the thread if you are interested
Right know we found a way to flash an unlocked verion of the firmware, but we need to test it.
There is one guy that is actually working on it, as it has a bricked pixel 4 XL, but he didn't manage to succed yet, and I am currently helping him to troubleshoot.
So, as every help is precious, it would appreciated if you help us to win google's bootloader lock