MTK erased preloader
MTK erased preloader
(06-02-2021, 02:12 PM)Haku I really need some help on this. I damaged my preloader on a BLU Vivo XL4 by running:
fastboot flash preloader preloader_k62v1_64_bsp.bin
Now all i get in SP Flash Tools is STATUS_EXT_RAM_EXCEPTION
(06-02-2021, 09:48 PM)Haku Thanks for the response. The battery is non-removable. I tried those DA files for my device already but I'm getting the same error. Before I bricked it, I managed to unlock the bootloader by running:
fastboot oem unlock
Also when I run the exploit at https://github.com/MTK-bypass/bypass_utility, it gives me following output (so I don't even think I need DA files):
[2021-02-06 12:15:03.622167] Waiting for bootrom
[2021-02-06 12:15:38.508022] Found port = COM7
[2021-02-06 12:15:38.531108] Device hw code: 0x766
[2021-02-06 12:15:38.531608] Device hw sub code: 0x8a00
[2021-02-06 12:15:38.531608] Device hw version: 0xca00
[2021-02-06 12:15:38.531608] Device sw version: 0x0
[2021-02-06 12:15:38.532111] Device secure boot: False
[2021-02-06 12:15:38.532111] Device serial link authorization: False
[2021-02-06 12:15:38.532611] Device download agent authorization: False
[2021-02-06 12:15:38.532611] Disabling watchdog timer
[2021-02-06 12:15:38.533613] Insecure device, sending payload using send_da
[2021-02-06 12:15:38.572376] Found send_dword, dumping bootrom to bootrom_766.bin
My other question is: Can that exploit (bypass_utility) be modified in such a way that it can write back the correct preloader to the device? As it seems to be the only tool that works with it ATM.
(09-09-2021, 01:54 AM)iammclovin804 Hey which preloader did you use? I'm having the same issue with an XL4.
(09-09-2021, 02:18 PM)X3non(09-09-2021, 01:54 AM)iammclovin804 Hey which preloader did you use? I'm having the same issue with an XL4.
blu vivo xl4? there's a firmware listed @ https://www.hovatek.com/forum/thread-26456.html