yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] migueltherocker:
So.... Only the MR1 radios are safe? I really hate to sound like a noob, but I want to make absolutely sure. I'm not sure if it's ALL the GB radios (MR2 and MR2.5) that may cause bricking, or only the one that was removed (and since then prohibited from once again being posted.

So, which radios are safe?
[Thunderbolt Android Development] TheOnlyOne93:
No radio or rom is safe, you can brick on any of them at any time.. It's like playing the lottery.

Edit: Actually more like playing Russian Roulette
[Thunderbolt Android Development] migueltherocker:
Sounds exciting! Thanks, I just wasn't sure if the whole "gingerbread radios brick phones" theory had been debunked or not.
[Thunderbolt Android Development] USSENTERNCC1701E:
Yeah, people have bricked on stock unrooted too, it almost just seems as though whatever faulty hardware is a time bomb
[Thunderbolt Android Development] distortedloop:
Do these radio-scare bricking threads need to stay stickied? When was the last verified actual brick? Where any unrecoverable bricks actually confirmed as being caused by either of the GB radios, and only the GB radios? "Feels" like a non-issue now.
[Thunderbolt Android Development] TheOnlyOne93:
We just had something brick last night running gb. Also there not gb radios, there froyo/gb radios. they will work on both as long as it's the newer MR2 based froyo
[Thunderbolt Android Development] distortedloop:
What particular combo of rom and radio was being ran? Was the chip type ascertained.
[Thunderbolt Android Development] hyghpocalypse:
Actually, I too bricked last night. Think I had the 2.5 radio installed (when first released into the wild) and just updated to DBv3Rc4. In fact was switching/downloading to use a different font when I'd/phone crapped out.

While for me I was able to restore (long process but it is possible), I cannot speak for the rest. So head this, bricking, legit or any other means, can occur at any moment, any time, and lastly any device. So take the plunge and flash your phone.

h2
[Thunderbolt Android Development] scotty1223:
sounds like you did not suffer from the same fate as the other bricks,wich are thot to be hardware failure.
[Thunderbolt Android Development] chadstone30:
can we unsticky this thread? it's dead.
[Thunderbolt Android Development] SWhetsel:
I 2nd this. Kinda sick of seeing it at the top of the Forum everyday when it doesn't seem to be much of an issue anymore.
[Thunderbolt Android Development] bmx5656:
I havent been here in a few weeks, so GB roms are all working now? No bricking? all features are working with gb now?
[Thunderbolt Android Development] distortedloop:
If you were able to recover the phone, you did not brick it. Bricking, at least as used in this thread, means it is not recoverable by any means known to date.

Sent from Thunderbolt
[Thunderbolt Android Development] bp328i:
NO, you did not brick, but nice story...
[Thunderbolt Android Development] SWhetsel:
I cant speak for everyone, but I have a everything working on my ROM. 4G, Camera works, wifi works, everything working. I dont see many people on here that are truly bricked.
[Thunderbolt Android Development] toebee76:
I bricked on Friday, constant boot loop even in recovery. I was running CM7 with the MR1 radio at the time. So looks pretty random to me.
[Thunderbolt Android Development] fixxxer2008:
if people are still bricking then it's hardware related and i think verizon should be issuing a recall of sorts. as much as i love the tbolt there seems to be alot of issues with the phone.
[Thunderbolt Android Development] distortedloop:
Massive recall's never going to happen. It would cost Verizon too much money. They'll just continue to replace bricks for those that it happens to under either warranty or insurance. In the "real world" (the millions who don't read xda), actually even in the xda world, I think the bricking is a relatively rare event.
[Thunderbolt Android Development] oc3rulz:
rosenbaa29 - How on earth does your post qualify as relative to Gingerbread related Bricking? SRSLY, that is spam
[Thunderbolt Android Development] arl16:
SOOO... I think I bricked it.

Just went to BAMF 3.0 RC5 w/ the MR2 Radio

Everything was actually working great. Then I decided I wanted to change the right button for Rosie. I installed FeatureAdd_Sense30_BAMFRC4_RB_Map.zip, not thinking about the fact that it was for RC4, and when it rebooted, it just gets to the "das BAMF the Badddest" splashscreen and hangs.

Tried going to recovery, but it immediately goes to HBoot and tries to flash the radio. Can't scroll down to Recovery.

Pulled the battery, and even the sd card. Same results.

Any tips? Thanks!

(PS I've been searching and reading hundreds of posts - can't find what to do. Thanks again in advance for any tips...)

Oh, I should also mention, this is my first move to GB. Had been on BAMF 1.8 remix. First GB Radio. Wiped everything.
[Thunderbolt Android Development] scotty1223:
i personally have a hard time beleiving your phone is finding and trying to install a PG05IMG file on an sd card that isnt there :eek: you should be able to select recovery from hboot with no sd card,tho that wont do you any good,as youll have no backups to restore,and no roms to flash with no SD.

what you need to to is remove the sd card,put it in a card reader,put it i your puter,and remove the PG05IMG file.

now you should be able to get to recovery and restore a backup or reflash your rom.

at any rate,you are far from the bricks being described in this thread.
[Thunderbolt Android Development] arl16:
Maybe that wasn't QUITE accurate - let me rephrase - it found the PG05IMG file, and said, Want to install? (And yeah, without an SD card, I couldn't recover anything). In any case, my only choices were Yes, or Reboot. It wouldn't let me scroll down to recovery.

BUT, your solution was perfect! Thank you, thank you, thank you! I don't know why I didn't think of that, but I guess that's what brainstorming and asking questions on these forums is for.

So thank you, I really didn't want to sit and learn adb tonight (any more than I minimally know it now), and I know my wife didn't want me to. Recovering/restoring now...
[Thunderbolt Android Development] sidsixseven:
I can confirm bricks are still happening because I just bricked. However, I also absolutely agree that I believe it's hardware related.

Here is how I'm defining brick -- I can get into HBOOT and that's it. I have removed the PG05IMG file, attempted to get into recovery, attempted Fast Boot, flashed several RUUs. Including the unsigned MR1 stock RUU and when I ran out of all other options, flashed the stock RUU and S-ON bootloader to return to stock.

In all instances, same thing. As soon as the phone cycles past the white splash screen, I see a glimpse of the second splash screen (or recovery if that's what I am attempting) and then the phone reboots. Most of the time, I don't even get the glimpse.

I'm fairly confident that because I was basically able to flash this phone back to stock through HBOOT that the problem has to be hardware related.

Did I contribute to the problem? No clue. Never OC'd above 1.4ghz and usually set min CPU speed at 386mhz. According to the serial number, it appears my phone was manufactured in February like many of the other phones that bricked with this problem. So IMO, it's definitely hardware related.

For reference, I was using the latest OTA radio released on 7/8. In terms of timing, I was just booting the phone into Recovery to wipe dalvik cache when the problem began.

I booted into Recovery from ROM Manager, which I usually don't do, but I don't think that caused it. I did recently flash a new ROM/kernel, but since I don't believe either of those caused the problem, I'm not going to share that information and "scare" people. It's also why I'm posting this information here and not in the kernel or ROM thread. This happened a couple of days ago and I have been monitoring those threads for other brick reports -- no one has mentioned anything.

Sometimes a phone will have a defect and I think that's what happened. A hardware defect. No mysterious ROM, Radio or Kernel glitch. In terms of causality, the only thing that

may

have contributed is either something to do with some unexpected glitch in CWR or ROM Manager or perhaps undervolting or overclocking damaged the CPU. No way to tell really but I choose to believe it was hardware defect.
[Thunderbolt Android Development] scotty1223:
1)if you were able to recover it,you didnt brick as being described in this thread. these bricks are unrecoverable.

2)ive never know flashing software to fix hardware prollems :eek:

you had some sort of software issue that a stock,signed image was able to fix.
[Thunderbolt Android Development] bp328i:
In the two paragraphs above the sentence you quoted he said:

This is exactly what happend to my Thunderbolt. I could boot into hboot and flash an RUU but then the phone never boot up and would only make it to the splash screen. Every time I booted into recovery it would reboot as well, just like sidsixseven posted his did.

He sir, is a true brick just as I was.
[Thunderbolt Android Development] scotty1223:
no sir,he was not,if he was able to recover his phone. from the very first post(i know its a long time ago,and many pages back :eek: ):

again,his situation is not the same as the bricks being described in this thread.

if you recovered you phone,you were not a brick,either. if you were unable to recover,YOU were a brick as described here,but he is not.
[Thunderbolt Android Development] bp328i:
Where in his post does it say he recovered his phone? It says he was able to flash the stock RUU and then right after that he said;

"In all instances, same thing. As soon as the phone cycles past the white splash screen, I see a glimpse of the second splash screen (or recovery if that's what I am attempting) and then the phone reboots. Most of the time, I don't even get the glimpse."

Boot loops don't happen in recovery because of a bad flash...if they do we're all screwed!!! Again, he sir, is a true brick.

And I do know the difference between a boot loop and a brick as I was one of the first true bricks. My Thunderbolt bricked before any warning was posted to get off Gingerbread.
[Thunderbolt Android Development] scotty1223:
this statement sure makes it sound like it was recovered:

again,IF his phone was recovered,he was not a brick. if he just doesnt know how to communicate to people so that they understand his situation and his phone was not recovered,then fine, it was a brick.

if your phone was not recovered,then it was a real brick. congratulations.

i dont doubt he had a prollem.but in order to be relevant to this thread,and the same type of failure,the phone cannot be recovered. flashing the "stock ruu"(not sure what that means,there are several) will not magically fix a failed mmc(or other failed hardware).
[Thunderbolt Android Development] 66dude:
Hello! His phone was NOT recovered! If it was recovered, he would already be able to boot all the way to Sense or AOSP. But in his case, he could not do so. His situation sounds like a true bootloop that CANNOT be recovered!
[Thunderbolt Android Development] bp328i:
Wow...Really?

His communication was fine maybe you should read his post again, the part you quoted he's talking about getting the phone back to stock through HBOOT. Stock = S-ON he never said it was recovered or that it would boot up. To the contrary he said;

Are you just not reading the above part of his post?

And yet again, since when does a bad flash cause recovery to bootloop??? It doesn't!!!

As far as flashing the stock RUU, if your not sure what it means like you said you should read this post. http://xdaforums.com/showthread.php?t=1009423 It might just save your Thunderbolt one day.

I'm no noob when it comes to Android, I have been rooting, modding and theming since the G1 days. I have recovered from my fair share of soft bricks "bootloops" when testing new things out. And guess what the only time I have seen a phone reboot when it was in recovery was my Thunderbolt when it was a true brick. Yes my Thunderbolt is working again, because I got a new one!

When you go through the exact same thing as he has described then we will talk more, until then I'm done.
[Thunderbolt Android Development] bp328i:
Thank you...
[Thunderbolt Android Development] scotty1223:
whatever guys :rolleyes:

"able to flash this phone back to stock through HBOOT" sounds to me like a bootable phone on a stock rom.

every firmware version has a signed ruu. and you could call any of them a "stock RUU". we still dont know for sure what one he flashed.

you guys can read into it,and make whatever assumptions you want,ill keep saying this:

IF he recovered his phone,it wasnt a brick.

if he dint recovery it,then it was a brick and you guys win! congratulations,youre smart here on xda :eek: i guess we wont know for sure unless he posts back.
[Thunderbolt Android Development] bp328i:
Please just answer this;

And yet again, since when does a bad flash cause recovery to bootloop???
[Thunderbolt Android Development] scotty1223:
wtf does it matter? :confused: i never said,nor insinuated that a bad flash caused a recovery bootloop or his prollem.

i said he had some sort of software issue that was fixed with a software flash,assuming that whatever signed RUU he used,fixed his phone back to a workable unit.

again,there is not software that you can flash that will fix a failed mmc or other hardware components.
[Thunderbolt Android Development] bp328i:
It matters because he did say the phone would bootloop even in recovery. If your phone bootloops in recovery your screwed, it's a hardware fail not software.

Is it really that hard to understand?
[Thunderbolt Android Development] scotty1223:
no its not. im also not sure whats hard to understand about this:

IF he recovered his phone it wasnt a brick.

notice the "if". i keep saying it because while it insinuates to me his phone was recovered i do NOT know this for sure(unlike you who seem to be 100% certain of the facts youve derived from his post)

there have been a couple of other instances where people had what they claim to be indenticle situations(recovery loop and all) and were able to recover.

if he was able to recover,recovery bootloop or not, he was not bricked. at this point im done arguing with you. since you will likely keep this up until i stop,so you can have the last words,this will be the last post from me about it. so make your next post really clever :rolleyes:
[Thunderbolt Android Development] 66dude:
You apparently have the reading comprehension of a fourth grader. Yes, he was able to flash a ROM. Yes, he was able to go into CWR. But is his phone "recovered"?

NO!

Now, you may have heard of some similar or identical situations of this happening, but every phone is different. Not all would be able to "recover" given identical situations.

Now, was that so effin' hard to understand?

​
[Thunderbolt Android Development] bp328i:
Here is clever for you. Your wrong, plain and simple, wrong but you can't admit it. Did you re-read his post and realize that you read it wrong in the first place? If I'm wrong on something I just admit it and move on.

Let me spell it out for you, If your phone keeps bootlooping while in recovery like he stated his does YOU ARE NOT GETTING IT BACK TO A WORKABLE STATE IT IS A HARDWARE FAIL.

You keep assuming he got it back to a workable state. Your assumption is dead wrong, how do I know? Because I went through exactly what he posted, so I'm not only 100% certain I'm 110% certain.

Show me one post that someone on here has said they bootlooped in recovery and were able to recover their phone. You can't because it's not here, yes there have been many people that said they bricked their phone and they were nothing more than a bootloop but none of them were bootlooping in recovery.

Trust me I'm more than happy to tell someone that their phone did not "brick" if it was just a bad software flash.

You really should read more before you jump on here and tell people that their issue was not a true brick.
[Thunderbolt Android Development] bp328i:
Again, Thank you, some people just don't get it!
[Thunderbolt Android Development] scotty1223:
i was not wrong about anything. if his phone was recovered,it was not a brick.

if i read it wrong and it was not recovered it was a brick. ive been sayin this all along.

you are the one that wants to keep arguing about it.
[Thunderbolt Android Development] scotty1223:
reading comprehension has nothin to do with it. i inferred from his statements he recovered his phone. you infered he did not. he never specefically says one or the other.

but good job getting in on the argument. :rolleyes:
[Thunderbolt Android Development] bp328i:
Really, he never specifically says? This is where the reading comprehension comes into play.

His third sentence he states his problem, the rest is what he tried to do to fix the problem.

There is no getting through to you so you believe what you want, and the rest of us will know what really happend.

Good Day to you sir.
[Thunderbolt Android Development] sidsixseven:
Wow. Sorry for the drama. It's a brick. I never expected a bunch of arguing about it. I was just posting what happened to confirm that they still occur BUT THAT I THOUGHT IT WAS UNRELATED TO RADIO, KERNEL OR ROM. Just my $0.02 and I wasn't tossing blame at the feet of some developer or Radio release.

In any event, the phone was never recovered. Nor could I ever get into recovery. HBOOT, yes. Recovery, no. Any attempt to get into recovery was immediately met with a reboot. Any attempt to boot the phone normally was met with a reboot. Selecting Fastboot through HBOOT was also met with a reboot.

The only thing that I could do was flash RUUs through HBOOT. Thus, using HBOOT, I flashed several unsigned RUUs that should have returned me to stock root with no success. And finally, I flashed the RUUs and S-ON bootloader that should have taken the phone back to an out-of-the-box image.

Even under that scenario (and under every scenario) the only thing that I could do is get into HBOOT. So yes -- this is the true brick described in this thread.
[Thunderbolt Android Development] sidsixseven:
I thought I was pretty clear. Perhaps he thinks HBOOT and Recovery are interchangeable or something? At no point did I ever say I successfully got into Recovery or that returning to the stock image fixed the problem.
[Thunderbolt Android Development] scotty1223:
i assure you im quite familiar with hboot and recovery. your satement that you were able flash back to stock sure sounded to me like you flashed it and had a workihng phone.

apparently this was incorrect,my humblest apologies :rolleyes:

at any rate,im not sure why these 2 needed to drag it out in this manner.

i said "if you recovered your phone it wasnt bricked" wich is a true statement. all that was needed was for the peanut gallery to remain quiet until you showed back up and said "i never recovered it".
[Thunderbolt Android Development] bp328i:
Your first post was crystal clear for anyone that actually read it and understands how the phone works.

Sorry to hear about your Thunderbolt, I had the same thing happen to mine and its not a good feeling at all when you go into recovery and it reboots.
[Thunderbolt Android Development] 6stringandy:
Can we give that a rest already, I don't wanna read a bunch of pages about senseless arguing, I'm on this thread to find out if there's been a fix or something from one of these xda gurus that's gonna keep us from bricking in gb. Let's keep the nerd rage to a minimum so all us other noobs and not so noobs can get some valuable info and then get on with our lives.
[Thunderbolt Android Development] 6stringandy:
While we're on the subject of gb bricking bolts, is there a gb Rom and radio combo that has been confirmed to brick, or not brick for that matter? I just went through the pain of rooting this phone and never got this excited about rooting my last Droid (the incredible) and now I'm terrified to flash anything because I've never pricked and don't wanna start now.

To put all of that into a shorter sentence, is there a confirmed gb Rom and radio combo that I can flash to and not brick?
[Thunderbolt Android Development] scotty1223:
the current thots are that a certain early build lot or lots have faulty or off brand parts. someone on android forums bricked on cm7 and the 402 radio,and there is a least 1 report of a stock brick,so it apparetnly doesnt have anything to do with what rom or radio youre on.

feel free to run whatever you wish. while its possible that certain roms/radios and/or overclocking may speed up the process,if you have a phone from one of the lots thats going to brick,its going to brick... it doesnt matter what rom and radio youre on.

the 627 radio is part of the latest maintenance release,so if any of the so-called gingerbread radios are safe,it would theoretically be that one ;)

i personally spend most of my time on cm7 with occasion visits to the other AOSP GB roms,and an occasional leak rom. i ran the senseless th3ory over the weekend,wich ran pretty good. i use the 627 radio.

last and not least my apologies for letting the senseless argument go on so long. i should never have even wasted my time trying to explain myself to the hardcore xda know it alls ;)
[Thunderbolt Android Development] 6stringandy:
I've had this bolt not even a week, think I may be on the clear then?
[Thunderbolt Android Development] scotty1223:
i would certainly think so. seems all the early build phones would have been given out by now.

look under your battery for the serial number,or open a command window and type "adb devices". you can decipher your build date on the serial number/info collection thread.

EDIT: this thread:

http://xdaforums.com/showthread.php?t=1130407
[Thunderbolt Android Development] NeoS:
I had a request to unstick this thread, because the info is old and not entirely correct anymore.
[Thunderbolt Android Development] bolt_of_thunder:
Well my bolt just bricked randomly today. And the weird part is I am running a Froyo based rom and haven't had any problems until now. I'm on BAMF 1.8.6 Remix running the MR2 radio. I've tried everything short of flashing a RUU but it looks like that doesn't even work. Am I screwed?
[Thunderbolt Android Development] scotty1223:
if your phone is endlessly bootlooping in recovery and in the OS,then unfortunately,yes.

go to this thread and try and get the output: http://xdaforums.com/showthread.php?t=1098363

id also go here,if you havent allready and give him the serial number: http://xdaforums.com/showthread.php?t=1130407

then go to andirc chat and see if they still are trying to get info from the bricks.if not,then you can flash an ruu,wich wont fix it,but will let you return it to verizon.
[Thunderbolt Android Development] solarpolitiks:
When did you buy your Thunderbolt? This kind of stuff just scares me.

Would warranty cover this if I told them my phone just started doing this?
[Thunderbolt Android Development] networkmagician419:
My sisters phone is not rooted but doing this exactly. Can anyone confirm this is affecting stock phones?
[Thunderbolt Android Development] tu3218:
My TB won't boot into hboot. I hold down power button and volume down and does nothing, if I let go it just boots up. Any suggestions?
[Thunderbolt Android Development] thetwiztidfreak:
Think I will stick with GB been running radio since day one of leak with no problems. Thanks for the warnging though guys.
[Thunderbolt Android Development] capflya:
Keep holding it down... You're probably not holding it down long enough. Keep holding it until hboot comes up.

Sent from my GingerBamf'd Remix Thunderbolt - going back to froyo :/
[Thunderbolt Android Development] dvation191:
Should be interesting to see if reports of bricks continue. So far it appears to be a very small percentage of people.
[Thunderbolt Android Development] mojonation1487:
agreed. I restarted straight to bootloader from the menu and it doesn't recognize any radio I have on my sd card
[Thunderbolt Android Development] houseboatwayne:
I keep trying to revert back but I find myself growling at my hand and starts shaking.