Huawei GR5 2017 (BLL-L22) Not Showing Up During DC Phoenix Flash

[ngage3650]

Hi all,

I purchased the DC Phoenix pack for 72 hours to try and revive a Huawei GR5 2017 that's completely dead.

Black screen. No fastboot, adb, eRecovery - nothing.
Connected to my PC and I got "USB SER" which I installed the drivers (That had to be digitally signed etc)
But the phone shows up as "Huawei USB Com 1.0" in Device Manager.

So using the DC Software, I go to Download File and I couldn't find anything (Typed GR5, BLL-L22 etc and no results)
Instead I used the latest update.app file and it showed everything (File structure etc)

Then as I clicked start it said that there was no phone connected.
Unplugged and plugged in again and nothing, same thing.

The PC has recognized the phone but all it says is "Huawei USB COM 1.0 (COM72)"

I also tried the usual 3 button flash from SD Card and OTG and nothing.

So have I spent the $30 on the software that probably won't be able to fix it? Or is there something else I can try to get it working.

Would really appreciate some help.
Thanks!

[Valdemaras]

In usb com 1.0 mode you can use only board software or loader + oeminfo solution as explained in method 2/3 of dc-phoenix guide which you must read before initiating anything on the software. Your phone goes under Berlin code name which you should use in search field. I'd suggest to use loader + oeminfo and then flash full stock rom if mobile enters fastboot.

[ngage3650]

I did read through the guide and from what I can see, the methods are usually the same. (Read them again and again to make sure and I am reading the guide for the USB COM one)
The phone doesn't enter fastboot apart from the USB COM Driver so I'll try again and see what happens.

EDIT: I tried with the Board Software, it detects the phone but says "Can't open COM 72" and fails.
EDIT2: I tried with a loader and same thing, "cannot open COM Port" and phone is detected as the USB COM Driver still.
It says waiting for fastboot device and I can't boot into fastboot at all.
EDIT3: Played around with it further (Drivers etc) and got it to start writing but I get "Error writing Bootloader
30/05/2019 6:19:18 AM Writing device finished - INCOMPLETE"

The board software file is - "Berlin-L21_Berlin-L23_Berlin-L22_MBD001031_Board Software_general_05021YGY"
The Update.app is - "Berlin-L22_C636B160_Firmware_Cambodia_Nepal_Thailand_Phil ippines_Egypt_Nonspecific"
And the customization is the same.

Will try another board software but it can not write the bootloader.

Tried another board software, same result.

Screenshots are attached.

[Valdemaras]

Then only way to revive it is to replace main board on device

[ngage3650]

Then only way to revive it is to replace main board on device

Yeah that is unfortunate. I tried everything to revive it and nothing. Would I be able to get a refund on the tool if that's ok?

[Valdemaras]

Refund now completed.