[Android General] rjt.rockx:
Nah, you can't flash this recovery through the CWM recovery itself. The easiest method and the one that most users would understand and prefer would be the fastboot method. But, if you're looking for a no-bootloop quick method to flash it, and the fastboot method didn't work, doing it through a Terminal Command would be your alternative way.

Steps for flashing a .img file to a specific partition ( here, recovery ) :

Here are the two methods :

1st Method ( Using ADB ) -- This needs the phone to be connected to the computer.

Go to the folder containing the recovery.img file you just downloaded.

Shift + Right Click on any empty space in the folder and Select Open Command Window Here

Connect the phone to the computer and make sure you have USB Debugging enabled and not USB Storage

Type these into the Command Window :

adb devices -- This should show the Device attached as KarbonnTitaniumS5Plus-xxxx or any such line.

adb get-state -- This is to ensure USB Debugging works. It will show device, recovery or offline, but here, we would be looking for device

adb reboot bootloader -- This reboots the device into Fastboot mode, also called as HBOOT or Bootloader. This mode is necessary for flashing the recovery.img file

fastboot oem unlock -- This is to ensure that you can flash xxxx.img files to specific partitions of the device.

fastboot flash <<partitionname>> <<nameofrecoveryimagefile.img>> -- This flashes the specific partition image file to the specified partition. Here, we would be looking for something like fastboot flash recovery philzrecoverys5plus.img for the PhilZ Touch Recovery and fastboot flash recovery twrprecovery.img for the TWRP Recovery and fastboot flash recovery cwmrecoverys5plus.img for the.... Well, you understand what I mean. This should show some text on the device like Transferring Flash or Writing Flash and the Time and Speed of it, that would confirm your flashing.

fastboot reboot -- This command reboots the device into the normal system, and lo, you're ready to go !

From here, you can reboot to recovery and back again without any issues. This is the tried and tested method, the method which worked perfectly when I tried it on my device. Else, if you have no patience for connecting the Phone to the PC, jabbing on the keyboard and entering n number of commands, you could try this out :

2nd Method ( Using Terminal Emulator ) -- This doesn't need the phone to be connected to the computer.

Place the recovery.img file in the Internal Storage or External SD Card -- Here, I'm placing it as in storage/sdcard0/xxxxrecovery.img

Install Terminal Emulator or any such app onto the phone and Open it.

Type these commands one by one :

su -- This gives root permissions to the Command Executor.

flash_image recovery /storage/sdcard0/xxxxrecovery.img -- This flashes the recovery image file to the recovery partition.

Close the Terminal Window.

Done !

Note : If you're following the Second ( Terminal Emulator ) Method, note that there is a space between flash_image and recovery and the path of the image file. The first method is the preferred one, which worked perfectly with no errors for me; while the second method is risky and might return some errors while trying it out.

Another Loooooong Note : The TWRP Recovery might, in some rare cases, show your battery level as 19% when it is at 99% and the same goes for the others. If you are encountering this error damn frequently, I'd recommend reverting back to the original CWM basic recovery as it doesn't show any battery info at all ! You also have the option of wiping your Battery Statistics in case the Battery Error in the Touch Recoveries made the system too show the same error. Once, after fully charging the phone to 100% and rebooting to recovery, I found that the TWRP recovery showed the battery level at 19% ! Out of curiosity, I rebooted back to the system and it too, showed it at 19% ! I just plugged it into the charger and was like Whoa !, as the battery sprang from 19% to 24% in 7 seconds flat ! I know that neither the reboot to recovery does drain out that much battery, nor does the recovery randomly perform such miracles on it. So, I just flashed CWM basic recovery to it using fastboot mode, opened it, did a Battery Stats wipe and rebooted to the System. It was back to 99% ! So, a full Battery Statistics wipe helped me solve such errors, and might do the same to you too.

Yet Another Short-But-Not-So-Short Note : I'd recommend disabling the Boot Animation on the phone ( using ROM Toolbox Lite or Pro ) so that the possibility of bootloops is diminished. No Boot Animation = Less Chance of Bootloops !