Database Info

Softbricked X2

Hello!!
As the title says, my X2 became softbricked and I believe it is all due to the incorrect or incompatible TWRP manager installation from the Google Play Store. My X2 keeps on rebooting. I have tried to go to recovery and wipe the data and cache. I've also attempted to reinstall or downgrade to B106 from B106sp01 but it keeps on saying that it is incompatible. I've searched and read lot of posts on the forum and it brought me to fastboot TWRP recovery which is compatible to the X2. I've worked my way around the TWRP recovery despite the Chinese language and also flashed the B106 system, boot, cust, userdata, etc images through fastboot but I have no luck.
Has anyone been in this kind of problem with their Mediapad X2? please help :crying::crying::crying::crying:

Try to Format your Sdcard with your Pc,and reflash the Stock ROM again.

hagba said:
Try to Format your Sdcard with your Pc,and reflash the Stock ROM again.
Click to expand...
Click to collapse
I've tried to do what you said but it's still on bootloop

mcdhol_24 said:
I've tried to do what you said but it's still on bootloop
Click to expand...
Click to collapse
You need to Fastboot flash the stock ROM, then wipe. That will fix your problem.

sadly the stock firmware of huawei is always in .APP format it has to be a .zip i tried to extract the system image and recovery image from stock and flashed it through fastboot but still no luck

mcdhol_24 said:
sadly the stock firmware of huawei is always in .APP format it has to be a .zip i tried to extract the system image and recovery image from stock and flashed it through fastboot but still no luck
Click to expand...
Click to collapse
Download Huawei Update Extractor to extract the .APP file to a folder than you can use Fastboot to flash the boot.img cust.img, userdata.img, system.img, recovery.img which will bring you back to stock B106. This is how you recover from a soft brick.

ajsmsg78 said:
Download Huawei Update Extractor to extract the .APP file to a folder than you can use Fastboot to flash the boot.img cust.img, userdata.img, system.img, recovery.img which will bring you back to stock B106. This is how you recover from a soft brick.
Click to expand...
Click to collapse
Ok i am trying to flash the 5 files you said. fingers crossed. Thanks

mcdhol_24 said:
Ok i am trying to flash the 4 files you said. fingers crossed. Thanks
Click to expand...
Click to collapse
Flash the boot, cust, cache, recovery, system, and userdata img files....it will work, no worries.

ajsmsg78 said:
Flash the boot, cust, cache, recovery, system, and userdata img files....it will work, no worries.
Click to expand...
Click to collapse
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.

mcdhol_24 said:
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.
Click to expand...
Click to collapse
Maybe there is something you didn't flash.

ajsmsg78 said:
Maybe there is something you didn't flash.
Click to expand...
Click to collapse
I have no luck now... I think my only hope is to wait for a new firmware by Huawei which will be compatible to B106sp01. I've fully wiped the data and cache then flashed the boot, cache, cust, recovery, userdata, system images and I ended up in bootloop still. I think it's because fully wiping the phone does erase everything and flashing those 6 images was not enough or incomplete files sort of... :crying: :crying:
Thanks for your help though but I hope I find another way to fix it

mcdhol_24 said:
I have no luck now... I think my only hope is to wait for a new firmware by Huawei which will be compatible to B106sp01. I've fully wiped the data and cache then flashed the boot, cache, cust, recovery, userdata, system images and I ended up in bootloop still. I think it's because fully wiping the phone does erase everything and flashing those 6 images was not enough or incomplete files sort of... :crying: :crying:
Thanks for your help though but I hope I find another way to fix it
Click to expand...
Click to collapse
Which stock rom did you Fastboot flash, B106 or SP01? Any time I've bootlooped (for example when I tried flashing xposed) I just fastboot flashed stock B106 and it boots right up. That's weird. Try booting into stock recovery (volume up and power) with the USB cable still in the computer and try it without being in it. Also try fastboot flashing the stock boot.img again (fastboot flash boot boot.img) it has to be something with the boot. You can also try fastboot flashing the super_bootb106 img file and see if it boots then. Or try flashing just the boot.img from the B106SP01 rom (extract the boot.img with Huawei Update Extractor)

ajsmsg78 said:
Which stock rom did you Fastboot flash, B106 or SP01? Any time I've bootlooped (for example when I tried flashing xposed) I just fastboot flashed stock B106 and it boots right up. That's weird. Try booting into stock recovery (volume up and power) with the USB cable still in the computer and try it without being in it. Also try fastboot flashing the stock boot.img again (fastboot flash boot boot.img) it has to be something with the boot. You can also try fastboot flashing the super_bootb106 img file and see if it boots then. Or try flashing just the boot.img from the B106SP01 rom (extract the boot.img with Huawei Update Extractor)
Click to expand...
Click to collapse
THANK YOU FOR YOUR HELP SIR!!!! Ive tried to flash the SUPER boot image from the TWRP installer. IT IS NOW WORKING THANK YOU THANK YOU!!!!!!:laugh::laugh::laugh::laugh::laugh::laugh:

mcdhol_24 said:
THANK YOU FOR YOUR HELP SIR!!!! Ive tried to flash the SUPER boot image from the TWRP installer. IT IS NOW WORKING THANK YOU THANK YOU!!!!!!:laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Awesome news!

mcdhol_24 said:
It still is bootlooping. I tried to press the volume up and power button to reach the stock recovery mode and right now it is displaying a USB plug in a progress circle % and chinese characters that I do not understand.
Click to expand...
Click to collapse
When doing it make sure that the phone is not hooked to the computer or it will try to do a USB update which I know nothing about.

Hello, could someone help me?
I installed TWRP and accidentally pressed one of the buttons on the recovery, and the phone now does not leave the fastboot screen (rescue mode), and below the android figure appears:
Error!
Func NO: 10 (boot image)
Func NO: 2 (load failed)
Is it possible to resurrect the phone? If so, can anyone help me fix?
Sorry for the bad english.
Thank you.

Germano1980 said:
Hello, could someone help me?
I installed TWRP and accidentally pressed one of the buttons on the recovery, and the phone now does not leave the fastboot screen (rescue mode), and below the android figure appears:
Error!
Func NO: 10 (boot image)
Func NO: 2 (load failed)
Is it possible to resurrect the phone? If so, can anyone help me fix?
Sorry for the bad english.
Thank you.
Click to expand...
Click to collapse
You have to fastboot the factory boot.img or super.img with every one you were using
fastboot the recovery twrp recovery.img
fastboot the boot.img
search the forum for the extract tool and get the img files from the rom file that you were using.
PM me if you need help with fastboot commands.

mtyler7807 said:
You have to fastboot the factory boot.img or super.img with every one you were using
fastboot the recovery twrp recovery.img
fastboot the boot.img
search the forum for the extract tool and get the img files from the rom file that you were using.
PM me if you need help with fastboot commands.
Click to expand...
Click to collapse
Thanks for answering. I am newbie in these matters. If you can guide me with these fastboot commands, I am very grateful. I have the extractor update and have the extracted files (in this case, for V100R001C233B106 ROM), but the phone goes no longer in TWRP. Still, no way to fix this?
Thank you.

Germano1980 said:
Thanks for answering. I am newbie in these matters. If you can guide me with these fastboot commands, I am very grateful. I have the extractor update and have the extracted files (in this case, for V100R001C233B106 ROM), but the phone goes no longer in TWRP. Still, no way to fix this?
Thank you.
Click to expand...
Click to collapse
1. plug the phone up the computer and hold the volume down button down on the phone to get into fastboot mode.
2. Download https://drive.google.com/file/d/0ByTxb-IFfEL-REcweFFWdlE4Nnc/editand put all those files into a folder on your computer.
3. Copy the extracted img files to the same folder that you got from your huawei firmware, "recovery.img, boot.img, cust.img, cache.img"
4. In the folder where you copied all that stuff - Hold down the shift key and write click in the white and Click on "Open command window Here".
A command prompt will appear.
Now it is time to work.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
5. remove your memory card from your phone and use a card reader and hook it to your computer and and copy the dload folder to the base of the memory card drive with the update.app file in it.
stick it back in your phone with the usb cable not connected. It should automatically start to install, but if not then hold all three buttons down until it does.
finished.

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

The stock recovery comes up instead of flashed twrp

Hello,
When I try to reboot to recovery the stock recovery comes up instead of twrp.
I have flashed multiple versions (through adb) of compatible twrp recoveries, but the issue was the same with all of them.
I am on android oreo with the latest update.
I just want to access twrp.
Did anyone experienced the same, or does anyone know hot solve this problem?

How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'

ante0 said:
How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'
Click to expand...
Click to collapse
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up

MLGarlic said:
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up
Click to expand...
Click to collapse
Post output from command prompt when flashing.

ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
I cannot access it but as i remember its output was successful. Nothing failed.
But somewhere it wrote that 31 version doesnt match 39 killing. But i could still flash the recovery afterwards successfully

ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?

i am using this recovery for my Mate 9 (L29) at https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993. Works fine. I suggest when you flash it via fastboot, please don't use command to reboot phone. Instead, just unplug phone and manually shut it off. Then, hold vol up + power buttons, it should load TWRP. I experienced that the reboot command loads eRecovery than TWRP.

martinhinge said:
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?
Click to expand...
Click to collapse
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353

ante0 said:
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
Click to expand...
Click to collapse
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help

martinhinge said:
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help
Click to expand...
Click to collapse
What?
The thread I linked is for Mate 9, only one download link is in there.
Direct link: https://mega.nz/#!tgd2BIRS!NOk3XkSaBX8PC5xjyrZNyIIz52aSoPZFphQNauhTKGQ

[SOLVED] bricked, ERROR MODE NO11, NO2

[solved]
so I have rebranded from l09 to DL00 to take the opreo update with succsess
-flashed RR Os form openkirin
-instaled magisk and rebooted
now im stuck at error mode:
Attention!
please update system again
android logo
error!
Func NO:11 (erecovery image)
Error NO :2 (load failed)
I can boot to fastboot and boot to erecovery but can't factory reset from erecovery (gets me back at error mode)
cant boot to twrp
I've tried to flash 320twrp but nothing chenged
tried to flash rom again but bithing changed
please help!
SOLVED using fastboot: flashing from the same firmware that you bricked - kernel, system, cust, recovery_ramdis

The problem is magisk, uninstall it

Elkkooz said:
The problem is magisk, uninstall it
Click to expand...
Click to collapse
how to install it when i can't boot to OS
?

Jelke997 said:
so I have rebranded from l09 to DL00 to take the opreo update with succsess
-flashed RR Os form openkirin
-instaled magisk and rebooted
now im stuck at error mode:
Attention!
please update system again
android logo
error!
Func NO:11 (erecovery image)
Error NO :2 (load failed)
I can boot to fastboot and boot to erecovery but can't factory reset from erecovery (gets me back at error mode)
cant boot to twrp
I've tried to flash 320twrp but nothing chenged
tried to flash rom again but bithing changed
please help!
Click to expand...
Click to collapse
Flash twrp by the following command,
fastboot flash recovery_ramdisk <your file as usual>

boris dmello said:
Flash twrp by the following command,
fastboot flash recovery_ramdisk <your file as usual>
Click to expand...
Click to collapse
nope, tried that.. it just gets me back into same error mode

HI,
Could you please share the fastboot commands to flash kernel, system, cust? Thanks.

[email protected] said:
HI,
Could you please share the fastboot commands to flash kernel, system, cust? Thanks.
Click to expand...
Click to collapse
fastboot flash krenel KERNEL.img
fastboot flash cust CUST.img
fastboot flash system SYSTEM.img

Jelke997 said:
fastboot flash krenel KERNEL.img
fastboot flash cust CUST.img
fastboot flash system SYSTEM.img
Click to expand...
Click to collapse
Hi,
Is it same for Oreo?

Solved How?

boris dmello said:
Solved How?
Click to expand...
Click to collapse
Bottom of OP message:
"SOLVED using fastboot: flashing from the same firmware that you bricked - kernel, system, cust, recovery_ramdis"

Help Mate 9 MHA-L09C432B368 Stuck in Error mode 11 recovery image 2 image failed

I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.

Help
Hello how are you. I had the same problem, I could not access to erecovery or recovery and worse to the system. only ERROR MODE appeared on the screen, Func NO: 11 (recovery image) Error NO: (image Failed!) .. could enter fastboot mode. with PHONE Unlocked and FRP Unlock but I took it to the official technical service of my country and they told me that it had no solution. at the time of testing on my computer I was left with PHONE Relocked and FRP lock in the fastboot. I have the code of my Bootloader and the FRP even though I can not unlock it to install files to my phone. help

hybrid09 said:
I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Click to expand...
Click to collapse
I think I can help the same happened to me. Is FRP still unlocked?

Re: I stuck with my Mate 9 Error mode numbers 11 and 2
Newrooter22 said:
I think I can help the same happened to me. Is FRP still unlocked?
Click to expand...
Click to collapse
Hi my phone have bootloader and FRP unlocked you can fix your phone for this error mode 11 and 2 ?

I wanted to ask please if this Thread can be closed since I could solve the problem, I share the solution which I obtained through a partner of the website HTC Mania @rodrigocarlosqm to which I am immensely grateful. Thanks to your generosity I was able to recover my phone and I do not want as a paperweight, the arrangement was simple buy credits in dc phoenix, in my case download the official version oreo 368, extract the update.app file and place it in the flashing program, restart the cell phone, in case it does not do so automatic do not panic turn it off and let it turn on normally, enter the recovery stock, make a wipe, then restart and return to the recovery in this case make a wipe hard reset, restart and terminate once that happens the phone it will restart again and once this is done, the operating system will start without any inconvenience. Thank you very much to everyone who helped with the help and ideas. I could find the result and I would like to thank @rodrigocarlosqm again, he was the one who helped me recover the brick he had. For all those who are in the same situation please I hope you can solve it before any query is at your disposal. Thank you all.