aospGBMod v0.2.1 | AOSP 2.3.1 (Gingerbread)

you can use the volume key to move up/down if the trackball doesnt work. also do you have the newest clockwork recovery there? i know there were a few put out lately, due to issues like your having.
 
No, I'm in. Got the CM7 screen, force reboot at sign in Google Account. I wonder though, if I flash back to the old recovery, will it still reboot into the GB Mod?
 
straight from the page i linked you to: In order to flash aospGBMod you need the ClockworkMod Recovery installed. This is due to the need to be able to wipe the boot, system, data, and cache partitions. Most bootloops are caused by the recovery not fully wiping/formatting these partitions. Wiping factory is also recommended.

so i would say yes you could but your better off to use clockwork if you can.
 
  • Like
Reactions: chefkeyser
Can I go ahead and flash the 2.5.0.1 version though just in case I need to reboot into recovery? 3.0.0.5 is just to flash the 2.3 based-ROMS correct?
 
hey guys, trying doing this..

I just left the 2.xx cm image on, and it worked fine. But, for those of you coming from a different rom (other than CM) you should try flashing CM 6.1 first, then flash 7. I was already running 6.1, and I didn't have to wipe or anything and it saved all my apps, texts, etc.
 
  • Like
Reactions: chefkeyser
yes, i went straight from 6.1 to 7 and just flashed the gapps zip file. Maybe I got lucky? I am just glad it worked for me :) did that end up working for anyone else?
 
yes, i went straight from 6.1 to 7 and just flashed the gapps zip file. Maybe I got lucky? I am just glad it worked for me :) did that end up working for anyone else?

That didn't work, but flashing a capped kernel at 691 after flashing the ROM and gapps worked very well. And it allowed me to do so without changing the recovery.
 
Ohh, maybe it was the kernel that wasn't compatible.. I just flashed to the capped @768mhz and i forget what i had on there previously. this kernel doesn't seem to make it too fast though.
 
Ohh, maybe it was the kernel that wasn't compatible.. I just flashed to the capped @768mhz and i forget what i had on there previously. this kernel doesn't seem to make it too fast though.

The capped 691 Kernal is for stability -- 768 has proven to be unstable for certain phones and causes crashes and/or reboots.

Flashing the newest ROM now :)
 
The capped 691 Kernal is for stability -- 768 has proven to be unstable for certain phones and causes crashes and/or reboots.

Flashing the newest ROM now :)

Flashing 2/09 is causing the same bootloops. I believe it's being caused by 2.5.0.7.