Thread: Color CM 7.1 Stable is Out!
View Single Post
Old 11-11-2011, 01:52 PM   #51
sufue
lost in my e-reader...
sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.sufue ought to be getting tired of karma fortunes by now.
 
Posts: 8,140
Karma: 64613820
Join Date: Mar 2010
Location: sunny southern California, USA
Device: Android phone, Sony T1, Nook ST Glowlight, Galaxy Tab 7 Plus
Quote:
Originally Posted by goldberry View Post
Sufue why not just format your card and try it again.


Make sure the image on your card is this one
generic-sdcard-v1.2.img from here

I prefer to write my image with win32diskimager

After it is done remove put in your computer and place the latest encore 7.1 stable zip on the card along with Gapps that goes with it then put the card in and boot let it do its work and after the screen goes black, takes a while to process all the files, press and hold the power button until it starts up. You need to get wifi going before doing your google gapps setup.

p.s. I have had no problems placing the ROM and Gapps on at the same time and it saves a step.

An important thing is when it works make an image of that card and save it so in future if you want to update the ROM to another stable or nightly you simply put the new zip on the card in the boot partition and (after making another image for all your files to be saved) and reboot in recovery mode.
I did re-format (that's why I said I tried it twice) and try it again, and it did the same thing twice. And I am using Win32 Disk Imager.

I have been using generic-sdcard-v1.3.img, which verygreen's thread indicates is the latest. Maybe I'll try it with generic-sdcard-v1.2.img as you suggest - although I presume that's older, maybe there's something quirky going on in the generic-sdcard-v1.3.img. But, I sort of suspect not, since both times, after "expanding", it created the four partitions (first boot/FAT, two linux, last/FAT which occupies the rest of the card) exactly as verygreen says it should, which sort of implies the problem is not there.

EDIT: Actually when I click your link, it gives me generic-sdcard-v1.3.img also...I think it has been updated..

The problem is that when I then take my card, which seems to look as it should, and try to press and hold the power button to boot to Android, it seems to want to try to "expand" again, and doesn't boot to Android.

And, I'm using a Sandisk Class 4 as most of the threads seem to indicate, so I'm doubtful the problem is there either.

I'm now wondering if I should maybe try a different nightly, instead of update-cm-7.1.0-encore-signed?
Last edited by sufue; 11-11-2011 at 01:55 PM.
sufue is offline   Reply With Quote