Database Info

My honor 8 refuse update

hello, i will try to explain my problem :
My honor was bricked by an error of flash.
I have "repair" it by a way found here on xda : flash boot.img, cust, recovery, system, and after i have could make the update by dload.
Then all was ok under the firmware LO9C432B131.
But now, i can't update to B360...
Before my brick, i had the ota update to B360... but now i have nothing....
If i try the update by dload, it says : "problem compatibility"
I have downgraded to B120 and ota update was good for B131. But nothing for B360
If someone can explain me...thank you so much (actually the phone is no rooted and relocked)

Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.

sysak said:
Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.
Click to expand...
Click to collapse
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.

takichiman said:
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.
Click to expand...
Click to collapse
Yes, but I believe the issue comes from manual flashing of partitions. I have also tried that when my phone was dead and the recovery and eRecovery always threw "package incompatible" error. I think restoring the entire file system to factory condition (which happens during the rollback process) is the sure best way to fix all issues.

Thanks for your answers,
I finally got the update with the charlie app...(not easy this method !)
But now i don't know if ota will be ok...
I will perhaps do the rollback as you said to restore the entire file system...

Honor 8 (FRD-L09) brick help.

Hello.
I need a help with my Honor 8, it's been bricked and I honestly don't know if there is much to do in my current situation.
So the phone has locked bootloader and stock recovery.
Fastboot always returns 'Command not allowed'
What exactly happened:
I was running Stock ROM, rooted, TWRP Recovery with unlocked bootloader.
An official OTA update popped-up on my phone, I was in a rush and I missclicked (don't even ask lol) and the update started installing, I knew I'm screwed.
So I was about to play with fastboot, but it always returned 'Command not allowed'.
And probably the worst mistake happened a few minutes ago (6:00 am trying to fix it half a sleep), I was reading some posts about the dload method, >>FASTFORWARD I installed an official update using the dload method and locked my bootloader by doing this.
QUICK SUMMARY:
So I'm stuck on a bootloop.
The 3 button combo works.
Stock Recovery works as well.
Fastboot does NOT work. (I tried flashing, unlocking, temp-booting.. but nothing)
adb always returns error:
Code:
device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is there ANYTHING I can do in my current situation? :crying:
Thanks in advance for any help.
Have a nice day.

Hello, as long as you have an official recovery, a proper BOOT.IMG and the dload method is working there is still a chance( i hope), the only thing you need to know is that if the firmware is the wrong for your phone it will deny it. It means that is if you try to install an android 6.0 based stock ROM over a 7.0 ROM , it will say software upgrade failed or something like that.
You need to know under which Android version you were and install the same or maybe a more recent one but not to far away from your actual ROM, try the next one. You can also try to downgrade USING a rollback package that you can download on honor official site. Make sure that's the the correct file for your phone.
Hope you'll make it bro, let me know how the situation evolve
(sorry for any language mistake, english isn't my native language.)

Rayan19997 said:
Hello, as long as you have an official recovery, a proper BOOT.IMG and the dload method is working there is still a chance( i hope), the only thing you need to know is that if the firmware is the wrong for your phone it will deny it. It means that is if you try to install an android 6.0 based stock ROM over a 7.0 ROM , it will say software upgrade failed or something like that.
You need to know under which Android version you were and install the same or maybe a more recent one but not to far away from your actual ROM, try the next one. You can also try to downgrade USING a rollback package that you can download on honor official site. Make sure that's the the correct file for your phone.
Hope you'll make it bro, let me know how the situation evolve
(sorry for any language mistake, english isn't my native language.)
Click to expand...
Click to collapse
Woohoo, after a few tries & factory resets I was able to boot my phone again using the dload method :victory: The TWRP recovery has vanished and it seems like there is no sign of root(?) either, I'm gonna redo everything again, thanks so much for your help, you saved me bro <3 Have a wonderful day.

I am really glad that you get your phone back on track ! And yh the dload method bring you to stock everything, stock recovery,stock system etc etc.
Have a nice day

crepnik said:
Woohoo, after a few tries & factory resets I was able to boot my phone again using the dload method :victory: The TWRP recovery has vanished and it seems like there is no sign of root(?) either, I'm gonna redo everything again, thanks so much for your help, you saved me bro <3 Have a wonderful day.
Click to expand...
Click to collapse
Hi Crepnik,
Even I am facing the same issue. Can you please tell me which ROM did you download.
My phone was update to Nougat EMUI 5.0
Thanks

[email protected] said:
Hi Crepnik,
Even I am facing the same issue. Can you please tell me which ROM did you download.
My phone was update to Nougat EMUI 5.0
Thanks
Click to expand...
Click to collapse
Try to flash the rollback package and then an EMUI 4.x ROM. They're both available on honor official site

Rayan19997 said:
Try to flash the rollback package and then an EMUI 4.x ROM. They're both available on honor official site
Click to expand...
Click to collapse
Hi Ryan,
Thank you so much for responding.
I could see two ROM in the official site http://www.hihonor.com/in/support/
HONOR 8 Firmware (FRD-L02, C675B130CUSTC675D002, India)
HONOR 8 Firmware (FRD-L02, Android 6.0, EMUI 4.1, C675B160, India Channel)
I tried with both the ROMs but no luck
I placed the update.APP file inside sdcard but the update stops at 5% showing that it has failed.
I also tried flashing the recovery.IMG in fastboot mode.
I have lost all the hopes in my new phone
In the rescue mode it says UNLOCKED.
Please guide me with some detailed steps.
Thanks

Flash the stock recovery of the ROM that was previously installed on your phone , then with dload method flash the rollback package downloaded from honor site , and finally flash one of the two ROM, it may resolve your issue because the phone won't accept a lower firmware without flashing the rollback package first. As long as you can use dload method it should be fine.
If it doesn't work try to flash boot.img , recovery.img, cust.img, vendor.img and system.img extracted from a clean firmware downloaded on honor official site
Let us know how the situation evolve

Semi bricked honor 6x bln - L24. Please read, weird problems

So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?

The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.

All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x

Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it

TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?

TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360

xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?

xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.

do i need the stock recovery flashed in order to do dload?

well i followed the first half of your guide and it successfully "updated" but my storage is encrypted

xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed

well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that

xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really

okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?

xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP

RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:

xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!

Reisntalling B385 stock rom to my FRD-L04

Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:

The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.

hackslash said:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
Click to expand...
Click to collapse
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Sent from my FRD-L04 using Tapatalk

juanboja said:
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Click to expand...
Click to collapse
Unlock your bootloader and follow this guide:https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306/
Choose the B385 firmware or any newer firmware available for your region.

So I decided to finally reinstall the stock firmware in my Honor 8 FRD-L04 in B389, and this is where the nightmare began.
- I made a full backup with TWRP just in case and I decided I wanted to start from the earliest firmware possible available.
- I started unrooting my phone using the UnSU zip by Osmosis.
- Then I flash via bootloader the recovery and boot image of the firmware B360.
- I flashed the rollback package from the Huawei official site with the B122 firmware also available at the same place. I saved the rollback package in my root directory in the dload folder, and loaded it with the 3-button method. After this I wasn't able to boot my phone normally, I was stuck in a boot loop. I still continue with the next firmware, the B122, and it was successfully loaded (this also relocked my bootloader).
- It is important to say I clear many times the cache and wipe/erase data through stock recovery options, and also tried to erecover but I wans't able to connect to the WiFi. I guess something was missing (at this point I was already going crazy).
- I was still stucked at a boot loop after loading the B122, so I decided to unlock my bootloader and flash the twrp 3.1.1-1-frd.img
- From there I tried to wipe data and cache and system and everything, but I wasn't able because an error saying unable to mount always appeared.
- After rebooting, since I already had unlocked the bootloader, the initial message prompting: "press power to continue, press for 3 seconds for erecovery, etc..." appeared.
- I enter the erecovery options with the hope it will do something... and it did!!! I could connect this time through WiFi and the system asked to update the firmware and many other things it said at that moment. This was the first time I felt relieved through the night.
- The phone updated perfectly, it started at the firmware B122 and I kept updating it until I reached the B389.
- I unlocked the bootloader again and rooted the phone. And everything is running smooth as silk!
I know this is a very long story, but I just want to get it out there in case anyone is facing the same problem I just passed. Hope this helps someone and brings peace to them! =) Good luck!

I believe B385 is not functional with TWRP. Flash B360 and reboot to recovery. This should go to stock recovery, where you will have to do a factory reset. I got EMUI working, but it refuses to update to any newer version (it does show B380 but doesn't update). Also there should be updates after making that update. The updates did work for other people, so you may be able to have it working.

juanboja said:
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
Click to expand...
Click to collapse
Try flash B360 then OTA to 388 or 391 (If 391 singed).

blackbuffalo said:
Try flash B360 then OTA to 388 or 391 (If 391 singed).
Click to expand...
Click to collapse
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk

juanboja said:
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0

blackbuffalo said:
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
Click to expand...
Click to collapse
Thank you very much for this info!
Sent from my FRD-L04 using Tapatalk

[NEED HELP] Unbrick Honor 6x

I've somehow bricked my 6X.
I have an EU version successfully debranded to India variant BLN-L22 and upgraded to EMUI 8.0, unencrypted and rooted with Magisk.
Something went wrong during the flash of AEX for hi6250 devices (which is reported to be 6X compatible ): I was mainly stuck in a bootloop except for two times when the phone booted, but internal storage wasn't recognized properly (in settings I was able to see the correct percentage of available space but in default file manager I wasn't able to access it and also downloading files to internal storage was impossible, as if my it was full - which isn't true since I was able to move file there through TWRP file manager).
At that point I was pretty pissed, I've forced fastboot and used update.bat to flash stock Oreo again and here things screwed up.
I took a full TWRP backup before experimenting with AEX and copied it to my pc; I'm able to push it to internal storage through adb, but then TWRP isn't able to restore it, dunno why.
My phone is in these condition now:
fastboot is available, commands from pc are working here
bootloader is unlocked
FRP is unlocked
I have a working TWRP recovery (askuccio 3.2.3) which I can access and use; I'm able to replace it with Elemental 3.2.1, with the one provided in the "update.bat" thread (which is another 3.2.1 version) or with stock recovery
if I replace TWRP with stock recovery and boot into it, it shows the update screen and it freeze at 5%, then reboot; no factory reset option there
when I'm into TWRP I can push files from pc to internal memory through adb
pretty sure my phone is still decrypted, dunno if it's still rooted tho
eRecovery is gone
I have no idea how eRecovery gone missing since I never touched that partition; trying to flash ERECOVERY_RAMDISK.img through fastboot using "fastboot flash erecovery_ramdisk erecovery_ramdisk.img" which fails (remote: command not allowed) and "fastboot flash recovery2 erecovery_ramdisk.img" which fails (remote: partition length get error) as well as through Multi Tool (the size or path does not match the file system markup); if I try to boot into eRecovery I get error mode screen: Func NO : 11 (recovery image) Error No : 2 (load failed) and I have no idea how to try to restore it in another way (pretty sure all I need is to factory reset through it and then reflash the firmware for unbrick my phone).
Atm I've tried only Multi Tool: I can successfully flash everything in the unbrick section but it doesn't solve my problem (guess it's due to my missing eRecovery).
I still need to try Image Download method (which I would like to keep it as last resource since it requires to disassemble my device and since I have a working fastboot and TWRP), HuRu and dload (I don't have a micro SD big enough atm, only 2GB - dunno if it can can work from internal storage the same).
Thank you for any help.
@player615 @shashank1320 @vovan1982 @RedSkull23

I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.

shashank1320 said:
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
Click to expand...
Click to collapse
How do I do that?
I mean, flash OEMINFO and Custom Bin and then dload method as per debranding guide or HWOTA7, since I'm on Oreo/Emui8 now?

You already debrnaded to Indian version and then updated to Oreo right?

shashank1320 said:
You already debrnaded to Indian version and then updated to Oreo right?
Click to expand...
Click to collapse
Exactly. I was on BLN-L21 Nougat (EU), debranded to BLN-L22 (Indian) through fast method (flash oem and cust bin, dload, update through system update) and then upgraded to Oreo through HWOTA8_BLN - script method.
Multi Tool list my device as BLN-L22 8.0.0.510(C675).

Just dload b340 indian variant. You should be fine

I restored my device countless times with HuRUpdater, the best tool I used on Huawei devices. It always go fine, but a microSD of at least 3GB is required (files to flash are usually 2,70GB). Probably the device won't boot with stock recovery because as you pointed out, it needs to format first before booting since that you was decrypted. HuRUpdater needs to be executed from microSD because it flashes files from there to internal storage, so flashing from there isn't allowed due obvious reasons.
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)

shashank1320 said:
Just dload b340 indian variant. You should be fine
Click to expand...
Click to collapse
RedSkull23 said:
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
Click to expand...
Click to collapse
dload doesn't work, I guess it's because I miss eRecovery.
If I hold vol+ vol- and power my phone boot into TWRP; I've tried replacing it with stock recovery but it freeze at 5%.
Any way to flash eRecovery from fastboot or as a zip from TWRP?
Gonna get a SD and for HuRu if I won't be able to solve it differently.
Edit: managed to boot into dload screen, but it states "software install failed".

AleNonsense said:
Edit: managed to boot into dload screen, but it states "software install failed".
Click to expand...
Click to collapse
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)

RedSkull23 said:
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
Click to expand...
Click to collapse
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!

AleNonsense said:
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
Click to expand...
Click to collapse
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!

Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.

player615 said:
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
Click to expand...
Click to collapse
Wait: wiping /data with TWRP makes it visible through custom recoveries since that it removes encryption, but when you flash whole EMUI 8 on system stock recovery_ramdisk is reflashed on the recovery partition too, and it forces to reformat /data before booting because if not it'll say that OS is seriously corrupted bla bla bla... EMUI 8 doesn't have to run encrypted?
By the way HuRU is faster, easier and leaves bootloader unlocked.

RedSkull23 said:
If you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Click to expand...
Click to collapse
Nope: don't get me wrong, but I'm here since 2012 and I'm pretty used to this kind of stuff.
I can assure you I haven't picked wrong packages nor any other noobish error: in fact I wouldn't even had to post here if I had encountered just some standard problem lol... my device wasn't fixable through usual ways, or else I would have been able to
RedSkull23 said:
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse
Just heard back from assistance and they are waiting for a new motherboard since there was nothing to do, good to me I was still covered by warranty.
Now it would be nice to know what screwed up my device so bad, since I hadn't any problem till the flash of AEX for hi6250 devices (so 6X compatible) and even in the case it wasn't flashing a wrong rom has never fked up a motherboard in my experience, but whatever.
My only trouble is I'm pretty sure I won't be able to unlock bootloader when my phone will be back, now
Also, thank you to everyone who tried to help!

try this
i had issues also until i found this step by step, i named everything just as he has pictured and made sure to just add the .zips all 3 needed, got correct FW from FW finder and also be sure to put the actual HuRuUpdater.zip in the same folder with the FW files and name the parent folder just like the pic on post shows...poof working stock FW and did not relock my BL....Honor 8 FRD-L04 reverted from no OS to stock 7.0 on EMUI 5 https://www.getdroidtips.com/hurupdater-tool/#comment-109621
RedSkull23 said:
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse