Huawei mate 9 - mha-l29c567

[pvitruvian]

Hi, I'm trying to recover my phone from a bootloop situation after trying to update it to Oreo.

I followed the "Huawei Bricked phone repair guide with DC Phoenix" guide, Method 1 and 2 until now. with Method 1 DC Phoenix got stuck (Not Responding after an hour) after failing in flash boot, recovery and recovery1.

I used MHA-L29C567B190 FullOTA-MF-PV firmware downloaded from HiCloud.

After this attempt, the phone change from lock to unlock (bootloader) and it doesn't enter to eRecovery anymore normal boot take me to an error screen.

Then I tried Method 2, I download all files from DC-UNLOCKER:

MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Non specific_Android_7.0_EMUI_5.0.dgtks
L29B_C567B190_update_data_hw_usa.APP
MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP

and again DC Phoenix got stuck after the following messages:

Erasing nvme partition
Erase partition nvme ...FAILED
Cannot get FBlock info from device.
Activating backdoor: DONE

I don't want to continue with out your opinions please.

I purchased the DC-Phoenix + HCU timed license package.

Thanks,
pvitruvian

[pvitruvian]

I have some news, I started over with Method 2 but now I rebooted my PC and just open DC Phoenix. I completed Step 1 with VERLIST error so I continued with Step 2 (HCU rewrite vendor & country), after that I went back to Method 1 trying to flash Firmware but I got the VERLIST error again.
I tried this many twice, with the firmware downloaded here and with the HiCloud firmware (without customization file). After running Method 1 my phone didn't boot so I have to start from Method 2 again to boot the phone and enter to “Manufacture mode”.

DC UNLOCKER files result:

20-Dec-17 5:20:57 PM Starting to write device in UPGRADE mode...
File to update: MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP
Validating file...
Looking for attached port...
Preparing to write...
Writing partition: SHA256RSA...OK
Writing partition: CRC...OK
Writing partition: CURVER...OK
Writing partition: VERLIST...
Error downloading file MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0_3.dtwork, partition: VERLIST
Error writing software

20-Dec-17 5:21:43 PM Starting to write device in UPGRADE mode...
File to update: L29B_C567B190_update_data_hw_usa.APP
Validating file...
Looking for attached port...
Preparing to write...
Device does not support this update file
Error writing software
20-Dec-17 5:22:26 PM Writing device finished with ERROR

HiCloud file result:

Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
COM6: Android Adapter PCUI (COM6)
COM8: DBAdapter Reserved Interface (COM8)

20-Dec-17 5:30:46 PM Starting to write device in UPGRADE mode...
File to update: UPDATE.APP
Current version: MHA_Global
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 26: SHA256RSA...OK
Writing file 2 of 26: CRC...OK
Writing file 3 of 26: CURVER...OK
Writing file 4 of 26: VERLIST...
Error downloading file 4 of 26
Error writing software
20-Dec-17 5:31:29 PM Writing device finished with ERROR

Cannot update device in upgrade mode

[Valdemaras]

Hi, I'm trying to recover my phone from a bootloop situation after trying to update it to Oreo.

I followed the "Huawei Bricked phone repair guide with DC Phoenix" guide, Method 1 and 2 until now. with Method 1 DC Phoenix got stuck (Not Responding after an hour) after failing in flash boot, recovery and recovery1.

I used MHA-L29C567B190 FullOTA-MF-PV firmware downloaded from HiCloud.

After this attempt, the phone change from lock to unlock (bootloader) and it doesn't enter to eRecovery anymore normal boot take me to an error screen.

Then I tried Method 2, I download all files from DC-UNLOCKER:

MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Non specific_Android_7.0_EMUI_5.0.dgtks
L29B_C567B190_update_data_hw_usa.APP
MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP

and again DC Phoenix got stuck after the following messages:

Erasing nvme partition
Erase partition nvme ...FAILED
Cannot get FBlock info from device.
Activating backdoor: DONE

I don't want to continue with out your opinions please.

I purchased the DC-Phoenix + HCU timed license package.

Thanks,
pvitruvian

OTA updates won't work for recovering anything.... Must use Full stock roms only! Make sure you are using latest DC-Phoenix v49 version, to avoid stuck do not use computer and do not click anywhere while flash is in progress,

[pvitruvian]

OTA updates won't work for recovering anything.... Must use Full stock roms only! Make sure you are using latest DC-Phoenix v49 version, to avoid stuck do not use computer and do not click anywhere while flash is in progress,

What do I have to do with HiSuite? It pops up and tries to connect the phone on every reboot.

[Valdemaras]

What do I have to do with HiSuite? It pops up and tries to connect the phone on every reboot.

You have to keep closing it from running on PC.

[pvitruvian]

I tried again with files downloaded from DC Phoenix v49:

MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP
L29B_C567B190_update_data_hw_usa.APP

I Uninstall HiSuite so I have nothing to touch during the proccess

I always get the same error:

Waiting for fastboot device...

Device found: 45IS5VE737557376

Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
COM6: Android Adapter PCUI (COM6)
COM8: DBAdapter Reserved Interface (COM8)

21-Dec-17 9:20:57 AM Starting to write device in UPGRADE mode...
File to update: MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP
Validating file...
Looking for attached port...
Preparing to write...
Writing partition: SHA256RSA...OK
Writing partition: CRC...OK
Writing partition: CURVER...OK
Writing partition: VERLIST...
Error downloading file MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0_3.dtwork, partition: VERLIST
Error writing software

21-Dec-17 9:21:43 AM Starting to write device in UPGRADE mode...
File to update: L29B_C567B190_update_data_hw_usa.APP
Validating file...
Looking for attached port...
Preparing to write...
Device does not support this update file
Error writing software
21-Dec-17 9:22:26 AM Writing device finished with ERROR

After that I can't go to Step 2 because the phone doesn't boot (Bootloop/eRocovery) and I can't set it to “Manufacture mode”. I don't know what I'm doing wrong. Please Help me!

[Valdemaras]

I tried again with files downloaded from DC Phoenix v49:

MHA-L29B_C567B190_Firmware_United_States_Nonspecific_A ndroid7.0_EMUI5.0.APP
L29B_C567B190_update_data_hw_usa.APP

I Uninstall HiSuite so I have nothing to touch during the proccess

I always get the same error:



After that I can't go to Step 2 because the phone doesn't boot (Bootloop/eRocovery) and I can't set it to “Manufacture mode”. I don't know what I'm doing wrong. Please Help me!

Good thing our guide says what to do then. But as always you never read. Flash only in fastboot so that phone can boot up, repair your vendor/country and then flash in upgrade mode.

[pvitruvian]

Good thing our guide says what to do then. But as always you never read. Flash only in fastboot so that phone can boot up, repair your vendor/country and then flash in upgrade mode.

I didn't choose to run the process in "upgrade mode", DC Phoenix change the phone mode automatically.

"Select "Standard" mode. DC-Phoenix will flash phone in fastboot and finish flashing in upgrade mode at once."

Where does in the guide say that I just have to run the process in fastboot mode and after fixing Vendor/country in "upgrade mode"? Do I have to stop DC Phoenix before it finish?

[Valdemaras]

You have to flash board/factory software, boot up, repair model/country/vendor, flash your wished firmware/update data.

[pvitruvian]

You have to flash board/factory software, boot up, repair model/country/vendor, flash your wished firmware/update data.

Sorry but it will help if you put more detailed information on the guide, instructions are not really clear, at least for me.

Finally, while I was waiting for an answer, I tried eRecovery again (it didn't work before flashing factory ROM) and it worked, so I'm back on the stock ROM!.

I've to use HCU to fix empty board.

Everything seems to be ok now.

Thanks.

[Valdemaras]

Great news, glad it all worked out in the end for you.