[Kazam Thunder Q4.5] matt4321:
So I was at XDA DevCon and Kazam donated me one of their Thunder Q4.5 devices, I'm going to be doing my best to bring much loved XDA goodies to this device, there is no time schedule or eta's, this will go at the pace at which I can go!

I am aware that a few others won the Thunder Q4.5 during giveaways, so if you want to help in getting some development love on this device then feel free. I'm also aware that a lot of people probably don't own this device, so if it's just me documenting and bringing things to the device then so be it! :)

System

I've gained root and dumped /system, available here for inspecting: https://www.androidfilehost.com/?fid=23681161096071461

Recovery & Boot

CWM Recovery working on the Kazam Thunder 4.5Q

You need MTK Droid Root & Tools to install:

1) Select the "root, backup, recovery" tab

2) Select the "Install already prepared files" button and hit "Recovery and Boot"

3) For the Boot.img select the downloaded Boot.img below and for recovery select the Recovery.img below.

4) When you get the "Install patched boot to phone" window, select "Yes"

5) When you get to "Install created recovery" select "Yes".

6) When asked to reboot into recovery, that is down to you!

7) Profit!

Recovery: https://www.androidfilehost.com/?fid=95747613655040353

Patched Boot Img: https://www.androidfilehost.com/?fid=95747613655040352

Old Documentation:

This is where some tricky stuff is, I've never dealt with a device that doesn't have a dedicated /recovery other than Xperia who combine it with /boot though that is easy to deal with.

As we can see here:

Partition Information:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002980000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000002f80000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003000000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003300000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003380000 2 /dev/block/mmcblk0
android 0x000000002bc00000 0x0000000003d80000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002f980000 2 /dev/block/mmcblk0p6
usrdata 0x0000000040000000 0x0000000037780000 2 /dev/block/mmcblk0p7
fat 0x000000006fc00000 0x0000000077780000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8 0
7 /system ext4 /dev/block/mmcblk0p5 (null) 0
8 /sdcard2 vfat /dev/block/mmcblk0p8 (null) 0

mbr, pro_info, nvram, seccfg, uboot, bootimg, recovery, misc, logo, ebr2, expdb, bmtpool

These are all in /dev/block/mmcblk0 and we want hold of bootimg and recovery as these are the important ones!

There is a hexadecimal offset of some sort by the looks of things:

recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0

Converting these in to deciaml values give:

recovery 6291456 37224448 2 /dev/block/mmcblk0

The issue lies with the fact that this looks like over 2gig or something, a recovery image is not that big, should be <10mb.