yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] tx3kgtman:
ohh no now we have a downgrading brick chance!!! what to do??? stay on gb and risk brick or downgrade and risk brick?

lol on a serious note how much battery did you have left before you tried to downgrade? sounds like its dead. Try a battery pull and or charge it.
[Thunderbolt Android Development] psicrest:
I got a bootloop experience.

I got a freshly charged battery so I turned on my 4G to tether to my tablet, after few minutes my phone suddenly died, tried to turn it on, goes to the bootscreen then turned off automatically, there are times i can manage to get to boot animation/ sometimes it goes to HTC screen then dies.

I tried going to the HBOOT, but phone dies automatically before i can do anything. Good thing bought an external battery charger and 2 extra battery from ebay for $11. I swap my battery to a freshly charged one using the external charger, and my thunderbolt is now back to life. It seems like the GB rom is not charging the battery properly I probably had a low battery but the rom reports that im around 80-90%.

Im not sure if this is the case to other bricked phone, but for a second i though my phone was bricked.
[Thunderbolt Android Development] Dstu03:
I dont think you are bricked at least not from the radio issues of GB they are causing bootloops you sure you had a good battery when you flashed
[Thunderbolt Android Development] gifferjesus:
I was diggin' GB but yeah, I don't insure my phones and thus am not risking a brick THAT probable just yet. I shall return to Gingeritis as soon as they solve this though, I miss some of the neat features.
[Thunderbolt Android Development] :
Can we reload the 4.4.7 BAMF radio with the 1.6.3 instead of the stock radio one?

If I was not hearing the Dev,s advise switching I would stay too! Having no issues at all currently,, bummer, tycoon 4 all the hard work! Gb will be back this was an alpha.

Cheers,
[Thunderbolt Android Development] gifferjesus:
Won't work with GB.
[Thunderbolt Android Development] Dstu03:
Load the lastest Froyo radio in hboot then flash a froyo rom through cwr

Its truly not worth bricking your phone over wanting some cool features of GB
[Thunderbolt Android Development] maizekidstill81:
[x] Back to froyo

[x] Looking for Bamf 1.6.3

[ ] Loving it ..........negative
[Thunderbolt Android Development] htowngator:
Yea i have been holding out for a while because I didnt trust the alpha rom after watching people have so many issues.

My bamf froyo rom is rock solid and gets awesome battery life.
[Thunderbolt Android Development] qumahlin:


I see replies to the contrary...so ill just wait and see :)
[Thunderbolt Android Development] qumahlin:
Also i don't know why people are talking about insurance. You don't need insurance. If the phone is still in its warranty period a vzw corp store will swap it for you right there. No asurion claim needed

Well providing you don't have any obvious root looking stuff at boot

Can always flash same radio twice to make it a real brick
[Thunderbolt Android Development] corenojoe:
Warranty only covers manufacturer defects. Don't think bricking it because your using a leaked radio counts lol.

Although most Verizon employees wouldn't know the difference anyways lol I seriously think any one of us could be CEO of that company within a month if we got a job there and they found out we had even a clue about how phones work.
[Thunderbolt Android Development] Southern_mind:
Yeah I love landscape rosie

Sent using Tapatalk from Thunderbolt with Lighting Rom 3.3.1
[Thunderbolt Android Development] ataranine:
Really?

No.

Nowadays, it's all about WHO you know, not WHAT you know.
[Thunderbolt Android Development] qumahlin:
Yup they don't. Ive bricked two incs from bad radio flashes and had them returned as defects.
[Thunderbolt Android Development] michaelkahl:
Thanks jcase for the warning. I'm back to Froyo. I can't wait on a claim.
[Thunderbolt Android Development] zxsix:
You bastard!

;)
[Thunderbolt Android Development] micompcs:
You obviously don't know how cell phone companies work.

And, yes, I work at vzw.
[Thunderbolt Android Development] chayesfss:
so glad I read this before I flashed.
[Thunderbolt Android Development] stastnysnipes26:
Does anyone know if this has anything to do with flashing through ROM manager/not wiping data? I think I'm gunna risk it. If I brick, ill pour some water on it and pay my insurance deductible
[Thunderbolt Android Development] wooddale:
I can wait until it gets fixed. Had I been home I would probably did it but Im in the north woods of Wi lucky I can get a signal Im tethering with my phone on a pole outdside the cabin whatever works
[Thunderbolt Android Development] micompcs:
Here's the scoop on what happened to me. I was on das BAMF 2.0-5 and things were not acting right, so I switched back over to 2.0-4.01 and as soon as it cycled to reboot it went into a boot loop. It didn't have time to do anything. Didn't even go into recovery. Just boot looped. I pulled the battery, started it up in hboot, clicked recovery, it went to the recovery screen with the rom manager logo acting like it was going to flash, and after about three seconds it went straight back to boot loop.

So, I flashed the pg05img.zip in this thread, and, to no avail, removed the battery, went into hboot, hit recovery, and tried to flash another rom. After about 10 seconds of being in recovery, the device went back into boot loop.

I cannot access recovery, in any form, for more than a few seconds before it reboots into loop mode. No time to flash a new radio, rom, or anything else for that matter. Make of it what you may, I haven't got a clue how, or if its even possible, to fix it.
[Thunderbolt Android Development] matt.simpson:
I put the radio I had on the SD card on first, then rebooted, choosing to skip install this time.

Rebooted, moved radio file out of SD root, reported into recovery and restored backup of bamf 1.6.3

Running smooth.
[Thunderbolt Android Development] matticus:
Any other common threads?

I have been reading through the thread and wonder if there is anything common among all the bricks besides the radio. It seems with these being somewhat isolated situations, there may be something additional in common. On the bricked phones were they all using stock batteries or something aftermarket? Were they plugged in at the time? What type of charging was used, wall or USB? OEM charger or otherwise? Any unusual behaviors at all previous to bootloop like strange behaviors while being connected to the charger or pc? (I add that one because as I am typing I have my Bolt plugged into my laptop and at random intervals, I keep getting the "New device plugged in" and "Device unplugged" sounds.)

I am torn between playing it safe and going back to froyo and keeping a close eye on my phone's behavior so that in the event it does tank and boot loop, I can at least try to shed some light on the reason behind the issue. Besides, if it does decide to give up, I can probably find a phone or two around the house with some of Adrynalyne's handiwork on it. I think I still have my Omnia in a drawer somewhere.
[Thunderbolt Android Development] gsxraddict:
Just curious as to how this was narrowed down to the radio? Not challenging it just a straight up question. <---just so no one takes it wrong.
[Thunderbolt Android Development] onyx_64:
micompcs, Are you using the new 3.1 ClockworkModRecovery?

And did you mean you were able to flash the pg05img.zip in HBOOT, in this thread , or tried to and didnt work?

Sorry about the phone..
[Thunderbolt Android Development] burntorangefan:
@jcase, appreciation from Seattle. Wading thru 48 pages of mind numbing drivel it's easy to lose sight that some of us have careers and families and while we love playing with our phones, bricking would be a big deal...helping keep us from screwing ourselves is something you don't have to do, but do. I'm gonna ignore the dummies that think you and adryn aren't doing the community a service because that's simply idiotic.
[Thunderbolt Android Development] micompcs:
I'm using v3.0.2.5. My phone bricked before I was able to flash the new one. And, yes, I was able to flash the PG05IMG.zip in hboot. It did nothing, however.
[Thunderbolt Android Development] happimeal:
Im just guessing but id say if it was the ROM, you would be able to bypass loading it by loading into recovery or bootloader first, since its the radio, it gets loaded no matter what.

Again, just a (somewhat educated) guess.
[Thunderbolt Android Development] joshw0000:
I bought my Thunderbolt, my wife's, and 2 others from Craigslist. I have no insurance on any of my phones. Guess what I'm doing?
[Thunderbolt Android Development] TMYINC:
I took the red pill....is that bad? lol
[Thunderbolt Android Development] onyx_64:
Thanks for the reply! I was beginning to wonder if it were the CMR 3.1 tht was causing it, but evidently, its not. Thanks for your inputs..

guess its back to froyo for me.
[Thunderbolt Android Development] joshw0000:
Yea, I think jcase stated something along those lines many, many pages ago. The fact that CM roms are not reporting this bootloop of death and they run on Froyo radios reiterates your response.
[Thunderbolt Android Development] ska.t73:
Well then they are not having the same issue. The issue that this is about is an unrecoverable bootloop. You can't fix it, you can't flash anything.

Please point out where in this thread you have seen someone who knows what they are talking about reply to the contrary.
[Thunderbolt Android Development] AlpineM3:
The proof is in the amount of people claiming to have a bricked phone running Gingeritis.......none
[Thunderbolt Android Development] tekhna:
Correlation is not causation, and further, the sample size might be much smaller. BAMF is a pretty popular ROM.
[Thunderbolt Android Development] ska.t73:
Really!?!

I'm sorry but just because the 12 people that are running Gingeritis haven't had this happen doesn't mean it isn't happening.

Seriously heed the warning or not, just don't get but hurt if you happen to brick and we all laugh at you.
[Thunderbolt Android Development] astang99:
can we all just play along nicely, lol, it has to be the radio, its the only thing thats the same across all the GB roms...
[Thunderbolt Android Development] erishasnobattery:
Not saying one is any better than the other, but you're looking at nearly 240,000 views on BAMF vs 120,000 on Gingeritis. When there's only about 10 confirmed reports of this, it's very likely noone on Gingeritis has had that misfortune yet.

After witnessing it first hand, I flashed back so fast my SD card smoked...
[Thunderbolt Android Development] ska.t73:
But didn't you hear no one that uses Gingeritis has had this issue... It can't be the radio...

And yes that we sarcasm...
[Thunderbolt Android Development] joshw0000:
The nature of the problem itself clearly lies the blame on the radio. I've bootlooped several different devices because of bad roms, beta roms, and just plain dumb/reckless flashing. I've always been able to recover the phone by booting into recovery (stock recovery on my DX). The fact that you can't boot into recovery or even bootloader means the problem is deeper then the rom.

Why are so many people ready to throw developers under the bus and risk bricking a very expensive phone? I, for one, value my phone and the developers who make it awesome.
[Thunderbolt Android Development] Ryanmo5:
Thread stuck until further notice..
[Thunderbolt Android Development] khanam:
if its the radio which might be causing issues, its simply not worth the risk trying to play russian roulette with it. a radio issue is the most serious kind. rom/kernel issues are easy to solve, not so for the bootloader/radio. a bad one will normally brick your phone and there is nothing called a solvable brick. a brick is a brick. your phone is dead and gone to meet alexander graham bell, its ultimate maker.
[Thunderbolt Android Development] jcase:
Citation please, because I do not believe this to be true.
[Thunderbolt Android Development] iastonish:
So just flash that pg05img in the first post in hboot to go back to the froyo radio?
[Thunderbolt Android Development] jcase:
you do understand, all the GB roms are pretty much the same deep down inside? 100% based off the same leak.
[Thunderbolt Android Development] ska.t73:
This is from AlpineM3 over in the Gingeritis thread. Lol is this kid serious?
[Thunderbolt Android Development] KDKobes:
One thing I noticed off the bat with the ginger roms is the battery issues everybody seem to have. Whether its the battery charging forever or not showing the correct charge...I can't help but wonder if dock mode has anything to do with it. Everytime I plugged in the device dock mode would run in the background and it seemed I could charge it for hours to have it show it only charged 30%. After removing dock mode its been just fine.
[Thunderbolt Android Development] ska.t73:
Yep I was pointing out how stupid the Gingeritis kids are for acting like this is a ROM issue because it hasn't happened to any of them.
[Thunderbolt Android Development] jcase:
Yeah i quoted the wrong person, <3
[Thunderbolt Android Development] freebird_78:
I was thinking the same thing about the battery issues. I was running the GB leak from the first hour it was leaked here, but never once had any battery issues. In fact, battery life might have even been better for me. I was getting 2 days to a charge in town. Wondering if I jumped the gun reverting back to 1.6.3. I do really miss GB.
[Thunderbolt Android Development] bamaredwingsfan:
My phone is too important to me to risk bricking it. About 4 weeks ago, my phone played a big part in probally saving my life. I was out on my delivery route, and got a call to take cover ASAP. 5 minutes later a F4 tornado came an wiped out the area i was heading to. If not for getting that call, i might not be here today. So i returned the favor an reverted back to froyo;)
[Thunderbolt Android Development] jcase:
All had GB leak radios

All had roms based off the same GB Leak (ignore the ignorant who claim one rom or another doesnt have the problem, as they don't have the full details)

All were thunderbolts.
[Thunderbolt Android Development] want a droid:
Jcase how is that possible fix for bricked thunderbolts coming? I saw your tweet on it. If it's >50% chance of saving a bricked phone I'm going to go back to GB.

Small percentage of bootlooped people + possible fix if I do get bootloop = back to GB
[Thunderbolt Android Development] ska.t73:
Yea you should see him over in the Gingeritis thread trying to whip up the fanboys... Says he wants to stop the spread of false info that it isn't rom related... Lol
[Thunderbolt Android Development] gifferjesus:
I'm a fan of Gingeritis but yeah, some of the other users are a bit dickish, it's embarrassing sometimes.
[Thunderbolt Android Development] DroidTh3ory:
LMAO, I knew someone like you in High School... "Hey guy's, listen to what Jimmy said about Dave's girl. Look really, he said that. Can you believe it?"

You say he is trying to "whip up the fan boys" when you C/Ped a quote from him, to bring over here, trying to start ****, swinging from the Devs nuts.
[Thunderbolt Android Development] Asmodeus6:
Easy there... not all of us are completely stupid. Some of just read EVERY post in this godforsaken thread to see if any USEFUL information had surfaced as to the actual cause, radio or otherwise.

Ok maybe we are stupid... continue reading... :o

I'm having a real tough time with the volume buttons in my TPU case on this phone. I flashed the GB radio twice. By accidently pushing the wrong volume key.

Yup. I sat there with the OMFG :eek: [Cartman voice] NOoooOOoooooooo face on the whole time it did it's thing. Hit power and as soon as it booted out of Hboot I yanked the battery. Figuring I was probably totally effed.

It wasn't.

I've been running Gingeritis for a couple days now.

As to the post pertaining to the "who has a brick that had cm7 on their phone first" stuff. Negative. First thing I flashed since I loved it on the Incredible. Not loving it *yet* on the TB. So I downloaded all the previous radio's from Adrenalyn's radio thread and flashed something GB. Ginigeritis looked cool so on a whim I flashed it. My battery takes a million years to charge but it lasts TWICE as long. Seemed good enough to hang around on it and watch the rom /kernel develop further. (to those of you throwing rocks at the rom.) Opposite on the versions of Das BAMF I tried thus far. Stripped and remix.

I may flash the phone back to the stock rom I debloated myself and wait it out. I may not. At the end of the day, what I can do, that most of you can't do is walk in the back of my store and switch my own phone out with a new one.

Thanks for the warning jcase and adrynalyne. And for your all your work.
[Thunderbolt Android Development] ska.t73:
Well jack ass he was the one to say (in the very quote I used) that everyone should come over here and back him up.

I'm sorry if knowing what I'm talking about means I'm "swinging from the devs nuts". The stupid kid is spreading all sorts of bad info that could cause people to ignore a pretty serious issue. I'm sorry that you are too much of a fanboy to see that.
[Thunderbolt Android Development] jcase:
It was a theory posted on reddit, and it does not work. (as suspected)
[Thunderbolt Android Development] BryanP:
conclusions with data

It might be helpful to create a question list or multi option poll to try and find some commonalities in the boot looping bolts. I'm also wondering if it could be a battery incompatibility causing the battery to not charge or the phone to shut down thinking the battery is low. http://xdaforums.com/showthread.php?t=1096704 Hopefully this can be quickly confirmed or denied by others who are boot looping. Since we dont know how many people are running each GB rom it's hard to create a statistical argument but if nobody has had an issue except those on bamf than at least to me it's at least worth mentioning which rom was being run when the boot loop started. bamf 2.05 did seem to drain my battery faster than normal but it could very well be related to not being able to leave the phone alone.

previous radio

Rom when boot loop appeared

Cleared Cache before flashing

tried fresh battery

tried alternate charger (grasping at straws but easy to test)
[Thunderbolt Android Development] jcase:
Some people are being very ignorant.
[Thunderbolt Android Development] micompcs:
It would also be helpful if you read some of these posts before creating one of your very own.

The battery issue has been debunked, as is stated in the OP.

The commonality list has been generated, based on all known bricks that suffer from this exact type of boot looping.
[Thunderbolt Android Development] Farva0412:
So I just flashed a froyo radio and cm7 should o be okay? I only ran gb for 3 days.
[Thunderbolt Android Development] gifferjesus:
I would think so.
[Thunderbolt Android Development] DroidTh3ory:
No name calling in my post....

Anyway, I am not defending him, I think the statement that is ROM specific is nonsense and nobody else is really jumping on that train either. When this was posted people divided... some reverting and some sticking it out. In the Gingeritis thread, it was discussed, Chingy asked who was sticking around and made a decision to keep it going.... for someone that "knows what they are talking about" you should have read through how it all played out in the first place before showing up to the game late trying to be the couch.

People are continuing to use Gingervitis because we don't believe it is affected, but because it has been decided.... its not that big of a ****ing deal.

LOL
[Thunderbolt Android Development] tsachi:
Boot looped and survived

I got stuck with the white HTC screen. Unfortunately I didn't have a chance to look at the threads this afternoon, and when I saw what it means, needless to say my face turned whiter than the HTC load screen. Only thing I could do is go into bootload and flash radios, which as many people mentioned before doesn't help. I ended up taking one of the full restores (Mecha_9600_NV_MFG_VZW_1.64_0211_PRL58008 which I had from the original rooting) and used a card reader to load it on my sd-card. After it ran it's course I restarted and was relieved to hear thunder crushing. I am now at non-rooted stock, and the phone is working.

I hope more of you out there manage to get out of this, and I would definitely recommend against using the GB until the next leak.

If you want to try the one I did it is from an old post. There is a newer version at http://xdaforums.com/showthread.php?t=996616 that may also work
[Thunderbolt Android Development] patalo:
^

Coach, not couch. Grammar Nazi right here :)
[Thunderbolt Android Development] jcase:
This is a cross post from Chingy's thread, on my personal thoughts RE takign the risk.

I'm not chingy but I am going to give you my non-asked for two cents.

Users are aware of the issue, and the rarity of it. It is a personal choice, just like the choice to speed to make it to work on time.

If i had enjoyed the GB roms (I never ran them beyond testing, too iffy for me), then I would be taking that risk. I also have spare phones and the means (and desire) to buy a new phone.
[Thunderbolt Android Development] ska.t73:
Thanks for that... I actually enjoyed GB, i however can't risk losing my phone. I really don't think we will have too long to wait for a better radio...
[Thunderbolt Android Development] oscar925:
could you wipe everything flash froyo radio,reboot to GB,go to recovery and flash a froyo rom?
[Thunderbolt Android Development] BryanP:
I do read thank you. The OP was edited between starting and posting.
[Thunderbolt Android Development] micompcs:
The OP was edited an hour and a half ago...
[Thunderbolt Android Development] SteveDusa:
Just to play safe, I've reverted back to the MR1 radio and BMAF Remixed 1.6.3.

I am going to miss the few things GB offers that Froyo doesn't... WORKING ActiveSync Exchange for Hotmail Plus. GB syncs correctly but Froyo won't. Netflix too.

But let's just hope that official working GB will be released soon so our devs can get their hands on it.

Thanks for sharing the information.
[Thunderbolt Android Development] Asmodeus6:
When I went to GB I flashed the radio, hit power, as soon as I got the start screen I pulled the battery, deleted the PMG5IMG file, booted back into Hboot, picked recovery, wiped everything. Flashed a GB rom.

I would imagine you could do the same thing without ever booting the phone the whole way up to go back as long as you have a rom and radio on your SD card.

(I used my card reader and laptop to move **** around)

It's how I'm going back to Froyo here in about 5 minutes... :(
[Thunderbolt Android Development] psicrest:
I've noticed there are several version of the GB radio that was leaked

http://www.multiupload.com/HU471CMQI0 ----

MD5: EE2A824E51CB148A2256F93E30A3B9F9

http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ----

MD5: fda2a314975dd829b4e3611ecc8cfa13

PG05IMG_gingerradio.zip <- from http://xdaforums.com/showthread.php?t=1082001 links already removed. Same MD5 here: http://www.androidpolice.com/2011/05/16/download-leaked-gingerbread-rom-for-the-htc-thunderbolt/ ----

MD5: 52DD83AA40E30186C9FBEFAFD1BAB534

I used the MD5: EE2A824E51CB148A2256F93E30A3B9F9 radio on mine.
[Thunderbolt Android Development] KDKobes:
As long as you do it before you get the reboot of death.(bricked)
[Thunderbolt Android Development] Asmodeus6:
Can anyone explain this ^

How is this not being discussed, but things like roms, kernels, and batteries are?

:confused:
[Thunderbolt Android Development] techrevive:
Just a thought, could this be battery related... I feel like the phone is not really charging when it says it is on gb.... I can't really test since I use multiple batteries and I'm not stuck in bootloop. Can someone who is stuck try a fully charged battery from either a froyo phone or external charger and see if this will let you out of loop?
[Thunderbolt Android Development] micompcs:
You flashed the PG05IMG_downgrade.zip?
[Thunderbolt Android Development] jcase:
There is only one version, just multiple repacks.