Database Users

Recovery mod on Mtk6595 Soc

How to Build new recovery modded for Zopo zp999 or 3X Mtk 6595M
In this thread we will discuss how to create or build new recovery modded for Zopo zp999 Mtk 6595M.
But also we are studing the new Mtk 6595 SOC.
Everybody are Welcome!​
XDA:DevDB Information
How to Build New Recovery mod on Mtk6595 Soc, Tool/Utility for all devices (see above for details)
Contributors
ghost45, Carliv, Bigrammy,Marsapa,Codelover,Yuweng,SevenMaxs.
Version Information
Status: Testing
Created 2014-12-29
Last Updated 2014-12-29

The Discussion Is Here for moment:
http://forum.xda-developers.com/gen...-recovery-modded-zopo-zp999-3x-t2946325:good:

Reserved for Future USe

Factory ROM BackUp
Sharing my findings on how to manually make a SP Flash Tool Factory ROM backup on this new MediaTek MT6595 SoC . . .
For vendors that doesn't offer it or for users that couldn't find it for their new unknown brand MT6595 . . .
Based on the discussion here, MTK Droid Tools doesn't work & there are only two known MT6595, the Zopo999 & Lenovo X2 that offers SP Flash Tool format.
Below are ways to manually backup the Factory ROM on MT6595.
Method 1
Using adb shell dd command
It is now even easier to make backup on the new MT6595 b'cos it is using direct device path instead of the old format dumchar_info. Require root access !
Based on ghost45 feedback here, you can directly use dd command to make a backup.
Code:
adb shell
[COLOR="blue"]ls -al /dev/block/platform/mtk-msdc.0/by-name[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]boot[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p7[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]cache[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p14[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-16 18:25 flashinfo -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]lk[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p6[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]logo[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p11[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-16 18:25 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-16 18:25 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-16 18:25 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-16 18:25 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]recovery[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p8[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]secro[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p9[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]system[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p13[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]userdata[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p15[/COLOR]
Based on Factory ROM from Zopo, you'll only need to make backup of 8 partition as highlighted above.
Code:
adb shell su -c "dd if=[COLOR="Blue"]/dev/block/mmcblk0p7[/COLOR] of=/sdcard/boot.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p14[/COLOR] of=/sdcard/cache.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p6[/COLOR] of=/sdcard/lk.bin"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p11[/COLOR] of=/sdcard/logo.bin"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p8 [/COLOR]of=/sdcard/recovery.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p9[/COLOR] of=/sdcard/secro.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p13[/COLOR] of=/sdcard/system.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p15[/COLOR] of=/sdcard/userdata.img"
Updates
Found out you can also use below command to backup too.
Code:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="Blue"]boot[/COLOR] of=/sdcard/boot.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]cache[/COLOR] of=/sdcard/cache.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]lk[/COLOR] of=/sdcard/lk.bin"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]logo[/COLOR] of=/sdcard/logo.bin"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]recovery[/COLOR] of=/sdcard/recovery.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]secro[/COLOR] of=/sdcard/secro.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]system[/COLOR] of=/sdcard/system.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]userdata[/COLOR] of=/sdcard/userdata.img"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You don't actually need userdata as a Factory Reset will format it & you'll have your MT6595 in working condition again, in case of a brick. As you notice above, cache.img, secro.img & usedata.img from Zopo SP Flash Tools is only 6.1Mb, 135.2Kb & 21.9Mb respectively.
Thanks to Master Shifu mrjavum for sharing his findings, you can also make backup of the preloader partition too.
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/preloader.bin bs=512c count=512 skip=4
However, you'll need to manually delete the trailing FF & 00 at the end of file of preloader.bin that you backup via dd command. You can use any HexEditor to do that. WARNING : Be careful, the new SP Flash Tool v5 will load this file while older version will pop-up error message when you use incompatible preloader.bin.
View attachment 3093329View attachment 3093330View attachment 3093331View attachment 3093332View attachment 3093333View attachment 3093334View attachment 3093335
Here is the tricky part, you'll need to use either Zopo999 or Lenovo X2 scatter.txt & manually make necessary adjustment to suit to your MT6595. WARNING : Might brick your MT6595 on any mistake made ! Lenovo X2 has the extra preload partition too.
Below is Zopo999 partinfo. Make comparison to your MT6595 & update it accordingly.
Code:
adb shell
[COLOR="blue"]cat /proc/partinfo[/COLOR]
Name Start Size
pgpt 0x0000000000000000 0x00000000000[COLOR="blue"]80000[/COLOR]
proinfo 0x0000000000080000 0x0000000000[COLOR="blue"]300000[/COLOR]
nvram 0x0000000000380000 0x0000000000[COLOR="blue"]500000[/COLOR]
protect1 0x0000000000880000 0x0000000000[COLOR="blue"]a00000[/COLOR]
protect2 0x0000000001280000 0x0000000000[COLOR="blue"]a00000[/COLOR]
seccfg 0x0000000001c80000 0x00000000000[COLOR="blue"]40000[/COLOR]
lk 0x0000000001cc0000 0x00000000000[COLOR="blue"]60000[/COLOR]
boot 0x0000000001d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
recovery 0x0000000002d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
secro 0x0000000003d20000 0x0000000000[COLOR="blue"]600000[/COLOR]
para 0x0000000004320000 0x00000000000[COLOR="blue"]80000[/COLOR]
logo 0x00000000043a0000 0x0000000000[COLOR="Blue"]800000[/COLOR]
expdb 0x0000000004ba0000 0x0000000000[COLOR="blue"]c60000[/COLOR]
preload 0x00000000055a0000 0x00000000[COLOR="blue"]20260000[/COLOR] [COLOR="Red"]<- Only [COLOR="Blue"]Lenovo X2[/COLOR] has this preload partition[/COLOR]
system 0x0000000005800000 0x00000000[COLOR="Blue"]52000000[/COLOR]
cache 0x0000000057800000 0x000000000[COLOR="blue"]7000000[/COLOR]
userdata 0x000000005e800000 0x0000000[COLOR="blue"]344580000[/COLOR]
flashinfo 0x00000003a2d80000 0x000000000[COLOR="blue"]1000000[/COLOR]
sgpt 0x00000003a3d80000 0x00000000000[COLOR="blue"]80000[/COLOR]
Zopo999 MT6595_Android_scatter.txt
Code:
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6595
project: vanzo95_lwt_ds_kk
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: preloader
file_name: preloader_vanzo95_lwt_ds_kk.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x[COLOR="blue"]40000[/COLOR]
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
- partition_index: SYS1
partition_name: pgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS2
partition_name: proinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x[COLOR="blue"]300000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000
physical_start_addr: 0x380000
partition_size: 0x[COLOR="blue"]500000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS4
partition_name: protect1
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x880000
physical_start_addr: 0x880000
partition_size: 0x[COLOR="blue"]a00000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS5
partition_name: protect2
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1280000
physical_start_addr: 0x1280000
partition_size: 0x[COLOR="blue"]a00000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS6
partition_name: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1c80000
physical_start_addr: 0x1c80000
partition_size: 0x[COLOR="blue"]40000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS7
partition_name: lk
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1cc0000
physical_start_addr: 0x1cc0000
partition_size: 0x[COLOR="blue"]60000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS8
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d20000
physical_start_addr: 0x1d20000
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d20000
physical_start_addr: 0x2d20000
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: secro
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3d20000
physical_start_addr: 0x3d20000
partition_size: 0x[COLOR="blue"]600000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: para
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4320000
physical_start_addr: 0x4320000
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS12
partition_name: logo
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x43a0000
physical_start_addr: 0x43a0000
partition_size: 0x[COLOR="blue"]800000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS13
partition_name: expdb
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4ba0000
physical_start_addr: 0x4ba0000
partition_size: 0x[COLOR="blue"]c60000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS14
partition_name: system
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5800000
physical_start_addr: 0x5800000
partition_size: 0x[COLOR="blue"]52000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS15
partition_name: cache
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x57800000
physical_start_addr: 0x57800000
partition_size: 0x[COLOR="blue"]7000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: userdata
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5e800000
physical_start_addr: 0x5e800000
partition_size: 0x[COLOR="blue"]49c00000[/COLOR] [COLOR="Blue"]<- i have absolutely no idea how this figure comes about, as i know Zopo999 comes with 16GB or 32GB variant[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0084
physical_start_addr: 0xFFFF0084
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
- partition_index: SYS18
partition_name: sgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0004
physical_start_addr: 0xFFFF0004
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
Method 2
Using ROM_0 upload from SP Flash Tool
There are already tons of guides doing this so i won't touch on this . . .
What is interesting about this is syserr actually made the discovery & shared his findings since last year ! :good: But i guess nobody discover his thread including myself until i hunt for ways to make backups on the new MT6595 since we have been spoilt by the awesomeness of MTK Droid Tools doing these automatically for us but now it doesn't work on the new MT6595 . . .
As syserr has mentioned on his thread, MTK Droid Tools is actually also using dd command to split the ROM_0 uploaded from SP Flash Tool too.
i have tried it on my old MT6577 & it worked perfectly splitting up all the partitions & generate a perfectly working scatter.txt from dumchar_info too . . . :good: Having said that, however, its not compatible for use with the MT6595 scatter V1.1.2 format.
Complete full output.
Code:
./dice.sh MT6577_Android_scatter_emmc.txt ROM_0 > log.txt
i have modded his script to show as below so we know how it works . . .
Code:
scatter file name = MT6577_Android_scatter_emmc.txt
SP Flash Tool ROM file name = ROM_0
Processing: PRELOADER
start: 0x0
size: 0x40000
(0x0) Size in DEC = [COLOR="Blue"]0[/COLOR]
(0x40) Size in DEC = [COLOR="blue"]64[/COLOR]
dd if=ROM_0 of=raw.partitions/PRELOADER bs=4096 skip=[COLOR="blue"]0[/COLOR] count=[COLOR="blue"]64[/COLOR]
Processing: DSP_BL
start: 0x40000
size: 0x5C0000
(0x40) Size in DEC = 64
(0x5C0) Size in DEC = 1472
dd if=ROM_0 of=raw.partitions/DSP_BL bs=4096 skip=64 count=1472
Processing: MBR
start: 0x600000
size: 0x4000
(0x600) Size in DEC = 1536
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/MBR bs=4096 skip=1536 count=4
Processing: EBR1
start: 0x604000
size: 0x4000
(0x604) Size in DEC = 1540
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/EBR1 bs=4096 skip=1540 count=4
Processing: PMT
start: 0x608000
size: 0x400000
(0x608) Size in DEC = 1544
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/PMT bs=4096 skip=1544 count=1024
Processing: NVRAM
start: 0xa08000
size: 0x500000
(0xa08) Size in DEC = 2568
(0x500) Size in DEC = 1280
dd if=ROM_0 of=raw.partitions/NVRAM bs=4096 skip=2568 count=1280
Processing: SECCFG
start: 0xf08000
size: 0x20000
(0xf08) Size in DEC = 3848
(0x20) Size in DEC = 32
dd if=ROM_0 of=raw.partitions/SECCFG bs=4096 skip=3848 count=32
Processing: UBOOT
start: 0xf28000
size: 0x60000
(0xf28) Size in DEC = 3880
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/UBOOT bs=4096 skip=3880 count=96
Processing: BOOTIMG
start: 0xf88000
size: 0x600000
(0xf88) Size in DEC = [COLOR="blue"]3976[/COLOR]
(0x600) Size in DEC = [COLOR="blue"]1536[/COLOR]
dd if=ROM_0 of=raw.partitions/BOOTIMG bs=4096 skip=[COLOR="blue"]3976[/COLOR] count=[COLOR="blue"]1536[/COLOR]
Processing: RECOVERY
start: 0x1588000
size: 0x800000
(0x1588) Size in DEC = [COLOR="blue"]5512[/COLOR]
(0x800) Size in DEC = [COLOR="blue"]2048[/COLOR]
dd if=ROM_0 of=raw.partitions/RECOVERY bs=4096 skip=[COLOR="blue"]5512[/COLOR] count=[COLOR="blue"]2048[/COLOR]
Processing: SEC_RO
start: 0x1d88000
size: 0x400000
(0x1d88) Size in DEC = 7560
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/SEC_RO bs=4096 skip=7560 count=1024
Processing: MISC
start: 0x2188000
size: 0x60000
(0x2188) Size in DEC = 8584
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/MISC bs=4096 skip=8584 count=96
Processing: LOGO
start: 0x21e8000
size: 0x300000
(0x21e8) Size in DEC = 8680
(0x300) Size in DEC = 768
dd if=ROM_0 of=raw.partitions/LOGO bs=4096 skip=8680 count=768
Processing: EXPDB
start: 0x24e8000
size: 0x200000
(0x24e8) Size in DEC = 9448
(0x200) Size in DEC = 512
dd if=ROM_0 of=raw.partitions/EXPDB bs=4096 skip=9448 count=512
Processing: ANDROID
start: 0x26e8000
size: 0x19000000
(0x26e8) Size in DEC = 9960
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/ANDROID bs=4096 skip=9960 count=102400
Processing: CACHE
start: 0x1b6e8000
size: 0x19000000
(0x1b6e8) Size in DEC = 112360
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/CACHE bs=4096 skip=112360 count=102400
Processing: USRDATA
start: 0x346e8000
size: 0x34300000
(0x346e8) Size in DEC = 214760
(0x34300) Size in DEC = 213760
dd if=ROM_0 of=raw.partitions/USRDATA bs=4096 skip=214760 count=213760
Processing: FAT
start: 0x689e8000
size: 0x976080A8
(0x689e8) Size in DEC = 428520
(0x976080A8) Size in DEC = 2539684008
dd if=ROM_0 of=raw.partitions/FAT bs=4096 skip=428520 count=2539684008
Based on his script output above, below should work on the new MT6595.
Code:
Name Start Size
boot 0x0000000001d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
Code:
start: 0x1d20000
size: 0x1000000
0x1d20 - Convert to decimal = [COLOR="Blue"]7456[/COLOR]
0x1000 - Convert to decimal = [COLOR="blue"]4096[/COLOR]
dd if=ROM_0 of=boot.img bs=4096 skip=[COLOR="blue"]7456[/COLOR] count=[COLOR="blue"]4096[/COLOR]
You can also use his trim.sh & trimFF.sh to automatically remove all the unused FF & 00 at preloader.bin too . . . :good:
i don't have a MT6595 to confirm all this so owners of the new MT6595 should Trial & Error, more info then study syserr's thread . . . :good:

This is the end Source for developing the recovery for this MTk6595M:
Post341:
http://forum.xda-developers.com/showpost.php?p=57923477&postcount=341
carliv said:
Ok, then cwm test 3 it is!
Here are the final recoveries:
CWM Modd ZP999
Carliv Touch Recovery 3.0 ZP999
TWRP 2.8.3.0 ZP999
PHILZ Recovery ZP999
Thanks for support, enjoy using them!
Now for people who want to use the device folder tree from my github (I will update that in short time).
Take a look on BoardConfig to see what flags must be used, and add a local-manifest in your building repo with this content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/carliv/" name="carliv"/>
<project path="bionic/libc/arch-arm/cortex-a17" name="bionic_libc_arch-arm_cortex-a17" remote="carliv" revision="master" />
<project path="device/zopo/zp999" name="device_zopo_zp999" remote="carliv" revision="master" />
</manifest>
then do a repo sync. If you have already a local-manifest just add the project path line in it.
Next open cortex-a7.mk file from /bionic/libc/arch-arm/cortex-a7 folder and replace the content with this:
Code:
ifneq ($(TARGET_2ND_CPU_VARIANT := cortex-a17),)
include bionic/libc/arch-arm/cortex-a17/cortex-a17.mk
else
include bionic/libc/arch-arm/cortex-a15/cortex-a15.mk
endif
include bionic/libc/arch-arm/generic/generic.mk
That's it, then you can build. The most important part on BoardConfig is this:
Code:
TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_8888"
BOARD_USE_FRAMEBUFFER_ALPHA_CHANNEL := true
TARGET_DISABLE_TRIPLE_BUFFERING := false
BOARD_CUSTOM_GRAPHICS := ../../../device/zopo/zp999/recovery/graphics.cwm.c
TW_BOARD_CUSTOM_GRAPHICS := ../../../device/zopo/zp999/recovery/graphics.twrp.c (for twrp only)
Without any of these flags, the recovery won't boot. Cheers!
Click to expand...
Click to collapse

Other Important Source for this Mtk6595M By THE The King of the Devs.........."Carliv" and his tricks!!!
Here we can find other details:
https://github.com/carliv/device_zopo_zp999/commit/ee057c5cd1483dc92be57b307ae907fd67022783
:victory:

Recovery Modded V2 and others last Sources mtk6595
carliv said:
Ok, then if it works let's make it really final this time.
Recoveries with fixed internal sdcard (I'm not sure about twrp because that works different):
CWM Modd ZP999 v2
Carliv Touch Recovery 3.0 ZP999 v2
TWRP 2.8.3.0 ZP999 v2
PHILZ Recovery ZP999 v2
Click to expand...
Click to collapse
Others..... last Sources mtk6595 :victory:

Other Source details to build the twrp for mtk6595:
carliv said:
Oh, finally! And for twrp? None of them works?
Now let me tell you why this damn thing phone drove me crazy. This could be usefull for the other guys who try to solve this problem: @mrjavum, @SevenMaxs, @codelover, and other.
I was right about 32 bits framebuffer, but I took as good info that flag from Lenovo source BoardConfig:
Code:
TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_8888"
So I focused my efforts to implement that pixel format RGBA_8888 and 32bits framebuffer. Only that was wrong and all work I did yesterday was in vain. Not entirely my fault, but I should check that earlier.
So what was the problem? Today morning I wake up and I had the ideea to take a look in lenovo x2 kernel gpu driver code, and I found this:
Code:
/* USE_[COLOR="Red"]RGBA_8888[/COLOR]_FB */
{
int res;
struct fb_var_screeninfo info;
info = psLINFBInfo->var;
info.activate = FB_ACTIVATE_NOW;
info.bits_per_pixel = 32;
[COLOR="LightBlue"]info.transp.offset = 24;
info.transp.length = 8;[/COLOR]
[COLOR="Red"]info.red.offset = 0; <- normally this should be 16
info.red.length = 8;[/COLOR]
[COLOR="SeaGreen"]info.green.offset = 8;
info.green.length = 8;[/COLOR]
[COLOR="Blue"]info.blue.offset = 16; <- normally this should be 0
info.blue.length = 8;[/COLOR]
res = fb_set_var(psLINFBInfo, &info);
Can you see what's wrong here? No? Let me show you:
The RGBA8888 format is the second, and first is ARGB8888. So they use the name RGBA_8888 but pixel map defines is for ARGB - also the offsets are changed too (like it would be ABGR), but once you get the real map that can be set easily. So no matter how hard I tried there was no way I could get a good result with that, because I used the values for RGBA_8888:
Code:
[COLOR="Red"]vi.red.offset = 24;[/COLOR]
[COLOR="Red"] vi.red.length = 8;[/COLOR]
[COLOR="Green"]vi.green.offset = 16;
vi.green.length = 8;[/COLOR]
[COLOR="Blue"]vi.blue.offset = 8;
vi.blue.length = 8;[/COLOR]
[COLOR="LightBlue"] vi.transp.offset = 0;
vi.transp.length = 8;[/COLOR]
But why they used ARGB format and named it RGBA? Because Android doesn't have support for ARGB only RGBA:
They share same pixel size(4), same pixel format (4x8), only thing different is chanel colors map, so I was doing wrong trying to use a different color map.
I hope now we will get better results.
For cwm test 16 I used my custom graphics.c file, and about that issue with non-mounting sdcards that can be solved tunning fstabs and init files. I wasn't pay much attention to that since I wanted to get it start first.
After all feedbacks came out, I'll clean up the file, make some few more tests and I will update my device folder on github for all of you that need these things.
Guys I worked for your phone more than for any phone I ever had :victory:
....
Click to expand...
Click to collapse

yuweng said:
Sharing my findings on how to manually make a SP Flash Tool Factory ROM backup on this new MediaTek MT6595 SoC . . .
For vendors that doesn't offer it or for users that couldn't find it for their new unknown brand MT6595 . . .
Based on the discussion here, MTK Droid Tools doesn't work & there are only two known MT6595, the Zopo999 & Lenovo X2 that offers SP Flash Tool format.
Below are ways to manually backup the Factory ROM on MT6595.
Method 1
Using adb shell dd command
It is now even easier to make backup on the new MT6595 b'cos it is using direct device path instead of the old format dumchar_info. Require root access !
Based on ghost45 feedback here, you can directly use dd command to make a backup.
Code:
adb shell
[COLOR="blue"]ls -al /dev/block/platform/mtk-msdc.0/by-name[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]boot[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p7[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]cache[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p14[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-16 18:25 flashinfo -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]lk[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p6[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]logo[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p11[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-16 18:25 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-16 18:25 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-16 18:25 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-16 18:25 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]recovery[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p8[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]secro[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p9[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]system[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p13[/COLOR]
lrwxrwxrwx root root 2014-12-16 18:25 [COLOR="blue"]userdata[/COLOR] -> [COLOR="blue"]/dev/block/mmcblk0p15[/COLOR]
Based on Factory ROM from Zopo, you'll only need to make backup of 8 partition as highlighted above.
Code:
adb shell su -c "dd if=[COLOR="Blue"]/dev/block/mmcblk0p7[/COLOR] of=/sdcard/boot.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p14[/COLOR] of=/sdcard/cache.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p6[/COLOR] of=/sdcard/lk.bin"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p11[/COLOR] of=/sdcard/logo.bin"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p8 [/COLOR]of=/sdcard/recovery.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p9[/COLOR] of=/sdcard/secro.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p13[/COLOR] of=/sdcard/system.img"
adb shell su -c "dd if=[COLOR="blue"]/dev/block/mmcblk0p15[/COLOR] of=/sdcard/userdata.img"
Updates
Found out you can also use below command to backup too.
Code:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="Blue"]boot[/COLOR] of=/sdcard/boot.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]cache[/COLOR] of=/sdcard/cache.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]lk[/COLOR] of=/sdcard/lk.bin"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]logo[/COLOR] of=/sdcard/logo.bin"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]recovery[/COLOR] of=/sdcard/recovery.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]secro[/COLOR] of=/sdcard/secro.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]system[/COLOR] of=/sdcard/system.img"
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/[COLOR="blue"]userdata[/COLOR] of=/sdcard/userdata.img"
View attachment 3093328
You don't actually need userdata as a Factory Reset will format it & you'll have your MT6595 in working condition again, in case of a brick. As you notice above, cache.img, secro.img & usedata.img from Zopo SP Flash Tools is only 6.1Mb, 135.2Kb & 21.9Mb respectively.
Thanks to Master Shifu mrjavum for sharing his findings, you can also make backup of the preloader partition too.
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/preloader.bin bs=512c count=512 skip=4
However, you'll need to manually delete the trailing FF & 00 at the end of file of preloader.bin that you backup via dd command. You can use any HexEditor to do that. WARNING : Be careful, the new SP Flash Tool v5 will load this file while older version will pop-up error message when you use incompatible preloader.bin.
View attachment 3093329View attachment 3093330View attachment 3093331View attachment 3093332View attachment 3093333View attachment 3093334View attachment 3093335
Here is the tricky part, you'll need to use either Zopo999 or Lenovo X2 scatter.txt & manually make necessary adjustment to suit to your MT6595. WARNING : Might brick your MT6595 on any mistake made ! Lenovo X2 has the extra preload partition too.
Below is Zopo999 partinfo. Make comparison to your MT6595 & update it accordingly.
Code:
adb shell
[COLOR="blue"]cat /proc/partinfo[/COLOR]
Name Start Size
pgpt 0x0000000000000000 0x00000000000[COLOR="blue"]80000[/COLOR]
proinfo 0x0000000000080000 0x0000000000[COLOR="blue"]300000[/COLOR]
nvram 0x0000000000380000 0x0000000000[COLOR="blue"]500000[/COLOR]
protect1 0x0000000000880000 0x0000000000[COLOR="blue"]a00000[/COLOR]
protect2 0x0000000001280000 0x0000000000[COLOR="blue"]a00000[/COLOR]
seccfg 0x0000000001c80000 0x00000000000[COLOR="blue"]40000[/COLOR]
lk 0x0000000001cc0000 0x00000000000[COLOR="blue"]60000[/COLOR]
boot 0x0000000001d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
recovery 0x0000000002d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
secro 0x0000000003d20000 0x0000000000[COLOR="blue"]600000[/COLOR]
para 0x0000000004320000 0x00000000000[COLOR="blue"]80000[/COLOR]
logo 0x00000000043a0000 0x0000000000[COLOR="Blue"]800000[/COLOR]
expdb 0x0000000004ba0000 0x0000000000[COLOR="blue"]c60000[/COLOR]
preload 0x00000000055a0000 0x00000000[COLOR="blue"]20260000[/COLOR] [COLOR="Red"]<- Only [COLOR="Blue"]Lenovo X2[/COLOR] has this preload partition[/COLOR]
system 0x0000000005800000 0x00000000[COLOR="Blue"]52000000[/COLOR]
cache 0x0000000057800000 0x000000000[COLOR="blue"]7000000[/COLOR]
userdata 0x000000005e800000 0x0000000[COLOR="blue"]344580000[/COLOR]
flashinfo 0x00000003a2d80000 0x000000000[COLOR="blue"]1000000[/COLOR]
sgpt 0x00000003a3d80000 0x00000000000[COLOR="blue"]80000[/COLOR]
Zopo999 MT6595_Android_scatter.txt
Code:
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6595
project: vanzo95_lwt_ds_kk
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: preloader
file_name: preloader_vanzo95_lwt_ds_kk.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x[COLOR="blue"]40000[/COLOR]
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
- partition_index: SYS1
partition_name: pgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS2
partition_name: proinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x[COLOR="blue"]300000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000
physical_start_addr: 0x380000
partition_size: 0x[COLOR="blue"]500000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS4
partition_name: protect1
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x880000
physical_start_addr: 0x880000
partition_size: 0x[COLOR="blue"]a00000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS5
partition_name: protect2
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1280000
physical_start_addr: 0x1280000
partition_size: 0x[COLOR="blue"]a00000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS6
partition_name: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1c80000
physical_start_addr: 0x1c80000
partition_size: 0x[COLOR="blue"]40000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS7
partition_name: lk
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1cc0000
physical_start_addr: 0x1cc0000
partition_size: 0x[COLOR="blue"]60000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS8
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d20000
physical_start_addr: 0x1d20000
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d20000
physical_start_addr: 0x2d20000
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: secro
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3d20000
physical_start_addr: 0x3d20000
partition_size: 0x[COLOR="blue"]600000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: para
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4320000
physical_start_addr: 0x4320000
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS12
partition_name: logo
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x43a0000
physical_start_addr: 0x43a0000
partition_size: 0x[COLOR="blue"]800000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS13
partition_name: expdb
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4ba0000
physical_start_addr: 0x4ba0000
partition_size: 0x[COLOR="blue"]c60000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS14
partition_name: system
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5800000
physical_start_addr: 0x5800000
partition_size: 0x[COLOR="blue"]52000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS15
partition_name: cache
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x57800000
physical_start_addr: 0x57800000
partition_size: 0x[COLOR="blue"]7000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: userdata
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5e800000
physical_start_addr: 0x5e800000
partition_size: 0x[COLOR="blue"]49c00000[/COLOR] [COLOR="Blue"]<- i have absolutely no idea how this figure comes about, as i know Zopo999 comes with 16GB or 32GB variant[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0084
physical_start_addr: 0xFFFF0084
partition_size: 0x[COLOR="blue"]1000000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
- partition_index: SYS18
partition_name: sgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0004
physical_start_addr: 0xFFFF0004
partition_size: 0x[COLOR="blue"]80000[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
Method 2
Using ROM_0 upload from SP Flash Tool
There are already tons of guides doing this so i won't touch on this . . .
What is interesting about this is syserr actually made the discovery & shared his findings since last year ! :good: But i guess nobody discover his thread including myself until i hunt for ways to make backups on the new MT6595 since we have been spoilt by the awesomeness of MTK Droid Tools doing these automatically for us but now it doesn't work on the new MT6595 . . .
As syserr has mentioned on his thread, MTK Droid Tools is actually also using dd command to split the ROM_0 uploaded from SP Flash Tool too.
i have tried it on my old MT6577 & it worked perfectly splitting up all the partitions & generate a perfectly working scatter.txt from dumchar_info too . . . :good: Having said that, however, its not compatible for use with the MT6595 scatter V1.1.2 format.
Complete full output.
Code:
./dice.sh MT6577_Android_scatter_emmc.txt ROM_0 > log.txt
i have modded his script to show as below so we know how it works . . .
Code:
scatter file name = MT6577_Android_scatter_emmc.txt
SP Flash Tool ROM file name = ROM_0
Processing: PRELOADER
start: 0x0
size: 0x40000
(0x0) Size in DEC = [COLOR="Blue"]0[/COLOR]
(0x40) Size in DEC = [COLOR="blue"]64[/COLOR]
dd if=ROM_0 of=raw.partitions/PRELOADER bs=4096 skip=[COLOR="blue"]0[/COLOR] count=[COLOR="blue"]64[/COLOR]
Processing: DSP_BL
start: 0x40000
size: 0x5C0000
(0x40) Size in DEC = 64
(0x5C0) Size in DEC = 1472
dd if=ROM_0 of=raw.partitions/DSP_BL bs=4096 skip=64 count=1472
Processing: MBR
start: 0x600000
size: 0x4000
(0x600) Size in DEC = 1536
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/MBR bs=4096 skip=1536 count=4
Processing: EBR1
start: 0x604000
size: 0x4000
(0x604) Size in DEC = 1540
(0x4) Size in DEC = 4
dd if=ROM_0 of=raw.partitions/EBR1 bs=4096 skip=1540 count=4
Processing: PMT
start: 0x608000
size: 0x400000
(0x608) Size in DEC = 1544
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/PMT bs=4096 skip=1544 count=1024
Processing: NVRAM
start: 0xa08000
size: 0x500000
(0xa08) Size in DEC = 2568
(0x500) Size in DEC = 1280
dd if=ROM_0 of=raw.partitions/NVRAM bs=4096 skip=2568 count=1280
Processing: SECCFG
start: 0xf08000
size: 0x20000
(0xf08) Size in DEC = 3848
(0x20) Size in DEC = 32
dd if=ROM_0 of=raw.partitions/SECCFG bs=4096 skip=3848 count=32
Processing: UBOOT
start: 0xf28000
size: 0x60000
(0xf28) Size in DEC = 3880
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/UBOOT bs=4096 skip=3880 count=96
Processing: BOOTIMG
start: 0xf88000
size: 0x600000
(0xf88) Size in DEC = [COLOR="blue"]3976[/COLOR]
(0x600) Size in DEC = [COLOR="blue"]1536[/COLOR]
dd if=ROM_0 of=raw.partitions/BOOTIMG bs=4096 skip=[COLOR="blue"]3976[/COLOR] count=[COLOR="blue"]1536[/COLOR]
Processing: RECOVERY
start: 0x1588000
size: 0x800000
(0x1588) Size in DEC = [COLOR="blue"]5512[/COLOR]
(0x800) Size in DEC = [COLOR="blue"]2048[/COLOR]
dd if=ROM_0 of=raw.partitions/RECOVERY bs=4096 skip=[COLOR="blue"]5512[/COLOR] count=[COLOR="blue"]2048[/COLOR]
Processing: SEC_RO
start: 0x1d88000
size: 0x400000
(0x1d88) Size in DEC = 7560
(0x400) Size in DEC = 1024
dd if=ROM_0 of=raw.partitions/SEC_RO bs=4096 skip=7560 count=1024
Processing: MISC
start: 0x2188000
size: 0x60000
(0x2188) Size in DEC = 8584
(0x60) Size in DEC = 96
dd if=ROM_0 of=raw.partitions/MISC bs=4096 skip=8584 count=96
Processing: LOGO
start: 0x21e8000
size: 0x300000
(0x21e8) Size in DEC = 8680
(0x300) Size in DEC = 768
dd if=ROM_0 of=raw.partitions/LOGO bs=4096 skip=8680 count=768
Processing: EXPDB
start: 0x24e8000
size: 0x200000
(0x24e8) Size in DEC = 9448
(0x200) Size in DEC = 512
dd if=ROM_0 of=raw.partitions/EXPDB bs=4096 skip=9448 count=512
Processing: ANDROID
start: 0x26e8000
size: 0x19000000
(0x26e8) Size in DEC = 9960
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/ANDROID bs=4096 skip=9960 count=102400
Processing: CACHE
start: 0x1b6e8000
size: 0x19000000
(0x1b6e8) Size in DEC = 112360
(0x19000) Size in DEC = 102400
dd if=ROM_0 of=raw.partitions/CACHE bs=4096 skip=112360 count=102400
Processing: USRDATA
start: 0x346e8000
size: 0x34300000
(0x346e8) Size in DEC = 214760
(0x34300) Size in DEC = 213760
dd if=ROM_0 of=raw.partitions/USRDATA bs=4096 skip=214760 count=213760
Processing: FAT
start: 0x689e8000
size: 0x976080A8
(0x689e8) Size in DEC = 428520
(0x976080A8) Size in DEC = 2539684008
dd if=ROM_0 of=raw.partitions/FAT bs=4096 skip=428520 count=2539684008
Based on his script output above, below should work on the new MT6595.
Code:
Name Start Size
boot 0x0000000001d20000 0x000000000[COLOR="blue"]1000000[/COLOR]
Code:
start: 0x1d20000
size: 0x1000000
0x1d20 - Convert to decimal = [COLOR="Blue"]7456[/COLOR]
0x1000 - Convert to decimal = [COLOR="blue"]4096[/COLOR]
dd if=ROM_0 of=boot.img bs=4096 skip=[COLOR="blue"]7456[/COLOR] count=[COLOR="blue"]4096[/COLOR]
You can also use his trim.sh & trimFF.sh to automatically remove all the unused FF & 00 at preloader.bin too . . . :good:
i don't have a MT6595 to confirm all this so owners of the new MT6595 should Trial & Error, more info then study syserr's thread . . . :good:
Click to expand...
Click to collapse
This command I did backup -> adb shell su -c "dd if = / dev / block / platform / mtk-msdc.0 / by-name / boot of = / sdcard / boot.img"
for restore these backup -> adb shell su -c "dd if = / sdcard / boot.img / boot of = / dev / block / platform / mtk-msdc.0 / by-name"
I am right;

it is actually the exact reverse of that command for back up . . .
Code:
adb push boot.img sdcard/
adb shell su -c "dd if=/sdcard/boot.img of=/dev/block/platform/mtk-msdc.0/by-name/boot"
However, you can't do it on a fully booted up Android OS, can only be done while at custom recovery . . .

yuweng said:
it is actually the exact reverse of that command for back up . . .
Code:
adb push boot.img sdcard/
adb shell su -c "dd if=/sdcard/boot.img of=/dev/block/platform/mtk-msdc.0/by-name/boot"
However, you can't do it on a fully booted up Android OS, can only be done while at custom recovery . . .
Click to expand...
Click to collapse
I want to restore the recovery if needed
Thanks

How to root Lenovo A7000 & Install CWM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Taking it down, because most of the user's are complaining they cannot root and the method is not working.
It was already mentioned that this is for Lenovo K3 Note, same model as Lenovo A7000. Previously Lenovo K3 worked for Lenovo A6000 as well. I rooted mine as well, but I don't know what is wrong with others. Sorry and please wait for some developer to release one specially for Lenovo A7000.

Need stock recovery!
Can you please give stock recovery. It will be really helpful.
EDIT : Got it.

bro my phone not detecting after removing battery and connecting usb cable ?
plz reply ..

kdoweb1 said:
bro my phone not detecting after removing battery and connecting usb cable ?
plz reply ..
Click to expand...
Click to collapse
1)remove battery
2)connect your device to PC using USB cable with volume up button pressed.

didnt work

not recognized my device even after connectin usb cable with vol up button pressed and battery removed...........
pls help....... need to root for urgent & imp use

Something is missing you need to reattach the battery it will install mt65xx driver
or you can download from here
Code:
http://www.mediafire.com/download/31nddwqdot5ajp2/MT6575+USB+VCOM+drivers.zip
and make sure u have enough battery
thanks to techolaty admin
:good::good::good:

guys need help here..
I am getting the below error once I press download and connect the phone Lenovo A7000.
"PMT changed for the ROM; it must be downloaded"
I have attached screenshot..
Note: I had followed the steps mentioned here..

cannot install games
Bro when i am installing games like asphalt 8 and modern combat 5 from file explorer on lenovo a7000 it not installing by giving message that
THE PACKAGE DUPLICATE PERMISSION NULL.
But the games are running on other device with low specs.Please help or give reason for this happening.

linuxmelz said:
guys need help here..
I am getting the below error once I press download and connect the phone Lenovo A7000.
"PMT changed for the ROM; it must be downloaded"
I have attached screenshot..
Note: I had followed the steps mentioned here..
Click to expand...
Click to collapse
flash your phone before this process
:good:

Games
[email protected] said:
Bro when i am installing games like asphalt 8 and modern combat 5 from file explorer on lenovo a7000 it not installing by giving message that
THE PACKAGE DUPLICATE PERMISSION NULL.
But the games are running on other device with low specs.Please help or give reason for this happening.
Click to expand...
Click to collapse
This is because You're using Modded Games from random websites. install from Play store or use the original APK

No need of all these rooting hassle
How to root your MT6752 Android phone with Iroot :
Download IROOT - ------ www(.)mgyun(.)com/en/getvroot -------- { remove the brackets }
You just need to perform some easy steps that are explained in the video.
Step 1 - Turn on USB debugging and unknown sources.
Step 2 - Install your phone's ADB drivers.
Step 3 - Install IROOT.
Step 4 - Connect you phone to your pc using the original USB cable.
Step 5 - Click on the root button.
You are done and now your android is rooted !!
Will post on SU replacement later
then again I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DUE TO THIS TUTORIAL

Slow motion / Time lapse video recording
Hi guys, the camera is capable of recording slow motion videos sensor is IMX219 [email protected] 180 fps and [email protected] 120 fps.
But why it is not available?
Using any other software give this options?

Seeing as the original poster edited his entire message out and for all I know, some download links as well, I noticed that this phone doesn't even have its own sub for it! So that's not a good sign very small den community.... . I don't own it but, it is packaged and distributed with Dolby processing which runs as a background service, this is a universal application has been tested on other Android devices and found to increase any devices sound quality. more info on that later there will be a thread.
The app I'm looking for is called atmosphere and installed on these things stock. Please contact me if you care about the further development of this device.
Does anybody have a link to Lenovo's n7000 factory image? , preferably stock. Might as well also add if you don't have the link but have installed and you're rooted, that works as well. I just want this one application. Thanks.

berryman13 said:
Please contact me if you care about the further development of this device.
Does anybody have a link to Lenovo's n7000 factory image? , preferably stock. Might as well also add if you don't have the link but have installed and you're rooted, that works as well. I just want this one application. Thanks.
Click to expand...
Click to collapse
thanks for your interest in a7000. unfortunately, lenovo doesn't provide stock firmware. but,the kernel source is up.
Requesting DEVs to support this powerful device.
those who own this device, do a factory dump and upload it. Let's start development for this.
kernel source:
http://download.lenovo.com/consumer/open_source_code/lenovo_a7000-a_osc_201504.zip
lenovo K3 note has similar specs.
here is the firmware section for that (google translated):
http://translate.googleusercontent....0&st=0&usg=ALkJrhjEgEHu0IqBYZR3SeqmO3p-wTjB0Q

aneesathil said:
thanks for your interest in a7000. unfortunately, lenovo doesn't provide stock firmware. but,the kernel source is up.
Requesting DEVs to support this powerful device.
those who own this device, do a factory dump and upload it. Let's start development for this.
kernel source:
http://download.lenovo.com/consumer/open_source_code/lenovo_a7000-a_osc_201504.zip
lenovo K3 note has similar specs.
here is the firmware section for that (google translated):
http://translate.googleusercontent....0&st=0&usg=ALkJrhjEgEHu0IqBYZR3SeqmO3p-wTjB0Q
Click to expand...
Click to collapse
no lenovo K3 note has maxxaudio which is already ported and what is required is Dolby Atmos .
Request :
Anyone who has rooted his lenovo A7000 can please upload the root/system folder (after compressing it would be around 500-600 mb) .

Hi...nothing wrong with you....
It is saying the error of "PMT changed for the rom"...that means the scatter file was some thing not suited...(I think)...
But, if u can provide us the scatter file of Mtk6752m , it could help us ...
I've tried with the scatter file of Acer jade s56...but it failed....

Clone of Lenovo A7000-a
Lenovo A76000-m is a clone of our device A7000 except for the camera may be we can use the ROM if A7600m as our and other development purpose

chikkarajusk said:
Hi...nothing wrong with you....
It is saying the error of "PMT changed for the rom"...that means the scatter file was some thing not suited...(I think)...
But, if u can provide us the scatter file of Mtk6752m , it could help us ...
I've tried with the scatter file of Acer jade s56...but it failed....
Click to expand...
Click to collapse
Open notepad Rename the txt as MT6752_Android_scatter.txt
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6752
project: aiocu_wtfp
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: preloader
file_name: preloader_aiocu_wtfp.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: pgpt
file_name: NONE
is_download: false
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: INVISIBLE
reserve: 0x00
- partition_index: SYS2
partition_name: proinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000
physical_start_addr: 0x380000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS4
partition_name: protect1
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x880000
physical_start_addr: 0x880000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS5
partition_name: protect2
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1280000
physical_start_addr: 0x1280000
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: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1c80000
physical_start_addr: 0x1c80000
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS7
partition_name: lk
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1cc0000
physical_start_addr: 0x1cc0000
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS8
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d20000
physical_start_addr: 0x1d20000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d20000
physical_start_addr: 0x2d20000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: secro
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3d20000
physical_start_addr: 0x3d20000
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: para
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4320000
physical_start_addr: 0x4320000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS12
partition_name: logo
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x43a0000
physical_start_addr: 0x43a0000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS13
partition_name: expdb
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4ba0000
physical_start_addr: 0x4ba0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS14
partition_name: frp
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x55a0000
physical_start_addr: 0x55a0000
partition_size: 0x100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS15
partition_name: tee1
file_name: trustzone.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x56a0000
physical_start_addr: 0x56a0000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: tee2
file_name: trustzone.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x5ba0000
physical_start_addr: 0x5ba0000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: metadata
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x60a0000
physical_start_addr: 0x60a0000
partition_size: 0x2760000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS18
partition_name: system
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x8800000
physical_start_addr: 0x8800000
partition_size: 0x80000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS19
partition_name: cache
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x88800000
physical_start_addr: 0x88800000
partition_size: 0x1a800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS20
partition_name: userdata
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0xa3000000
physical_start_addr: 0xa3000000
partition_size: 0x49c00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS21
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0084
physical_start_addr: 0xFFFF0084
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
- partition_index: SYS22
partition_name: sgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0004
physical_start_addr: 0xFFFF0004
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00

puchupechu said:
Open notepad Rename the txt as MT6752_Android_scatter.txt
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6752
project: aiocu_wtfp
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: preloader
file_name: preloader_aiocu_wtfp.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: pgpt
file_name: NONE
is_download: false
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: INVISIBLE
reserve: 0x00
- partition_index: SYS2
partition_name: proinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000
physical_start_addr: 0x380000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS4
partition_name: protect1
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x880000
physical_start_addr: 0x880000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS5
partition_name: protect2
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1280000
physical_start_addr: 0x1280000
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: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1c80000
physical_start_addr: 0x1c80000
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS7
partition_name: lk
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1cc0000
physical_start_addr: 0x1cc0000
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS8
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d20000
physical_start_addr: 0x1d20000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d20000
physical_start_addr: 0x2d20000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: secro
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3d20000
physical_start_addr: 0x3d20000
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: para
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4320000
physical_start_addr: 0x4320000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS12
partition_name: logo
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x43a0000
physical_start_addr: 0x43a0000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS13
partition_name: expdb
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4ba0000
physical_start_addr: 0x4ba0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS14
partition_name: frp
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x55a0000
physical_start_addr: 0x55a0000
partition_size: 0x100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS15
partition_name: tee1
file_name: trustzone.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x56a0000
physical_start_addr: 0x56a0000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: tee2
file_name: trustzone.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x5ba0000
physical_start_addr: 0x5ba0000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: metadata
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x60a0000
physical_start_addr: 0x60a0000
partition_size: 0x2760000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS18
partition_name: system
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x8800000
physical_start_addr: 0x8800000
partition_size: 0x80000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS19
partition_name: cache
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x88800000
physical_start_addr: 0x88800000
partition_size: 0x1a800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS20
partition_name: userdata
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0xa3000000
physical_start_addr: 0xa3000000
partition_size: 0x49c00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS21
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0084
physical_start_addr: 0xFFFF0084
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
- partition_index: SYS22
partition_name: sgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0004
physical_start_addr: 0xFFFF0004
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
Click to expand...
Click to collapse
Well I'm out of station right now... Will check it and confirm you abt the status once I'm back.. Tq..

[ROM] Micromax Canvas Xpress 2 E313 CM 12.1 B5

CyanogenMod 12.1 For Micromax Canvas Xpress 2 E313
Note : Do Not Download ROMS Outside XDA Or Any Other Websites They May Add Harmful Applications in Rom.
Click Thanks!! :highfive:​
Follow Me On Facebook Click Here
Must Read
Read Everything Very Carefully Then Proceed With The Installation.
I "Abhi Tripathi " Is Not Responsible If Somehow You Broke Your Phone Or Anything Happens.
You Must Understand All Pros and Cons Of Installing A Custom Rom ​​​
Info.
Porting Is Hard. It Consumes Time. I Didn't Do It For Money Or Any Kind Of Fame
*I DO IT FOR YOU* So Appreciate It
It's Fully Working CM 12.1 Except For The Bugs Which Is In Source
Enjoy Whole New 5.1.1 CM Lollipop Experience With Themes And Mods
Unbeatable Performance And Battery Life
Smooth UI
More Free Ram
Bugs
Video Recording Doesn't Works - Use Video Recording App Instead
Wifi HotSpot Doesn't Work
Some USSD Codes Doesn't Work
Camera Shows Wrong Resolution(Not An Issue)
​
​Here Are Some Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To Install
Instal PhilZ Recovery - Click Here To See Procedures
Download E313_CM_12.1.zip
Go To PhilZ Recovery
Simply Install Zip
Done
Features
All CM Themes Supported
All* CM Features
All Nine Sensors Working
GPS Working
Better Battery Life*
Better AF In Camera*
PlayStore Preinstalled
5.1.1 Based
Rooted
And Much More!
Download
E313_CM_12.1.zip 331MB -Click Here To Download
Notes :-
You Need To Calibrate Battery.
After Installation Go in About Then Enable "Advanced Mode"
Now Go Back In Setting There Will Be Two New Options
"Status Bar" & "Notification Drawer" Use Them To Add More Icon In Status Bar.
There Are Some Source Bugs In CyanogenMod's 12.1 Beta 5 Which Cannot Be Resolved
Like
1.) Video Recording Doesn't Works - Install "Videocam illusion" From Playstore
2.)HotSpot Doesn't Works
3.)Camera Shows 8MP For Front & Back Both However It's Not An Issue
4.) Some USSD Codes Doesn't Works
5.)FM Doesn't Works
Credits
Team Cyanogen
Micromax E313 Developers Group Join On FB Here
XDA:DevDB Information
Cyanogen Mod 12.1 B5 For Micromax Canvas Xpress 2 E313
Contributors
abhimortal6
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12.1
Version Information
Status: Beta
Current Beta Version: 5.0
Created 2015-10-07
Last Updated 2015-10-07

uga buga buga

well thanks abhi.... is there any way to solve ussd codes issues?
like if we use another dialer ?

shub4m said:
well thanks abhi.... is there any way to solve ussd codes issues?
like if we use another dialer ?
Click to expand...
Click to collapse
unfortunately No!

Is there any way to solve hotspot bug

how to get the notification pannel? can any one help plz?

Can you make a CM13 ROM for Micromax E313? its Marshmallow

super

I did a complete wipe and flashed the rom, but whenever I reboot I get stuck on the boot animation! Each time I have to go to recovery and wipe dalvik cache and cache to turn on the phone. Help me out

do i need to root before installing cm 12.1 in xpress 2

The mod has been successfully installed on my phone but the phone is again and again restarting plz help how to fix this issue

how can I flash this by sp flash tool...cuz my divice got bricked so I cant follow the above steps

It's good ,but it has many issues too!
Certain apps are misbehaving along with bad video quality.Sometimes wifi also doesn't work. Suddenly my sim isn't working and finally..it's taking forevever to reboot.:crying:

Unknown Baseband & Invalid IMEI
After Flashing the Baseband version is show unknown & invalid IMEI number. please, please help me.
Please upload the NVRAM backup file of Xpress 2.

abhimortal6 said:
unfortunately No!
Click to expand...
Click to collapse
Flash cyanogen c-apps!

Plz sort out the hotspot issue
Hi. I am facing a hotspot issue. Can u plz resolve it.

Hey plz can u make cm13 for e313 (marshmallow)

I have downloaded this ROM and updated my phone but I can't scroll down the notification bar..?? Can u plz help me?

Panasonic eluga z (MTK6592) Custom rom
abhimortal6 said:
uga buga buga
Click to expand...
Click to collapse
Thanks for the rom for Micromax E313
but i will be gratefull of you if you read the below message ang help me.
can you please , port a custom rom either 6.0 or 7.0 or 8.0 for "Panasonic eluga z" (MTK6592M) which is now on stock rom 4.4 kitkat . I have tried a lot but a lot of time it shows status 7 error or sometimes goes in bootloop . And also if possible provide a philz recovery also.
PLEASE HELP,
THANKS.
-Panasonic Eluga Z_scatter.txt--->
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6592
project: k3466
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader_k3466.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: EXT4_IMG
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: TEST
file_name: NONE
is_download: false
type: EXT4_IMG
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: FRP
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4aa0000
physical_start_addr: 0x4aa0000
partition_size: 0x100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS17
partition_name: EXPDB
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x4ba0000
physical_start_addr: 0x4ba0000
partition_size: 0xc60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS18
partition_name: ANDROID
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5800000
physical_start_addr: 0x5800000
partition_size: 0x45000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS19
partition_name: CACHE
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x4a800000
physical_start_addr: 0x4a800000
partition_size: 0x8000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS20
partition_name: USRDATA
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x52800000
physical_start_addr: 0x52800000
partition_size: 0x49c00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
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'll take a look

ZTE Blade L3 // Lollipop 5.0.2 // Root-Challenge

Howdy Guys,
since i am new to this virtual place, i´d like to introduce myself... my name shall not be known, but my alias is rincee.
i live in germany, so please be patient with possibly upcoming bad english - or misunderstandings of any kind. i´ll try at my very best to be mostly understandable.
i am completely new to the whole android thing, up to now never had a smartphone at all (except an old, beaten-up iphone 2g having been handed over by a friend to me which i played around with a little(the phone, not the friend, besides))
i guess, for introduction, it lasts saying that i just bought two ZTE Blade L3 with lollipop 5.0.2 onboard, for my and my girl.
first impression was, nice elegant 5´ display, nice haptics, nice Lollipop, nice little phone for nice little 80,- Euros.
So i started to make it mine, personalisation, exploring the possibilities of Android, and, unfortunately, discovering the fringe of personalisation. i learned some about overcoming the limitations of the system by getting ROOT-access and superuser-rights, and thought to me, ´well, lets get it on, root it an see how far you get´ - and it turned out that up to now the ZTE Blade L3 with lollipop 5.0.2 seems to be unrootable with my little knowledge. i am stucked...
XDAdevelopers popped up in Googlesearch, so i decided to sign up and try to find info how to get superuser rights on this phone, sadly i could not find a special tutorial of how to achieve this on the phone. There isn´t even a thread to cover this, so i´d like to start such one to challenge all the fabulous hackers on this board to set up a ROOT for this thing.
i tried a lot of oneclick-tools, all of them failed (Kingroot, kingo root, towelroot etc.), so i decided to make this the hard way, but i have no clue where to start. i suppose, billions of Users of this phone will be happy for a working root, since there is none to be found in the net. Strangely, some Users report that they where able to root with kingroot which did not work with mine.
Looking forward for interesting exchange,
rincee
UPDATE:
18 views to this post within 30 Minutes, seems to be a bigger matter to alot of people...

Well hello count me in for the same issue together with a lot of requests from kingroot to any other rooting tool.
BTW i got 4 of them for all my family so guys i think is a good idea for someone to find a solution.
And dont bother googling i am googling more than 2-3 weeks even in russian,chinese,spanish sites thank god for google-translate and filled my Laptop with a lot of malware because i wasnt sure if it is a malware or just the solution so PLEASE if someone has spare time look into it if you need any more info feel free to post i can help with info of the mobile or any other thing.

Challenge accepted!
Well, I own a ZTE Blade L3 that just got the update for the version 5.0.2 last night.
Will do my best and, hopefully, shall come with a tutorial on how to gain root access through the night.
Let's do it! ?

Awesome, Dude...
Theres another Thread where someone posted issues rooting his 5.0.2, i suppose this guy will also be really happy having his L3 rooted...
I tried all oneclick tools like kingroot, Kingo Root, towelroot etc, nothing worked correctly. Maybe the guys from kingroot will like to know how you did it (when you´ve done it) to add the method to their tool. In another forum two guys port a cyanogenmod to the l3, maybe they could give you a hint or two since they dug deep into the hardware to do this... i am not allowed to post links here, you can find them in android-hilfe, followed by a dot and "de", and there in the ZTE Blade L3/L3+ subsection.
When rooted, i´d lilke to add some features to the phone, like using the external SD as internal SD (the external is 32GB, which sends all the limitations to oblivion) or combine all the memory together as one single memory. this internal/external thing reminds me of the damn 640k limitations and emm386-fiddling back in the old DOS times to get games running...
Next, i´d like to install a proper firewall and a working AdBlocker, i love Android but am really annoyed by all the Ads in Apps and my Phone.
And i´d like to use my phone by voice via my bluetooth headset, even from a locked screen, so the phone can stay in my pocket and talks back to me when i talk to it. i found some tools that talk to me when i get mail or so, but i cant talk back when the screen is locked, i constantly use my hands at work, therefore it´ll be a big thing for workflow to voicecontrol.
Oh, and of course i´d like to add a feature that scratches the ice off my Car window in the morning dreams...
I only want full access to my little pocket computer to do whatever i want, it P****es me off not to be able to. So big thanks to you that you give it a try, billions of l3 Users will truly appreciate your work.

Hey glad to have one more in the companion on searching the other topic is made by me I tried all I wrote will go to this website is and will post back if any of you finds a way please say so as for kingroot will post there too and will post back
Sent from my ZTE Blade L3 using XDA Free mobile app

Hi, i "know" you from the german website
I hope KingRoot may root also the 5.0.2 LL ROM for the Blade L3.
My L3 (also german) had 5.0 LL and so Version 4.5 rooted it.
No next step is to get an recovery like CWM, TRWP on it.
Question to other Blade L3 users - especially RUSSIAN language speakers.
This russian website, 4pda.ru
contains lot of ZTE Blade L3 stuff (recovery CWM, TRWP, some other ROMs).
All TRWP img fail for me, ZTE tries to boot in recovery, black screen than (i think reboots) normal.
If i flash stock recovery back it boots in recovery mode. So it is sure the flash worked.
because of russian language (even using google translate) the website above is very hard to use.
Does someone can see/tell if the TWRP/CWM .imgs are for my ZTE Blade L3 Model ?
And can the .img copied by ADB shell, dd .... , or flashify (an apk) like i did it with the stock_recovery.img?
Info from MTK Droid Tool:
Hardware : MT6582
Model : ZTE Blade L3
Build number : DIS_EU_B128DL_P182A20V1.0.0
Build date UTC : 20150522-023522
Android v : 5.0
Baseband v: MOLY.WR8.W1449.MD.WG.MP.V1.P5,MOLY.WR8.W1449.MD.WG.MP.V1.P5, 2015/03/27 14:31
Kernel v : 3.10.54 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP Fri May 22 10:56:19 CST 2015
scatter info:
Code:
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.1
platform: MT6582
project: MTDTtest
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x1400000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
- partition_index: SYS1
partition_name: MBR
file_name: MBR
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1400000
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS2
partition_name: EBR1
file_name: EBR1
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1480000
physical_start_addr: 0x80000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1500000
physical_start_addr: 0x100000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS4
partition_name: NVRAM
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1800000
physical_start_addr: 0x400000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS5
partition_name: PROTECT_F
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1D00000
physical_start_addr: 0x900000
partition_size: 0xA00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS6
partition_name: PROTECT_S
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x2700000
physical_start_addr: 0x1300000
partition_size: 0xA00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS7
partition_name: SECCFG
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x3100000
physical_start_addr: 0x1D00000
partition_size: 0x20000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS8
partition_name: UBOOT
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3120000
physical_start_addr: 0x1D20000
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: BOOTIMG
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3180000
physical_start_addr: 0x1D80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x4180000
physical_start_addr: 0x2D80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: SEC_RO
file_name: secro.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x5180000
physical_start_addr: 0x3D80000
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS12
partition_name: MISC
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x5780000
physical_start_addr: 0x4380000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS13
partition_name: LOGO
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x5800000
physical_start_addr: 0x4400000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS14
partition_name: EXPDB
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x5B00000
physical_start_addr: 0x4700000
partition_size: 0xA00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS15
partition_name: ANDROID
file_name: system.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x6500000
physical_start_addr: 0x5100000
partition_size: 0x80000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: CACHE
file_name: cache.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x86500000
physical_start_addr: 0x85100000
partition_size: 0xE200000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: USRDATA
file_name: data.img
is_download: true
type: NONE
linear_start_addr: 0x94700000
physical_start_addr: 0x93300000
partition_size: 0x13CC80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS18
partition_name: BMTPOOL
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0xFFFF00A8
physical_start_addr: 0xFFFF00A8
partition_size: 0x1500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00

Please help me to unbrick my zte blade l3

Hi every one
I still have Lollipop 5.0 on my L3, Why ?

Super

hi guys, as I read many of you has a ZTE blade L3 bought in Germany with android 5.0 like me. And I kindly ask you all, somebody who has experience with SPflash tool to make a copy of his ROM and share pls. I have tried all ROMs from 4PDA.ru but no one works, now I have white screen on boot and boot sound, probably I have format my reloader, and it not accept any oter. And I have no back ups exept scatter.txt and imei.bak. Thank you all in advance!
---------- Post added at 11:07 PM ---------- Previous post was at 10:59 PM ----------
hi guys, as I read many of you has a ZTE blade L3 bought in Germany with android 5.0 like me. And I kindly ask you all, somebody who has experience with SPflash tool to make a copy of his ROM and share pls. I have tried all ROMs from 4PDA.ru but no one works, now I have white screen on boot and boot sound, probably I have format my reloader, and it not accept any oter. And I have no back ups exept scatter.txt and imei.bak. Thank you all in advance!

zte blade L3 please help with my brick!
hallo, as I read you have same phone ZTE blade L3 , and your adroid is 5.0? I have flashed my with wrong preloader and now have only white screen on boot. Could you pls so kind copy your RAM by SPflashtool an share it with me and other users who looking for it? Just if you dont't know how to do that, I can sent you step by step quide, and there no any risk for your phone. Many thanks in advance.

Please help me!
My ZTE Blade L3 isn´t starting anymore!
It stucks in a Bootloop. (I think some system data is damaged) I Tried to fix it with applying an Update (I have the standard Recovery), but it isn´t working.
The only response I get is: Installation abort.
I think it could be the wrong Update (For this device but to old an for the Mexican Version of it, I have the German Version), but I can´t find any better Update. Can I somehow repair it with adb?
Is there any solution to recover my Phone??
Please help! I have no Idea what to do!
Thanks a lot
Jan

How to create a boot sound on ZTE Blade L3 (5.0.2) ?
Hi guys,
I am using a ZTE Blade L3, 5.0.2 rooted with Kingroot. I want to add a Boot Sound on the Boot animation. I've read and tried many things to add the sound but nothing work.
Heres what i have found and done :
- Moved file to /system/media ; /system/media/audio/ui ; /system/etc/ ; /data/local/
- Changed file name to PowerOn.ogg
- Convert the file in wav, mp3 and ogg
- modify the "desk.txt" in the bootanimation.zip to add a "s PowerOn.ogg"
- I modified the permission to -rw -r -r
I ve seen a blog that talks about an "audio-conf.txt" but can't find a way how to use this. github.com/android/platform_frameworks_base/commit/ebf9a0d8a888042c16ec0cb6dd8419f18038663f
Nothing work. Please if you have any idea, let me know. I am stuck since days with this and I really need it.
Thanks,
Olivier

Ageratos said:
Well, I own a ZTE Blade L3 that just got the update for the version 5.0.2 last night.
Will do my best and, hopefully, shall come with a tutorial on how to gain root access through the night.
Let's do it! ?
Click to expand...
Click to collapse
ZTE Blade L3

Iroot roots Blade l3 5.0.2
today i rooted my zte blade l3 with Iroot v3.2.3 as su-app IT installed Kinguser Workshop Luke charme no Probs AT the moment!
But you know be carfull its at your opinion if you brick your phone.​

Iroot does NOT work
Un!X said:
today i rooted my zte blade l3 with Iroot v3.2.3 as su-app IT installed Kinguser Workshop Luke charme no Probs AT the moment!
But you know be carfull its at your opinion if you brick your phone.​
Click to expand...
Click to collapse
Are your sure? I have tried Iroot v3.2.3 and it doesn`t work with Lollipop 5.0.2

today i rooted my zte blade 3...
first i flashed this twrp recovery using sp tool https://forum.xda-developers.com/android/development/recovery-twrp-2-8-2-0-alcatel-one-touch-t3296852
boot mobile into recovery flash su.zip check latest...then do factory reset in recovery...after that reboot mobile..it stuck on logo for 1 min
after that i just reflashed stock recovery only and BOOM phone booted successfully and rooted...pm me for any questions

nessyb said:
today i rooted my zte blade 3...
first i flashed this twrp recovery using sp tool https://forum.xda-developers.com/an...overy-twrp-2-8-2-0-alcatel-one-touch-t3296852
boot mobile into recovery flash su.zip check latest...then do factory reset in recovery...after that reboot mobile..it stuck on logo for 1 min
after that i just reflashed stock recovery only and BOOM phone booted successfully and rooted...pm me for any questions
Click to expand...
Click to collapse
Does it work for Lollipop 5.0.2?

Rooted with Kingroot APP, not PC version. Twice. You should disable Google Play Protect first or it will block Kingroot. I also disabled SIM PIN, lock screen and made Kingroot administrator before rooting. Good luck! And yes, it works on Lollipop 5.0.2. But if it fails, try again.

Duper User said:
Rooted with Kingroot APP, not PC version. Twice. You should disable Google Play Protect first or it will block Kingroot. I also disabled SIM PIN, lock screen and made Kingroot administrator before rooting. Good luck! And yes, it works on Lollipop 5.0.2. But if it fails, try again.
Click to expand...
Click to collapse
Thanks. It's been a while since I got root with Kingroot for PC. I eliminated garbage Gapps and other unnecessary apps. Then I eliminated the root again.
Regards.

Please make a custom recovery and custom ROM for Asus ZenPad Z380M

No, this is not another thread asking about root methods for the Z380M. I actually have some useful information here.
The Asus stock firmware sucks big time. And the bootloader cannot be unlocked. But fortunately, there seems to be a way to flash a custom boot and recovery images, or anything you want into any location.
The Z380M (and its cousin Z300M) is a Mediatek device that allows easy access to the SoC's Meta mode over USB. I won't go into details about what that is or how to use SP Flash Tool. That is all public information. I'll just get straight to the point.
To boot to meta mode, with the tablet powered off, hold down Volume Up while you plug in the USB cable. Of course you have to have Flash Tool waiting for the device on your PC at this point. While you can use any version of SPFT v5 to read back data, the only version SPFT that works for flashing ("downloading") is v5.1532. This will let you flash a custom recovery or custom boot image (kernel). I'm posting a scatter file for this device.
Now of course the bootloader is permanently locked. So that means it verifies the signature of any boot or recovery image before it starts it. But that's not the end of the world. As far as I can tell, it still lets you boot custom images that have some signature on them (i.e. self-signed), not necessarily the OEM's. The bootloader merely warns you about Android's Yellow boot state at the logo screen, but lets you continue booting. I tested this by deliberately corrupting the boot image's signature.
Of course, this capability makes rooting the stock ROM trivial. But what I would really like to have is TWRP for this tablet. And I think so would a lot of people. And I would love to have a custom ROM on it that's closer to Android AOSP. The kernel source is up on Asus's site. So someone please get on that.
Now a bit of warning: the first time you flash something with SPFT, it may corrupt your partition table. That's why you should make a complete backup before you flash anything. SPFT has a habit of resizing the userdata partition for some reason. But this updated scatter file should prevent that from happening.
Asus Z380M scatter file:
Code:
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT8163
project: asus8163_tb_380_m
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader_asus8163_tb_380_m.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
d_type: FALSE
reserve: 0x00
- partition_index: SYS1
partition_name: pgpt
file_name: NONE
is_download: false
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: INVISIBLE
reserve: 0x00
- partition_index: SYS2
partition_name: proinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000
physical_start_addr: 0x380000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS4
partition_name: protect1
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x880000
physical_start_addr: 0x880000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS5
partition_name: protect2
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1280000
physical_start_addr: 0x1280000
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: asus_nvm
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1c80000
physical_start_addr: 0x1c80000
partition_size: 0x100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS7
partition_name: persist
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1d80000
physical_start_addr: 0x1d80000
partition_size: 0x2000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS8
partition_name: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x3d80000
physical_start_addr: 0x3d80000
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS9
partition_name: lk
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3dc0000
physical_start_addr: 0x3dc0000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: boot
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3e40000
physical_start_addr: 0x3e40000
partition_size: 0xff7000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x4e37000
physical_start_addr: 0x4e37000
partition_size: 0xff7000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS12
partition_name: secro
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5e2e000
physical_start_addr: 0x5e2e000
partition_size: 0xff7000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS13
partition_name: para
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x6e25000
physical_start_addr: 0x6e25000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS14
partition_name: logo
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x6ea5000
physical_start_addr: 0x6ea5000
partition_size: 0x800000
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: 0x76a5000
physical_start_addr: 0x76a5000
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: frp
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x80a5000
physical_start_addr: 0x80a5000
partition_size: 0x100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS17
partition_name: tee1
file_name: tz.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x81a5000
physical_start_addr: 0x81a5000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS18
partition_name: tee2
file_name: tz.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x86a5000
physical_start_addr: 0x86a5000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS19
partition_name: kb
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x8ba5000
physical_start_addr: 0x8ba5000
partition_size: 0x200000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS20
partition_name: dkb
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x8da5000
physical_start_addr: 0x8da5000
partition_size: 0x200000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS21
partition_name: metadata
file_name: NONE
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x8fa5000
physical_start_addr: 0x8fa5000
partition_size: 0x2000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS22
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xafa5000
physical_start_addr: 0xafa5000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS23
partition_name: ADF
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xbfa5000
physical_start_addr: 0xbfa5000
partition_size: 0x2000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS24
partition_name: APD
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xdfa5000
physical_start_addr: 0xdfa5000
partition_size: 0x6400000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS25
partition_name: cache
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x143a5000
physical_start_addr: 0x143a5000
partition_size: 0xC800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS26
partition_name: system
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x20ba5000
physical_start_addr: 0x20ba5000
partition_size: 0xdfc00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS27
partition_name: userdata
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x1007a5000
physical_start_addr: 0x1007a5000
partition_size: 0x2aac56e00
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS28
partition_name: sgpt
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0004
physical_start_addr: 0xFFFF0004
partition_size: 0x4200
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00

How did you get the scatter file ?
I want to get it from the latest nougat ota update and im also looking in to building twrp for this tablet.

The scatter file I handcrafted myself. I read back the GPT layout from the tablet and spent an afternoon calculating the partition addresses and lengths. The general format just follows examples of other scatter files on the web.
The layout should be the same for Nougat. If not, it will complain about the PMT (partition management table which it derives from the GPT) having changed when you try to "download" (should really be called upload) something. You can also get a list of partition addresses with the fastboot oem emmc_show_partitions command in LBA format.
BTW, that was an awesome update with Android N. It solves pretty much all the problems I've had with this tablet. Asus really came through with this one.

heres a twrp image, i keep getting red error when i flash it grrr.
https://mega.nz/#!3xwkXYpT!PHclNbl2bsxZLMs9YHJc4b16DnYVKPd3z70xYAeLG4M
when tablet reboots its revert's the's the recovery to stock so remember that, by running recovery-from-boot.p on boot up.

Hold on, there's still hope... I checked the image file in a hex editor and it doesn't seem to have any cryptographic signature in it. You have to sign it somehow with your own key. I'm not saying that a self-signed image will necessarily pass the security checks, but a lack of a signature will definitely cause the red boot state error.
I know the stock firmware replaces the recovery at every boot, but do you know if the new stock recovery still erases your data as soon as you select Recovery at the boot menu? Or did they add some kind of a warning. I don't want to fall for the automatic factory reset again.

Dude, it's not even the red state that's the problem. There is something wrong with the recovery itself. I think it is trying to boot but it's crashing and restarting. I just wasted a whole lot of time trying to self-sign your image. I did manage to do that. But it turns out you don't even need the signature. (There's 2 sigs, but that's a discussion for another topic.)
The red state is merely a warning. I just tested the stock boot image with the signatures zeroed out. The bootloader is not happy about it, but it continues booting just fine. :-O The Play store even says the device is certified. The recovery should work the same way. Please fix it.

Nice will look into it and yes it still erases at boot menu.
---------- Post added at 12:53 PM ---------- Previous post was at 12:29 PM ----------
By the way i unpacked the system img i got from sp tool , remove some apps and flashed it bk with no problems so thats handy. You do need to do a factory reset if u remove any apps though.

Thanks for the heads up. The system partition has dm-verity enabled. Something weird probably happens when you load a modded system image. It would probably be best to disable verity in the fstab file.
Any progress on the TWRP?

nope not yet, also got this recovery which is same soc mt8163 and trying to port with no success yet.
and will update the kernel better if they ever release the nougat version of it.
https://mega.nz/#!vhJDTCaJ!-Li4KYpNz2KThFHvGaKDOiyyj3UnrAF3de1ySE-Bzi0

diplomatic said:
Now of course the bootloader is permanently locked. So that means it verifies the signature of any boot or recovery image before it starts it. But that's not the end of the world. As far as I can tell, it still lets you boot custom images that have some signature on them (i.e. self-signed), not necessarily the OEM's. The bootloader merely warns you about Android's Yellow boot state at the logo screen, but lets you continue booting. I tested this by deliberately corrupting the boot image's signature.
Of course, this capability makes rooting the stock ROM trivial.
Click to expand...
Click to collapse
Hi, next week, I'll get a device with an identical SoC (acer iconia tab 10 a3-a40)
Fortunately, this device's bootloader can be unlocked.
But atm, I'm somewhat blind, or I overlook something... I have no idea, how to root this device, using a modified boot.img/recovery.img
So please, point me into the right direction.
(I don't need the basics, I'm aware, how to unpack/repack/modifying the .img files)
Thanks in advance.

Oh, when I posted that, I had a wrong impression of what's involved in rooting. I just thought you could mount the system partition on your PC, add some binaries, flash it back and enjoy your root access. But after looking at SuperSU's installation script, it quickly became clear that this would not work. The process is a lot more involved now. Android 6+ requires a systemless root with substantial mods to the boot image. It also needs to add a mountable image file to your data partition. And you can't access the data partition outside your device because it's encrypted. Probably the easiest path for you would be to make or find a custom recovery for your device and install a SuperSU zip from there. But ask yourself this: do you really need root if you already have a custom recovery from which you can manipulate any file on /data? I have not rooted my Z380M and don't plan to.

Ah ok, so my first impression was correct and I'm not that blind.
The problem is, there is no custom recovery available.
But I'm not sure, if Android 6 needs "systemless root", but will investigate further.
I was able to root a lollipop device (or was it a Remix system image?) manually a while ago, with copying and "chmodding" the necessary files into /system.
Nut sure, if that works with MM...

Well, it's not too hard to compile your own TWRP. And you sound like the right man for the job. You just need a bare-bones device tree and binary kernel inserted into the minimal Omni/TWRP repo. You can follow my TWRP source for the ZenPad or use other mt8163 or mt67xx recovery sources.

diplomatic said:
Well, it's not too hard to compile your own TWRP. And you sound like the right man for the job. You just need a bare-bones device tree and binary kernel inserted into the minimal Omni/TWRP repo. You can follow my TWRP source for the ZenPad or use other mt8163 or mt67xx recovery sources.
Click to expand...
Click to collapse
I know, I've did it years ago, but for a Snapdragon.
But I remember, that was a lot of hassle and a 20GB download, for just replacing a few files...
But: a "minimal Omni/TWRP repo" sounds good, will check your links.
PS: interesting that a mt67xx source might work.
EDIT: I will probably first try, to port your TWRP to the Acer.

diplomatic said:
Oh, when I posted that, I had a wrong impression of what's involved in rooting. I just thought you could mount the system partition on your PC, add some binaries, flash it back and enjoy your root access. But after looking at SuperSU's installation script, it quickly became clear that this would not work. The process is a lot more involved now. Android 6+ requires a systemless root with substantial mods to the boot image. It also needs to add a mountable image file to your data partition. And you can't access the data partition outside your device because it's encrypted. Probably the easiest path for you would be to make or find a custom recovery for your device and install a SuperSU zip from there. But ask yourself this: do you really need root if you already have a custom recovery from which you can manipulate any file on /data? I have not rooted my Z380M and don't plan to.
Click to expand...
Click to collapse
That most likely explains why those King(o)root utilities are of no use on a Nabi SE my friend and I were trying to poke the internals on. It came with Android 6.0 pre-installed if that's any indication. As crazy as it sounds, my method for editing the firmware was to dump /system, mount it on a PC using osfmount and an EXT4 driver, edit it offline, and chuck it back in to the device. I didn't get any issues with doing such offline system image edits so far, as I tried it on another device to much success.