bkerler / mtkclient

MTK reverse engineering and flash tool
GNU General Public License v3.0
2.47k stars 493 forks source link

handshake error/DAA_SIG_VERIFY_FAILED #1068

Closed r4db closed 1 month ago

r4db commented 2 months ago

i am trying to fix bricked oppo reno 5z

[20:04:52]: Status: Waiting for PreLoader VCOM, please connect mobile [20:05:22]: Status: Handshake failed, retrying... [20:05:26]: Status: Handshake failed, retrying... [20:05:29]: Status: Handshake failed, retrying... [20:05:39]: Status: Handshake failed, retrying...

and if it helps the device shows up as usb serial device on device manager but i have installed mtk drivers

update: i tried linux

[07:11:50]: We're not in bootrom, trying to crash da... [07:11:50]: Crashing da... [07:11:53]: Crashing da... [07:11:56]: Crashing da... [07:11:59]: Loading payload from mt6853_payload.bin, 0x264 bytes [07:11:59]: Kamakiri / DA Run [07:11:59]: Trying kamakiri2..

Port - Device detected :) Preloader - CPU: MT6853(Dimensity 720 5G) 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: 0x996 Preloader - Target config: 0x5 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: False Preloader - Mem write auth: False Preloader - Cmd 0xC8 blocked: False Preloader - Get Target info Preloader - HW subcode: 0x8a00 Preloader - HW Ver: 0xca00 Preloader - SW Ver: 0x0 Preloader Preloader - [LIB]: upload_data failed with error: DAA_SIG_VERIFY_FAILED (0x7024) Preloader Preloader - [LIB]: Error on uploading da data Preloader - Jumping to 0x0 DeviceClass - USBError(19, 'No such device (it may have been disconnected)') Preloader - Status: Waiting for PreLoader VCOM, please connect mobile

Port - Hint:

Power off the phone before connecting. For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb. For preloader mode, don't press any hw button and connect usb.

Port - Device detected :) Preloader - CPU: MT6853(Dimensity 720 5G) 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: 0x996 Preloader - Target config: 0x5 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: False Preloader - Mem write auth: False Preloader - Cmd 0xC8 blocked: False Preloader - Get Target info Preloader - HW subcode: 0x8a00 Preloader - HW Ver: 0xca00 Preloader - SW Ver: 0x0 DeviceClass - USBError(19, 'No such device (it may have been disconnected)') Preloader Preloader - [LIB]: Error on DA_Send cmd Preloader - Status: Waiting for PreLoader VCOM, please connect mobile Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... DeviceClass - USBError(19, 'No such device (it may have been disconnected)') Preloader - Status: Waiting for PreLoader VCOM, please connect mobile Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying... Preloader Preloader - [LIB]: Status: Handshake failed, retrying...

NasiGorengBurung commented 2 months ago

This is common issue that no one willingly to solve. I hope someone can provide solution to solve handshake failed, because i do not know how to solve it, even my chipset is not in v6 list, and there are da file that's exact to my chipset :/

NasiGorengBurung commented 2 months ago

Found it, this should help you https://web.archive.org/web/20240130100627/https://github.com/bkerler/mtkclient/issues/52

r4db commented 1 month ago

Found it, this should help you https://web.archive.org/web/20240130100627/https://github.com/bkerler/mtkclient/issues/52

sadly it didnt work for me

r4db commented 1 month ago

i tried mtk bypass. It didnt work it just said "waiting for device" even after plugging it in

NasiGorengBurung commented 1 month ago

i tried mtk bypass. It didnt work it just said "waiting for device" even after plugging it in

Check if it support by mtk bypass. Example, Helio P70 are being supported. I remember when i tried unsupported MTK SoC on mtk bypass, it just draw paragraph of code error

NasiGorengBurung commented 1 month ago

Found it, this should help you https://web.archive.org/web/20240130100627/https://github.com/bkerler/mtkclient/issues/52

sadly it didnt work for me

https://github.com/bkerler/mtkclient/issues/758

r4db commented 1 month ago

Found it, this should help you https://web.archive.org/web/20240130100627/https://github.com/bkerler/mtkclient/issues/52

sadly it didnt work for me

758

i think i have found my problem #830 but my question is how do i get da and auth file for this device?

NasiGorengBurung commented 1 month ago

i tried mtk bypass. It didnt work it just said "waiting for device" even after plugging it in

In mtk thread, xda server. Some people said...

try running mtkclient and see if it runs successfully. If it's stuck or gives out an error even if you've successfully downloaded all dependencies and run BROM properly. You can get the bypass utility here and the payloads here (Put it in a way so that default_config and main.py in the same folder), it supports several more than the listed SoCs, one way to figure out is to find out is to run the bypass utility with -t and try to find your hardware code on the default config file

NasiGorengBurung commented 1 month ago

Follow the default config and main py stuff. It will expand mtk bypass soc support lists and it might support your soc

NasiGorengBurung commented 1 month ago

Also "figure out" part too

NasiGorengBurung commented 1 month ago

Found it, this should help you https://web.archive.org/web/20240130100627/https://github.com/bkerler/mtkclient/issues/52

sadly it didnt work for me

758

i think i have found my problem #830 but my question is how do i get da and auth file for this device?

For da: https://androidmtk.com/mediatek-da-file

For auth. Follow steps for mtk bypass i said, after do step. Do on mtk bypass

NasiGorengBurung commented 1 month ago

Maybe run mtkclient with da file after auth step

r4db commented 1 month ago

i tried mtk bypass. It didnt work it just said "waiting for device" even after plugging it in

In mtk thread, xda server. Some people said...

try running mtkclient and see if it runs successfully. If it's stuck or gives out an error even if you've successfully downloaded all dependencies and run BROM properly. You can get the bypass utility here and the payloads here (Put it in a way so that default_config and main.py in the same folder), it supports several more than the listed SoCs, one way to figure out is to find out is to run the bypass utility with -t and try to find your hardware code on the default config file

thanks will try when i have time

NasiGorengBurung commented 1 month ago

You know, i decided to help you further, because i know how to feel to have hard time to save phone from being bricked

r4db commented 1 month ago

Follow the default config and main py stuff. It will expand mtk bypass soc support lists and it might support your soc

i did all the steps you mentioned but same thing "waiting for device" even though my cpu is supported mt 6853 i also tried to use those other apps like auth bypass but with gui it detects the device but with error "slaa/daa error" or something like that image image image on device manager it shows up as this image image

i also tried mtk bypass on linux same problem

NasiGorengBurung commented 1 month ago

Well then, sorry to break it to you. I have similar problem as yours, and i have no clue how to solve that

Do not worry. There are another chance, in XDA server, there are thread that help you to get phone from bricked, and there's helper that's familiar with MediaTek https://discord.com/invite/xda-422814981520621569

r4db commented 1 month ago

where do i get loader and auth? also can i use testpoint to enter brom? @bkerler

bkerler commented 1 month ago

As the readme already states, fused devices with V6 aren't supported right now.

bkerler commented 1 month ago

As oppo devices are total crap, even if you have auth, you cannot write anything without special permission/token.

NasiGorengBurung commented 1 month ago

As oppo devices are total crap, even if you have auth, you cannot write anything without special permission/token.

I agree, but what fused mean?