try from stock again(odin-flashed+re-partitioned), flash cwm-fixed-for-cm7(odin-flashed, do NOT RE-PARTITION!), flash the kernel in the cm11 OP(it will boot into TWRP recovery; note DO NOT FLASH A TWRP-INJECTED ROM FOR TWRP TO APPLY ONLY THE RECOVERY, IT WILL CORRUPT /SYSTEM AND /DATA PARTITIONS AS IT WAS MOUNTING THEM BEFORE THE TWRP RECOVERY INJECTION REBOOT!!, THUS HAVING ERRORS WHEN FLASHING!! TO FIX RESTORE ANY WORKING TWRP BACKUP, OR USE ODIN TO START OVER!! ), (did over-killing CAPS LOCK make it look important enough to remember) XD, anyways...
when in TWRP flash the following(as all checked with a blue "x", incase u dont use TWRP much):
flash the newest version in @Unjustified Dev
's thread for (unofficial) CM11(as its the rom u are currently having troubles with, and u had a glitched version where the update-binary was not signed all the way in his rom, as if u look at the difference in the binary from it and the newer rom version, it didnt transfer all the way), then the special GAPPS in one of the comments ON A SEPARATE FLASH!, or goto paranoid-android's forum and flash the newest Modular-mini 4.4 GAPPS AGAIN!! ON A SEPARATE FLASH!,, then any mods/add-ons u want(can be on same flash as GAPPS, along with any other additional zips, with the exclusion of data restoring ones like Titanium-Backup-made "update.zip", as that will only restore the system-apps at the moment as it requires data partition to be setup, e.g. first_boot=completed_successfully, then u can goto recovery and flash it for a quicker data recovery)
the only reason why i didn't tell u to make a backup is cause when u flashed the kernel to get the TWRP, its an incompatible kernel for stock, but if u are on a rom u like, make a backup for it first, then flash to stock for a cleaned-out partition, i always suggest making regular/routine backups(about every 3-7 days, or when trying a new rom/Rooted-or-flashed-mod)+(and routinely deleting/cleaning older ones, or ones u don't use), or at least update the titanium-backup-made "update.zip" for faster data recovery(DO NOT INCLUDE SYSTEM-APPS BUILT WITH THE ROM INSIDE THE ZIP, AS SOMETIMES IT WILL OVERLAP THE ROMS ZIP AND CAUSE SOME ERRORS, SAME WITH ITS DATA!!) (opps caps-lock of remembering again, where did that come from) :P
note: in case u(the OP, or others who see this comment) the key-combos(or requirements) for the following partition loading(s) are:
-(ANY)recovery = Volume_DOWN+Volume_UP+Power
-Download-Mode = Plugged into USB-Cable(From AC(Wall-Adapter), DC(Car-Port)(may or may-not work, as it only did for me literally twice since ive owned the phone XD), or Computer(USB-Port( duh )))+Vol_DOWN
-System= (any other combination, as long as POWER is pushed down for ~2-5 seconds (and other partition combinations are not pressed+held after the second "samsung" popup, and/or for two consecutive "samsung" popups or more in some cases)
ADB Commands for rebooting partitions are
non-adb-shell-based, as in shell there is ALOT more ways u could do it)
-System (method1)= adb reboot
-System (method2)= adb reboot system
-Recovery (method1) = adb reboot recovery
-Recovery (method2) = adb reboot-recovery
-Download = adb reboot download
-POWER_OFF = adb reboot -p
Glad if i could be any help with this mini-thread comment now that i see the length XD but i tried to be through and user-friendly as i could think XD if u have any other things wrong or needed to know, feel free to ask on here =)
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Originally Posted by Payton95
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
im not trying to sound like a smart-@$$, but if u look into the errors on the thing, like alot of systems it usually tends to load from top-to-bottom, and in that specific version build it was the update-binary not signed all the way in the transfer in sign-apk (notice the first error, "e:error executing updater binary in zip '/sdcard", and without the binary even if the recovery is compiled right for the phone model(e.g. with the right partition labels for system, data, cache, etc, it wont be able to know for the specfic code to use it by without the binary that is unique for each individual phone(in the update-binary file), by my observations in the systems used anyways =S, cause i manages to fix that specfic zip later after downloading the newer version, just for testing of THAT error, and replaced the update-binary and re-signed and it worked =)[COLOR="Silver"]