Database Info

[TUTORIAL]How to update EVA-L09C636 (Asia-Pacific) model to B361 (EMUI 5)

I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.

That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.

whyhowie said:
I had been searching for a way to update my EVA-L09C636 (Asia-Pacific) model to EMUI 5.0. During the previous month I tried to install EVA-L09C636B361 firmware via either dload and Huawei Updater, but such means of direct installation never worked out.
Now the problem is solved, and the solution is quite simple, though a little bit unexpected: using Huawei Updater to install EVA-L19C636B190 before installing EVA-L09's own B361 firmware. I mean, it is interesting that we have to "borrow" the B190 firmware from the Dual SIM L19 model in order to update to EMUI 5.
(I'm not the first person to find the solution. I just found out that in a Taiwanese forum a tutorial is already posted. )
So there are two steps to install B361:
1.
Install EVA-L19C636B190 via Huawei Updater
Use Custom ROM URL
Copy and paste the link to EVA-L19C636B190:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v64578/f1/
Use the HiSuite on PC to finish the installation of B190 (Set its proxy to 127.0.0.1 and the port to 41279)
2.
Repeat the previous process, but this time, replace the link with the one to EVA-L09C636B361:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1256/g104/v73928/f1/
Again, use the HiSuite to finish the installation of B361
Note that the C636B190 version firmware for L19 model does run on L09 without the support of the L09-exclusive NFC. I think there should be a thread discussing this. Anyways, before official update comes out, the two steps above seem to be the only way to install EMUI 5 on the Asia-Pacific EVA-L09C636 version without losing data.
Click to expand...
Click to collapse
I was searching for this for months. I bought my p9 EVA-L09C636 in the US (I'm european) and I never had the chance to update, even at 4.1.1. I went crazy because I tried several times to unlock the bootloader first, installing twrp and flashing updates but with no success. It's unbelievable that I need to fake the version with huawei updater to obtain the updates for my phone. Now I've Nougat, without factory reset, with everything working, from nfc to all stock apps and services. Thank you very much

Z-Blade said:
That is interesting, I dont have a C636 but I would assume just doing step 2 without the need to flash a L19B636 would do the trick.
Click to expand...
Click to collapse
Well, in that case it keeps failing at 1%. I saw some previous posts talking about this as well.

Need Help
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?

Thanks finally I was able to update my P9 to Nougat using this steps. The only difference is that there is a EVA-L09C636B190 available now so i didnt have to use the version for any other cell, I was afraid to do it. So following this steps i was able to upgrade from 168 to 190 and finally to 361 version.

My Phone is Huawei P9 EVA-L09C636
Even though my phone is L09 I've flashed L19 by following the steps on this thread -
(https://forum.xda-developers.com/mate-8/general/nxt-l09c636b521-official-firmware-guide-t3544729/)
2016.12.29 - EVA-L19C636 - EVA-L19C636B361
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1583/g104/v74666/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...ll/hw/spcseas/update_data_full_hw_spcseas.zip
it's still NRD90M test-keys. but i'm cool with it.

Works on AL00 as well?
I was wondering if I can get the most current european rom on my AL00 with that method as well?

Holy cow thank you for this tutorial.
I spent six hours following every tutorial I could find on the web and my P9 staunchly refused to install ANY update from the very next one after the one it came with all the way up to the latest!
After hours and hours of trying this method is the one that worked.
Edit: This firmware is a developer build.
There have been several updates installed since it was released.
After you this firmware it you should immediately install Huawei Firmware Finder from the Play Store and install the latest full OTA.
The developer build changes the device ID of your phone so you have to manually add the model of your phone in Firmware Finder as:
EVA-L19C636
Otherwise Firmware Finder would tell you there are no firmwares available for your model.
If you can't install the latest OTA immediately after installing this firmware, first install the next one available (38 if I recall correctly) then install the latest OTA -- 38 will say it failed to install but it actually installs just fine, then install the latest full OTA.
That will give you all the bug fixes and the security patches from Google.
Also note that this firmware works on both the dual sim and single sim models (it's built for the single sim but my device is dual sim and the sim configuration in settings works).

snjflame said:
My model is Huawei P9 EVA-L09C636
I tried to update like this, it's started updating and got an error while updating then phone rebooted with new update,
but there's lot of errors,
Built Number displays as - NRD90M test-keys
Updater missing in settings
Camera missing
Flash Light not working
Clock missing
File Manger missing
and few more default huawei apps missing.
How do I fix it or downgrade to previous version back?
Click to expand...
Click to collapse
The build number is normal.
As for the disappearing apps, it sounds like you have faulty flash storage.
That will cause files and apps to randomly disappear.

Updating a C432

Just recently bought this phone, and after scouring this forums the past few days I found that the EMUI that shipped with my phone is 4-5 months old (Dec '16) and that there have been multiple updates since, even though the OTA on my phone says I'm using the latest version. This scares me, not so much for features, but because of potentially missing security patches.
Looking at hwmt.ru's listings, there's a lot of updates, and for my specific model the latest OTA is B181, and the latest "full" update (I assume these are whole images) is B156.
Can I download the B156 updates (basically the same way used when rooting the phone) to update the stock ROM?
And if that is correct, what are all the listings on that site under the "A" (or "Тип") column with "OTA" for?

Download the firmware finder app for android and update through it: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You probably won't be able to update to 181 though... You'll have to test which ones you can install. Huawei needs to approve each firmware version before we can install through system update.

B181 didn't work, authentication error, gonna try the other way and work my way up instead.
Nice that someone made a tool to automate this though, even though it's a hacky way

Nevermind that, every single version gets that authentication error, even the ones older than the one I have currently installed.

Having trouble with SD card firmware updates.

Hello everybody,
Firstly, apologies about all text, no links.. But i'm new to the site and don't have enough posts to link yet.
So, i'm new to the Mate 9 (had Samsungs for quite a few years now... Overpriced battery sucking hogs that never last to 18 months withou massive issues) and I really haven't gotten into the custon side of/flashing etc since my original galaxy (dunut, before the s!) /HTC Desire, sgs3 days.... So i'm probably quite out of touch... But still capable to learn and especially follow a good guide!
Now, my thing is... I want to stay stock as I use Android pay quite a lot... Yet with my experience with optus they are ATROCIOUS at updates, every with volume sale items like the Galaxy s4, 5 &6 so I can only imagine that i'll never get an update with the mate 9.
I purchased my phone outright, but second hand.... So I don't think I'll have a warranty anyway.
So far I have gathered that I can only debrand if I unlock the bootloader (and pay remains broken even if it gets relocked with an original rom) so for me, at least for the time being, that's out.
My next option is to side load firmware from the SD card... I just want to keep up to date. There is some screen sensitivity issues that the newest firmware apparently addresses.. Not to mention camera updates and battery usage updates (already VERY impressed with the battery though, especially after my S6- Awful phone)
Trouble is, I can't get any update to complete! - They get to 5% and then fail!
The firmware models I've tried have slightly different numbers to what's on my Optus Mate 9... But I can't find any exact matches, so I'm kind of expecting this to be the cause of my failed updates, even when I've downloaded from the different sites following the guides.
Currently i'm running with this;
Model: MHA-L09
Build: MHA-L09C34B122
EMUI: 5.0
Android: 7.0
and I have tried these three updates from the Huawei... Note 2 full and one OTA. Also note the firmware/region differences... But it's as close as I can find.
2017.04.25 MHA L09BC346B181 FULL-MF
2017.04.25 MHA L09BC346B181 OTA-MF
2017.04.24 MHA L09BC34B170 FULL-MF
I've also followed these two guides (and another one with a B170 update), downloading the updates from each respective site in case the firmware was something different than what I could find. Note also that one tells you to put the dload folder into the device memory.. Which won't work, so I just did it in SD which enables the phone to recognise the update file.
(links not allowed sorry, removed and replaced with text, can probably google to see what I did, always fails on step 1)
From get droid tips, upgrade to B170 & B181
from stechguide, upgrade it B181
Not to mention having followed all the guides I could find on this forum.
I'm sorry if I've missed a discussion that already deals with this (or similar) or if it's really bleedingly obvious. I'm just at a bit of a loss here!
Thanks in advance.

Sorry,
This is for Australian firmware. Optus.

Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.

Thanks for that,
I'd obviously misunderstood what's available already... Figured since I don't have the 10x zoom available like the latest release, I was behind.

ante0 said:
Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.
Click to expand...
Click to collapse
Yes, new users are led the wrong way by reading these guides.
The dload method probably worked with older devices so the Mate 9 articles seem to be created by copy and paste and replacing the older devices name with "Mate 9". Voila! There's your new shiny article about the Mate 9 and people klick it.

Yeah. I got sucked in. Noob mistake.
Sorry for polluting the board with my stupidity!
Very out of touch with behind the scenes android.
Thanks for taking the time guys

Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.

Saw that. Figured I'm just stuck as is for now. I'll check out what you're referring to!

Leighm0 said:
Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.
Click to expand...
Click to collapse
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.

Texan1 said:
should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
IMHO yes you should. Don't let FF/FH turn into an obsession, just enjoy your phone.
Sent from my MHA-L29 using XDA Labs

Texan1 said:
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.

By the way, when you unlock bootloader on mate 9, then flash a full firmware (either the update and rebrand guide, Firmware finder or funky) your bootloader gets locked again. So no real harm done.

Leighm0 said:
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.
Click to expand...
Click to collapse
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?

Texan1 said:
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?
Click to expand...
Click to collapse
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.

Leighm0 said:
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.
Click to expand...
Click to collapse
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?

Good question... Wondering that myself.
Sent from my MHA-L09 using XDA Free mobile app

Texan1 said:
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?
Click to expand...
Click to collapse
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..

Leighm0 said:
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..
Click to expand...
Click to collapse
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.

Texan1 said:
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.
Click to expand...
Click to collapse
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!

Leighm0 said:
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!
Click to expand...
Click to collapse
Iirc they go by IMEI.

Downloaded Firmwares with 2 instead of 3 .zip-files

Hi there,
So in a nutshell i am wondering what to do with firmware updates that do not include the "data_public" zip file. I have received my unlock code recently and after a lot of messing about and some learning from mistakes, i've managed to finally run a stock MHA-L29C432B198 build while being on TWRP and rooted. During that time i have downloaded quite a few different versions of firmware and as all the guides are always talking about 3 zip files, i've discarded those 2-zip builds, but now i want to upgrade to B321 and the build i found (supposedly full ota) does not include the data public zip and i would like to know if there is anything to do about that - do i get it from somewhere else? do i just omit it? do i wait till it shows up somewhere? and what is the whole deal with sometimes including it and sometimes not?

Could you post the link to the firmware you found?
Anyway, you could try downloading through the Firmware Finder app, it will get all 3 files.
And latest for C432 now (Oreo) is B361 as of yesterday, I'm installing it right now.
Edit: Weird. Bootloader didn't get locked after flashing. Saves me some steps

The firmware finder app is my source, and i'll leave you a screenshot of the most recent versions on there - the topmost build (B198 fullOTA-MF PV) has 2 zips, the 198 fullOTA-MF has three, in spite of having a smalle overall size.
Firmware finder recommends to download the pv build to flash in twrp which is how i noticed this discrepancy. Where did you get hold of b361? Have you rebranded your phone?

Two-files ROMs (PV) are usually for rollback.
They are normal ROMs but you have to modify mankindtw's script for two files instead 3. Or use FF if they are authorized.

Boeserwolf93 said:
The firmware finder app is my source, and i'll leave you a screenshot of the most recent versions on there - the topmost build (B198 fullOTA-MF PV) has 2 zips, the 198 fullOTA-MF has three, in spite of having a smalle overall size.
Firmware finder recommends to download the pv build to flash in twrp which is how i noticed this discrepancy. Where did you get hold of b361? Have you rebranded your phone?
Click to expand...
Click to collapse
B361 is oreo. Found on pro-teammt.ru. You'll have to search for MHA-L29 (or L09) 8.0.0 for oreo.
Mine would be MHA-L29 8.0.0.361 (C432)
Latest nougat is B198.

ante0 said:
B361 is oreo. Found on pro-teammt.ru. You'll have to search for MHA-L29 (or L09) 8.0.0 for oreo.
Mine would be MHA-L29 8.0.0.361 (C432)
Latest nougat is B198.
Click to expand...
Click to collapse
that certainly solves the practical side of my problem...
5[Strogino] said:
Two-files ROMs (PV) are usually for rollback.
They are normal ROMs but you have to modify mankindtw's script for two files instead 3. Or use FF if they are authorized.
Click to expand...
Click to collapse
...while this allows me to work on finding out more about the theoretical side.
Thank you both for the help, I appreciate it.
Sidenote: if it were up to me, this thread could now be closed.

Another device stuck on FRD-L09C432B394

First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!

YorkiEg said:
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
Click to expand...
Click to collapse
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?

ScardracS said:
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
Click to expand...
Click to collapse
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version

YorkiEg said:
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
Click to expand...
Click to collapse
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407

ScardracS said:
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
Click to expand...
Click to collapse
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!

YorkiEg said:
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
Click to expand...
Click to collapse
For b406 and/or b407 I think you have to expect a bit

ScardracS said:
For b406 and/or b407 I think you have to expect a bit
Click to expand...
Click to collapse
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it

YorkiEg said:
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
Click to expand...
Click to collapse
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.

pix106 said:
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
Click to expand...
Click to collapse
That’s what’s frustrating me, all the firmware files I’ve downloaded are approved for my device Or so does Firmware Finder app says! Yet they all fail to install at 5%!
Proxy method doesn’t work on B404, or at least not working for me So nothing is working now
I’ve had enough with this phone, just to avoid smashing it into a wall next time it drives me crazy, I’m looking to get another phone, Xiaomi Mi A2 might be the one. Still looking though

Successful update
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
It downloaded the ROM files then when download completed it said the package has changed and requested to download again! I downloaded that and it started installation! Everything went well during installation but at the end it said it has failed because it could not find the update package I thought it failed and restarted the device only to find it running Android 8 and EMUI 8! Full reset and all working flawlessly
HiSuite acknowledges the update and offers to rollback to B407 if you’re having problems! Please note that I was stuck on B394! So even rolling back would be an upgrade
I’ve tested different apps, NFC (I never use it for contactless payments though so can’t confirm that, but I can’t see why it wouldn’t work) Also GPS and everything’s working just fine! Only issue is/was battery draining but that’s due to the auto launch in battery settings! I changed some of the application settings into manual launch and all great now!
Thank you for all those who helped :good: And hopefully this might help some of the frustrated Honor 8 users like myself! And hopefully won’t be stuck on B521 now!

YorkiEg said:
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK)
Click to expand...
Click to collapse
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?

Himmagery said:
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Click to expand...
Click to collapse
No such thing as stupid question! We all need to start somewhere
Finding the rollback package is via the official Honor support website for (Preferably) the country where you purchased your handset from. Or if it was EU, any EU country.
Rollback process will be executed by downloading and unzipping 2 files, the Honor 8_Rollback Package_FRD-L09_from Android 7.0 EMUI 5.0 to Android 6.0 EMUI 4.1_C900B300 (Around 75 MB in size) and the Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_CXYZB131 (Around 1.75GB in size).
Next you should have a MicroSD Card installed, formatted, and create a folder on root called dload.
Then Unzip the files you downloaded, will get you 2 Update.app files, copy the first one (From C900B300) to the dload folder, switch phone off, press Volume-, Volume+ and the Power button and don’t let go till system starts updating, this one won’t take long.
When finished, format you MicroSD Card, create dload folder again, then copy the second Update.app file (From CXYZB131) into the folder, same button combination to update. This update will take longer.
When finished, try Firmware Finder app immediately if you can and use the in-app proxy method to let your phone do the update, if it didn't work, let the phone do OTA update but don’t let it update too many times because Firmware Finder doesn’t work with newer System Update apps.
Hope that helps. And good luck :good:

YorkiEg said:
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
Click to expand...
Click to collapse
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is

darklighthim said:
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
Click to expand...
Click to collapse
Glad it worked for you :good:
The fingerprint scanner was a bit of a hit and miss for me when I first updated but it wasn't bad enough to mention, and it has settled now! Other than that, still running smoothly