Database Develop

Error mode, really hard bricked

I tried to force update to b170, resored the backup from howtoroot thread and flashed stock recovery from within twrp, rebooted and my devicve is stuck on
ERROR MODE
err no11 recovery image
errror no 2 load failed
doesnt boot to fastboot, cant be seen by pc
cant even turn it off... it is infinite loop if i hold power button it boots "huawei logo for 1 second and again error mode"
Please help me to recover my device :/

Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect

aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode

aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
HI man I have the some problem error mode screen but in oreo update p8 lite 2017 any solution plz

p181153 said:
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
Click to expand...
Click to collapse
If you solved your problem tell me plz plz plz

jalel25 said:
If you solved your problem tell me plz plz plz
Click to expand...
Click to collapse
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community

p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
I hope one of them help me ?

jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.

mijanto313 said:
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
Click to expand...
Click to collapse
I tried that. My phone has been in this state for probably a month already. I heard the only solution is DC Phoenix via testpoint method.

Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?

p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots

Botar230 said:
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Click to expand...
Click to collapse
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !

Freysheur said:
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Click to expand...
Click to collapse
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot

Botar230 said:
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Click to expand...
Click to collapse
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !

Freysheur said:
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Click to expand...
Click to collapse
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs

Botar230 said:
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
Why before i used the flash recovery and it worked ?
Do you have an answer to the error " FAILED (remote: partition length get error) " ?
---------- Post added at 11:25 AM ---------- Previous post was at 10:40 AM ----------
Ok, i try install ROM via TWRP..
I have no errors but i bootloop again.. and he puts me in the menu Huawei eRecovery..
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I try install ROM via Fastboot CMD.
C:\Users\Alban\Desktop\fastboots>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
C:\Users\Alban\Desktop\fastboots>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15524 KB)...
OKAY [ 0.389s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.413s

Hmmmm, i installed MorfuZ rom, he boot but he restart alone..
So I do not have a rom ...

jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Everyone, I made a guide on my website to unbrick the device.
Here is the link:
http://mrviking.simplesite.com/440246066

Stuck in ERROR MODE

hello guys pretty new to the flashing scene and ive made a mistake. ive tried flashing different twrp.img files and nothing and i mean nothing will make the recovery work, dont have access to the standard recovery either. my model is VTR-L09C440 unlocked bootloader. ive tried every possible solution that i can find and nothing works. Please help thanks
edit
i can flash kernals and recovery imgs via fastboot but still wont load up
apparently my system is 8.0.0.046(0BZC
any help? been here for like 10 hours trying to fix this!

no help i see......

How did you flash twrp ?
fastboot flash recovery_ramdisk yourtwrp.img

Blackball said:
How did you flash twrp ?
fastboot flash recovery_ramdisk yourtwrp.img
Click to expand...
Click to collapse
yeah i think i did it like that but it won't allow me to go in twrp itself by doing the commands volume up. keeps showing
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR!
FUNC NO:11 {RECOVERY IMAGE}
ERROR NO:2 {LOAD FAILED}

absynteZero said:
Hello Cloud,
arff fianl fantasy 7....arff arfffff so many hours without sleepin...sin is defeated!
it seems you don't flash well the TWRP.
frist you need the good,
https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449
verify drivers.
verify that files you want to flash are in the fastboot.exe computer folder (the better is system root c
Go to fastboot mode
try
fastboot erase recovery_ramdisk
flash as
fastboot flash recovery_ramdisk nameofTWRPfile.img
and try again.
if you're really bricked, try as
fastboot flash recovery nameofTWRPfile.img
?
after this, if issue persist, maybe try to extract ramdisk.img from official update from Firmware finder with YOUR soft version.
and flash it before flash TWRP as
fastboot erase ramdisk
and
fastboot flash ramdisk RAMDISK.img
take the manufacturers cables not noname , and try to change usb
Click to expand...
Click to collapse
ive had no luck trying that. will give the huawei Multi tool a shot see if that can fix my problem

Solved Successfully flashed the update.app files with dc phoenix app. but it still says im on fromfuture which i dont understsnd considering i flashed a clean

Stuck in TWRP

So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help

It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?

Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too

If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.

AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.

Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.

ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.

AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update

ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.

AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!

ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical

Bricked P20 PRO, please help.

I was upgrading to EMUI 9.1 and relocking bootloader, but ended up with botloop ony my P20 Pro.
Fastboot - working.
Bootloader - unlocked.
FRP - not visible (was unlocked).
Erecovery - "Getting package info failed."
HiSuite 9.1.0.305 - "System recovery isn't available on this device."
TWRP flashing - can't enter it after fastboot reboot.
Code:
fastboot oem get-build-number
(bootloader) :CLT-L09 8.1.0.164(EEAC782)
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L09 9.0.0.195(C432E5R1P9)
I was trying to use Huawei Update Extractor with 8.1.0.164(EEAC782), 9.0.0.195(C432E5R1P9), CLT-LGRP2-OVS 9.1.0.325 as following:
Code:
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
Sadly it didn't brought any result.
Please help me with resolving this issue.

Did you try with the dload method?

aka.petteri said:
Did you try with the dload method?
Click to expand...
Click to collapse
Dload was my thought, but i didn't got OTG cable yet.

aka.petteri said:
Did you try with the dload method?
Click to expand...
Click to collapse
I tried dload method.
With 8.1.0.164, 9.0.0.195, 9.1.0.325 i'm getting "Software install failed".

I managed to boot too TWRP.
I had to patch it from fastboot, then boot to recovery with VolUP, then make wipe and hold still VolUp.
Seems like EMUI patched, so P20 is back!

Cinceres1989 said:
I managed to boot too TWRP.
I had to patch it from fastboot, then boot to recovery with VolUP, then make wipe and hold still VolUp.
Seems like EMUI patched, so P20 is back!
Click to expand...
Click to collapse
Hi,
How did you manage it to bring it back?
I have the same issue, in fastboot I see my phone, but can't get into bootloader nor erecovery..
Everything unlocked, but I have a black screen!

Honor 9 lite with weird error wile booting: Func NO : 15 (bl31 image) |I Func NO : 1 (security verify failed!)

Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards

oloco2 said:
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Try something from the following:
A) in fastboot mode use command
fastboot erase userdata
reboot and try to flash stock recovery_ramdisk and flash full stock FW via dload
B) try to update your phone via eRecovery - turn off, plug the cabel and press and hold Power + Vol Up. In eRecovery's menu select "Download latest etc etc."
C) fully discharge the battery and try previous methods
(in your case little chance, this method works with error 11/2, you have 15/1)
D) use testpoint method
E) paid services (dc-phoenix etc.)

Thank so much for your help -Alf-
Unfortunally I have to say that now my phone is not able to enter fastboot mode.
What I dd:
The comands you asked for:
fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0JRE)
OKAY [ 0.007s]
Finished. Total time: 0.009s
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
OKAY [ 0.008s]
Finished. Total time: 0.009s
As nothing changed, I used testpoints.
I had to enter fastboot oem unlock 5KKK7... in order to unlock bootloader again
But now.. Phone keeps rebooting with the same eror window as before, but I'm still unable to ener not fastboot mode not erecovery.
Now i really feel locked, as I think there's nothin else I can do.
I also unplugged battery multiple times in order to discharge all the circuit, but no news...
Any other idea, please?
Regards

oloco2 said:
Unfortunally I have to say that now my phone is not able to enter fastboot mode
Click to expand...
Click to collapse
oloco2 said:
The only way I can use thee phone is via fastboot.
Click to expand...
Click to collapse
?

Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...

oloco2 said:
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
Click to expand...
Click to collapse
Try this method - turn off, hold Volume Down and plug the cabel.

oloco2 said:
System 8.0.0.046(0JRE
Click to expand...
Click to collapse
oloco2 said:
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Click to expand...
Click to collapse
oloco2 said:
failed input oem_nv_item error
Click to expand...
Click to collapse
oloco2 said:
SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
Click to expand...
Click to collapse
Testpoint or dc-phoenix, bro.

-Alf- said:
Testpoint or dc-phoenix, bro.
Click to expand...
Click to collapse
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards

oloco2 said:
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
Click to expand...
Click to collapse
You have to flash board software using testpoint . Google it, I have no experience with that.

Ok. Thank you -Alf-. I will have a look to google.
But in the meanwhile, if someone else coukd help me a little bit, will be more than welcome
Regards!!

Hi -Alf-
I got good news for me. I got fastboot working again. I need to use potatonv in order to get it, but anywayI think it's good news.
Please, any other idea in order to make it come back, please?
Thank you

oloco2 said:
any other idea in order to make it come back,
Click to expand...
Click to collapse
your phone has an incomplete FW (System 8.0.0.046 (0JRE)),, an unknown model and a problem with oeminfo. Do you even read what I'm writing???
https://forum.xda-developers.com/t/...-security-verify-failed.4453855/post-86982695

Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards

oloco2 said:
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/i-bricked-my-honor-9-lite.3799176/post-76943641

Hey -Alf- !
I can ay that finally I got it working.
How I did it:
I got a full firmware for my devce and using Huawei Update extractor I extracted all the images to a folder.
Using a little script un batch I createda .txt with multiple lines:
fastboot flash cache cache.img
fastboot flash crc crc.img
fastboot flash curver curver.img
fastboot flash cust cust.img
fastboot flash dts dts.img
fastboot flash eng_system eng_system.img
fastboot flash eng_vendor eng_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmet erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
fastboot flash fastboot fastboot.img
fastboot flash fw_hifi fw_hifi.img
fastboot flash fw_lpm3 fw_lpm3.img
fastboot flash hisiufs_gpt hisiufs_gpt.img
fastboot flash boot kernel.img
fastboot flash modemnvm_update modemnvm_update.img
fastboot flash modem_fw modem_fw.img
fastboot flash odm odm.img
fastboot flash package_type.img package_type.img
fastboot flash patch patch.img
fastboot flash preas preas.img
fastboot flash preavs preavs.img
fastboot flash preload preload.img
fastboot flash product product.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash sensorhub sensorhub.img
fastboot flash sha256rsa sha256rsa.img
fastboot flash system system.img
fastboot flash teeos teeos.img
fastboot flash trustfirmware trustfirmware.img
fastboot flash userdata userdata.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash verlist verlist.img
fastboot flash version version.img
fastboot flash xloader xloader.img
And I run all the commands.
Some of them gave me some errors like partition lenght or something like that, but at the end, once rebooted, the error was gone.
Then, I updated all the firmware usong dload.
Now I'm facing a little error about oeminfo. I think itis due to the fact that the firmware I used was rusian, and my phone is from EU. I already created another thread in this forum.
I want to thank you for your tme and your ideas.
I hope this post can help someone over there with an error like mine.
Thank you very much for your time and help
Regards

No problem. Btw, why russian FW? I gave you a link with EU FW . Okay, your choice...
oloco2 said:
Now I'm facing a little error about oeminfo
Click to expand...
Click to collapse
Little?

Yes, The russian FW I flashed was yeterday. Now, after you replied to my post, I will try to upgrade FW to the EU version. I hope now everything works as it should
The "litle error" about oeminfo is:
"/preas/xxx" in some parts of the settings. I read somewhere it was due to oeminfo.I'm I wrong?
Thank you!!

I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!

All fixed!!
I found this oeminfo:
OEMinfo & Dump & CERT Honor 9 Lite (LLD-ALL)
OEMinfo & Dump & CERT Honor 9 Lite (LLD-AL00 / LLD-AL10 / LLD-AL20 / LLD-AL30 / LLD-TL00 / LLD-TL10 / LLD-L21 / LLD-L22 / LLD-L31 / LLD-L32 / LLD-L42). Share File Certificate, File Dump, OE…
azrom.net
After updating it, all info seems to be correct in about. Also, there's a new OTA for me!
What a road gave me this phone
I hope I'mnot comming back to here in a while
Thank you for all your help
Regards!!!

oloco2 said:
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
Click to expand...
Click to collapse
Kindly share your batch script, pls