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

[ROM] aospCMod | AOSP 2.3.4 / CM7 (Gingerbread) [05/23/11]

andygu3 said:
What recovery are you using, hopefully clockworkmod ;-) You will have to wipe in the partitions menu. Boot, data, cache and system. Do not wipe sd, obviously! Then flash rom and gapps. Reboot
Click to expand...

Thanks Andy. After Formating all the above partitions and flashing both the rom and gapps before rebooting I am up and running GB with out any unknown issues.

Thanks again for the help.
 
worked like a charm as per andy's instructions. now for the question of the hour...How is this different from Froyo? Auto correct on the keyboard seems better, new music player... thats about all I can notice
 
chawski said:
worked like a charm as per andy's instructions. now for the question of the hour...How is this different from Froyo? Auto correct on the keyboard seems better, new music player... thats about all I can notice
Click to expand...

With GB on only about 1% of phones right now, developers for apps are not developing just yet but I'm sure things will be developed for GB soon, imo. I feel GB is a little bit quicker;)
 
Aloha - I am Using 3.0.0.6 -
Nice recovery . If you want you need to either push through ADB or TE - I can help with TE. No issues nandroiding back to older CW recoveries.

NOTE - Google is slowly changing their Coding - Eventually you will need to update to the newer CW. This might even be the case for the Stable 2.3 (still up for debate)
 
I am sure that CWM will eventually change the recovery image when needed tom3.0.0.6, but yes it can simply be pushed through Terminal Emulator when I get a few seconds I will post the process in a thread for those that want, so we don't have to keep typing it when they start wanting to flash it, LOL ;)


MahaloCat said:
Aloha - I am Using 3.0.0.6 -
Nice recovery . If you want you need to either push through ADB or TE - I can help with TE. No issues nandroiding back to older CW recoveries.

NOTE - Google is slowly changing their Coding - Eventually you will need to update to the newer CW. This might even be the case for the Stable 2.3 (still up for debate)
Click to expand...
 
DonB said:
I am sure that CWM will eventually change the recovery image when needed tom3.0.0.6, but yes it can simply be pushed through Terminal Emulator when I get a few seconds I will post the process in a thread for those that want, so we don't have to keep typing it when they start wanting to flash it, LOL ;)
Click to expand...


Even with the lowly v2.5.0.1, I still don't have any trouble with GB, just fyi!
 
I know, but you know how peeps are they want the latest and greatest, so the option is there


andygu3 said:
Even with the lowly v2.5.0.1, I still don't have any trouble with GB, just fyi!
Click to expand...
 
So, I guess maybe it should be added to the top of the thread that AOSP Android 2.3 is best flashed with ClockworkMod recovery? That might save a lot of trouble right off the bat.

DonB, you use Amon RA still do you not? Did you have trouble flashing AOSP Android 2.3 from Amon RA's recovery?
 
I was still using Amon Recovery. It flashed but bootlooped. Flashed Clockwork though and it is running smoothly now.

One thing to note is i tried to flash clockwork via Terminal and it would not flash GB. I used ADB after and it worked. Not sure if its an isolated incident or not though.
 
That is because you need to download the new TE from the market for GB


horseinthehouse said:
I was still using Amon Recovery. It flashed but bootlooped. Flashed Clockwork though and it is running smoothly now.

One thing to note is i tried to flash clockwork via Terminal and it would not flash GB. I used ADB after and it worked. Not sure if its an isolated incident or not though.
Click to expand...
 
No I am back on CWM as I was having issue with RA and TE with Rom 9.9.2


LBPHeretic said:
So, I guess maybe it should be added to the top of the thread that AOSP Android 2.3 is best flashed with ClockworkMod recovery? That might save a lot of trouble right off the bat.

DonB, you use Amon RA still do you not? Did you have trouble flashing AOSP Android 2.3 from Amon RA's recovery?
Click to expand...
 
DonB said:
No I am back on CWM as I was having issue with RA and TE with Rom 9.9.2
Click to expand...

So, DonB, would you recommend I just switch to ClockworkMod Recovery? I plan on using the AOSP Android 2.3 ROM mainly when its finally stable. I figure switching now and redoing my Nandroids in ClockworkMod Recovery is a good idea. I like going with a recovery that will work with any ROM now and in the future.

Is the new Terminal Emulator app just an update to the old one or is it a completely different app? Do you have a link to it on AppBrain or something, so I can get the right one?
 
Yes, most have had issues with CWM mainly when they would use the app to do the commands, if you simply use it to flash your recovery, and then use the manual recovery boot to Nandroid and Flash then there should not be any issues, in your case for GB yes I would use the new CWM, mind you the 2.5 version also works, but the newer version is preferred and yes TE from the market is a new version 1.0.21 as the one that came with AOSP I believe is an older version 1.0.16.

FYI I myself have not played much with GB as I am waiting until it is a little more stable version as I use my camera quit a bit, I simply flash back and forth to play with it, lol ;)


LBPHeretic said:
So, DonB, would you recommend I just switch to ClockworkMod Recovery? I plan on using the AOSP Android 2.3 ROM mainly when its finally stable. I figure switching now and redoing my Nandroids in ClockworkMod Recovery is a good idea. I like going with a recovery that will work with any ROM now and in the future.

Is the new Terminal Emulator app just an update to the old one or is it a completely different app? Do you have a link to it on AppBrain or something, so I can get the right one?
Click to expand...
 
can I use my current TE to flash the new image, then dl the new TE, or do I dl the new TE first?
 
MahaloCat said:
Rob - if you are running CM6 you can use your current.
If AOSP .9.9.2 you need the new TE
Click to expand...

ended up using Method II on the GB Wiki

Method II

Flash recovery using: RomManager

  1. Download recovery-clockwork-3.0.0.5-heroc.img
  2. In the sdcard, go to /clockworkmod/koush.tangtgaming.com/recoveries/
  3. Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img
  4. Rename the recovery-clockwork-3.0.0.5-heroc.img to recovery-clockwork-2.5.0.1-heroc.img
  5. Go to Rom Manager and press Flash ClockworkMod Recovery and reboot your handset to recovery, you should see the orange text.
Click to expand...
only thing not listed in these instructions is that you need to move the 3.0 img into the /clockworkmod/koush.tangtgaming.com/recoveries/ file after you renamed the old one
 
That is obvious otherwise you would not have to rename the old one


ROB281 said:
ended up using Method II on the GB Wiki

only thing not listed in these instructions is that you need to move the 3.0 img into the /clockworkmod/koush.tangtgaming.com/recoveries/ file after you renamed the old one
Click to expand...
 
I just installed v0.1.7 last night and see today there is a newer version, 0.2. What is the difference? I like what I'm using now, the only thing not working is my camera and I can live without it. If I wanted to update to v0.2 do I need to wipe everything again before I install?

Thanks, Gary
 
A new ClockworkMod recovery image eh? Wow, I am always behind the times on these things. ;)

Do I really have to rename it the same name as the old ClockworkMod recovery image to get it to flash? I mean, I do not mind if I do, I just think it is weird. :D
 
Let me know when you are ready...can walk you through it.
FYI - To avoid a HUGE pain in your A$$ - Flash to a CM6 ROM before you want to do this.
 
You must log in or register to reply here.
Back
Top Bottom