Database Develop

P9 Bricked, Bootloader Locked. No TWRP Installed. FML (Send Help)

Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.

kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.

ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
I think there is not solution for this problem. We have to wait. (I have the same problem but in Al00 running Al19 rom)

How do you check for FRP lock on a Huawei phone just curious.

ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you

kyle_2103 said:
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you
Click to expand...
Click to collapse
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.

ChaseRxx said:
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.
Click to expand...
Click to collapse
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?

kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
I've tried some command in fastboot mode but there's always an error: Remote: command not allowed.
I can't do anything with fastboot mode

1. Try to force update with Power Button + Min Vol Button + Max Vol Button, liked you said this isn't working try to do the button combination with the phone connect it to the PC; in my case some times dload din't works after I connected the phone to the computer.
2. Other thing, something happend if you turn of the phone and leave Max Vol Button pressed, you should be entering to eRecovery.
3. Remember that sometimes enter in eRecovery mode requires to the phone be turn off otherwise you can't access to Recovery. So if this is the case follow bullet #2 and them #1.
PD: OFC I'm assuming you already have the dload folder with an compatible version of stock ROM on your SDCARD. If you don't have any version tries this one: https://forum.xda-developers.com/p9...dload-file-p9-eva-l09-b136-t3382818?nocache=1
Hope I helped you, I already bricked twice my P9 corrupting System Table Partitions.
Jeremy Molina.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
If you did the change of Unlock OEM before the bricked in an previous authorized computer you will still have rights for, otherwise new Android Security features is going to rejected the request.

Exacly

Dload/ no network
ChaseRxx said:
Exacly
Click to expand...
Click to collapse
Hi guys! Im new sorry if posted in wrong place/topic, I did dload method as here https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 to debrand my L09 Vodafone to stock software and now I end up in EVA-C900B136 and my sim card/network is not working anymmore I had download the software package is in the above post and did force flash.
Many thanks for help!!!

kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.

dondrog said:
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.
Click to expand...
Click to collapse
fastboot oem unlock (followed by bootloader code)

kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello gays i install nougat 7
install with TWRP after install my phone is no keybord no all problems and i can`t active oem waht i do all command
remote not allowed coomand and i try to install all veriosn but still problem please help me
i install
EVA-L19C432B322-update
and my phone 6369C-EVA L19
my mistake please help me
i try to swoftware sim but swoftware failed
--
incompatibility with current version please download the correct update package
i upload vedio on youtube see please https://www.youtube.com/watch?v=V2yH...ature=youtu.be
sry for my bad engilsh

Any help would be greatly appreciated
I have a P9 L09, i have unlocked the bootloader, flashed TWRP recovery, and started flashing some roms. I have succesfully flashed a cyanogenmod, and it booted properly, but when it started it asked me for a password which i did not know, so i google searched and found out that it is a common issue and i need to wipe data from recovery. I tryed that but it did not work it says failed, and nothing works in the wipe advanced section, beside system. And also in the custom recovery it says that the internal storage has 0MB ! I was able to put other custom roms on the SDcard and flash them, they booted but every single one asks for the password.. I then tryed to install stock rom with the dload method, but it crashes and 40% , and i tryied the System Recovery option in HiSuite and it says it is not compatible with my device. Any help would be greatly appreciated! Thank you!

kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello. I have the same problem. I have my unlock code but in fastboot, adb command says it failed. Sorry for bad english. What can i do?
FAILED: REMOTE COMMAND NOT ALLOWED FINISHED.

Same problem on my honor &x locked bootloader and bricked. unlocking the oem like you said above does not work

Honor 4x factory reset and recovery menu not work

Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.

If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).

oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....

Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.

oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX

Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked

thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down

shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.

zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!

I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.

Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.

Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...

Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.

P9 rescue - only fastboot (Help please)

Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers

I've gone through that before, but ended up using DC-Phoenix to unbrick it when it's FRP and bootloader locked. Cost me about $15. There is a post on how to do this but I'll have to search for it again.
Here is the post I used:
https://forum.xda-developers.com/showpost.php?p=71767614&postcount=7

I guess you enter fastboot by Vol- and Power?
Not sure if the following method could help you with, but you can analyze before you go for dc-phoenix:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7

scammander said:
Hi,
I have a P9 here I'm was asked to repair. I think it is kind of bricked and I hope some one can help me to unbrick it.
According to the auto dc-unlocker identification:
Found Phone : EVA-L09
Firmware : EVA-L09C432B386
FB LockState: LOCKED
USER LockState: LOCKED
So, bootloader locked and FRP locked. I don't know if the Firmware version above is right. All I know is that some Update.app files were flashed to the state of the phone now and before there where bootloops while the start animation and stuck boot with black screen.
At the moment I can do:
- turn on to see only the first huawei log with "powered by android", then nothing happens
- I can not enter eRecovery or update for Update.app
- I can only enter fastboot
I have the unlock code for the bootloader. I can not commit any fastboot commands (oem unlock, flash, etc) all is blocked with:
FAILED (remote: Command not allowed)
The locked FRP should be the reason for this.
I think OEM-unlock and usb debug from developer section was not enabled as the phone was usable. adb commands like "adb reboot bootloader" fail with
error: device '(null)' not found
fastboot devices shows the device
I have tried to uncharge the battery and then try to enter other modes than fastboot. No luck with that.
Do I have any chance to unbrick it without paying for the dc-unlocker/phoenix?
Can I do something with SRKTool?
If I have to use unlocker,
- do I have to unlock the bootloader?
- should I flash the same firmware that is now on the phone (B386) and where can I find it? (found only 1000 other versions until now)
Hope for answers
Click to expand...
Click to collapse
So you can not update via dload method? Did you try booting into recovery (not Recovery)? And you can't update with Update.app, you need to flash update.zip and full_update.zip via TWRP or Recovery. What wanted the owner of this phone to do, that he bricked it ?

Thank you all for your answers. Like I tried to describe: I was not able to access any other mode than fastboot.
"was able": I used DC-Phoenix now and it worked just fine.
Little confusing is that in all tutorials, even the on on the DC site, the UI of the tool is different.
But that's now Problem. The current Version is lot easier. Just "Standard Mode", select Update.app (full), Click Update.
The Phone gets flashed with fastboot, DC will restart it to update mode and will flash again. All automatic.
Really easy.

so you paid 15 USD ?

DallasCZ said:
so you paid 15 USD ?
Click to expand...
Click to collapse
Yes I did, and it worked.

Huawei P9 stuck In bootloop

what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.

lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock

lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s

lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's

lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off

zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?

So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.

ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS

Huawei Wtf!

My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !

So he needs his phone, I take phone but does not can't do anything like open bootloader or any thing with ADB or format and His system was returned to Android 6 !

albelushi7 said:
My friend have Problem his device after trying to install custom ROM just a reboot but not go into system so he go to Huawei shop and I wait 3 days after that told him should go to another shop We can't fix it!, but before that his phone his phone open bootloader and can use ADB ،When the device is returned from him it's locked and can't open bootloader or do anything ،They told him not responsible for this and can't the installation the system in his device wtf Huawei Oh really !
Click to expand...
Click to collapse
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)

zgfg said:
If your friend was able to flash custom ROM, he had to have Bootloader unlocked.
It means that he did have Bootloader code - he had to keep it because same Bootloader code is good for the same phone for the whole life. Unfortunately, people didn't dare to care about that, similarly like not caring to learn first (before they bricked the phones) about what and how to flash - this is unfortunately one of the reasons (bad posts on Internet) that Huawei changed the policy about BL codes (and now everyone, also those who do care what and how) suffer.
Anyway, for P9 you can still buy the BL code for 4-5 USD.
Also, if they returned the phone unbricked, with MM, you should be able to upgrade to Nougat by DLOAD, not needing to unlock BL (ir they didn't put c300 MM)
Click to expand...
Click to collapse
Thanks for your reply, now cant flash anything < . I try to fix what can be fixed, he has the code but now when doesn't work or something is wrong, when try with ADB to unlock bootloader (.. "FAILED > emote: Command not allowed) also FRP LOCK .
i try many version with DLOAD but does not work! < Maybe can give me to try it ! another thing when try to format It seems not working only 2 % .fact now I do not know what to do with his phone but I will try!

To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION

zgfg said:
To unlock FRP, you must unlock OEM from Settings, Development menu.
As you described, phone was bootable (to MM) when returned from service - but now, after the failed DLOADing, etc, is it bootable any more
You cannot DLOAD any P9 firmware to any P9 phone. Firmware must be:
- of the same model and cust (otherwise you first needed to rebrand)
- it must be shown eg in FirmwareFinder as FullOTA-MF-PV (not just FullOTA-MF)
If not cared about (specially about model and cust) - no wonder if it bricked the phone
If you cannot boot anymore to read full model, cust and build number from Settings, About, you can read from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow). You will need ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install.
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)

albelushi7 said:
fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.013s]
finished. total time: 0.014s
-----
fastboot oem get-product-model
...
(bootloader) EVA-L19
OKAY [ 0.011s]
finished. total time: 0.012s
----
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.010s
------
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0OHZ)
OKAY [ 0.011s]
finished. total time: 0.012s
-----
fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!

zgfg said:
According to:
Code:
(bootloader) locked
your Bootloader is locked.
Does the Fastboot show also FRP locked?
And you cannot login to Android (to unlock OEM=FRP)?
According to:
Code:
(bootloader) EVA-L19
vendorcountry: hw/meafnaf
Your P9 should be L19 (dual SIM), and you had c185 Middle East cust.
From your previous posts, phone was on MM (EMUI 4), maybe you successfully upgraded to Nougat (EMUI 5)
But according to:
Code:
(bootloader) :System 8.0.0.046(0OHZ)
you attempted to flash some Oreo (EMUI 8) - and that bricked the phone?!
Click to expand...
Click to collapse
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo

albelushi7 said:
the FPR loked its showed in fastboot and the system not boot anymore
actually its 8 oreo When I checked it through adb , but i said m.m Because recovery and erecovery like on emui4 !
also when i try use Erecovery Touch Not working to Connect to Wi-Fi !
Yes is P9 L19 c185 and when try use DLOAD FullOTA-MF-PV in stuck huawei logo
Click to expand...
Click to collapse
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849

zgfg said:
It's bricked since you flashed Oreo Bootloader over the MM or N firmware, and hence it also does not accept DLOAD
To fix, you would need to flash by Fastboot, but Bootloader is locked and you are not allowed to.
To unlock BL you would need to unlock FRP, but due to the brick you cannot enter to System to unlock OEM/FRP
Hence you are stuck…
-You can try one more DLOAD by downloading this package:
https://androidhost.ru/bN4
You will have to unzip/untar (whatever applies), you should find a folder Docs inside with the Installation guide.
This is official package for DLOAD repair (P9 L19 c185 b403) for Huawei service shops, but I'm not sure would it work over your bricked Bootlloader from Oreo
-Certainly you could recover by TestPoints (but you can also definitely brick the phone by one wrong move there),
but it requires openening back-cover, short-connecting two pins and flashing the appropriate bord firmware (you would also need TestPoints drivers).
It's risky, TG I never need it, if you want to learn about you will need to search on the Net and XDA
-Otherwise, due to the facts as above, I can only recommend you to seek for the paid help from DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Ask them in advance, it might cost you cca 20 EU credits (tools and instructions for unlocking FRP and Bootloader, unbricking and flashing official Nouga firmware).
You can probably arrange also for debranding to L19 c432 Nougat if you wish
If you would then want to rebrand and upgrade to AL10 c00 b540 Oreo, you will have to start with:
- unbricked phone with latest Nougat firmware
- having Bootloader code ready
and to carefully follow OP instructions from this thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
I can't believe the phone back to work again!

How to bring the phone back to life and to work? The phone was restarting at the Huawei logo, adb not working and I have bootloader code but not working FPR looked and bootloader looked
Dload not working , so what I do , try use DC phoneix and go forward the bootloader unlocked and FPR but unfortunately must phone go to update mode but unfortunately now stuck again with no fastboot and no recovery !
finally I try with testpoint with IDM and Huawei bored and working!
and upgrade or install system with dload
After that install Android 7 and update to Oreo 8 with TWRP ?.