• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] CyanogenMod 7 | Android 2.3.5 (Gingerbread) | Current Version: 09122011

been having lots of problems with this release wiped data tried everything i know sometimes ill get it to boot 2 x in a row others it just hangs on the boot screen even with all the defualt settings before i touch anything. anyone else been having issues?

I had mine hang on the initial install and then the second boot but since then it seems to be working fine.. Other then not liking OC'ed passed 710.. :mad: Usually I reboot multiple times after a full wipe or upgrade just to let things settle in.. Haven't really had a chance to mess with it too much though.. Getting late.. Will be back at it in the mornin..

Oh, and just FYI.. I flashed to stock first (was having gps issues and playing it safe), full wipe, and installed the older gapps from 0521..

EDIT: Spoke too soon.. about the 6th reboot it hung on me too.. Installed TitBU and was gonna reboot one last time before restoring..... Anyways.. I'll let this blue android stare at me for the night i guess :D
 
Ok, just got home from work. Left it on the charger today so battery is at 100%.
After 3 or 4 failed attempts last night, I decided to try it with the older gapps-20110307. Still hanging up at the boot screen. Waited a few minutes, pulled the battery, waited a few minutes, rebooted. Stuck. Aaaargh. Ok, so I grabbed Isaac's last build with the new gapps and it worked fine. So I'm assuming the problem isn't with the new gapps. Drat.

Just an afterthought. The fact I'm on cricket wouldn't have anything to do with it, would it?
 
Ok, just got home from work. Left it on the charger today so battery is at 100%.
After 3 or 4 failed attempts last night, I decided to try it with the older gapps-20110307. Still hanging up at the boot screen. Waited a few minutes, pulled the battery, waited a few minutes, rebooted. Stuck. Aaaargh. Ok, so I grabbed Isaac's last build with the new gapps and it worked fine. So I'm assuming the problem isn't with the new gapps. Drat.

Just an afterthought. The fact I'm on cricket wouldn't have anything to do with it, would it?
nope not at all. I think it has more to do with the kernel. I may have to leave it out next round n stick to the 710 one.
 
nope not at all. I think it has more to do with the kernel. I may have to leave it out next round n stick to the 710 one.

That was my thinking as well, since mine has never worked with any of the OC 748 builds. Works just fine on the OC 710 though, and honestly, it runs far faster at 710 or even 650 than it does at 600, so no loss to me.
 
The defualt cricket rom showed both 1x signal and 3g im on cm7 now is there anyway to get that back i realize it mainly uses 3g but i just like to see
 
The defualt cricket rom showed both 1x signal and 3g im on cm7 now is there anyway to get that back i realize it mainly uses 3g but i just like to see

I'm on CRICKET & when the signal switches from 3G to 1x it will show as 1x.

The smart aleck in me has to state the obvious here:

BE CAREFUL WHAT YOU WISH FOR! :D
 
so the new mod/build--Current Build (06182011) from PlayfulGod: CM7.1-Ascend-06182011_signed.zip--- from the wiki doesnt want to boot up for me, like it goes to a screen, with a blue android icon that says ascend.it just stays there and thats it, anybody else have this problem?
 
I think ill stick with the 05212011 build. Its seems more stable then the 06182011. Nothing really seems different about it at all, just more problems, D:
Hope to get a new release, but more stable. Keep up the good work though PG!
 
going by this last line in the 05212011 Changelog...

Do not flash the OC_748 package with this build! It needs to be updated first.

I'm betting it did not... I'm running the 05142011 currently
 
Question ppl, did isaac's 0521 build oc past 710?

No, 0514 could if you flashed the new kernel on top of the install i believe though.. Just double checked.. 0514 you could (748 kernel never worked well for me if i remember correctly) but from the wiki for 514:

New to CM7-Ascend! Since there are some users who can run 748 MHz quite well, I've included another zip that can be flashed (after gapps) to bring back 748 MHz. This is the best solution as users who can't run 748 can stay current and the CPU killers (just kidding) can have their extra MHz. You can find it in the "Download Links" section below or ROM Manager.

Says don't flash that over 521 though..
 
No, 0514 could if you flashed the new kernel on top of the install i believe though.. Just double checked.. 0514 you could (748 kernel never worked well for me if i remember correctly) but from the wiki for 514:

New to CM7-Ascend! Since there are some users who can run 748 MHz quite well, I've included another zip that can be flashed (after gapps) to bring back 748 MHz. This is the best solution as users who can't run 748 can stay current and the CPU killers (just kidding) can have their extra MHz. You can find it in the "Download Links" section below or ROM Manager.

Says don't flash that over 521 though..
k thats what I thought. That means my src had a private kernel src isaac shared with me. And as it seems to be the root of the booting issues, I think its best to leave it out next round.
 
I just downloaded & installed it today @ 6:00AM via the phone's web browser using the standard 3G signal & CM7 does work.
I'm sorry some of you are having difficulties installing & running CM7.

All I can suggest is perform a total wipe & format(except for SDcard) & attempt a direct download using the phone's browser.(3G or WI-FI)


I've used this method for all CM7 builds since 05092011 & have never experienced any issues whatsoever.
 
I just downloaded & installed it today @ 6:00AM via the phone's web browser using the standard 3G signal & CM7 does work.
I'm sorry some of you are having difficulties installing & running CM7.

All I can suggest is perform a total wipe & format(except for SDcard) & attempt a direct download using the phone's browser.(3G or WI-FI)


I've used this method for all CM7 builds since 05092011 & have never experienced any issues whatsoever.

oh okay, wait is there anything wrong with me doing this :

first i go to CWM and
wipe data/factory reset
wipe cache partiton
wipe dalvik code
format boot
format data
format system
format cache
install "CM7.1-Ascend-6182011_signed.zip"
install "gapps-gb-20110613-signed.zip"
fix permissions
is that what you do when you flash a ROM?
 

oh okay, wait is there anything wrong with me doing this :

first i go to CWM and
wipe data/factory reset
wipe cache partiton
wipe dalvik code
format boot
format data
format system
format cache
install "CM7.1-Ascend-6182011_signed.zip"
install "gapps-gb-20110613-signed.zip"
fix permissions
is that what you do when you flash a ROM?
kev, its most likely your phone and nothing you did. The kernel that got included in this build is a hit or miss on the ascend. Some run it just fine and others just wont boot. Hoping next build will work out more for the masses ;)
 

oh okay, wait is there anything wrong with me doing this :

first i go to CWM and
wipe data/factory reset
wipe cache partiton
wipe dalvik code
format boot
format data
format system
format cache
install "CM7.1-Ascend-6182011_signed.zip"
install "gapps-gb-20110613-signed.zip"
fix permissions
is that what you do when you flash a ROM?

Only perform the 'fix permissions' after d/l & installing IF you are experiencing difficulties.
It is not always necessary to fix permissions,only when you are having difficulties.
Read the 'FIX PERMISSIONS' section of 'ROM MANAGER' for reference to this.

Otherwise,your steps listed for installing CM7 are sound.
 
Only perform the 'fix permissions' after d/l & installing IF you are experiencing difficulties.
It is not always necessary to fix permissions,only when you are having difficulties.
Read the 'FIX PERMISSIONS' section of 'ROM MANAGER' for reference to this.

Otherwise,your steps listed for installing CM7 are sound.

i did it without fixxing permissions and still same result, p.s
all this crazy things have been occuring since my phone been droped in a pool bu t i quickly recovered it and, let it dryed and it worked again.
 
Back
Top Bottom