[General Questions and Answers] tvladan:
ok ... some updates from me

all of the bellow were done in the following environment: lollipop R16 rooted with iroot (kinguser apk) using mtk droid tools 2.5.3 and sp flash tools 3.1352

first of all I started by making a complete backup of the system using the mtk dorid tools / sp flash tools method described here: http://forum.gsmhosting.com/vbb/f60...artphone-how-read-backup-1656510/#post9415324.

At some point in the tutorial you have to read an address form scatter file, just use the linear_start_addr, and select the one of the partition after USER DATA, so you will get a backup of all your apps, phone numbers, calls, etc.

than thinkering with things i found out that the bootloader was locked so I unlocked it via fastboot / adb with this command: fastboot oem unlock , there will be a disclamer and also a notice that the phone will be factory rested. Just press yes, since you have the USER DATA backup from above, and you can flash that back with sp flash tools after unlocking.

to check first if you have a locked boot loader use this command from command prompt: fastboot getvar all . At some point there wil be a line that says locked yes or on.

so moving on to recovery:

while trying to flash i discovered that our stock recovery is protected by a file named recovery-from-boot.p ... found in /system folder of the device, that should reflash / revert to stock every time you try to boot in recoveru so using root explorer i just deleted the file (you can rename it if you like recovery-from-boot.p.back or something)

first i tried the CWM autobuild method from MTK droid tools, with no luck just got the eroorr: NO KERNELGZ, NO SPLIT BOOT ... since no one knows what this is .. i moved on, but while thinkering with thinks here, i realized (by unpacking the boot.img and comparing it with one from an older device - an APLS MID tablet) - that our boot.img has other adresses that the ones considered normal, have no ideea what this means ... so i moved on

to TWRP / PHILS both auto and manul via pack / unpack.

In the auto mode I got the region overlapping error, that is caused by the fact that both TWRP and PHILS are some kb bigger than our stock ... so I moved to unpack / repack the recoveries, erased the SusperSU folder and flashed them succesfully to the phone. The problem was that when rebooting to recovery all i got from both were black screens with (sometimes) blue horizontal lines flickering in the left side and after 5-10 second the andorid booted up by itself. Used this guide from here:http://xdaforums.com/showthread.php?t=2798257 many thanks to yuweng and all the team win members for the great tool and tutorials on it.

so ... black screens from both recoveries so far. Also tried older versions of TWRP with no luck ... :( The problem here is i could not pull the error logs from the phone to see what went wrong, my guess is that there were no logs created since adb could not find them ...

than i moved on to carliv recovery, tried to port and flash a recovery ... all went great untill the boot, when I also got black screens ... followed the guide from here http://xdaforums.com/showthread.php?t=1825722

my next steps are:

flash R21 since i never bothered to install it, and try there to see if twrp or phills would install without black screens, if not, ask very very nicely, in my knees, someone form teamwin to port / compile a recovery for our device:laugh:

also regarding the new R24 update that is discussed here, it should be flashable through the stock recovery because it should be a signed official zip and the stock recovery / adb push command from pc should be able to install it.

while writing the above line an idea came to me to try and sign the xposed zip (with zipsign apk from the market) and flash it with stock recovery, unfortunately it does not work, installation starts and than ends with no error :(

so ... if anyone has R21 / R24 installed and wants to try and flash twrp autobuild with no overlap region problem for our phone (the supersu folder is deteled from it) i attached it here, but just remember do a FULL BACKUP FIRST with mtk / sp flash !!!! than flash the attached file and than if something goes wrong (and it probably will) you can flash back your stock recovery form the backup.