Red State on highly elusive MT6853 device

Ml133d
Newbie

2

21-07-2021, 04:28 PM

#1

Hi Team,

Has anyone had any luck overcoming the BROM protection on a bricked Mediatek Dimensity 800u based device?

Or experience in using this: https://github.com/bkerler/mtkclient - which seems to have a payload for this highly elusive chipset?

Thanks in advance,
Mueed

X3non
Recognized Contributor

22,062

22-07-2021, 03:47 PM

#2

(21-07-2021, 04:28 PM)Ml133d Hi Team,

Has anyone had any luck overcoming the BROM protection on a bricked Mediatek Dimensity 800u based device?

Or experience in using this: https://github.com/bkerler/mtkclient - which seems to have a payload for this highly elusive chipset?

Thanks in advance,
Mueed

you could actually try the payload from that link in mtk bypass @ https://www.hovatek.com/forum/thread-37957.html
you'll need to copy the payload.bin for your chipset into the payloads folder
then modify default_config.json5 (add the configs for your chipset using the contents within as example)
the config values for your chipset you can get from the link @ https://github.com/bkerler/mtkclient/blo..._config.py

e.g for MT6853, you can add the following into default_config.json5

Code:

"0x996": { // mt6853

        "watchdog_address": 0x10007000,

        "var_1": 0xA,

        "payload": "mt6853_payload.bin"

    },

it seems like something that could work, you try and let us know how it goes

This post was last modified: 22-07-2021, 03:52 PM by X3non.

Ml133d
Newbie

2

22-07-2021, 08:24 PM

#3

Thank you X3non it makes sense but unfortunately I get this error:

[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n

Maybe the MTKClient payload isn't compatible with the Bypass utility?

Thanks again

X3non
Recognized Contributor

22,062

23-07-2021, 04:43 PM

#4

(22-07-2021, 08:24 PM)Ml133d Thank you X3non it makes sense but unfortunately I get this error:

[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n

Maybe the MTKClient payload isn't compatible with the Bypass utility?

Thanks again

the error doesn't seem related to the payload but rather libusb, you could try removing the filter and installing it again or you could even try using a PC with different Windows OS

alternatively, you could try using mtkclient, the readme is quite easy to understand and it's almost similar to bypass ultility
i'll explain how to use zadig (windows tool) though because it might be difficult to understand

launch the tool from the setup (windows) folder
now the tricky part is crashing brom ; see https://www.hovatek.com/blog/how-to-forc...brom-mode/ (seeing as you've used mtk bypass, you'll understand this step)
you should get mtk usb port in device manager before proceeding with zadig > Options > List all devices
In the dropdown bar in zadig, you'll find and select mtk usb port
now change the dropdown bar just beside the green right hand arrow symbol to libusb-win32
finally click the "replace driver" button
if successful, then in device manager you'll find "mtk usb port" now listed under libusb*** instead of under "ports & lpt"

at this point, you can move onto mtkclient's readme ##usage
various commands for various things such as bypassing sla e.t.c or even reading / writing from emmc (incase you wish to backup or flash rom files)

let me know how it goes

This post was last modified: 23-07-2021, 04:46 PM by X3non.

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions