How does Hauwei firmware naming scheme work? - Huawei Mate 20 Pro Questions & Answers

Just looking on Firmware Finder and just wondering about these full firmware files and whats the difference between them
LYA-LGRP2-OVS 9.0.0.xxx - Base firmware?
Laya-LGRP2-OVS 9.0.0.xxx - Base firmware intended for carrier customization?
Laya-L0CCCxxxxxxxxx - Carrier customized build and their build number adds onto what ever base it was created from... but any future base firmware releases ignore this increase
FullOTA-MF (MF means multi file e.g. more than one update is contained in the package.... What does this mean, that it contain updates for both L09 and L29 or something else?)
FullOTA-MF-PV (PV means point version and is used to move between android versions e.g. 7 to 8" but that can't be the case unless we have android 10 as there is a M2P firmware with that listed as its type)

Xalies said:
Just looking on Firmware Finder and just wondering about these full firmware files and whats the difference between them
LYA-LGRP2-OVS 9.0.0.xxx - Base firmware?
Laya-LGRP2-OVS 9.0.0.xxx - Base firmware intended for carrier customization?
Laya-L0CCCxxxxxxxxx - Carrier customized build and their build number adds onto what ever base it was created from... but any future base firmware releases ignore this increase
FullOTA-MF (MF means multi file e.g. more than one update is contained in the package.... What does this mean, that it contain updates for both L09 and L29 or something else?)
FullOTA-MF-PV (PV means point version and is used to move between android versions e.g. 7 to 8" but that can't be the case unless we have android 10 as there is a M2P firmware with that listed as its type)
Click to expand...
Click to collapse
So you mean if I can use LYA-LGRP2-OVS 9.0.0.xxx or Laya-LGRP2-OVS 9.0.0.xxx to upgrade my LYA-L09? ... And another question, what are the regions and numbers that exist for mate 20 pro? (CUST)

Related

Honor 7 L01 B130 to ?????? ?

I have Honor 7
PLK-L01c185b130 Android 5.0.2
i had never update it
What version need i to update it to latest stock firmware android 6 or higher ?
c185? it's from the middle east region, right?
Honestly I'm not familiar with your model, so my suggestion is: download Firmware Finder from the Play Store, and check for the latest firmware available it automatically detects your model, gives you a list with all the updates available (both incremental and full OTA), and this way you are sure to choose the right file.
ypu can download latest firmware from huawei site and flash it manually to update

Update from 8.1 to 9 but still showing update available

Hi guys,
today i updated my Honor 10 from COL-L29C432B151 (8.1.0.151) to COL-L29C432E4R1P9B159 (9.0.0.159).
At build no it now shows COL-LGRP2-OVS 9.0.0.177.
But it still tells me that there is an update available (which won't OTA because device is rooted etc.)
I thought i used the latest version available
At Firmware finder is see
Col-L29DC10E3R1P13T8B177 (9.0.0.177),COL-LGRP2-OVS 9.0.0.177 as OTA-MF and
Col-L29DC10E3R1P13T8B177 (9.0.0.177) as FullOTA-MF (what i think i need).
Do i have to update to one of those
I think that's the small update for fixing camera app and call issue.
It looks like you get an Firmware for another device? Firmwarefinder (Andropidapp) Shows only .159. for the Honor 10 COL-L29C432.
FunkyHuawai shows also the .159 as latest firmware: https://funkyhuawei.club/fulllist
Only a patch. See the screenshot below.
i'm just a bit confused right now.
In the past my build version was like COL-L29 8.1.0.151(C432).
Yesterday i flashed COL-L29C432E4R1P9B159 (9.0.0.159) LINK
And now it looks like this:
Why is the regional code C432 missing?
Can i now flash every firmware?
There is a 9.0.0.160 available
COL-L29C10E3R1P12B160 (9.0.0.160)
Click to expand...
Click to collapse
i think this is for russia.
The latest firmware i can find for col-l29c432 is the one i just flashed yesterday: COL-L29C432E4R1P9B159 (9.0.0.159)
So why is my phone showing an available patch?
Don't they create a new firmware for every patch?
Or is the latest one just missing in huawei firmware finder?
just officially updated
best regards
Mine's now also on the latest patch: 9.0.0.159(patch01) and not showing update available any more.
But it still doesn't show C432 and the other stuff..?
Still confused

Emui 9, Android 9 DOWNLOAD for P10, P10 Plus, Honor 9, Mate 9 - open beta update

https://www.getdroidtips.com/download-android-9-0-pie-beta-for-huawei/
You're welcome
Just notice:
The regions for the P10 firmware are limited to Latin America, Argentina und China.
Don't flash the firmware before rebranding your phone! It's also possible that you can't use the mobile network in your country with a firmware from a different region.
The Chinese versions, AL00 and TL00 don't have Google services including play store installed.
So, don't install anything without knowing what you do
I still wait for C432E1R1P8 and try flash to Pie Beta ??*
Jannomag said:
Just notice:
The regions for the P10 firmware are limited to Latin America, Argentina und China.
Don't flash the firmware before rebranding your phone! It's also possible that you can't use the mobile network in your country with a firmware from a different region.
The Chinese versions, AL00 and TL00 don't have Google services including play store installed.
So, don't install anything without knowing what you do
Click to expand...
Click to collapse
Do you have to rebrand first? What happens if you don't rebrand before flashing this?
I read that it will make you region C900 but nobody said if C900 is a problem. It's just the international version.
So you could still use the phone on region c900 right?
Possibly single/dual sim will be affected?
I don't know if it works different with pie, but my last information is, that you can't install it. The recover, even the NoCheck version, checks the oeminfo partition first. I also never heard about C900 VTR models, the international version without branding is C432, while this code is for France / Western Europe on older devices.
It can happen, that your phone shows developer version. Then you'll have some problems to rebrand to a real version with pie, because there are no oeminfo files for pie, yet.
If your phone is in developer mode, you're able to use it as normal but you won't be able to update via OTA or even with methods like HWOTA8.
Is it worth to upgrade to Android Pie 9.0 ? Does anybody has some experience with it ? I read somewhere that 9.0 works much more with Ai algorithms. Like prediction, etc. Beside that Ai for OS usability i am more curios if / interested in:
- if it uses less RAM memory
- if it use less battery power
- if it has a performance boost overall
If all of this points are opposite on 9.0 , i don´t see any benefits in it.
Sledgeham said:
Is it worth to upgrade to Android Pie 9.0 ?
Click to expand...
Click to collapse
This thread not for discussion of why or worth just talk about the installation and questions about how to install please.
Jannomag said:
I don't know if it works different with pie, but my last information is, that you can't install it. The recover, even the NoCheck version, checks the oeminfo partition first. I also never heard about C900 VTR models, the international version without branding is C432, while this code is for France / Western Europe on older devices.
It can happen, that your phone shows developer version. Then you'll have some problems to rebrand to a real version with pie, because there are no oeminfo files for pie, yet.
If your phone is in developer mode, you're able to use it as normal but you won't be able to update via OTA or even with methods like HWOTA8.
Click to expand...
Click to collapse
What if we rebrand to version C605 which is this 9.0 firmware region then flash the rom.
Theoretically if this is the first firmware available in europe for Pie then we should get an update of final version soon after right?
So won't need to rebrand later and by that time Pie will be full release??
The main concern is to make sure bootloader code does not change during rebranding because then we're stuck.
fatjoez said:
What if we rebrand to version C605 which is this 9.0 firmware region then flash the rom.
Theoretically if this is the first firmware available in europe for Pie then we should get an update of final version soon after right?
So won't need to rebrand later and by that time Pie will be full release??
The main concern is to make sure bootloader code does not change during rebranding because then we're stuck.
Click to expand...
Click to collapse
C605 is for Latin America / Columbia. If they use other network frequencies than Europe and Huawei specified those frequencies in the firmwares than you're not able to use it here.
But yes, you should be able to rebrand to C605 by flashing the correct oeminfo. Rebrand on Oreo first before you update to Pie.
The bootloader code shouldn't change because of rebranding, it's hard coded into the bootloader and Huawei uses serial, model number (not region) and IMEI to make the code, those information won't change.
If you'll get updates while using a phone in a different region as the firmware says, isn't clearly, yet. Huaweis update plitics are a miracle, some guys still stuck on Nougat, some guys are getting the newest updates.
Update manually if you want to be up to date.
Guys I'm from Argentina and want to install emui 9. Tried to move to SD but fat32 has 4gb files limit. Is there any way to install it from internal storage?
Format SD to NTSF
So, did anybody from Europe rebranded and got it working with gsm properly? If so, to which region did u rebranded? Thank you.
Good evening to everyone. Is there a twrp for p 10 EMUI 9? Thank you

Convert C432 to OVS

Hi There,
currently I have the C432E10R1P16 LYA29 Dual Sim Version on my Mate 20 Pro.
I want to go for a faster update ring, I even found a full_update_base zip for the LYA-LGRP2-OVS 9.0.0.320 but I cannot migrate to that.
I tried hisuite but it won't help... I tried reverting to an older release which is funny cause it downloads this folder : LYA-LGRP2-OVS 9.0.0.266 so I thought, I should be able to update... but no...
Any Idea Recommendation? Thanks!!
OVS are globale version and usable on L09 and L29 but flashing should be make with dload method. no over way. Keep it mine that safetynet will not pass coz it's not a C432 region specific firmware.
latest "legit" version for C432 is 9.1.0.301
ilos said:
OVS are globale version and usable on L09 and L29 but flashing should be make with dload method. no over way. Keep it mine that safetynet will not pass coz it's not a C432 region specific firmware.
latest "legit" version for C432 is 9.1.0.301
Click to expand...
Click to collapse
it is interesting though that the directory what Hisuite automacially created and downloaded for me so I can revert to a different version (emui 9.0)
was LYA-LGRP2-OVS 9.0.0.266 so if I have the C432E10R1P16 LYA29 why did it install this for me automatically? for me it would be reasonable to think that : LYA-LGRP2-OVS 9.0.0.320 should be working as well.. but I cannot install not even with the dload method.... even the 310 would not work with the dload version (with C432) I don't really understand it

F707U AT&T Odin Firmware Links

For those who don't know, F707U is the model number of all of the US carrier versions of the Galaxy Z Flip 5G. The F707U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. These are much tougher to find than other carriers' files due to AT&T's policy against public hosting of their firmware files - they can't be obtained from SamFirm or Frija or SamMobile. But I pay for a subscription to a site that gets AT&T files, and also sometimes gets other carriers' firmware files before they hit SamFirm/Frija, so that's where my files come from.
So I'll be uploading at least one USERDATA for each bootloader version, and I'll do the full firmware (for at least one build per bootloader level) if AT&T was the only carrier to get that specific build.
Since firmware is universal on U models, for a full flash you can use the other 4 Odin files (BL, AP, CP, CSC) from any other firmware of the same build. You can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. You can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader level.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=318351
NOTES:
- I won't be providing detailed instructions on how to flash files in Odin. If you're not aware of how to do that, there are countless "beginner's guide to Odin flashing"-type threads here on XDA already
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- If the phone doesn't do it automatically, the correct procedure for manually switching from one carrier's firmware to another is:
1. With no SIM inserted, flash the full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
- USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija - for the latest version. If you need an old USERDATA for a CSC/region that's not commonly found, let me know and I can probably get it.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Do you have the tmobile or the unlocked userdata?
BTW samfirm or freya do not have any f707u firmaware
jacllondon said:
Do you have the tmobile or the unlocked userdata?
Click to expand...
Click to collapse
iBowToAndroid said:
USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija
Click to expand...
Click to collapse
jacllondon said:
BTW samfirm or freya do not have any f707u firmaware
Click to expand...
Click to collapse
Yes, you absolutely CAN get F707U firmware from Frija
iBowToAndroid said:
Yes, you absolutely CAN get F707U firmware from Frija
Click to expand...
Click to collapse
thanks.
You were right. Iwas putting f707u with error. it needed to be sm-707u....Newby mistake lol
What is the csc of unlocked?
jacllondon said:
thanks.
You were right. Iwas putting f707u with error. it needed to be sm-707u....Newby mistake lol
What is the csc of unlocked?
Click to expand...
Click to collapse
XAA
Thank you. So I flashed everything with odin. Trying to de brand from att to unbranded. I flashed successful but the att logo and bloatware are still there. tried to use Tmobile user data, but does not overwrite theatt one. Am I doing something wrong? maybe forgetting a step to delete att userdata before flashing tmb's one? Thank you
---------- Post added at 05:47 PM ---------- Previous post was at 05:08 PM ----------
nevermind. I used a patched odin and flashed the XAA... thank you
iBowToAndroid said:
For those who don't know, F707U is the model number of all of the US carrier versions of the Galaxy Z Flip 5G. The F707U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. These are much tougher to find than other carriers' files due to AT&T's policy against public hosting of their firmware files - they can't be obtained from SamFirm or Frija or SamMobile. But I pay for a subscription to a site that gets AT&T files, and also sometimes gets other carriers' firmware files before they hit SamFirm/Frija, so that's where my files come from.
So I'll be uploading at least one USERDATA for each bootloader version, and I'll do the full firmware (for at least one build per bootloader level) if AT&T was the only carrier to get that specific build.
Since firmware is universal on U models, for a full flash you can use the other 4 Odin files (BL, AP, CP, CSC) from any other firmware of the same build. You can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. You can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader level.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=318351
NOTES:
- I won't be providing detailed instructions on how to flash files in Odin. If you're not aware of how to do that, there are countless "beginner's guide to Odin flashing"-type threads here on XDA already
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- If the phone doesn't do it automatically, the correct procedure for manually switching from one carrier's firmware to another is:
1. With no SIM inserted, flash the full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
- USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija - for the latest version. If you need an old USERDATA for a CSC/region that's not commonly found, let me know and I can probably get it.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Click to expand...
Click to collapse
What (if any) are the differences between the US models (F707U) and the European models (F707B)? Can European builds be applied to US models? I'm asking because Android 11 has been released for the European models but not the US ones yet.
Stuart R said:
Can European builds be applied to US models? I'm asking because Android 11 has been released for the European models but not the US ones yet.
Click to expand...
Click to collapse
Nope
AT&T USERDATA for Android 11 has been added - build TL6.
I also added the full firmware package because I didn't see that anyone else had uploaded it on AFH yet.
From now on, you can expect AT&T USERDATAs to be added right away, when new bootloaders and new Android versions are released
iBowToAndroid said:
Yes, you absolutely CAN get F707U firmware from Frija
Click to expand...
Click to collapse
Indeed. I've downloaded two Android 11 releases there!
Hey, I have a SM-F707U ATT and it doesn't have One UI 3 so what should I flash on it to get One UI 3? sorry of the question is too noob
bhoot1234567890 said:
Hey, I have a SM-F707U ATT and it doesn't have One UI 3 so what should I flash on it to get One UI 3? sorry of the question is too noob
Click to expand...
Click to collapse
Idk which update added One U1 3.0. I guess flash Android 11 and see if that has it
Bootloader 2 firmware has been added, along with the AT&T USERDATA - build ending in UD9
One UI 3.1.1 for U firmware was just added - go get it if you're interested!! Build UH4
One U1 3.1.1 has now been released for U1 firmware as well - available via the various firmware download tools
Android 12 full firmware and AT&T USERDATA has been added - build UL9
Hello, do you have the latest att firmware, thank you very much for sharing!!
luookeee said:
Hello, do you have the latest att firmware, thank you very much for sharing!!
Click to expand...
Click to collapse
I see you haven't read the OP.
"....any U or U1 firmware version can be flashed to any U or U1 device at any time...."
iBowToAndroid said:
I see you haven't read the OP.
"....any U or U1 firmware version can be flashed to any U or U1 device at any time...."
Click to expand...
Click to collapse
Of course I saw it. I'm just worried about what's different. Let me try it thank you!!

Categories

Resources