Database Info

honor 8 bricked bootloop

Hi, I have a honor 8 that bootloops I can only access to fastboot not in bootloader or recovery. Bootloader is locked, i can't flash anything and i can't unlock it because I don't have the Product ID. The dload and three fingers method doesn't work. What can I try to unbrick it? I can't even turn it off.

OG_Winzer said:
Hi, I have a honor 8 that bootloops I can only access to fastboot not in bootloader or recovery. Bootloader is locked, i can't flash anything and i can't unlock it because I don't have the Product ID. The dload and three fingers method doesn't work. What can I try to unbrick it? I can't even turn it off.
Click to expand...
Click to collapse
Which number of firmware you tried via dload??
Which firmware number you were on before issue??

When you say that the dload method doesn't work, what do you get when you try it ? You have to flash the proper firmware for your phone, otherwise it will deny it, you can maybe use a rollback package.

Try the Huawei tool ... U can fix it easily and you can play around don't panic it's the first thing ...

hassanjavaid8181 said:
Which number of firmware you tried via dload??
Which firmware number you were on before issue??
Click to expand...
Click to collapse
I tried one firmware via dload but the phone doesn't even detect anything there isn't any error it just keeps rebooting. The firmware i need to install is FRD-L09C432B131.

Rayan19997 said:
When you say that the dload method doesn't work, what do you get when you try it ? You have to flash the proper firmware for your phone, otherwise it will deny it, you can maybe use a rollback package.
Click to expand...
Click to collapse
i just does nothing. not any errors or loading. The phone just keeps rebooting.

OG_Winzer said:
i just does nothing. not any errors or loading. The phone just keeps rebooting.
Click to expand...
Click to collapse
Maybe you are doing it wrong. As long as you have a stock boot.img and a stock recovery you should be able to use this method.

luisaet82 said:
Try the Huawei tool ... U can fix it easily and you can play around don't panic it's the first thing ...
Click to expand...
Click to collapse
If you mean Hisuite I already tried it. my PC detects the phone and hisuite launches by itself but then doesn't detect any phones. when I try the rescue tool "resuce mode enter..." appears on the screen but then hisuite says that the phone isn't compatible with the rescue mode.

OG_Winzer said:
If you mean Hisuite I already tried it. my PC detects the phone and hisuite launches by itself but then doesn't detect any phones. when I try the rescue tool "resuce mode enter..." appears on the screen but then hisuite says that the phone isn't compatible with the rescue mode.
Click to expand...
Click to collapse
I think he doesn't mean hisuite but Huawei multi-tool, which is available on xda forums and enable to recover from a brick
Envoyé de mon FRD-L09 en utilisant Tapatalk

Rayan19997 said:
I think he doesn't mean hisuite but Huawei multi-tool, which is available on xda forums and enable to recover from a brick
Envoyé de mon FRD-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
I tried it too but it didn't work. I tried again the dload method and I achieved to access to EMUI. I tried to recover from wifi but it sayd "getting package info failed" I can now use the dload method but it gives me an error "software install failed"

OG_Winzer said:
I tried one firmware via dload but the phone doesn't even detect anything there isn't any error it just keeps rebooting. The firmware i need to install is FRD-L09C432B131.
Click to expand...
Click to collapse
I asked firmware number because you cannot flash lowers firmware number after flashing higher firmware number..
You were on b131??

OG_Winzer said:
I tried it too but it didn't work. I tried again the dload method and I achieved to access to EMUI. I tried to recover from wifi but it sayd "getting package info failed" I can now use the dload method but it gives me an error "software install failed"
Click to expand...
Click to collapse
Alright I think this is a good point , now that you can use the dload method you need to know under which EMUI version you were because the phone won't accept a firmware that is lower or to high compared to your actual EMUI version.
What I did when I was in your case is flashing a rollback package downloaded from honor official site and then flash an old EMUI which is under Android 6.x.
After a few tries you can make it, I hope I've been clear, English isn't my native language
An investment in knowledge pays the best interest.
B.Franklin

Rayan19997 said:
Alright I think this is a good point , now that you can use the dload method you need to know under which EMUI version you were because the phone won't accept a firmware that is lower or to high compared to your actual EMUI version.
What I did when I was in your case is flashing a rollback package downloaded from honor official site and then flash an old EMUI which is under Android 6.x.
After a few tries you can make it, I hope I've been clear, English isn't my native language
An investment in knowledge pays the best interest.
B.Franklin
Click to expand...
Click to collapse
Thanks a lot for your help but I don't really know how but while I was trying to go back to the erecovery menu the phone just boot up and it worked. I did a factory reset because the phone was a bit laggy and now it works.

Lol everything's alright then
An investment in knowledge pays the best interest.
B.Franklin

OG_Winzer said:
I tried it too but it didn't work. I tried again the dload method and I achieved to access to EMUI. I tried to recover from wifi but it sayd "getting package info failed" I can now use the dload method but it gives me an error "software install failed"
Click to expand...
Click to collapse
Ok here i go ... Open the Huawei tool ... And follow steps to install TWRP ...turn of the phone , once it's off hold the volume button down then connect the phone to the PC that would take to some type of fastboot ! Flash recovery the 2 option .... Reboot into TWRP .. from the Huawei tool u would see and option of stock i think there u can copy the recovery OEM info system and boot option flash them all one by one .... Reboot the phone ... And you would be redirected to recovery from WiFi and now it would work since u flash the OEM info now the phone knows what to look for u won't get the getting info failed ... And that's it just makes sure u have a good stable WiFi connection ...
And like a said the more calm and relax u do these the better the first time I screw the phone I almost get a heart atack :crying: it's easy

Unable to get Product ID - Honor 8
hassanjavaid8181 said:
Which number of firmware you tried via dload??
Which firmware number you were on before issue??
Click to expand...
Click to collapse
My Honor 8 broke after it downloaded and installed the very first update. Since the failed 'update' I am NOT able to access Android at all. The phone was stuck on the Huawei eRecovery screen which fails to connect via wi-fi and is unable to connect or retrieve any information from the server to update and repair the phone. I was able to use a 'roll-back' package and install the stock firmware (FRD-AL10), but since I have done the roll-back and restored the stock firmware the phone boots to the first screen where you select your 'Region', then the 'Language', WiFi connection, Agree to the Terms & Conditions, then skip the following steps for Cloud and something else - after all this it goes back to the 'REGION' selection screen, then again the Language selection screen and so on - it just loops and never boots into Android.
Thus I am unable to get the Product ID, the unlock code, etc.
The phone is still locked and UNrooted as all the other solutions rely on the phone being UNlocked and Rooted - but since I DON'T have access to Android I cannot do anything with the phone.
Can someone help me to retrieve the Product ID from an essentially 'DEAD' Honor 8 phone??
---------- Post added at 06:47 PM ---------- Previous post was at 06:38 PM ----------
OG_Winzer said:
Thanks a lot for your help but I don't really know how but while I was trying to go back to the erecovery menu the phone just boot up and it worked. I did a factory reset because the phone was a bit laggy and now it works.
Click to expand...
Click to collapse
I have followed this 'dload' process to load the stock 'FRD-AL10 - ...C00B135' onto my Honor 8, it completes successfully then the phone reboots to where I have to select the Region, then Language, then WiFi, then agree to the Agreement, etc.. then the phone 'loops' back to the Region, Language, WiFi, selection and everything from start.
Is there a way to get past this 'loop' to the point where the phone actually boots into Android?? I cannot access the Product ID, unlock or root the phone.
Any help will be appreciated, thanks.

[Honor 8] update from NRD90M test-keys 5.0 to 5.1

I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico

Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445

I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs

SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work

If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs

SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?

Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes

SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!

Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated

It's EMUI 5.0.1 not 5.1, I think.

"Your device has failed verification..." after Firmware Finder update [SOLVED]

"Your device has failed verification..." after Firmware Finder update [SOLVED]
Hello to everyone!!
I have a problem with my Honor 8, it is the FRD-L09 model firmware B394.
I installed Firmware Finder from Playstore and tried to downloaded the B402 version, it downloaded a lot of packages ota and then tried to install the update without success.
After that, when I turn on the phone, there is this message. If I push the power button the phone starts.
I don't know if it can be useful but if I go into fastboot mode the phone says: phone unlocked and frp locked, but I haven't unlock the bootloader. The phone is new, purchase from the honor site.
Thank you in advance!!
EDIT: I was able to resolve the problem with the rollback guide of huawei, flashing MM via dload!!

When you update with FF, I recommend to use the change DNS thing. Just for the future.

Days Tech said:
When you update with FF, I recommend to use the change DNS thing. Just for the future.
Click to expand...
Click to collapse
I used that option, I did this before on the honor of my friend without issues. I don't understand what happened

xxfraxx said:
I used that option, I did this before on the honor of my friend without issues. I don't understand what happened
Click to expand...
Click to collapse
You can try to reinstall EMUI on it. There is a guide called "back to emui from custom roms", which requires the openkirin twrp, though. Anyway, did you check that you have firmware access with IMEI?

Days Tech said:
You can try to reinstall EMUI on it. There is a guide called "back to emui from custom roms", which requires the openkirin twrp, though. Anyway, did you check that you have firmware access with IMEI?
Click to expand...
Click to collapse
Yes, I checked it before start the update
EDIT: Can I use the restore option into Hisuite?

When using either option, in System Update press the 3dot menu and select full package. This will download one large update rather than the multiple OTA files.

linkazoid said:
When using either option, in System Update press the 3dot menu and select full package. This will download one large update rather than the multiple OTA files.
Click to expand...
Click to collapse
I will do that, thanks!!
There is no way to fix this problem?
EDIT: I was able to resolve the problem with the rollback guide of huawei, flashing MM via dload!!

xxfraxx said:
Hello to everyone!!
I have a problem with my Honor 8, it is the FRD-L09 model firmware B394.
I installed Firmware Finder from Playstore and tried to downloaded the B402 version, it downloaded a lot of packages ota and then tried to install the update without success.
After that, when I turn on the phone, there is this message. If I push the power button the phone starts.
I don't know if it can be useful but if I go into fastboot mode the phone says: phone unlocked and frp locked, but I haven't unlock the bootloader. The phone is new, purchase from the honor site.
Thank you in advance!!
Click to expand...
Click to collapse
Typically you get this problem when you install an update without locking the bootloader.. This happened with me couple of weeks back.. I think happens, cos during the process of the update the bootloader gets locked, but it doesnt come up on the fastboot (donno why)
I just unlocked the bootloader using the OEM code and voila it worked... I was able to get ride of this message as well as root the phone.. Do try and let me know!

@kishorev
have you asked OEM code from huawei site?

Hnktc said:
@kishorev
have you asked OEM code from huawei site?
Click to expand...
Click to collapse
Yes the bootloader unlock code..

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

[GUIDE] HSTool for upgrading firmware of BL locked Huawei View 20 [LATEST FW: 248]

Ty to the folks over at the Honor Mate 20 Pro forum especially @mikeos we are now able to update our Honor View 20 to all available firmwares up to 9.1.0.248
Warning: Do not use this method to upgrade to Android 10, it will brick the device and there are currently no ways to unbrick!
Disclaimer:
Tested with PCT-L29C432, this method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed ***
This means if IMEI is not approved for installation in a certain region SafetyNet might fail, so make sure to enable "Show Only FUll-OTA and Show packages for current region" in FF settings to reduce the risk of flashing a firmware for a other region.
Would people that do not have PCT-L29C432 model please leave there model here so i can add them, many thanks!
Note that if your BL is unlocked, this method will lock it!
People without USB adapter can also use this method to upgrade to approved region firmware updates but make sure only to use Full OTA packages!
Cust partition (region) will stay original based on device oeminfo. C432 wil stay C432 after upgrade and so forth.
Usage:
Make sure to uninstall HiSuite first if installed.
1. Install HiSuite 301 (Do not run after install)
2. Install HiSuite patch
3. Replace XML file in (C:\Users\%UserName%\AppData\Local\HiSuite\userdata\UpdateDogDev)
4. Unzip HStool to c:\
4. Copy rom "update_full_base" to c:\
5. Disable Internet
6. Copy C:\Windows\System32\drivers\etc\host to desktop and remove or comment out 188.225.84.142 query.hicloud.com example https://pastebin.com/haquj6Tr
7. Copy host file back to C:\Windows\System32\drivers\etc\
8. Turn off the phone
9. Hold the volume down button
10. Plug-in the USB cable while still holding the volume down button until you see fastboot
Usage: run HSTool on c:\ and follow prompts.
Requirements
- HSTool
- HiSuite-9.0.2.301
- HiSuitePatchInstaller
- Modified XML to recover Honor View 20 using HiSuite
- Downloaded full firmware using huawei firmware finder (update_full_base) or Direct Download links
Dowloads:
- HSTool:
https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
- HiSuite
https://drive.google.com/open?id=1dgiAJG3kfqscbiutjZ28v6Do-i9lZJz0
- HiSuite XML
https://drive.google.com/open?id=1pajhXUe3th-lPRfBQex2UiyntoxUgL77
- HiSuite Patcher
https://drive.google.com/open?id=1GYpONCf8ci4UwIyBo0Z_1UsN3RBs5gvf
SafetyNet Test List:
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.229 = CTS Pass
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.235 = CTS Pass
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.238 = CTS Pass

Hey, does it wipe data?

mchtt said:
Hey, does it wipe data?
Click to expand...
Click to collapse
No it does not wipe data but as always it's a good idea to back it up first

- Downloaded full firmware using huawei firmware finder (update_full_base)
Click to expand...
Click to collapse
Hi TerrorToetje
What Firmware have you Downloaded with Firmware Finder? I use http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full/changelog_base.xml
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full//update_full_base.zip
But after flashing and booting in Recovery it stops at 5% with an error and restarts the Phone

Is app launch speed difference relevant with the improvement they made?

TerrorToetje said:
Ty to the folks over at the Honor Mate 20 Pro forum especially @mikeos we are now able to update our Honor View 20 to all available firmwares up to 9.1.0.229
Disclaimer:
Tested with PCT-L29C432, this method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed ***
This means if IMEI is not approved in certain region SafetyNet might fail. My IMEI was not approved but I still pass Safetynet on latest firmware.
People without USB adapter can also use this method to upgrade to approved region firmware updates but make sure only to use Full OTA packages!
Cust partition (region) will stay original based on device oeminfo. C432 wil stay C432 after upgrade and so forth.
Usage:
Make sure to uninstall HiSuite first if installed.
1. Install HiSuite 301 (Do not run after install)
2. Install HiSuite patch
3. Replace XML file in (C:\Users\%UserName%\AppData\Local\HiSuite\userdata\UpdateDogDev)
4. Unzip HStool to c:\
4. Copy rom "update_full_base" to c:\
5. Disable Internet
6. Copy C:\Windows\System32\drivers\etc\host to desktop and remove or comment out 188.225.84.142 query.hicloud.com example https://pastebin.com/haquj6Tr
7. Copy host file back to C:\Windows\System32\drivers\etc\
8. Turn off the phone
9. Hold the volume down button
10. Plug-in the USB cable while still holding the volume down button until you see fastboot
Usage: run HSTool on c:\ and follow prompts.
Requirements
- HSTool
- HiSuite-9.0.2.301
- HiSuitePatchInstaller
- Modified XML to recover Honor View 20 using HiSuite
- Downloaded full firmware using huawei firmware finder (update_full_base)
Dowloads:
- HSTool:
https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
- HiSuite
https://drive.google.com/open?id=1dgiAJG3kfqscbiutjZ28v6Do-i9lZJz0
- HiSuite XML
https://drive.google.com/open?id=1pajhXUe3th-lPRfBQex2UiyntoxUgL77
- HiSuite Patcher
https://drive.google.com/open?id=1GYpONCf8ci4UwIyBo0Z_1UsN3RBs5gvf
Click to expand...
Click to collapse
finally the Honor view 20 works as fast as his big brother the Mate 20 PRO, it is a happiness

Kingkaktus said:
Hi TerrorToetje
What Firmware have you Downloaded with Firmware Finder? I use http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full/changelog_base.xml
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full//update_full_base.zip
But after flashing and booting in Recovery it stops at 5% with an error and restarts the Phone
Click to expand...
Click to collapse
PCT-LGRP2-OVS 9.1.0.229
But make sure to download it using FF, and remember only FullOTA-MF packages.

mchtt said:
Is app launch speed difference relevant with the improvement they made?
Click to expand...
Click to collapse
The overall speed is better but also remember we got this:
https://www.xda-developers.com/huawei-honor-gpu-turbo-3/

TerrorToetje said:
This method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed
Click to expand...
Click to collapse
Is the SafetyNet check based solely on IMEI? I noticed you mentioned that your IMEI was not approved but SafetyNet was still fine after the update but I'm not sure about risking my own device.
My device is also a PCT-L29 C432, checking firmware access on FF for PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF says that the firmware is "not approved", so presumably I'm in the same situation.

NekoMichi said:
Is the SafetyNet check based solely on IMEI? I noticed you mentioned that your IMEI was not approved but SafetyNet was still fine after the update but I'm not sure about risking my own device.
My device is also a PCT-L29 C432, checking firmware access on FF for PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF says that the firmware is "not approved", so presumably I'm in the same situation.
Click to expand...
Click to collapse
No it's not really the IMEI but the device fingerprint, the device firmware needs to be Certified in order to pass. Sometimes certain firmwares are builded for internal testing with other fingerprints (Not approved by google), if you have the same device and and planning to go to 9.1.0.229 I cannot think of any reason why you would not pass saftynet. PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF firmware is "not approved" for installation but you will pass saftynet. However if we would force flash a firmware from a other region well that might change things.
There is a setting in FF to only show packages for the current region, those should be fine.
Best Regards,

How will then I update from this firmware I think it's will not be working

jirka607 said:
How will then I update from this firmware I think it's will not be working
Click to expand...
Click to collapse
Please explain what does not work?

I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.

dlhak said:
I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.
Click to expand...
Click to collapse
Well you can't brick it if you followed all steps, if anything comes up i'm here

dlhak said:
I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.
Click to expand...
Click to collapse
I can help too

TerrorToetje said:
Well you can't brick it if you followed all steps, if anything comes up i'm here
Click to expand...
Click to collapse
I am having failed to decmpress the file error
after it finished downloading the recovery with HiSuite.

TerrorToetje said:
Please explain what does not work?
Click to expand...
Click to collapse
No what I'm asking is if I can then update to newer firmware by ota? Or how it will be done

Nevermind, I did two things and I don't know which one fixed my issue, I disabled my Antivirus and moved my "Documents" folder into its original location "C:"
Update is done.
I am now on Magic 2.1

dlhak said:
I am having failed to decmpress the file error
after it finished downloading the recovery with HiSuite.
Click to expand...
Click to collapse
Spaces in path maybe?

jirka607 said:
No what I'm asking is if I can then update to newer firmware by ota? Or how it will be done
Click to expand...
Click to collapse
Ota will work once the newer firmware gets approved for your region, otherwise using this method is an alternative method.