[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Yeah possibly though ive gone through all libs everywhere i can see and i cant see anything dedicated to it, im thinking it may be split up into multiple dummy named files that have been scattered throughout /system/lib & system/etc

System runs alot smoother now ive decrapped it im trying to do the same make a flashable custom rom , so far no luck with it so far i need to adjust some more of the /system/framework .jars aswell as some libs that are incompatible and not letting it boot,

Havent managed to get anymore recoveries done for it yet have been halted for a week or two sadly as had an outpoor of people wanting a custom recovery for there chinese wish phones currently the one im modding a recovery for, oh on that subject to i did manage to get a working recovery on it but i had to use ancient carliv touch recovery and MTK MTK CWM for UBIFS as its running a nand chip,

Ive tried building twrp and a new updated CWM but they just wont mount partitions under MTD or ext4 only under emmc, my system is a little funny though its running MTD on these under designated mtd

/boot

/logo

/recovery

/nvram

But /system /cache /usrdata are allocated to MTD block partitions with an ext4 system when using dumchar_info in the terminal, i confirmed this again when i tore down the stock untouched recovery in the f.stab, f.stab.fat.nand, & f.stab.nand /system /cache & /usrdata are all allocated to emmc@usrdata, emmc@cache, emmc@android, and as ext4,

But when i set them as ext4 in the recovery.fstab they will not mount they give off invalid argument, ive tried to correct the arguments but with no luck,

Same with CWM the newer source i think that maybe the recovery applet within the SBIN is designed for EMMC compatible devices as the ancient CWM with carliv touch source mounts all partitions correctly, i just stick with it though its a but messy but has touch support interface like TWRP just not as pretty i started with the recovery applet and built and modified the **** out of everything else stock and voila i call it blue hat recovery lol did all the res and everything myself all original, now thats done i can build a flashable 6.0 .zip to see if that will mod and mount the 6.0 .jar files properly as have had no luck through terminal and chmod 644, so flashable .zip is my thinking as i can generate an updater script that will include the correct mod codes for the system and save me figuring them out manually now i have a working custom recovery on it,

Ill be back to the 5044T after though,

I had a quick go at one when we last spoke but had to leave it as i just couldnt get it to boot, i dont think i disabled DM-Verity correctly in the fstab and what not,

What lines did you edit within recovery and boot.img to disable it my thinking is that was what was blocking my TWRP V2 from booting as it would stick on a black screen after logo so was trying to boot i think,

I was thinking of doing something alot newer also as i looked at board specs but what written on paper isnt always so in my case unfortunately ive noticed some quite considerable lag within the stock debloated firmware with some processes taking 2+ minutes to do something my S7 can do in 5 seconds so if you were to it would be considwrably slow unless you can hack it enough to be light but also stable and speedy,

What ive done for speed and optimization within my 6.0 build im doing for MT7562 is added scripts within /system/etc/init.d/ and set the permissions for them,

All that is needed to run the scripts is busybox installed and busyboxes applets do the rest in the background, tested on the stock firmware untouched but rooted and after reboot even the boot animation just flys along makes it easier than recoding framework etc to be smoother,

Keep me up to date anyway with progress and if you need any info along the way im happy to help :)