Database Develop

p9plus update to Emui 5.0 issue....

My p9plus is not getting any sort of update ...it is currently on Emui 4.1 and its build number is VIE-L09c627B160 can any one help me ?

Aadiisarki said:
My p9plus is not getting any sort of update ...it is currently on Emui 4.1 and its build number is VIE-L09c627B160 can any one help me ?
Click to expand...
Click to collapse
you can try using Firmware Finder Free. its available for download it from Play Store

Mine is stuck too not haven't received a single update since I bought it still on emui 4.1 FF is useless it donwloads the update just fine but it always fails on the installation at 1% my build N is VIE-L29C605B131.

Aadiisarki said:
My p9plus is not getting any sort of update ...it is currently on Emui 4.1 and its build number is VIE-L09c627B160 can any one help me ?
Click to expand...
Click to collapse
What country/region are you from?
What is the present firmware version B160 dated?
Firmware Finder (FF) (online version) shows B150 as the latest, so FF's probably not going to help you unfortunately: http://pro-teammt.ru/firmware-database/?firmware_model=VIE-L09c627&firmware_page=0
Your only other option may be to convert to another region's ROM, which has received regular updates - e.g. Euro C432 ROM (latest is B382, dated March 2018). But, it's a risky procedure which involves unlocking the bootloader, rooting the phone, changing the vendor country info with SRK Tool, etc, etc.
Coreinsp said:
Mine is stuck too not haven't received a single update since I bought it still on emui 4.1 FF is useless it donwloads the update just fine but it always fails on the installation at 1% my build N is VIE-L29C605B131.
Click to expand...
Click to collapse
Which update did you try? If you're still on 4.1, then you should try a much earlier update (i.e. the very 1st 5.0 update) - I'd recommend one of the B361s from here (or via the FF app): http://pro-teammt.ru/firmware-database/?firmware_model=VIE-L29C605&firmware_page=0
Always download & apply the FullOTA-MF, in this case ~1.3Gb file size.
Once you have installed B361 successfully, try the B381 update (not the latest B382 as it will not work at this stage most likely). Again, download the FullOTA-MF (1.4Gb) & apply it.

GaT7 said:
What country/region are you from?
What is the present firmware version B160 dated?
Firmware Finder (FF) (online version) shows B150 as the latest, so FF's probably not going to help you unfortunately: http://pro-teammt.ru/firmware-database/?firmware_model=VIE-L09c627&firmware_page=0
Your only other option may be to convert to another region's ROM, which has received regular updates - e.g. Euro C432 ROM (latest is B382, dated March 2018). But, it's a risky procedure which involves unlocking the bootloader, rooting the phone, changing the vendor country info with SRK Tool, etc, etc.
Which update did you try? If you're still on 4.1, then you should try a much earlier update (i.e. the very 1st 5.0 update) - I'd recommend one of the B361s from here (or via the FF app): http://pro-teammt.ru/firmware-database/?firmware_model=VIE-L29C605&firmware_page=0
Always download & apply the FullOTA-MF, in this case ~1.3Gb file size.
Once you have installed B361 successfully, try the B381 update (not the latest B382 as it will not work at this stage most likely). Again, download the FullOTA-MF (1.4Gb) & apply it.
Click to expand...
Click to collapse
I tried all of the full OTA on FF all them download just fine but every time the phone restarts to install the update for some reason it fails at 1% of the install.
Sent from my VIE-L29 using Tapatalk

try B202 first
I had an P9+ B130 version and was able to upgrade to B202, which is needed as a stepping stone to MIUI 5. I used FF with the proxy update scheme. The B202 update worked while other versions stopped at verifying the update, which is just what you experienced.
Coreinsp said:
I tried all of the full OTA on FF all them download just fine but every time the phone restarts to install the update for some reason it fails at 1% of the install.
Sent from my VIE-L29 using Tapatalk
Click to expand...
Click to collapse

cjviking said:
I had an P9+ B130 version and was able to upgrade to B202, which is needed as a stepping stone to MIUI 5. I used FF with the proxy update scheme. The B202 update worked while other versions stopped at verifying the update, which is just what you experienced.
Click to expand...
Click to collapse
I'm out of luck then it seems that the B354 update is no longer available on FF which is the "steppingstone" in my case.
Sent from my VIE-L29 using Tapatalk

Same problem here. I'm still on vie-l29c636b103. Any solutions?

Does Unlocking Bootloader disable OTA updates?

I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )

dgoncalves81 said:
I've gone through the process of entering my IMEI and serial number in the EMUI bootlocker website and its given me a code.
I haven't yet done any further steps including the adb commands required to remove the blootlock.
However I can now see on the MT Huawei Firmware update list that there is a new update (128) and I'm on (120b)
I've tried using the VPN option to force the update to obtain the firmware from its own servers to no avail.
The firmware checker simply states the firmware isn't compatible with device.
..has somehow simply registering caused it to be blocked for future updates?
##Secondly##.. Does continuing the process and using abd unblock commands cause it to no longer work with OTA?
Or is it only when and if you root it - that OTA can not work? (or does it work)
Quite confused and would really appreciate any advice as ideally I would like to keep OTA, but have root at sometimes with the hope that I could disable root anytime a OTA updates comes available and then re-enable after.
Any advice greatly appreciated )
Click to expand...
Click to collapse
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)

tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Via twrp? What method? Depending on the device type you would have to debrand first

dladz said:
Via twrp? What method? Depending on the device type you would have to debrand first
Click to expand...
Click to collapse
The method I was referring is with HuRUpdater.
HuRupdater Thread

tamaskurti said:
The method I was referring is with HuRUpdater.
HuRupdater Thread
Click to expand...
Click to collapse
Have you used this before? On the P20 Pro?
Only reason i ask is the P20 Pro is not listed on the supported devices and as i said you would need to have the correct firmware for your device, the newer firmwares are made for the European version of the device L29 not L09, so providing you're on L29 and it's the correct firmware then it should work, but i would not like to be the person to crash test this.
I'm on the L09 which doesn't take L29 firmwares unless i debrand and then try it.

I have CLT-L29C432B128. (I have updated with hurupdater since the 128 fw is not yet approved from firmware finder)
I thinking on try flashing cn firmware.

tamaskurti said:
It is NOT related with unlocked bootloader or rooted firmware.
It's related with emui 8.1 version whitch is NOT supported by FirmwareFinder.
So basically VPN or Proxy wont work with that.
Another thing: the firmwares listed on FF aren't approved at appearance date. This means that we must wait a bit for approval, and after that can FF download the selected firmware (again, emui 8.1 is not supported).
If you are in hurry with flashing the new firmwares, you can via TWRP (methods described on forum).
BUT be aware, that even with that you can brick your phone
(trust me: after 2 days, when i brought my phone, it was hardbricked... i haven't other choice but RMA, and obviously they have changed the phone. SO be very careful.)
Click to expand...
Click to collapse
Thanks for the advice!
So the list if updates that firmware finder shows are upcoming updates - rather than being released for offical OTA distrubtion from the date listed?
If firmware finder gets it first I'm wondering if you know generally when the OTA updates start to be pushed out via the OTA update system?

I don't know.
Generally about 2-3 weeks (maybe less).

Can't update my P9

My P9 is currently running Nougat and I want to update to Oreo but in "About phone" it says I'm running Android 5.1 and EMUI 3.1 (I'm 99% sure I'm running Nougat). My phone is second hand and I've never rooted it but the last owner might've (if so then it got unrooted before it was sold). I have 4 months left on my warranty if it matters. Whenever I put update.app into a dload folder on my SD card I get an error at 5% when trying to update saying "Software install failed, Incompatibility with current version. Please download the correct update package." I use Firmware Finder to find the latest update and in "About phone" it says my build number is "EMUI-A168-L09C432B040SP11-log" so that's what version of updates I download. I don't get any OTA updates and Firmware Finder's DNC and proxy method don't work for me either. When downloading Nougat I did it manually (through dload) and I think it was some sort of beta or leaked version or something. I don't know what else to try but I just want Oreo on my phone. My bootloader isn't unlocked and my phone is definitely not rooted. I live in the UK so my phone is most likely from there too. What should I do or try?
Edit: I just tried updating my phone through Firmware Finder using the proxy but I get a package checksum error when I try

"Android 5.1 ... 99% Nougat" - Can you post the screenshot of your Settings/About (mask your IMEI) to see what are really your EMUI and Android versions. Also, scrolling down in About should show date (month, year) of the Google security patch - usually it means that Huawei built the ROM the same or next month.
You can also install from Google Play apps like My Device or DevCheck to see if they recognize it as Nougat
Googling for emui-a168-l09c432b040sp11-log finds that it was some early beta version (June 2016) for Android N, see eg (Chrome can automatically translate from Hungarian to English)
https://huaweiblog.hu/tag/emui-a168-l09c432b040sp11-log/
Frankly, I don't believe the phone under warranty was released with beta Nougat, rather that previous owner installed the beta (also I don't know is the phone covered by warranty with that beta N).
Look also to XDA, thread
https://forum.xda-developers.com/showpost.php?p=67931734&postcount=62
subsequent posts, how people who installed beta N (c432 cust or other custs like c900) went back to their official Marshmallow (or upgraded to official Nougat).
"tried updating my phone through Firmware Finder" - I don't find anything at all on Firmware Finder for EMUI-A168.
IMO, you cannot 'update' from your EMUI-A168-L09C432 to the regular EVA-L09C432 (good that it didn't brick your phone). Generally, going from one model/cust to another requires rebranding which is a whole different process, not just taking whatever ZIPs from Finder Finder and flashing them by DLOAD or by DNS/proxy in FF.
IMO, you must go back from your Beta N to official MM (from that time). Then (if it was EVA-L09C432) you will receive OTA updates to official N, or if necessary you will need to rebrand to eg c432 (since some other custs, like English Vodafone, got stuck at MM, there are no N builds for them).
Of course, rebranding (it voids the warranty), if necessary, requires to unlock the Bootloader.
Finally, Oreo is available only for Chinese cust, not even for European c432, and it requires (unlocking Bootloader and) HWOTA7 method, but for that you must first get rid of your Beta N (even rebrand if necessary - see above) to be able to start the HWOTA7 process towards the Chinese Oreo from some of the latest official Nougat builds, see
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
I'm not sure if HWOTA7 (that can be also used for updating Nougat builds ans rebranding from one Nougat cust to another) is applicable to your Beta N.

Try unlocking bootloader and use hwota7

sasi2006166 said:
Try unlocking bootloader and use hwota7
Click to expand...
Click to collapse
It's probably not even neccessary, it is already c432, it should be enough to flash c432 b182 by DLOADvto come back to c432 MM, and then OTA updates will bring him to the latest c432 b50x Nougat - no unlocking bootliader needed
To the other side HWOTA7 might be risky as it requires EMUI 5 and it's not sure is it there in that early Nougat beta build

zgfg said:
It's probably not even neccessary, it is already c432, it should be enough to flash c432 b182 by DLOADvto come back to c432 MM, and then OTA updates will bring him to the latest c432 b50x Nougat - no unlocking bootliader needed
Click to expand...
Click to collapse
Use hwota7 to update to oreo is more faster and have face unlock

sasi2006166 said:
Use hwota7 to update to oreo is more faster and have face unlock
Click to expand...
Click to collapse
HWOTA7 directly from that b040sp11 might be risky as HWOTA7 requires pure EMUI 5 and it's not sure is it there in that early Nougat beta build - therefore going back to MM c432 b182 is betrer (google, you will find people from that time doing so from that Nougat beta)
Once at b182, OTA will bring him to the latest c432 Nougat (his warranty will be back) and then if he wants he can unlock bootliader and use HWOTA7 to go to Oreo (without warranty anymore)

Here you find EVA-L09c432b182 and how to flash it
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Only the following steps apply for you:
2, 11, 12, 13, 14, 15
With the small modification for step (11):
- ignore the first sentence "Go back to main menu and reboot your phone - but not to system. " since you are not coming here from TWRP
- instead, switch the phone off and then boot as in the second sentence "You must press Vol+ and Vol- (in the middle) down until EMUI Software Installing begin and b182 will flashed" and continue with the rest
Upon the OTAs as in step (15), you will have official c432 Nougat (and your warranty)
Later, it's up to you if you want to unlock Bootloader (4 Euros needed for the Bootloader code) and to upgrade to Oreo by use of HWOTA7 method

zgfg said:
Finally, Oreo is available only for Chinese cust, not even for European c432
Click to expand...
Click to collapse
Am I understanding that correclty, still no official (beta) Oreo for Europeans?

neuer31 said:
Am I understanding that correclty, still no official (beta) Oreo for Europeans?
Click to expand...
Click to collapse
What is not understood, there is no Oreo and there won't be for European, Mid East, etc custs
There is (official, no beta) but only for Chinese cust.
Using it, responding you from my P9 EVA -L19C432 rebranded to Chinese Oreo EVA-AL10C00B528

zgfg said:
What is not understood, there is no Oreo and there won't be for European, Mid East, etc custs
There is (official, no beta) but only for Chinese cust.
Using it, responding you from my P9 EVA -L19C432 rebranded to Chinese Oreo EVA-AL10C00B528
Click to expand...
Click to collapse
Oh okay, must have misunderstand it in the past then. I was under the impression that one day they release it for Europe aswell. Rebrand it is then
Thanks for confirming

Lock bootloader again with oeminfo to try the warranty repair

Hi, unfortunately my p10 drop on the floor from an high of 8 cm... Yes almost 4 in an the camera now has a strange yellow border. Of course this issue happens only on the color camera. The b/w camera works well.
The problem is that I have unlocked the bootloader. Can I do something to prepare the phone for rma?
I've the original oem info and of course the unlock code.
Thank you in advance

Maybe downgrade to nougat and then ota update to oreo will help. When I made debrand had unlocked bootloader and frp. Then did ota update to oreo and now have bootloader and frp properly locked.

lukastob said:
Maybe downgrade to nougat and then ota update to oreo will help. When I made debrand had unlocked bootloader and frp. Then did ota update to oreo and now have bootloader and frp properly locked.
Click to expand...
Click to collapse
What guide should I follow for this?

For debrand I used this guide:
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
but I was doing it on nougat and I am not sure how it works with downgrading from oreo to nougat.
If you are already on oreo (and C432 region) you could try to use this guide :
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
tutorial 2 to flash the first full-ota oreo 8.0.0.360 from: http://pro-teammt.ru/firmware-database
but here is question to @Jannomag if it's certain that the script will work from newer to older oreo version. If so then try to use HiSuite to downgrade to nougat (for .360 it should be possible when hit firmware update -> switch to other version) and finally do the ota update to oreo. Be aware that I am not absolutely sure it will work, just suppose it should.

lukastob said:
For debrand I used this guide:
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
but I was doing it on nougat and I am not sure how it works with downgrading from oreo to nougat.
If you are already on oreo (and C432 region) you could try to use this guide :
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
tutorial 2 to flash the first full-ota oreo 8.0.0.360 from: http://pro-teammt.ru/firmware-database
but here is question to @Jannomag if it's certain that the script will work from newer to older oreo version. If so then try to use HiSuite to downgrade to nougat (for .360 it should be possible when hit firmware update -> switch to other version) and finally do the ota update to oreo. Be aware that I am not absolutely sure it will work, just suppose it should.
Click to expand...
Click to collapse
Downgrading to a lower version as Dec2018 security patches can be indeed a problem but this shouldn't cause a brick. The updated should fail flashing /kernel and /ramdisk from update files.

Jannomag said:
Downgrading to a lower version as Dec2018 security patches can be indeed a problem but this shouldn't cause a brick. The updated should fail flashing /kernel and /ramdisk from update files.
Click to expand...
Click to collapse
I tried to flash B365 oreo over B384 with tutorial 2, update started as usual then reached 100% and phone switched off totaly. Now looks like bricked, can't switch on, charging doesn't work, when connected to pc system shows unrecognized USB SER device. Is there any hope to unbrick it?

I have the same. Send to warranty and they fix this by replace the Motherboard. Now i can't unlock bootloader because no offical codes and DC unlocker not support newest security patch from Huawei. Otherwise Phone works fine and i have extra warranty to 2022 .

Current Firmware Update Method for Unlocked Rooted CLT-L09 9.1.0.328

Hi,
What is the current working method to update firmware on an unlocked rooted CLT-L09?
I would like to keep root and unlocked.
It's currently on 9.1.0.328. I see there are 9.1.0.388 and 10.0.0.157 available. Are there any negative consequences of updating to 10?
Apologies if this has been answered before but there are too many methods posted over various time for various versions it is hard to decipher which is the latest working version for my situation.
Thank you!
K

Download from FF and extract the original recovery from 9.1.0.328 and flash it. Now you're back on stock/unlocked. check the OTA updates. and after the update apply magisk again and you will be rooted on the last version. The procedure is the same to continue updating. Android 10 isn't ready for P20 pro, neither is root.

Horayken said:
Download from FF and extract the original recovery from 9.1.0.328 and flash it. Now you're back on stock/unlocked. check the OTA updates. and after the update apply magisk again and you will be rooted on the last version. The procedure is the same to continue updating. Android 10 isn't ready for P20 pro, neither is root.
Click to expand...
Click to collapse
I've got the 328 update_full_base.zip but how do I extract the original recovery? The only img file inside is ptable.img
Sorry if this is a dumb question haven't flashed the phone in a while.

there is an app called huawei extractor. i'ts here on XDA. Disable checksum verify if gives an error while trying to extract.