Database Develop

Convert UL00 to L09 and Update to B303

Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.

Tuerkay said:
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Click to expand...
Click to collapse
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09

brumgav said:
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
Click to expand...
Click to collapse
change oeminfo back to dualcu/cn or leave as hw/meafnaf?

Tuerkay said:
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Click to expand...
Click to collapse
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post

brumgav said:
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
Click to expand...
Click to collapse
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version

Tuerkay said:
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Click to expand...
Click to collapse
Have you done a factory reset during any of the above?

brumgav said:
Have you done a factory reset during any of the above?
Click to expand...
Click to collapse
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.

Tuerkay said:
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Click to expand...
Click to collapse
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on

brumgav said:
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
Click to expand...
Click to collapse
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
i currently have no permission manager and no mobile data manager

Tuerkay said:
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
Click to expand...
Click to collapse
I think I wrote CRR-L09C432B114

@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.

bgx said:
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
Click to expand...
Click to collapse
tried many different things but nothing worked. Now i´m back at C433B114 until someone finds a solution.
I´m missing so many functions but i won´t change back to C00B160 because my main language isn´t supported well enough

Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?

Iverom said:
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Click to expand...
Click to collapse
European version only supports 1 SIM

Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?

plantunes said:
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
Click to expand...
Click to collapse
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.

Tuerkay said:
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Click to expand...
Click to collapse
Do you have a CL00 converted into a L09?
If you do, you could change that string "ro..dual.sim.phone" into TRUE and see what happens. It would be absolutely great if that was possible!

I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.

Lightofdarkness666 said:
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Click to expand...
Click to collapse
Flashed all files and then tried a clean update. Didn´t work. My Mate S shows the right Build and Vendor but i´m still not able to use the C432 Update.app´s.
Are you able to update manually?
Is your phone originally an L09 or UL00 device? If it´s an UL00 Mate S, could you tell me exactly what you did?

My phone is originally an L09, but i broke it in UL00C00, can't get back to L09, recovery don't boot, flash via fastboot lead to freeze at boot

Dload for p8 lite 2017

Someone help me! Please!
Why I can't flash anything with dload method? I have tried lots of things: stock recovery, twrp, erecovery, proxy. But nothing. I tried to use firmware finder too for download an update fullota (of course, all the 3 ZIP package) and tried to put in dload the zips, the update.apps, but won't work. For dload I mean the three buttons method. It gives me always failed, at 5%, with the error "Software Install Failed". Please help me! I tried to toggle signature too to the firmware with huawei firmware extractor but not working. How I can flash firmware (especially firmware founded with firmware finder) using dload method? Please help me and my friends! Thank you to everyone!

These beta build found by firmware Finder might be not enable to be installed on your device. Use the latest check with EMEI to know if it fits.

Gazatus said:
These beta build found by firmware Finder might be not enable to be installed on your device. Use the latest check with EMEI to know if it fits.
Click to expand...
Click to collapse
I'm sorry didn't get the last part. Can you clarify it please ?
I'm on the same boat as the op. With the firmware finder I can only find PRA-LX1C33B130 but like op said, it stops at 5%. The firmware for my phone is PRA-LX1C33B120, but I can't find it anywhere. Right now my phone is bricked because I really can't find any version to install it.

Update firmware Finder, select the update you want and hit "check......" then it will now ask you for IMEI compatibility check
For me, Ive found more than 10 firmwares, I'm on B110 and there is up to b125... Nevertheless I can't install the proxy add-on, I can't use their "register with dns" feature, and I can't past the 5% threshold on dload flash. It seems to be not working at all for pra-lx1. I'm on stock B110 update (phone came with b100 and the B110 update was a legal ota without any mods).
Did you try to send a mail to huawei support team? Explain that you are a dev and you need to stock rom. They may send you a link share it please!

Gazatus said:
Update firmware Finder, select the update you want and hit "check......" then it will now ask you for IMEI compatibility check
For me, Ive found more than 10 firmwares, I'm on B110 and there is up to b125... Nevertheless I can't install the proxy add-on, I can't use their "register with dns" feature, and I can't past the 5% threshold on dload flash. It seems to be not working at all for pra-lx1. I'm on stock B110 update (phone came with b100 and the B110 update was a legal ota without any mods).
Did you try to send a mail to huawei support team? Explain that you are a dev and you need to stock rom. They may send you a link share it please!
Click to expand...
Click to collapse
That option is on android right ? I can't use it, so I was trying with the windows version but it doesn't have any option for checking the firmware (or at least i'm not finding it). ~
Well after you said that there is a option to check the firmware the only one that I found (PRA-LX1C33B130) when I checked the firmware it said that It was not approved to install. I guess that is why it stops at 5% ? maybe ? hopefully the firmware status goes to approved somewhere in the neaaarr future.

squallx85 said:
That option is on android right ? I can't use it, so I was trying with the windows version but it doesn't have any option for checking the firmware (or at least i'm not finding it). ~
Well after you said that there is a option to check the firmware the only one that I found (PRA-LX1C33B130) when I checked the firmware it said that It was not approved to install. I guess that is why it stops at 5% ? maybe ? hopefully the firmware status goes to approved somewhere in the neaaarr future.
Click to expand...
Click to collapse
I get software Install Failed at 5% using dload ALWAYS! Even with authorized/allowed firmware. I'm thinking that dload on Huawei p8 lite 2017 is not working at all.

Simple UPDATE of EVA-L19C636B190 to Nougat FAILED

Hello guys,
I have failed. And now I do not know how to continue.
My tragic storry: I wanted to update my HUAWEI P9 from Marshmallow to Nougat and got an error during update, because I am an idiot. I took an (wrong) update from some site, putted it in a dload folder on a sd card and started the update. The update started, the phone rebooted and continued. But at 5% comes "Software update failed! Incompatibulity with current version. Please download the correct update package."
After that I started to search for a solution.
Now I found this site and it seems that here are a lot of people, that are able to solve such problems between wakeup and teeth brushing. I hope someone here can help me with good advices, which avoid me of damaging my phone completely and bring me instead on the way that I can solve my problem.
Enough of the chatter, this is my current knowledge (correct me if I am wrong):
I have (had) a P9 with EVA-L19C636B190 Firmware. (I have noted this before update)
L19 stands for the dual sim P9.
C636 is the Asia/Pacific Hardware
B190 was the old version of stock Android (Marshmallow)
(I know now, that I have tooked the wrong Hardware-Package. I should have taken C636 and
everything would have become beautiful)
As I understand, the wrong Firmware is now on my phone and the bootloader try to continue the update each time I start an Update.
If I start the phone normaly, I get the EMUI logo with the options to "Download latest version and recovery" (No way, with the wifi connection, he can not find a server to download), "Reboot" and "Shutdown".
I suppose, that there is a partition on my phone, where the wrong update file was loaded to. Because if I try to "update" back to EVA-L19C636B190, there is no difference, the update ends at 5%, even without a sd card. So I think, that I need to clear this partition and need to start an update with the dload-folder-method again.
As I understand some artikles here, I need for that a special tool (SRK), with which I can clear the partition in the FASTBOOT&RESCUE MODE. But for that the phone must be unlocked.
In next step I need to unlock the boatloader with the huawei online tool where i get the unlock code based on my serial number and so on.
What would you say to my plan? Or is there an easier method?
What do I need for that?
Please be indulgent with me, I try to learn and to undestand to solve my problem
Thank you in advance.

strange rebrand clt-l09 to clt-29 c432

i make rebrand to my p20 pro clt-09 to clt-29 c432 but after install i have new strange version !! its clt-l29 chipset-boston 8.1.0.001 ( 01FL) !! so what is this

Have you copied and edited oeminfo.bin via adb?

i also got the same problem. also my phone is unrecognized from PC......if i want to transfer file to pc i need to rebbot into twrp, then PC will recognize my phone again...dont know if this problem is related
is there any way to solve this..i already flash vendor.img using fastboot but cannot flash verlist.img (if the build number is in verlist.img)
i read the forum say that flash version.img will correct this problem....but in our FW there is no version.img

https://forum.xda-developers.com/showpost.php?p=76473957&postcount=1
Follow the steps for rebranding (especially part with oeminfo).
If you have root access You can also download oeminfo from link directly to your phone and follow edit commands for edit via some terminal app directly on phone since you don't have adb connection.

I also got this strange build name after I tried to rebrand my P20 Pro from CLT-L09 8.0.0.110(C782) to CLT-L29(C432) using FunkyHuawei
I'm not sure what are the implications. Which region is 01FL? It seems to be stuck on the very first version (8.1.0.001) and no update is available
What should I do?

I have same problem after rebranding Clt-L04 to Clt-l29, I have chipset-boston 8.1.0.001 (0193), I want to know what 0193 ?, is that we can do update

Ok I think I can help because I reversed this issue like 5 minutes ago. Take note, my device is a CLT-L09. I flashed a file for the CLT-L29 instead and caused myself problems.
You need the huawei firmware finder app
Once you have that app installed, put in your model number and download the files for your model. You need the public, hw and update.zip files (You will see those words in the 3 files, I believe in you, you can do this)
Flash these files with HurUpdater. See here and follow instructions: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you did this right you should see the correct model and software info in About Phone
Let me know if this wasn't clear enough

So I'm also getting the chipset-boston model problem, can anyone elborate a bit more on how to fix this? I've gone thru the steps 3 times and no change. Any further software installs fail at 5%. The first one went through no problem.

Can you give any more info so that I can try help? What model is your phone etc? What files did you download and flash?

I solved it by rooting and deleting the oeminfo folder in data/local/tmp directory and then copying the oeminfo file to data/local/tmp. All commands then ran without error.

~ Just wondering,, I have a CLT-L09(C782) Huawei P20 Pro in UK and I did the *# dial and it said my chipset-boston 8.1.001 is this normal.....
I have no root,, not even attempted,, only official software from Huawei OTA updates thats all... I wouldn't root as on contract..

Nor receiving updates anymore

I have been using firmware finder to update my PRA-LX1. Now as I can see I don't receive any official updares. I'm stuck at security patch June. Even though July update is available when I check for updates in System Update it sais 'No updates'.
Any solutions?

FullOfMysteries said:
I have been using firmware finder to update my PRA-LX1. Now as I can see I don't receive any official updares. I'm stuck at security patch June. Even though July update is available when I check for updates in System Update it sais 'No updates'.
Any solutions?
Click to expand...
Click to collapse
I guess you are on Oreo.
Go to the firmware finder and find the list of firmwares and which correspond to the July security update,and check if it is approved for installation,if it is then go ahead and press update through VPN and follow the instructions.
Choose OTA not FullOTA if you are on Oreo,since it also took me a while to get the update.

dinoderda said:
I guess you are on Oreo.
Go to the firmware finder and find the list of firmwares and which correspond to the July security update,and check if it is approved for installation,if it is then go ahead and press update through VPN and follow the instructions.
Choose OTA not FullOTA if you are on Oreo,since it also took me a while to get the update.
Click to expand...
Click to collapse
so you're saying that firmware finder works on oreo if I choose the OTA firmware?
the problem is that firmware finder doent seem to work on oreo. Even though the update is approved, with vpn started the System Update app says 'No updates'.

FullOfMysteries said:
so you're saying that firmware finder works on oreo if I choose the OTA firmware?
the problem is that firmware finder doent seem to work on oreo. Even though the update is approved, with vpn started the System Update app says 'No updates'.
Click to expand...
Click to collapse
Oh really? I haven't really tried it on Oreo so I don't know,try updating it the manual way through dload,you can find how to do this on the forums.

dinoderda said:
I guess you are on Oreo.
Go to the fi mairmware finder and find the list of firmwares and which correspond to the July security update,and check if it is approved for installation,if it is then go ahead and press update through VPN and follow the instructions.
Choose OTA not FullOTA if you are on Oreo,since it also took me a while to get the update.
Click to expand...
Click to collapse
dinoderda said:
Oh really? I haven't really tried it on Oreo so I don't know,try updating it the manual way through dload,you can find how to do this on the forums.
Click to expand...
Click to collapse
I have tried different types of the Dload method but no one ses to work. I tried something from the WAS-LX1 SD CARD UPDATE GUIDELINE but using an update for this phone. Well, even if that update is available for update, with the dload method it says that 'The update package is not compatible with the current version. Please download the right package and try again." And I have tried that with about 10 other updates witch were available in firmware finder.. but I got the same results.

It seems that no method of updating is working for me right now... Or maybe I am doing the dload method wrongly.

I can't find specific stept for the dload method on the forums. On some of them is even said that dload method doesn't work on this phone all together.

FullOfMysteries said:
I can't find specific stept for the dload method on the forums. On some of them is even said that dload method doesn't work on this phone all together.
Click to expand...
Click to collapse
Hmm,well as a last resort try to use dload with a service firmware.
I am sending you links for PRA-L31,the one I have,and you can check if you have that one by going into the engineering menu,and you do that by going into the dialer and typing this: *#*#2846579#*#*,and then going to Veneer Informations and Version Info.
http://androidhost.ru/6uc - this is for the July security patch firmware (aka the newest one),but it will take 8 hours to download,at least it took that time for me
https://mega.nz/#F!nwhAWDjC!cNovAN6dKLlO_YZ9fjMbzQ - this is for the firmware you are probably running right now
All of these links are from 4PDA forums.
https://4pda.ru/forum/index.php?showtopic=809771&view=findpost&p=65929494 - here you can find instructions on how to do it,if you don't understand them basically you need to firstly apply the UPDATE.APP from the first update_sd.zip you find in the dload folder,and then do the vendor UPDATE.APP which you can find in the PRA-L31 folder.
I am sorry if you cannot completely understand what am I saying,I am typing this in a bit of a rush so...

dinoderda said:
Hmm,well as a last resort try to use dload with a service firmware.
I am sending you links for PRA-L31,the one I have,and you can check if you have that one by going into the engineering menu,and you do that by going into the dialer and typing this: *#*#2846579#*#*,and then going to Veneer Informations and Version Info.
http://androidhost.ru/6uc - this is for the July security patch firmware (aka the newest one),but it will take 8 hours to download,at least it took that time for me
https://mega.nz/#F!nwhAWDjC!cNovAN6dKLlO_YZ9fjMbzQ - this is for the firmware you are probably running right now
All of these links are from 4PDA forums.
https://4pda.ru/forum/index.php?showtopic=809771&view=findpost&p=65929494 - here you can find instructions on how to do it,if you don't understand them basically you need to firstly apply the UPDATE.APP from the first update_sd.zip you find in the dload folder,and then do the vendor UPDATE.APP which you can find in the PRA-L31 folder.
I am sorry if you cannot completely understand what am I saying,I am typing this in a bit of a rush so...
Click to expand...
Click to collapse
THANK YOU SO MUCH! This actually helped me restore my phone to normal. I installed the B363 version from the MEGA link ( I had B360 installed. my mistake was that I initially installed the wrong version with firmware finder, B360 instead of B363). But once I installed the B360 I got a notification to update to B369.
Thank you for your help!

dinoderda said:
Hmm,well as a last resort try to use dload with a service firmware.
I am sending you links for PRA-L31,the one I have,and you can check if you have that one by going into the engineering menu,and you do that by going into the dialer and typing this: *#*#2846579#*#*,and then going to Veneer Informations and Version Info.
http://androidhost.ru/6uc - this is for the July security patch firmware (aka the newest one),but it will take 8 hours to download,at least it took that time for me
https://mega.nz/#F!nwhAWDjC!cNovAN6dKLlO_YZ9fjMbzQ - this is for the firmware you are probably running right now
All of these links are from 4PDA forums.
https://4pda.ru/forum/index.php?showtopic=809771&view=findpost&p=65929494 - here you can find instructions on how to do it,if you don't understand them basically you need to firstly apply the UPDATE.APP from the first update_sd.zip you find in the dload folder,and then do the vendor UPDATE.APP which you can find in the PRA-L31 folder.
I am sorry if you cannot completely understand what am I saying,I am typing this in a bit of a rush so...
Click to expand...
Click to collapse
Thank you for this simple and useful guide. :good:
I was able to successfully update back to stock using Normal upgrade *#*#2846579#*#* dload method (not force with 3 buttons) and service firmware 8.0.0.363(C432). After that, got OTA for 8.0.0.369.. Everything went fine, except device name changed automatically to P9 lite 2017
Is this okay?? The same happens with service firmware you mentioned 8.0.0.369(C432)...
Beside that, Power+Vol+ gives me no more eRecovery, just EMUI with options to wipe data or reboot..
My device: P8 lite 2017 PRA-LX1 (PRA-L31)

Almironi said:
Thank you for this simple and useful guide. :good:
I was able to successfully update back to stock using Normal upgrade *#*#2846579#*#* dload method (not force with 3 buttons) and service firmware 8.0.0.363(C432). After that, got OTA for 8.0.0.369.. Everything went fine, except device name changed automatically to P9 lite 2017
Is this okay?? The same happens with service firmware you mentioned 8.0.0.369(C432)...
Beside that, Power+Vol+ gives me no more eRecovery, just EMUI with options to wipe data or reboot..
My device: P8 lite 2017 PRA-LX1 (PRA-L31)
Click to expand...
Click to collapse
Yeah that is good,since this is a firmware which was released around Croatia,Albania,Czech Republic and etc,but there it is called P9 Lite 2017 instead of P8 Lite 2017 so it is no problem.
And I believe you enter eRecovery by holding Volume Up while plugging in your phone to a charger or USB port on a computer,at least that is how I did it before on Nougat,haven't touched any recoveries I fixed my phone with DC Phoenix.