[Android Q&A, Help & Troubleshooting] rajneeshmalik:
Hi to all,

I am a new member here, and my 1st post.

First I will give description of my device, installed software etc and then come to the issue.

My Device - As shown in Mtk Droid Tools 2.5.3d

Hardware : MT6582 (MT8312 is Fake!)

Model : 3G 7271-HD70

Build number : iBall Slide 3G 7271-HD70_KK_V9.0,2014-11-5

Build date UTC : 20141105-125918

Android v : 4.4.2

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V35.P4, 2014/06/27 14:22

Kernel v : 3.4.67 (zouqb@softdeps01) (gcc version 4.7 (GCC) ) #1 SMP Wed Nov 5 20:46:33 CST 2014

Uboot build v : -----

LCD Driver IC : 0-kd070d23-40na-a16

The Color button on the Bottom Left of MTK Droid shows GREEN, indicating I have Root Access on my device and also have installed:

Kingroot

abdb insecure (enabled insecure mode)

Busybox

USB debugging, Connected via MTP mode through USB

On my PC I have:

Windows 7,

PDANet A4183 drivers,

VCOM drivers, Preloaders etc.

MTK Droid Tools 2.5.3d

SP Flash Tools v5.1548

ISSUE NO-1 = BEING FACED IN MTK DROID TOOLS

=========================================

My device gets detected in the MTK Droid but after clicking on the Backup (in root.backup.recovery tab) it goes upto preloader_and_dsp and sits there for ever. The green bar at the bottom keeps on moving from left to right, for ever.

On my device, I checked the situation using root browser, in my SD Card -> location -> /mnt/media_rw/sdcard0/clockworkmod/backup/160520-200455/ and saw the same file preloader_and_dsp and the size is 2.03 MB. Checked back after 1 hour, the size increased upto 3.00 MB ONLY!

That way one can understand how many years it will take to backup around 5 GB of my Stock ROM + User data.

Now I killed the MTK Droid Tools. Log from Opening up the MTK droid upto killing it is (attached)

To double check, I did a factory reset on my device, formatted my SD Card and followed the same procedure, but the results were same. After doing some research I found out there could be some adb clash and therefore I executed the command, which showed my device getting detected by adb.

C:\adb>adb devices

List of devices attached

0123456789ABCDEF device

However, I found that after opening MTK Droid Tools, adb.exe file gets executed and shows up in the Task manager. And the moment I start taking the backup, another adb.exe files gets executed from the same folder (2 adb.exe in the task manager) and the file preloader_dsp gets hung up. However, when I killed one adb.exe file in the task manager, the procedure speeds up and MTK droid tools creates the backup of my device into the HDD.

Now it doesn't matter when I kill adb.exe. If I kill it at initial stage i.e. when the size is of preloader_dsp is 2 Mbs or if I kill it when the size reaches 3 Mbs, the file thus created (preloader.bin) is 119,176 bytes only.

The screen shot of Resource monitor showing adb.exe in wait chain.... attached.

So the files created by MTK droid tools are:

16,777,216 boot.img

512 EBR1

512 EBR2

3,145,728 logo.bin

512 MBR

524,288 misc

7,631 MT6582_Android_scatter.txt

119,176 preloader.bin

16,777,216 factory_NONmodified_recovery.img

6,291,456 secro.img

1,073,741,824 system.img

NOW SP FLASH TOOL (v5.1548)

====================

I opened MTK droid back again, using Block Map (attached), and created scatter file called MT6582_Android_scatter.txt (attached)

I opened up SP Flash Tool (v5.1548) and loaded the same scatter file and using the Readback Tab-> Add button created ROM_0 using:

physical_start_addr: 0x0 of preloader.bin (as mentioned in the scatter file) ---- in the Start Address

linear_start_addr: 0x14E380000 of FAT

... in the Length Fields of the Dialog box -> Readback block start address and confirmed that the Type is HEX.

Switched of my device and using the Reset button (my devices has inbuilt battery) clicked Readback button on SP Flash Tools.

I took around 20 minutes for the process to get completed and it confirmed with a Green BOX with Tick, indicating that the task is finished OK. The file ROM_0 was created.

Now in the MTK droid tools -> root.backup.recovery -> To process file ROM_ from Flash Tool I extracted the ROM_0 that I created in the SP flash tools and it took around 25 minutes for the process to get completed and the task completed as OK.

List of files thus created (!Files_to_FlashTool)

5,718,016 3G-7271-HD70_141105__boot_patched_160518-201438.img

6,416,384 3G-7271-HD70_141105__recovery_160518-201438.img

22,020,096 bmtpool

16,777,216 boot.img

132,120,576 cache.img

4,294,967,296 data.img

512 EBR1

512 EBR2

10,485,760 expdb

16,777,216 factory_NONmodified_recovery.img

3,145,728 logo.bin

512 MBR

524,288 misc

7,631 MT6582_Android_scatter.txt

5,242,880 nvram.bin

119,176 preloader.bin

10,485,760 protect_f

10,485,760 protect_s

3,145,728 pro_info

131,072 seccfg

6,291,456 secro.img

1,073,741,824 system.img

393,216 uboot.bin

The size is around 5.2 GB and matched the files/sizes created by the MTK Droid tools as well.

The List above seems ok apparently, but while I checked in the blockmap of MTK droid tools I found out:

1. The size PRELOADER.BIN on blockmap/scatter file shows 20971520 bytes (20 MB) but on disk it is 119,176 bytes. (in both the process i.e. MTK Droid Tools -> Backup AND SP Flash Tools ROM_0)

2. The sizes of the recoveries created are differrent in all the 3 files.

3. The MTK Droid Tools did not create any CWM flash recovery, only SP Flash Tools created.

Now my questions.

Question 1. Why I am not able to create Backup using MTK droid tools and I have to manually kill the adb.exe to roll on the process.

Question 2. Why is size of file Preloader.bin not matching the addresses in the blockmap/scatter file. (using both the procedures i.e. from SPFT ROM_0 and MTK droid tools.

Question 3. How reliable is this preloader.bin, if I am caught in a situation where I have to flash preloader.bin.

Question 4. When the size of the factory_NONmodified_recovery.img is 16,777,216 bytes, why are the file sizes of ------ CWM boot recovery patched file 3G-7271-HD70_141105__boot_patched_160518-201438.img is 5718016 bytes ---------- and 3G-7271-HD70_141105__recovery_160518-201438.img is of 6,416,384 bytes

Question 5. Which one is the CWM recovery SP Flash tools created in Question 4 above.

All in all, is my procedure correct or I am faulting somewhere.

I used 3 PCs to carry on the procedure and have been doing research for the past several weeks. When I used ROM Manager APK on my device to install CWM recovery, it says, Sorry your device is currently not supported. Have you tried installing CWM manually? I have read this fact that not on all the phones, the ROM manager app works, so I opted for MTK Droid and SPF Tools.

This is my first time flashing/backup experience and am therefore too skeptical.

Thanks so much in advance and Kind regards,

Rajneesh

Files attached: Oops, cannot attach files. Therefore pasting the text of my scatter file and USBdreview.

1. Log from opening up the MTK droid tools, taking the backup and killing it.

2. Blocksmap by MTK Droid Tools

3. MT6582_Android_scatter.txt

4. Screen Shot of SP Flash tools after loading scatter file in the end.

5. Screen Shot of Resource Moniter showing adb.exe

6. USBdreview showing my detected device.

MT6582_Android_scatter.txt

________________________

############################################################################################################

#

# General Setting

#

############################################################################################################

- general: MTK_PLATFORM_CFG

info:

- config_version: V1.1.1

platform: MT6582

project: MTDTtest

storage: EMMC

boot_channel: MSDC_0

block_size: 0x20000

############################################################################################################

#

# Layout Setting

#

############################################################################################################

- partition_index: SYS0

partition_name: PRELOADER

file_name: preloader.bin

is_download: true

type: SV5_BL_BIN

linear_start_addr: 0x0

physical_start_addr: 0x0

partition_size: 0x1400000

region: EMMC_BOOT_1

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: BOOTLOADERS

reserve: 0x00

- partition_index: SYS1

partition_name: MBR

file_name: MBR

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x1400000

physical_start_addr: 0x0

partition_size: 0x80000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS2

partition_name: EBR1

file_name: EBR1

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x1480000

physical_start_addr: 0x80000

partition_size: 0x80000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS3

partition_name: PRO_INFO

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x1500000

physical_start_addr: 0x100000

partition_size: 0x300000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: PROTECTED

reserve: 0x00

- partition_index: SYS4

partition_name: NVRAM

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x1800000

physical_start_addr: 0x400000

partition_size: 0x500000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: BINREGION

reserve: 0x00

- partition_index: SYS5

partition_name: PROTECT_F

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x1D00000

physical_start_addr: 0x900000

partition_size: 0xA00000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: PROTECTED

reserve: 0x00

- partition_index: SYS6

partition_name: PROTECT_S

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x2700000

physical_start_addr: 0x1300000

partition_size: 0xA00000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: PROTECTED

reserve: 0x00

- partition_index: SYS7

partition_name: SECCFG

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x3100000

physical_start_addr: 0x1D00000

partition_size: 0x20000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

- partition_index: SYS8

partition_name: UBOOT

file_name: lk.bin

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x3120000

physical_start_addr: 0x1D20000

partition_size: 0x60000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS9

partition_name: BOOTIMG

file_name: boot.img

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x3180000

physical_start_addr: 0x1D80000

partition_size: 0x1000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS10

partition_name: RECOVERY

file_name: recovery.img

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x4180000

physical_start_addr: 0x2D80000

partition_size: 0x1000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS11

partition_name: SEC_RO

file_name: secro.img

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x5180000

physical_start_addr: 0x3D80000

partition_size: 0x600000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS12

partition_name: MISC

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x5780000

physical_start_addr: 0x4380000

partition_size: 0x80000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

- partition_index: SYS13

partition_name: LOGO

file_name: logo.bin

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x5800000

physical_start_addr: 0x4400000

partition_size: 0x300000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS14

partition_name: EBR2

file_name: EBR2

is_download: true

type: NORMAL_ROM

linear_start_addr: 0x5B00000

physical_start_addr: 0x4700000

partition_size: 0x80000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS15

partition_name: EXPDB

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x5B80000

physical_start_addr: 0x4780000

partition_size: 0xA00000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

- partition_index: SYS16

partition_name: ANDROID

file_name: system.img

is_download: true

type: YAFFS_IMG

linear_start_addr: 0x6580000

physical_start_addr: 0x5180000

partition_size: 0x40000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS17

partition_name: CACHE

file_name: cache.img

is_download: true

type: YAFFS_IMG

linear_start_addr: 0x46580000

physical_start_addr: 0x45180000

partition_size: 0x7E00000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS18

partition_name: USRDATA

file_name: data.img

is_download: true

type: YAFFS_IMG

linear_start_addr: 0x4E380000

physical_start_addr: 0x4CF80000

partition_size: 0x100000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS19

partition_name: FAT

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x14E380000

physical_start_addr: 0x14CF80000

partition_size: 0x7EC80000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

- partition_index: SYS20

partition_name: BMTPOOL

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0xFFFF00A8

physical_start_addr: 0xFFFF00A8

partition_size: 0x1500000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: false

is_reserved: true

operation_type: RESERVED

reserve: 0x00

-------------------------------------------------

USBDreview

==================================================

Device Name : 0000.0013.0002.003.000.000.000.000.000

Description : 3G 7271-HD70

Device Type : Unknown

Connected : Yes

Safe To Unplug : Yes

Disabled : No

USB Hub : No

Drive Letter :

Serial Number :

Created Date : 30-May-16 18:03:56

Last Plug/Unplug Date: 30-May-16 19:38:43

VendorID : 0bb4

ProductID : 0c02

Firmware Revision : 2.16

USB Class : 00

USB SubClass : 00

USB Protocol : 00

Hub / Port :

Computer Name :

Vendor Name :

Product Name :

ParentId Prefix :

Service Name : WUDFRd

Service Description:

Driver Filename : WUDFRd.sys

Device Class : WPD

Device Mfg : iBall

Power :

USB Version :

Driver Description: iBall Slide 3G 7271-HD70

Driver Version : 6.1.7600.16385

Driver InfSection : MTP

Driver InfPath : wpdmtp.inf

Instance ID : USB\VID_0BB4&PID_0C02&MI_00\6&1df24836&10&0000

Capabilities : SurpriseRemovalOK

==================================================

==================================================

Device Name : 0000.0013.0002.003.000.000.000.000.000

Description : Android ADB Interface

Device Type : Vendor Specific

Connected : Yes

Safe To Unplug : No

Disabled : No

USB Hub : No

Drive Letter :

Serial Number :

Created Date : 30-May-16 18:03:57

Last Plug/Unplug Date: 30-May-16 19:38:43

VendorID : 0bb4

ProductID : 0c02

Firmware Revision : 2.16

USB Class : ff

USB SubClass : 42

USB Protocol : 01

Hub / Port :

Computer Name :

Vendor Name :

Product Name :

ParentId Prefix :

Service Name : WinUSB

Service Description: Android USB Driver

Driver Filename : WinUsb.sys

Device Class : AndroidUsbDeviceClass

Device Mfg : Google USB

Power :

USB Version :

Driver Description: Android ADB Interface

Driver Version : 2.0.10.2

Driver InfSection : USB_INSTALL

Driver InfPath : oem45.inf

Instance ID : USB\VID_0BB4&PID_0C02&MI_01\6&1df24836&10&0001

Capabilities :

==================================================

==================================================

Device Name : iBall_Slide

Description : MCX Micromax A74 USB Device

Device Type : Unknown

Connected : Yes

Safe To Unplug : Yes

Disabled : No

USB Hub : No

Drive Letter : L:, M:

Serial Number : 0123456789ABCDEF

Created Date : 30-May-16 18:03:55

Last Plug/Unplug Date: 30-May-16 19:38:43

VendorID : 0bb4

ProductID : 0c02

Firmware Revision : 2.16

USB Class : 00

USB SubClass : 00

USB Protocol : 00

Hub / Port :

Computer Name :

Vendor Name :

Product Name :

ParentId Prefix : 6&1df24836&10

Service Name : usbccgp

Service Description: Microsoft USB Generic Parent Driver

Driver Filename : usbccgp.sys

Device Class : USB

Device Mfg : (Standard USB Host Controller)

Power : 500 mA

USB Version : 2.00

Driver Description: USB Composite Device

Driver Version : 6.1.7601.18328

Driver InfSection : Composite.Dev

Driver InfPath : usb.inf

Instance ID : USB\VID_0BB4&PID_0C02\0123456789ABCDEF

Capabilities : Removable, UniqueID, SurpriseRemovalOK

==================================================