Replies: 4 comments 1 reply
-
Please don't kill me I'm a newb |
Beta Was this translation helpful? Give feedback.
-
I read somewhere that erasing and then flashing everything would solve the update issue since I have rooted my phone previously. I rebooted when I erased everything I wanna kms |
Beta Was this translation helpful? Give feedback.
-
Also tried this: Preloader - Status: Waiting for PreLoader VCOM, please reconnect mobile to brom mode Port - Hint: Power off the phone before connecting. ........... Port - Hint: Power off the phone before connecting. ........... Port - Hint: Power off the phone before connecting. ........... Port - Hint: Power off the phone before connecting. ........... Port - Hint: Power off the phone before connecting. ..........Preloader |
Beta Was this translation helpful? Give feedback.
-
The issue lies here:
The binary S-version just got incremented, so if you have the latest firmware flashed the rollback check in the DA will fail. This is because the file MTK_DA_V5.bin is for the previous S-version. The da1 patch for the version check is stale, and fails to hit its mark, but you can easily fix it by editing the source code. Change Good luck! |
Beta Was this translation helpful? Give feedback.
-
I have a hard bricked TECNO POVA 5 Pro 5G, I erased every partition that needs to be flashed when flashing a stock firmware, which is a dumb thing to do that I thought this would solve the OTA issue I've been facing. I accidentally rebooted without thinking and I had erased preloader and everything. I tried this tool and it detect BROM but not preloader. Any tips to write preloader.bin?
I always get this error when typing
py mtk w preloader preloader.bin --preloader=preloader.bin --debugmode
DAXFlash - [LIB]: Error on sending parameter: DA version Anti-Rollback error (0xc0020053)
Beta Was this translation helpful? Give feedback.
All reactions