Apparently, trying to get myself to install a clean rom has ended up on me having no rom at all, only FastBoot access and access to TWRP 2.8.1.0. So. How in this world do i install ANYTHING, when apparently every single ROM version patches over the older versions? where do i find a clean stock rom i can install through TWRP? ( Default recovery throws a cust error ). This is kind of getting insane already.
I hate being this kind of person who registers on a forum just to have some ( possibly incredibly stupid ) problems solved. But here i go.
Since i've heard that there's a lollipop update for Android ( literally 2 days ago ), i decided to start an upgrade. Sadly, it seems like somehow when i installed Se7en ROM, i ****ed something up. After looking around i did manage to find a proper copy of TWRP 2.8.1.0 that i could use for recovery, and after fighting a half brick i had following some of the comments left over here i have gotten back to "normal operation"
The device boots normaly but it seems like it won't do anything on Recovery. The bootloader states it's from version 133 so i am trying to install that as i am writting this. With that said, i see a lot of confusion going on on how to update, and the few threads i find with boot and recovery images, seem to be either dead or get my phone stuck on a bootloop. the custom recovery seems to work but it is not doing any IO operations, apparently. If this is relevant, it seems like the caché partition has been broken somehow. something that would easily be fixed, if it weren't because of the fact it isn't writting or reading.
Is there a way i can safely go to stock from where i am? ( i got an unlocked bootloader, so there is that ), and from there on, how do i safely upgrade to a more modern build? All the mirrors for TWRP2870 seem to crash, returning my phone back to the bootloader. And apparently that is mandatory for an upgrade later on.
I apologize for my lack of knowledge on this.
I apparently have deleted my somewhat working system for nothing. I need to have the stock firmware as a ZIP file for it to be flashed. Does anyone have an idea?
Aaaand now, trying to flash an updated bootloader and recovery i am stuck in what looks like a complete full brick.
Go me.
Flash MyRom 1.2 (http://forum.xda-developers.com/showthread.php?t=2948887) through TWRP. Now you've should got a running system back.
Then flash the emui 2.3 stock Recovery. If you don't find any link the download a B1xx Rom (the last 4 characters of the build-number matters) and extract recovery.img with the huawei update extractor.
After beeing back on stock recocery flash B609 with the normal update-methode. Go on for B621 -> B623 -> B830.
TWRP 2.8.7.0 will work once you updated to at least B609.
I'd been in a comparable situation once again. The correlation of different firmwares/recoverys/custom roms is just confusing when you start dealing with.. So I really can feel with you[emoji14]
l3Nni said:
Flash MyRom 1.2 (http://forum.xda-developers.com/showthread.php?t=2948887) through TWRP. Now you've should got a running system back.
Then flash the emui 2.3 stock Recovery. If you don't find any link the download a B1xx Rom (the last 4 characters of the build-number matters) and extract recovery.img with the huawei update extractor.
After beeing back on stock recocery flash B609 with the normal update-methode. Go on for B621 -> B623 -> B830.
TWRP 2.8.7.0 will work once you updated to at least B609.
I'd been in a comparable situation once again. The correlation of different firmwares/recoverys/custom roms is just confusing when you start dealing with.. So I really can feel with you[emoji14]
Click to expand...
Click to collapse
Well. i may probably be in trouble since i tried to flash directl ythe B609 bootloader and Recovery from the update.app ( as it looks like 609 is the last known "full" update ), and i can't seem to get back to it. But if i do manage to get enough to flash TWRP again I now know how to get back on track. Right now no matter what buttons do i press, i am stuck at the carrier logo, then it jsut reboots again.
Thank you very much for the reply! i now wish i was patient enough to have waited for this instead of doing a bad flash.
Was there an error or was the B609 Flash successful? Maybe (when you managed to boot into bootloader) flashing TWRP 2.8.1.0 fails now. If so, then try version 2.8.7.0 and use MyRom 3.3.
Did you try connecting your (powered off) device to your PC while pressing volume down permanently? I'm not sure if the phone boots itself now, probably you have to press power, too. Hopefully the phone boots now into bootloader.
l3Nni said:
Was there an error or was the B609 Flash successful? Maybe (when you managed to boot into bootloader) flashing TWRP 2.8.1.0 fails now. If so, then try version 2.8.7.0 and use MyRom 3.3.
Did you try connecting your (powered off) device to your PC while pressing volume down permanently? I'm not sure if the phone boots itself now, probably you have to press power, too. Hopefully the phone boots now into bootloader.
Click to expand...
Click to collapse
Fastboot gave me no failures. it did your typical "sending data .... OK" message. Only remarkable message is that it said that fastboot was informed that the target device only had 800MB ( in bytes ) available for usage. which i fail to recognize as a proper size for any volume that the device could contain.
I could not get into either the recovery or the bootloader, i even tried to press all three buttons and see if i could initiate a update, at least to know if the recovery worked. No luck.
I don't have my phone right now with me since i'm out and i am using an older, backup phone, but i will definetly try once i get back. and give it another try, maybe doing it coldly will make it work.
Related
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
Hi everyone,
I am looking for the way to start this phone directly on the fastboot mode as it is softbricked and it doesn't recognise anything (i can't go on recovery, no matter which one) after I flash a stupid update.app of 500 mb
I think I have to flash system.img boot.img and recovery.img
Thanks in advance, it don't go on the fastboot by himself like he did before, after i flashed twrp
Edit: Found, vol - & power while wired to the computer. Gonna see why i can't access even the stock recovery
Press and hold power and vol(-) buttons ... long time. Of course first remember to connecting device to PC by USB. [emoji14]
Hundreds times...it was described on this forum. [emoji26]
Sent from my HUAWEI P7-L10 using Tapatalk
New question, I installed the B121 full stock, rom, kernel, everything like when i baught him first day, except of my unlocked BL.
Now, the stock recovery can't install ANY update.app it always write "FAIL" without getting any %, it just fail as it start. I can't find the way to resolve this.
And I got many questions,
Can the recovery of B121 install the B609 ROM?
Can the B609 install B121? I mean how is the retrocompatibility working with this device/recovery?
In a update.app you got many files, boot.img, system.img but also 3rdmodem.img hifi.img modem.img...
What are those files? Why am I not allowed to flash them? Why I could start my device without flashing every files? They aren't necessary? Or they are generated by the "base rom" constitued of boot/system/cust/recovery/userdata?
Also, do I need to be rooted or something to boot on twrp? I can't boot on any other recovery except from B121, even if i extract one from update.app 609...
Thanks in advance
Is it possible to install TWRP with your device running the Nougat beta ?
The recovery is separate from the firmware. So I don't see why it wouldn't be possible. Root on the other hand I wouldn't know but I suppose the SuperSU beta zip file flashed with custom recovery would get the phone rooted.
If it was a kernel being flashed then that would matter as it affects the firmware (as it replaces the stock kernel).
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
FedoraMan said:
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
Click to expand...
Click to collapse
I tried to install the custom recovery using adb, however my phone can't be detected ?
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
FedoraMan said:
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
Click to expand...
Click to collapse
Already tried this, since installing the Nougat beta my PC only recognises my phone when in recovery mode. I installed TWRP but phone still boots into the original erecovery and not TWRP
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
FedoraMan said:
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
Click to expand...
Click to collapse
Yes installed with fastboot, I manually booted into recovery (volume up + power button) right after flashing it. I thought flashify requires root ??
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
FedoraMan said:
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
Click to expand...
Click to collapse
Yeah, I just flashed the update using the dload method. The main reason I want to install TWRP is so i can downgrade. I've tried using the dload method to downgrade however it doesn't work.
For the dload method, I think you have to flash stock recovery first
FedoraMan said:
For the dload method, I think you have to flash stock recovery first
Click to expand...
Click to collapse
I am currently using stock recovery and it still won't let me downgrade, the update reaches 51% then an error occurs. Would it be possible to flash downgrade firmware using fastboot ?
I believe you can, but you should check online to see if it is.
FedoraMan said:
I believe you can, but you should check online to see if it is.
Click to expand...
Click to collapse
I will check and try this method, I'll get back to you with the results
Ok. Good luck!
Same problem here, I installed a leaked Nougat beta for the Honor 8 via TWRP and when I tried to get back to TWRP it wouldn't let me. I've tried to flash it again via fastboot but I can't boot into it :/
I have this problem too after Flashing Nougat.
I have already flashed twrp recovery via fastboot, installation complete. But I cant boot into recovery mode.
I have never had this kind of problem before. If you tried a cold boot (Hold volume up + power), try typing "adb reboot recovery" instead (or the other way around, if you've done that)
Hello.
I came from z3.
For z3 to get in recovery with N u have to hold down vol button and insert cable. Charger or PC
Sent from my EVA-L19 using XDA-Developers mobile app
I don't know if this works, but I was looking around in HiSuite (huawei's phone thing app on pc) and saw a ROM flashing option. Try that.
I have bricked my phone after Magisk install fail.
I first unlocked bootloader succesfully
then i installed twrp succesfully
then i flashed magisk using twrp - this failed and sent device to erecovery. (which won't find package)
i used twrp to wipe data, now i was able to boot, and it installed like a fresh EMUI. However, almost all apps were broken- could not download themes/camera shut down etc.
To fix this, i wanted to restore to stock and did the following: download update package for my VTR-L09 of EMUI b175 (I was on b162 before), used Huawei Update Extractor to extract files and flashed BOOT.IMG, SYSTEM.IMG and RECOVERY.IMG. This was done without error.
Now my phone won't boot at all. I am stuck at the 'your device can't be trusted' screen. I cannot go into recovery. When I connect via USB, I hear the chime in Windows but I can't seem to connect with ADB.
What to do now?? Am I hard-bricked? I hope that anyone knows how to deal with my phone bricked like this. Please help me to solve this issue.
Best of wishes.
Edit: I am able to enter forced recovery, however updates fail at 5%.
I am also able to fastboot with USB, however I am unsure what to do next.
I unbricked my phone! Many thanks to who ah way and his solution found here: https://forum.xda-developers.com/p10/how-to/guide-unbricking-p10-using-hwota-windows-t3714416
:victory:
why are you doing it when you dont understand it?
You cannot flash part of B175 firmwar eover B162 firmware.. OMG.
use the HWOTa to go back to stock and please stop playing with the device without propper knowledge
Hi there guys. Please excuse me for posting this in the QA thread but because I am a new member it wouldn't let me post in the recovery section. I joined XDA just to get some help with my Huawei P9
So I have a Huawei P9 (EVA-L19) and I tried to load a custom rom onto my phone. I was going to load resurrection remix 6 onto my phone but did not get that far.
I got as far as flashing TWRP recovery onto my phone. Once I flashed TWRP recovery I still could not get into TWRP 3.1.1 instead I kept entering eRecovery. So I flashed Recovery2 with TWRP and now my phone is in a boot loop. If I let the phone battery drain completely I can boot the phone. But if I shut down or reboot the phone for any reason while there is power in the battery the phone gets stuck in a boot loop. My Bootloader is unlocked but I can't get the phone into fastboot mode. Even with Volume- and Power key and USB. It just goes straight to "phone can't be trusted page" and then boot loops. Is there a way to fix my phone when I let it run completely flat and then log back into EMUI? I tried factory refresh but it just got stuck on bootloop.
So to summarize.
*My phone gets stuck on a boot loop on all reboot/power on scenarios EXCEPT when starting from a completely drained battery.
*Cannot access fastboot.
*Unlocked bootloader
*Not Rooted
*Rebooting phone gets it stuck in a boot loop.
*How to fix phone either back to EMUI or RR6.0
I would wish to either just get my phone working again on EMUI as a last resort. But ultimately I would like to finish putting on RR6.0 because I was unhappy to hear P9 wouldn't get Oreo updates.
Alastair_S1D said:
Hi there guys. Please excuse me for posting this in the QA thread but because I am a new member it wouldn't let me post in the recovery section. I joined XDA just to get some help with my Huawei P9
So I have a Huawei P9 (EVA-L19) and I tried to load a custom rom onto my phone. I was going to load resurrection remix 6 onto my phone but did not get that far.
I got as far as flashing TWRP recovery onto my phone. Once I flashed TWRP recovery I still could not get into TWRP 3.1.1 instead I kept entering eRecovery. So I flashed Recovery2 with TWRP and now my phone is in a boot loop. If I let the phone battery drain completely I can boot the phone. But if I shut down or reboot the phone for any reason while there is power in the battery the phone gets stuck in a boot loop. My Bootloader is unlocked but I can't get the phone into fastboot mode. Even with Volume- and Power key and USB. It just goes straight to "phone can't be trusted page" and then boot loops. Is there a way to fix my phone when I let it run completely flat and then log back into EMUI? I tried factory refresh but it just got stuck on bootloop.
So to summarize.
*My phone gets stuck on a boot loop on all reboot/power on scenarios EXCEPT when starting from a completely drained battery.
*Cannot access fastboot.
*Unlocked bootloader
*Not Rooted
*Rebooting phone gets it stuck in a boot loop.
*How to fix phone either back to EMUI or RR6.0
I would wish to either just get my phone working again on EMUI as a last resort. But ultimately I would like to finish putting on RR6.0 because I was unhappy to hear P9 wouldn't get Oreo updates.
Click to expand...
Click to collapse
RROS 6.0 must go on Android Oreo / EMUI 8.
You first had to rebrand your phone by HWOTA7 to Chinese Oreo AL10 c00 b535 or b528.
Were you rebrabding and hence needed TWRP, or you were trying to flash RROS 6 (for Oreo) on L19 (on Nougat or even MM) together with TWRP 3.1.1 for Nougat?
Please answer precisely:
- What was the full name and number of your stock build you were starting from (like EVA-L19c432b504 or so, not just "P9 L19")
- Have you already flashed (by Fastboot) RROS 6.0 or your first step was trying to install this TWRP?
- Where did you pick up that TWRP 3.1.1.1?
If you picked directly from TWRP site then this TWRP might not work even for Nougat (EMUI 5.x)
- If you picked proper TWRP from XDA threads, then there is always an important detail described:
Immediately upon flashing TWRP, you must boot into TWRP - otherwise you loose TWRP as if it was never flashed.
You must:
- press and keep pressing Vol+
- type in: fastboot reboot, Enter
- IMMEDIATELY at the moment when phone turns off, disconnect USB
- keep pressing Vol+ until you see it boots to TWRP.
Reasons that you were not able to install TWRP might be:
- wrong TWRP
- you did not follow this 'trick'
- you were flashing proper TWRP for Nougat but your L19 was on MM (EMUI 4.x), or you were flashing it once you already rebranded to Chinese AL10 Oreo, or upon you flashed RROS 6....
There are various possibilities, please precisely describe - it's not why TWRP did not flash but why (after this possible mess) your phone does not boot and how to fix it now
zgfg said:
RROS 6.0 must go on Android Oreo / EMUI 8.
You first had to rebrand your phone by HWOTA7 to Chinese Oreo AL10 c00 b535 or b528.
Were you rebrabding and hence needed TWRP, or you were trying to flash RROS 6 (for Oreo) on L19 (on Nougat or even MM) together with TWRP 3.1.1 for Nougat?
Please answer precisely:
- What was the full name and number of your stock build you were starting from (like EVA-L19c432b504 or so, not just "P9 L19")
- Have you already flashed (by Fastboot) RROS 6.0 or your first step was trying to install this TWRP?
- Where did you pick up that TWRP 3.1.1.1?
If you picked directly from TWRP site then this TWRP might not work even for Nougat (EMUI 5.x)
- If you picked proper TWRP from XDA threads, then there is always an important detail described:
Immediately upon flashing TWRP, you must boot into TWRP - otherwise you loose TWRP as if it was never flashed.
You must:
- press and keep pressing Vol+
- type in: fastboot reboot, Enter
- IMMEDIATELY at the moment when phone turns off, disconnect USB
- keep pressing Vol+ until you see it boots to TWRP.
Reasons that you were not able to install TWRP might be:
- wrong TWRP
- you did not follow this 'trick'
- you were flashing proper TWRP for Nougat but your L19 was on MM (EMUI 4.x), or you were flashing it once you already rebranded to Chinese AL10 Oreo, or upon you flashed RROS 6....
There are various possibilities, please precisely describe - it's not why TWRP did not flash but why (after this possible mess) your phone does not boot and how to fix it now
Click to expand...
Click to collapse
No I did not get as far as flashing RR6.
I downloaded TWRP 3.1.1 openkiren for Eva from TWRP's download page.
I only got as far as attempting to flash TWRP no custom rom was flashed yet.
I could of sworn I HAD EVA-L19C185B405 when I started this process.
However I now have EVA-L19C185B403. Not sure if my phone rolled back somehow. If I try search for updates it says the phone is up to date.
My L19 is on Nougat. It's on EMUI 5.0.3 Android 7.0
I did not rename my phone with any Chinese P9 builds or any tricks like that. Didn't even know you had to do that.
My phone still works provided I don't reboot it. And if I do reboot it, it gets stuck on the bootscreen until it drains completely. Then I plug it in to power and it boots successfully again.
Alastair_S1D said:
No I did not get as far as flashing RR6.
I downloaded TWRP 3.1.1 openkiren for Eva from TWRP's download page.
I only got as far as attempting to flash TWRP no custom rom was flashed yet.
I could of sworn I HAD EVA-L19C185B405 when I started this process.
However I now have EVA-L19C185B403. Not sure if my phone rolled back somehow. If I try search for updates it says the phone is up to date.
My L19 is on Nougat. It's on EMUI 5.0.3 Android 7.0
I did not rename my phone with any Chinese P9 builds or any tricks like that. Didn't even know you had to do that.
My phone still works provided I don't reboot it. And if I do reboot it, it gets stuck on the bootscreen until it drains completely. Then I plug it in to power and it boots successfully again.
Click to expand...
Click to collapse
For EMUI 5.x you must use TWRP 3.1.1 from XDA (adapted for Huawei Nougat and its encryption), best the latest build eg from post #1
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
and you must flash it with the trick at rebooting as described in previous answer.
Your TWRP you flashed to Recovery2 (?) is likely not even good for Huawei N (but probably for MM).
You must fix your Recovery2 by flashing back the proper stock Recovery2.
You need to download update.zip corresponding to your c185 build by Firmware Finder (find XDA thread about, there is also PC version), unzip and put update.app to Huawei Update Extractor (find also XDA thread about) to extract your stock Recovery2.
Once you repair, please carefully read HWOTA7 instructions how to rebrand (and upgrade to Chinese Oreo - this is a must if you would like to play with OpenKirin Oreo ROMs, they can not be installed to L19 Nugat builds) - and this required rebranding is far more than 'renaming'
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
You must fix your Recovery2 by flashing back the proper stock Recovery2.
You need to download update.zip corresponding to your c185 build by Firmware Finder (find XDA thread about, there is also PC version), unzip and put update.app to Huawei Update Extractor (find also XDA thread about) to extract your stock Recovery2.
Click to expand...
Click to collapse
Can you guide me to these links?
Alastair_S1D said:
Can you guide me to these links?
Click to expand...
Click to collapse
Put to Google eg
XDA Firmware Finder
or
XDA Huawei Update Extractor
For the other two I gave you links.
You will really need to spend your time to read the guides
Ok how do I reflash the recovery2 if I cant get into fastboot mode on my phone. Can I do it from inside EMUI?
There are two ways to boot to Fastboot
1) Power off, connect by USB to PC, press and keep pressing Vol-, press Pow
2) From Android, enable Dev options and ADB, connect by USB and execute: adb reboot-bootloader
You cannot by either way?
For Oreo but also reported for some newest Nougat builds, eRecovery gives you an option to reinstall current firmware.
But if you cannot boot to eRecovery, because you attempted to flash TWRP over Recovery2...
Actually, try to boot to eRecovery: power off, connect by USB to charger, press and keep pressing Vol+, press Pow.
If it boots to TWRP (instead of to eRecovery) you can try:
-flash stock eRecovery to recovery2
- flash (proper, from XDA, link was above) TWRP to recovery
There are other methods: HuRUpdater, HWOTA7, HWOTA as improved variations of nonCheckRecovery, but
- first two require Fastboot to start (they will flash TWRP)
- last two require already installed TWRP
(apparently not applicable to your brick)
In HiSuite, for Oreo (maybe also Nougat, I don't know if it depends on Huawei firmware or newest HiSuite version on the PC), there is an option to upgrade/downgrade.
You can try if you could (re)install some stock firmware that way but I never played with.
For eRecovery and HiSuite (if you would be able to do) it is unclear if (re)installation of stock firmware will succeed (or even further brick your phone - don't know if anybody else had such a brick as yours and tried them).
If none as above, you may try DC Phoenix (15 Euros credit?):
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
I didn't need it but search on XDA, from time to time people report (usually in not highly exposed threads) that they were able to unbrick various Huawei phones (when no other methods worked or they were too lazy to investigate and experiment) - but their on-line instructions are not very detailed and they are not very friendly if contacted for help