Database Develop

Error mode, really hard bricked

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Help!!, frp locked bootloader locked

So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE

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

I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)

EgonsS said:
I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)

I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s​

RAR1991 said:
I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s​
Click to expand...
Click to collapse
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command

victoriordachi said:
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command
Click to expand...
Click to collapse
thanks for the interest but like always.
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.937s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.953s​

victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
FAILED (remote: partition error)

So I was digging on my phone and I was able to put it in recovery mode it shows USB logo with 5 % and adb devices command give that result
E:\>adb devices
List of devices attached
PSEDU17315000315 recovery​if anyone can get something from that

Hassan__12 said:
So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE
Click to expand...
Click to collapse
Try this:
fastboot flash recovery xxx(name of recovery).IMG.
It's the old nougat command. Might work. Depends on what partition scheme your device has. Give it a shot. Likely won't but you can try.

Got same issue yesterday. After some i got a length partition issue.
I did the full OTA from eRecovery. Now i'm on PRA-LX1 8.0.0.368 C02 (NOT C432).
I should try again (i believe my device is now totally stable - i think i flashed bad rom with HuRUpdater...) and see if i can flash a TWRP (certainly 3.2.1 Oreo) with fastboot flash recovery_ramdisk twrpfile.img
Will let you know.

hello colleagues need your help huawei PRA-LA1 on the screen only huavei write how the bootloader will unlock me

Brick my MI A2

After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?

https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188

minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)

Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.

use ./fastboot flashing unlock_critical

Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.

djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.

Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.

djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.

meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?

Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.

Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!

people try:
1- Another usb port
2- Another usb cable
3- Another PC

I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs

woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?

Bricked phone flashing twrp 3.3 on p20 pro. Don't know what to do.

Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.

androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk

zencooler said:
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for replying. I've just tried that and it says 'Your system is not supported for recovery'.

Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka

cielik said:
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....

androidyeah... said:
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
Click to expand...
Click to collapse
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:

Try to use the Flash TOOL of this post, it always works with me.
https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964

androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Try to use OTG dload method.
If you need firmware and help tell me!

I had this problem on my EML-L29, tjis helped me:
factory reset
wipe cache
fastboot erase system
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot

Yeah, similar to what I had to do. Factory reset wasn't possible for me, but flashing partitions worked.

Bricked P20 Pro
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.

Wrong section. Can this be moved please.
I thought there was a new ROM thread..

Rustyrobotguy said:
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Click to expand...
Click to collapse
You can always go into fastboot mode in emergency mode.
Just connect the phone to PC via USB cable and then press power key + Volume Down.
It will bring you into Fastboot Emergency.
Then you can play with fastboot commands.
I recommend you to extract RECOVERY_RAMDIS.img from UPDATE.APP (you can get it from update.zip file for your firmware) into a folder that keeps your fastboot exe file. Then do following command on your PC:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
It will give you stock recovery.
Then you can do command:
fastboot reboot
Immediately after this command disconnect USB cable and press Volume Up key.
On recovery you can do wiping your data partition and don't he factory reset.
If it not help and you are still on boot loop you can go again into fastboot emergency mode and do fastboot command:
fastboot -w
This will reformat your data partition and after this your phone will boot into erecovery to do factory reset again. It should help you to bring your phone into live.
Regards.
Sent from my SM-N960F via Tapatalk

androidyeah... said:
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Click to expand...
Click to collapse
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s

thoughtless22 said:
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
Click to expand...
Click to collapse
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk

zencooler said:
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?

thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Same Problem for me. cant find any way to get this to work.. my Phone is bricked 2 month now i miss it lol
does anyone have a Solution for this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Try thoes command in fastboot:
HTML:
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
fastboot oem get-build-number
if it returns something weird, then you are fvcked up.
mine messed up once, I had to get to Service Center to replace the motherboard.
Maybe, now there is some 3rd party way can save you phone, I don't know.

Huawei p9 recovery fail!

I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected. Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

khangkhong said:
I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected.
Click to expand...
Click to collapse
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?

zgfg said:
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?
Click to expand...
Click to collapse
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.

khangkhong said:
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.
Click to expand...
Click to collapse
Before relocking Bootloader you must make sure that you have stock Recovery, stock Boot/Ramdisk image (that is, must be unrooted), stock Kernel (if you experimented with custom Kernels).
Unfortunately, if you didn't have, Factory reset as part of relocking Bootloader fails and may cause brick
Don't know what is the cust for Philippines/Asia and what are its latest firmware versions, and do they allow DLOAD installations (only firmwares named as FullOTA-MFPV on Firmware Finder can be installed by DLOAD, those with MF but without PV cannot be).
Btw, what is the cust for Asia you were flashing with, EVA-L19cXXX?
If eRecovery cannot recognize the phone model, it might be due your attempts to flash various firmwares by DLOAD
Can you boot to Fastboot and connect by Fastboot from PC (probably no more since you attempted to relock Bootloader, which disabled OEM Unlock and USB debugging):
- Switch off, connect by USB to PC, press and keep pressing Vol- and press Pow button.
If you could boot to Fastboot, there are Fastboot commands to read what the phone thinks it is its latest cust and build number, that can help to unbrick.
Also, it helps to DC-Phoenix (paid tool for unbricking)
PS: Don't know why people go for relocking Bootloader. There have been so many posts here and there with users who bricked their phones when attempting to re-lock Bootloader(because they had TWRP, they did not unroot, they had custom DOMs, etc).
Besides:
- Unlocked Bootloader DOES NOT prevent/affect OTA upgrades
- relocked Bootloader is different from originally locked Bootloader and Huawei service can still recognize that Bootloader was unlocked and relocked
- Some new stock firmwares automatically lock (not relock) Bootloaders upon upgrades

I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”

khangkhong said:
I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”
Click to expand...
Click to collapse
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION

zgfg said:
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398

khangkhong said:
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398
Click to expand...
Click to collapse
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware

@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?

misagh72 said:
@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?
Click to expand...
Click to collapse
People, this has been written in many other threads and posts:
- Before doing Bootloader relock or Factory reset, you must unroot, restore stock Recovery, otherwise it bricks.
You can try to reinstall by using eRecovery.
But since you still have TWRP, read my post #8, you have link and instructions to the HWOTA method.
Of course, I have described to the other user who has L19c636, you must flash by HWOTA for your model L09/L19 and your cust cXXX - I gave instructions in the posts #4 and #6 how to boot to Fastboot and which Fastboot commands to use to obtain info for your phone

zgfg said:
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware
Click to expand...
Click to collapse
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.

khangkhong said:
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.
Click to expand...
Click to collapse
>> downloaded all files and put them into HWOTA and rebooted. Nothing happens
Nothing can happen by itself
>> . I tried Vol+, Vol-, and Power button to force to install files
This is HWOTA, not DLOAD.
It's desrcribed in the HWOTA tutorial that you must boot to TWRP, and TWRP has Install tab where you choose Storage (SD card), Zip installation, and then select the script from HWOTA folder, and then Swipe to start flashing
>> when I boot I'm always on eRecovery and cannot boot to TWRP
I wrote you in the previous post that you must first install TWRP. Your Bootloader says it is unlocked.
You must install TWRP from the thread I gave you the HWOTA link - do you know how to install TWRP from Fastboot?
Have the HWOTA folder ready on the SD card, so that when you install TWRP from Fastboot, you must immediately reboot from Fastboot directly to TWRP, then navigate in TWRP to it's Install option and proceed by HWOTA installation as described in its OP post

I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.

khangkhong said:
I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.
Click to expand...
Click to collapse
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)

zgfg said:
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)
Click to expand...
Click to collapse
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:

khangkhong said:
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:
View attachment 4755207
Click to expand...
Click to collapse
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate over the Web links, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp

zgfg said:
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate to them, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp
Click to expand...
Click to collapse
Thanks for the reply. I’ll try your suggestions.