[Blade General] peter64:
Hey thanks again for the tips Ricky. I'm definitely going to have to do more of a read-up on what effect the scatter files have. Did you make your's from scratch? Or were you building off an existing Blade V7 Lite scatter file? The one thing I've noticed is the difference for the platform and project name values on the various files I've been diffing.

file1

- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6737M
project: ztexa6735m_35u_m
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000

file2

- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6737M
project: ztexa6735m_35gu_m
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000

file3

- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6735M
project: hct6735m_35gu_l1
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000

I'm pretty not too sure what my platform is as MtkDroidTool reported the following.

Hardware : MT6735P

Model : ZTE BLADE V0720
Build number : ZTE_BLADE_V0720_B01

Build date UTC : 20160606-133855
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V79.P15, 2016/06/06 21:07

Kernel v : 3.18.19 (root@scl_xa243_202) (gcc version 4.8 (GCC) ) #1 SMP Mon Jun 6 21:33:09 CST 2016

But my recovery.img/ramdisk/default.prop says ro.board.platform=mt6735m and ro.build.flavor=full_ztexa6735m_35u_m-user

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MRA58K
ro.build.display.id=ZTE_BLADE_V0720_B01
ro.build.version.incremental=1465219574
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0
ro.build.version.security_patch=2016-06-01
ro.build.version.base_os=
ro.build.date=Mon Jun 6 21:38:55 CST 2016
ro.build.date.utc=1465220335
ro.build.type=user
ro.build.user=root
ro.build.host=scl_xa243_202
ro.build.tags=release-keys
ro.build.flavor=full_ztexa6735m_35u_m-user
ro.product.model=ZTE BLADE V0720
ro.product.mtp=
ro.product.brand=ZTE
ro.product.name=P635A32_JP_DWB
ro.product.device=ZTE_BLADE_V0720
ro.product.board=
ro.build.sw_internal_version=DWB_JP_P635A32V1.0.0B05
ro.build.sw_version=ZTE_BLADE_V0720_B01
ro.product.customize=P635A32_JP_DWB
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=ZTE
ro.product.locale=ja-JP
ro.wifi.channels=
ro.board.platform=mt6735m
# ro.build.product is obsolete; use ro.product.device
ro.build.product=ZTE_BLADE_V0720
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=P635A32-user 6.0 MRA58K 1465219574 release-keys
ro.build.fingerprint=ZTE/P635A32_JP_DWB/ZTE_BLADE_V0720:6.0/MRA58K/20160606.212718:user/release-keys
ro.build.characteristics=default
# end build properties

UPDATE:

I found the project name defined in the same file recovery.img/ramdisk/default.prop

ro.mediatek.project.path=device/ztexa/ztexa6735m_35u_m

So right now I'm thinking that the top part is probably supposed to be

- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6737M
project: ztexa6735m_35u_m
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000

As for the recovery partition they all seem to be much the same location and with the same parameters.

partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2D80000
physical_start_addr: 0x2D80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
empty_boot_needed: false
reserve: 0x00

I will heed your warning though and be aware that I may lose my recover-ability.

It'll probably be afew weeks before I have the nerv to try and flash the recovery, I need to learn how to build a twrp custom recovery and be pretty confident it will work before I try. Luckily the I can compare the changesets of russian stock and twrp recovery images I linked above.

Even if I can root it I'm not sure it will be much help to anyone else as I'm my handset is Japanese, but the procedure should be the same for anyone.