8 replies to this topic

[washingtondroid]

<Long time reader, first time poster.>

HTC Inc having issues after a Cyanogen 7 flash. I downgraded firmware from 2.3.4 to Froyo 2.2 before I flashed Cyanogen 7. Cleared all cache etc. I booted up my phone and everything worked great for a few hours, or a day. I re-downloaded all my apps from Google Play and I thought everything was fine. Then all of the sudden Google Play stops working and force closes, won't let me download any more apps, (market upgraded to Play and force closes all the time, now other apps are being affected too.)

I downloaded three different google app APK .zip files and flashed each one (after deleting cache/data etc) and the same issue, Google Play still force closes and there is a message that i am downloading something that is already downloaded etc. I tried flashing JUST the Google Play APK through a file manager and it fails.... I'm lost. Last night I reflashed the latest Google Apps .zip file and now i don't even have the Market/Play or Gmail now.

QUESTION:
Any solutions? Besides reinstall ClockWork and start over from scratch. It took me a full day to figure out how to flash Cyanogen, I'd hate to have to do that again.  have an old mac that is not compatible with ClockworkMod3, so I had to use it at work on a PC...

If I do a factory reset at this time with Clockwork installed will it return to stock 2.2 froyo?

I'm lost at this point.

[bassmadrigal]

Did you do a Factory Reset/Data Wipe when you installed CM? It is required when coming from stock.

And no, doing a Factory Reset/Data Wipe will just erase any personal data on the phone (minus the sdcard). It will leave you with just CM installed.

[washingtondroid]

bassmadrigal, on 10 June 2012 - 05:08 PM, said:

Did you do a Factory Reset/Data Wipe when you installed CM?....

I'm 99% sure that I did. I followed the step-by-steps as closely as possible on the cyanogen update wiki.

I restored a Nandroid backup,back at 2.2 now, hoping a fresh install of Cyanogen 7.1.0 will work this time, (but it did last time too, for a day then everything sent wacky, force quits, media quits, all apps and Play quits...after allowing me to download all me previous apps...?)

If Cyanogen 7 proves to be unstable, at this point could I try a previous build? say 7.0? Or could I also try and experimental build like 7.2 at this point?

....sorry for my lack of understanding, I can follow enough steps to get me into trouble most times.

[bassmadrigal]

You are welcome to try any build you'd like. I would actually suggest running 7.2 RC3 as it contains a lot of new features and a lot of bug fixes.

When you install CM, do me a favor. Download CM and gapps (make sure you get the latest official for CM7 from http://goo.im/gapps) to your sdcard, then reboot into recovery, under the Mounts and storage menu select Format /system, then perform a Factory Reset/Data Wipe. After this, install CM and gapps and reboot. If you restore anything with something like Titanium Backup, make sure you only restore apps and their data. If you restore any system-related settings, you can botch your whole install.

[washingtondroid]

I think I'll try the latest CM build soon. I reflashed (?) Cyanogen 7 again as I did before, cleared the data and cache, (this time the dalvik cache, as I saw that somewhere..?) and everything is working as it should be. I am skeptical that is will hold as it got fried last time after a day or working properly, not sure how that happened? If things go haywire again, I'll try your method or suggestions above. My fingers are crossed, I so want CM to work this time on my phone. I flashed it a year ago and then returned to stock, but now I realize CM has much more to offer and I want to keep it

thanks for your input and help.

[pcd4me]

I had a similar issue a few months back. I had been running CM for months and never had any major issues. Then, practically every app started force closing. I started thinking about what I had done just before the issue showed itself. The thing that stood out was I had tried to do a *228 to update the roaming list, PRL just before this started happening. Bad idea, that utility only works with a sense ROM for the DINC. I restored to an earlier recovery and haven't had the issue since. Anytime I want to update the PRL I flash back to a stock ROM, flash to new PRL and then back to CM. The PRL is now updated. Hope this helps someone.

[washingtondroid]

@pcd4me thanks, good to know.

@bass, so everything is doing fine now. i flashed the latest stable build of 7.2, couldn't be happier, such a better device. Some weird things that I liked better on stock ROM like the camera app, but almost everything is so customizable it's fantastic.

Wonder is 9 is coming to the Droid Inc?

[PonsAsinorem]

washingtondroid, on 12 July 2012 - 04:56 AM, said:

Wonder is 9 is coming to the Droid Inc?

With JB source out, probably not. But you never know. And there are about 3 different CM9 kangs out at xda if you can't wait for official.

[ajax_borges]

Is it a requirements to downgrade from Android 2.3.4 (with the HTC Incredible) before flashing to CM7.2?

I've never rooted my phone before and never used a new MOD (other than the one Verizon put on the phone) and just want to make sure I'm doing it right. I see that on the wiki (http://wiki.cyanogen...ll_Update_Guide) it doesn't mention the need to downgrade but this thread mentions 2.2 and I didn't know if it was a requirement.