[Q] MTK 6589 - Recovery Creation - Android Q&A, Help & Troubleshooting
Hi.
I have a Feiteng H7189 with MTK 6589 and Android 4.2.1
I have rooted it
I have taken the scatter file with MTKDroid
I have taken the Recovery.IMG with ADB
I want to compite a new recovery with CWM or TWRP
I have tried but all the file I create do not work
If I put again the original recovery.img all fine
Anyone can compile a recovery form me ? Thanks
here the scatter and the recovery original:
www ddlstorage com/jtav2acevcnn/recovery_H7189.rar.htm
Here some info to compile:
[email protected]:/ $ cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 2439.94
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 2
Hardware : MT6589
Revision : 0000
Serial : 0000000000000000
[email protected]:/ $
[email protected]:/ $ cat /proc/dumchar_info
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 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 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003400000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003700000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002cb80000 2 /dev/block/mmcblk0p6
usrdata 0x0000000040000000 0x0000000034980000 2 /dev/block/mmcblk0p7
fat 0x0000000071180000 0x0000000074980000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Nameartition 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
[email protected]:/ $
Use this to easily make and flash your own cwm for mtk6589 devices...http://forum.xda-developers.com/showthread.php?t=2379412
Related
Start addresses in MTKDroidTool log does not match start adresses in scatter file
I'm new to XDA developer and I registered because I would like to share my findings to the MTKDroidTool developers. I am using MTKDroidTool 2.4.3 and SP_Flash_Tool_v3.1252.1.104 to root a CAT B15 and these tools work fine. While looking in the MTKDroidTool log files, I noticed a difference in start addresses between the log and scatter files. The MTKDroidTool gives the following start addresses in the logfile: Part_Name Size StartAddr Type MapTo preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 ebr1 0x0000000000004000 0x0000000000080000 2 /dev/block/mmcblk0p1 pmt 0x0000000000400000 0x0000000000084000 2 /dev/block/mmcblk0 nvram 0x0000000000500000 0x0000000000484000 2 /dev/block/mmcblk0 seccfg 0x0000000000080000 0x0000000000984000 2 /dev/block/mmcblk0 uboot 0x0000000000080000 0x0000000000a04000 2 /dev/block/mmcblk0 bootimg 0x0000000000600000 0x0000000000a84000 2 /dev/block/mmcblk0 recovery 0x0000000000600000 0x0000000001084000 2 /dev/block/mmcblk0 sec_ro 0x0000000000600000 0x0000000001684000 2 /dev/block/mmcblk0p2 misc 0x0000000000080000 0x0000000001c84000 2 /dev/block/mmcblk0 ogo 0x0000000000300000 0x0000000001d04000 2 /dev/block/mmcblk0 expdb 0x0000000000200000 0x0000000002004000 2 /dev/block/mmcblk0 android 0x0000000020100000 0x0000000002204000 2 /dev/block/mmcblk0p3 cache 0x0000000020100000 0x0000000022304000 2 /dev/block/mmcblk0p4 usrdata 0x0000000040000000 0x0000000042404000 2 /dev/block/mmcblk0p5 The Scatter files shows: PRELOADER 0x0 DSP_BL 0x40000 MBR 0x600000 EBR1 0x680000 __NODL_PMT 0x684000 __NODL_NVRAM 0xa84000 __NODL_SECCFG 0xf84000 UBOOT 0x1004000 BOOTIMG 0x1084000 RECOVERY 0x1684000 SEC_RO 0x1c84000 __NODL_MISC 0x2284000 LOGO 0x2304000 __NODL_EXPDB 0x2604000 ANDROID 0x2804000 CACHE 0x22904000 USRDATA 0x42a04000 __NODL_FAT 0x82a04000 __NODL_BMTPOOL 0xffff00a8 The mismatches seems to start at EBR1, the scatter files says that the start address equals 0x680000 but the logfile states 0x080000. It seems that the values in the logfile at the following mask 0xff00000 are not correct. The scatter file is correct because I rooted my phone successfully but the logfile appears to be off. The logfile states '10' while the scatter file says 'a' and so on. Are my findings correct and is the information above enough to help the MTKDroidTool developers?
[Q] Can't flash CWMR for BLU Dash 4.0
Hello everyone. Today I tried to flash Clockworkmod Recovery following the instructions in this video: youtube[DOT]com/watch?v=e5oWt_mpNpw ...Since I cant access downloading mode on my device (a chinese factory menu comes up) I instead went into fastboot mode and tried to flash the recovery image in the video, but when I do I get this error: "partition recovery not support flash". I did some research and found out that my recovery is in a combined partition called mmcblk0. How do I flash it? I used Code: dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=37224448 and got (what i think) is my recovery image. Also, these are py partitions Code: [email protected]:/ # cat /cache/recovery/last_log cat /cache/recovery/last_log Starting recovery on Thu Apr 10 02:26:23 2014 Partition Information: preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0 recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0 sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0 misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0 logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0 expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0 android 0x0000000028a00000 0x0000000003740000 2 /dev/block/mmcblk0p4cache 0x0000000017800000 0x000000002c140000 2 /dev/block/mmcblk0p5usrdata 0x0000000052c00000 0x0000000043940000 2 /dev/block/mmcblk0p6fat 0x00000000513e0000 0x0000000096540000 2 /dev/block/mmcblk0p7bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0 recovery filesystem table ========================= 0 /tmp ramdisk (null) (null) 0 1 /boot emmc boot (null) 0 2 /cache ext4 /dev/block/mmcblk0p5 (null) 0 3 /data ext4 /dev/block/mmcblk0p6 (null) 0 4 /misc emmc misc (null) 0 5 /recovery emmc recovery (null) 0 6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p7 0
ota update
please help i have a kazam trooper x4.5 i tried to do system update over ota but it fails but don't no why i have found this log file Starting recovery on Thu Aug 28 10:05:19 2014 Partition Information: preloader 0x0000000000600000 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 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0 recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0 sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0 misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0 logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0 expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0 android 0x0000000028a00000 0x0000000003740000 2 /dev/block/mmcblk0p4 cache 0x0000000017800000 0x000000002c140000 2 /dev/block/mmcblk0p5 usrdata 0x0000000052c00000 0x0000000043940000 2 /dev/block/mmcblk0p6 fat 0x0000000051440000 0x0000000096540000 2 /dev/block/mmcblk0p7 bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0 recovery filesystem table ========================= 0 /tmp ramdisk (null) (null) 0 1 /boot emmc boot (null) 0 2 /cache ext4 /dev/block/mmcblk0p5 (null) 0 3 /data ext4 /dev/block/mmcblk0p6 (null) 0 4 /misc emmc misc (null) 0 5 /recovery emmc recovery (null) 0 6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p7 0 7 /system ext4 /dev/block/mmcblk0p4 (null) 0 I:no boot messages locale is [(null)] can't open /dev/tty0: No such file or directory framebuffer: fd 3 (480 x 854) ioctl(): blank: Invalid argument ioctl(): blank: Invalid argument installing_text: (1 x 1 @ 1896) erasing_text: (1 x 1 @ 1599) no_command_text: (1 x 1 @ 1599) error_text: (1 x 1 @ 1599) Ielta package path name: /data/data/com.redbend.dmClient/files/vdm_update I:Setting recovery boot... I:boot.command=boot-recovery I:boot.recovery=recovery I:chilid return code:62I:Resetting recovery boot... I:boot.command= I:boot.recovery= I:local update package not exist /sdcard/update-gmobi.zip I:android_reboot(ANDROID_RB_RESTART) Rebooting...
[HELP] [MTKDroid Tools] Can't make the CWM Recovery for my Tablet!
Hello, I'm from Bangladesh. I'm using Mycell P2 a china generic 7" android tablet. It's 4.4.3 (Kitkat) & 1 GB of RAM. I have also rooted this using Kingroot. The fact is, i can't make the CWM Recovery for this gadget using MTKDroid tools. It shows "Fake kernel does not correspond to your device"..... etc like something while trying to make CWM. Now how can i make the CWM for my gadget? Experts assist most needed in this condition. So please help me in this situation. However, My gadget is not so popular so that i can't find out the exact CWM for it from anywhere. I also submitted the MTKDroid tools log for my device. It may helpful for you to recognize the problem. I'm new here, i don't know where it should be better to publish. If it would be the wrong place to publish such post please consider me to apology. Thanks. Here is my MTKDroid tools logcat... 30/07/15 09:54:53 -----------Start------------ v2.5.3 (1390155029) 19.01.2014 18:10:29 30/07/15 09:54:53 UserLanguage =English 30/07/15 09:54:59 * daemon not running. starting it now on port 5037 * 30/07/15 09:54:59 * daemon started successfully * 30/07/15 09:55:20 --->>> Connect to device <<<--- 30/07/15 09:55:20 /data/local/tmp/zzz/recovery: No such file or directory 30/07/15 09:55:21 lrwxrwxrwx 1 shell shell 28 Jul 30 03:55 /data/local/tmp/zzz/busybox -> /data/local/tmp/zzz/recovery 30/07/15 09:55:22 /system/etc/firmware/modem_1_wg_n.img 30/07/15 09:55:22 MT6582_S00 30/07/15 09:55:22 3+0 records out 30/07/15 09:55:22 12 bytes (12B) copied, 0.001787 seconds, 6.6KB/s 30/07/15 09:55:22 Cpuinfo 狒rdware =MT8312 30/07/15 09:55:22 ATTENTION! Fake Hardware in kernel or firmware doesn't correspond to phone! 30/07/15 09:55:22 Hardware : MT6582 (MT8312 is Fake!) 30/07/15 09:55:22 Part_NameSizeStartAddrTypeMapTo 30/07/15 09:55:22 preloader 0x0000000001400000 0x0000000000000000 2 /dev/misc-sd 30/07/15 09:55:22 mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 30/07/15 09:55:22 ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 30/07/15 09:55:22 pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 30/07/15 09:55:22 nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 30/07/15 09:55:22 protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 30/07/15 09:55:22 protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 30/07/15 09:55:22 seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 30/07/15 09:55:22 uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 30/07/15 09:55:22 bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0 30/07/15 09:55:22 recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0 30/07/15 09:55:22 sec_ro 0x0000000000600000 0x0000000002980000 2 /dev/block/mmcblk0p4 30/07/15 09:55:22 misc 0x0000000000080000 0x0000000002f80000 2 /dev/block/mmcblk0 30/07/15 09:55:22 logo 0x0000000000300000 0x0000000003000000 2 /dev/block/mmcblk0 30/07/15 09:55:22 ebr2 0x0000000000080000 0x0000000003300000 2 /dev/block/mmcblk0 30/07/15 09:55:22 expdb 0x0000000000a00000 0x0000000003380000 2 /dev/block/mmcblk0 30/07/15 09:55:22 android 0x0000000040000000 0x0000000003d80000 2 /dev/block/mmcblk0p5 30/07/15 09:55:22 cache 0x0000000020000000 0x0000000043d80000 2 /dev/block/mmcblk0p6 30/07/15 09:55:22 usrdata 0x0000000040000000 0x0000000063d80000 2 /dev/block/mmcblk0p7 30/07/15 09:55:22 fat 0x00000000483a0000 0x00000000a3d80000 2 /dev/block/mmcblk0p8 30/07/15 09:55:22 bmtpool 0x0000000000000000 0x00000000febf00a8 2 /dev/block/mmcblk0 30/07/15 09:55:22 Part_Nameartition name you should open; 30/07/15 09:55:22 Size:size of partition 30/07/15 09:55:22 StartAddr:Start Address of partition; 30/07/15 09:55:22 Type:Type of partition(MTD=1,EMMC=2) 30/07/15 09:55:22 MapTo:actual device you operate 30/07/15 09:55:22 rootfs on / type rootfs (rw,seclabel,relatime) 30/07/15 09:55:22 tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755) 30/07/15 09:55:22 devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600) 30/07/15 09:55:22 proc on /proc type proc (rw,relatime) 30/07/15 09:55:22 sysfs on /sys type sysfs (rw,seclabel,relatime) 30/07/15 09:55:22 selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) 30/07/15 09:55:22 none on /acct type cgroup (rw,relatime,cpuacct) 30/07/15 09:55:22 none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000) 30/07/15 09:55:22 tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700) 30/07/15 09:55:22 tmpfs on /mnt/asec type tmpfs (rw,seclabel,relatime,mode=755,gid=1000) 30/07/15 09:55:22 tmpfs on /mnt/obb type tmpfs (rw,seclabel,relatime,mode=755,gid=1000) 30/07/15 09:55:22 none on /dev/cpuctl type cgroup (rw,relatime,cpu) 30/07/15 09:55:22 tmpfs on /storage/usbotg type tmpfs (rw,seclabel,relatime,mode=755,uid=1000,gid=1000) 30/07/15 09:55:22 /[email protected] on /system type ext4 (ro,seclabel,relatime,noauto_da_alloc,commit=1,data=ordered) 30/07/15 09:55:22 /[email protected] on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered) 30/07/15 09:55:22 /[email protected] on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered) 30/07/15 09:55:22 /[email protected]_f on /protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered) 30/07/15 09:55:22 /[email protected]_s on /protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered) 30/07/15 09:55:22 /dev/block/loop0 on /mnt/cd-rom type iso9660 (ro,relatime) 30/07/15 09:55:22 /dev/block/vold/179:8 on /mnt/media_rw/sdcard1 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) 30/07/15 09:55:22 /dev/fuse on /storage/sdcard1 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other) 30/07/15 09:55:22 /dev/block/vold/179:97 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) 30/07/15 09:55:22 /dev/block/vold/179:97 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) 30/07/15 09:55:22 /dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other) 30/07/15 09:55:22 /dev/block/dm-0 on /mnt/asec/com.picsart.studio-1 type ext4 (ro,dirsync,seclabel,nosuid,nodev,noatime) 30/07/15 09:55:22 /dev/block/dm-1 on /mnt/asec/com.gameloft.android.ANMP.GloftIMHM-1 type ext4 (ro,dirsync,seclabel,nosuid,nodev,noatime) 30/07/15 09:55:22 Model : P2 30/07/15 09:55:22 Build number : MT83X2_MR706Z_MR706Z1H1C8W1.2014090110 30/07/15 09:55:22 Build date UTC : 20140901-025832 30/07/15 09:55:22 Android v : 4.4.3 30/07/15 09:55:22 ls: /system/recovery-from-boot.p: No such file or directory 30/07/15 09:55:22 Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 1 10:53:51 HKT 2014 30/07/15 09:55:22 --- NOT Root Shell 30/07/15 09:55:22 ls: /system/bin/su: No such file or directory 30/07/15 09:55:22 -rwxr-xr-x 1 root root 71264 Feb 12 19:10 /system/xbin/su 30/07/15 09:55:22 Uboot build v : ----- should be root shell 30/07/15 09:55:22 LCD Driver IC : ----- should be root shell 30/07/15 09:55:23 Baseband v: MOLY.WR8.W1315.MD.WG.MP.V35, 2014/03/12 14:00 30/07/15 09:55:55 --- ROOT button 30/07/15 09:56:05 ATTENTION! Requests for confirmation on the device screen are possible! 30/07/15 09:56:10 uid=0(root) gid=0(root) 30/07/15 09:56:10 -rw-rw-rw- 1 shell shell 146744 Jan 29 2013 /data/local/tmp/adbd 30/07/15 09:56:11 mount: mounting rootfs on / failed: Device or resource busy 30/07/15 09:56:11 -rwxr-x--- 1 root root 146744 Jul 30 03:56 /sbin/adbd 30/07/15 09:56:18 --- ROOT Shell 30/07/15 09:56:18 LCD Driver IC : 0-tf070mc124_dsi 30/07/15 09:56:18 --- root shel it is received temporarily before reboot ! 30/07/15 09:56:54 Free space: system- 76.6M; data- 153.4M; media_rw/sdcard0- 1.1G; C:\ 16668M 30/07/15 09:56:54 --- Recovery And Boot 30/07/15 09:56:54 - Option recWrite = 0, recBootPhone = 1, recBootFile = 0 30/07/15 09:56:54 12288+0 records in 30/07/15 09:56:54 12288+0 records out 30/07/15 09:56:54 6291456 bytes (6.0MB) copied, 0.224207 seconds, 26.8MB/s 30/07/15 09:57:03 KERNEL 3421968 30/07/15 09:57:03 ROOTFS 829725 30/07/15 09:57:03 --- ERROR :No find KernelGZ 30/07/15 09:57:03 --- ERROR :No Split Boot Image 30/07/15 09:57:03 --- task is complete --- 30/07/15 09:57:45 --- Disconnect from device 30/07/15 09:57:49 -----------End --------------
how to backup scatter file from MTK Device?
hi to all i'm make dump from mtk device but no mach by orginal file my work : my phone is root and busybox installed g360h mt6572 1-adb shell cat /proc/dumchar_info Part_Name Size StartAddr Type MapTo preloader 0x0000000000600000 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 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0 recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0 sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0 misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0 logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0 expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0 android 0x0000000032000000 0x0000000003740000 2 /dev/block/mmcblk0p4 cache 0x0000000000700000 0x0000000035740000 2 /dev/block/mmcblk0p5 usrdata 0x000000000fe00000 0x0000000035e40000 2 /dev/block/mmcblk0p6 fat 0x0000000028ce0000 0x0000000045c40000 2 /dev/block/mmcblk0p7 bmtpool 0x0000000000000000 0x00000000ff9f00a8 2 /dev/block/mmcblk0 Click to expand... Click to collapse 2- 0x0000000000080000 for mbr part_name : convert 80000 hex to 524288 dec / 4096 = 128 dd if=/dev/block/mmcblk0 bs=4096 skip=0 count=128 of=/sdcard/mbr.bin but not mach org file mbr pls help me for true dump
Does anyone advise?
Waiting...