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

Root [ROM] GB-CMod7-Beta

I had a serious project on my hands with this one, but it was well worth the work! Had to refresh on use of adb, fix the screen off/on animations, and had three random reboots since I flashed it. Stock 2.2.2 on my first opt m sucked, stock 2.2.1 was even worse on my replacement after I found the first one in the washing machine the other day... I was really missing cm5 on my old g1 and saw no stable port for my new phone. Sad face.
This was the answer to my prayers! Uberprops to Reppard and to all the testers that worked around the bugs!
This has revolutionized my phone, and the end product is so polished, I think we could cut out the gapps and shoot this over to cyanogen as an Optimus m port release candidate.
 
Flashed OC kernal. No boot loops. wifi works .
Overclocked stable at 806mhz!
So this kernel was from 2.2.1? shouldn't that cause problems since my phone was originally 2.2
 
2.2 can always upgrade, thats the way they made it. but downgrading is the problem.

note: if you had 2.2 to begin with and you've upgraded to 2.2.1, you can re-downgrade to 2.2--that was the old way we had to root our phones that andyo70 came up with. not to denigrate that--we didn't have root without his efforts so kudos to him.

but i have read, and perhaps this is what you meant anyway, that if your phone came with 2.2.1 to begin with, that such a method won't work for going back to 2.2. I don't know why as I didn't look much into it, but evidently it doesn't.
 
note: if you had 2.2 to begin with and you've upgraded to 2.2.1, you can re-downgrade to 2.2--that was the old way we had to root our phones that andyo70 came up with. not to denigrate that--we didn't have root without his efforts so kudos to him.

but i have read, and perhaps this is what you meant anyway, that if your phone came with 2.2.1 to begin with, that such a method won't work for going back to 2.2. I don't know why as I didn't look much into it, but evidently it doesn't.
That is correct. They made a very slight hardware change, I believe it had to be hardware if you have a phone that shipped with 2.2.1 and try to flash a 2.2 kernel you lose the screen. By that I mean when you boot up you hear the sounds but nothing on the black screen. you cant make it do anything.
Though the system is running fine it just wont turn on the screen.
 
so.. interesting thing.. my gps decided it didnt want to figure out where i was.. so i decided to download and flash gapps-gb-20110613.zip for shits and giggles. all of the apps that kept force closing on me that used the gps, e.g, Raindar.. Foodspotting.. everything that needed the gps works now.. and so far the gps knows wher ei am all the time.. but now of course that has caused another issue.. Gmail app force closes.. LOL

thinking about it again.. maybe i shouldve wiped the cache and dalvik cache b4 i flashed it.. lol.. hmm.. time for some more testing..
 
ok.. soo.. i knida messed up.. buit in the end it was very good.. tried to do a wipe and restore my backup b4 flashing gapps.. forgot that my new recovery works very well with the ext partition and wiped it.. lost me apps.. did the restore anyway.. loaded up.. almost stock cm7.. so.. since i was already there i decided to do a complete wipe and reflash from scratch.. wiped/factory reset.. wiped dalvik etc. flashed cm7, flashed r.O.C.K kernel, flashed gapps. rebooted, let it load up. rebooted after finishing and flashed the mms fix. rebooted. gps works rigth away.. no more finding me in North carolina until i clear the map cache and stuff. gmail works flawlessly. every app thats needs gps works flawlessly. not a single force close, except Root explorer of course.. but thats no biggie. just in case anyone needs the info.. i flashed in this order:
GBCM70.1a2SD.zip
r.O.C.K-v0.3-AnyROM.zip
gapps-gb-20110613-signed.zip
REBOOT to load everything
Once loaded skipped the google login stuff
Reboot to recovery
Flash
MetroMMSFIX[Gingerbread].zip
REBOOT
and flawless.
 
so.. interesting thing.. my gps decided it didnt want to figure out where i was.. so i decided to download and flash gapps-gb-20110613.zip for shits and giggles. all of the apps that kept force closing on me that used the gps, e.g, Raindar.. Foodspotting.. everything that needed the gps works now.. and so far the gps knows wher ei am all the time.. but now of course that has caused another issue.. Gmail app force closes.. LOL

thinking about it again.. maybe i shouldve wiped the cache and dalvik cache b4 i flashed it.. lol.. hmm.. time for some more testing..

Trying to flash this again I've found that leaving "Send anonymous usage info" checked during first boot and GPS was working, mostly fine. Sometimes it would locate me way off and then get it right in about 10 seconds. Changing INTERMEDIATE_POS to 0 in /system/etc/gps.conf fixed that. Then Maps would work but other apps that use GPS FC'd or wouldn't work. Then I saw your post. d/led that gapps and looked to see what was different in there that would make it work. Copied over /system/app/NetworkLocation.apk and now everything GPS related seems to be working fine. Hopefully some of that helps somebody. ymmv :)
 
glad to see you got it working. in the future, if you only have one app failing to work and FC'ing on you, it's worth it to just try to reinstall that app. If it's a system app, just see if you can get an update for it. I remember when I first rooted the old way by downgrading to 2.2, when I downgraded and rebooted, Gmail was FC'ing on me. I took my friend's suggestion and installed it off the market again (I guess there was an update available?). Worked fine.
 
I have an ext3 partition set up. Some apps i have noticed that crash. If you "move to phone" it works fine..like cpumaster had that problem
 
heres some screenies for ya..
device1.png
device3.png
device4.png
device.png
device5.png
device2.png

Just curious, how did you get it to be fully themed? for example on the dialer, how did you make the digits blue and all the arrows blue in the call log? I tried to install themes through the theme chooser and it only skins half the things that are supposed to be....
 
glad to see you got it working. in the future, if you only have one app failing to work and FC'ing on you, it's worth it to just try to reinstall that app. If it's a system app, just see if you can get an update for it. I remember when I first rooted the old way by downgrading to 2.2, when I downgraded and rebooted, Gmail was FC'ing on me. I took my friend's suggestion and installed it off the market again (I guess there was an update available?). Worked fine.

yeah when i flashed teh gapps.zip and rebooted the gmail app wasnt on my phone anymore.. had to download from market and it fced everytime it tryied to update and everytime i tried to open it.. uninstalled it and re-installed it and same thing.. that why i tryed to do the restore and etc.. int he end though was worth it.. now its just the low volume thing.. but everything else is perfect

Just curious, how did you get it to be fully themed? for example on the dialer, how did you make the digits blue and all the arrows blue in the call log? I tried to install themes through the theme chooser and it only skins half the things that are supposed to be....

I used the Blue Bionic theme from upwardspiral on the market. if you follow the link to the developers website on the market you will find a listing on xda with links to the extra theming. u will need metamorph from the market and there are 3 addition zip files u need to download to get everything themed and flash them with metamorph. they are as follows for the blue:
BlueBionicBasicMdpi.zip
BlueBionicAddonMdpi.zip and
xtremeDialerMdpiBlue.zip all available from devs website.
 
So.. i have come up with a theory.. Im somewhat of a noob when it comes to android in the fact that i have only been using and tinkering with android for a little over 2 months. In that time i have flashed pretty much everybodys phone i know. All kinds of devices, every carrier. All phones are differant and nott he same roms are available for all phones and the rooting procedure can vary from an app to having to adb everything. So my theory is as follows. I believe most of the problems with this rom stem from it being an all-in-one package. I have Flashed Cyanogen on many differant phones from CM5 to CM7. The one constant in all these flashings save this particular rom are as follows: Wipe/Reset Data, Wipe Cache, Wipe Dalvik-cache etc. Partition card if you are planning on using EXT w/a2sd. Flash CM6,CM7.zip, Flash gapps-version-whatever.zip, Flash kernel is one is not included with the particular port of the rom ur using. Reboot, and if using A2SD go to cyanogenmod settings>applications, uncheck allow moving apps to sd and select internal storage for apps. Reboot to recovery, Clear Cache, clear dalvik-cache, Flash DTa2sd-beta-whatever beta ur using.zip. Reboot. and everything is perfect. never had a problem with anything this way. Im thinking that if we were to follow this procedure for this particular rom 90% if not all of the issues would go away. in all actuality, its an extra 4 minutes tops to do it this way. This is what i did last night, save flashing the a2sd script over the already installed one.. and everything is perfect on my phone.. save the volume issue which someone is working on. just my 2 cents. feel free to bash away lol...
 
I have an ext3 partition set up. Some apps i have noticed that crash. If you "move to phone" it works fine..like cpumaster had that problem

I got the same problem. The only way to solve it is to move the apps to the phone.
 
tripdoc,
I dont know what caused my initial problems..
Never being prompted with setup for my google account. apps not working.
I did those exact steps. Downloaded in IE
I had to manully flash in gapps
 
So.. i have come up with a theory.. Im somewhat of a noob when it comes to android in the fact that i have only been using and tinkering with android for a little over 2 months. In that time i have flashed pretty much everybodys phone i know. All kinds of devices, every carrier. All phones are differant and nott he same roms are available for all phones and the rooting procedure can vary from an app to having to adb everything. So my theory is as follows. I believe most of the problems with this rom stem from it being an all-in-one package. I have Flashed Cyanogen on many differant phones from CM5 to CM7. The one constant in all these flashings save this particular rom are as follows: Wipe/Reset Data, Wipe Cache, Wipe Dalvik-cache etc. Partition card if you are planning on using EXT w/a2sd. Flash CM6,CM7.zip, Flash gapps-version-whatever.zip, Flash kernel is one is not included with the particular port of the rom ur using. Reboot, and if using A2SD go to cyanogenmod settings>applications, uncheck allow moving apps to sd and select internal storage for apps. Reboot to recovery, Clear Cache, clear dalvik-cache, Flash DTa2sd-beta-whatever beta ur using.zip. Reboot. and everything is perfect. never had a problem with anything this way. Im thinking that if we were to follow this procedure for this particular rom 90% if not all of the issues would go away. in all actuality, its an extra 4 minutes tops to do it this way. This is what i did last night, save flashing the a2sd script over the already installed one.. and everything is perfect on my phone.. save the volume issue which someone is working on. just my 2 cents. feel free to bash away lol...


Can you pm me the link to that gapps zip and I will include that and my rock kernel in the update. That make it two steps less. Thanks for the trouble shooting you are doing. Nice to see someone else being proactive with finding solutions! I worked hard on this port and i believe it to be 90 percent functional with a few little bugs. I will work on the audio stuff and some of the screen issues when I get my rig back up and running and have a broadband connection. Just bought 4 gigs of ram today I can't wait!
 
Can you pm me the link to that gapps zip and I will include that and my rock kernel in the update. That make it two steps less. Thanks for the trouble shooting you are doing. Nice to see someone else being proactive with finding solutions! I worked hard on this port and i believe it to be 90 percent functional with a few little bugs. I will work on the audio stuff and some of the screen issues when I get my rig back up and running and have a broadband connection. Just bought 4 gigs of ram today I can't wait!
I had only copied /system/app/NetworkLocation.apk out of the gapps zip and GPS and wifi/mobile based location seem to be working fine now. That might
be the only file that was missing.
 
Back
Top Bottom