How to backup your ROM with MTK droid tools !

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
14,677
2,179
113
48
London UK
haha...is that what you were worried about...you only need to press the root button if the coloured box in the bottom left hand side is blue...if it is green then mtk droid tools does not need to grant you temporary root which is what this 'ROOT' button is for


so make sure that the coloured box is green...then proceed to make the backup,just be aware that you may receive errors as sometimes it will want to load the backup to your sd card before dumping it onto your p.c.


don't ask me why it can just be funny like that,my umi zero wouldn't create a complete backup without an ex sd card inserted even though i had well over 10GB internal memory free


make sure you make 2 or 3 backups and then compare them to make sure all the correct files are there


 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
haha...is that what you were worried about...you only need to press the root button if the coloured box in the bottom left hand side is blue...if it is green then mtk droid tools does not need to grant you temporary root which is what this 'ROOT' button is for


so make sure that the coloured box is green...then proceed to make the backup,just be aware that you may receive errors as sometimes it will want to load the backup to your sd card before dumping it onto your p.c.


don't ask me why it can just be funny like that,my umi zero wouldn't create a complete backup without an ex sd card inserted even though i had well over 10GB internal memory free



make sure you make 2 or 3 backups and then compare them to make sure all the correct files are there



So this means that any errors reported by MTK Droid Tools is due to lack of full root permisions?
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
So this means that any errors reported by MTK Droid Tools is due to lack of full root permisions?
When i start the phone in CWM recovery and connect to MTK Droid Tools, the status box is cyan-blue!
 

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
14,677
2,179
113
48
London UK
When i start the phone in CWM recovery and connect to MTK Droid Tools, the status box is cyan-blue!
why are you connecting the device through CWM recovery...?


there is no tutorial that asks you to do this...just make sure usb debugging is enabled in dev options and make sure drivers are good then if the box stays blue press the 'root' button for temporary root to create the backup...you may also get a request on your device screen for superuser access,if that happens then you will need to root the device and install superSU,but considering that you have CWM installed already all you will need to do is flash a superSU .zip with CWM and this should give you root,then you can make the backup


if you want to unroot afterwards then just go into superSU settings and scroll down to 'full unroot'
 

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
why are you connecting the device through CWM recovery...?


there is no tutorial that asks you to do this...just make sure usb debugging is enabled in dev options and make sure drivers are good then if the box stays blue press the 'root' button for temporary root to create the backup...you may also get a request on your device screen for superuser access,if that happens then you will need to root the device and install superSU,but considering that you have CWM installed already all you will need to do is flash a superSU .zip with CWM and this should give you root,then you can make the backup


if you want to unroot afterwards then just go into superSU settings and scroll down to 'full unroot'
But if I get the request on my device screen for superuser access, and install superSU, it means that the backup operation will result in a rooted backup firmware. Right?
 

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
14,677
2,179
113
48
London UK
But if I get the request on my device screen for superuser access, and install superSU, it means that the backup operation will result in a rooted backup firmware. Right?
no...because root requires a superuser application to access...without this and it's binaries root is not possible...so you will have a normal backup
 

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
no...because root requires a superuser application to access...without this and it's binaries root is not possible...so you will have a normal backup
But once i install superSU.zip through CWM recovery and start the device, my firmware will allready be rooted and superSU application icon present on my device.


This means that any backup performed by MTK Droid Tools will be a rooted backup firmware.
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
But once i install superSU.zip through CWM recovery and start the device, my firmware will allready be rooted and superSU application icon present on my device.


This means that any backup performed by MTK Droid Tools will be a rooted backup firmware.
I forgot to mention that my stock factory firmware has the recovery-from-boot.p file present in the system.


That means that if I start the device normally, CWM recovery will be replaced automatically by Factory recovery.


That's why I have to boot my device in CWM recovery mode to make the backup.
 

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,316
410
113
exactly if you backup with superSU flashed its rooted ..


but why care about if rooted or not ?you can simply unroot within 1 minute.
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
exactly if you backup with superSU flashed its rooted ..​


but why care about if rooted or not ? you can simply unroot within 1 minute.​


This might sound stupid for some of you in civilized countries. But in my country, some manufacturers / retailers are unreliable, so to speak gently, when it comes to warranty conditions of the device. So, that's why I want to have a full unrooted stock factory backup of my firmware. Furthermore, my phone manufacturer do not post on their website the official firmware package.​


Sorry if I bored or annoyed someone by my insistence.​


By the way, did you received my private message?​
 
Last edited by a moderator:

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,316
410
113
sorry i get about 30 messages a day and cant read everything :S


if you unroot and delete the binaries there should be no problem but anyway you can also do a readback with flashtools
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
sorry i get about 30 messages a day and cant read everything :S


if you unroot and delete the binaries there should be no problem but anyway you can also do a readback with flashtools
I did the read back with flashtools. And i followed the steps from you tutorial. I thought it was enough, until i noticed that my folder contains all the required files but the preloader.bin. Then i verified you video and your folder contain the same files like mine.


As far as I know the preloader.bin is required by SP Flash Tool to put the phone in download mode. Is it right or is it not?
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
attach your scatter please
Here it is:



Code:
############################################################################################################


#

#Â  General Setting

#

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

- general: MTK_PLATFORM_CFG

  info:

    - config_version: V1.1.2

      platform: MT6592

      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: 0x40000

  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: 0x0

  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: 0x80000

  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: NORMAL_ROM

  linear_start_addr: 0x100000

  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: NORMAL_ROM

  linear_start_addr: 0x400000

  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: EXT4_IMG

  linear_start_addr: 0x900000

  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: EXT4_IMG

  linear_start_addr: 0x1300000

  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: NORMAL_ROM

  linear_start_addr: 0x1D00000

  physical_start_addr: 0x1D00000

  partition_size: 0x40000

  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: 0x1D40000

  physical_start_addr: 0x1D40000

  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: 0x1DA0000

  physical_start_addr: 0x1DA0000

  partition_size: 0xA00000

  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: 0x27A0000

  physical_start_addr: 0x27A0000

  partition_size: 0xA00000

  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: 0x31A0000

  physical_start_addr: 0x31A0000

  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: NORMAL_ROM

  linear_start_addr: 0x37A0000

  physical_start_addr: 0x37A0000

  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: 0x3820000

  physical_start_addr: 0x3820000

  partition_size: 0x800000

  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: 0x4020000

  physical_start_addr: 0x4020000

  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: NORMAL_ROM

  linear_start_addr: 0x40A0000

  physical_start_addr: 0x40A0000

  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: SPDATA

  file_name: NONE

  is_download: false

  type: EXT4_IMG

  linear_start_addr: 0x4AA0000

  physical_start_addr: 0x4AA0000

  partition_size: 0xD60000

  region: EMMC_USER

  storage: HW_STORAGE_EMMC

  boundary_check: true

  is_reserved: false

  operation_type: INVISIBLE

  reserve: 0x00


- partition_index: SYS17

  partition_name: ANDROID

  file_name: system.img

  is_download: true

  type: EXT4_IMG

  linear_start_addr: 0x5800000

  physical_start_addr: 0x5800000

  partition_size: 0x4D000000

  region: EMMC_USER

  storage: HW_STORAGE_EMMC

  boundary_check: true

  is_reserved: false

  operation_type: UPDATE

  reserve: 0x00


- partition_index: SYS18

  partition_name: CACHE

  file_name: cache.img

  is_download: true

  type: EXT4_IMG

  linear_start_addr: 0x52800000

  physical_start_addr: 0x52800000

  partition_size: 0x8000000

  region: EMMC_USER

  storage: HW_STORAGE_EMMC

  boundary_check: true

  is_reserved: false

  operation_type: UPDATE

  reserve: 0x00


- partition_index: SYS19

  partition_name: USRDATA

  file_name: data.img

  is_download: true

  type: EXT4_IMG

  linear_start_addr: 0x5A800000

  physical_start_addr: 0x5A800000

  partition_size: 0x100000000

  region: EMMC_USER

  storage: HW_STORAGE_EMMC

  boundary_check: true

  is_reserved: false

  operation_type: UPDATE

  reserve: 0x00


- partition_index: SYS20

  partition_name: FAT

  file_name: NONE

  is_download: false

  type: NORMAL_ROM

  linear_start_addr: 0x15A800000

  physical_start_addr: 0x15A800000

  partition_size: 0x248100000

  region: EMMC_USER

  storage: HW_STORAGE_EMMC

  boundary_check: true

  is_reserved: false

  operation_type: INVISIBLE

  reserve: 0x00


- partition_index: SYS21

  partition_name: BMTPOOL

  file_name: NONE

  is_download: false

  type: NORMAL_ROM

  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
 I described the steps i follows in my post on page 17 and given all the details.
 
Last edited by a moderator:

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,316
410
113
do another readback with end adress


0x1400000


just tried again on a cubot and it worked. i didnt even notice that preloader was missing because i focused on CWM and did backup later
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
do another readback with end adress


0x1400000


just tried again on a cubot and it worked. i didnt even notice that preloader was missing because i focused on CWM and did backup later
this shoud be entered on start address?
 

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,316
410
113
The preloader file itself is NOT needed to put phone into downloading mode.


the preloader also should NEVER BE FLASHED ! , if the preloader on the phone is corrupted by downloading a wrong preloader on it, you need the file. But usually the file is not needed and should be backuped anyway during the mtkdroid tools backup
 

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,316
410
113
no, post said end adress start is as always 0x0000000000000000
 
Last edited by a moderator:

djtetei

Member
Jan 24, 2015
33
2
8
43
Braila
The preloader file itself is NOT needed to put phone into downloading mode.


the preloader also should NEVER BE FLASHED ! , if the preloader on the phone is corrupted by downloading a wrong preloader on it, you need the file. But usually the file is not needed and should be backuped anyway during the mtkdroid tools backup
So as long as I have the rest of the files from the read back, I should be fine? Because it will save me a lot of trouble.


 By the way: why that end adddress? It does not corespons to any value in my scatter.
 
Last edited by a moderator: