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

MTKClient Compatibility with MT6765 (2023 Handset) #1243

Open
RobertHerreraEECS opened this issue Oct 8, 2024 · 3 comments
Open

MTKClient Compatibility with MT6765 (2023 Handset) #1243

RobertHerreraEECS opened this issue Oct 8, 2024 · 3 comments

Comments

@RobertHerreraEECS
Copy link

RobertHerreraEECS commented Oct 8, 2024

Hi there,

I am currently having some issues triggering BROM mode on a Galaxy Handset (2023) A03s SM-S135DL. In short, what I'm noticing is this version of the MT6765 does not seem vulnerable to a wide variety of different attacks: MTKClient using auth file or alternate DA's, MTKClient fails to initially crash the DA in first place, test point shorting does not default to BROM mode but defaults to the preloader. Grounding or otherwise tampering with the SD line between the SoC and eMMC does not trigger BROM as originally anticipated.

Do you have any insight as to whether these newer variants may have a hardware-based mitigation such as a fuse that disable download (BROM) mode?

@R0rt1z2
Copy link
Contributor

R0rt1z2 commented Oct 8, 2024

Hi there,

I am currently having some issues triggering BROM mode on a Galaxy Handset (2023) A03s. In short, what I'm noticing is this version of the MT6765 does not seem vulnerable to a wide variety of different attacks: MTKClient using auth file or alternate DA's, MTKClient fails to initially crash the DA in first place, test point shorting does not default to BROM mode but defaults to the preloader. Grounding or otherwise tampering with the SD line between the SoC and eMMC does not trigger BROM as originally anticipated.

Do you have any insight as to whether these newer variants may have a hardware-based mitigation such as a fuse that disable download (BROM) mode?

Based on the description you provided, I wouldn't be surprised if Samsung has disabled BROM mode using fuses, similar to what some OEMs like Xiaomi, Amazon, and others have done.

If that’s the case, unfortunately, there’s not much you can do, as there isn’t a known Preloader-based exploit for the MT6765 that gives you arbitrary code execution at all.

Apparently, someone reported an issue (regarding connection issues) with the same phone model (I think?) not too long ago: #251.

@petskungu
Copy link

Same here, I've tried to exploit the preloader on LG k51, but it disconnects as soon as it connects, no brom and no active bootloader, if anyone knows a what around this particular device please reach me @ [email protected]

@splitmare
Copy link

splitmare commented Nov 6, 2024

I have managed to enter BROM mode on Galaxy A13 5G but it requires wiping the PGPT (which i somehow wiped with a locked bootloader, dont ask me how)

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

4 participants