Since the official Mango has been released yesterday, there is finally a new version available. Since i've installed the developer release, i didn't got the update but i thought that since the version number was the same, i didn't miss anything.
Lately i've found more sources that claim that some firmware versions have been updated so i'm wondering if i should update to the official version.
I've also seen that the official mango release is stated as the KH5 version, opposed to the KH2 version i'm currently running right now and was the developer release.
So mainly my question is: what are the big differenses between the official mango release (KH5) and my developer release (KH2)?
With the new firmware versions now available: has batterytime improved? I find the current batterytime (1 day and 8 or 16 hours) a bit low, so i'm hoping that power management has been improved?
And lastly: i've updated to the developer release including the CSC that came with it. At the time (flashing) i didn't realise it would mess up my provider information. I got rid of most of the branding, but the boot up and default search provider remain T-Mobile (German) which is somewhat annoying. What CSC do i need to download/use in order to get back to my original unbranded T-Mobile Dutch version i bought in the shop? I cannot seem to find one that, i think, is what i need, namely a XEN-type CSC.
I own the Canadian P20 pro variant (CLT-L04) and just installed a recent official OTA firmware update for it - version 8.1.0.111 (from 8.1.0.009). My device started with 8.1.0.007.
I've been debating about rebranding in order to get the more recent firmware updates which appear to be up to version 8.1.0.132 (?) worrying that I was missing the more recent features.
But after checking out the changes in this firmware I realized that I have many of the same features of the supposedly more recent firmwares such as:
1. The new zoom button in the camera interface placed at the bottom of the screen in the shape of a square.
2. The new slow motion box that detects movement and starts the super slow motion automatically.
3. ISO select up to 102400 is Pro mode.
4. Camera defaults to 2x mode in aperture mode (not a fan on this)
5. The HiTouch feature accessible through the camera (the eyeball icon - top left) or by touching the screen with two fingers
6. Latest security patch is for June 1st, 2018 (this is behind some other firmwares I believe that have July patches?)
7. Selfie beautification is much lower .
I'm not sure what other features I'm missing out on compared to the supposedly more recent firmwares but these seem very similar to what are being reported in firmware 8.1.0.132.
Does this mean that Huawei releases different features by region even if the firmware has the same version number? In other words, firmware version 8.1.0.11 in Canada will have features that 8.1.0.11 in another country does not? This means one cannot directly compare firmwares by version number alone and assume they are equivalent in terms of features and changes across devices.
Anyone else running 8.1.0.11 on any other variant who can check whether they also have the features I've observed in my firmware version?
So confusing :
In any case, I'm much less concerned about rebranding now that I seem to have some of the more recent firmware changes.
I'm not 100% sure, but my opinion is that different regions elaborate in different speed the base firmware.
I am not speaking about minor country differences, but major like: Eu, China, Russia, US, Canada etc.
For example:
european firmware numbers are far ahead of china firmware numberings, however, eu firmwares lack a lot of functionality, that cn firmwares had already
(eu fw CLT-L29C432B132 has the functions, that CLT-AL01C00B112 cn firmware already had)
So i am assuming, that this happens in your case.
One prove is FF - look at the changelogs: despite one has july patch, however another from june patch has a lot more improvements
And about FF speaking: always take a look at version numbers ex:
CLT-L04C792B113 (8.1.0.113) FullOTA-MF 3.43 GB 2018.07.11 3085 1604 version nr: 154641 1
CLT-L29C432B131a (8.1.0.131a) FullOTA-MF 3.3 GB 2018.07.05 2943 1604 version nr: 150210 1
How did you get 111 in Canada? Ota won't update past 109 for me
viper98 said:
How did you get 111 in Canada? Ota won't update past 109 for me
Click to expand...
Click to collapse
u the same viper98 from rfd?? lmao
for me, im on 109 as well. No available updates.
Thanks tamaskurti for your observations and explanation.
As for other Canadians on firmware 109 all I did to get the update is manually check by pressing the "check for updates" button in the system ->system updates page.
I use firmware finder to check for new firmwares only. The OTA updates come a little more than a month after the date that is listed in the firmware finder description.
E.g., firmware 111 was dated June 14th and I received it July 20th.
UPDATE: There is yet another update on FF for version 113 for the Canadian model. It is dated July 11th so I expect to see the OTA update middle of August if this pattern holds.
BTW I'm with Koodo mobile (Telus) and bought the phone through them. Maybe they are faster to approve the firmwares than Bell or Rogers and thats why some of you are getting it later? Just a guess.
I'll try to keep this thread updated with any other firmware changes that I notice when I receive . 113
Weird. I checked with a koodo sim in Thursday and it didn't find anything
oraos said:
Thanks tamaskurti for your observations and explanation.
As for other Canadians on firmware 109 all I did to get the update is manually check by pressing the "check for updates" button in the system ->system updates page.
I use firmware finder to check for new firmwares only. The OTA updates come a little more than a month after the date that is listed in the firmware finder description.
E.g., firmware 111 was dated June 14th and I received it July 20th.
UPDATE: There is yet another update on FF for version 113 for the Canadian model. It is dated July 11th so I expect to see the OTA update middle of August if this pattern holds.
BTW I'm with Koodo mobile (Telus) and bought the phone through them. Maybe they are faster to approve the firmwares than Bell or Rogers and thats why some of you are getting it later? Just a guess.
I'll try to keep this thread updated with any other firmware changes that I notice when I receive . 113
Click to expand...
Click to collapse
Looks like it updated to .114 now. Just an FYI
Being behind on updates feels bad
I just got 111 pushed today
tried on my koodo sim
still nothing there either
With Bell, just received the 111 update. How do we go about rebranding? Wouldn't mind trying a new Rom
Hi is it possible to flash an S10 Exynos from the Vodafone branded firmware to the plain unbranded firmware?
If so is anybody able to point me in the right direction for a guide to doing so? The phone is already network unlocked, I just want to get updates at the same time as everyone else, at the moment I'm still on the July security patch for example.
I've searched through a lot of results but am really struggling since the words 'unlock', 'firmware', 'flash', 'stock' etc come up in so many threads.
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. ?
Hello everyone I live in th u.s. and use my a71 on att. I bought my phone at rent a center and it has buc1 firmware and the csc is TTT (Trinidad and tobago). I would like to install a custom rom because I recently rooted and the smartview feature which I use often isn't working right and none of the fixes are either. My question is this: which firmware should I install to get a clean slate and possibly try a custom rom? Not sure why a phone in the US was sold with Trinidad firmware. I would prefer not to flash the stock ttt firmware if possible is there a better option? Thanks guys
hi friend, I have been almost in same situation (different country) and i would like to share with you my experience maybe it will help if you are still looking. some options / features included in the ROM / OS depend on where the device was sold or aimed to be sold initially by Samsung, for example 2 phones same model, same tech specs, same android version, if one is old in Europe with a certain firmware, it may not have same all options / features as same one sold in US or elsewhere .... i bought a device sold initially in Italy and couldn't find samsung pay or fm radio app in it (even that device does support it from hardware side) and not possible to install it as third-partie app either in anyway possible, and it didnt show up even with a custom ROM .... so i did some dig in and found THAILAND firmware for same android version have it by default + others things i was looking for such as native call recording .... basically long story short, as longer you already rooted it, we can forget about warranty, which should gives you more freedom to install wharever you want ... a custom rom is specially to enhance perf by removing some apps and adding some more features that arents includeed in stock firmware ... but if you are okay with basic stock firmware and all its apps and contenents you don't have to install ncessarry a custom rom ... you can juts look for a specific firmware REGION/COUNTRY that have the option you are looking for and go fo it, like i did from Italy to Thailand (while im living in whole different country of those two), and all will be working fine for you ^^