1. If there are firmware for installing from a modified recovery (CWM or TWRP) for your device and your goal is to flash it, but it becomes necessary to flash the modem mode image through the flasher, then in the case of mtk you often do not have to understand the details of the firmware firmware through SP Flashtool, you only need to readinstructions on the firmware of the modified recovery without using the program-flasher.
2. If you still need to work with the flasher, be sure to check out thethese recommendationsbefore you start work.
3. Always copy the folder with the flasher and firmware to the root of the system disk and work from it, because This often helps to avoid certain problems.
4. For beginners, it is recommended to automatically install the driver for firmware via the bat-file or via Driver_Auto_Installer_EXE, look for these packages withmarked under spoiler with drivers and utilities and also don't forget that before installing drivers on windows 8-10 you need disable driver signature verification . More experienced users can practice manual driver installation for firmware .
5. How without harm to test the performance of the driver / program-flasher and get backup of stock firmware in one bottle? We read firstCreating a Rom-backup (FULL BACKUP without user data)" , and thenthis post.
6. Explanation of the drivers, if you see the "Unknown Device"
7. Be sure to read the list "Useful literature"because your question may not fit the format of the topic and the answer may lie elsewhere.

• Not a secret that in different batches kitayfonov sometimes change hardware components that do not work correctly with firmware for similar devices with the previous game, certainly a non-working phone you do not get, but the software provided by the manufacturer to retailers often turns out to be "the most recent "and after the new firmware version of the device software designed for older revisions apparatus, the user runs the risk of a partially non-working phone. To avoid this very strongly recommended to make a complete device firmware rom-backup phone!
  
• Applies to phones on the processor MT6575 and MT6577: You need to sew preloader and dsp_bl only in the case of a brick rise! In all other regular updates and flashing NEVER, do not put these checkboxes in the SP Flash Tool and DO NOT include formatting! You may have problems with which you will not cope at home or it will be difficult to do it. The mindless flashing of these sections is absolutely useless and very risky, especially on the platforms MT6575 and MT6577.
  
• Regarding other MTK phones when flashing devices via SP_Flash_Tool, do not sew the preloader file unless absolutely necessary and DO NOT enable formatting.
  
• The logs of the program SP_Flash_Tool are stored along the path:C: \ ProgramData \ SP_FT_Logs \ "Date folder" \ "Log files" , and also they can be opened through the menu of the USB flash drive Help ->Open logs folder .
  
• Recommendations for connecting the device for firmware
  
• Ports for normal and emergency firmware using SPFT
  
• Translation help (help) on the SP Flash Tool
  
• Description of SP Flash Tool firmware modes

Disabling signature verification on Windows 8 is done like this. :

1. Win + I ->Change computer settings ->Are common ->Special download options ->Reload now.
   
2. When you turn off, click Diagnose ->Extra options ->Boot Parameters ->Reboot.
   
3. After the menu appears, select "Disable mandatory driver signature verification".
   
4. Next is installing drivers according to the instructions.
   

Disabling signature verification on Windows 8.1 is done like this:

1. Win + I ->Options ->Change computer settings ->Upgrade and Repair ->Recovery ->Reload now.
   
2. When you turn off, click Diagnose ->Extra options ->Boot Parameters ->Reboot.
   
3. After the menu appears, press F7 and wait for the computer to restart.
   
4. Next is installing drivers according to the instructions.
   

Disabling signature verification on Windows 10 is done like this:

1. Hold down the Windows and shift keys and hold them down.
   
2. Next Start ->Shut down ->Reboot
   
3. Release the Windows and shift keys, and select the "Diagnostics" item.
   
4. On the next page, select "Advanced Options"
   
5. Next, go to the "boot options"
   
6. Just click “Reboot” and wait for the system to boot until the next step.
   
7. After restarting, we will be on the page for choosing the system boot option. Press the F7 key.
   
8. The computer will restart and disable driver signature verification.
   
9. Next is installing drivers according to the instructions.
   

At the time of connecting the phone to a computer you can see that there your device, see "Android Composite ABD Interface" with a yellow triangle icon, you specify the device file path to the driver, but the manager insists the devices that the drivers are all excellent and does not want to renew it is necessary to make editing the file where you want to register the PID \ VID, and so, the data must first find out from your computer. Right click on the device with a yellow triangle, properties, device ID. There will be two lines. These lines need to duplicate a file with the drivers. Then you need to re-enter the path to the driver.

Example:
android_winusb.inf - make changes in this file
% SingleAdbInterface% = USB_Install, USB \ VID_0BB4 & PID_0C01
% CompositeAdbInterface% = USB_Install, USB \ VID_0BB4 & PID_0C01 & REV_0255
% SingleAdbInterface% = USB_Install, USB \ VID_0BB4 & PID_0C01
% CompositeAdbInterface% = USB_Install, USB \ VID_0BB4 & PID_0C01 & REV_0255

vid \ pid can change, put your values

This spoiler considers the most frequent errors and their possible solutions, there is also a more complete list of errors in English in case you get an error, there is rarely a chance to find it inthe following listand another part of hints in English is presentedhere. Also, do not forget that the search on the topic works, so before asking a question, do not be lazy to drive an error code into it, because The answer to your question may be much closer than it seems.
Attention: Fresh versions of the flash driver give error numbers in HEX, here numbers are painted in the DEC number system. So do not be afraid to see for example the error number (0x7D4), just select the HEX number system in the calculator and substituting 7D4 we will see that in DEC this is our notorious 2004 error.

1. Launch the USB flash drive, in the "Download" tab, download the scatter file (if you do not have a scatter file for your device, use it from a device with the same processor), it doesn’t matter if there are no more firmware files in the folder with it (actual for the version of the driver up to 5.1628 inclusive). Remove all the checkboxes, leave a tick only on the first line - PRELOADER:
Note: If you want to use a newer version of proshivalschika version 5.1628, then tick on the Preloader section without the presence of this file in a folder with a scatter-file to put new versions proshivalschika not allow. If you have the opportunity to find a preloader it on your device model, then copy it to a folder to the scatter-file you wish to use and upload the file to a scatter-fleshtul. Next, making sure to block preloader check mark will appear, skip to step 2. If this is not possible, then proceed as follows:
but. Download this archive with my preloader [attachment = "9019071: preloader.zip"] b. Unzip the preloader.bin file to the folder where you have the scatter file you plan to use.
at. Using the Notepad ++ program, open this scatter file, find the section called Preloader and we are interested in the file_name lineRename the preloader.bin file to a file with the name from the line file_name (in the case of this example, the file preloader.bin is renamed to preloader_lcsh92_wet_jb9.bin)
e. You load your scatter file into the flasher, see the marked preloader block and go further according to the instructions.
NOTE: For this procedure fleshtulu needs only the fact of the presence of scatter files and preloader, so we can afford to take absolutely any preloader. But attention this can be done only for this stage. If suddenly you are inattention or some other reason, in the future will use this file for the firmware of your device, you'll get your hands on the brick which is extremely difficult to then raise. Therefore, after the removal of the dump from your device is not too lazy to delete or rename the file so that in the future not to forget that it is not on your device, and do not spoil yourself and others nerves. And a good tip for the future: Do not try to buy the latest version of proshivalschika, use the version that is recommended either by the manufacturer or by the Komrad your devices.

2. Determine where and how much we will read. Go to the "Memory Test" tab, remove all the checkboxes, leave only one, as shown in the screenshot - "RAM Test":

2.1. Press the Start button:

2.2. After that, connect your device off to the USB-port.

2.3. There will be a memory test, which will show, among other things, the following information (that is what we need):

Blocks with a zero size do not interest us. We leave only those that have size. In this case, we are interested in 4 blocks:

Thus, we received the names of our regions and their sizes. Starting addresses in each region will always be from scratch: 0x0

3. Now, copying the received information into a notebook, go to the "ReadBack" tab and press the "Add" button:

3.1. On the line that appears, click twice:

3.2. We set the file name (by default ROM_0) and the place where the memory block will be saved.

3.3. In the window that appears, fill in three parameters, according to previously obtained data:

For example, for the EMMC_USER region, in my case, the parameters will be as follows:
Region: EMMC_USER
Start Address: 0x0
Length: 0x3ab400000

After entering this data, click OK.

Note: in this unit, which is considered by the example of the work, there are 4 regions (you have the number of regions may be different, so reading from the regions that allows you to select fleshtul). However, this is not on all devices. Often, especially in applications in the early chipsets fleshpamyat has only one "USER" area. If your device has one region in the corresponding menu for entering block reading parameters will be no option to select the region. Also note that the calculation of the blocks, drain dump devices with the type of NAND flash memory occursdifferent method.

3.4. Disconnect the device from the computer (the device must remain off).

3.5. Press the "ReadBack" button and then connect the switched off device to the USB port, reading occurs.

3.6. After successfully reading the block, go to p.3.1 and so we read all the regions that the flashlight allows you to choose, the RPMB does not count, it is not needed.

RESULT: As a result, we get solid blocks of flash memory, the largest of which is the user region - EMMC_USER, maybe 4, 8, 16 or even 32GB (depending on the device model). If necessary, the blocks can be flashed into the device using the "Write Memory" flashlight function (see spoiler below "Instructions for using the Write Memory function"), or extract from them on the computer the desired section using Hex-editor (Manual for cutting blocks manually), and you can also useutility for automatic cutting rum WwR MTK. Note that SP_Flash_Tool_v5.1352.01 does not work with blocks of more than 4GB, so if your flash memory is larger, use one of the latest versions of the program, or read it in parts (but this is inconvenient).Original instructions

Item 1. Create a scatter.

• Go to the settings of the smartphone in the menu item "security" and put a daw on "Unknown sources."
  
• We go into the settings of the smartphone in the menu item "about the phone" and repeatedly tap on the "build number" and as you see the inscription "you become a developer" go to the menu and enter the new activated menu item "for developers", there you check the box Usb.
  
• We connect the included phone to the computer.
  
• Launch MtkDroidTools and wait for it to connect to the phone (see the bottom left corner of the program).
  
• Press the "Block map" button, a window with a map will appear. In this window, click the button "Create a scatter file" and save the file (the name is better not to change).
  

Item 2. Reading the ROM from the phone.
2.1 Preparation

• Run SP_Flash_Tool
  
• Open the saved scatter (blocks with addresses will appear in the list)
  
• Go to the Read back tab.
  
• Add a block (Add button)
  
• Double click to open the added block, specify the name of the file to save (starts with ROM_)
  
• Further in the appeared window in the second field we enter into the address of the cache block from the scatter file (it is recommended to open this file through the notepad ++ program) and click OK.
  Note:
  1) If the scatter file is of the old type (see the screenshot below), then you will immediately find the necessary cache block without problems by opening it in notepad (or as in the example below through notepad ++)
  
  An example of a section of the old type file scatter

  [attachment = "4233494: old.png"]
  
  2) You can also find a new type file scatter (see screenshot below), in this case you need to drive a cache block with the mark linear_start_addr
  
  An example of a section of the scatter file of a new type

  [attachment = "4233520: new.png"]
  
  * Below are screenshots on the example of the old type of file scatter.
  

2.2 Reading

• Disconnect the phone from the computer, if still not done.
  
• Turn off the phone
  
• We take out and insert the battery back
  
• In the program SP_Flash_Tool, press the Read back button
  
• Connect the phone to the USB in the program should run first red, then blue progress bars. If you didn’t run, try disconnecting the phone, distorting the battery, and then connecting it to the computer again. If it does not help, it means problems with the drivers or try connecting the device without a battery and repeat this step.
  
• My process takes about 20-25 minutes. After the process is completed, a green circle appears, now you can disconnect the phone from the computer and turn it on. SP_Flash_Tool can now be closed.
  

Item 3. Preparing blocks for firmware

• Again open MtkDroidTools and connect the included phone. Make sure that MtkDroidTools sees it.
  
• Go to the root, backup, recovery tab
  
• Click the button "Create backup from ROM_ flash" and select the previously saved file from the program SP_Flash_Tool.
  
• The program will offer to automatically create a CWM, patch the boot - this is at your discretion (but if you want a clean backup, which is recommended, then we refuse to patch).
  
• The backup will appear in the MtkDroidTools \ backups \ ... folder
  

• Now you need to save the created backup, they can always return the phone to its original state. In addition to the folder with a bunch of files from MtkDroidTools, I also recommend saving the ROM_ file for reinsurance.
  

Important information on this manual.
1) Refusing to automatically create a CWM in the backup folder, it will be named factory_NONmodified_recovery.img and, accordingly, when you download the scatter file to the USB flash drive, it will not be picked up automatically and displayed, so for convenience it is recommended to rename it immediately to recovery.imgAnd also a uboot.bin file is created with it. A nuance may also arise, it is that after downloading the scatter file, the USB flash drive may not substitute this file in the UBOOT section, if this does not happen, then simply rename the uboot.bin file to lk.bin and in a new way we load the scatter file (the block should fall into place).

2) Since we cut our backup by cache block, then when you load the file scatter into the USB flash drive, you will not see the CACHE and USRDATA blocks (this is done so that you do not accidentally transfer your personal data along with the backup to the person who will bail out your backup).But there is a caveat, if the device is restored from backups without these blocks, it can continue the boot screen is not loaded, to load completed successfully you must go to the recovery menu and make wipe factory reset. If rekaveri not get there, you are looking for these units from the factory firmware from similar type devices (check to make sure to match processor model, the number of flash memory and version of android), copy these files to a folder of your firmware (or backup) and sewn again already with these files. Also, if you have the desire to deal with the technical aspects, the two lower blocks with a predetermined desired length you can do yourself atof this instruction. Here in the topic such blocks are called "Dummies".

• Download and unpack the program SP_Flash_Tool on your computer
  
• Download and unpack the program SPMultiPortFlashDownloadProject on your computer with the ability to select components in uboot(only relevant for devices with MT6575 and MT6577 processors based on the AGOLD project, for the rest we skip)
  
• Download and install USB VCOM drivers.
  
• Unpack the archive with the factory firmware for your smartphone (the directory to the unpacked folder with the firmware files should not contain Cyrillic characters).
  
• Turn off the smartphone. The cable is not connected to the computer.
  
• Remove and insert the battery back.
  
• (skip if drivers are already installed) We connect the phone to the computer with a cable. The operating system will find a new device - specify the system folder with the USB driver VCOM (for its version of the OS). If something does not work with the installation of drivers, then read the instructions for installing drivers.
  
• (skip if drivers are already installed) Disconnect the cable from the computer.
  
  Next are the numbered items, they are relevant only for devices with an MT6575 and MT6577 processor based on the AGOLD project (i.e. with a dynamic component selection), for the rest we skip

1. Run the program SPMultiPortFlashDownloadProject.
   
2. Select the menu Factory database>Setup data source file and specify the file MTK_DATABASE.mdb (it lies in the SP_MDT folder).
   
3. Choose the File menu>Open Download Agent File and specify the file MTK_AllInOneDA.bin (it lies in the SP_MDT folder).
   
4. Click the Scatter File and select the file MT6577_Android_scatter_emmc.txt (it is in the folder with the firmware).
   
5. Select the type of rear and front cameras and the type of display controller that correspond to your device using the sensor installation button. The easiest way to find out exactly which cameras are installed in your device, and what kind of display, is to ask about it in the topic topic on your device. It's okay if you make a mistake in these parameters. Just ask again with the necessary parameters.
   
   [attachment = "5974047: SPMDT.png"]
6. The program SPMultiPortFlashDownloadProject is no longer needed, it has already made the necessary changes to uboot. Close the program SPMultiPortFlashDownloadProject.
   

• Run the program SP Flash Tool.
  
• Click on the Scatter-loading button and select the MT6577_Android_scatter_emmc.txt file (it is in the folder with the firmware, the devices are different, therefore the file will be named after the processor name, for example MT6789, etc.).
  
  Screenshots from the 3rd version of the program

  [attachment = "5920901: Unnamed1.png"]

  Screenshots from the 5th version of the program

  [attachment = "5920904: Unnamed.png"]
  
  
• IMPORTANT! For devices on the MT6575 and MT6577 processor, we uncheck the Preloader and dsp_bl items, for other MTK-based devices, just tick the Preloader.
  
• Press the Download button if we use the 3rd version of the flash driver, or select the download only mode and press the Download button if we use the 5th version.
  
• Connect the smartphone to your computer turned off cable. The program should see it and start flashing. If your smartphone is not detected, disconnect it from your computer, remove and reinsert the battery and reconnect to your computer. In Device Manager, when correctly installed drivers at the time of the firmware should com port monitor MediaTek PreLoader USB VCOM Port if the preloader is not damaged or MTK USB Port / USB Serial Device - with a damaged preloadere. A finishing EEPROM or in the event any error is disabled and the device disappears from the device manager.
  [attachment = "4242138: 4241491111.jpg"]
  
  
• After the end of the firmware, disconnect the smartphone from the computer and turn on the device.
  
  Screenshots from the 3rd version of the program

  [attachment = "3045049: 3036234.png"]

  Screenshots from the 5th version of the program

  [attachment = "5920908: Unnamed2.png"]

Note:port "MTK USB Port" (PID 0003) or in newer versions of Windows, it can also be automatically determined by the name of "USB Serial Device" fault, and appears in the case of a damaged unit Preloader. If you are watching the opening of the port while attempting to flash the device, then you should know that it allows you to flash only Preloader unit through the function Download only, entire firmware pour through it will not work. Therefore, the appearance of this port the first step is to ask only one block Preloader, and then upon successful completion of the operation to flash the firmware already remaining blocks to uncheck Preloader points.The boot loader initialization order when working with ft.

Sp Flash Tool is another useful feature - it record-ROM drive files created by the program-flasher directly to the addresses in the memory. Function is useful for example when you have damaged NVRAM and want to restore it or just want to fill the firmware to the device via ROM-file. The principle of creating rum files the same as described under spoiler rom-backup. But for clarity, we repeat it here as an example of a single block of NVRAM. Readback need for a procedure to retrieve only the scatter, and can be taken from any device with the same processor. And to work with the function write memory, you will need a scatter file and block preloader on your device, so before you start recording rom-file take care of loading the scatter procedures in fleshtul and check the box on the preloader section.

Read (readback):

• To begin with, let's create a NVRAM block ROM file. To do this, through the notepad ++ program, open our Scatter file and find the block we are interested in. We need two values ​​from the block, namely: linear_start_addr and partition size.
  [attachment = "5863875: nvram notepad.jpg"]
  
  
• Next, run the Sp Flash Tool, load our scatter file, and go to the Readback tab. We click on the plus sign (the Add button), we have a line with a check mark.
  [attachment = "5863878: readback.jpg"]
  
  
• Double click on the line and set the file name. For convenience, I will call it ROM_NVRAM and press the “save” button.
  [attachment = "5863881: save nvram.jpg"]
  
  
• Before us appears the settings window, in which we need to write the previously marked values ​​from the scatter file. In the Start Addres field, we copy the value of linear_start_addr, and in the Lenght field, the partition size value and press the “Ok” button.
  [attachment = "5863885: readback_block_input.jpg"]
  
  
• Next, click on the Readback button, turn off the device, distort the battery (if possible) and connect the switched off device to the computer. The unit will begin reading and a green circle will appear on completion.
  [attachment = "5863889: OK.jpg"]

Write (Write Memory):

• Next, disconnect the device from the computer and activate the write memory tab. In order to activate the write memory function, you must run the Sp Flash Tool and press the key combination Ctrl + Alt + V (Advanced Mode should appear in the title bar).
  [attachment = "5863893: advanced mode.jpg"]
  
  
• Then, as standard, we substitute our scatter file from the device to the flash unit and make sure that we have a check mark on the preloader item and that the preloader block itself is physically present and loaded.
  [attachment = "6281106: preloader.jpg"]
  
  
• Next, in the toolbar, click on the Window tab, put a tick on the write memory item and immediately get to a new tab.
  [attachment = "5863896: write memory.jpg"]
  
  
• In the File Patch field, we need to specify the path to our created ROM file (in our example, using the NVRAM block). To do this, click on the folder button to the right of the line and select our file. In the line below Begin Addres (HEX), copy the value of our block linear_start_addr from the scatter file.
  [attachment = "5863901: write memory input.jpg"]
  
  Note: all rom-files need to be written to your region, therefore, since the NVRAM block is located in the EMMC_USER region, you can see in the screenshot above that it will be written to it. If the rum file you need was removed from another region, then you need to record it into it. For example, a screenshot from the device in which there is a choice of three regions:
  [attachment = "9432266: CR.jpg"]
  The number of regions you may have differs from the example, or it may all be located in one region; Moreover, we note that if everything you need is in the same region, then the region selection in the flashlight will not be available to you.
  
  
• Next, click on the write memory button, turn off the device, distort the battery (if possible) and connect the switched off device to the computer. The recording of the block will begin and a green circle will appear on completion. Next, disconnect the device from the computer and turn it on. Mission Complete). Thus, you can record any ROM files created by the SP Flash Tool, the main thing to remember is the starting address of the block from which you started creating your ROM file.

The SP Flash Tool for downloading the Preloader block to the Download tab requires a binary with a preloader, and not a whole merged ROM of the EMMC_BOOT_1 region. Therefore, if we need a native preloader for the operations with the flasher, and the manufacturer did not provide the native firmware for the device, then we need to extract it from the region's backup. Well, let's look at an example of how this can be done using a hex editor.

1. Open the hex editor and drag and drop into the window the ROM file of the backup of the region in which the Preloader is located.

2. We open our ROM file. The first thing to do is to scroll the editor's slider to the MMM.8 type caption ... FILE_INF - this is the beginning of our preloader. Next, double-click on the first letter M (1) by clicking on the start of our preloader and see that the initial portion of the code (2), to which this marked symbol belongs, is highlighted.

3. Turn the editor's slider until you see the beginning of the solid layer FF FF FF FF - in front of it is the end of our preloader. Set the cursor as shown in the screenshot below. Also, instead of the FF FF layer, the FF FF can be a layer with zeros 00 00 00 00, if it hits zero, then we place the cursor in the same way just before zeros.

4. Press the key combination ctrl + shift + F9 and see that this is how we selected our preloader. To save it, right-click on the selected area and select Write Selection.

5. Through Notepad ++ we look at the name of our preloader in the Scatter file, with which we are going to use it and call it also in the save location selection window (1) (optional, since you can name the preloader as you please, don’t forget names indicate the extension .bin). Click on Write (2) and enjoy our finished preloader.

6. This type of preloader, if you did everything correctly, you can easily use it in the SP Flash Tool, in the Download tab and the USB flash drive will not swear at it.

Note: If you nakasyachite somewhere, the flashlight will talk about an incorrect preloader file and will not load it.
Also an alternative way to extract the preloader and as a logical continuation from the author of the method, the auto foreman preemployer is presented MTKsplit (savagemessiahzine.com)

"It should be borne in mind that in modern phones, operational (RAM / DRAM) and flash memory (eMMC / NAND / NOR) are most often implemented as a single chip, so errors related to RAM may also indicate a malfunction of Flash, and the opposite. "
1. Launch the USB flash drive, in the "Download" tab, download the scatter file (if you do not have a scatter file for your device, use it from a device with the same processor), it doesn’t matter if there are no more firmware files in the folder with it (actual for the version of the driver up to 5.1628 inclusive). Remove all the checkboxes, leave a tick only on the first line - PRELOADER:
Note: If you want to use a newer version of proshivalschika version 5.1628, then tick on the Preloader section without the presence of this file in a folder with a scatter-file to put new versions proshivalschika not allow. If you have the opportunity to find a preloader it on your device model, then copy it to a folder to the scatter-file you wish to use and upload the file to a scatter-fleshtul. Next, making sure to block preloader check mark will appear, skip to step 2. If this is not possible, then proceed as follows:
but. Download this archive with my preloader [attachment = "9019071: preloader.zip"] b. Unzip the preloader.bin file to the folder where you have the scatter file you plan to use.
at. Using the Notepad ++ program, open this scatter file, find the section called Preloader and we are interested in the file_name lineRename the preloader.bin file to a file with the name from the line file_name (in the case of this example, the file preloader.bin is renamed to preloader_lcsh92_wet_jb9.bin)
e. You load your scatter file into the flasher, see the marked preloader block and go further according to the instructions.
NOTE: For this procedure fleshtulu needs only the fact of the presence of scatter files and preloader, so we can afford to take absolutely any preloader. But attention this can be done only for this stage. If suddenly you are inattention or some other reason, in the future will use this file for the firmware of your device, you'll get your hands on the brick which is extremely difficult to then raise. Therefore, after the removal of the dump from your device is not too lazy to delete or rename the file so that in the future not to forget that it is not on your device, and do not spoil yourself and others nerves. And a good tip for the future: Do not try to buy the latest version of proshivalschika, use the version that is recommended either by the manufacturer or by the Komrad your devices.

2. Go to the "Memory Test" tab, put all the checkboxes that can be put on this tab (you may have different information from the one shown in the screenshot):

2.1. Press the Start button:

2.2. After that, connect your device off to the USB-port.

2.3. There will be a memory test that will show information regarding the memory of your device:

3. Analyze all the information by scrolling scroll of the resulting list for errors. If there are no errors, then everything is fine with memory. If you get an error during memory tests, there is a high probability that the device died fleshpamyat / or moved into Read Only mode, which for us is equivalent, as at home no one nor the other is not treated .. Also note the analysis of the errors in the absence of NAND memory (the above screenshot hit the frame), or UFS ignored if your device type EMMC. there is also athe assumption about the possibility of determining the problem in case of a failed flash memory through the flasher's logs .

Sometimes it is necessary to extract the necessary files from the system or usrdata image. Under Linux, this is done simply by mounting the disk, but now we will see how to mount this case under Windows. We will need two utilities: DiskInternals Linux Reader and sgs2toext4.jar (download them from spoilers with drivers and utilities ), and also to use the second utility, the installed Jdk on the computer. The first is necessary for mounting the image, the second for distilling the factory image in ext4 format. Here I will explain that the images we create ourselves through mtkdroidtools, for example, immediately go in ext4 format and therefore do not need distillation, but the factory images in the DiskInternals Linux Reader program are not correctly mounted from the box and therefore need to be run through sgs2toext4.jar. Now, in order, using the example of mounting the usrdata factory image:

1) Open sgs2toext4.jar and drag the image into the window that appears, close the window at the end of the procedure and see that another ext4 image appeared in the folder with the factory image. And if our image has an ext4 structure initially, then you do not need this item:If you try to overtake an already finished image through this utility, then you will fail, because the program just loops in and never writes done.

2) Open DiskInternals Linux Reader and mount our ext4 image, the procedure on the screenshot:If you try to mount a non-ext4 image in this program, the program will write that the file system is not supported and it will not open.

3) Next, we see our mounted image in the program window and to open it simply double-click on it:
4) We see what is inside the image, in this case there is one folder (there are four files inside the folder). To extract it, we need to select it and act on points in the screenshot:
5) Then select the save directory and click next:
6) In the window that appears, click next:
7) Everything was saved successfully, click ready and use:

We are looking for firmware for any Android devices
Help in firmware for any Android devices
Processing (unpacking and assembly) of firmware and images (* .img, * .bin) strictly under WINDOWS
Kingo Android Root
Instructions on firmware through the program SPMultiPortFlashDownloadProject
Instructions on firmware installation on SOC MTK 6589 (8389), installing Custom Recovery (CWM), getting root
Test points for preloader firmware
Creating backup using MtkDroidTools
Thread on MtkDroidTools on the forumsavagemessiahzine.com
Mobile Memory Markup
ADB and all that can be done with it
MauiMETA - a program for working with NVRAM (modem)
ROM_BackUp-Splitter (for MTK65 ** ROM)
Wwr MTK - Program for working with ROM files on MTK phones, with software dumped