V10

[jfberne]

I have Honor V10 build: build: BKL-L09 9.1.0.362(C636E3R1P12)
vendor/region: hw/spcseas

According to https://www.dc-unlocker.com/DC-Phoen...epair-tutorial

1) I tried method 1 : rescue recovery
bypass version check
It fails at :
Error downloading file Berkeley-L09_8.0.0.131(C636)_Firmware_Malaysia_Australia_No nspecific_Android8.0.0_EMUI8.0.0_05014WKY_6.dtwork , partition: XLOADER

Now the screen is black. So I turned to:

2) method 2:
When testpoint shorted, I cannot get into fastboot mode. Obvously rewrite OEMINFO with BKL-L09 fails at:
Waiting for fastboot device...
Looking for a device in fastboot mode
No devices detected in fastboot mode
Software written
When testpoint not shorted, rewrite OEMINFO fails at
Writing OEMINFO partition
OEMINFO partition update :FAIL Command not allowed

When testpoint shorted, writing Berkeley-BD_1.0.0.19_Board_Software_China_Nonspecific_Andro id_8.0_EMUI8.0_05022HCX.dgtks
fails at
Error writing Bootloader

Instructions would be appreciated by the clients.

[Valdemaras]

Looking for a device in fastboot mode
No devices detected in fastboot mode
have you checked if this isn't driver problem in device manager on pc? Oeminfo can only be flashed after you connect via testpoint and select bootloader file which will unlock permissions otherwise you will get command not allowed if device is locked.

[jfberne]

I chose another bootloader file Kirin970_t1_A8.1_V6 instead of Kirin970_t1_A8.0_V1, then I could write the bootloader, then rewrite OEMINFO via testpoint.
Thanks for the hint, I made progress.
My goal is to downgrade to EMUI 8, I am still working on that: should I update with
Berkeley-BD_1.0.0.19_Board_Software_China_Nonspecific_Andro id_8.0_EMUI8.0_05022HCX.dgtks
or
Berkeley-L09_8.0.0.131(C636)_Firmware_Malaysia_Australia_No nspecific_Android8.0.0_EMUI8.0.0_05014WKY.APP
?

[Valdemaras]

It really depends in what state is mobile. It is safer to flash with stock rom instead of board software.