17 replies to this topic

[rjr162]

Hope someone can help me...

I'm getting stuck at installing: SDCARD:update-cm-7.1.0-Fascinate-signed.zip
It finds, opens, and tries to install the update.

It fails at

assert failed: getprop("ro.product.device") == and then all the different model options/
The error is:
E:Error in /sdcard/update-cm-7.1.0-Fascinate-signed.zip
Status 7
Installation aborted.

I know early on I had a similar issue with my Galaxy S because it was a GT-i9000T and not the standard GT-i9000 (Although since the first update I did via Samfirmware.com or CM7.. can't remember which... it shows as a i9000 anymore without the T). But since this is made for the SCH-I500/Fascinate, I'm not sure why this is popping up.

Did manage to fubar the whole file system early on and recovered via heimdall using EB01. Was going to try the suggested MIUI 1.11.25, but even with 1.12.x all the links point to expired or removed dropbox areas.. can anyone provide some help?

[crommy74]

rjr162, on 19 January 2012 - 03:06 AM, said:

Hope someone can help me...

I'm getting stuck at installing: SDCARD:update-cm-7.1.0-Fascinate-signed.zip
It finds, opens, and tries to install the update.

It fails at

assert failed: getprop("ro.product.device") == and then all the different model options/
The error is:
E:Error in /sdcard/update-cm-7.1.0-Fascinate-signed.zip
Status 7
Installation aborted.

I know early on I had a similar issue with my Galaxy S because it was a GT-i9000T and not the standard GT-i9000 (Although since the first update I did via Samfirmware.com or CM7.. can't remember which... it shows as a i9000 anymore without the T). But since this is made for the SCH-I500/Fascinate, I'm not sure why this is popping up.

Did manage to fubar the whole file system early on and recovered via heimdall using EB01. Was going to try the suggested MIUI 1.11.25, but even with 1.12.x all the links point to expired or removed dropbox areas.. can anyone provide some help?

I'm having the same problem!

[fletcher969]

Ok, information diversity overload!  Ran into a glitch trying to install CM7.1 onto my GF's Fassy, and honestly, I think the sheer diversity of conflicting information regarding the right way to root, install CWM, and upgrade new ROMs is almost overwhelming for the Fassy.

Anyway, I rooted her phone using Odin with the Atlas 2.2 pit, the eh03_full_odin.tar, and I "think" CWM_recovery_all.zip (at this point I can't specifically recall due to all the solutions I've tried, most of which didn't work).  So, she's rooted, but when I've tried to upgrade her to CM7.1 (update-cm-7.1.0-Fascinate-sgned.zip) from CWM after wiping data and caches, I receive the "assert failed: getprop("ro.product.device") ==" response (incl. Status 7).  It may be worth noting I've tried installing it as update.zip also from the sd root also.  Curious if turning off signature check might work, even thought the ROM appears to be signed?

So, my question is:  Given where I am currently, should I follow this forum's wiki's suggestions, or will I have to perform some backtracking to a stock ROM as some other threads on this and other forums have suggested is the best place to start, will I have to modify the bootloader, install a newer version of CWM, etc?  Again, I find so many different approaches online, I figured it's best to just toss it out where I am currently, and see what's suggested.  Here's the relevant info:

Kernel: 2.6.35.7
Firmware: GB 2.3.5
Build: EH03
Baseband: S:i500.04 V.EH03
CWM: 2.5.1 (Voodoo)

Thanks for whatever suggestions...

EDIT:  Turned out the Class 10 card she had purchased was the problem.  Put a smaller Class 4 card in it's place, and all went well with the CWM4 for CM7.

Edited by fletcher969, 09 March 2012 - 02:16 AM.

[pastoryusuk]

People had the same problem with the nook color (I was one of them).  Something about the way Android writes to higher class micro SD cards.  Class 2 8GB worked for me.  Class 6 8GB did not.

[ultorCorp]

Hey everyone,

I am having a horrible time with this thing. I have tried to follow the instructions listed in the guide to the letter, but I fail before I can even really start.

I have rooted previously in the past, but did not install a custom ROM on this as I just wanted to use Titanium to get rid of a few default programs. The issue I was running in to was at the part where you commandline enter in the %dir%/heimdall flash --recovery recovery.bin I get an error message saying it cannot find any attached devices. I have installed the stock Samsung drivers, rewritten over them with the zadig.exe (I see the 'Gadget Serial' option instead of the Samsung one) and tried it repeatedly. Nothing works there.

So, thinking I was clever, I tried to use Odin to accomplish the same task. Worked like a charm. Got it to get to the newer version of CWM and got all the options I should have gotten.

Continuing on, I put the CM7.zip file on the SD card and reset into CRM (the one with blue text). Formatted to default, cleared cache/Davlik, selected install from ZIP file, selected it, and started the install. Progress bar gets to about 1/4 complete, then the phone resets on its own. When it comes up, I see Samsung, then it changes to Galaxy S Cyanogen Mod 7, then back to Samsung.

Thinking I was nearly there, I let it sit. For about 5 minutes. It just kept doing this, so I figured something was wrong. I removed the battery, and tried to do the install again. Same issue. So I tried to just straight up boot. Comes to the same Samsung/Galaxy S Cyanogen Mod 7 screen.

I cannot access the default ROM as I was an idiot and didn't back it up when I started.

So now, my phone is a brick that knows 3 words and a number.

I did remove the SD Card and looked at the CMR logs, seems that it is having issues with the mounting of the SD card. I don't know if there is a way to fix this or not, but now that I am stuck, I have no real recourse.

Thanks in advance to everyone. If you want me to post the logs of the CMR, I will.