[G Tablet Q&A, Help & Troubleshooting] Misty soul:
In order to be able to reboot in recovery, you may have to rewrite the recovery.img using nvflash. There is a really good tutorial about how to set up nvflash here: nvflash FULL restore, using bekit's original image (Instructions). You can follow it for installing nvflash itself on your computer, but should stop before attempting to flash your tablet with the zip file with names starting as nvflash_gtablet. The reason for that is that this zip file is really for a Gtablet, not a Malata Zpad. If you want to completely restore your Malata to stock, you have to get another file. I used one named nvflash_t2_mp_wifi_1202.rar (it is in rar format instead of zip format, but basically it is simply an archive). You can find this rar file by using your preferred web search engine, it is available from several free download sites. The download.bat file in this archive plays a similar role to the nvflash_gtablet.bat in the thread above and it references the other files in the rar archive that contain Malata specific stuff instead of Gtablet specific stuff.

However, in your case you may overwrite just the recovery partition instead of the full tablet. If you look at the configuration file from the rar above (named android_fastboot_full.cfg), you will see a terse description of how the Zpad partitions are set up and you will see there is a partition called SOS which is partition number 11 and is filled with the binary image recovery.img. This is basically the bootloader which is used when you power the tablet on with Vol+ pressed. Note that there is a difference here with Gtablet (you can look at the gtablet.cfg file in the gtablet zip file from the thread above to check). In the gtablet case the SOS partition is partition number 9, not 11. So I would suggest you to reset the content of partition 11 with a recovery image to be able to boot in recovery mode.

Before attempting to put this recovery, lets do some preliminary checks, though, just so you understand how nvflash is used and how your own tablet is configured. I suggest you to run the following commands with nvflash, from you computer with the tablet connected in APX mode (i.e. started with Power and Vol-, not Power and Vol+). Then, from a command line on your computer and when you are in the folder where the various files from the rar have been unpacked you can run:

nvflash --bl bootloader.bin --getpartitiontable mypartitiontable.txt

This should send the bootloader on the tablet (hence you should see a one line message at the top of the empty black screen of the tablet, telling you the tablet is ready in nvflash recovery mode), read the partition table and put it in a new file named mypartitiontable.txt on your computer. Check this text file and compare its content with the configuration table. Double check the SOS partition is partition 11. If this is OK, you can proceed with flashing the recovery image to this partition 11. This is done with the command:

nvflash --bl bootloader.bin --download 11 recovery.img

If you use the recovery.img from the rar file, you will restore the initial setting of your tablet. You may choose to use the recovery.img file that is inside the update.zip from CM 0.8 instead so you have it installed. As far as I understand, CW 0.8 is simply a custom recovery image, which explains why you enter it by powering up the tablet with Vol+.

Don't bother sending the partitions from your tablet, as I wrote in the my thread, I finally succeeded in unbricking my own tablet. However, it may be a good idea for you to retrieve all your partitions and store them safely on your computer, just in case you need to reflash them later on. As this will imply several commands and sending the bootloader is cumbersome, you can use a feature when each nvflash command that use --go will let the bootloader run waiting from another command to be sent, and using --resume in the following command to tell it the bootloader is already running. So you will have something like this to do:

nvflash --bl bootloader.bin --go
nvflash --resume --read 2 02-BCT.img --go
nvflash --resume --read 3 03-PT.img --go
nvflash --resume --read 4 04-EBT.img --go
nvflash --resume --read 5 05-NVC.img --go
nvflash --resume --read 6 06-MBT.img --go
nvflash --resume --read 7 07-BLO.img --go
nvflash --resume --read 8 08-MSC.img --go
nvflash --resume --read 9 09-KLO.img --go
nvflash --resume --read 10 10-OGO.img --go
nvflash --resume --read 11 11-SOS.img --go
nvflash --resume --read 12 12-LNX.img --go
nvflash --resume --read 13 13-APP.img --go

Of course, what I wrote should be considered with the usual warnings: I am not an expert, you may break your device, I take no responsibility if something bad happen ... I simply hope this helps ...