Preloader file in ENGROM (REDMI9) - Redmi 9 / Poco M2 Questions & Answers

Preloader file in ENGROM (REDMI9) - Redmi 9 / Poco M2 Questions & Answers

Should I uncheck the preloader file in flashing the Engineering Rom of redmi 9?

Related

GM 4G Dont work second sim after brick. Please help me!

Hi, i have GM 4G Dual. My phone was bricked, i download LUZ59F_DUOS.zip and flashed. But phone became single sim. Text in about phone: General Mobile 4G. How fix it? Please help me.
forum.one-teams.com/Konu-TOOL-HardbrickFix-General-Mobile-4G-QFIL-HardBrick-Tool
Sorry for my english, i used translator.

Just flash non-hlos.bin for dual
I've already pulled for one-team forum

nhmanas said:
Just flash non-hlos.bin for dual
I've already pulled for one-team forum
Click to expand...
Click to collapse
I flashed CM 13 Recover SW QFIL (Wileyfox Swift) for dual sim work, later i found Dual Sim QFIL Firmware (GM 4G Dual), now it is impossible to install the LUZ59F_DUOS and Dual Sim QFIL Firmware (GM 4G Dual). But CM 13 Recover SW QFIL (Wileyfox Swift) flasing successfully. I used normal and modified cable. How fix it? Please help!!!
QFIL Log:
HTML:
Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
SEARCHPATH:C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM:
rawprogram_upgrade.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:True
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM file path: C:\Users\XXX\Downloads\Compressed\SW\main\rawprogram_upgrade.xml
PATCH file path:C:\Users\XXX\Downloads\Compressed\SW\main\patch0.xml
Programmer Path:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
Image Search Path: C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM file path: C:\Users\XXX\Downloads\Compressed\SW\main\rawprogram_upgrade.xml
PATCH file path:C:\Users\XXX\Downloads\Compressed\SW\main\patch0.xml
Start Download
Program Path:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download

TigOne said:
I flashed CM 13 Recover SW QFIL (Wileyfox Swift) for dual sim work, later i found Dual Sim QFIL Firmware (GM 4G Dual), now it is impossible to install the LUZ59F_DUOS and Dual Sim QFIL Firmware (GM 4G Dual). But CM 13 Recover SW QFIL (Wileyfox Swift) flasing successfully. I used normal and modified cable. How fix it? Please help!!!
QFIL Log:
HTML:
Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
SEARCHPATH:C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM:
rawprogram_upgrade.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:True
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM file path: C:\Users\XXX\Downloads\Compressed\SW\main\rawprogram_upgrade.xml
PATCH file path:C:\Users\XXX\Downloads\Compressed\SW\main\patch0.xml
Programmer Path:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
Image Search Path: C:\Users\XXX\Downloads\Compressed\SW\main
RAWPROGRAM file path: C:\Users\XXX\Downloads\Compressed\SW\main\rawprogram_upgrade.xml
PATCH file path:C:\Users\XXX\Downloads\Compressed\SW\main\patch0.xml
Start Download
Program Path:C:\Users\XXX\Downloads\Compressed\SW\main\prog_emmc_firehose_8916.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
well pal.. I don't understand a thing.. I see that you are Turkish. PM me in Turkish. We are not allowed to use any other language but English on xda forums.

nhmanas said:
well pal.. I don't understand a thing.. I see that you are Turkish. PM me in Turkish. We are not allowed to use any other language but English on xda forums.
Click to expand...
Click to collapse
You can make a copy of the system, for the HDD RAW Copy or eMMC Raw Tool? Please share me!

TigOne said:
You can make a copy of the system, for the HDD RAW Copy or eMMC Raw Tool? Please share me!
Click to expand...
Click to collapse
the link for CM 13 Recover SW QFIL is not working, can you post it again. I have a wileyfox swift that is bricked

ZTE Axon A2016 brick

Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?

saardukar said:
Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?
Click to expand...
Click to collapse
Have you tried to go into recovery mode and install any rom from there?

Crazyhat said:
Have you tried to go into recovery mode and install any rom from there?
Click to expand...
Click to collapse
Recovery is not available. Nether fastboot or adb.

Unlocking bootloader [For all MTK devices]

Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.

Hey will this work on vivo y91i with mt6762

Is there a possibility of phone getting bricked

This is not working on Redmi Note 11t 5g

belkaliz said:
Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.
Click to expand...
Click to collapse
Will Try for unlocking FRP

belkaliz said:
Unlocking bootloader on Nokia 5.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? (Subject to OEM's)
*
* We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
*/
Requirements:
PC with Linux/Windows/MacOS.
Nokia 5.1 with any version of Android.
Installed mtkclient with offical instruction.
Straight arms.
If you using windows, installed preloader vcom driver.
Unlocking bootloader:
Open terminal (cmd) on folder with mtkclient.
Power off device.
Run command:
Code:
python mtk xflash seccfg unlock
Hold a Vol- button and connect device to PC.
Wait for the script to finish.
Enjoy unlocked bootloader.
Notes:
Data won't be wiped, but it is better to make backup.
Works on all MTK devices, except entering on BROM.
Click to expand...
Click to collapse
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.

Anonymous V said:
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.
Click to expand...
Click to collapse
the message "orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds...." is normal for bootloader unlocked mtk devices

yeah i know that but in my case it cause a boot loop, after i unlock the bootloader and boot my phone because of the bootloop do you know how to fix it?

$cronos_ said:
the message "orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds...." is normal for bootloader unlocked mtk devices
Click to expand...
Click to collapse
yeah i know that but in my case it cause a boot loop, after i unlock the bootloader and boot my phone because of the bootloop do you know how to fix it?

Anonymous V said:
i tried it but it says
orange state
your device has been unlocked and cannot be trusted
booting in 5 seconds....
then after that got i got a bootloop forcing me to relock it again and flash stock rom to fix my phone.
Click to expand...
Click to collapse
You just have to go to recovery mode and wipe all data and then just reboot the phone will boot normally

St4rh4ck3r said:
You just have to go to recovery mode and wipe all data and then just reboot the phone will boot normally
Click to expand...
Click to collapse
thanks for the answer !but i manage to unlock it without losing any data

Seems not working for vivo y72 5g, any help?
The command python mtk xflash seccfg unlock seems not to be working for mtk client also

Incomtus said:
Seems not working for vivo y72 5g, any help?
The command python mtk xflash seccfg unlock seems not to be working for mtk client also
Click to expand...
Click to collapse
Did you try the other comand??
This command -----------> python mtk da seccfg unlock
Because we have the same problen and this one solves it try it!

Anonymous V said:
Did you try the other comand??
This command -----------> python mtk da seccfg unlock
Because we have the same problen and this one solves it try it!
Click to expand...
Click to collapse
I already tried it, mtk client ask to plug the phone, I do it, it detects it, BUT two possibilities are happening every time I tried : it says the phone has been unplugged or it remains stuck on "trying kamakiri2" and nothing happens....
I installed mtk client again i tried again and it does the same. Sometimea it gets stuck on "jumping on 0x0"

Incomtus said:
I already tried it, mtk client ask to plug the phone, I do it, it detects it, BUT two possibilities are happening every time I tried : it says the phone has been unplugged or it remains stuck on "trying kamakiri2" and nothing happens....
I installed mtk client again i tried again and it does the same. Sometimea it gets stuck on "jumping on 0x0"
Click to expand...
Click to collapse
In developers option did you turn on the oem unlock option?? The error (trying kamakiri2) hhappened to me what i did is i reinstalled everything from python to preloader driver

Anonymous V said:
In developers option did you turn on the oem unlock option?? The error (trying kamakiri2) hhappened to me what i did is i reinstalled everything from python to preloader driver
Click to expand...
Click to collapse
Yes oem unlock is activated. okay you think that comes from python preloader driver? Can you give a little more details? It will be very nice

Incomtus said:
Yes oem unlock is activated. okay you think that comes from python preloader driver? Can you give a little more details? It will be very nice
Click to expand...
Click to collapse
Im not quite sure why but i think kamakiri2 uses python to operate the whole proccess thats why if the python is not working the whole process will not work too, while in preloader(its a substitute of fastboot)helps the mtk client connect or communicate with ur phone thats why if the drivers is corrupted or something wrong happened mtk client wont work correctly, btw while you are unlocking your bootloader did you see something like (DA failed to send or offset error)?

Anonymous V said:
Im not quite sure why but i think kamakiri2 uses python to operate the whole proccess thats why if the python is not working the whole process will not work too, while in preloader(its a substitute of fastboot)helps the mtk client connect or communicate with ur phone thats why if the drivers is corrupted or something wrong happened mtk client wont work correctly, btw while you are unlocking your bootloader did you see something like (DA failed to send or offset error)?
Click to expand...
Click to collapse
I am not sure bro, I will try again in the evening

Incomtus said:
I am not sure bro, I will try again in the evening
Click to expand...
Click to collapse
Ok bro and to be sure pls put your mtk client log, in here as well sowe can all se the problem.

Anonymous V said:
Ok bro and to be sure pls put your mtk client log, in here as well sowe can all se the problem.
Click to expand...
Click to collapse
Here is the logs
the first is when i try without touching any hw bouton :
Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
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: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
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
Mtk - We're not in bootrom, trying to crash da...
PLTools - Crashing da...
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
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
second with all butons (just detect and lost it)
..Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
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: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
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
PLTools - Crashing da...
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
Last try when i pushed vol- and on/off button got stuck on kamakiri2:
Port - Device detected
Preloader - CPU: MT6833(Dimensity 700 5G k6833)
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: 0x73
Preloader - Disabling Watchdog...
Preloader - HW code: 0x989
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
PLTools - Loading payload from mt6833_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
<

[GUIDE] [MTK] How to use MTKClient and set it up!

So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk)
I am writing this guide especially for the RM6785 community.
This tool is very useful, you can unlock almost any mediatek device using it (brand won't matter), you can write partitions, read partitions, and even erase partitions.
This tool can also get you out of any kind of brick!
Thanks to bkerler for making such an amazing tool!
How to use it?
Well first of all, I will talk about how to install it inside windows, because most of the users here are most likely using windows.
Download the mtkclient folder from here: https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Extract it, and open it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now it's time to download python.
If you are on windows 11/10, you can download Python directly from the microsoft store, and I recommend you to do it from there.
If you are on windows 8.1 or lower, you will have to download it from the web.
After installing python is complete.
Open the command prompt inside the mtkclient-main folder.
connect to the internet
and type:
pip3 install -r requirements.txt
and wait for it to install completely.
This will basically set up mtkclient to perform every command.
(ignore this warning)
So after this command is done, you need to install usbdk.
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
After you install usbdk, just restart your PC.
So your mtkclient setup is finished now!
Now you can basically do anything with it.
Let me tell you how it works:
For example, if you want to flash something into a partition, you do:
python mtk w *partitionname* *filename*
the w indicates "write"
so for example if i want to flash, lets say boot img.
python mtk w boot *location of the boot img*
in simple words:
python mtk w boot boot.img
to pull a partition from your device:
python mtk r *partitionname* *filename*
the r indicates "read"
you can pull the image as any name that you'd like"
example:
python mtk r vbmeta realme6vbmeta.img
to erase partitions:
python mtk e *partition*
the e indicates "erase
so for example i want to clear my userdata partition
python mtk e userdata
you can also write,flash,erase multiple partitions at once.
for example:
python mtk w boot,vbmeta boot.img,vbmeta.img
python mtk r dtbo,boot dtbo.img,boot.img
python mtk e metadata,userdata
you can also unlock the bootloader through it:
python mtk da seccfg unlock
so to actually begin the flashing/reading/erasing process, enter the command.
power off your device
hold both of the volume buttons, and quickly connect usb (do not leave the volume buttons until the command is done)
So that is basically how you use it, thanks for reading!
I will make a version for linux users soon!

hey i am getting handshake failed error, not sure how to fix this.

Sidharth09 said:
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk)
I am writing this guide especially for the RM6785 community.
This tool is very useful, you can unlock almost any mediatek device using it (brand won't matter), you can write partitions, read partitions, and even erase partitions.
This tool can also get you out of any kind of brick!
Thanks to bkerler for making such an amazing tool!
How to use it?
Well first of all, I will talk about how to install it inside windows, because most of the users here are most likely using windows.
Download the mtkclient folder from here: https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Extract it, and open it.
View attachment 5741507
Now it's time to download python.
If you are on windows 11/10, you can download Python directly from the microsoft store, and I recommend you to do it from there.
If you are on windows 8.1 or lower, you will have to download it from the web.
After installing python is complete.
Open the command prompt inside the mtkclient-main folder.
connect to the internet
and type:
pip3 install -r requirements.txt
View attachment 5741509
and wait for it to install completely.
This will basically set up mtkclient to perform every command.
View attachment 5741511
(ignore this warning)
So after this command is done, you need to install usbdk.
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
After you install usbdk, just restart your PC.
So your mtkclient setup is finished now!
Now you can basically do anything with it.
Let me tell you how it works:
For example, if you want to flash something into a partition, you do:
python mtk w *partitionname* *filename*
the w indicates "write"
so for example if i want to flash, lets say boot img.
python mtk w boot *location of the boot img*
in simple words:
python mtk w boot boot.img
to pull a partition from your device:
python mtk r *partitionname* *filename*
the r indicates "read"
you can pull the image as any name that you'd like"
example:
python mtk r vbmeta realme6vbmeta.img
to erase partitions:
python mtk e *partition*
the e indicates "erase
so for example i want to clear my userdata partition
python mtk e userdata
you can also write,flash,erase multiple partitions at once.
for example:
python mtk w boot,vbmeta boot.img,vbmeta.img
python mtk r dtbo,boot dtbo.img,boot.img
python mtk e metadata,userdata
you can also unlock the bootloader through it:
python mtk da seccfg unlock
so to actually begin the flashing/reading/erasing process, enter the command.
power off your device
hold both of the volume buttons, and quickly connect usb (do not leave the volume buttons until the command is done)
So that is basically how you use it, thanks for reading!
I will make a version for linux users soon!
Click to expand...
Click to collapse
Hello have you made the Linux version?

Thank you for this guide, I have encountered an error on Tecno spark 8C(kg5j) when trying either of the commands in ubuntu.
Here is an output of the error.
-----
DAXFlash - [LIB]: xread error: unpack requires a buffer of 12 bytes
DAXFlash
DAXFlash - [LIB]: Error jumping to DA: -1
-----

Johnhek said:
handshake failed error
Click to expand...
Click to collapse
Check this out: https://github.com/bkerler/mtkclient/issues/52

Fair warning, there are a TON of multiple GB dependencies to make this work. I'm seriously starting to wonder if trying to un brick my $1,800 device is even worth the trouble.
I have an RFinder B1+ with a MTK 6765 chipset. It has external batteries only and boot loops when one is attached due to a bad lk.img flash. The device does show up brieflu in Windows task manager as a MediaTek COM port when I plug in a USB cable with no battery attached.
Should I plug in the battery first or try to run mtkclient without it?

I was using "wl" command (write list: write partitions from directory to flash) and I had a very dumb issue:
I moved the partition images to the mtkclient folder and started the wl comand, but when the partitions were all copied, the comand continued checking all the subfolders looking for more partition files to write to the phone... and it "found" one: inside of the python lib folder there is a file called gpt and the command overwrited my pgpt partition with that file!
Now of course any command trying to read or write partitions crash because the pgpt partition is corrupt.
I can read sectors and indeed I have confirmed that the contents of the first sectors (that would correspond to pgpt partition) actually contains plain text from the pgt file at python lib folder.
Before this mistake, I saved the gpt table to a file and I also have gpt scatter information from my phone.
I would need help to restore the pgpt partition using the sgpt partition or using the pgt scatter information, or the gpt table copied from my phone before the deletion or any other way to restore the phone...
Someone can help me?

I Have a lg k61, I can use mtkclient but I have no fastboot. Im wondering if its posible to boot a bin without flashing it (like fastboot boot recovery.img) because I think that the only reazon I cant install a working twrp in my device is the way I flash it, directly to boot partition.
Maybe is it possible to flash the recovery to b slot, force boot from that slot, flash from twrp the zip to boot_a partition, then set a slot?

darklight_69 said:
Hi, not quite sure with the terminologies in the commands part, if i want to root /give root access to my phone which command should i use?
Click to expand...
Click to collapse
You read to your pc from your phone vía mtkclient the boot_a.bin. You then rename it to boot_a.img, then you turn on your phone, move the img to it, install magisk, patch the boot.img, move it to your pc again, rename the patched to *.bin again and flash it to your boot_a partition vía mtkclient.

Jaguar_90 said:
You read to your pc from your phone vía mtkclient the boot_a.bin. You then rename it to boot_a.img, then you turn on your phone, move the img to it, install magisk, patch the boot.img, move it to your pc again, rename the patched to *.bin again and flash it to your boot_a partition vía mtkclient.
Click to expand...
Click to collapse
if it's not bothering, could you please make a detailed step by step or link a post for a detailed instruction on how to exactly do what youve said? sorry i am having a hard time comprehending the steps, dont want to mess the procedure, thank you
or can i pm u instead?

darklight_69 said:
if it's not bothering, could you please make a detailed step by step or link a post for a detailed instruction on how to exactly do what youve said? sorry i am having a hard time comprehending the steps, dont want to mess the procedure, thank you
or can i pm u instead?
Click to expand...
Click to collapse
Here is a more detail steps.
You need to find out if the Phone is using AB slot or not. For AB slot partitions, you need to know which slot is active and flash accordingly.
Use Mtkclientand to copy the boot_a.bin.
For AB slot: python mtk r boot_a boot_a.bin
For AB slot: python mtk r boot_b boot_b.bin
For single slot: python mtk r boot boot.bin
You rename it to boot_a.img
Copy the boot_a.img to phone's internal storage.
Install Magisk on the phone.
Open Magisk app.
Click the Install button .
Select the patch the image file option.
After you patched boot_a.img, copy the patched boot_a.img to the PC.
Rename the patched boot_a.img to boot_a.bin.
Use MTKClient to flash it to the boot_a partition.
For AB slot: python mtk w boot boot.bin
For AB slot: python mtk w boot_a boot_a.bin
For single slot: python mtk w boot_b boot_b.bin

edited this instead sicne i cant delte this reply, please ignore this one

i want to ask some questions here in advance after reading the entire process so i can reduce the unnecessary replies from me lol
magi44ken said:
You need to find out if the Phone is using AB slot or not. For AB slot partitions, you need to know which slot is active and flash accordingly.
Click to expand...
Click to collapse
-my phone is using a/b slot and is currently on B slot
magi44ken said:
Use Mtkclientand to copy the boot_a.bin.
For AB slot: python mtk r boot boot.bin
For AB slot: python mtk r boot_a boot_a.bin
Click to expand...
Click to collapse
do i need to run all of them one by one?
and in 2nd command's case, sicne i'm currently in slot b should i rename "boot_a | boot_a.bin" to "boot_b | boot_b.bin"?
magi44ken said:
You rename it to boot_a.img
Click to expand...
Click to collapse
okay for this part its just changing the extension
magi44ken said:
Copy the boot_a.img to phone's internal storage.
Click to expand...
Click to collapse
you mean like the regular transfer when the phone is on right? XD
magi44ken said:
Install Magisk on the phone.
Open Magisk app.
Click the Install button .
Select the patch the image file option.
After you patched boot_a.img, copy the patched boot_a.img to the PC.
Rename the patched boot_a.img to boot_a.bin.
Use MTKClient to flash it to the boot_a partition.
For AB slot: python mtk w boot boot.bin
For AB slot: python mtk w boot_a boot_a.bin
For single slot: python mtk w boot_b boot_b.bin
Click to expand...
Click to collapse
well, the earlier questions will clear the confusion in this part anyways but i still got the gist of it.
also on this post, it mentioned something about vbmeta.img, do i no longer need that?

Hello, if I have a bin file (Rom1) from another device, can I read the rpmb key with mtkclient this way?

I do not understand these messages:
mtkclient-main\mtk_gui:557: DeprecationWarning: Enum value 'Qt::ApplicationAttribute.AA_EnableHighDpiScaling' is marked as deprecated, please check the documentation for more information.
QApplication.setAttribute(Qt.AA_EnableHighDpiScaling, True)
...and...
\mtkclient-main\mtk_gui:118: DeprecationWarning: Function: 'QLibraryInfo.location(QLibraryInfo.LibraryPath location)' is marked as deprecated, please check the documentation for more information.
translations_path = QLibraryInfo.location(QLibraryInfo.TranslationsPath)
When trying to flash the preloader, the execution of the command started like this:
Device detected : )
Preloader - CPU: MT6771/MT8385/MT8183/MT8666(Helio P60/P70/G80)
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: 0x788
Preloader - Target config: 0x0
Preloader - SBC enabled: False
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
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 - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 5649224A4BD6F0263F7ABC130DCE05AA
Preloader - SOC_ID: 67EB8D8456F3D36A30C5801507195F549290F216EF032600F78136D5E0D540D5
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
It is a Unihertz Titanium (UFS) that stopped responding. The previous owner tried to prepare the bottles of Gargoyle-LOS20 by deleting user data, cache and system. I would like to help him and save the device for him.
I would like to use the graphical interface of mtkclient. But unfortunately the tool does not load the files from the unpacked stock ROM...where do I have to put the files in the mtkclient-main directory?

how come your preloader gets detected? mine only shows up for 1 sec in device manager
Medionato said:
I do not understand these messages:
mtkclient-main\mtk_gui:557: DeprecationWarning: Enum value 'Qt::ApplicationAttribute.AA_EnableHighDpiScaling' is marked as deprecated, please check the documentation for more information.
QApplication.setAttribute(Qt.AA_EnableHighDpiScaling, True)
...and...
\mtkclient-main\mtk_gui:118: DeprecationWarning: Function: 'QLibraryInfo.location(QLibraryInfo.LibraryPath location)' is marked as deprecated, please check the documentation for more information.
translations_path = QLibraryInfo.location(QLibraryInfo.TranslationsPath)
When trying to flash the preloader, the execution of the command started like this:
Device detected : )
Preloader - CPU: MT6771/MT8385/MT8183/MT8666(Helio P60/P70/G80)
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: 0x788
Preloader - Target config: 0x0
Preloader - SBC enabled: False
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
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 - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 5649224A4BD6F0263F7ABC130DCE05AA
Preloader - SOC_ID: 67EB8D8456F3D36A30C5801507195F549290F216EF032600F78136D5E0D540D5
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
It is a Unihertz Titanium (UFS) that stopped responding. The previous owner tried to prepare the bottles of Gargoyle-LOS20 by deleting user data, cache and system. I would like to help him and save the device for him.
I would like to use the graphical interface of mtkclient. But unfortunately the tool does not load the files from the unpacked stock ROM...where do I have to put the files in the mtkclient-main directory?
Click to expand...
Click to collapse

I tried installing directly from here: https://github.com/bkerler/mtkclient. It works for the most part. But I would have liked to use the graphical interface, but that somehow fails. The files don't load into the selection windows and the command buttons don't respond either. Only the terminal control works. But I could not flash the preloader yet. The battery of the device doesn't seem to be charged either. I can't control this...is this possibly a hindering problem?

Medionato said:
I tried installing directly from here: https://github.com/bkerler/mtkclient. It works for the most part. But I would have liked to use the graphical interface, but that somehow fails. The files don't load into the selection windows and the command buttons don't respond either. Only the terminal control works. But I could not flash the preloader yet. The battery of the device doesn't seem to be charged either. I can't control this...is this possibly a hindering problem?
Click to expand...
Click to collapse
Which device are you using?

anybody knows how to solve this problem? i get this whenever i try to extract boot.bin
Code:
.DeviceClass
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m

DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes

I have a Xiaomi Redmi 9 (cattail) device
I am trying to use mtkclient to unbrick my device but i am getting this error:
Code:
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Here is the entire output:
Code:
MTK Flash/Exploit Client V1.6.0 (c) B.Kerler 2018-2022
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.
If it is already connected and on, hold power for 10 seconds to reset.
Port - Device detected :)
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
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: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe7
Preloader - SBC enabled: True
Preloader - SLA enabled: True
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: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: BEA9E2CD55FC2EB3794A2835E280608C
Preloader - SOC_ID: 27976D1C1A81DBCDB0FC5383E67CB00ADF62A75E37C7066C28E877FFDB8AC544
PLTools - Loading payload from mt6765_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /home/kyeboard/MIUI_FIX/mtkclient/mtkclient/payloads/mt6765_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
xflashext - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
xflashext
xflashext - [LIB]: Error on patching da1 version check...
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "get_vfy_policy" in preloader
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - DRAM config needed for : 150100434a544434
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes

Hey @LiaFourté, can you please help me?

here with the same problem

If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin

bretjoseph said:
If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin
Click to expand...
Click to collapse
didnt work

maybe write partition to boot_b or boot if you dont have a/b device

kuubichan said:
I have a Xiaomi Redmi 9 (cattail) device
I am trying to use mtkclient to unbrick my device but i am getting this error:
Code:
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Here is the entire output:
Code:
MTK Flash/Exploit Client V1.6.0 (c) B.Kerler 2018-2022
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.
If it is already connected and on, hold power for 10 seconds to reset.
Port - Device detected :)
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
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: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe7
Preloader - SBC enabled: True
Preloader - SLA enabled: True
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: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: BEA9E2CD55FC2EB3794A2835E280608C
Preloader - SOC_ID: 27976D1C1A81DBCDB0FC5383E67CB00ADF62A75E37C7066C28E877FFDB8AC544
PLTools - Loading payload from mt6765_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: /home/kyeboard/MIUI_FIX/mtkclient/mtkclient/payloads/mt6765_payload.bin
Port - Device detected :)
DA_handler - Device is protected.
DA_handler - Device is in BROM mode. Trying to dump preloader.
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2136.bin
xflashext - Patching da1 ...
Mtk - Patched "Patched loader msg" in preloader
xflashext
xflashext - [LIB]: Error on patching da1 version check...
Mtk - Patched "Patched loader msg" in preloader
Mtk - Patched "get_vfy_policy" in preloader
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - DRAM config needed for : 150100434a544434
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes
Click to expand...
Click to collapse
I can flash your device if you want to.
Let me know.

bretjoseph said:
If the devices isnt powering on you will have to dissamble so that you can remove the battery and put it back on it will power on.
Next write a boot partition using the devices preloader on your computer like like
Code:
mtk w boot_a boot.img --preloader=preloader_ki7_v7510.bin
Click to expand...
Click to collapse
From where do you get this, the one for R9a is preloader_k62v1_64_bsp

mvikrant97 said:
I can flash your device if you want to.
Let me know.
Click to expand...
Click to collapse
How? if the issue is with drivers or tool.

SubwayChamp said:
How? if the issue is with drivers or tool.
Click to expand...
Click to collapse
I'll use a paid software to flash the device.
Don't worry you don't need to pay for it.

mvikrant97 said:
I'll use a paid software to flash the device.
Don't worry you don't need to pay for it.
Click to expand...
Click to collapse
Good, and how we can do?, I have all the firmware for Redmi 9a, but I can´t get it to work as of now.

SubwayChamp said:
From where do you get this, the one for R9a is preloader_k62v1_64_bsp
Click to expand...
Click to collapse
try doing a boot.img dump it should also download the preloader when it fetches the boot.img in the folder where you dump

bretjoseph said:
try doing a boot.img dump it should also download the preloader when it fetches the boot.img in the folder where you dump
Click to expand...
Click to collapse
Thanks for replying, I´m not getting to work the mtk-client, it´s keeping throwing errors like DAXFlash - [LIB]: Error on sending DA, so I thought that the other way around could solve it, I could flash nor read any partition. It worked perfectly for my previous devices though.

SubwayChamp said:
Thanks for replying, I´m not getting to work the mtk-client, it´s keeping throwing errors like DAXFlash - [LIB]: Error on sending DA, so I thought that the other way around could solve it, flash nor read any partition. It worked perfectly for my previous devices though.
Click to expand...
Click to collapse
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.

Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..

Ank Sak said:
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.
Click to expand...
Click to collapse
Ank Sak said:
Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..
Click to expand...
Click to collapse
which phone is it?

mvikrant97 said:
which phone is it?
Click to expand...
Click to collapse
Lenevo K8 note , mtk6797 mediatek cpu

Ank Sak said:
I reached that in mtk client when my device went through smack down!
&& Sp flash tool couldn't get through sending DA, I went to shop , they couldn't do anything.. told me motherboard is dead
Have tried the battery removing part. No use.
Click to expand...
Click to collapse
Thanks, in SPFT it throws "EXT_RAM_EXCEPTION" error.
Ank Sak said:
Maybe GitHub has a solution , people are talking about passing the preloader , idk if it works..
Click to expand...
Click to collapse
Maybe, It´s possible that the preloader is the culprit, probably the preloader is corrupt.
But the funniest is that some days ago, with those errors, I taken to a service center, with Unlock tool, without the need to do nothing more than pressing both volume buttons (device off) it started to flash, and solved it, I re-bricked it by flashing the firmware (the latest), it´s suppose to not cause damage but it bricked. So the eMMC is not damaged.

SubwayChamp said:
Thanks, in SPFT it throws "EXT_RAM_EXCEPTION" error.
Maybe, It´s possible that the preloader is the culprit, probably the preloader is corrupt.
But the funniest is that some days ago, with those errors, I taken to a service center, with Unlock tool, without the need to do nothing more than pressing both volume buttons (device off) it started to flash, and solved it, I re-bricked it by flashing the firmware (the latest), it´s suppose to not cause damage but it bricked. So the eMMC is not damaged.
Click to expand...
Click to collapse
service center don't use unlock tool but third party repair shop does

mvikrant97 said:
service center don't use unlock tool but third party repair shop does
Click to expand...
Click to collapse
A Service Center can be authorized or non authorized. Specialization and/or segmentation in the matter/product is what the Marketing inclines this or that name to give as proper, and client consider correct both. Where I live, there are a lot of Official Repair Shops along the country, they´re called too, Service Center/Repair Center, same way, there are a lot of Service Center of a specific product, this is where plays a role the segmentation and specialization. Just to add, that some large enterprises have both department in the hierarchy.

Database Develop

welcome