GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > DC Unlocker

Reply
 
LinkBack Thread Tools Display Modes
Old 08-13-2019, 07:23   #1 (permalink)
Freak Poster
 
SeharH's Avatar
 
Join Date: Sep 2017
Location: ISI,AU3,And At SeharH's World
Posts: 329
Member: 2753718
Status: Offline
Sonork: FB : SeharH Gsm Services
Thanks Meter: 372
MHA-L09 Repeat Dead After flash stock or board file


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
  Reply With Quote
Old 08-13-2019, 08:55   #2 (permalink)
Product Supporter
 
Join Date: Sep 2013
Posts: 3,150
Member: 2023196
Status: Offline
Thanks Meter: 1,067
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.
  Reply With Quote
Old 08-13-2019, 09:06   #3 (permalink)
Freak Poster
 
SeharH's Avatar
 
Join Date: Sep 2017
Location: ISI,AU3,And At SeharH's World
Posts: 329
Member: 2753718
Status: Offline
Sonork: FB : SeharH Gsm Services
Thanks Meter: 372
Quote:
Originally Posted by Namelocked View Post
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
  Reply With Quote
Old 08-13-2019, 09:14   #4 (permalink)
Freak Poster
 
SeharH's Avatar
 
Join Date: Sep 2017
Location: ISI,AU3,And At SeharH's World
Posts: 329
Member: 2753718
Status: Offline
Sonork: FB : SeharH Gsm Services
Thanks Meter: 372
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
  Reply With Quote
Old 08-13-2019, 13:01   #5 (permalink)
Major Poster
 
Join Date: Feb 2017
Location: Canada
Posts: 41
Member: 2689153
Status: Online
Thanks Meter: 24
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
  Reply With Quote
Old 08-13-2019, 14:51   #6 (permalink)
Freak Poster
 
SeharH's Avatar
 
Join Date: Sep 2017
Location: ISI,AU3,And At SeharH's World
Posts: 329
Member: 2753718
Status: Offline
Sonork: FB : SeharH Gsm Services
Thanks Meter: 372
Quote:
Originally Posted by Takeda93 View Post
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
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 03:24.



Powered by Searchlight © 2019 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2017 -
Page generated in 0.31613 seconds with 7 queries

SEO by vBSEO