Successfully rebranding Chinese COL-AL10 to European COL-L29: report

Successfully rebranding Chinese COL-AL10 to European COL-L29: report - Honor 10 Guides, News, & Discussion

Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.

mrspeccy said:
Dear community,
- In Step 17, I said ./oeminfo COL-29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
.
Click to expand...
Click to collapse
Can you share me the link to OEM info binary tool ?

It's linked from the thread I used for the first attempt. Direct access: https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo

the problem its how to get the bootloader unlock code ?

sweetjuice said:
the problem its how to get the bootloader unlock code ?
Click to expand...
Click to collapse
Correct. I received the code from Huawei before they stopped handing out the unlock codes. At the moment, I do not know of any alternatives.

mrspeccy said:
Dear community,
(...)
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hey, thanks a lot for this thread!
Soo I am about to maybe do the same as you did – would you suggest/think that just doing the second Part will do the trick for me?
Can't really tell if the first part contained something that's relevant for the second/final part to work.
Furthermore – did you encounter any issues yet, now that you've used the eu rom for a bit?
(And does your device show up as certified within the Play Store?)
Oh and of what I understood, you'll have to do OTA Updates manually?
Thanks again for the effort!

Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.

mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
Great. I can assure you that without magisk but stock recovery it passes safety net as well.

mrspeccy said:
Hi,
if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:
1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:
mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu
3. You "install" the HuRUpdater zip from within TWRP.
If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.
Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
Click to expand...
Click to collapse
I'm the same device and is annoying chinese stuff, but i have some fear to do that. I already have the unlock code, but did not unlocked yet.

Same procedure for AL 10 c675?

Hi mine has this L29 Sp6c200 any chance changing roms?

Boorifee said:
Hi mine has this L29 Sp6c200 any chance changing roms?
Click to expand...
Click to collapse
Yes follow same procedure
.
First of all have a root access to your L29

Great find sir!!
mrspeccy said:
Dear community,
I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.
In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mate-10/how-to/discussion-hard-brick-infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.
I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".
My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:
- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.
- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085.
- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu
(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)
After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.
The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.
I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.
This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.
I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Click to expand...
Click to collapse
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.

tinguyen said:
Hi OP,
Is it possible if you could post a step to step procedure how you rebranded your phone. I have tried what you said but it turned my phone into a "beta" firmware with model number of "FTY-L29". Very weird. I have have missed something along the way now that I can't undo. If you could please help me out. Thank you very much.
Click to expand...
Click to collapse
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.

miststudent2011 said:
Becareful , what was your previous build number and the firmware build number you tried to flash.
Can you also share more details asked in this thread .
https://forum.xda-developers.com/honor-10/how-to/discussion-hard-brick-infos-t3824022
I hard bricked a device after flashing another firmware over this same build fty l09 after flashing one firmware.
Click to expand...
Click to collapse
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz

tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
5.1??

tinguyen said:
I was in COL-AL10 like yours as well because I bought it from 3rd party site. Now I'm just waiting for someone to post a proper procedure of how to undo or install new firmware over the existing one. My phone is still usable but it's just not the right firmware that I wanted and its back to EMUI 5.1 too. zzzzzzz
Click to expand...
Click to collapse
Can you provide me build number before flash and build number you flashed they are important here to solve the case.

vampirian said:
Great. I can assure you that without magisk but stock recovery it passes safety net as well.
Click to expand...
Click to collapse
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?

vollkornbaguette said:
Soo I just managed to rebrand my col-al10 to col-l29 (will share my whole experience soon).
But now it says my device is uncertified in the Play store (said so before Magisk & TWRP were installed and still says so, now that I've installed both and Magisk says SafetyNet is passed).
Any suggestions?
Click to expand...
Click to collapse
Can you use Google Pay after rebanding to EU version?

Johnson Chen said:
Can you use Google Pay after rebanding to EU version?
Click to expand...
Click to collapse
Hey, no I can't - and I am pretty sure it's because of the uncertified status in Google Play.
I think so because when trying to add my mastercard for contactless payment as described in my Google Pay thread, it doesn't work either but this time it's a different error message.

Related

[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.

Debrand from FRD-AL00 to FRD-L09 and update to Nougat.

As some of you might know, I recently bought FRD-AL00 variant of this amazing phone. For those who doesn't know, this is Chinese variant with 4GB of RAM and 32 GB of internal storage. Its European equivalent is FRD-L09 and from same rationale, FRD-AL10 and FRD-L19 are equivalents but it has 64GB of internal storage.
I bought it at AliExpress and it came flashed with FRD-L19C432B131 (wrong firmware). The phone were really unstable, it was rebooting very often, specially when I played videos on YouTube or when phone was under heavy load (low memory and many apps opened).
My first try: Debrand to right EU version (FRD-L09). I did it doing standard procedures: Unlock bootloader/TWRP/Root/Debrand/Flash (FRD-L09C432B131). I followed these tutorials:
** WARNING: Backup your data cause this procedure wipes everything. **
** Do it at your own risk **
1) Unlock bootloader/Install TWRP/Root:
Followed this procedure: https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
1.1) For this step I ran DCUnlocker because I coudn't get my unlock code from Huawei
1.2) Warning: Pay attention and install right version of TWRP, there are two links to download
1.3) Flash superSU
1.3.1) Download SuperSU
1.3.2) Flash it through TWRP
1.3.2.1) Power off and then press volume up + power (unplug USB)
1.3.2.2) Press "Install", select SuperSU ZIP and flash it. Now you're root
2) Debrand using SRKTool
Followed steps in this tutorial: https://www.youtube.com/watch?v=JZVsIKtdgV4&t=310s
2.1) I skipped step to change build.prop, cause right after debrand I reflashed new ROM
2.2) Warning: Don't forget to enable USB debugging, grant access to your computer and grant access to SRKTool actions in SuperSU (it will ask for permission when SRK tries to change something). Make sure SuperSU is running
2.3) After reboot, just power off your phone and move to next step
3) Flash EU ROM
3.1) Make sure you copied ROM FRD-AL09C432B131 and unziped at folder dload on your SDCard
3.2) Press Volume UP + Volume Down + Power
3.3) At this point, your phone might enter in Huawei's recovery mode and start flashing new ROM. It takes about 5 ~ 10 minutes
Now. I realized even "right" ROM for similar model were still unstable. Actually nothing has changed. My next attempt: Nougat!
4) Update to Nougat
This step were simpler. Just execute Charles method and it works seamsless:
Charles Method: https://forum.xda-developers.com/showpost.php?p=69885525&postcount=11
Other responses for different variants: https://forum.xda-developers.com/honor-8/how-to/various-responses-charles-app-b360-t3541342
In my case (FRD-L09C432B131), the response I used was:
Code:
{
"status": "0",
"autoPollingCycle": "1",
"components": [{
"name": "FRD-L09C432B360",
"version": "FRD-L09C432B360",
"versionID": "73856",
"description": "FRD-L09C432B360 (2017/01/18)",
"createTime": "2017-01-18T01:57:51+0000",
"url": "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73856/f1/"
}]
}
PS: did not lost any data on this upgrade but backup, just to make sure you won't loose anything.
Finally...
Now, phone is running FRD-L09C432B360 and seems to be very stable.
Please let me know if you have any questions and follow me on Twitter: emilioyn.

mediasonic said:
As some of you might know, I recently bought FRD-AL00 variant of this amazing phone. For those who doesn't know, this is Chinese variant with 4GB of RAM and 32 GB of internal storage. Its European equivalent is FRD-L09 and from same rationale, FRD-AL10 and FRD-L19 are equivalents but it has 64GB of internal storage.
I bought it at AliExpress and it came flashed with FRD-L19C432B131 (wrong firmware). The phone were really unstable, it was rebooting very often, specially when I played videos on YouTube or when phone was under heavy load (low memory and many apps opened).
My first try: Debrand to right EU version (FRD-L09). I did it doing standard procedures: Unlock bootloader/TWRP/Root/Debrand/Flash (FRD-L09C432B131). I followed these tutorials:
** WARNING: Backup your data cause this procedure wipes everything. **
** Do it at your own risk **
1) Unlock bootloader/Install TWRP/Root:
Followed this procedure: https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
1.1) For this step I ran DCUnlocker because I coudn't get my unlock code from Huawei
1.2) Warning: Pay attention and install right version of TWRP, there are two links to download
1.3) Flash superSU
1.3.1) Download SuperSU
1.3.2) Flash it through TWRP
1.3.2.1) Power off and then press volume up + power (unplug USB)
1.3.2.2) Press "Install", select SuperSU ZIP and flash it. Now you're root
2) Debrand using SRKTool
Followed steps in this tutorial:
&t=310s
2.1) I skipped step to change build.prop, cause right after debrand I reflashed new ROM
2.2) Warning: Don't forget to enable USB debugging, grant access to your computer and grant access to SRKTool actions in SuperSU (it will ask for permission when SRK tries to change something). Make sure SuperSU is running
2.3) After reboot, just power off your phone and move to next step
3) Flash EU ROM
3.1) Make sure you copied ROM FRD-AL09C432B131 and unziped at folder dload on your SDCard
3.2) Press Volume UP + Volume Down + Power
3.3) At this point, your phone might enter in Huawei's recovery mode and start flashing new ROM. It takes about 5 ~ 10 minutes
Now. I realized even "right" ROM for similar model were still unstable. Actually nothing has changed. My next attempt: Nougat!
4) Update to Nougat
This step were simpler. Just execute Charles method and it works seamsless:
Charles Method: https://forum.xda-developers.com/showpost.php?p=69885525&postcount=11
Other responses for different variants: https://forum.xda-developers.com/honor-8/how-to/various-responses-charles-app-b360-t3541342
In my case (FRD-L09C432B131), the response I used was:
PS: did not lost any data on this upgrade but backup, just to make sure you won't loose anything.
Finally...
Now, phone is running FRD-L09C432B360 and seems to be very stable.
Please let me know if you have any questions and follow me on Twitter: emilioyn.
Click to expand...
Click to collapse
plz tell me how can i update mu FRD-L09 to nougat?

is there any complete video tutorial to upgrade FRD-L09? kindly help me...

Is anyone tried this method? I need confirmation , as i bought FRD-AL00 and want to debrand it to L09.
Thanks in advance.

Can it upgrade to B389? And use 2 sims sir?

ALASTOR1111 said:
Is anyone tried this method? I need confirmation , as i bought FRD-AL00 and want to debrand it to L09.
Thanks in advance.
Click to expand...
Click to collapse
I bought the phone AL00 with Noagat on board same as author wrote, but my experience was not good with it, same symptoms as in beginning of this post... After my trying to update to newer Noagat ROM, it was downloaded, flashed and phone could not boot.
So i had to made return to emui 4.1 by using rollback ROM and 3 buttons method. Same unstable work, i finished with going back to AL00 brand and ROM, now it works good, anyway AL00 ROMS multilingual and it is not hard to install all google environment on this ROM...

I have non of complaints on phone, exept i live in Serbia, and my mobile carrier is Telenor. LTE800 frequency on 4G its not supported on FRD-AL00. Only that....

TheHunterVN said:
Can it upgrade to B389? And use 2 sims sir?
Click to expand...
Click to collapse
But now, You got the dual sim function right?

ALASTOR1111 said:
Is anyone tried this method? I need confirmation , as i bought FRD-AL00 and want to debrand it to L09.
Thanks in advance.
Click to expand...
Click to collapse
Try this guide 100% working https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-t3612873

Not for me, i'm on EMUI 5 (android 7.0) and its dual sim phone.

ALASTOR1111 said:
Not for me, i'm on EMUI 5 (android 7.0) and its dual sim phone.
Click to expand...
Click to collapse
Then try this https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220

I am in China, My cell phone is AL00(EMUI5), after use SRKTOOL change oeminfo, at that time I thought the phone bricked.
Fortunately L09C432B131 firmware rescue my phone, and receive OTA update to B360.
After that, I did not receive any update, even place firmware(394/391/388) into dload.
How can I get an update, anyone help me?

heretic43 said:
I am in China, My cell phone is AL00(EMUI5), after use SRKTOOL change oeminfo, at that time I thought the phone bricked.
Fortunately L09C432B131 firmware rescue my phone, and receive OTA update to B360.
After that, I did not receive any update, even place firmware(394/391/388) into dload.
How can I get an update, anyone help me?
Click to expand...
Click to collapse
U faced the same issue like me. Sadly, i font know why and stayed in b360 for 2 months. Maybe stay in this rom 4ever )

TheHunterVN said:
U faced the same issue like me. Sadly, i font know why and stayed in b360 for 2 months. Maybe stay in this rom 4ever )
Click to expand...
Click to collapse
Maybe we should back to AL00, but I don't want to, just stay here...

heretic43 said:
Maybe we should back to AL00, but I don't want to, just stay here...
Click to expand...
Click to collapse
Me too. Do u have the stock AL00 rom?

TheHunterVN said:
Me too. Do u have the stock AL00 rom?
Click to expand...
Click to collapse
I have a TWRP backup B387, if back to AL00, restore backup or change omeinfo, which one should I choose?

heretic43 said:
I have a TWRP backup B387, if back to AL00, restore backup or change omeinfo, which one should I choose?
Click to expand...
Click to collapse
Honestly i dont know. Maybe another pro can help you. But can u upload ur backup plz? I will try to back to b387

TheHunterVN said:
Honestly i dont know. Maybe another pro can help you. But can u upload ur backup plz? I will try to back to b387
Click to expand...
Click to collapse
backup Partition (boot, cust, system) not include OEM, do you really want to try it?

Hello, i am trying to rebrand my new honor 8 from China. It's an FRD-AL10 with EMUI 5. Do i proceed with the steps as seen in the first post?
Edit: I've bricked it. Any suggestions?

This thread is a oneway ticket to the brick =(

[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.

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.

Database Info

welcome