Needhelp with this issue. After installing this driver and ready to flash phone the connection of usb keep disconnecting thus preventing me from flashing. I'm using latest windows 10 anniversary update. Help please!
I had a same problem with disconnecting. Phone was turned off - when I connected to PC, I heard connecting sound - also see usb drivers - but only for 2 seconds, after that, disconnecting sound and nothing.
I figure out this myself accidentally and hope it help others. The problem arise from the ROM itself. So no matter what you do to connect the phone it will disconnect itself and making impossible for you to flash.
What you need to do is simple but dangerous. Instead of check "Download Only" option in SP Flash Tools Check "Download Only + Flash". What you doing here is you brick the phone in order to flash it. Sound crazy right! But this option will wipe out all error in rom so you will be able to flash it later.
Now the phone is brick :(, when you put the battery back the phone wont even start to boot. Just blank screen. You also cannot charge the phone. Remove the battery and try connect it again this time check "Download Only" in SP Flash Tools. This will install back fresh ROM and also flash the phone. Wait the flashing phone. Disconnect and voil!
I search everywhere including forum and all for days but no avail. Lots of suggestion but no solution. So its really easy solution now I'm enjoying my Lenovo S920 with original firmware just like newly bought android. Remember this is not a complete guide and only as reference.
MT65xx Preloader Drivers are very important and useful for MediaTek phone users. Here you can download MT65xx Preloader Drivers for Windows 7/8/10/11. And also you will get to know about its installation procedure. So if you are new to drivers, this guide is going to help you.
These are the Preloader Drivers, also referred to as VCOM Drivers. These are used to connect MediaTek phones with PC even without any battery inside the phone. It let the PC know that a MediaTek phone is connected in switch-off mode. So it is just like the other USB Drivers, but it works in a different case.
It allows windows PC to detect MediaTek phones on various flash tools (like SP Flash Tool) to flash files or make other changes. It comes in handy when a MediaTek phone is in a boot loop or stuck at the boot logo, then you can easily connect your phone to pc, and it will be detected.
The steps will be the same for all the versions of Windows (Vista, XP, 7, 8, 10, 11). And after installation, a restart is not required, but I will recommend a restart. Remember that this driver is only for MediaTek phones, not Snapdragon, Exynos, or Kirin.
Now you can use the driver to connect smartphones based on the MediaTek MT65xx chipset. Download SP Flash Tool on your windows and flash firmware, custom recovery, custom ROM or other zip files on your phone. If you have any questions regarding flashing, drivers, tools, and root, you can ask in the comment section. You can also use Facebook to ask questions, we will reply in a moment.
MediaTek Inc. is one of the largest smartphone chip makers in the world. At Oxygen Forensics we have implemented data extraction from Android devices based on MTK chipsets in Oxygen Forensic Detective.
This type of extraction method is based on a low-level proprietary protocol which was designed for firmware updates and repair of MTK-based devices, allowing data extraction from password-locked devices. The majority of MTK chipsets is currently supported in Oxygen Forensic Detective.
To put the device in preloader mode, turn off the device and connect it via USB. A virtual MediaTek COM port will be exposed in the system for one second. If nothing is done during this period, the device will switch back to charging mode. However, if the handshake procedure is initiated during this time, users can continue to communicate with the MediaTek device using the special protocol.
On some devices, investigators will need to press one or both volume buttons on the turned off device and then connect the device via USB in order to enter the special mode. Only after that, the device will switch to preloader or BROM mode.
For optimal work in this mode, we recommend to install the driver included into the product package. If MTK driver is installed correctly, the extraction process will continue. Otherwise, you will have to reinstall the driver in the system or find the correct driver for this device and repeat the process.
DA mode provides a high-level API of interaction with the device and supports commands that can be used to read device physical image. The software uses the universal DA loader. But some devices require a vendor-signed DA file to operate. For such devices to be supported in Oxygen Forensic Detective, upload the corresponding third-party DA file into the software.
Oxygen Forensic Detective also uses the DAA disabling technique, which allows to bypass the DA file signature check and use the universal DA file. DAA disabling is implemented via a vulnerability in BROM. During exploitation of this vulnerability, all processes are run in RAM. Therefore, this operation is safe, since the device returns to its original state after reboot.
Encryption of user data is enabled on Android devices by default and cannot be disabled. Starting with Android 10, file-based encryption (FBE) is used for data encryption. On earlier Android versions, full disk encryption (FDE) was used. Encryption process uses the hardware key, if the chipset supports that.
If MTK device memory is encrypted, the contents of the extracted physical image is encrypted as well. In order to decrypt it, we need to know the hardware key and lock screen password (if it was set), as well as the decryption algorithm. A part of the algorithm is common for all Android devices, but the other part is implemented within the Trusted Execution Environment (TEE) and varies for different TEE OSs.
MTK devices utilize several different TEE systems such as Kinibi, Trusty, Microtrust, T6, RSEE, etc. due to the abundance of vendors releasing their devices on MTK chipsets. The TEE OS implementations on different MTK chipsets have their own customizations and version history. All these factors lead to a large variety of encryption algorithms, albeit somewhat similar, but with nuances critical for data decryption process.
It is worth noting that some lower-level MTK devices do not implement or skip a number of modules responsible for cryptography at the hardware level. Thus, there are MTK devices with unencrypted user data, as well as MTK devices that use only software-based encryption. Prior to Android 8, this was very common.
Hardware keys can be extracted from the device via a special exploit that is implemented in our software. During exploitation of the vulnerability, all processes are run in RAM, meaning this action is safe since the device returns to its original state after reboot.
If the chipset is not in the list of supported chipsets, the investigator can attempt to extract the hardware keys which is typically successful. However, in this case there is a higher probability of issues arising during the password bruteforce and/or data decryption phase.
6. The exploit designed for extraction of hardware keys will be launched after the encryption type check is complete. In some cases, users might be asked to reconnect the device in accordance with the instructions.
Some Xiaomi devices implement proprietary Second Space technology. Practically, this feature creates another user space with its own set of applications and data, as well as a separate password. In this case, two passwords are required to decrypt all the data: the primary user one and the one from the Second Space. The software provides ability to bruteforce both passwords if they are unknown.
It is possible to import the image without entering the password; however, in this case most of the user data will not be available. On devices with file based encryption, BFU data can be extracted along with some media files.
Some MediaTek devices use F2FS instead of EXT as their file system, which has been designed to be mostly used on SSDs. Thus, the image analysis can take much longer time. For devices with large memory capacity, the difference can be several hours versus several minutes.
At Oxygen Forensics our solution is updated multiple times every year. We offer training courses and webinars that will help you learn the ins and outs of Oxygen Forensic Detective and stay up to date on new features and tools needed for your investigation. Returning customer? Sign up for our newsletter to stay in the loop.
3a8082e126