P10 Plus Bricked | Need Help with Testpoint

[Disillusioned]

Hello All,

I've a hard bricked P10 Plus. Fastboot gives error in writing lots of commands and Method 1 / 2 for DC Phoenix has also not worked.
The phone probably had November 2018 security patch which I'm sure has caused Method 1 and 2 to fail.

The last resort I've is to try testpoint method. But this phone's testpoint is way tricky than I thought. The pin is right below the connector where USB flex gets connected. So I'm unable to use a tweezer and short the testpoint with ground. Further, in my attempts to flip the board over batter, have only USB flex connected (no battery etc) I was unable to make the testpoint work.

I would appreciate if someone can help answer below:
1. Would testpoint work after November 2018 patch or I would get similar errors as in Method 1 and 2?
2. Does testpoint need battery flex connected?
3. For P10 Plus shall I use a wire to connect testpoint with ground?

[Disillusioned]

Update
Made the testpoint and the phone was detected under Huawei USB COM 1.0 mode.

Flashing board software failed, most probably because the phone was on Android 8.0 and board software is for 7.0 and what DC Phoenix supports.

Quite unfortunate but seems like there is no way to fix this phone for now, unless folks at DC Unlocker come out with a solution.

[Valdemaras]

May only attempt loader + oeminfo then full stock rom matching your device version.

[Disillusioned]

Thanks for the suggestion.

I tried all the bootloader files and Kirin960_T2_A7.0_V3 and Kirin960_T2_A7.0_V4 seem to be working. (Log from V3 is in screenshot)

Here's the log from writing bootloader (V4) and oeminfo (VKY L09) :

Device detected:
COM25: HUAWEI USB COM 1.0 (COM25)
BOOTLOADER File to update: Kirin960_T2_A7.0_V4
OEM File to update: VKY-L09
4/8/2019 8:29:19 AM Starting to write device...

Writing bootloader...
Writing Kirin960_T2_A7.0_V4_3.dtwork...
Writing Kirin960_T2_A7.0_V4_4.dtwork...
Writing Kirin960_T2_A7.0_V4_5.dtwork...

Waiting for fastboot device...
Device found: NUPKK17517600027


Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xxx

IMEI1:xxx

MEID:xxx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 1043mv

Writing OEMINFO partition
OEMINFO partition UPDATE ...OK
Software written
4/8/2019 8:29:52 AM Writing device finished OK




However, while writing stock ROM, I'm getting below log (ROM: Vicky-L09A_C654B198_Firmware_Canada_Rogers_Communication s_Android_7.0_EMUI_5.1.APP):

Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: NUPKK17517600027


4/8/2019 8:56:38 AM Starting to write device in FASTBOOT mode...

Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xxx

IMEI1:xxx

MEID:xxx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 3148mv


Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error
Cannot get FBlock info from device
Trying to unlock device...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error

Extracting partition FW_LPM3...
Writing FW_LPM3 partition
FW_LPM3 partition UPDATE :FAIL image verification error

Extracting partition FASTBOOT...
Writing FASTBOOT partition
FASTBOOT partition UPDATE :FAIL image verification error

Extracting partition VECTOR...
Writing VECTOR partition
VECTOR partition UPDATE :FAIL image verification error

Extracting partition MODEMNVM_UPDATE...
Writing MODEMNVM_UPDATE partition
MODEMNVM_UPDATE partition UPDATE ...OK

Extracting partition TEEOS...
Writing TEEOS partition
TEEOS partition UPDATE :FAIL image verification error

Extracting partition TRUSTFIRMWARE...
Writing TRUSTFIRMWARE partition
TRUSTFIRMWARE partition UPDATE :FAIL image verification error

Extracting partition SENSORHUB...
Writing SENSORHUB partition
SENSORHUB partition UPDATE :FAIL image verification error

Extracting partition FW_HIFI...
Writing FW_HIFI partition
FW_HIFI partition UPDATE :FAIL image verification error

Extracting partition BOOT...
Writing BOOT partition
BOOT partition UPDATE ...OK

Extracting partition RECOVERY...
Writing RECOVERY partition
RECOVERY partition UPDATE ...OK

Extracting partition RECOVERY2...
Writing RECOVERY2 partition
RECOVERY2 partition UPDATE ...OK

Extracting partition DTS...
Writing DTS partition
DTS partition UPDATE ...OK

Extracting partition CACHE...
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition
CACHE partition UPDATE ...OK

Extracting partition SYSTEM...
Writing SYSTEM partition
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 429216908 bytes
send sparse file OK
SYSTEM partition UPDATE ...OK

Extracting partition ISP_FIRMWARE...
Writing ISP_FIRMWARE partition
ISP_FIRMWARE partition UPDATE :FAIL image verification error

Extracting partition MODEM_FW...
Writing MODEM_FW partition
MODEM_FW partition UPDATE :FAIL image verification error

Extracting partition HISEE_IMG...
Writing HISEE_IMG partition
HISEE_IMG partition UPDATE ...OK

Extracting partition HISEE_FS...
Writing HISEE_FS partition
HISEE_FS partition UPDATE ...OK

Extracting partition USERDATA...
Erasing USERDATA partition
Partition USERDATA erased
Writing USERDATA partition
USERDATA partition UPDATE ...OK


Software written
4/8/2019 9:04:04 AM Writing device finished - INCOMPLETE

Waiting for fastboot device...
No devices detected in fastboot mode

Cannot update device in upgrade mode

[Disillusioned]

So I tried some other combinations

After writing loader + oeminfo, I tried board softwrae in USB 1.0 mode.



4/8/2019 9:17:35 AM Starting to write device in FASTBOOT mode...
File to update: VKY-AL00_M00A066_Board_Software_general_7.0.0_r1_EMUI5 .1_05022AWK_testpoint.dgtks
Device detected:
COM25: HUAWEI USB COM 1.0 (COM25)

Writing bootloader...
Writing VKY-AL00_M00A066_Board_Software_general_7.0.0_r1_EMUI5 .1_05022AWK_testpoint_4.dtwork...

Error writing Bootloader
4/8/2019 9:17:57 AM Writing device finished - INCOMPLETE




However, board software followed by stock rom would proceed to flash with error in fastboot:
Looking for a device in force upgrade mode
No devices detected in force upgrade mode
Device found: NUPKK17517600027


4/8/2019 9:20:51 AM Starting to write device in FASTBOOT mode...
File to update: VKY-AL00_M00A066_Board_Software_general_7.0.0_r1_EMUI5 .1_05022AWK_testpoint.dgtks

Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xx

IMEI1:xx

MEID:xx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 4716mv


Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Cannot get FBlock info from device
Trying to unlock device...
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition

Erasing cust partition
ERASE partition cust : FAIL failed to erase partition

Erasing version partition
ERASE partition version : FAIL failed to erase partition

Erasing misc partition
ERASE partition misc : FAIL failed to erase partition

Erasing userdata partition
ERASE partition userdata : FAIL failed to erase partition
xloaderpartition is not written because is in the APP file

Writing ptable partition
ptable partition UPDATE ...OK
fastbootpartition is not written because is in the APP file
vectorpartition is not written because is in the APP file
dtspartition is not written because is in the APP file
fw_lpm3partition is not written because is in the APP file
sensorhubpartition is not written because is in the APP file
fw_hifipartition is not written because is in the APP file
teeospartition is not written because is in the APP file
recoverypartition is not written because is in the APP file
cachepartition is not written because is in the APP file
bootpartition is not written because is in the APP file

Writing nvme partition
nvme partition UPDATE ...OK
trustfirmwarepartition is not written because is in the APP file
modem_fwpartition is not written because is in the APP file
modemnvm_updatepartition is not written because is in the APP file

Writing modem_om partition
modem_om partition UPDATE ...OK

Writing modemnvm_img partition
modemnvm_img partition UPDATE ...OK
isp_firmwarepartition is not written because is in the APP file
userdatapartition is not written because is in the APP file
systempartition is not written because is in the APP file

Writing version partition
version partition UPDATE ...OK

Writing splash2 partition
splash2 partition UPDATE ...OK

Writing frp partition
frp partition UPDATE ...OK

Writing secure_storage partition
secure_storage partition UPDATE ...OK

Writing modem_secure partition
modem_secure partition UPDATE ...OK
hisee_imgpartition is not written because is in the APP file
hisee_fspartition is not written because is in the APP file

Writing reserved4 partition
reserved4 partition UPDATE ...OK

Writing ufs_fw partition
ufs_fw partition UPDATE ...OK


Software written

4/8/2019 9:21:20 AM Writing device finished - INCOMPLETE

Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xx

IMEI1:xx

MEID:xx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 3038mv


4/8/2019 9:21:24 AM Starting to write device in FASTBOOT mode...

Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xx

IMEI1:xx

MEID:xx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 3038mv


Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error
Cannot get FBlock info from device
Trying to unlock device...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL image xloader1 verification error

Extracting partition FW_LPM3...
Writing FW_LPM3 partition
FW_LPM3 partition UPDATE :FAIL image verification error

Extracting partition FASTBOOT...
Writing FASTBOOT partition
FASTBOOT partition UPDATE :FAIL image verification error

Extracting partition VECTOR...
Writing VECTOR partition
VECTOR partition UPDATE :FAIL image verification error

Extracting partition MODEMNVM_UPDATE...
Writing MODEMNVM_UPDATE partition
MODEMNVM_UPDATE partition UPDATE ...OK

Extracting partition TEEOS...
Writing TEEOS partition
TEEOS partition UPDATE :FAIL image verification error

Extracting partition TRUSTFIRMWARE...
Writing TRUSTFIRMWARE partition
TRUSTFIRMWARE partition UPDATE :FAIL image verification error

Extracting partition SENSORHUB...
Writing SENSORHUB partition
SENSORHUB partition UPDATE :FAIL image verification error

Extracting partition FW_HIFI...
Writing FW_HIFI partition
FW_HIFI partition UPDATE :FAIL image verification error

Extracting partition BOOT...
Writing BOOT partition
BOOT partition UPDATE ...OK

Extracting partition RECOVERY...
Writing RECOVERY partition
RECOVERY partition UPDATE ...OK

Extracting partition RECOVERY2...
Writing RECOVERY2 partition
RECOVERY2 partition UPDATE ...OK

Extracting partition DTS...
Writing DTS partition
DTS partition UPDATE ...OK

Extracting partition CACHE...
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition
CACHE partition UPDATE ...OK

Extracting partition SYSTEM...
Writing SYSTEM partition
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 469762048 bytes
send sparse file OK
sending sparse file 429216908 bytes
send sparse file OK
SYSTEM partition UPDATE ...OK

Extracting partition ISP_FIRMWARE...
Writing ISP_FIRMWARE partition
ISP_FIRMWARE partition UPDATE :FAIL image verification error

Extracting partition MODEM_FW...
Writing MODEM_FW partition
MODEM_FW partition UPDATE :FAIL image verification error

Extracting partition HISEE_IMG...
Writing HISEE_IMG partition
HISEE_IMG partition UPDATE ...OK

Extracting partition HISEE_FS...
Writing HISEE_FS partition
HISEE_FS partition UPDATE ...OK

Extracting partition USERDATA...
Erasing USERDATA partition
Partition USERDATA erased
Writing USERDATA partition
USERDATA partition UPDATE ...OK


Software written
4/8/2019 9:28:00 AM Writing device finished - INCOMPLETE

Waiting for fastboot device...

[Disillusioned]

Also, the phone is showing FRP locked and phone unlocked in Fastboot.
Previously both were unlocked.

After removing the testpoint phone would not show any sign of life, not even Fastboot.

Please advise..

[Valdemaras]

You should try putting mobile in upgrade mode manually when software cant put it automatically.

[Disillusioned]

Log from writing VKY-L09_NV_partitions_backup.dgtks

Device found: NUPKK17517600027


4/8/2019 8:51:23 AM Starting to write device in FASTBOOT mode...
File to update: VKY-L09_NV_partitions_backup.dgtks

Looking for a device in fastboot mode
Device found: NUPKK17517600027

SN:NUPKK17517600027
IMEI:xx

IMEI1:xx

MEID:xx
Build number: :NRD90M test-keys
Model: VKY-L09
Battery state: 4778mv


Erasing modemnvm_backup partition
ERASE partition modemnvm_backup : FAIL failed to erase partition
Cannot get FBlock info from device
Trying to unlock device...
Erasing modemnvm_backup partition
ERASE partition modemnvm_backup : FAIL failed to erase partition

Erasing modemnvm_factory partition
ERASE partition modemnvm_factory : FAIL failed to erase partition

Erasing modemnvm_system partition
ERASE partition modemnvm_system : FAIL failed to erase partition

Writing modemnvm_backup partition
modemnvm_backup partition UPDATE ...OK

Writing modemnvm_factory partition
modemnvm_factory partition UPDATE ...OK

Writing modemnvm_system partition
modemnvm_system partition UPDATE ...OK


Software written

4/8/2019 8:51:46 AM Writing device finished – INCOMPLETE

[Disillusioned]

You should try putting mobile in upgrade mode manually when software cant put it automatically.

It doesn't with volume low and plugging the cable.

I thought I could flash stock without testpoint by booting into Fastboot with volume low key, but now the phone is completely dead.

[Valdemaras]

What you need to do is to flash loader + oeminfo, if after flashing them phone remains in fastboot, you must flash full stock rom matching that oeminfo data. Firmware can not be lower android version!

[Disillusioned]

What you need to do is to flash loader + oeminfo, if after flashing them phone remains in fastboot, you must flash full stock rom matching that oeminfo data. Firmware can not be lower android version!

Thanks. That's just what I did.

After flashing loader, phone would go to Fastboot for writing oeminfo. The flashing would be successful and the phone would stay in fastboot.

In fastboot, I would flash the stock rom that's available in your repository i.e. Vicky-L09A_C654B198_Firmware_Canada_Rogers_Communication s_Android_7.0_EMUI_5.1.APP

The phone was previously in Android 8.0, but there's no VKY L09 8.0 available in the repository.

Sorry you didn't get a chance to go through logs, but in short, error is in flashing XLOADER, FW_LPM3, FASTBOOT, VECTOR, TEEOS, TRUSTFIRMWARE, SENSORHUB, FW_HIFI, ISP_FIRMWARE, MODEM_FW.

[Disillusioned]

So I tried a different oeminfo file i.e. for VKY-L29 available on DC Phoenix.
Downloaded stock rom for VKY L29 from the repository and flashed it.

As usual for error flashing XLOADER, FASTBOOT etc.

Tried flashing Vicky-L29A_8.0.0.372(C636)_Firmware_8.0.0_r1_EMUI8.0_050 14KDX.APP
XLOADER and FASTBOOT passed, but there was errorflashing KERNEL and MODEM.

Now I don't even have credits to try anything else. This phone is a disaster.

[gascat]

i have had several disaster situation with various units, im still having a bit of a nightmare with a couple now but once ive worked it all out ill try an post up a guide with some tips. for now your best bet is likely to try booting in fastboot and connecting to hisuite, modify the .xml file in appdata/local/hisuite/updatedogdev to include your model in the "china" region and attempt a restore with hisuite recovery whether this will wrk or not though can be hit and miss depending on wht region youre on and how the info coming back from fastboot getvars is, if its messed up youll end up with an error saying "recovery pacakage not available" but if youre lucky and its reading right its probably your best chance for restore

[ruslanuz]

I had the same situation, but finally unbricked my p10 plus.

[Disillusioned]

I had the same situation, but finally unbricked my p10 plus.

Thanks. How did you do it, can you share details please.