How To backup Mediatek [MTK] device

Search This thread

rajit

Senior Member
Oct 13, 2012
895
853
kolkata
geek2gyaan.blogspot.com
How to Make a full backup ROM for MT6592,MT6589, MT6582, MT6577, MT6575, MT6572, MT6516 phones. This is basically for all MTK phones from MediaTek.

This is also a great way to share your firmware with someone who may need the stock ROM for their bricked phone. Or if you're the bricked one, you can direct someone with the same phone as you to this tutorial so they can prepare their ROM for you.

Important: Make sure to accept any SuperSU or SuperUser permission requests your phone may ask for while you're doing these steps. Any firewall requests your PC may have installed, also allow.

The tutorial will show you how to:

- make a full backup of your ROM (firmware)
- make the ROM firmware ready for SP Flash Tools

What you need:

- A rooted MTK phone

- BusyBox (can be downloaded from Google Play)

- MTK Droid Tools v2.5.0 Download Here

- ADB drivers Download Here or Here(so your computer can communicate with your rooted phone)

A) Prepare your phone and get the utilities we'll need

1. Enable debugging mode on your phone. From your homescreen, tap the Menu button > Settings > Development. Tap 'Debug Mode' and make sure it's checked.

2. Install BusyBox. Go to Google Play and search 'BusyBox' and install.

3. Install PDANet ADB Drivers. Download from here. Run the download and follow the instructions. A USB cable is required to connect your phone to your PC. After installing the drivers, keep your phone connected.

4. Download MTK Droid Tools 2.5.0 and extract to a known location on your PC.

B) Open ADB prompt to begin communication with the phone

1. Go into the extracted MTK Droid Tools folder from step 4 and right-click on 'MTKdroidTools.exe'. Select 'Run as administrator'.

2. Wait several seconds while MTK Droid Tools communicates with your phone. You'll eventually see the main screen come up with all of your phone's information. Look in the bottom left hand corner of the main window, you should see a green square. If it's yellow, you can try to click the 'root' button in MTK Droid Tools to get temporary root shell. If this doesn't work, and you've already got CWM, alternatively you can boot into CWM and then the little square should be green.

C) Read back the ROM with MTK Droid Tools

1. Go back to the main menu of MTK Droid Tools and select the 'Root, Backup, Recovery' tab.

2. Click the 'Backup' button. You will see MTK Droid Tools start to read all the data from your phone Smile. This can take awhile. So let it do it's thing. Have a coffee, whatever.

3. After it's finished reading back the ROM, another window will pop up asking you if you'd like to compress the image. Better to select 'Yes'. This will save space and make it into one tight package. MTK Droid Tools will then pack it up into a zip and then let you know it's finished.
İmage
backup_jpg2.jpg

D) Prepare the data from MTK Droid Tools for SP Flash Tools

1. In the MTK Droid Tools 'root, backup, recovery', you will a button that says 'To prepare blocks for Flash Tool'. Click it.

2. A new explorer window will open directly to the backups folder that MTK Droid Tools made. Select your phone's backup folder. It will look something like *your phone*-backup-YYMMDD. Open this folder.

3. Inside your phone's backup folder, you will see a file called 'files.md5'. Select this and the process will start Smile

4. This will take a while. Go have another coffee or shot of whiskey, smoke a joint. Whatever your like.

5. After it's finished, open the folder where you extracted MTK Droid Tools. There you will see a folder called 'backup'. Open this folder, then open the folder for your phone (*your phone*-backup-YYMMDD). There will be a folder called '!Files_to_FlashTool'. That's the folder to use for flashing with SP Flash Tools! Smile

flashtool.jpg


This Guide can be Found on Chianaforums, but i poste specialy becuse of many Q700/Q700i users still unkown from this :(

Credit:-
@yuweng , @rua1 still don't know who is the developer of this app, if anything missing PM me :highfive:
 

Attachments

  • backup_jpg2.jpg
    backup_jpg2.jpg
    3.7 KB · Views: 3,669
  • flashtool.jpg
    flashtool.jpg
    3.7 KB · Views: 3,308
Last edited:

KieranFoot

Member
Sep 17, 2010
47
18
Rochdale
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...

I'm all for information dispersal, but just copying annoys me.

Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.

Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.

Sent from my A1-810 using XDA Premium HD app
 

rajit

Senior Member
Oct 13, 2012
895
853
kolkata
geek2gyaan.blogspot.com
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...

I'm all for information dispersal, but just copying annoys me.

Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.

Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.

Sent from my A1-810 using XDA Premium HD app
i don't have any regret that what i am doing ,, if you don't think its helpful or coped then use the Report button and END this conversion
smiley-bounce016.gif
 
Last edited:

KieranFoot

Member
Sep 17, 2010
47
18
Rochdale
Here is how to backup your device for those more interested in how it works.

Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.

Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.

Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.


Code:
preloader    0x0000000000c00000   0x0000000000000000   2   /dev/misc-sd
mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1
pmt          0x0000000000400000   0x0000000000100000   2   /dev/block/mmcblk0
pro_info     0x0000000000300000   0x0000000000500000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000800000   2   /dev/block/mmcblk0
protect_f    0x0000000000a00000   0x0000000000d00000   2   /dev/block/mmcblk0p2
protect_s    0x0000000000a00000   0x0000000001700000   2   /dev/block/mmcblk0p3
seccfg       0x0000000000020000   0x0000000002100000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000002120000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000002180000   2   /dev/block/mmcblk0
recovery     0x0000000000a00000   0x0000000002780000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000003180000   2   /dev/block/mmcblk0p4
misc         0x0000000000080000   0x0000000003780000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000003800000   2   /dev/block/mmcblk0
expdb        0x0000000000a00000   0x0000000003b00000   2   /dev/block/mmcblk0
android      0x0000000040000000   0x0000000004500000   2   /dev/block/mmcblk0p5
cache        0x000000002bc00000   0x0000000044500000   2   /dev/block/mmcblk0p6
usrdata      0x000000033a220000   0x0000000070100000   2   /dev/block/mmcblk0p7
bmtpool      0x0000000001500000   0x00000000ff3f00a8   2   /dev/block/mmcblk0

As you can see it gives you the block device used for the partition and the size and start of the position on that device.

Sent from my A1-810 using XDA Premium HD app
 
Last edited:

abhinav2hd

Senior Member
Aug 9, 2013
370
858
Pune
Here is how to backup your device for those more interested in how it works.

Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.

Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.

Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.


Code:
preloader    0x0000000000c00000   0x0000000000000000   2   /dev/misc-sd
mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1
pmt          0x0000000000400000   0x0000000000100000   2   /dev/block/mmcblk0
pro_info     0x0000000000300000   0x0000000000500000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000800000   2   /dev/block/mmcblk0
protect_f    0x0000000000a00000   0x0000000000d00000   2   /dev/block/mmcblk0p2
protect_s    0x0000000000a00000   0x0000000001700000   2   /dev/block/mmcblk0p3
seccfg       0x0000000000020000   0x0000000002100000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000002120000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000002180000   2   /dev/block/mmcblk0
recovery     0x0000000000a00000   0x0000000002780000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000003180000   2   /dev/block/mmcblk0p4
misc         0x0000000000080000   0x0000000003780000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000003800000   2   /dev/block/mmcblk0
expdb        0x0000000000a00000   0x0000000003b00000   2   /dev/block/mmcblk0
android      0x0000000040000000   0x0000000004500000   2   /dev/block/mmcblk0p5
cache        0x000000002bc00000   0x0000000044500000   2   /dev/block/mmcblk0p6
usrdata      0x000000033a220000   0x0000000070100000   2   /dev/block/mmcblk0p7
bmtpool      0x0000000001500000   0x00000000ff3f00a8   2   /dev/block/mmcblk0

As you can see it gives you the block device used for the partition and the size and start of the position on that device.

Sent from my A1-810 using XDA Premium HD app

dude.. Why to follow an odd and complicated backup method like yours when an easy tool like mtkdroidtool is available which can easily backup whole firmware and it is tested by several users which means it is reliable tool.
 

vampirefo

Senior Member
Apr 3, 2010
3,243
1,641
Here is how to backup your device for those more interested in how it works.

Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.

Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.

Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.


Code:
preloader    0x0000000000c00000   0x0000000000000000   2   /dev/misc-sd
mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1
pmt          0x0000000000400000   0x0000000000100000   2   /dev/block/mmcblk0
pro_info     0x0000000000300000   0x0000000000500000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000800000   2   /dev/block/mmcblk0
protect_f    0x0000000000a00000   0x0000000000d00000   2   /dev/block/mmcblk0p2
protect_s    0x0000000000a00000   0x0000000001700000   2   /dev/block/mmcblk0p3
seccfg       0x0000000000020000   0x0000000002100000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000002120000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000002180000   2   /dev/block/mmcblk0
recovery     0x0000000000a00000   0x0000000002780000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000003180000   2   /dev/block/mmcblk0p4
misc         0x0000000000080000   0x0000000003780000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000003800000   2   /dev/block/mmcblk0
expdb        0x0000000000a00000   0x0000000003b00000   2   /dev/block/mmcblk0
android      0x0000000040000000   0x0000000004500000   2   /dev/block/mmcblk0p5
cache        0x000000002bc00000   0x0000000044500000   2   /dev/block/mmcblk0p6
usrdata      0x000000033a220000   0x0000000070100000   2   /dev/block/mmcblk0p7
bmtpool      0x0000000001500000   0x00000000ff3f00a8   2   /dev/block/mmcblk0

As you can see it gives you the block device used for the partition and the size and start of the position on that device.

Sent from my A1-810 using XDA Premium HD app

Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.

I think I got it figured out, wont know for sure until I get my phones to test.

Anyway basically I just

cat /proc/dumchar_info

this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.

to pull eg backup

dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112

to restore

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
 
Last edited:

KieranFoot

Member
Sep 17, 2010
47
18
Rochdale
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.

I think I got it figured out, wont know for sure until I get my phones to test.

Anyway basically I just

cat /proc/dumchar_info

this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.

to pull eg backup

dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112

to restore

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112


Yup, that's right :D
 

xlSKYFiRElx

Senior Member
Apr 24, 2014
78
7
Sector One
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones

and here is my log, notice the bolded and underlined letters, i need help :( thanks in advance :)

Code:
In system already available:  Android Debug Bridge version 1.0.31

 --->>> Connect to device <<<---
 --- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
 --- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
 --- scatter is write to the file: 
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
 --- We keep blocks: 
 - preloader_and_dsp
 - MBR
 - EBR1
 - nodl_pro_info
 - nvram.bin
 - userdata_nvram_only.tar
 - nodl_protect_f.ext4.img
 - nodl_protect_f.ext4.tar
 - nodl_protect_s.ext4.img
 - nodl_protect_s.ext4.tar
 - nodl_seccfg
 - lk.bin
 - boot.img
 - recovery.img
 - secro.img
 - nodl_misc
 - logo.bin
 - nodl_expdb
 - system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
 --- We keep folders contents copying on PC 
   - /data/nvram
   - /system
  --- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR  ---[/B][/U]
 --- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
  -- preloader_and_dsp: md5 OK;  ... it is copied  ... cut OK
  -- MBR: md5 OK;  ... it is copied 
  -- EBR1: md5 OK;  ... it is copied 
  -- nodl_pro_info: md5 OK; 
  -- nvram.bin: md5 OK; 
  -- userdata_nvram_only.tar: md5 OK; 
  -- nodl_protect_f.ext4.img: md5 OK; 
  -- nodl_protect_f.ext4.tar: md5 OK; 
  -- nodl_protect_s.ext4.img: md5 OK; 
  -- nodl_protect_s.ext4.tar: md5 OK; 
  -- nodl_seccfg: md5 OK; 
  -- lk.bin: md5 OK;  ... it is copied 
  -- boot.img: md5 OK;  ... it is copied 
  -- recovery.img: md5 OK;  ... it is copied 
  -- secro.img: md5 OK;  ... it is copied 
  -- nodl_misc: md5 OK; 
  -- logo.bin: md5 OK;  ... it is copied 
  -- nodl_expdb: md5 OK; 
  -- system.ext4.img: md5 OK;  ... it is copied 
 --- copying is complete  ---

 --->>> Connect to device <<<---
 

rajit

Senior Member
Oct 13, 2012
895
853
kolkata
geek2gyaan.blogspot.com
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones

and here is my log, notice the bolded and underlined letters, i need help :( thanks in advance :)

Code:
In system already available:  Android Debug Bridge version 1.0.31

 --->>> Connect to device <<<---
 --- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
 --- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
 --- scatter is write to the file: 
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
 --- We keep blocks: 
 - preloader_and_dsp
 - MBR
 - EBR1
 - nodl_pro_info
 - nvram.bin
 - userdata_nvram_only.tar
 - nodl_protect_f.ext4.img
 - nodl_protect_f.ext4.tar
 - nodl_protect_s.ext4.img
 - nodl_protect_s.ext4.tar
 - nodl_seccfg
 - lk.bin
 - boot.img
 - recovery.img
 - secro.img
 - nodl_misc
 - logo.bin
 - nodl_expdb
 - system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
 --- We keep folders contents copying on PC 
   - /data/nvram
   - /system
  --- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR  ---[/B][/U]
 --- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
  -- preloader_and_dsp: md5 OK;  ... it is copied  ... cut OK
  -- MBR: md5 OK;  ... it is copied 
  -- EBR1: md5 OK;  ... it is copied 
  -- nodl_pro_info: md5 OK; 
  -- nvram.bin: md5 OK; 
  -- userdata_nvram_only.tar: md5 OK; 
  -- nodl_protect_f.ext4.img: md5 OK; 
  -- nodl_protect_f.ext4.tar: md5 OK; 
  -- nodl_protect_s.ext4.img: md5 OK; 
  -- nodl_protect_s.ext4.tar: md5 OK; 
  -- nodl_seccfg: md5 OK; 
  -- lk.bin: md5 OK;  ... it is copied 
  -- boot.img: md5 OK;  ... it is copied 
  -- recovery.img: md5 OK;  ... it is copied 
  -- secro.img: md5 OK;  ... it is copied 
  -- nodl_misc: md5 OK; 
  -- logo.bin: md5 OK;  ... it is copied 
  -- nodl_expdb: md5 OK; 
  -- system.ext4.img: md5 OK;  ... it is copied 
 --- copying is complete  ---

 --->>> Connect to device <<<---

i think in your case you should use latest mtk tools as mtk6572 is new :D
 

rajit

Senior Member
Oct 13, 2012
895
853
kolkata
geek2gyaan.blogspot.com
thanks sir, but i already fixed that. my problem now is, mtk droid tools did not generate a backup image of ANDROID, USRDATA, and CACHE .. which is all needed in SPFT .. how can i fix it ? please ? thanks :)

I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out
 

xlSKYFiRElx

Senior Member
Apr 24, 2014
78
7
Sector One
I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out

well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated :confused:
 
Jun 3, 2014
10
0
Bucharest
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones

and here is my log, notice the bolded and underlined letters, i need help :( thanks in advance :)

Code:
In system already available:  Android Debug Bridge version 1.0.31

 --->>> Connect to device <<<---
 --- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
 --- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
 --- scatter is write to the file: 
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
.........
 - nodl_expdb
 - system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
 --- We keep folders contents copying on PC 
   - /data/nvram
   - /system
  --- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR  ---[/B][/U]
 --- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
  .................

 --->>> Connect to device <<<---
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.
 
Last edited:

Vicky khan

Senior Member
Apr 14, 2013
159
14
How Much time Does it Usually takes !

Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ? :confused:
 

Domcek

Senior Member
Oct 7, 2008
161
26
Zagreb
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.

... Also check your internal SD for free space as some of the backups can end up in cwm folder.

Sent from my NOA H42 using Tapatalk

---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------

Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ? :confused:

It can last up to an hour depending of PC, used data and system space, etc.
 

xdafan666

Member
Nov 1, 2013
35
3
well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated :confused:

I backup apps, userdata and cache with Titanium Backup. After a nandroid restore (e.g., CWM) Titanium Backup does the rest. Hope this helps.

Btw, Looking forward to your Firefly S120 (aka Cubot C11) custom ROMs ;)
 

nestea57

Member
Dec 12, 2012
38
1
Hello,
This way doesn't work.
It needs to backup every data on the phone from root !
This way backup only the system folder... Then, every apps data are not saved.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    How to Make a full backup ROM for MT6592,MT6589, MT6582, MT6577, MT6575, MT6572, MT6516 phones. This is basically for all MTK phones from MediaTek.

    This is also a great way to share your firmware with someone who may need the stock ROM for their bricked phone. Or if you're the bricked one, you can direct someone with the same phone as you to this tutorial so they can prepare their ROM for you.

    Important: Make sure to accept any SuperSU or SuperUser permission requests your phone may ask for while you're doing these steps. Any firewall requests your PC may have installed, also allow.

    The tutorial will show you how to:

    - make a full backup of your ROM (firmware)
    - make the ROM firmware ready for SP Flash Tools

    What you need:

    - A rooted MTK phone

    - BusyBox (can be downloaded from Google Play)

    - MTK Droid Tools v2.5.0 Download Here

    - ADB drivers Download Here or Here(so your computer can communicate with your rooted phone)

    A) Prepare your phone and get the utilities we'll need

    1. Enable debugging mode on your phone. From your homescreen, tap the Menu button > Settings > Development. Tap 'Debug Mode' and make sure it's checked.

    2. Install BusyBox. Go to Google Play and search 'BusyBox' and install.

    3. Install PDANet ADB Drivers. Download from here. Run the download and follow the instructions. A USB cable is required to connect your phone to your PC. After installing the drivers, keep your phone connected.

    4. Download MTK Droid Tools 2.5.0 and extract to a known location on your PC.

    B) Open ADB prompt to begin communication with the phone

    1. Go into the extracted MTK Droid Tools folder from step 4 and right-click on 'MTKdroidTools.exe'. Select 'Run as administrator'.

    2. Wait several seconds while MTK Droid Tools communicates with your phone. You'll eventually see the main screen come up with all of your phone's information. Look in the bottom left hand corner of the main window, you should see a green square. If it's yellow, you can try to click the 'root' button in MTK Droid Tools to get temporary root shell. If this doesn't work, and you've already got CWM, alternatively you can boot into CWM and then the little square should be green.

    C) Read back the ROM with MTK Droid Tools

    1. Go back to the main menu of MTK Droid Tools and select the 'Root, Backup, Recovery' tab.

    2. Click the 'Backup' button. You will see MTK Droid Tools start to read all the data from your phone Smile. This can take awhile. So let it do it's thing. Have a coffee, whatever.

    3. After it's finished reading back the ROM, another window will pop up asking you if you'd like to compress the image. Better to select 'Yes'. This will save space and make it into one tight package. MTK Droid Tools will then pack it up into a zip and then let you know it's finished.
    İmage
    backup_jpg2.jpg

    D) Prepare the data from MTK Droid Tools for SP Flash Tools

    1. In the MTK Droid Tools 'root, backup, recovery', you will a button that says 'To prepare blocks for Flash Tool'. Click it.

    2. A new explorer window will open directly to the backups folder that MTK Droid Tools made. Select your phone's backup folder. It will look something like *your phone*-backup-YYMMDD. Open this folder.

    3. Inside your phone's backup folder, you will see a file called 'files.md5'. Select this and the process will start Smile

    4. This will take a while. Go have another coffee or shot of whiskey, smoke a joint. Whatever your like.

    5. After it's finished, open the folder where you extracted MTK Droid Tools. There you will see a folder called 'backup'. Open this folder, then open the folder for your phone (*your phone*-backup-YYMMDD). There will be a folder called '!Files_to_FlashTool'. That's the folder to use for flashing with SP Flash Tools! Smile

    flashtool.jpg


    This Guide can be Found on Chianaforums, but i poste specialy becuse of many Q700/Q700i users still unkown from this :(

    Credit:-
    @yuweng , @rua1 still don't know who is the developer of this app, if anything missing PM me :highfive:
    3
    Here is how to backup your device for those more interested in how it works.

    Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.

    Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.

    Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.


    Code:
    preloader    0x0000000000c00000   0x0000000000000000   2   /dev/misc-sd
    mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0
    ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1
    pmt          0x0000000000400000   0x0000000000100000   2   /dev/block/mmcblk0
    pro_info     0x0000000000300000   0x0000000000500000   2   /dev/block/mmcblk0
    nvram        0x0000000000500000   0x0000000000800000   2   /dev/block/mmcblk0
    protect_f    0x0000000000a00000   0x0000000000d00000   2   /dev/block/mmcblk0p2
    protect_s    0x0000000000a00000   0x0000000001700000   2   /dev/block/mmcblk0p3
    seccfg       0x0000000000020000   0x0000000002100000   2   /dev/block/mmcblk0
    uboot        0x0000000000060000   0x0000000002120000   2   /dev/block/mmcblk0
    bootimg      0x0000000000600000   0x0000000002180000   2   /dev/block/mmcblk0
    recovery     0x0000000000a00000   0x0000000002780000   2   /dev/block/mmcblk0
    sec_ro       0x0000000000600000   0x0000000003180000   2   /dev/block/mmcblk0p4
    misc         0x0000000000080000   0x0000000003780000   2   /dev/block/mmcblk0
    logo         0x0000000000300000   0x0000000003800000   2   /dev/block/mmcblk0
    expdb        0x0000000000a00000   0x0000000003b00000   2   /dev/block/mmcblk0
    android      0x0000000040000000   0x0000000004500000   2   /dev/block/mmcblk0p5
    cache        0x000000002bc00000   0x0000000044500000   2   /dev/block/mmcblk0p6
    usrdata      0x000000033a220000   0x0000000070100000   2   /dev/block/mmcblk0p7
    bmtpool      0x0000000001500000   0x00000000ff3f00a8   2   /dev/block/mmcblk0

    As you can see it gives you the block device used for the partition and the size and start of the position on that device.

    Sent from my A1-810 using XDA Premium HD app
    1
    Please rate the thread 5stars For support And Press thanks Too :D
    1
    This post has made my day, and it seems to be only method for my tablet to get its rom dumped. I tried emmc and mtd but didnt work. Now as i made the recovery.img in my sd with the help of mentioned command, how do we supposed to know the bs count and skip stuff of a partition? so that i can make a complete dump. Any help will be highly appriciated and will complete my research on this topic. Thanks

    you get that info from
    dumchar_info
    1
    you get that info from
    dumchar_info
    i am also having this same issue. By using this command "dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112" dumping of recovery.img was successful but i can't figure out the bs, count and skip for boot.img. can you please explain how to find those values to dump boot.img or any other partitions.

    This is the output of my dumchar_info:
    Part_Name Size StartAddr Type MapTo
    preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
    mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
    ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
    pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
    nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
    protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
    protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
    seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
    uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
    bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0
    recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0
    sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4
    misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0
    logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0
    expdb 0x0000000000a00000 0x0000000004700000 2 /dev/block/mmcblk0
    android 0x0000000071c00000 0x0000000005100000 2 /dev/block/mmcblk0p5
    cache 0x0000000010400000 0x0000000076d00000 2 /dev/block/mmcblk0p6
    usrdata 0x0000000149680000 0x0000000087100000 2 /dev/block/mmcblk0p7
    bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
    Part_Name:partition name you should open;
    Size:size of partition
    StartAddr:Start Address of partition;
    Type:Type of partition(MTD=1,EMMC=2)
    MapTo:actual device you operate

    Edit: I figured it out myself. and made a simple guide also on it. thx btw. guide: http://xdaforums.com/general/general/guide-dumping-boot-img-recovery-img-t3339530