How to completely backup your Chinaphone !

30

itxtutor

Editor in Chief
Staff member
May 15, 2015
60,078
1
113
Good evening (morning
) ,


Here comes a updated guide on how to backup your chinaphone for mtk based smartphones



You can also find written guides and downloads here :


Downloads:

PDAnet ADB drivers
http://pdanet.co/

MTK Droid tools v2.5.3
https://www.4shared.com/rar/YhjJpFkKba/mtkdroidtools_v253.html


2) Readback + Root Tutorial

https://www.china-devices.com/forum/index.php?threads/root-cwm-readback-your-rom-with-sp-flash-tools.12958/

Just follow the steps shown in the video:

https://www.youtube.com/watch?v=s66e-kwvKUU
 
Last edited by a moderator:
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
great new tutorial steven...covered every angle...:DD
 
2

djtetei

Member
Jan 24, 2015
33
0
8
42
Braila
DEVICE:




  • Brand: ALLVIEW
  • Model: X2 SOUL (Gionee Elife S5.5 clone)





PREVIOUS PHONE SPECIFICATIONS (displayed by MTK Droid Tools 2.5.3):

  • Hardware : MT6592
  • Model : X2_Soul
  • Build number : X2_Soul
  • Build date UTC : 20140915-033605
  • Android  v : 4.4.2
  • Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P5, 2014/06/07 10:47
  • Kernel v : 3.4.67 (android@ANDROID8) (gcc version 4.7 (GCC) ) #1 SMP  Mon Sep 15 10:30:01 HKT 2014

The device is not fitted with SD Card slot!


PHONE STATUS:

  • CWM Recovery installed
  • Rooted

The device manufacturer provides O.T.A. (Over The Air) updates only.


TASK 1:

  • Install the new update released by manufacturer.
ACTIONS:

  • Flash back stock factory recovery.img (SUCCESS)
  • Install the new firmware update (SUCCESS)

CURRENT PHONE SPECIFICATIONS (displayed by MTK Droid Tools 2.5.3):

  • Hardware : MT6592
  • Model : X2_Soul
  • Build number : X2_Soul
  • Build date UTC : 20150127-152019
  • Android  v : 4.4.2
  • Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/11/11 18:23
  • Kernel v : 3.4.67 (android@android-desktop2) (gcc version 4.7 (GCC) ) #1 SMP  Tue Jan 27 22:11:29 CST 2015


TASK 2:

  • Backup the new firmware update.
ACTIONS:

  • Read back the ROM in SP Flash Tool (SUCCESS)
  • Process the ROM from SP Flash Tool in MTK Droid Tools (SUCCESS)
  • Create patch BOOT image and CWM Recovery image (SUCCESS)

TASK 3:

  • Install CWM Recovery image
ACTIONS:

  • Open SP Flash Tool
  • Load the scatter file
  • Check RECOVERY only and enter the path to CWM Recovery image
  • Download CWM Recovery image to device (SUCCESS)

TASK 4:

  • Root the device and install Busybox
ACTIONS:

  • Boot in CWM Recovery
  • Install UPDATE-SuperSU-v2.45.zip
  • Reboot device from CWM Recovery
  • Install Root Explorer
  • Remove (delete) recovery-from-boot.p file
  • Install Busybox
  • Install Root Checker and verify root access and Busybox installation status (SUCCESS)

TASK 5:

  • Backup the ROM in MTK Droid Tools
ACTIONS:

  • Turn on the device
  • Open MTK Droid Tools 2.5.3
  • Device is detected with YELLOW status color
  • Press the "ROOT" button to obtain root shell access (SUCCESS)
  • Go to "Root, backup, recovery" tab
  • Select "BACKUP"

RESULT:

  • ERROR :  Zero file, no space left on device!

MTK Droid Tools 2.5.3 - LOG EXTRAS

06/02/15 22:34:52 -----------Start------------ v2.5.3 (1390155029) 19.01.2014 18:10:29


06/02/15 22:34:52 UserLanguage =Romanian


06/02/15 22:34:52 In system already available:  Android Debug Bridge version 1.0.31


06/02/15 22:34:57 * daemon not running. starting it now on port 5037 *


06/02/15 22:34:57 * daemon started successfully *


06/02/15 22:35:01 Last version v2.5.3


06/02/15 22:35:01 Maked 1387564576


06/02/15 22:35:01 URL http://dfiles.ru/files/ne1gnposp


06/02/15 22:35:03


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


06/02/15 22:35:03 -rwxrwxrwx shell    shell      795076 2012-06-29 11:18 recovery


06/02/15 22:35:03 /system/etc/firmware/modem_1_wg_n.img


06/02/15 22:35:03 MT6592_S00


06/02/15 22:35:03 3+0 records out


06/02/15 22:35:03 12 bytes (12B) copied, 0.001209 seconds, 9.7KB/s


06/02/15 22:35:03 Hardware : MT6592


06/02/15 22:35:03 Part_Name    Size    StartAddr    Type    MapTo    Region


06/02/15 22:35:03 preloader    0x0000000000040000   0x0000000000000000   2   /dev/misc-sd     BOOT_1


06/02/15 22:35:03 mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1   USER


06/02/15 22:35:03 pro_info     0x0000000000300000   0x0000000000100000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 nvram        0x0000000000500000   0x0000000000400000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 protect_f    0x0000000000a00000   0x0000000000900000   2   /dev/block/mmcblk0p2   USER


06/02/15 22:35:03 protect_s    0x0000000000a00000   0x0000000001300000   2   /dev/block/mmcblk0p3   USER


06/02/15 22:35:03 seccfg       0x0000000000040000   0x0000000001d00000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 uboot        0x0000000000060000   0x0000000001d40000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 bootimg      0x0000000000a00000   0x0000000001da0000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 recovery     0x0000000000a00000   0x00000000027a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 sec_ro       0x0000000000600000   0x00000000031a0000   2   /dev/block/mmcblk0p4   USER


06/02/15 22:35:03 misc         0x0000000000080000   0x00000000037a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 logo         0x0000000000800000   0x0000000003820000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 ebr2         0x0000000000080000   0x0000000004020000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 expdb        0x0000000000a00000   0x00000000040a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 spdata       0x0000000000d60000   0x0000000004aa0000   2   /dev/block/mmcblk0p5   USER


06/02/15 22:35:03 android      0x000000004d000000   0x0000000005800000   2   /dev/block/mmcblk0p6   USER


06/02/15 22:35:03 cache        0x0000000008000000   0x0000000052800000   2   /dev/block/mmcblk0p7   USER


06/02/15 22:35:03 usrdata      0x0000000100000000   0x000000005a800000   2   /dev/block/mmcblk0p8   USER


06/02/15 22:35:03 fat          0x0000000248100000   0x000000015a800000   2   /dev/block/mmcblk0p9   USER


06/02/15 22:35:03 bmtpool      0x0000000000000000   0x00000000ffff00a8   2   /dev/block/mmcblk0     USER


06/02/15 22:35:03 Part_Name:Partition name you should open;


06/02/15 22:35:03 Size:size of partition


06/02/15 22:35:03 StartAddr:Start Address of partition;


06/02/15 22:35:03 Type:Type of partition(MTD=1,EMMC=2)


06/02/15 22:35:03 MapTo:actual device you operate


06/02/15 22:35:03 rootfs on / type rootfs (rw,seclabel,relatime)


06/02/15 22:35:03 tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)


06/02/15 22:35:03 devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)


06/02/15 22:35:03 proc on /proc type proc (rw,relatime)


06/02/15 22:35:03 sysfs on /sys type sysfs (rw,seclabel,relatime)


06/02/15 22:35:03 selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)


06/02/15 22:35:03 none on /acct type cgroup (rw,relatime,cpuacct)


06/02/15 22:35:03 none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)


06/02/15 22:35:03 tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)


06/02/15 22:35:03 tmpfs on /mnt/asec type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)


06/02/15 22:35:03 tmpfs on /mnt/obb type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)


06/02/15 22:35:03 none on /dev/cpuctl type cgroup (rw,relatime,cpu)


06/02/15 22:35:03 /emmc@android on /system type ext4 (ro,seclabel,relatime,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:35:03 /emmc@usrdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)


06/02/15 22:35:03 /emmc@cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)


06/02/15 22:35:03 emmc@spdata on /spdata type ext4 (rw,seclabel,relatime,data=ordered)


06/02/15 22:35:03 /emmc@protect_f on /protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:35:03 /emmc@protect_s on /protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:35:03 /dev/block/loop0 on /mnt/cd-rom type iso9660 (ro,relatime)


06/02/15 22:35:03 /dev/block/vold/179:9 on /mnt/media_rw/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)


06/02/15 22:35:03 /dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)


06/02/15 22:35:03 /dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)


06/02/15 22:35:03 Model : X2_Soul


06/02/15 22:35:03 Build number : X2_Soul


06/02/15 22:35:03 Build date UTC : 20150127-152019


06/02/15 22:35:04 Android  v : 4.4.2


06/02/15 22:35:04 ls: /system/recovery-from-boot.p: No such file or directory


06/02/15 22:35:04 Kernel v : 3.4.67 (android@android-desktop2) (gcc version 4.7 (GCC) ) #1 SMP  Tue Jan 27 22:11:29 CST 2015


06/02/15 22:35:04  --- NOT Root Shell


06/02/15 22:35:04 ls: /system/bin/su: No such file or directory


06/02/15 22:35:04 -rwxr-xr-x 1 root root 75364 Feb 6 19:05 /system/xbin/su


06/02/15 22:35:04 Uboot build v : ----- should be  root shell


06/02/15 22:35:04 LCD Driver IC : ----- should be  root shell


06/02/15 22:35:04 Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/11/11 18:23


06/02/15 22:35:12  --- ROOT button


06/02/15 22:35:19 ATTENTION! Requests for confirmation on the device screen are possible!


06/02/15 22:35:19 uid=0(root) gid=0(root)


06/02/15 22:35:20 -rw-rw-rw-    1 shell    shell       146744 Jan 29  2013 /data/local/tmp/adbd


06/02/15 22:35:20 mount: mounting rootfs on / failed: Device or resource busy


06/02/15 22:35:20 -rwxr-x---    1 root     root        146744 Feb  6 20:35 /sbin/adbd


06/02/15 22:35:27  --- ROOT Shell


06/02/15 22:35:27 LCD Driver IC : 0-gn_samsung_s6e8fa0x01


06/02/15 22:35:27  --- root shel it is received temporarily before reboot !


06/02/15 22:37:13  --- Disconnect from device


06/02/15 22:44:24


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


06/02/15 22:44:24 -rwxrwxrwx shell    shell      795076 2012-06-29 11:18 recovery


06/02/15 22:44:24 /system/etc/firmware/modem_1_wg_n.img


06/02/15 22:44:24 MT6592_S00


06/02/15 22:44:24 3+0 records out


06/02/15 22:44:24 12 bytes (12B) copied, 0.000599 seconds, 19.6KB/s


06/02/15 22:44:24 Hardware : MT6592


06/02/15 22:44:24 Part_Name    Size    StartAddr    Type    MapTo    Region


06/02/15 22:44:24 preloader    0x0000000000040000   0x0000000000000000   2   /dev/misc-sd     BOOT_1


06/02/15 22:44:24 mbr          0x0000000000080000   0x0000000000000000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 ebr1         0x0000000000080000   0x0000000000080000   2   /dev/block/mmcblk0p1   USER


06/02/15 22:44:24 pro_info     0x0000000000300000   0x0000000000100000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 nvram        0x0000000000500000   0x0000000000400000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 protect_f    0x0000000000a00000   0x0000000000900000   2   /dev/block/mmcblk0p2   USER


06/02/15 22:44:24 protect_s    0x0000000000a00000   0x0000000001300000   2   /dev/block/mmcblk0p3   USER


06/02/15 22:44:24 seccfg       0x0000000000040000   0x0000000001d00000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 uboot        0x0000000000060000   0x0000000001d40000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 bootimg      0x0000000000a00000   0x0000000001da0000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 recovery     0x0000000000a00000   0x00000000027a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 sec_ro       0x0000000000600000   0x00000000031a0000   2   /dev/block/mmcblk0p4   USER


06/02/15 22:44:24 misc         0x0000000000080000   0x00000000037a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 logo         0x0000000000800000   0x0000000003820000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 ebr2         0x0000000000080000   0x0000000004020000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 expdb        0x0000000000a00000   0x00000000040a0000   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 spdata       0x0000000000d60000   0x0000000004aa0000   2   /dev/block/mmcblk0p5   USER


06/02/15 22:44:24 android      0x000000004d000000   0x0000000005800000   2   /dev/block/mmcblk0p6   USER


06/02/15 22:44:24 cache        0x0000000008000000   0x0000000052800000   2   /dev/block/mmcblk0p7   USER


06/02/15 22:44:24 usrdata      0x0000000100000000   0x000000005a800000   2   /dev/block/mmcblk0p8   USER


06/02/15 22:44:24 fat          0x0000000248100000   0x000000015a800000   2   /dev/block/mmcblk0p9   USER


06/02/15 22:44:24 bmtpool      0x0000000000000000   0x00000000ffff00a8   2   /dev/block/mmcblk0     USER


06/02/15 22:44:24 Part_Name:Partition name you should open;


06/02/15 22:44:24 Size:size of partition


06/02/15 22:44:24 StartAddr:Start Address of partition;


06/02/15 22:44:24 Type:Type of partition(MTD=1,EMMC=2)


06/02/15 22:44:24 MapTo:actual device you operate


06/02/15 22:44:24 rootfs on / type rootfs (rw,seclabel,relatime)


06/02/15 22:44:24 tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)


06/02/15 22:44:24 devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)


06/02/15 22:44:24 proc on /proc type proc (rw,relatime)


06/02/15 22:44:24 sysfs on /sys type sysfs (rw,seclabel,relatime)


06/02/15 22:44:24 selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)


06/02/15 22:44:24 none on /acct type cgroup (rw,relatime,cpuacct)


06/02/15 22:44:24 none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)


06/02/15 22:44:24 tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)


06/02/15 22:44:24 tmpfs on /mnt/asec type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)


06/02/15 22:44:24 tmpfs on /mnt/obb type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)


06/02/15 22:44:24 none on /dev/cpuctl type cgroup (rw,relatime,cpu)


06/02/15 22:44:24 /emmc@android on /system type ext4 (ro,seclabel,relatime,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:44:24 /emmc@usrdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)


06/02/15 22:44:24 /emmc@cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)


06/02/15 22:44:24 emmc@spdata on /spdata type ext4 (rw,seclabel,relatime,data=ordered)


06/02/15 22:44:24 /emmc@protect_f on /protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:44:24 /emmc@protect_s on /protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)


06/02/15 22:44:24 /dev/block/loop0 on /mnt/cd-rom type iso9660 (ro,relatime)


06/02/15 22:44:24 /dev/block/vold/179:9 on /mnt/media_rw/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)


06/02/15 22:44:24 /dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)


06/02/15 22:44:24 /dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)


06/02/15 22:44:24 Model : X2_Soul


06/02/15 22:44:24 Build number : X2_Soul


06/02/15 22:44:24 Build date UTC : 20150127-152019


06/02/15 22:44:24 Android  v : 4.4.2


06/02/15 22:44:24 ls: /system/recovery-from-boot.p: No such file or directory


06/02/15 22:44:24 Kernel v : 3.4.67 (android@android-desktop2) (gcc version 4.7 (GCC) ) #1 SMP  Tue Jan 27 22:11:29 CST 2015


06/02/15 22:44:25  --- ROOT Shell


06/02/15 22:44:25 LCD Driver IC : 0-gn_samsung_s6e8fa0x01


06/02/15 22:44:25 drwxrwxrwx 2 shell shell 4096 Feb 6 18:10 zzz


06/02/15 22:44:25 Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/11/11 18:23


06/02/15 22:45:00 Free space: system- 285.2M; data- 3.6G; media_rw/sdcard0- 9.1G;  E:\ 105703M


06/02/15 22:45:00 -rwxrwxrwx shell    shell      795076 2012-06-29 11:18 recovery


06/02/15 22:45:00  --- Backup Button


06/02/15 22:45:00  --- The preservation folder on the computer: E:\ALLVIEW X2 SOUL\SERVICE TOOLS\MTKDroidTools 2.5.3\backups\X2_Soul_150127_backup_150206-224500\


06/02/15 22:45:00  --- In phone files will remain in the folder: /mnt/media_rw/sdcard0/clockworkmod/backup/150206-224500/


06/02/15 22:45:00  --- scatter is write to the file:





E:\ALLVIEW X2 SOUL\SERVICE TOOLS\MTKDroidTools 2.5.3\backups\X2_Soul_150127_backup_150206-224500\MT6592_Android_scatter.txt


06/02/15 22:45:00  --- We keep blocks:


06/02/15 22:45:00  - preloader_and_dsp


06/02/15 22:45:00 0+0 records in


06/02/15 22:45:00 0+0 records out


06/02/15 22:45:00 0 bytes (0B) copied, 0.002492 seconds, 0B/s


06/02/15 22:45:00  - ERROR :  Zero file, no space left on device!


06/02/15 22:45:01  --- We keep folders contents copying on PC


06/02/15 22:45:01    - /data/nvram


06/02/15 22:45:02    - /system


06/02/15 22:48:37  --- task end with ERROR  ---


06/02/15 22:52:54 -----------End --------------
I repeated the backup operation several times, but I got the same result as above.


If you read the log, you will notice the storage space available is as follows:

  • system: 285.2 MB
  • data: 3.6 GB
  • media_rw/sdcard0: 9.1GB
  • E:\ 105703 MB

QUESTION: Does anyone have any idea what is wrong here?


I am open to any suggestions.


Thank you for your patience!
 
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
the problem is that mtk droid tools is looking for an ex sd card to write the dump to before it passes it onto your p.c....it can be an ass like that sometimes i think it is because your sd card maybe failed to mount in CWM double check there as well,it might only be reading your internal memory you may have to set/reset permissions in CWM,or what i suggest you do is try to backup your NVRAM separately from the rest of the rom and add the file to the backup when complete,same for the other missing files,(data + system) that it stored on your p.c. in a separate folder...then create a new scatter with these files added and you should be ok


also check this folder that these files were dumped into all you may have to do is add them to the scatter just by pointing to the path where they are stored once sp flash tools sees them you can 'create scatter' and you should have a complete rom
 
2

djtetei

Member
Jan 24, 2015
33
0
8
42
Braila
the problem is that mtk droid tools is looking for an ex sd card to write the dump to before it passes it onto your p.c....it can be an ass like that sometimes i think it is because your sd card maybe failed to mount in CWM double check there as well,it might only be reading your internal memory you may have to set/reset permissions in CWM,or what i suggest you do is try to backup your NVRAM separately from the rest of the rom and add the file to the backup when complete,same for the other missing files,(data + system) that it stored on your p.c. in a separate folder...then create a new scatter with these files added and you should be ok


also check this folder that these files were dumped into all you may have to do is add them to the scatter just by pointing to the path where they are stored once sp flash tools sees them you can 'create scatter' and you should have a complete rom
When I performed the backup task the phone was powered on normally, not in CWM recovery mode. So my internal sd card was mounted as media_rw/sdcard0.


My device does not have an external SD card slot.


If for example I want to make a nandroid backup, in CWM recovery mode I select "Backup to internal SD card".


Thank you!
 
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
did you try my other options like backing up the files separately and then adding them to your backup...?


were the other files sitting in a separate folder like mtk droid tools said they were...?
 
2

djtetei

Member
Jan 24, 2015
33
0
8
42
Braila
did you try my other options like backing up the files separately and then adding them to your backup...?


were the other files sitting in a separate folder like mtk droid tools said they were...?
The backup folder contents is:

  • nvram [folder]
  • system [folder]
  • firmware.info
  • mount.info
  • phone.info
No other files were present.


I am beginning to think that MTK Droid Tools has a bug or something, which does not allow to write on internal sd card.


It seems that in these tutorials was assumed that all devices are equipped with an external card slot, which is not always true.


Thank you.
 
Last edited by a moderator:
10

ashis

Member
Aug 18, 2015
38
0
18
Can someone plz post download link for essentials required in the video...

Like MTk droid tools etc.

The link above is not working and i want MTK droiddroid tools..

Help plzz
 
2

MagB

New Member
Aug 26, 2015
3
0
3
2

MagB

New Member
Aug 26, 2015
3
0
3
@itxtutor I have UMI Hammer Android 4.4.4, already rooted. I want to make complete backup of my smartphone using MTK Droid Tools as shown in video made by ITXTutor. As I connected my phone and started the MTK Droid Tools, the tools shows yellow and the log message shows "connect to device" and "--- ERROR  :  --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!". If I click "Root", the indicator becomes green and shows HAMMER (root access). So I don´t continue the further steps (Click "Backup", etc.) since I am afraid I will brick my phone or something.

Moreover: I can´t create scatter file thru "Blocks map", since the button "Create scatter file" is disabled.

Please help. Thank you in advance.
 
Last edited by a moderator:
10

ashis

Member
Aug 18, 2015
38
0
18
Hey mrsim,

In the video above showing back p guide..

If my phone is rooted i only need to backup through MTK droid tools and then install CWM recovery..

Or then backup using sp flash tool as well
 
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
@itxtutor I have UMI Hammer Android 4.4.4, already rooted. I want to make complete backup of my smartphone using MTK Droid Tools as shown in video made by ITXTutor. As I connected my phone and started the MTK Droid Tools, the tools shows yellow and the log message shows "connect to device" and "--- ERROR  :  --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!". If I click "Root", the indicator becomes green and shows HAMMER (root access). So I don´t continue the further steps (Click "Backup", etc.) since I am afraid I will brick my phone or something.

Moreover: I can´t create scatter file thru "Blocks map", since the button "Create scatter file" is disabled.

Please help. Thank you in advance.
@MagB,

mtk droid tools has not been updated to work with the new 64bit SoC so you cannot really use it for making a full backup with these new devices....the best place to look for a rom for your device would be needrom.com

http://www.needrom.com/category/umi/umi-hammer/

Hey mrsim,

In the video above showing back p guide..

If my phone is rooted i only need to backup through MTK droid tools and then install CWM recovery..

Or then backup using sp flash tool as well
@ashis

well mtk droid tools is for backing up devices stock rom and also for creating CWM if needed for your device,(mtk 6592 and below not new 64bit SoC) and sp flash tools is for flashing roms onto devices,(all mtk versions depending on SoC only latest versions can flash 64bit SoC),...you cannot use sp flash tools to make a backup of your devices rom...sorry
 
Last edited by a moderator:
10

ashis

Member
Aug 18, 2015
38
0
18
Ok then, plzz post any link or video tutorial for creating CWM using MTK droid tools
 
Last edited by a moderator:
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
2

knightston

New Member
Dec 8, 2015
9
0
3
Hey, i manage to root my samsung s6 clone with iroot, and then try to back up the rom as per advice by sir @mrsim
 so i search the site and got here, when my unit detected by mtk droid, there's the info, as you can see i got the fake hardware, how to resolve it? second, when i press the root to obtain the root shield, a pop up message show, when press yes, (see another image), but when press no, another error appear, see another image.


How can i fully root my device?


View attachment 3206


View attachment 3207


View attachment 3208


View attachment 3209


 
 
Last edited by a moderator:
2

bopy

New Member
Jan 19, 2016
9
0
3
Hi!


Thank you for your tutorial. It doesnt work for me though. I get --- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!


Redmi Note 2 16GB / MIUI 16.6.7.0 (vendor custom ROM) + root / busybox 1.23.1-stericson / internal storage 9GB free, SD 31GB free
Win 8.1 / MtkDroidTools v2.5.3 / connected Redmi Note 2 (root shell)


Everywhere I look the following fixes are suggested:

- Install Busybox (check)
- Download MTK droid tools from a different source (check) (check) (check)
- Slot in an SD card with sufficient space into the phone (check)
- When prompted for Super User permissions on the phone and PC, select Ok or Grant (check)

Well, Im out. In addition start addresses under Blocks Map are different than addresses in downloaded MT6795_Android_scatter.txt (3 different sources, supposed to be for RN2). And also IMEI doesnt show in MTKDT phone information but it does show on the phone.
I would really appreciate some help.
Thank you
 
Last edited by a moderator:
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
Hi!


Thank you for your tutorial. It doesnt work for me though. I get --- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!


Redmi Note 2 16GB / MIUI 16.6.7.0 (vendor custom ROM) + root / busybox 1.23.1-stericson / internal storage 9GB free, SD 31GB free
Win 8.1 / MtkDroidTools v2.5.3 / connected Redmi Note 2 (root shell)


Everywhere I look the following fixes are suggested:

- Install Busybox (check)
- Download MTK droid tools from a different source (check) (check) (check)
- Slot in an SD card with sufficient space into the phone (check)
- When prompted for Super User permissions on the phone and PC, select Ok or Grant (check)

Well, Im out. In addition start addresses under Blocks Map are different than addresses in downloaded MT6795_Android_scatter.txt (3 different sources, supposed to be for RN2). And also IMEI doesnt show in MTKDT phone information but it does show on the phone.
I would really appreciate some help.
Thank you
if this is the redmi note,(new version),with mtk6795 then mtk droid tools will not work with this SoC...it has not been updated for a while and i doubt will ever be updated for the newer mtk versions mtk67xx...you will need to locate a stock rom online instead and use 'mobile uncle toolbox,(latest version),to backup your IMEI numbers just for safety
 
2

bopy

New Member
Jan 19, 2016
9
0
3
if this is the redmi note,(new version),with mtk6795 then mtk droid tools will not work with this SoC...it has not been updated for a while and i doubt will ever be updated for the newer mtk versions mtk67xx...you will need to locate a stock rom online instead and use 'mobile uncle toolbox,(latest version),to backup your IMEI numbers just for safety
Thank you for your reply.


Yes, this is Redmi Note 2 with mt6795. I never realized it is not supported. I have been through hundreds of pages and information is so dispersed its imposible to get to the bottom of things, at least not in a reasonable time frame. So thank you again. I have sort of expected this phone to be uber supported being sold in millions. I guess Xiaomi and Mediatek have to do their part.


I have allready installed Mobileuncle tools but unfortunately mt6795 is not supported (googling "mobileuncle tools supported chipsets" doesnt return anything useful, its trial and error :). I have also used Flashify and Partitions Backup but I doubt those backups will be of use in event of emergency. Well, its better than nothing. Flashify also is suggested for backing up IMEI/NVRAM but again no option on my phone to do that. Twrp 2.8.7 materialized hopefully will work as per en.miui.com. Some other idea?


Maybe just one more question: being that mt6795 is not supported in mtk droid tools should I disregard Blocks Map and go with MT6795_Android_scatter.txt?  Three sources say this scatter is for Redmi Note 2 (one is tutorial by a moderator on official en.miui.com forum) and it is needed for SP Flash Tool. I ask because so far nothing has worked on my phone and I am sort of freaked.


Thank you again.


 
 
30

mrsim

KingOfNoobs
Staff member
Mar 1, 2014
16,174
1
113
48
London UK
Thank you for your reply.


Yes, this is Redmi Note 2 with mt6795. I never realized it is not supported. I have been through hundreds of pages and information is so dispersed its imposible to get to the bottom of things, at least not in a reasonable time frame. So thank you again. I have sort of expected this phone to be uber supported being sold in millions. I guess Xiaomi and Mediatek have to do their part.


I have allready installed Mobileuncle tools but unfortunately mt6795 is not supported (googling "mobileuncle tools supported chipsets" doesnt return anything useful, its trial and error :). I have also used Flashify and Partitions Backup but I doubt those backups will be of use in event of emergency. Well, its better than nothing. Flashify also is suggested for backing up IMEI/NVRAM but again no option on my phone to do that. Twrp 2.8.7 materialized hopefully will work as per en.miui.com. Some other idea?


Maybe just one more question: being that mt6795 is not supported in mtk droid tools should I disregard Blocks Map and go with MT6795_Android_scatter.txt?  Three sources say this scatter is for Redmi Note 2 (one is tutorial by a moderator on official en.miui.com forum) and it is needed for SP Flash Tool. I ask because so far nothing has worked on my phone and I am sort of freaked.


Thank you again.


 
try this mobile uncle toolbox...it supports mtk67xx devices


 





 


also MIUI forums is the best place to get yourself a backup rom for this device...or to change the rom to the global developer version which receives updates about once a week,i had one of these devices,(prime version),and after flashing the global developer rom sold it to a mate because he needed a phone...this is really the best forum for all things xiaomi,also 'mtk droid tools was not created by mediatek...a russian guy created it but he seems to have gone off the radar for the last year or so..?


http://en.miui.com/forum-83-1.html
 
Last edited by a moderator:
2

bopy

New Member
Jan 19, 2016
9
0
3
The first few days I did use en.miui but I had so many questions (from severely noob ones to advanced ones) that I had to jump all around the web. Im glad because you have really helped me. With info and MUT v3.1.4 (it works). THANK YOU. For a newcomer the most trivial things are the most hidden. Although I sort of knew mtkdt was not created by mediatek but I figured they are hiding info on their chipset. lol


Also, I am trying to backup current vendor bloatware spyware custom ROM to keep 2 year warranty. Seller said all they care about is it comes in the same state I received it in. I guess only way is nandroid backup. Hope it works.


I was also considering unofficial weekly from http://xiaomi.eu but I guess at this point it is safer to go official first and then see. To confuse things further Xiaomi just started to lock bootloader on some devices so unofficial comes back into play. This "want to be a bit more advanced user" is not easy at all. :)


 


Thanks a million


M
 
Last edited by a moderator:
Help Users

You haven't joined any rooms.

    You haven't joined any rooms.