[Android Software/Hacking General [Developers Only]] bigrammy:
Thanks for explanation bro for the scatter How does carliv find this stuff :laugh:

Now for my findings on MDRT on the New Android 5.1 MTK67xx SoC.

So using MDRT as is I get no connection at all :confused:

See the first attached image :crying:

So I swapped the MDRT adb files for the working SDK adb files (in a normal environment that is) and I got this.

See the second image :eek:

Next I swapped the adb files again for cofface v5.1 adb and this is what I got (in a normal environment it works fine)

See the third image :(

After much much searching and testing I finally found an obscure adb combination that works :victory: :victory:

See Fourth image :D

I will bundle up the compatible adb and post later.

So MDRT can't root the Phone or pull the recovery so we need our trusty SPFlashtool. it's scatter time oh oh oh oh (MC Hammer :laugh: )

As [MENTION=5726442]AlexZap[/MENTION] as said we need could do with finding additional info for the scatter to be made up which may have odd partitions and without root this maybe difficult as we won't know the fs type :confused:

Enter Fastboot which seems to have been upgraded as of Android 5.1 :victory: :D

So now we

adb reboot bootloader

which takes you to Fastboot :eek:

now enter

fastboot getvar all

and the output is

C:\Users\bigrammy\Desktop\MTKDroid_2.5.3\adb>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 80000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:oemkeystore: 200000
(bootloader) partition-type:oemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: N320BH
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.174s

As we can see this gives us the partition name, size, and fs type raw data = NORMAL_ROM and ext4 = EXT4_IMG I guess if a partition was yaffs or ubifs it would state this. :confused:

We can still use adb shell without root to get the start address from the

cat /proc/partinfo

:good:

So I think we should have everything required to create a working scatter hopefully. :fingers-crossed:

Next I guess is over to [MENTION=4478781]yuweng[/MENTION] with the recovery port tool maybe :laugh:

Edit: [MENTION=5726442]AlexZap[/MENTION] I did a tune2fs on the ext4 /cache partition not sure if you can find anything useful for trimming the readbacks. :confused:

root@n320bh:/ # tune2fs -l /dev/block/mmcblk0p21
tune2fs 1.42.9 (28-Dec-2013)
Filesystem volume name: <none>
Last mounted on: /cache
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 25600
Block count: 102400
Reserved block count: 0
Free blocks: 99014
Free inodes: 25568
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 31
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 6400
Inode blocks per group: 400
Last mount time: Mon Sep 21 14:49:59 2015
Last write time: Mon Sep 21 14:49:59 2015
Mount count: 226
Maximum mount count: -1
Last checked: Thu Jan 1 01:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 1240 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
root@n320bh:/ # tune2fs -l /dev/block/mmcblk0p7
tune2fs 1.42.9 (28-Dec-2013)

[COLOR="Red"]Tried it on a none ext4 partition also LOL[/COLOR]
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p7
Couldn't find valid filesystem superblock.
1|root@n320bh:/ # e2fschk
tmp-mksh: e2fschk: not found
127|root@n320bh:/ # e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device