When we leaked the official ROM and radio image for the HTC Thunderbolt's Gingerbread update last week, users were understandably excited. An official Sense, Gingerbread ROM was probably highest on the list of demands for Thunderbolt users (aside from better battery life, perhaps).

Unfortunately, at this time, we have to officially advise anyone using any ROM based on this leak to revert to a Froyo build or to CyanogenMod 7 as soon as possible. This includes any and all third-party Gingerbread ROMs for the HTC Thunderbolt not based on CM7.

We don't take announcing this lightly, but we do so erring on the side of caution because of the extent to which this problem bricks the phone. There is no fix presently. If your Thunderbolt is caught in an endless boot loop, it is as good as dead at the moment. Our own Justin Case knows of at least ten reported cases of this problem presently - there are no warning signs and seemingly no pattern to its occurrence, and the problem can spring up days after having flashed the radio image in question.

It is especially important that you flash back to Froyo or to CyanogenMod 7. Using the leaked Gingerbread software is a violation of your warranty agreement. Verizon and HTC may refuse to replace your phone, turning your Thunderbolt into a $250 paperweight.

The glitch does not affect CyanogenMod 7 (though it is a Gingerbread ROM) because CM7 uses the Froyo version of the Thunderbolt's radio image.

Justin has provided basic instructions on how to flash back to the leaked Froyo RUU (ROM, radio, bootloader) (note: you will still have root upon flashing, and this will not overwrite your custom recovery) (this cannot be flashed from recovery, you must use the bootloader and adb):


Custom upgrade PG05IMG_MR1_upgrade.zip (md5sum : 7960c7977c25b2c8759605be264843ea)

Please check the md5sum before flashing.

To flash this file, rename it as PG05IMG.zip (windows users, please make sure it is not named PG05IMG.zip.zip) and place it on the root directory of your sdcard.

Then, reboot the phone into hboot, and enter the following command into adb:

adb reboot bootloader

And allow the update to flash.
If your phone displays "FASTBOOT", then select the bootloader option from the menu.


David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • Steve

    Exactly why I will not root my TB or do this other stuff. You guys cannot vouch for any of this, and correctly do not. You just push it out there for everyone to try as soon as some yahoo thinks he has made some breakthrough. There is no duty to rescue people who are dumb enough to volunteer their expensive new smartphones to be beta testers

    • asdf


      You won't root because you're ignorant and fearful. Using untested radio images is dumb. The ROM (including kernel) can not hurt your phone unless you're overclocking the kernel to dangerous levels.

      You can't "brick" a phone just installing a rom. Overclocking and radio images are the only risky thing.

      • Mesmorino

        Don't call him ignorant and fearful when you say using untested radio images is dumb. Who exactly is it supposed to be tested by, the devs who don't vouch for it, or the brave (and rich) risk takers who can afford to burn that kind of money? Using ANY of the radio images (tested or not) or rooting or what have you is completely AT YOUR OWN RISK.

        And what good is testing, if the fatal error is unreproduceable, strikes without warning and does not have a solution? It basically does not matter if they've tested it up the wazoo and got no errors because if it happens the only thing they can say is "sorry mate, sucks to be you"

        • jcase

          Everyone that followed the original (our) root guide (The only one, except when people removed our warnings and credits/stole our work) know the risks and were warned.

          I sure as hell put my devices on the line, before releasing something.
          If i brick, my fault. If a user bricks without me testing or warning them first, my fault.
          If a user bricks are being warned, and after I test, not my fault.
          Every thing critical put out by me, is tested before hard on my personal devices.

  • Abhishek

    I would suggest to make this post sticky for couple of days...so that every TB user have a look at it....otherwise it might tend to get lost in the upcoming articles.

    Thanks for awareness (though not a TB user).

  • Zack

    I heard that it was only phones that updated their radio that weren't rooted. Can anyone else clarify? I've had my TB running GB for a week now and its still flawless.

    • Mike

      Zack: That information is false. As stated int he post, the brick can occur weeks after upgrading to the GB radio.

      • Zack

        Thanks for the heads up man reverting back waiting for the img to download. Ill miss you so Sense 3.0 hey that rhymed.

  • Mesmorino

    @jcase (because the reply button seems to have gone awol...)

    Okay... you aren't disagreeing with anything I said. So you test it (and i'm not being sarcastic or snarky), and put your devices on the line (you have to test it on *something* after all, right?)

    If you brick the device, your fault.
    If a user bricks without you testing or warning them, your fault (I'd say their fault, but sure let's go with this)
    If a user bricks after being warned, and after you test, not your fault.

    Agreed, except that my point wasn't about whose fault it was, it was that all that testing is irrelevant because if the user bricks after you test, *it is not your fault*. In this very scenario here, the bricking can occur DAYS after flashing. Is you saying "oh but it was tested before release" supposed to make the brickee feel better?

    And would you call someone ignorant and fearful because they realise that at the end of the day, whatever happens to their device is THEIR responsibility, not some dev who tested it and got no errors?

    • TBDF

      It all comes down to developer credibility. If someone releases a patch/ROM/Mod, untested, without warnings as to its potential nature, then the fault of potential side effects falls on the developer, hurting their credibility, thus making future releases worthless to the public. It's developer responsibility, and failing to abide by it hurts the Android community.


    Everyone should have known the risk in ALPHA releases. The dev always warns about Alpha releases.....

  • adv

    But if a device got clockworkmod or stuff like that.
    Wudnt you be able to go into recovery?
    or is the radio f.. with the whole device.

  • nolmt60243

    This nasty little bootloop reboots regardless of hboot, recovery, etc. So the whole device is toast unless someone comes up with a way to break the loop.

  • Phillp

    can't you just del the radio zip on the sd card to stop the loop

  • TBDF

    What's the latest on this, anyone working at fixing this issue? I want me some gingerbread.

    • nicentral

      Seems to be mostly a hardware issue and only affecting certain phones regardless of root/non-root or ROM used. Head over to XDADevelopers and read up in their Thunderbolt forum. There's a whole thread on it.

  • Ashique

    get working update from here, checked and verified!!