Wellcome to Tehnotone.com!
Please disable your AdBlock before entering.

Published on  Last updated on September 23, 2016
MediaTek Chipset MT6589 MT6589M MT6589T

Example of a MediaTek Chipset on a PCB

The following archive contains MTK interface drivers (32 & 64 bit) for Windows XP, Windows Vista, Windows 7 & Windows 8:

Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Microsoft Windows 10 MTK Drivers (32 & 64 bit) + Drivers installation tutorial
Download SP Flash Tool v3 & v5 – Latest versions

Let’s Prepare our bricked MediaTek MT65xx device for a new beginning

This procedure apples to your  MT65xx device if:

A. The MT65xx device starts but hangs at manufacturer logo or somewhere else.
B. The MT65xx device restarts continuously after a specific number of seconds.
C. You want to update the MT65xx device with another firmware, or a specific firmware component like “recovery“.

1. Shut down your MT65xx device and wait until it vibrates and all lights are off.
2. Remove the back cover of the device and take out the battery pack from the device.

During the interventions that I’ll describe on this page, every time you connect your MT65xx device to your PC you will need to make sure that it is turned off, or, if it’s possible, it has the battery pack taken out. The procedures described below will work by putting your MT65xx device in Download Mode, a state in which the Flash Memory can be formatted and reprogrammed.

The flash memory holds all the binary information required for the MT65xx device to boot up and function. (The flash memory also contains the internal memory of the device, holding up drivers, applications and other types of data in memory structures like ROM (Read Only Memory) & NVRAM (Non-Volatile Random Access Memory). The flash memory of MT65xx devices with an unlocked boot loader can be reprogrammed in a way that a software (SP Flash ToolSmartPhone Flash Tool for example) can write data to it between specific points (also known as memory blocks). Example: between 0x0 and 0x600000. These points in memory are contained in a file whose name includes “scatter”, file which must be loaded in the SP Flash Tool. Based on this file, the software will then look for the required components in the same directory in which the “scatter” file resides, listing them afterwards.

If you can not remove the battery from  your device (if it’s a tablet for example) you only need to shut down the device in a normal manner, or, if that’s not possible, do a forced shut down by holding down the power button for about 10 seconds, until all lights are off. (I know that  my own MediaTek 6589 device – Acer Liquid E2 Duo Dual SIM, has a LED indicator near the top, but other devices for which this guide could apply might not have such an indicator).

3. Extract “MT65xx Drivers” folder from the archive.
4. Open up the Device Manager window on your Windows PC.
5. Connect your device to the PC via the USB cable keeping an eye on the Device Manager window.

The notification LED on the MT65xx device (if there is one) must light up in a deep blue color as soon as you connect it to the PC. If your device was alive before you removed the battery or shut it down (I mean not bricked), In the Device Manager window  the unknown device “MT65xx Preloader” should show up.

Normally You’ve only got about 5 seconds to right-click the unknown device in the Device Manager window and then to update the driver. After 5 seconds the MT65xx device will automatically close the communication interface and the “MT65xx Preloader” will be gone until next time you connect your MT65xx device to the PC.

6. Right-click the “MT65xx Preloader” from the Device Manager window and click “Update driver software”. Use the second option to manually install the driver by indicating the driver directory.
7. Browse to the extracted folder “MT65xx Drivers” and select the folder corresponding to the version of Microsoft Windows that you are running. Click “Next” and the driver should now be installing…

The MT65xx device will keep the communication interface alive longer (as long as required) if it detects a data flow from the PC (Example: from SP Flash Tool). That is of course if you got the driver named “MediaTek PreLoader USB VCOM Port (COMx)  installed and showing up under “Ports (COM & LPT) in the Device Manager window, as soon as you connect your device to the PC. This also means that the device driver that you have installed at Step 7 was correctly recognized. In normal circumstances, with the battery pack inside, the Integrated Circuit within the MT65xx device will begin to charge the battery after 5 seconds.

What if our MT65xx device has got the wrong preloader? Here we go…

For the record, I will consider the MT65xx device as being recoverable through this procedure in that case in which there still is an interaction with the Device Manager on the Windows PC when you connect the MT65xx device without the battery pack if possible, via USB and the blue light turns ON (if the notification LED exists).

This procedure apples to your MT65xx device if:

A. The MT65xx device is not starting at all.
B. The MT65xx device is starting/restarting (vibrates) but the screen remains black.
C. The SP Flash Tool reports an error that prevents the successful download of the firmware files to your MT65xx device because your “PRELOADER” firmware component that you are trying to download is bad or corrupt.

BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)

SP Flash Tool Error: BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)

A, B and C are cases in which most likely you previously downloaded a bad or corrupt “PRELOADER” firmware component to your MT65xx device via SP Flash Tool. To get the right idea you might want to read below:

There is the situation in which if you download a new firmware to your MT65xx device that has either a bad, incompatible or corrupt “PRELOADER” component. The SP Flash Tool will report the download as being successful but your MT65xx device will not start afterwards and neither will the SP Flash Tool be able to download the firmware components again because the normal “MediaTek PreLoader” communication interface will not start unless the SP Flash Tool will first send a good “PRELOADER” firmware component.

The “PRELOADER” firmware component has the required attributes to allow the MT65xx device to communicate with the PC trough the normal “MediaTek PreLoader” download interface, trough which the SP Flash Tool is capable to send the rest of the firmware components to the  Flash Memory of the MT65xx device. If this “PRELOADER” firmware component was previously downloaded to the Flash Memory of the MT65xx device but it was incorrect or corrupt, the MT65xx device will use a special, low-layer interface, to communicate with the PC. This interface is non-removable and is the only interface that allow us to change the “PRELOADER”  firmware component if intended.

The SP Flash Tool can also handle this low-layer interface. However, the SP Flash Tool can only use this low-layer download interface to replace the “PRELOADER” component of the firmware. Afterwards, with the correct “PRELOADER” firmware component, the MT65xx device will instantly reinitialize its related Integrated Circuits, switching to the normal “MediaTek PreLoader” download interface that will take in the rest of the firmware components sent by SP Flash Tool. Your device will NOT remain dead if you follow this trough.

This low-layer interface is there to save the device no-matter how worst it got bricked. You only need the right driver to start the recovery process of the Flash Memory. The proper driver for this low-layer download interface is also located in “MT65xx Drivers” folder. The MT65xx device will keep the low-layer download interface alive for about one minute. During this time you need to update or install the driver.

In this case, initially, the PC could show an “Unknown Device” in Device Manager window, then it might automatically install a driver from Windows Update, most likely THE WRONG DRIVER. If this is the case, you must then manually force-update the driver for the low-layer download interface of the MT65xx device.

In my case, Microsoft Windows 7 64 bit wrongly installed the low-layer download interface of my MT65xx device as a “Alcatel Single RNDIS Interface” under “Network adapters“. The device is sometimes with an exclamation mark and it disconnects regularly being unable to start. That was because my PC was set to automatically search for drivers at Windows Update for all the new connected devices, so I expected this to happen. A simple method to avoid this scenario is to disconnect the PC from the internet before connecting the MT65xx device to that PC via USB. Otherwise you might have a hard time finding the device in the Device Manager window. depending upon the exact model of your MT65xx device and the operating system on your PC.

But if the bad has happened I had to right-click the suspicious device, select “Update driver software“, then browse the extracted “MT65xx Drivers” folder. In my case, in which a wrong driver was already installed for the low-layer download interface of my MT65xx device, I had to select the second option, to manually browse for the driver (Select it from a list from my computer) so that I can force-replace the wrong driver found automatically by Windows Update. So you must do if this is the case. Also you might select “Show all devices” from the device type selection window.

I clicked “Have Disk…” and browse to the “MT65xx Drivers” folder where I opened the one corresponding to my operating system, selected MDMCPQ.INF and hit “Open” then “OK“. In the window “MTK USB Port” was now shown as being installed, which is the correct low-layer download interface driver that I wanted to have.

On 64 bit operating systems you might need to confirm the unsigned driver installation and you might also do some settings in order to to allow your 64 bit operating system to use unsigned drivers like the ones provided on this page. My experience with these drivers on Microsoft Windows 7 64 bit was OK.

The point is that, when you connect the device with no battery inside or turned off and the blue light comes on, in the Device Manager Window you must have one of this two devices showing up under “Ports (COM & LPT)“:

1. The low-layer download interface – driver name: MTK USB Port (COMx)
2. The MediaTek PreLoader download interface – driver name: MediaTek PreLoader USB VCOM Port (COMx)

If you have that, you might proceed downloading the correct  firmware on your MT65xx device unsing SP Flash Tool. When you recover your MT65xx device from the state in which it has the wrong preloader, you must have both drivers mentioned above ready to establish the download link with your MT65xx device. You can look at the guide at the top side of this article to see how the MT65xx device behaves when it has the correct preloader.

If you have trouble installing a new MTK driver in your system or you see a high or unusual number beside COM Ports displayed in the Device Manager, you might want to clean the USB driver garbage in your system with USBDeview – Download USBDeview for 32 & 64 bit Windows – learn what it does and how to get rid of unwanted USB drivers and COM Port duplicates.

Copyright exceptions:
  1. Images from this webpage are not under Tehnotone.com copyrights. They might be under the copyrights of their respective owners.
  2. Downloads from this webpage are not under Tehnotone.com copyrights. They might be under the copyrights of their respective owners.
Share:
Tags:
  1. Anonymous says:

    When ever i try to install the driver it says operation failed in cmd window

  2. Anonymous says:

    Thank´s

  3. Anonymous says:

    Hi i have a Galaxy S7 Clone (MT6580) and i bricked it with Error 0xFC0 (4032) i even tried every tutorial but it didn’t worked for me. When i plug in the USB cable – the phone only reacts when i press the volume up or down button (the red led on the backside flashes when nothing is pressed and stays on if i press a button. if no program runs the phone disconnect after a few seconds. In device manager there is “MediaTek USB Port (COM5)” when its “on” , when i start SPFlash V5 , press Download / Firmware / Format the red line appears for about 45 seconds and then error 0xFC0 (4032)
    When i got it, the original Firmware seems to got a virus in it, so i decided it to update (original firmware : ALPS.L1.MP6.V2_GXQ6580.WEG.L_P62) and downloaded this one to apply with SPFlash : http://www.gsmchinamobile.com/2016/07/glaxay-a7-sm-a7100-mt6580-firmware.html
    After the worked update, phone started – but no screen (only backlight) , but sound and ADB etc (blind used) worked. I decided to flash it again and then it got that error after the update got green 🙁
    i will try to update to this : http://www.needrom.com/download/hdc-s7-sm-g930f/
    Maybe you have a idea how to fix that error and unbrick it :(((
    Greetings from germany
    Björn

  4. Anonymous says:

    thank

  5. Anonymous says:

    On 64 bit operating systems you might need to confirm the unsigned driver installation and you might also do some settings in order to to allow your 64 bit operating system to use unsigned drivers like the ones provided on this page. My experience with these drivers on Microsoft Windows 7 64 bit was OK.
    Hi, can I know what do you mean by unsigned drivers? How to do the settings? I’m only able to enter into the fastboot mode to update the driver or else it would be too short the time for me to update, haha five seconds or less is definitely not enough.
    Thank you.

    • Tehnotone.com says:

      Follow the instructions from the beginning of the following article to disable driver signature enforcement on Windows 10 64 bit: Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial
      A signed driver is a driver that uses a digital signature to authenticate that it has been certified by Microsoft to work with 64 bit Windows. This is an attempt from Microsoft to make Windows on new 64 bit PCs more stable (less Blue Screen of Death’s less hassle). But not all drivers can be sent to Microsoft to be digitally signed. That is a long process and only the large manufacturers can afford to do this for a wile and for a limited range of hardware they produce.

  6. Anonymous says:

    good work !!!

  7. Anonymous says:

    ok…

  8. Anonymous says:

    hola buenas tardes presento el error nanflash not detecte . mi teléfono blu advance 4.0 A270a, lo conecta la computadora lo formatea pero no hace mas nada. que me recomiendan por favor. gracias

  9. Anonymous says:

    good

Submit a new comment

Your email address will not be published.