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. ?
Related
Can someone tell me wich contry this is? I am guessing Brasil. I bought this phone from a retail in Romania. Thanks.
By the way, my build number is kxb21.85-14, i saw a new update here on xda, but when i click on system updates it tells me that my phone is running latest software version.
It's generic EU (reteu = retail EU afaik), as for the update it was pulled as some problems were found (don't know what mine seems fine) so you are on the latest at the moment.
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.
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.
Greetings folks, i have been reading a bit about changing the csc of the phone, I own a s21 Ultra G998B version and its branded with a owo rom, i live in Chile, and the Claro company of course is not up to date with the otas, and also i want to flash a clean rom with no bloatware. I read that with samkey i can change the CSC to an OXO (mine is owo) rom so i can then flash the muti csc rom. I also read that in order for samkey to work i have to roll back to may update? i'm currently on august update. am I correct in the process? can anyone recommend to which csc i can change so i won't turn my phone into a mess
thanks to all who can provide some light jeje
Isn't CHO the Multi-CSC Firmware for Chile?
varcor said:
Isn't CHO the Multi-CSC Firmware for Chile?
Click to expand...
Click to collapse
hi, yes it is, but i looked in samfirmware and the cho version is until august, so i think it would be the same? mine is chl which is for CLARO company and is also in august update, i would like september updates so i can try the andy 12 beta
When I bought it, it had May firmware. I changed CSC before any other update .
So , may update is working for SamKey.
Otherwise, you need to flash with latest Odin the may firmware of your CSC you want (downgraded)
Hello, could someone please tell me, is it possible to flash g998u1 with Thailand firmware, Chinese, etc?
Lexabogdanov said:
Hello, could someone please tell me, is it possible to flash g998u1 with Thailand firmware, Chinese, etc?
Click to expand...
Click to collapse
No to both. Thailand FW is configured for the Exynos SoC. The China FW, even though it's configured for the Snapdragon SoC it's not compatible with the US Unlocked variant. Do you live in Thailand? If so I'm curious why you aquired a US device. We often see users buying non native devices, maybe they got a good price, maybe they moved out of their region, maybe it's a company issued phone but it's a pain when call features or 5G don't align with your service provider. Flashing non stock firmware often causes more problems than it solves. Samsung is moving closer and closer to proprietary software for individual models, mix and match is becoming a thing of the past.
varcor said:
No to both. Thailand FW is configured for the Exynos SoC. The China FW, even though it's configured for the Snapdragon SoC it's not compatible with the US Unlocked variant. Do you live in Thailand? If so I'm curious why you aquired a US device. We often see users buying non native devices, maybe they got a good price, maybe they moved out of their region, maybe it's a company issued phone but it's a pain when call features or 5G don't align with your service provider.
Click to expand...
Click to collapse
I live in Kaliningrad, Russia. This device I've bought for 30usd, new, boxed,, here, in Russia, so I was looking for ways to make it work as a Russian device(full menu translation, bands, etc.). Actually no matter, which language is used, at first I had troubles using android 11-there was no esim. Than using abd I flashed it to oneui 4.0, esim works, all lte bands are supported.
Lexabogdanov said:
I live in Kaliningrad, Russia. This device I've bought for 30usd, new, boxed,, here, in Russia, so I was looking for ways to make it work as a Russian device(full menu translation, bands, etc.). Actually no matter, which language is used, at first I had troubles using android 11-there was no esim. Than using abd I flashed it to oneui 4.0, esim works, all lte bands are supported.
Click to expand...
Click to collapse
And 5G is not supposed for some years )))
Lexabogdanov said:
I live in Kaliningrad, Russia. This device I've bought for 30usd, new, boxed,, here, in Russia, so I was looking for ways to make it work as a Russian device(full menu translation, bands, etc.). Actually no matter, which language is used, at first I had troubles using android 11-there was no esim. Than using abd I flashed it to oneui 4.0, esim works, all lte bands are supported.
Click to expand...
Click to collapse
$30 USD is an awesome deal! If all bands and esim are functional that's probably as good as it gets. Unfortunately Exynos compatible FW which is dominant in Russia can't be installed on your device. Gboard may be your best option for Russian Language.
I have purchased this device from Wonda Mobile.
The customer service person has told me the original phone model is a Chinese NE2210. It will be flashed with NE2213 or NE2215 depending on region (I am from the UK so most likely NE2213?).
I was also told that the bootloader will be locked, payment app will work and the device will continue to receive updates.
My question, are the above true as far as you are aware?
Is it possible to flash a different region and leave the bootloader locked?
If it is possible to have the bootloader locked, I assume payments apps will work then?
Will the device continue to receive OTA updates if changed from NE2210 to NE2213 or NE2215?
Any possible issues I should be aware of?
I purchased the same device, originally NE2210, it was unpacked and flashed to NE2215 by the seller. The bootloader is locked, updates work normally, everything works great...
Thanks dzontra83. I used to be good at these things in the the golden days of modding our OnePlus phones and installing custom ROMS.
I read somewhere that you had to unlock your bootloader to change from NE2210 to NE2213 or NE2215. This is why I was a bit confused as to how the bootloader will come locked.
Feeling a bit more reassured that you have the same device with OxygenOS flashed.
Can I ask what region you are from as you have NE2215. I am led to believe NE2213 is for Europe?
dzontra83 said:
I purchased the same device, originally NE2210, it was unpacked and flashed to NE2215 by the seller. The bootloader is locked, updates work normally, everything works great...
Click to expand...
Click to collapse
does Netflix work in HD and is widevine level set to L1?
abdulhamid1978 said:
I have purchased this device from Wonda Mobile.
The customer service person has told me the original phone model is a Chinese NE2210. It will be flashed with NE2213 or NE2215 depending on region (I am from the UK so most likely NE2213?).
I was also told that the bootloader will be locked, payment app will work and the device will continue to receive updates.
My question, are the above true as far as you are aware?
Is it possible to flash a different region and leave the bootloader locked?
If it is possible to have the bootloader locked, I assume payments apps will work then?
Will the device continue to receive OTA updates if changed from NE2210 to NE2213 or NE2215?
Any possible issues I should be aware of?
Click to expand...
Click to collapse
My advice would be to get the NE2213 and avoid the chinese variants.
Sooner or later you'll hit a snag..
More to the point, I wouldn't buy this phone if I knew then what I know now.
dladz said:
My advice would be to get the NE2213 and avoid the chinese variants.
Sooner or later you'll hit a snag..
More to the point, I wouldn't buy this phone if I knew then what I know now.
Click to expand...
Click to collapse
Thanks, exactly what problems did you experience that has put you off? I am getting it as it is under £700 for a 12gb/512gb.
abdulhamid1978 said:
Thanks, exactly what problems did you experience that has put you off? I am getting it as it is under £700 for a 12gb/512gb.
Click to expand...
Click to collapse
I have not and would not buy a device out of region.. Reason being is because there are quite a few things that could go wrong..
Main one is warranty, and for what? So you can save a few pennies, that's a penny wise and pound foolish decision.
What will happen when OnePlus "fix" your device if it goes wrong? You'll end up back on the Chinese firmware.
Are the basebands the same? Will it work when 13 is released? Is preformance the same?
Each to their own, but i just wouldn't risk saving a small amount of money for the potential problems they may arise.
Look at the threads created by poor souls who attempted to save money.
zorbakun said:
does Netflix work in HD and is widevine level set to L1?
Click to expand...
Click to collapse
It is L1, i havent tried Netflix yet, but most certanly it is, since it is L1.
I'm considering doing exactly this. I want a 512GB phone and the only option is the CN white panda. Can't do it otherwise. Was hoping for the 10T to offer 512GB but it ended up not (also is a downgrade in many areas)
Olao99 said:
I'm considering doing exactly this. I want a 512GB phone and the only option is the CN white panda. Can't do it otherwise. Was hoping for the 10T to offer 512GB but it ended up not (also is a downgrade in many areas)
Click to expand...
Click to collapse
Received delivery, transferring everything (apps + data) over from the current phone.
It was flashed to NE2215, not sure if this is correct for UK.
Hopefully it will receive OTA update. It came with Feb 22 security patch. It is updating to Jun 22 security patch.
Phone looks great though.
abdulhamid1978 said:
Received delivery, transferring everything (apps + data) over from the current phone.
It was flashed to NE2215, not sure if this is correct for UK.
Hopefully it will receive OTA update. It came with Feb 22 security patch. It is updating to Jun 22 security patch.
Phone looks great though.
Click to expand...
Click to collapse
Ne2215 is global afaik, UK is NE2213
Probably would have preferred NE2213. Not sure how the seller flashed it or if there is any downsides to NE2215
abdulhamid1978 said:
Probably would have preferred NE2213. Not sure how the seller flashed it or if there is any downsides to NE2215
Click to expand...
Click to collapse
Slower updates for sure..
zorbakun said:
does Netflix work in HD and is widevine level set to L1?
Click to expand...
Click to collapse
How do you check if Netflix is in HD? Mine shows widevine security level 1 according to the DRM info app.
abdulhamid1978 said:
How do you check if Netflix is in HD? Mine shows widevine security level 1 according to the DRM info app.
Click to expand...
Click to collapse
You have to open Netflix app
abdulhamid1978 said:
How do you check if Netflix is in HD? Mine shows widevine security level 1 according to the DRM info app.
Click to expand...
Click to collapse
open Netflix app, then go to settings->playback specifications and you will find if yours support HD & HDR playback.
This is what it shows
abdulhamid1978 said:
View attachment 5679285
This is what it shows
Click to expand...
Click to collapse
and your oneplus 10 pro is chinese NE2210 converted to global by seller?
zorbakun said:
and your oneplus 10 pro is chinese NE2210 converted to global by seller?
Click to expand...
Click to collapse
Yes, NE2210 converted by seller to NE2215. Came in box with Feb22 security patch and it updated OTA to Jun 22 after I received it.
abdulhamid1978 said:
Yes, NE2210 converted by seller to NE2215. Came in box with Feb22 security patch and it updated OTA to Jun 22 after I received it.
Click to expand...
Click to collapse
Thank you & Enjoy your phone.
Is there any way to activate call recording if not using the India rom or rooting?