[ONE Q&A, Help & Troubleshooting] Vonnegut:
Frankly speaking i'm against partial backups. That script was done 'cause someone asked for it. I can understand that most ppl here are not advanced users, so i see their point when they ask for a script which automatically creates another flashable script for 2 or 3 partitions. That script could be useful in solving a very specific (but still quite widespread) problem quickly.

But i'll stick to my view that having a proper full backup will protect from about anything. That's why i still think that flashing the script posted in chapter 11 of the Timmaaa's guide is the best choice http://xdaforums.com/showpost.php?p=54640979&postcount=1

That backup coupled with the official CM fastboot .zip cover each and every sector of our beloved phone.

It doesn't matter if it doesn't creates a flashable .zip (nobody sane in his mind would flash all of the blocks whenever he faces a problem): the point is that WE HAVE A FULL BACKUP.

Let's say somone, who's not very skilled with fastboot, faces a big problem. He won't know how to flash those sectors, but he still can write a post like this Hi guys, i'm in trouble. Fortunately i have a full backup of my phone. Can someone help me to flash it?. Simple as that.

Here's an example of what could go wrong. Usually custom ROMs never touch more then 2 partitions: kernel (=boot) and system. Some days ago i checked what the latest ColorOS does...here's an extract form the script:

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print("Writing aboot image...");
package_extract_file("emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/aboot");
ui_print("Writing modem image...");
package_extract_file("NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
ui_print("Writing sbl1 image...");
package_extract_file("sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1");
ui_print("Writing rpm image...");
package_extract_file("rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
ui_print("Writing tz image...");
package_extract_file("tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tz");
ui_print("Writing static_nvbk image...");
package_extract_file("static_nvbk.bin", "/dev/block/platform/msm_sdcc.1/by-name/oppostanvbk");
ui_print("Writing logo image...");
package_extract_file("logo.bin", "/dev/block/platform/msm_sdcc.1/by-name/LOGO");
ui_print("Writing reserve4 image...");
package_extract_file("reserve4.img", "/dev/block/platform/msm_sdcc.1/by-name/reserve4");

Horrible isn't it?

That ROM flashes not only the boot and the system, but also the bootloader, the modem, the rpm, the tz, the sbl1 and the LOGO. Ok, once someone knows that he can quickly fix everything and flash back the official partitions shipped with the official CM .zip.

But, as you can see, that ColorOS ROM doesn't stop there. It flashes also the oppostanvbk and the reserve4 partition (which even CM never touched so far).

I guess most users who flashed that ROM weren't aware of that...but if they made a full backup, they could easily restore their phone back to the standard international ROM. A partial backup won't be of any help in a case like that.

Can you see my point?

Anyway, i won't open a thread for that script, so feel free to put it in the OP. It won't solve each and every problem but it sure will help someone.