Database Develop

L09C636/C34 'VERLIST.IMG' entries

Been working towards debranding my P9 from L09C34 (optus/au) to L09C636 (hw/asia).
Tried following all the guides and consistently ending up with C900 firmware, but managed to successfully roll back to the original C34, with version number displayed correctly on the phone.
My question is this:
In the C34 firmware that came with the phone (and that i've been using to roll back) AND the C636 firmware, BOTH firmwares have only two lines in VERLIST.IMG:
EVA_C900B000
EVA_Global
How then, does this part of the debrand process affect the version number displaying correctly, if both the successful original firmware and the unsuccessful C636 firmware have the same entries?

I had the same issue with wife's P9 Optus rom is based on the Global Version. EVA_C900 you need to flash both rom and data partition
Sent from my iPad using Tapatalk

DanXbix said:
I had the same issue with wife's P9 Optus rom is based on the Global Version. EVA_C900 you need to flash both rom and data partition
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Thanks. I managed to successfully get back to the Optus firmware with the correct version displaying - but I still haven't cracked the de-brand without it showing C900 firmware - from what I read, C900 is a cross-flash firmware and will not get OTA updates. My main concern was getting the Nougat update, which has apparently started appearing on the unbranded devices.
Did you manage to de-brand your wife's phone to C636? Does it show the correct firmware version in 'about phone'?

I tried to debrand my C34 to C636 as well but ultimately, I gave up on it and went to the debranded C432 UK version. There are plenty of info on this forum on how to do it and there is no lose in functionality and it works perfectly fine with the AU carriers. Realistically, apart from the build having C432 instead of C636, you wouldnt see or feel a difference between the 2 models. If anything, C432 will get updates sooner than C636 (as proven with Nougat).

mate s and I want to update it how I do it?

Hello ,I never got a update for my Huawei mate s and I want to update it how I do it my my version is CRR-L09C576B125 from israel?

I was in the same situation
1 - Download the appropriate firmware for your device (same region (C576) and model type (L09)
2 - It'll contain two major files, UPDATE.APP and META-INF folder
3 - Create a folder called dload on the sdcard or internal storage
4 - Open the EMUI updater app and update from local storage, should begin automatically. If that doesn't work try rebooting into the recovery and it will update the device

Where I download my firmware?

No region-specific firmware? I also encountered something similar and installed European (C432) firmware from this thread, it is version B390 with EMUI 4.0.3, April 2017
https://forum.xda-developers.com/mate-s/general/huawei-mate-s-firmware-version-crr-t3589650
Original Source:
https://www.android-hilfe.de/forum/...te-b390-emui-4-03-crr-l09c432b390.826509.html
Be warned! : My Mate S was single SIM so the conversion to the European version was no problem, European versions are exclusively single-SIM if I am not mistaken. The installation procedure in the thread was what I used

It seems there are updates bu I'm stuck on B170

Hello,
I have a PRA-LX1 C432 unbranded and the updater keep saying I have the latest official update B170.
Using HFF we can see B181, 183 and 191 for C432 model. But... making a system dump of these builds we can see that there is in build.prop "generic_15" as phone model...
So I didn't install anything...
- Are the builds from HFF trustables ??
- Is there a way to force the update?
thanks!

sambastrakan said:
Hello,
I have a PRA-LX1 C432 unbranded and the updater keep saying I have the latest official update B170.
Using HFF we can see B181, 183 and 191 for C432 model. But... making a system dump of these builds we can see that there is in build.prop "generic_15" as phone model...
So I didn't install anything...
- Are the builds from HFF trustables ??
- Is there a way to force the update?
thanks!
Click to expand...
Click to collapse
Same I'm on B115 and there is up to B191 but only B181 passes check from B115 so will try it but pretty sure it will fail I'm sure from having this phone before you have start B110 and work way up they seem to have disabled manual update like use to on 5X 6X *#*# method don't seem to work anymore but I'm gunnar try anyway
Sent from my PRA-LX1 using Tapatalk

Tried going back to B110 but fails and tried newer ones same just fail every time
Sent from my PRA-LX1 using Tapatalk

I have same problem.... Im still on B175, no new updates in updater.

Sparco21 said:
I have same problem.... Im still on B175, no new updates in updater.
Click to expand...
Click to collapse
I wonder if we will see 8.0, I think all the different build numbers are region based I wonder if any of the p9 lite Roms would work as technically same device PRA-LX1 isn't it
Sent from my PRA-LX1 using Tapatalk

I unlocked my bootloader last night and warns it will wipe, well after the wipe and reboot all system apps like play store browser keyboard were gone I could not do anything other than do a erecovery and that didn't work so had to do a hard factory reset its all working now again but no twrp recovery, weird as
Sent from my PRA-LX1 using Tapatalk

Huawei is a mess...
thnaks for answers !

I tried update to B191 from B115 via Twrp tried flash first file update.zip but just fails, is it cos I left zipped should I unpack it?
Sent from my PRA-LX1 using Tapatalk

I was able to update to B181 with Firmware Finder, but nothing more...

islandman75 said:
I was able to update to B181 with Firmware Finder, but nothing more...
Click to expand...
Click to collapse
But there are more than one build 181, do you know which one you installed ?
your device name continues to be PRA-LX1 or moved to "generic_15" ?
Anything consistent in this update ?
thanks

sambastrakan said:
But there are more than one build 181, do you know which one you installed ?
your device name continues to be PRA-LX1 or moved to "generic_15" ?
Anything consistent in this update ?
thanks
Click to expand...
Click to collapse
Installed the FULL-OTA 181, and after that name didn't change to generic, stayed PRA-LX1... B181

islandman75 said:
Installed the FULL-OTA 181, and after that name didn't change to generic, stayed PRA-LX1... B181
Click to expand...
Click to collapse
Thanks
Problem is that HFF gives a list of something like 5 packages Full OTA for PRA-LX1C432...
Don´t know the diferences between packages ...

sambastrakan said:
Thanks
Problem is that HFF gives a list of something like 5 packages Full OTA for PRA-LX1C432...
Don´t know the diferences between packages ...
Click to expand...
Click to collapse
Yeah, forgot to say, the main difference was passing from EMUI 5.0 to EMUI 5.0.1

Any instructions how to flash with ff?

Can AL00 be reflashed to L31?

Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)

Try LLD-L31C432B131 or LLD-L31C432B132 full ota's. Do not flash Al00 to a L31 it doesn't end well.
Sent from my LLD-L31 using Tapatalk

MSandstrom said:
Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)
Click to expand...
Click to collapse
Your phone's varient depends mainly on the motherboard inside so your phone might not work properly if you flash firmware of other varients. If you wanna go back to stock your best option is to flash the correct firmware using HuRupdater tool.

Rebrand & Magisk.....

I have a C782 P20 Pro, now bootloader unlocked via ToolAllInOne and now I need help.
I'm stuck.
Recently, I updated to .282 firmware via the DNS method. I want to get off C782 onto C432 and this is where i'm having issues.
I purchased credits for FH and have now realised I need to be on Oreo!! I can't roll back to Oreo via Hi Suite, it doesn't give me the option since .282.
Root seems straight forward via TWRP but then i've seen posts of phones being bricked on TWRP. Bricking it would be a nightmare.
I need help getting Magisk on firstly. The guides I have read on here are from 2018, links don't work and i'm not sure the instructions still apply to Pie.
After that i'll see if I can work out how to rebrand.

chrissyyyw said:
I have a C782 P20 Pro, now bootloader unlocked via ToolAllInOne and now I need help.
I'm stuck.
Recently, I updated to .282 firmware via the DNS method. I want to get off C782 onto C432 and this is where i'm having issues.
I purchased credits for FH and have now realised I need to be on Oreo!! I can't roll back to Oreo via Hi Suite, it doesn't give me the option since .282.
Root seems straight forward via TWRP but then i've seen posts of phones being bricked on TWRP. Bricking it would be a nightmare.
I need help getting Magisk on firstly. The guides I have read on here are from 2018, links don't work and i'm not sure the instructions still apply to Pie.
After that i'll see if I can work out how to rebrand.
Click to expand...
Click to collapse
For Rooting with Magisk on Pie I followed the guide posted by smohanv https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964
The only difference is I had to get the latest RECOVERY_RAMDIS_9.0_282.img using the below method
1. Download the matching firmware for your device using Firmware finder https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder&hl=en_GB
2. Unzip the downloaded update_full_base.zip then extract recovery_ramdisk.img from the Update.app using https://forum.xda-developers.com/sho....php?t=2433454
copy this img to your device

You don't need twrp. There's a guide on here with an automated flash.bat script to revert back to Oreo. I did exactly what you're trying to do. Took me ages to find the best way, can't remember the exact post BUT if you search the forum for a post with "numpty" in the title, that's from me and links to it and explains the whole process [emoji16]
Sent from my CLT-L09 using Tapatalk

Wait, so now you can unlock yoir bootloader without using FunkyHuawei's paying method?

I mean you don't need to do it seperately sorry. The batch tool, will run through it including installing twrp in one go.
Unlock bootloader
Run tool
Follow instructions
Device is on oreo
Sent from my CLT-L09 using Tapatalk
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
Think he probably bought the code from somewhere and used toolallinone to run the unlock via the code
Sent from my CLT-L09 using Tapatalk
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
aka.petteri said:
Wait, so now you can unlock yoir bootloader without using FunkyHuawei's paying method?
Click to expand...
Click to collapse
Probably bought code then used it via toolallinone
Sent from my CLT-L09 using Tapatalk

blufreak said:
I mean you don't need to do it seperately sorry. The batch tool, will run through it including installing twrp in one go.
Unlock bootloader
Run tool
Follow instructions
Device is on oreo
Sent from my CLT-L09 using Tapatalk
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
Think he probably bought the code from somewhere and used toolallinone to run the unlock via the code
Sent from my CLT-L09 using Tapatalk
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Probably bought code then used it via toolallinone
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
I did buy the code and use toolallinone yep.
So I do need to install Twrp then?
Is there a chance of bricking the phone rebranding the Oreo way?

@chrissyyyw
There is no zero risk to make this kind of modification on a device.

Using the script ensures no errors in commands and it's all relative to the previous step so if you miss a step it won't complete. Phone is as it was. And no. I had my bootloader unlocked nothing else. The script installs twrp, debrand, restarts and then flashes the Oreo firmware for you
Sent from my CLT-L09 using Tapatalk

blufreak said:
Using the script ensures no errors in commands and it's all relative to the previous step so if you miss a step it won't complete. Phone is as it was. And no. I had my bootloader unlocked nothing else. The script installs twrp, debrand, restarts and then flashes the Oreo firmware for you
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info.
Do OTA updates work via this method?

Yup. Currently on .282 may security. Rebranded mine so I didn't have to fart about with ff and hope the firmware worked all the time etc
Sent from my CLT-L09 using Tapatalk

blufreak said:
Yup. Currently on .282 may security. Rebranded mine so I didn't have to fart about with ff and hope the firmware worked all the time etc
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
I've found the thread about the script @blufreak.
Seems straight forward enough, just one question about downloading the Oreo firmware and extracting the 3 files.
Do you download C782 to get you back onto Oreo and then use the FH tool to rebrand onto C432?

Yes. C432 won't install u till you have rebranded. Download C782. Extract. Run.
Run fh rebrand and use that to install C432. Start with a version of Oreo as close to the C782 version as you can, must be equal to or higher but not lower.
Sent from my CLT-L09 using Tapatalk

blufreak said:
Yes. C432 won't install u till you have rebranded. Download C782. Extract. Run.
Run fh rebrand and use that to install C432. Start with a version of Oreo as close to the C782 version as you can, must be equal to or higher but not lower.
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
Cool, I'll give it a go tomorrow.
With the software, in the guide it says you must dowload the one with the 3 files.
Does it matter which one FH downloads? Or is it just the equal too or greater than version number?

So for Oreo C782 I think I went for 159 but could be wrong. Easiest way to make sure is run hi suite, connect phone and click update then when it says you're up to date select other version and it will list a specific Oreo version. Then download that one from something like androidhost.ru and check the zips for the correct number of files and names. That was the most confusing part for me
Once I debranded I then installed the identical version of C432 via fh as per rebrand instructions..... Once handset started the update barrage started
Sent from my CLT-L09 using Tapatalk

blufreak said:
So for Oreo C782 I think I went for 159 but could be wrong. Easiest way to make sure is run hi suite, connect phone and click update then when it says you're up to date select other version and it will list a specific Oreo version. Then download that one from something like androidhost.ru and check the zips for the correct number of files and names. That was the most confusing part for me
Once I debranded I then installed the identical version of C432 via fh as per rebrand instructions..... Once handset started the update barrage started
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
Since installing. 282 via the DNS method my Huawei Suite doesn't give me the option to install another version at all.
It did when I was on. 168

Possibly as it's not an official release. Well, go for 159, it's a moderately up to date Oreo, and I remembered I found you had to do one earlier than the 160s for a reason to do with some of the files..... Don't ask me to be more specific lol. It doesn't matter really. As long as you do an Oreo below 160 you'll get updates straight away anyway. Just don't allow it to start updating when you boot into Oreo C782 obviously
Sent from my CLT-L09 using Tapatalk

blufreak said:
Possibly as it's not an 8 official release. Well, go for 159, it's a moderately up to date Oreo, and I remembered I found you had to do one earlier than the 160s for a reason to do with some of the files..... Don't ask me to be more specific lol. It doesn't matter really. As long as you do an Oreo below 160 you'll get updates straight away anyway. Just don't allow it to start updating when you boot into Oreo C782 obviously
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
That makes sense as I'm not sure Huawei have officially released it, even now.
2 questions before I get stuck into this tomorrow. ADB with charge mode, how do you enable that?
I have found CLT-L09C782B159 (8.0.0.159) on firmware finder on my laptop. Change log says it's the version to roll back.
I have been on the app on my phone, found the same FW version but only got the CLT and update.zip files, not the public?
The only version I can find with the 3 files you mentioned does not mention the rollback in the changelog?
Is this ok to go with @blufreak ?
Thanks

Download the files from androidhost.ru and it should be right. And Adb charge mode is under developer options (tap 7 times on build to reveal them)
Sent from my CLT-L09 using Tapatalk

blufreak said:
Download the files from androidhost.ru and it should be right. And Adb charge mode is under developer options (tap 7 times on build to reveal them)
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
The Oreo .159 version I can find with L09, Public and Full files is the October update.
The roll back version does not contain the 3 files.
https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=clt-l09c782&firmware_page=0
28/10/16 I have downloaded.
Is it ok to use the normal version?

I can't get into Fastmode, the phone keeps ignoring me pressing power and volume down and booting to the 'your device cannot be trusted' screen.