MHA-L09 Repeat Dead After flash stock or board file - GSM-Forum

SeharH · 08-13-2019, 07:23

This device can be alive while i update with bootloader kiring969_T2_A7.0_V4
After update bootloader device came on in fastboot mode than i write board and stock file in standard mode but it show many errors and at the end of result device again goes dead...

LOGS

Code:

Device found: 0123456789ABCDEF


8/12/2019 11:14:19 PM Starting to write device in FASTBOOT mode...
File to update: HLMHAAL00AM00A074_Download.xml

Looking for a device in fastboot mode
Device found: 0123456789ABCDEF


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

IMEI:8619XXXXXXXX

IMEI1:8619XXXXXXX
Build number: :MHA-L09C605B111
Model: MHA-L09
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


Process identifier:17624670


Erasing ver .. .

Erasing nvme partition
Partition nvme erased
custpartition is not written because is in the APP file

Erasing misc partition
Partition misc erased
userdatapartition is not written because is in the APP file
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

Writing recovery partition
recovery partition UPDATE ...OK
cachepartition is not written because is in the APP file

Writing boot partition
boot partition UPDATE ...OK

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 splash2 partition
splash2 partition UPDATE ...OK

Writing frp partition
frp partition UPDATE ...OK
custpartition is not written because is in the APP file

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 ufs_fw partition
ufs_fw partition UPDATE ...OK
Software written
8/12/2019 11:14:40 PM Writing device finished OK

Looking for a device in fastboot mode
Device found: 0123456789ABCDEF


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

IMEI:8619XXXXXXXXXXXX

IMEI1:861XXXXXXXXXX
Build number: :MHA-L09C605B111
Model: MHA-L09
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


8/12/2019 11:14:41 PM Starting to write device in FASTBOOT mode...
File size: 4,616,224,764  bytes
Current version(CURVER): MHA_EMUI6.0_Oversea_xloader


Looking for a device in fastboot mode
Device found: 0123456789ABCDEF


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

IMEI:8619XXXXXXXXXXX

IMEI1:8619XXXXXXXXXX
Build number: :MHA-L09C605B111
Model: MHA-L09
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


Process identifier:17624673


Erasing ver .. .

Writing XLOADER partition
XLOADER partition UPDATE ...OK

Writing FW_LPM3 partition
FW_LPM3 partition UPDATE ...OK

Writing FASTBOOT partition
FASTBOOT partition UPDATE ...OK

Writing VECTOR partition
VECTOR partition UPDATE ...OK

Writing VBMETA partition
VBMETA partition UPDATE :FAIL partition length get error
Cannot get FBlock info from device
Trying to unlock device...

Signing process may take few minutes

Trying to get data from server
Waiting in queue for signing service. Expected time 7 second(s) to get data from server

Trying to get data from server
Writing VBMETA partition
VBMETA partition UPDATE :FAIL partition length get error

Writing MODEMNVM_UPDATE partition
MODEMNVM_UPDATE partition UPDATE ...OK

Writing TEEOS partition
TEEOS partition UPDATE ...OK

Writing TRUSTFIRMWARE partition
TRUSTFIRMWARE partition UPDATE ...OK

Writing SENSORHUB partition
SENSORHUB partition UPDATE ...OK

Writing FW_HIFI partition
FW_HIFI partition UPDATE ...OK

Writing DTS partition
DTS partition UPDATE ...OK

Writing KERNEL partition
KERNEL partition UPDATE :FAIL partition length get error

Writing RECOVERY_RAMDISK partition
RECOVERY_RAMDISK partition UPDATE :FAIL partition length get error

Writing RECOVERY_VENDOR partition
RECOVERY_VENDOR partition UPDATE :FAIL partition length get error

Writing RECOVERY_VBMETA partition
RECOVERY_VBMETA partition UPDATE :FAIL partition length get error

Writing ERECOVERY_KERNEL partition
ERECOVERY_KERNEL partition UPDATE :FAIL image verification error

Writing ERECOVERY_RAMDISK partition
ERECOVERY_RAMDISK partition UPDATE :FAIL partition length get error

Writing ERECOVERY_VENDOR partition
ERECOVERY_VENDOR partition UPDATE :FAIL partition length get error

Writing ERECOVERY_VBMETA partition
ERECOVERY_VBMETA partition UPDATE :FAIL partition length get error

Writing RAMDISK partition
RAMDISK partition UPDATE :FAIL partition length get error

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

Writing SYSTEM partition
sending sparse file 399459220 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471684872 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471833804 bytes
Waiting for answer...
send sparse file OK
sending sparse file 454293908 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471264164 bytes
Waiting for answer...
send sparse file OK
sending sparse file 373293224 bytes
Waiting for answer...
send sparse file OK
sending sparse file 460011852 bytes
Waiting for answer...
send sparse file OK
sending sparse file 286750992 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition UPDATE ...OK

Erasing CUST partition
Partition CUST erased
Writing CUST partition
CUST partition UPDATE ...OK

Writing ISP_FIRMWARE partition
ISP_FIRMWARE partition UPDATE ...OK

Writing MODEM_FW partition
MODEM_FW partition UPDATE ...OK

Writing HISEE_IMG partition
HISEE_IMG partition UPDATE ...OK

Writing HISEE_FS partition
HISEE_FS partition UPDATE ...OK

Writing VERSION partition
VERSION partition UPDATE ...OK

Writing ODM partition
ODM partition UPDATE :FAIL partition length get error

Erasing USERDATA partition
Waiting for answer...
Partition USERDATA erased
Writing USERDATA partition
USERDATA partition UPDATE ...OK


Software written
8/12/2019 11:18:36 PM Writing device finished - INCOMPLETE

Waiting for fastboot device...

USB Device REMOVAL
Type: @oem130.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: 0123456789ABCDEF

No devices detected in fastboot mode

BR.
SeharH

Namelocked · 08-13-2019, 08:55

After using loader + oeminfo, are you flashing same firmware version as one that is in mobile or another? There shouldn't be much problem reviving android 7 version of this mobile if using correct files.

SeharH · 08-13-2019, 09:06

Quote:

Originally Posted by Namelocked

After using loader + oeminfo, are you flashing same firmware version as one that is in mobile or another? There shouldn't be much problem reviving android 7 version of this mobile if using correct files.

To me iam trying following setting may be something wrong iam doing...

BR.
SeharH

SeharH · 08-13-2019, 09:14

Result of stock file flash after update oem

Code:

DC Phoenix 0.0.0.115
user:SeharH

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


8/13/2019 1:07:52 AM Starting to write device in FASTBOOT mode...
File size: 4,616,224,764  bytes
Current version(CURVER): MHA_EMUI6.0_Oversea_xloader


Looking for a device in fastboot mode
Device found: 0123456789ABCDEF


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

IMEI:8xxxxxxxxxxx

IMEI1:86xxxxxxxxxxx
Build number: :MHA-L09C605B111
Model: MHA-L09
Battery state: 3177mv
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


Process identifier:17626700


Erasing ver .. .

Writing XLOADER partition
XLOADER partition UPDATE ...OK

Writing FW_LPM3 partition
FW_LPM3 partition UPDATE ...OK

Writing FASTBOOT partition
FASTBOOT partition UPDATE ...OK

Writing VECTOR partition
VECTOR partition UPDATE ...OK

Writing VBMETA partition
VBMETA partition UPDATE :FAIL partition length get error
Cannot get FBlock info from device
Trying to unlock device...

Signing process may take few minutes

Trying to get data from server
Writing VBMETA partition
VBMETA partition UPDATE :FAIL partition length get error

Writing MODEMNVM_UPDATE partition
MODEMNVM_UPDATE partition UPDATE ...OK

Writing TEEOS partition
TEEOS partition UPDATE ...OK

Writing TRUSTFIRMWARE partition
TRUSTFIRMWARE partition UPDATE ...OK

Writing SENSORHUB partition
SENSORHUB partition UPDATE ...OK

Writing FW_HIFI partition
FW_HIFI partition UPDATE ...OK

Writing DTS partition
DTS partition UPDATE ...OK

Writing KERNEL partition
KERNEL partition UPDATE :FAIL partition length get error

Writing RECOVERY_RAMDISK partition
RECOVERY_RAMDISK partition UPDATE :FAIL partition length get error

Writing RECOVERY_VENDOR partition
RECOVERY_VENDOR partition UPDATE :FAIL partition length get error

Writing RECOVERY_VBMETA partition
RECOVERY_VBMETA partition UPDATE :FAIL partition length get error

Writing ERECOVERY_KERNEL partition
ERECOVERY_KERNEL partition UPDATE :FAIL image verification error

Writing ERECOVERY_RAMDISK partition
ERECOVERY_RAMDISK partition UPDATE :FAIL partition length get error

Writing ERECOVERY_VENDOR partition
ERECOVERY_VENDOR partition UPDATE :FAIL partition length get error

Writing ERECOVERY_VBMETA partition
ERECOVERY_VBMETA partition UPDATE :FAIL partition length get error

Writing RAMDISK partition
RAMDISK partition UPDATE :FAIL partition length get error

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

Writing SYSTEM partition
sending sparse file 399459220 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471684872 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471833804 bytes
Waiting for answer...
send sparse file OK
sending sparse file 454293908 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471264164 bytes
Waiting for answer...
send sparse file OK
sending sparse file 373293224 bytes
Waiting for answer...
send sparse file OK
sending sparse file 460011852 bytes
Waiting for answer...
send sparse file OK
sending sparse file 286750992 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition UPDATE ...OK

Erasing CUST partition
Partition CUST erased
Writing CUST partition
CUST partition UPDATE ...OK

Writing ISP_FIRMWARE partition
ISP_FIRMWARE partition UPDATE ...OK

Writing MODEM_FW partition
MODEM_FW partition UPDATE ...OK

Writing HISEE_IMG partition
HISEE_IMG partition UPDATE ...OK

Writing HISEE_FS partition
HISEE_FS partition UPDATE ...OK

Writing VERSION partition
VERSION partition UPDATE ...OK

Writing ODM partition
ODM partition UPDATE :FAIL partition length get error

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


Software written
8/13/2019 1:11:31 AM Writing device finished - INCOMPLETE

And phone goes dead again after remove usb cable.....

BR.
SeharH

Takeda93 · 08-13-2019, 13:01

after you flash bootloader Kirin960 you have to flash board firmware in advance mode
reboot manual to upgrade mode with usb cable in
flash stock firmware
that's it

SeharH · 08-13-2019, 14:51

Quote:

Originally Posted by Takeda93

after you flash bootloader Kirin960 you have to flash board firmware in advance mode
reboot manual to upgrade mode with usb cable in
flash stock firmware
that's it

I've revive my phone completely but by other way....Phone required high bootloader so after update with high bootloader i revive my device..Thanks all for help allot...

BR.
SeharH

Dynam0 · 01-16-2020, 17:56

Quote:

Originally Posted by SeharH

I've revive my phone completely but by other way....Phone required high bootloader so after update with high bootloader i revive my device..Thanks all for help allot...

BR.
SeharH

What bootloader you used? Thanks in advance

solgeo · 01-17-2020, 09:05

Everything is very simple on support, type in the search (downgrade.)
Find board firmware MHA
and flash it.
I hope she helps, if not, write

Dynam0 · 01-17-2020, 22:25

Quote:

Originally Posted by solgeo

Everything is very simple on support, type in the search (downgrade.)
Find board firmware MHA
and flash it.
I hope she helps, if not, write

Thanks sir, Im just trying DC software recently and its amazing. Kirin960_T2_A7.0_V3 worked for me. Now im trying to flash a board software:

MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Non specific_Android_7.0_EMUI_5.0.dgtks

Dynam0 · 01-17-2020, 22:33

Code:

Looking for a device in force upgrade mode
No devices detected in force upgrade mode
Looking for a device in fastboot mode
Device found: UGM0217901000361


17/01/2020 04:17:50 p.m. Starting to write device in FASTBOOT mode...
File to update: F:\DC\MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0.dgtks

Looking for a device in fastboot mode
Device found: UGM0217901000361


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

SN:UGM0217901000361
IMEI:861956032538739

IMEI1:861956032538739

MEID:00000000000000
Build number: :MHA-LGRP2-OVS 9.0.1.189
Model: MHA-L09
Vendor/Country: Vendor/Country: entel/la
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


Process identifier:22245467


Erasing ver .. .

Erasing nvme partition
Partition nvme erased

Erasing cust partition
Partition cust erased

Erasing misc partition
Partition misc erased

Erasing userdata partition
Partition userdata erased

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

Signing process may take few minutes

Trying to get data from server
Unlock process finished successfully

Writing xloader partition
XLOADER partition update :FAIL image xloader1 verification error

Writing ptable partition
PTABLE partition update ...OK

Writing fastboot partition
FASTBOOT partition update :FAIL image verification error

Writing vector partition
VECTOR partition update :FAIL image verification error

Writing dts partition
DTS partition update ...OK

Writing fw_lpm3 partition
FW_LPM3 partition update :FAIL image verification error

Writing sensorhub partition
SENSORHUB partition update :FAIL image verification error

Writing fw_hifi partition
FW_HIFI partition update :FAIL image verification error

Writing teeos partition
TEEOS partition update :FAIL image verification error

Writing recovery partition
RECOVERY partition update ...OK

Erasing cache partition
Partition cache erased
Writing cache partition
CACHE partition update ...OK

Writing boot partition
BOOT partition update ...OK

Writing nvme partition
NVME partition update ...OK

Writing trustfirmware partition
TRUSTFIRMWARE partition update :FAIL image verification error

Writing modem_fw partition
MODEM_FW partition update :FAIL image verification error

Writing modemnvm_update partition
MODEMNVM_UPDATE partition update ...OK

Writing modem_om partition
MODEM_OM partition update ...OK

Writing modemnvm_img partition
MODEMNVM_IMG partition update ...OK

Writing isp_firmware partition
ISP_FIRMWARE partition update :FAIL image verification error

Erasing userdata partition
Partition userdata erased
Writing userdata partition
USERDATA partition update ...OK

Writing system partition
sending sparse file 432051356 bytes
Waiting for answer...
send sparse file OK
sending sparse file 470571876 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471790840 bytes
Waiting for answer...
send sparse file OK
sending sparse file 466866708 bytes
Waiting for answer...
send sparse file OK
sending sparse file 211676256 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition update ...OK

Writing vendor partition
VENDOR partition update ...OK

Writing splash2 partition
SPLASH2 partition update ...OK

Writing frp partition
FRP partition update ...OK

Erasing cust partition
Partition cust erased
Writing cust partition
CUST partition update ...OK

Writing secure_storage partition
SECURE_STORAGE partition update ...OK

Writing modem_secure partition
MODEM_SECURE partition update ...OK

Writing hisee_img partition
HISEE_IMG partition update ...OK

Writing hisee_fs partition
HISEE_FS partition update ...OK


Software written

17/01/2020 04:25:32 p.m. Writing device finished - INCOMPLETE

INCOMPLETE error. Whats the problem here? Some help, pls?

ashahzad_pk · 01-17-2020, 23:18

I am in the same boat. Please help

Sent from my SM-G975W using Tapatalk

solgeo · 01-18-2020, 09:24

Chech Support download files
Search Downgrade
Download MHA-Downgrade-Board-A074-7.0.0_r1.dgtks
flash with testpoint

08-13-2019, 08:55	#2 (permalink)
Namelocked Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas Posts: 4,690 Member: 2023196 Status: Offline Thanks Meter: 1,891	After using loader + oeminfo, are you flashing same firmware version as one that is in mobile or another? There shouldn't be much problem reviving android 7 version of this mobile if using correct files.

08-13-2019, 13:01	#5 (permalink)
Takeda93 Freak Poster Join Date: Feb 2017 Location: Canada Posts: 131 Member: 2689153 Status: Offline Thanks Meter: 45	after you flash bootloader Kirin960 you have to flash board firmware in advance mode reboot manual to upgrade mode with usb cable in flash stock firmware that's it

01-17-2020, 09:05	#8 (permalink)
solgeo No Life Poster Join Date: Nov 2017 Location: Russian Posts: 849 Member: 2778414 Status: Offline Thanks Meter: 342	Everything is very simple on support, type in the search (downgrade.) Find board firmware MHA and flash it. I hope she helps, if not, write

01-17-2020, 23:18	#11 (permalink)
ashahzad_pk No Life Poster Join Date: Aug 2005 Location: Canada Age: 44 Posts: 744 Member: 169896 Status: Offline Thanks Meter: 323	I am in the same boat. Please help Sent from my SM-G975W using Tapatalk

01-18-2020, 09:24	#12 (permalink)
solgeo No Life Poster Join Date: Nov 2017 Location: Russian Posts: 849 Member: 2778414 Status: Offline Thanks Meter: 342	Chech Support download files Search Downgrade Download MHA-Downgrade-Board-A074-7.0.0_r1.dgtks flash with testpoint