Can't flash CM11 on Fascinate - Fascinate Q&A, Help & Troubleshooting

I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.

---

mohan2k2 said:
I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.
Click to expand...
Click to collapse
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.

---

Still no go
Payton95 said:
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.
Click to expand...
Click to collapse
Still no go with JB 4.1 or CM 10.1. Cant mount e:data or e:system

---

Flashed a GB bootloader with Odin?

---

jason_streak said:
Flashed a GB bootloader with Odin?
Click to expand...
Click to collapse
if he's having a problem coming from stock, then its either or. attempted a flash from Slim Bean 4.2, having same issue...

---

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):
-data
-cache
-dalvik-cache
-system
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)
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 arenon-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 ----------
Payton95 said:
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.
Click to expand...
Click to collapse
im not trying to sound like a [email protected]$$, 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 =)

---

jkok said:
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):
-data
-cache
-dalvik-cache
-system
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse

---

after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.

---

tsdsbrk said:
after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.
Click to expand...
Click to collapse
yes, flashing the kernel is successful, but the wipe is not going well. when I advanced wipe either all four together or starting with the sysystem (one at a time) I get red letter failed.
thought maybe it had something to do with mounting so I tried a 16 gig class 10 chip instead of the 32 gig chip. no difference.
Im not giving up but am going to rtry ri go from stock to helly, to kit kat and see if that makes a difference.

---

aircooledbusses said:
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)

---

I have a spare fassy and just successfully flashed 11.1. Heres what I did.
Odin back to stock.
Flashed sc_milestone2_full
Flashed hellybean 4.2.2
Flashed TWRP then turned my phone off
Turned phone on and booted to recovery (TWRP at this point)
Flaahed 11.1 without doing any type of wipe.

---

jkok said:
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)
Click to expand...
Click to collapse
man.....I feel like a moron and I have to be doing something wrong. I can follow directions and my wife says im a good listener. but this is kicking my butt!! I appreciate the help and feel like im bothering asking for hand holding- so I really appreciate your patience.
going ge whiz route..........
after converting to rfs and flashing the kernel from cm11 it boots into TWRP and here in my problems begin.
"-When booted into TWRP do the ALL wipes (except SDCARD)"
if I factory reset all other wipes fail
if I advance wipe first either all four fail or one at a time each fail.
its embarrassing to ask how do I wipe my device, so at least I am glad this is the trouble shooting thread. lol
and thans for the sc_milestone advice, but I don't have that file otherwise I would go that route since you tried it and it works. I searched for milestone but did not find a file named the one you used.

---

The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk

---

lightningdude said:
The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip

---

tsdsbrk said:
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
Click to expand...
Click to collapse
coming from stock, ge whiz (rfs converted) or milestone I am receiving status 7, status 0 or get prop errors in recovery trying to flash anything other than the cm11 kernel
I thought it might be an error in reading sd card error so I changed it once, but it flashes the milestone from the sd card so I am not sure what is going on

---

did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.

---

tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1?
Click to expand...
Click to collapse
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.
Click to expand...
Click to collapse
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
4.Reboot recovery and you will now be in twrp
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5

---

I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386

---

tsdsbrk said:
I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386
Click to expand...
Click to collapse
Ill try just about anything at this point. Ive been using the helly 20131024, but ill try that one.
this is getting real curious. I do so enjoy pushing these older phones to their limit- this will all be worth it WHEN it works I am sure.

---

aircooledbusses said:
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
********4.Reboot recovery and you will now be in twrp********
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5
Click to expand...
Click to collapse
i highlighted the problem in alot of stars( *** ) once u are in TWRP from kernel flash u dont reboot to recovery again, that is whats causeing your errors, i tried to word it as "when u reboot into recovery" as-in when it boots up from kernel flash
try it once moire and it might work better, as when u do that the only partition it thinks u have is the kernel (boot.img, or /boot), thus /syste/ and /data arent being read to flash
as for the status 7, it might be cause the assert (getprop) on the top of the updater-script inside the zip under
META-INF>com>google>android>updater-script
edit it in NOTEPAD++!! and then put back in (without compression to solve some read-errors that could happen sometimes, but compression does make zip work, but sometimes uncompressed works faster for personal use),
then ill attach a zip for u to extract to your desktop, its a program called SignApk (notice its used to sign android zips), u will need to do this EVERY TIME u edit a flashable zip for it to flash right, to use it just extract it all into the same folder, make sure u have java (jre6+, and maybee jdk1.6.0_**+), then drag+drop the zip onto the DragApk.bat program and it will flash it with the same name with an added _signed before the zip, if u put it where your %path% system variable is u can go on command prompt and just type "signapk (zip name u edited) (zip name u want, that has to be different then the edited zip name or u get an empty zip for both)" u can leave out the second zip name and it will just do same name with a "_signed" before the extention, hope this helps =)