CM7 RC1 released

**PvilleComp** · 02-16-2011, 04:23 PM

Man o man and I just did a full wipe on #36. Now I gotta do it again!

Edit - Just checked ROM Manager - not there yet, gotta download from the link.

Edit of the Edit - Oooooo I should have read the link first - no need for a full wipe if you're upgrading from nightlies!

Instructions:

First time flashing CyanogenMod 7 to the HTC Incredible, or coming from another ROM?

1.Root the device and install ClockworkMod Recovery. Instructions are available here.

2.Perform a NANDroid backup of your current ROM.

3.Format the system, data & cache partitions of your device.

4.Perform a factory reset.

5.Flash CyanogenMod.

6.Optional: Install the Google Apps addon package.

Upgrading from earlier version of CyanogenMod 7?

1.Perform a NANDroid backup of your current ROM.

2.Flash CyanogenMod (your Google Apps will be backed up & restored automatically).

**davidnc** · 02-16-2011, 05:38 PM

Be prepaired for a slow download !! I almost done 60% dl now.

I will unblock the links once I am done haha

just kidding

**Majic_One** · 02-16-2011, 05:42 PM

Here's a Mediafire and Megaupload link for those who don't wanna wait.

**davidnc** · 02-16-2011, 05:54 PM

Originally Posted by Majic_One

Here's a Mediafire link for those who don't wanna wait.

Thanks what a difference its getting set to past my orginal DL (thats still downloading) haha

**Majic_One** · 02-16-2011, 06:14 PM

No Problem. I see we have the same phones. How's the Liberty on the Droid X? Thinking about flashing that on my X.

**glacierfanclub** · 02-16-2011, 06:20 PM

I'm switching from 6 to 7, and it is force closing after I flash. It will load the cyanogen 7 screen, but when I get to the welcome screen with the hand scrolling over the android, it force closes. From there everything works except for pushing it to begin.

Anyone else having this problem?

**crondable** · 02-16-2011, 06:33 PM

From what I've read over at XDA, it looks like it has to be flashed OVER a previous nightly. All the guys over there who have done full wipes have gotten stuck at the "Touch the Android to continue" screen on first boot.

**davidnc** · 02-16-2011, 06:56 PM

Originally Posted by Majic_One

No Problem. I see we have the same phones. How's the Liberty on the Droid X? Thinking about flashing that on my X.

so far liberty 1.5 has been great too.

sent using TaPaTaLk

**davidnc** · 02-16-2011, 06:59 PM

Originally Posted by crondable

From what I've read over at XDA, it looks like it has to be flashed OVER a previous nightly. All the guys over there who have done full wipes have gotten stuck at the "Touch the Android to continue" screen on first boot.

yup i flashed over the nightly no full wipe all good

sent using TaPaTaLk

**Upstreammiami** · 02-16-2011, 07:57 PM

yup i just flashed and got stuck on the welcome screen managed to bypass it but had no data and network settings fc... so much for rc1 lmao ... back to my beautiful rom

**PvilleComp** · 02-16-2011, 09:03 PM

Upstreammiami and others coming from a new rom. Here's a link to Nightly #38. It works on a clean install and is identical to RC1 if you are interested. Tonight's #39 will fix a latent rotary lockscreen image.

**glacierfanclub** · 02-16-2011, 09:18 PM

Going to install the nightly above then try to install the release candidate.

Quick question- so you say don't wipe- just install over? I should install the nightly, than go into clockwork and install the RC1 over it?

**PvilleComp** · 02-16-2011, 09:33 PM

If you install #38 + GAPPS (If you have not installed GAPPS already) and then download RC1, wipe cache and dalvik, then install RC1 it should work fine.

Slayher and some other devs have reported that they are already working on an RC1 fix for the problem. Apparently, some of the build files were not correct for the DInc. RC's are compiled by hand, not by bot. Oops - I'll post back when I see that the new RC is up.

**Upstreammiami** · 02-16-2011, 09:33 PM

That's cool man thanks I'll stick to miui

**crondable** · 02-16-2011, 09:35 PM

Originally Posted by glacierfanclub

Going to install the nightly above then try to install the release candidate.

Quick question- so you say don't wipe- just install over? I should install the nightly, than go into clockwork and install the RC1 over it?

If you really want to run the RC, yes. But I'd say build 38 is the better of two. Considering it works after a full wipe

**TheBlueCrayon** · 02-16-2011, 09:43 PM

Does anyone know if USB mounting works in more recent builds? I was running nightly #29 and it would freeze my phone every time I tried to mount it as an external drive. I booted into recovery and loaded the RC1 zip there and then flashed it over #29 (no wipe, as instructed). I am sort of new to this stuff, but my understanding is that RC1 is just a nightly that was deemed stable enough to be the first beta release. So if my thinking is correct, it should just patch everything and bring me up to par with the current release, right? I tried USB mounting after flashing RC1 and it still froze my phone. Is this an isolated incident or still a broken feature in the ROM?

**glacierfanclub** · 02-16-2011, 09:43 PM

ok, gonna use the nightly. Installed that and putting the GAPPS on right now.

**glacierfanclub** · 02-16-2011, 09:44 PM

are you reducing the cpu cycles of your phone? I think that is what does it. I had my phone set to 600 cycles when it was plugged in for instance, and that was too few. Once I corrected that problem it worked as a hard drive just fine.

**crondable** · 02-16-2011, 10:00 PM

Originally Posted by Upstreammiami

That's cool man thanks I'll stick to miui

Haterrrrrr

**PvilleComp** · 02-16-2011, 10:09 PM

Originally Posted by Punda

Does anyone know if USB mounting works in more recent builds? I was running nightly #29 and it would freeze my phone every time I tried to mount it as an external drive. I booted into recovery and loaded the RC1 zip there and then flashed it over #29 (no wipe, as instructed). I am sort of new to this stuff, but my understanding is that RC1 is just a nightly that was deemed stable enough to be the first beta release. So if my thinking is correct, it should just patch everything and bring me up to par with the current release, right? I tried USB mounting after flashing RC1 and it still froze my phone. Is this an isolated incident or still a broken feature in the ROM?

That was fixed with the new .37 kernel, but I think glacierfanclub is correct, don't underclock. In fact, with the new .37 kernel all you need to set on setcpu is a screen off profile. The battery life is really good. I'm at 52% on a 3500 battery after flashing #38 this morning, RC1 this evening and normal usage throughout the day.

**PvilleComp** · 02-16-2011, 10:11 PM

Originally Posted by Upstreammiami

That's cool man thanks I'll stick to miui

It's all about choice!

**crondable** · 02-16-2011, 10:11 PM

You could also flash either invisiblek's .37 kernel or chad's Incredikernel and use the Smartass governor which has a built in screen off profile!

**TheBlueCrayon** · 02-16-2011, 10:49 PM

Originally Posted by PvilleComp

That was fixed with the new .37 kernel, but I think glacierfanclub is correct, don't underclock. In fact, with the new .37 kernel all you need to set on setcpu is a screen off profile. The battery life is really good. I'm at 52% on a 3500 battery after flashing #38 thin morning, RC1 this evening and normal usage throughout the day.

I had some profiles set up in SetCPU but I took your advice and deleted all of them and had it reset to default speeds for the device (998MHz, scaling on demand). I went ahead and tried to USB mount again after this and it froze up still. The weird part is that it is mounting to the internal storage but not the SD card. It used to pop up 2 folders on my desktop (one for the phone storage, one for SD), but now just the one and the screen on the phone freezes after I press "OK" to the warning about applications not working while it is mounted. It's not a huge deal seeing as I don't do this too often and I do have a workaround (recovery), but it would be nice to have everything working as intended. Any more ideas? Am I missing something obvious?

**PvilleComp** · 02-16-2011, 11:16 PM

Originally Posted by Punda

I had some profiles set up in SetCPU but I took your advice and deleted all of them and had it reset to default speeds for the device (998MHz, scaling on demand). I went ahead and tried to USB mount again after this and it froze up still. The weird part is that it is mounting to the internal storage but not the SD card. It used to pop up 2 folders on my desktop (one for the phone storage, one for SD), but now just the one and the screen on the phone freezes after I press "OK" to the warning about applications not working while it is mounted. It's not a huge deal seeing as I don't do this too often and I do have a workaround (recovery), but it would be nice to have everything working as intended. Any more ideas? Am I missing something obvious?

From what you said about folders on the desktop, I'm assuming you're using a mac - I have not tried it on a mac, but I'll give it a shot in the morning when I get into the office. We keep a few around for experimentation purposes!