[Android General] rjt.rockx:
You seem damn confused. But, after reading your other post, I guess you might have figured it out. I'm posting the details here anyway...

YGDP is a windows software built by the Coolpad company for easy management and installation of their factory ROM images for specific variants of their smartphone models which they build at their company. They market only a few smartphones directly under their own banner, but sell most models of their smartphones to marketers like Karbonn, who just buy such models, install some of their own apps like Karbonn Live, etc., add their branding on the Smartphone and market it. This smartphone is a minor variant of the Coolpad 7295C device, with an 8 MP back camera instead of a 5 MP one. This variant's codename is 7295MI01, but ROMs built for Coolpad 7295C device too will work in this, with the rare possibility of Camera issues. The YGDP tool is used to install or flash the stock firmware or factory image onto such devices, and this works by transferring or extracting data onto the device's internal storage while the battery is taken out. The battery needs to be taken out to ensure no file or folder is being accessed or used while flashing the factory image, or else it might corrupt the device completely, leaving you with just an empty, useless, non-booting slab of weight like a brick. This is called bricking your device. Soft bricking refers to a state of bricking your phone in software terms, which you can recover by installing or flashing the ROM image, either stock or custom. Hard bricking refers to an unrecoverable state of bricking the device, the solution to which is replacing the corrupt hardware components completely.

The Android System is divided into many parts, out of which the main three are the boot image, the system image ( or folder ) and the recovery image.

The boot image is a file which contains the kernel, a main part in controlling the device. The Operating system ( Android, in this case ) sends a command to the kernel, which, in turn, controls the hardware accordingly. The boot image is the one which controls your device's state, and is the first thing that gets loaded while booting up your device. It sequences the launch order of the system files. If you get a custom kernel for your device, you may be able to overclock your device too.

Next is the recovery image. You would have rebooted into the Android System recovery image one day or the other. The recovery image is a part of the system which has a list of functions which can be performed without booting into the system. This is helpful as you can use its features to recover back from any changes that you might have made which corrupted your device, or brought it into an unwanted state. This can be helpful in recovering from software bricking, and has a kernel built into it, so that you can change the boot image through this. Custom recoveries add a lot of features to the recovery, so a working custom recovery is in every way better than the stock recovery. Custom recoveries, like the popular ClockWorkMod recovery and the TeamWin Recovery Project, give you the ability to install customized ROMs onto your device.

The System image ( or folder ) is the part of Android which contains all your apps, frameworks, tweaks, property files, fonts, audio files, boot animation, permissions, etc. This is pretty much self-explanatory and ..... y'all know what it is, so I'm skipping it.

There are three more partitions, namely fastboot, data ( or userdata ) and cache.

Fastboot is used to flash new images of any partition other that itself.

Data contains all your app data and its preferences.

Cache contains the files created by the app to increase its performance. ( Note : I'm not sure of this, any corrections would be appreciated. )

You can boot into recovery for this device by pressing the ( Lock + Volume Up ) key combination when the device is switched off. ( Mind you, switched off i.e powered off, not locked. )

If you're looking for the method to flash the file or the download link to the file, you can find it in my first post in this thread.