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

Root Gingerbread for Thunderbolt?

crazy8

Newbie
So last night something very exciting and yet sad happened to me last night. There was a screen on my phone that popped up saying there was an update from Verizon which was 73MB in size. Now something that big I assumed it was probably Gingerbread. I am currently running rooted Android 2.2 Froyo right now.

I chose "OK" from the pop up screen to go a head and do the update. Well after it did its thing for just a bit the phone restarted, which the pop up screen said it would do, and there was a droid on my screen with a loading or install progress bar under him and then a "!" appeared next to the droid guy and I left the phone on all night and when I woke up this morning, it was still like that.

I have ROM manager on my phone and I am new to rooting. If this is indeed the long awaited Gingerbread, or even if its not, how can I go about successfully installing this update being pushed to my phone?

Thanks in advance for any help with this.
 
I am currently running rooted Android 2.2 Froyo right now.

I chose "OK" from the pop up screen to go a head and do the update.


There is your problem. NEVER EVER accept an OTA update when you are rooted. EVERY SINGLE guide to rooting tells you this. This is exactly why people need to read everything about rooting so they know what they are doing.

And, no, that update isnt gingerbread.
 
There is your problem. NEVER EVER accept an OTA update when you are rooted. EVERY SINGLE guide to rooting tells you this. This is exactly why people need to read everything about rooting so they know what they are doing.

And, no, that update isnt gingerbread.

Thank you! There is a sticky thread in this section with *****'s around it saying not to accept any updates if you're rooted. I wish people would actually read the stickies. They're there for a reason after all :rolleyes:
 
Please keep it civil guys, you turn noobs into pros by educating, not chastising. :)

I wasn't chastising, I'm merely pointing out that there are threads put in place here to help people who don't know as much as the "veterans" and most choose not to read them.
 
Has someone sent a PM to the OP? I had a thread moved before and couldn't find it. They wouldn't have seen the sticky if they posted it in the wrong section
 
Has someone sent a PM to the OP? I had a thread moved before and couldn't find it. They wouldn't have seen the sticky if they posted it in the wrong section

When guides/mods move a thread we leave an "expiring redirect" which keeps the thread in it's original location for a period of time after it's moved. Most leave a one week redirect. Seeing as how the OP is new I'm sure alostpacket informed him by PM as well
 
Okay I assume this was in the "Android Applications" section as that is where I usually see alostpacket, those threads get buried quickly when not bumped and when one gets moved it no longer gets bumped in the other area of the forums.
 
Already done, wasn't at a CPU earlier so wasn't really able to. It just seems like people doing this is happening more and more, I hope when the GB update hits it doesn't do something when people accept it that prevents the phone from getting back into recovery.
 
Sorry I am just now seeing this. My forum etiquette is much better than I think I lead you all to believe. I am a member of many different forums and I am aware of the stickies. I guess I got to "Android Apps" and thought thats where I should post this, without looking further so I apologize. That was completely my fault. I will do better. :) Thank you all for your help. So maybe this is where I should be going to look at that sticky, but out of curiosity once GB is released what are the steps a rooted TB user should take to correctly install GB, keep of if his apps, data, settings, etc.?
 
If you are rooted you should wait until the rooted rom is released, then use titanium to backup all your apps once the rom is available and flash the rom
 
Back
Top Bottom