[Android Q&A, Help & Troubleshooting] X-weApon-X:
Ok, I can't get this into either of my Goophones, no way around the Boot.img being too small.

But I just did it successfully into my new Goophone, I got one from iBaby888. It's an MTK 6735/Mali-T720, 64 bit and running Lollipop 5.1. I ran the tool and copied the Boot.img file from my ROM, but I still get the old recovery rom, it says "No Command" with the broken android image. I'm rooted with Kingroot due to SuperSu Me not working on that device, I started ADB on the device and then from the PC and I got an immediate connection showing my device in the list/ When I ran the tool, it only said "using a secured boot image" but the process completed and I got a message that it was a success. But I still get the Broken recovery when I try to go in. When I boot recovery, I get choices "Recovery", "Fastboot" and "Normal". Recovery brings me to the "No Command" screen, "Fastboot", well I suppose that works but it just stays on a black screen that says ">>fastboot" and Normal is normal boot. The Recovery never has worked on this thing even when I just got it.

Should I have used the Recovery.img instead of "boot.img", or would I just try again? Or maybe Flash the device again using Format+download telling "format" for format the whole device? I don't really want to do it all over again, but I suppose I have it all backed up in Titanium.

Maybe I should try a different boot.ini from a different Rom, there are 5 Roms for that particular device, will using one of those brick it?

edit - Nope! I tried putting recovery.img in there, I get a message about boot.p being secured. It goes away too fast, I'll have to take a picture of it next time I try. I've tried 3 times, once more with boot.img and twice with recovery.img, it still wont even go into regular recovery. I'll try extracting the Rom and see what I got, don't know how to use MTK droid tools.

Edit 2 - I realised, I needed to use the manual method, I chose "recovery.img" and it aborted after a long process, "overlap". But then I chose the "boot.img" file from my ROM, and that aborted as well - I'm going to have to check and see that I'm using the right ROM. But every time I use the auto method, it says that it succeeded, but it won't load TWRP. But now a new thing is happening, instead of showing "No Command", it simply reboots and then just boots normally. So I think I may be using the wrong ROM. But the only ROM I have left on that machine is the ROM I used to flash! But I'll make sure it is, I'll download it anew, it may have been altered somehow.

Edit: I found a way to use Carliv's Kitchen to edit a TWRP image similar to my device: by copying the Kernel info from my stock recovery, I pasted it into the TWRP image where the kernel info resided. It boots to twrp, but the graphics are upside down (while the touch areas are still right side up). With practice I was able to root with SuperSu. After that, it is a simple process to use one of the TWRP apps to flash any other zips like Xposed and Resize through the device UI. I have the method explained in detail in one of my posts in my ChinaPhone/Clone group, but I cannot link through the XDA app, no access to special groups.it is in my thread "Beating a device into Submission", so anyone who is interested can search my profile in a browser to get to my group.