jt vanilla gingerbread

[nextjeter2]

in rom manager there is now a gb kernel mtd only.. anyone have an idea what it is?

 

[jjcasillas15]

v5 is up on ROM Manager...

 

[curley]

in rom manager there is now a gb kernel mtd only.. anyone have an idea what it is?

I believe that is the V2 kernel.

 

[Kashara321]

I was running this V3 getting ready to move to V4 when it fried my SD card on the two phones i put it on...

Granted I upgraded to this before the great step by step instructions came out so I may have done something wrong in setting them up...

Anyone else running into SD issues or have the SD card issues been resolved in these more recent releases?

thanks

 

[Landshark]

I was running this V3 getting ready to move to V4 when it fried my SD card on the two phones i put it on...

Granted I upgraded to this before the great step by step instructions came out so I may have done something wrong in setting them up...

Anyone else running into SD issues or have the SD card issues been resolved in these more recent releases?

thanks

You probably didn't do anything wrong. I think jt discovered there was something from GSM left in the code, and since our phones run on CDMA.......fried sd cards. As has been discussed in this thread, right now the best chance to avoid a future sd card fry is to load the GB bootloaders and use jt's V2 kernel.

 

[curley]

I was running this V3 getting ready to move to V4 when it fried my SD card on the two phones i put it on...

Granted I upgraded to this before the great step by step instructions came out so I may have done something wrong in setting them up...

Anyone else running into SD issues or have the SD card issues been resolved in these more recent releases?

thanks

Mine Fried also going from v3-v4. BUT you can run the Glitch Kernel also. That has been successful. Just don't run GB Bootloaders, since it is a froyo Bootloader. Read the post for glitch's kernel.

 

[sfobrien]

I believe that is the V2 kernel.

He has posted V3 now.

 

[curley]

Just read, someone lost their card on glitch. Still proceed with caution.

For best results I think everyone should back up their card, then r-format the card in gb. This seams to prevent the card fry.

 

[Snareman]

Anyone else having problems updating their roaming? When I do it, the voice tells me its worked, but then I get a message saying that it hasn't and then my signal goes to an X until I reboot. Also, oddly, I can text and talk, but am having trouble getting to stuff in the Market and internet. Ideas?

 

[curley]

Anyone else having problems updating their roaming? When I do it, the voice tells me its worked, but then I get a message saying that it hasn't and then my signal goes to an X until I reboot. Also, oddly, I can text and talk, but am having trouble getting to stuff in the Market and internet. Ideas?

You may need to switch your phone. I had the same problem, I had to activate an old VZW phone, then let it sit (I did for 15 minutes) and reactivate my Fassy last night. My 3G works fine again.

the update is an issue, but you do get the updated towers, so just reboot and you should be fine.

 

[Eaglesrulez]

I need to get backup assistant to get my contacts because apparently google didnt sync correctly so if anybody knows how to get backup assistant on Vanilla GB please tell me. Also is it possible to get your contacts back from titanium backup?

 

[sushiguy732]

I need to get backup assistant to get my contacts because apparently google didnt sync correctly so if anybody knows how to get backup assistant on Vanilla GB please tell me. Also is it possible to get your contacts back from titanium backup?

Are these your Google Contacts? If so you should be able to go into Accounts and Sync and make sure that Sync Contacts is checked.

 

[Eaglesrulez]

Are these your Google Contacts? If so you should be able to go into Accounts and Sync and make sure that Sync Contacts is checked.

No they weren't correctly synced with google and backup assistant is the only thing that synced correctly

 

[Snareman]

You may need to switch your phone. I had the same problem, I had to activate an old VZW phone, then let it sit (I did for 15 minutes) and reactivate my Fassy last night. My 3G works fine again.

the update is an issue, but you do get the updated towers, so just reboot and you should be fine.

Thanks. But I finally gave up and went to ComRom2.0 after having (and reading about) enough issues with the vanilla.

 

[Kjshearer]

has anyone gave this a try and what is your experience versus the CM7

Yeah this is a stripped down version of CM7 (so very bare). It's fast (as fast as CM7 easily) and lightweight (just as jt said in the OP).

There are a lot of customizing options in CM7 that aren't in this Vanilla version. Copilot doesn't seem to work on CM7 (I know of two separate people trying CM7 and Copilot), so this is a good alternate.

I can't think of any reason to use this instead of CM7 though...I'm guessing this is slightly faster (probably not noticeably) but only because it has a smaller footprint (fewer options).

 

[HappyG1970]

i cant even get the cm7to flash from my rom folder i put on my sd card. get the same fail, asserts failed. something 7..... that made the 5th time i tried. i read really good thins about cm7, and most of my classmates rave about it. seems to be me, sabban and others can get it to work. am i not talking "nice" enough to the stupid phone? nee some help while i still have hair. plz :'(

 

[sparesr4sissies]

i cant even get the cm7to flash from my rom folder i put on my sd card. get the same fail, asserts failed. something 7..... that made the 5th time i tried. i read really good thins about cm7, and most of my classmates rave about it. seems to be me, sabban and others can get it to work. am i not talking "nice" enough to the stupid phone? nee some help while i still have hair. plz :'(

You just need to make sure you follow the directions. It sounds like you're using the wrong version of ClockworkMod.