We have seen a few reports about this over the last few days and now it is becoming more official. Apparently the recently leaked Gingerbread 2.3 build for the HTC Thunderbolt has been causing some major issues and hard bricks for certain people. From what we are hearing the radio update in the leaked build has caused a overly large number of Thunderbolt users phones to go into an endless bootloop and currently rom builders like AndIRC have been unable to save these T-Bolts, or figure out what is causing the bricks. Has your Thunderbolt on Gingerbread bricked?

Users are being told to not take this lightly and that some have ran Gingerbread fine all week and suddenly the phone bootloops and bricks. Something is going on and developers from XDA are looking into the matter. They are suggesting everyone restores to a FroYo nandroid backup, or flash back to a Android 2.2 build for the time being. I know it is a shame to have to revert to the older version of Android, but rooting and flashing roms are not covered under warranty so if your Thunderbolt bricks Verizon or HTC can both refuse to replace the device (if they figure it out).

Please note that CyanogenMod 7 users are NOT affected by this issue. Anyone running a version of CM7 on the Thunderbolt does not need to change anything as CM7 Thunderbolt build is using the older FroYo radio and is not having the above issues. So basically for any Gingerbread rom, or any rom running the new leaked gingerbread radio for the Thunderbolt this could potentially cause issues and everyone is being advised to revert to FroYo. For more information regarding this head over to the XDA portals and Thunderbolt threads to get any questions answered.

[via XDA Developers]

  • Scott Sr1302

    I was bricked on my tb flashing cm7 through the Rom manager. I was able to recover by completely formatting and wiping all data, cache and davlik. I though it was done for but it booted up fine after I scrapped everything. For the brief period that I had the cm7 running on my tb I had what.I think was a radio fail, and was completely without service. A reboot put it to the white screen of death. Idk what happened… But I won’t be touching cm7 till there are more survival stories on the tb.

    • shogundogun

      You had flashed the radio that bricked it? If so, tell me what you did to save it… I flashed the radio update, now its as good as bricked… I can get it to do anything except see any network (other than wifi… it sees that)
      Is there another radio that I can flash to it? or am I just SOL

  • I just bricked my phone with the GB radio only yesterday… the second time… I’ll admit, I wasn’t sure about what I did the first time, but after the second phone…. ugh…. but, GOOD NEWS!!!! I have just flashed both radios at the same time, toggled my airplane mode on then off a few times, just because, then crossed my fingers and placed a test call… AND I HAVE MY PHONE BACK!!!!!

    Here is some help, but the best thing I think that helped was flashing both AT ONE TIME.


    and here’s the link for the combined radios…


    I have my phone back up and running (still on GB, after a GB radio f*ck up on my part)