Huawei Mate 9 (MHA-L29) Erase FRP problem

[NightWind]

Hello,

I've tried DC-Unlocker with my bricked Huawei Mate 9 to erase Factory Reset Protection, but without any success. Could you confirm please if it should work or will work in the future. Or did I made any something wrong?

I really need to unbrick my phone.


Logs:

================================================== =================
DC - Unlocker 2 Client 1.00.1361

Detecting phone :

selection :
manufacturer - Huawei phones
model - Huawei phone in fastboot mode

Found Phone : MHA-L29
Model : Huawei phone in fastboot mode
IMEI : **************
Serial NR. : **************
Firmware : MHA-L29C567B138

IMEI1:**************
FB LockState: LOCKED
USER LockState: RELOCKED
unlocked
Battery state: 5126mv

================================================== =================
Check account status
User : DmitriiSh
Credits left : 15

Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (**************) cost 15 cr
2017.02.02 16:41:36.631 Logging enabled !
================================================== =================
Factory reset protection Erase start
Erase FRP done!
Credits left : 0
================================================== =================

================================================== =================
DC - Unlocker 2 Client 1.00.1361

Detecting phone :
selection :
manufacturer - Huawei phones
model - Huawei phone in fastboot mode

Found Phone : MHA-L29
Model : Huawei phone in fastboot mode
IMEI : **************
Serial NR. : **************
Firmware : MHA-L29C567B138
IMEI1:**************
FB LockState: LOCKED
USER LockState: RELOCKED
unlocked
Battery state: 4868mv

================================================== =================

[Valdemaras]

Why you would want to unlock FRP on bricked phone? FRP unlock only removes google account sign in from boot up. Can try repair it with method 1 with dc phoenix https://www.dc-unlocker.com/DC-Phoen...epair-tutorial

[NightWind]

I want to unlock it because my phone does have a working firmware on it. My theory is that it cannot boot because my bootloader is relocked and it checks a signature of the recovery. It fails (due to the fact that I have TWRP in the recovery section) and boots into eRecovery. The problem is that I cannot unlock the bootloader again (with the right code) because of FRP flag.

I didn't bind my phone to the Google Account, but the thing I did is that: My phone was rooted and worked fine and I tried to relock my bootloader but, looks like, kept an option "OEM unlock" in the developer settings disabled. It allowed me to relock bootloader and didn't allowed to boot with TWRP in the recovery section. It, also, didn't allow to unlock bootloader again.

My current options are:
1. Flashing the recovery by using DC Phoenix from a europian firmware as my MHA-L29C567B138 isn't available anywhere. I hope the device won't reject that. Then I'll enable "OEM unlock" again and unlock bootloader
2. Unlock bootloader by using DC Phoenix. Is the tool able to do that for me? Again I have the right unlock code, but it doesn't allow me to do that (see detail bellow).
3. Wait until FRP unlock function will work for me.

What would you suggest to do? Does it make any sense?



>fastboot oem unlock **************
FAILED (remote: Command not allowed)

>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.016s]

>fastboot oem relock **************
FAILED (remote: stat not match)

[NightWind]

I've managed to recover my phone.

The first thing I did was flashing only RECOVERY partition from MHA-L29C432B138 (the firmware with my version is not available now). I was hoping that the bootloader would accept the official recovery from another location, but it didn't

Then I decided to try flashing BOOT partition. It was a more risky thing because bootloader from one firmware could fail to load another one. But it worked! The system loaded, I opened developer setting and enabled "OEM unlocking". It changed "FRP Lock" label in the fastboot screen to "FRP Unlock" and allowed me to unlock bootloader again.

Thank you for the tool!

[Valdemaras]

Great news, thank you for sharing this info with us.