Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Oppo F15/MT6771] - Device has is either already unlocked or algo is unknown. Aborting. #1125

Open
pram0dm opened this issue Jul 26, 2024 · 4 comments

Comments

@pram0dm
Copy link

pram0dm commented Jul 26, 2024

I'm trying to unlock the bootloader of my Oppo F15 and I'm hit with the DaHandler - [LIB]: Device has is either already unlocked or algo is unknown. Aborting. issue.

This may seem to be a duplicate of many earlier posts, but I didn't find any convincing answers to the issues that were reported.

Can you please let me know what might be causing this situation?

Below is the complete output for your perusal.

Port - Device detected :)
Preloader -     CPU:                    MT6771/MT8385/MT8183/MT8666(Helio P60/P70/G80)
Preloader -     HW version:             0x0
Preloader -     WDT:                    0x10007000
Preloader -     Uart:                   0x11002000
Preloader -     Brom payload addr:      0x100a00
Preloader -     DA payload addr:        0x201000
Preloader -     CQ_DMA addr:            0x10212000
Preloader -     Var1:                   0xa
Preloader - Disabling Watchdog...
Preloader - HW code:                    0x788
Preloader - Target config:              0xe5
Preloader -     SBC enabled:            True
Preloader -     SLA enabled:            False
Preloader -     DAA enabled:            True
Preloader -     SWJTAG enabled:         True
Preloader -     EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT:  False
Preloader -     Root cert required:     False
Preloader -     Mem read auth:          True
Preloader -     Mem write auth:         True
Preloader -     Cmd 0xC8 blocked:       True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader -     HW subcode:             0x8a00
Preloader -     HW Ver:                 0xca00
Preloader -     SW Ver:                 0x0
Preloader - ME_ID:                      414392D03FAC49E607288B21EA645ADD
Preloader - SOC_ID:                     82917D6451E226CF38164758140572DC7D692BE43DC787C87E35E0D689C568D6
Preloader
Preloader - [LIB]: Auth file is required. Use --auth option.
DaHandler - Device is protected.
DaHandler - Device is in BROM-Mode. Bypassing security.
DaHandler - Preloader is not supplied. Acquiring it through BROM exploit.
PLTools - Loading payload from mt6771_payload.bin, 0x264 bytes
Exploitation - Kamakiri Run
Exploitation - Done sending payload...
PLTools - Successfully sent payload: C:\Users\pmohandas\Downloads\DRM\mtkclient\mtkclient\payloads\mt6771_payload.bin
Port - Device detected :)
DaHandler
DaHandler - [LIB]: Device is in BROM mode. No preloader given, trying to dump preloader from ram.
DAXFlash - Uploading xflash stage 1 from MTK_DA_V5.bin
XFlashExt - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "hash_check" in preloader
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "get_vfy_policy" in preloader
XFlashExt - Patching da2 ...
XFlashExt - Security check patched
XFlashExt - DA version anti-rollback patched
XFlashExt - SBC patched to be disabled
XFlashExt - Register read/write not allowed patched
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - Sending emi data ...
DAXFlash - DRAM setup passed.
DAXFlash - Sending emi data succeeded.
DAXFlash - Uploading stage 2...
DAXFlash - Upload data was accepted. Jumping to stage 2...
DAXFlash - Boot to succeeded.
DAXFlash - Successfully uploaded stage 2
DAXFlash - DA SLA is disabled
DAXFlash - UFS Blocksize:0x1000
DAXFlash - UFS ID:       KM8V8001JM-B81
DAXFlash - UFS MID:      0xce
DAXFlash - UFS CID:      ce014b4d3856383030314a4d2d423831
DAXFlash - UFS FWVer:    31303030
DAXFlash - UFS Serial:   336336616630306338393063
DAXFlash - UFS LU0 Size: 0x1dcb000000
DAXFlash - UFS LU1 Size: 0x400000
DAXFlash - UFS LU2 Size: 0x400000
DAXFlash - HW-CODE         : 0x788
DAXFlash - HWSUB-CODE      : 0x8A00
DAXFlash - HW-VERSION      : 0xCA00
DAXFlash - SW-VERSION      : 0x0
DAXFlash - CHIP-EVOLUTION  : 0x0
DAXFlash - DA-VERSION      : 1.0
DAXFlash - Extensions were accepted. Jumping to extensions...
DAXFlash - Boot to succeeded.
DAXFlash - DA Extensions successfully added
XFlashExt - Detected V4 Lockstate
Sej - HACC init
Sej - HACC run
Sej - HACC terminate
Sej - HACC init
Sej - HACC run
Sej - HACC terminate
Sej - HACC init
Sej - HACC run
Sej - HACC terminate
DaHandler
DaHandler - [LIB]: Device has is either already unlocked or algo is unknown. Aborting.

Attached are my preloader and secfg files.

preloader_oppo6771.zip
secfg.zip

@pram0dm pram0dm changed the title [Oppo F15/MT6771] - Device has is either already unlocked or algo is unknown [Oppo F15/MT6771] - Device has is either already unlocked or algo is unknown. Aborting. Jul 26, 2024
@ghost
Copy link

ghost commented Jul 27, 2024

I mean it said the current algorithm isn't supported at this time? 🤦

@pram0dm
Copy link
Author

pram0dm commented Jul 27, 2024

I mean it said the current algorithm isn't supported at this time? 🤦

And yet we've instances like this?

@ghost
Copy link

ghost commented Jul 27, 2024

I mean it said the current algorithm isn't supported at this time? 🤦

And yet we've instances like this?

You must realize that some devices might have a newer algorithm than what the tool currently supports...

@pram0dm
Copy link
Author

pram0dm commented Jul 27, 2024

I mean it said the current algorithm isn't supported at this time? 🤦

And yet we've instances like this?

You must realize that some devices might have a newer algorithm than what the tool currently supports...

True.
But I'm hoping for the author to tell me if that's really the case or not since there are also positive outcomes to this error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant