[SuperR Kitchen] Methamphetadreams:
Hello! Firstly, thank you for all of your hard work, much respect.

I am thoroughly enjoying the setup and ease of use with your warez, sadly, It is not currently working for me! When I attempt to build a new ROM dump, it will completely dump all of my system files, or so I believe, but it will not pack it. I am unsure if this is meant to happen, but I am only left with an uncompressed folder named system.img. Next, it tells me that my recovery and boot images are non-existent. I do know for a fact that the recovery is able to be booted with # adb reboot recovery, but I am unable to reach it through general power+rocker tricks. I have already done the usual searching around with # cat /proc/mtd, # cat /proc/emmc, # cat /proc/partitions, and # mount, but there was nothing remotely named for my two images. I sincerely hope I am able to find them.

Here is what was left in my terminal:

2152 files pulled. 0 files skipped.
719 KB/s (1253454301 bytes in 1701.560s)

------------------------------------------------------
- SuperR's Kitchen -
- by SuperR -
------------------------------------------------------

Extracting recovery.img from your device ...

remote object '/recovery' does not exist

------------------------------------------------------
- SuperR's Kitchen -
- by SuperR -
------------------------------------------------------

Extracting system partition to /sdcard ...

su: invalid option -- C

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk

Pulling system.img from your device ...
remote object '/sdcard/system.img' does not exist
rm failed for /sdcard/system.img, Permission denied

------------------------------------------------------
- SuperR's Kitchen -
- by SuperR -
------------------------------------------------------

Extracting boot partition to /sdcard ...

su: invalid option -- C

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk

Pulling boot.img from your device ...
remote object '/sdcard/boot.img' does not exist
rm failed for /sdcard/boot.img, Permission denied

------------------------------------------------------
- SuperR's Kitchen -
- by SuperR -
------------------------------------------------------

Extracting recovery partition to /sdcard ...

su: invalid option -- C

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk

Pulling recovery.img from your device ...
remote object '/sdcard/recovery.img' does not exist
rm failed for /sdcard/recovery.img, Permission denied

------------------------------------------------------
- SuperR's Kitchen -
- by SuperR -
------------------------------------------------------

ERROR:
Something went wrong. Most likely you lack permission
to pull img's from your device.

Press ENTER to return to then Main menu

Further Information:

Model - Kata M3

Version - 4.4.2

Rooted - Yes

Permission - Yes

With the system files I already pulled, would I simply be able to swap /data, /system/app, /system/framework, /system/fonts, /system/media, /system/lib/libandroid_runtime.so, /system/lib, /system/etc/init.d around from an already built recovery of the ROM I'd like, THEN modify the build.prop to include all the information I need. I would enjoy using an alternative ROM like Cyanogenmod or Miui. If so, that would save me quite a bit of time, and I wouldn't have to bug you any longer!