Database Develop

Unbrick

Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks

frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry

danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>

frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/

danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:

not possible to flash firmware in downloade mode?

mrt box

elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..

Dude, I have the same problem with a P20 Pro since january!

Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.

deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?

fastboot and rescue mode

pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work

babyshark1983 said:
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
Click to expand...
Click to collapse
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?

zgfg said:
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
Click to expand...
Click to collapse
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)

babyshark1983 said:
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
Click to expand...
Click to collapse
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

zgfg said:
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official

babyshark1983 said:
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
Click to expand...
Click to collapse
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything

zgfg said:
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
Click to expand...
Click to collapse
hi just bootloader unlock
frp locked
thx

babyshark1983 said:
hi just bootloader unlock
frp locked
thx
Click to expand...
Click to collapse
That is the problem - to flash you need both Bootloader and FRP unlocked but with wrong TWRP or so, you locked FRP
To unlock FRP you would need to boot to System and check OEM Unlock under Developer Options - but if you ccannot boot to System, it is bricked
IMO, no other way now but to buy 15 EUR credit for DC Phoenix, they can unlock (TG, I didn't need to use DC Phoenix , hence cannot help about, you can ask them over their page)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
You can also search here on XDA, there were other users who un-bricked by their tool, if I recall there was also somebody with a similar brick: FRP locked but cannot boot to System

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.

flashing twrp - Command not allowed - please help - thank you!!!

Hello, I am stuck on flashing twrp and really appreciate any help.
That’s the procedure I followed so far:
have P8 lite 2017 PRA-LX1 EMUI 8.0.0
downgraded to EMUI 5.0.2
got OEM code thru DC-unlocker
unlocked bootloader thru ADB (file "platform-tools_r31.0.3-windows" from SDK Platform Tools release notes | Android Developers)
Fastboot&Rescue mode screen shows: Phone unlocked , FRP locked
downloaded twrp-3.5.2_9-0-prague and renamed in twrp (file "twrp-3.5.2_9-0-prague" from https://twrp.me/huawei/huaweip8lite2017.html)
C:\adb>adb devices
List of devices attached
57U7N1########## device
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (14894 KB) OKAY [ 0.640s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
What I am doing wrong? Does FRP needs to be unlocked as well?

capawuasta said:
Hello, I am stuck on flashing twrp and really appreciate any help.
That’s the procedure I followed so far:
have P8 lite 2017 PRA-LX1 EMUI 8.0.0
downgraded to EMUI 5.0.2
got OEM code thru DC-unlocker
unlocked bootloader thru ADB (file "platform-tools_r31.0.3-windows" from SDK Platform Tools release notes | Android Developers)
Fastboot&Rescue mode screen shows: Phone unlocked , FRP locked
downloaded twrp-3.5.2_9-0-prague and renamed in twrp (file "twrp-3.5.2_9-0-prague" from https://twrp.me/huawei/huaweip8lite2017.html)
C:\adb>adb devices
List of devices attached
57U7N1########## device
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (14894 KB) OKAY [ 0.640s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
What I am doing wrong? Does FRP needs to be unlocked as well?
Click to expand...
Click to collapse
FRP needs to be unlocked.
TWRP is for EMUI 8.
As far as I understand, you haven't updated Mobile to Android 8( EMUI 8),I want to Ask why didn't you?
If you android 11,then you need TWRP A11 unofficial. Search in threads of p8 2017.

Momin8454 said:
FRP needs to be unlocked.
TWRP is for EMUI 8.
As far as I understand, you haven't updated Mobile to Android 8( EMUI 8),I want to Ask why didn't you?
If you android 11,then you need TWRP A11 unofficial. Search in threads of p8 2017.
Click to expand...
Click to collapse
Hi Momin, thanks for the answer.
My mobile was on EMUI 8, but I downgraded to EMUI 5 following advice from DC-unlocker tech support team: it is easier to read OEM code on EMUI 5 than on EMUI 8.
Is there a TWRP for EMUI 5?
And how to unlock FRP? Since I unlocked the bootloader, the option “Enable OEM unlock” in developer menu cannot be enabled…

capawuasta said:
Hi Momin, thanks for the answer.
My mobile was on EMUI 8, but I downgraded to EMUI 5 following advice from DC-unlocker tech support team: it is easier to read OEM code on EMUI 5 than on EMUI 8.
Is there a TWRP for EMUI 5?
And how to unlock FRP? Since I unlocked the bootloader, the option “Enable OEM unlock” in developer menu cannot be enabled…
Click to expand...
Click to collapse
Please join this group, there are devs and others users in this group, they may guide you. https://t.me/hi6250group

I had this issue so I'll try to give some info and I hope it will help you or anyone else
my P8 Lite 2017 always goes to erecovery rather than twrp recovery
first you need to :
fastboot flash recovery_ramdisk twrp.img
then you need to boot the phone in android and with adb mode you need to :
adb.exe reboot recovery
for some reason, that's the only way for me to get to the TWRP Recovery
it's, weird, I don't get it either, I don't care, it works for me xD

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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