GSM-Forum

GSM-Forum (https://forum.gsmhosting.com/vbb/)
-   DC Unlocker (https://forum.gsmhosting.com/vbb/f1004/)
-   -   MHA-AL00B bricked (https://forum.gsmhosting.com/vbb/f1004/mha-al00b-bricked-2720571/)

aleksa55 11-04-2019 18:21
MHA-AL00B bricked
 
Original state
MHA-AL00 version 9.10.200 C00
and HUAWEI ID locked

Update OEMINFO:
Code:
Device detected:
COM54: HUAWEI USB COM 1.0 (COM54)
BOOTLOADER File to update: Kirin960_T2_A7.0_V3
OEM File to update: MHA-AL00
04-Nov-19 4:39:59 PM Starting to write device...

Process identifier:20116705


Writing bootloader...
Step 1...
Step 2...
Step 3...

Waiting for device REMOVAL/INSERTION...

Waiting for fastboot device...
Device found: 3HX0xxx


Looking for a device in fastboot mode
Device found: 3HX0xxx

Getting IMEI...

USB Device REMOVAL
Type: @oem49.inf,%huawei06%;HUAWEI USB COM 1.0
VidPid: VID_12D1&PID_3609
Instance id: 5&26e7c7e1&0&1


USB Device INSERTION
Type: @oem24.inf,%tplinkfastboot%;Android Bootloader Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&1d73674e&0&1

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

SN:3HX0xxx
IMEI:8652xxx

IMEI1:865xxx

MEID:A00000xxx
Build number: :MHA-AL00 9.1.0.200(C00E200R1P14)
Model: MHA-AL00
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked

Writing OEMINFO partition
OEMINFO partition update ...OK
Software written
04-Nov-19 4:40:34 PM Writing device finished OK
flash from fastboot
Code:
ooking for a device in fastboot mode
Device found: 3HX0xxx


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

SN:3HX0xxxx
IMEI:86770xxx
IMEI1:86770xxxx
Build number: :MHA-AL00C00B231
Model: MHA-AL00
Battery state: 0
OEM lock state info:
 FB LockState: UNLOCKED
 USER LockState: LOCKED
OEM get bootinfo:
 unlocked


Process identifier:20117082


Erasing ver .. .

Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition update ...OK

Extracting partition FW_LPM3...
Writing FW_LPM3 partition
FW_LPM3 partition update ...OK

Extracting partition FASTBOOT...
Writing FASTBOOT partition
FASTBOOT partition update ...OK

Extracting partition VECTOR...
Writing VECTOR partition
VECTOR partition update ...OK

Extracting partition VBMETA...
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
Unlock process finished successfully

Writing VBMETA partition
VBMETA partition update :FAIL partition length get error

Extracting partition MODEMNVM_UPDATE...
Writing MODEMNVM_UPDATE partition
MODEMNVM_UPDATE partition update ...OK

Extracting partition TEEOS...
Writing TEEOS partition
TEEOS partition update ...OK

Extracting partition TRUSTFIRMWARE...
Writing TRUSTFIRMWARE partition
TRUSTFIRMWARE partition update ...OK

Extracting partition SENSORHUB...
Writing SENSORHUB partition
SENSORHUB partition update ...OK

Extracting partition FW_HIFI...
Writing FW_HIFI partition
FW_HIFI partition update ...OK

Extracting partition DTS...
Writing DTS partition
DTS partition update ...OK

Extracting partition KERNEL...
Writing KERNEL partition
KERNEL partition update :FAIL partition length get error

Extracting partition RECOVERY_RAMDISK...
Writing RECOVERY_RAMDISK partition
RECOVERY_RAMDISK partition update :FAIL partition length get error

Extracting partition RECOVERY_VENDOR...
Writing RECOVERY_VENDOR partition
RECOVERY_VENDOR partition update :FAIL partition length get error

Extracting partition RECOVERY_VBMETA...
Writing RECOVERY_VBMETA partition
RECOVERY_VBMETA partition update :FAIL partition length get error

Extracting partition ERECOVERY_KERNEL...
Writing ERECOVERY_KERNEL partition
ERECOVERY_KERNEL partition update :FAIL partition length get error

Extracting partition ERECOVERY_RAMDISK...
Writing ERECOVERY_RAMDISK partition
ERECOVERY_RAMDISK partition update :FAIL partition length get error

Extracting partition ERECOVERY_VENDOR...
Writing ERECOVERY_VENDOR partition
ERECOVERY_VENDOR partition update :FAIL partition length get error

Extracting partition ERECOVERY_VBMETA...
Writing ERECOVERY_VBMETA partition
ERECOVERY_VBMETA partition update :FAIL partition length get error

Extracting partition RAMDISK...
Writing RAMDISK partition
RAMDISK partition update :FAIL partition length get error

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 470134820 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471486440 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471833284 bytes
Waiting for answer...
send sparse file OK
sending sparse file 436536428 bytes
Waiting for answer...
send sparse file OK
sending sparse file 470965000 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471393312 bytes
Waiting for answer...
send sparse file OK
sending sparse file 264329236 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition update ...OK

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

Extracting partition ISP_FIRMWARE...
Writing ISP_FIRMWARE partition
ISP_FIRMWARE partition update ...OK

Extracting partition MODEM_FW...
Writing MODEM_FW partition
MODEM_FW partition update ...OK

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 VERSION...
Writing VERSION partition
VERSION partition update ...OK

Extracting partition ODM...
Writing ODM partition
ODM partition update :FAIL partition length get error

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


Software written
04-Nov-19 5:08:49 PM Writing device finished - INCOMPLETE

Waiting for fastboot device...

USB Device REMOVAL
Type: @oem24.inf,%tplinkfastboot%;Android Bootloader Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&1d73674e&0&1
now phone power on only by test point in fastboot mode

pls help

Namelocked 11-05-2019 09:11
Yes, that what happens when you flash from fastboot. Please refer here https://www.dc-unlocker.com/dc-phoen...epair-tutorial For your phone must put check mark on rescue recovery option as mentioned in guide.

aleksa55 11-05-2019 10:29
Progress

Update OEM
Bootloader: Kirin960_T2_A7.0_V3
MHA-AL00 cn/all
from fastboot
HLMHAAL00AM00A073_Board Software_ ... ral_7.0.0_r1_EMUI5.0_05021YVS
selectet in DC-PHOENIX update_nv_rback.xml

Now phone boot normal with board fw from link
(all board fw MHA-XXX from dc support is useless for this case)

next step how to flash back normal fw: ?

aleksa55 11-05-2019 12:32
Quote:
Originally Posted by Namelocked (Post 13884741)
Yes, that what happens when you flash from fastboot. Please refer here https://www.dc-unlocker.com/dc-phoen...epair-tutorial For your phone must put check mark on rescue recovery option as mentioned in guide.
tutorial is familiar for many other model but does not work on MHA-AL00

aleksa55 11-05-2019 13:52
Fastboot and rescue recovery on

Quote:
PM Starting to try Rescue Recovery...


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:8677xxx

IMEI1:8677xxx
Build number: :MHA-AL00C00B231
Model: MHA-AL00
Battery state: 4319mv
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked


Process identifier:20143046

Getting build number...
Getting base version...
Getting cust version...
Getting preload version...

Erasing ver .. .
Writing rescue_recovery_kernel partition
rescue_recovery_kernel partition UPDATE ...OK
Writing rescue_recovery_ramdisk partition
rescue_recovery_ramdisk partition UPDATE ...OK
Writing rescue_recovery_vendor partition
rescue_recovery_vendor partition UPDATE ...OK

Cannot enter in Recovey mode

Namelocked 11-05-2019 17:54
It doesn't seem you did method 3.

aleksa55 11-05-2019 19:15
any solution to flash back firmware ?

aleksa55 11-05-2019 19:22
when i try to flash from update mode

Quote:
Validating file...
Looking for attached port...
Preparing to write...

Extracting partition SHA256RSA...
Writing partition: SHA256RSA...
Writing partition: SHA256RSA...OK

Extracting partition CRC...
Writing partition: CRC...
Writing partition: CRC...OK

Extracting partition CURVER...
Writing partition: CURVER...
Writing partition: CURVER...OK

Extracting partition VERLIST...
Writing partition: VERLIST...
Writing partition: VERLIST...OK

Extracting partition PACKAGE_TYPE...
Writing partition: PACKAGE_TYPE...
Writing partition: PACKAGE_TYPE...OK

Extracting partition HISIUFS_GPT...
Writing partition: HISIUFS_GPT...
Writing partition: HISIUFS_GPT...OK

Extracting partition XLOADER...
Writing partition: XLOADER...
Error downloading file MHA-L29B_8.0.0.363(C432)_Firmware_Serbia_Portugal_Belg ium_Spain_Denmark_Netherlands_Germany_Switzerland_ Italy_Bosnia_and_Herzegovina_Nonspecific_05014BFF_ 6.dtwork, partition: XLOADER

Error writing software
05-Nov-19 8:19:48 PM Writing device finished with ERROR

Namelocked 11-06-2019 11:25
Does flashing board software file succeed and mobile boots afterwards?

aleksa55 11-19-2019 18:10
fixed by other method ($$)


All times are GMT +1. The time now is 00:09.


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -

Page generated in 0.18933 seconds with 7 queries

SEO by vBSEO