Redmi 5 Plus MEG7 System has been destroyed [Answered]

[supersincero]

Hi
I already try to restore software using UMT and it flash ok, but still stuck in this error.

I want to try using Octo Pro, but receive this error:



Welcome to Medusa Pro Software version 2.2.2.
Started.
Reader #0: Generic EMV Smartcard Reader 0

Model Settings:
Interface : USB
Brand : Xiaomi
Model : Redmi_5_Plus_MEE7
SRF : C:/Program Files/Medusa Pro Software/firmwareFolder/XIAOMI_REDMI_5_PLUS_MEE7_USB.SRF
Core : Qualcomm MSM8953
Loader : QLoader_v2_Xiaomi

Connecting...
Connect unsuccessful.
SRF "C:/Program Files/Medusa Pro Software/firmwareFolder/XIAOMI_REDMI_5_PLUS_MEE7_USB.SRF" has been installed successfully.

Model Settings:
Interface : USB
Loading custom loader E:/Xiaomi/Celular/Redmi 5 Plus - MEG7/Xiaomi Redmi 5 Plus (Redmi Note 5) Firehose File [No Need Auth]/prog_emmc_firehose_Sdm660_ddr.elf file...
Core : Custom Loader
Loader : prog_emmc_firehose_Sdm660_ddr.elf

Connecting...
Connect unsuccessful.


What I doing wrong?

Tks

[Octopus support]

Hello.

Most likely, the protection bit and your phone are higher than the protection bit that our Loader works with.

You can load your loader by setting the Special Loader option.

[supersincero]

Yes, I tried too with this loader

""Model Settings:
Interface : USB
Loading custom loader E:/Xiaomi/Celular/Redmi 5 Plus - MEG7/Xiaomi Redmi 5 Plus (Redmi Note 5) Firehose File [No Need Auth]/prog_emmc_firehose_Sdm660_ddr.elf file...
Core : Custom Loader
Loader : prog_emmc_firehose_Sdm660_ddr.elf

Connecting...
Connect unsuccessful.""

But not work too. I find this loader ""prog_emmc_firehose_Sdm660_ddr.elf"" on internet that said this is no auth.

Any loader sujest to connect the phone to octo?

tks

[andrei_d1978]

Originally Posted by Octopus support

Hello.

Most likely, the protection bit and your phone are higher than the protection bit that our Loader works with.

You can load your loader by setting the Special Loader option.

It's time to output more information to the processor log, the full HW ID 0x000460E120161721, and not the stump 0x000460E1, also the cache of the root certificate registered in the proce and the PBL version, as well as the same data about the loader, and that it is built into the software and custom