yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Dnakaman:
Yes, but there is a difference. As an experienced user, you were able to recover. This issue with the unrecoverable brick...not even developers, let alone experienced users were able to recover from it. I think that is why there was so much concern.

If someone who knows what they are doing messed up and can't fix it...imagine average Joe trying to fight his way out of a wet paperbag.
[Thunderbolt Android Development] RileyGrant:
This is not a radio issue, I've seen this happen on the evo and even the nook countless times now, always on gingerbread, always the same symptoms. The emmc just seemingly fails, completely.
[Thunderbolt Android Development] Mean Bro Greene:
Now that you mention it, this exact problem has befallen my Nook. Same symptoms of the bricked Thunderbolts, and I was running Gingerbread. This might just be a big coincidence, but it's still interesting.
[Thunderbolt Android Development] LTE:
I would like to think so, but who knows for sure, maybe just some people with bad luck, bad batch of TBolt's that could not handle whatever the new radio was doing, like OC'ing where some tbolt's will work at 1.9Ghz and some won't...

What problem with stability? I have had 0 reboots and 0 FC's and been running for days on 2.3.4... I don't see any issues really. At least with LGS1.1 :) Only time I reboot is to backup/install each new rom as it comes out...
[Thunderbolt Android Development] JS0724:
Mainly the slow charging issues. I use my phone heavily at work and phone would be draining faster than it was charging, even on ac power.

Also, but not as important...

Cannot sync Peep contacts without phone force closing when one of them calls.

Various issues with Sense on ROMs with mixed versions of Sense. (2.1/3.0)
[Thunderbolt Android Development] LTE:
No slow charging issues anymore, I believe it was a kernel problem, fixed in 1.1 that I am using...

Dont know about peep, have not seen any other bugs yet... so might try it... PM me if u want the download link.
[Thunderbolt Android Development] amaury48:
Day 4 back on LGS 1.0 - Had 1 reboot, happened on the road exactly at the point where it switched from 4g to 3g area. I know exactly where this point is on a particular road in Tallahassee, leaving the City's 4g coverage area. Maybe coincidence, maybe not. Just thought it was worth mentioning. So far other than that It's going well.

Are all the devs on hold with further updates? With no definitive cause of bricks, may be time to move on ? What ya think? :cool:
[Thunderbolt Android Development] mallen462:
I'm still running strong on ginger I've been on ginger since its first release
[Thunderbolt Android Development] trusteelfan:
I have had the same thing happen to my nook also. I didnt even think about it being similar to whats happening to people's thunderbolts. I had a replacement sent, and the replacement one did the same thing after a week or so. I could get it to boot into recovery with a sdcard, but that was it. Sent that one in for a replacement now too.

So for now im back on Froyo until this gets resolved. Cant go without my primary phone.
[Thunderbolt Android Development] KDKobes:
Just reassures what I have been saying.
[Thunderbolt Android Development] bp328i:
I completely agree with you 100%. Even the best can make mistakes. I myself have stayed up way to late, drank way to many Bud Lights and made some big mistakes before and had to restore a backup, hell I had to sbf a few times on my OG Droid. But I can assure you that's not what happened with my Thunderbolt, I was not even by it when it bricked and there was no one else home at the time.

I have said this before and will say it again, it was running the best it has ever run and it was not even overclocked right before it bricked. I put it on the charger (stock charger and battery) went out and mowed my yard came in to find it looping to the splash screen.
[Thunderbolt Android Development] tcfrombn:
random hardware failure? ..neutrino hit the cpu? xD

i swear that happened to my ps3. went to turn it on one time and it wouldnt boot. had to get a replacement.
[Thunderbolt Android Development] Cubs2008:
If you run cm7 you can still have Netflix. :)
[Thunderbolt Android Development] BennyJr:
Going to cm7 as i type this
[Thunderbolt Android Development] GreginNH:
Which Radio?
[Thunderbolt Android Development] EggoEspada:
Really appreciate the information guys.

Sure gonna miss BAMF 2.0. :(

Sent from my ADR6400L
[Thunderbolt Android Development] biggiephat:
All this is pressure from the vendors.

Having our phones be able to revert back to a locked state.

won't let us have any fun
[Thunderbolt Android Development] mojonation1487:
wow mine just starting doing it. Is this some verizon shenanigans to protect their stuff?
[Thunderbolt Android Development] adrynalyne:
Just.stop.

Your issue that you had last week or so is not.the.same.issue.
[Thunderbolt Android Development] BennyJr:
No just an unfinished radio. This was an ALPHA radio.
[Thunderbolt Android Development] biggiephat:
an unfinished radio cannot revert your hboot back to ON...
[Thunderbolt Android Development] shelooga:
damn. i flashed the 605.7 radio, and then tried to install my rom, not restore a backup bc theres things i altered and want to keep, but now im stuck in the clouds. and since theres the radio file on my sd card (some moron didnt delete it after he flashed it) i cant get into recovery.

guess ill go borrow my friends tb to delete my pgm file and retry.

thanks for putting the fear of god in us jcase

seriously though, thanks for looking out for us
[Thunderbolt Android Development] Richpopski123:
You really think they want hundreds of people coming in saying they have broken phones?
[Thunderbolt Android Development] g00s3y:
just shut up when you have no idea what you are talking about
[Thunderbolt Android Development] You.:
it's just the radio causing the problem, right? Is it safe to be on a froyo radio and go to the GB rom to back up the apps I have?
[Thunderbolt Android Development] Tallica21:
Flashing the file it the OP will give us stock 2.2 with root and S-off? Is this correct
[Thunderbolt Android Development] adrynalyne:
Sure if you want a fancy PDA.
[Thunderbolt Android Development] Pithism:
Same

i've been running Gingerbread since das bamf 2.0 and everything has been working flawlessly and i dont see any signs of bricking. Jcase and others agree with this problem obv, but if there phones aren't bricking and its just us "normal" people phones with the problems then its probably something else and not just with the leak we have.
[Thunderbolt Android Development] g00s3y:
"Hi, VZ, I came in today because I flashed this test leak of Gingerbread that I found online and now my phone just keeps rebooting, help?"

:rolleyes:
[Thunderbolt Android Development] swimminsurfer256:
you won't ;)
[Thunderbolt Android Development] g00s3y:
There is so much fail in your statement I don't even know where to begin...

BTW could you enlighten me on the signs of bricking?
[Thunderbolt Android Development] Bxsteez:
From what i've been reading there aren't going to be any signs of bricking. The only sign you would get would be your phone not booting. I haven't had this problem but really why take the risk? Use Cyanogen and wait for a new radio. Just my opinion though
[Thunderbolt Android Development] onyx_64:
When's the next Gingerbread leak coming, jcase??

lol.. jk.
[Thunderbolt Android Development] tazman19:
With all the talk of bricking and the relatively low percentage that is coming back as bricked makes me wonder...The devs in this site are brilliant at what they do and maybe its as simple as what others have been whispering, hardware failure...I mean, lets face it, I believe they make things, especially appliances and electronics, TO FAIL after a certain amount of time. Not like the old days when you bought a TV, for instance, and had it run for 20 years. Or a fridge, stove, washer & dryer. They hope to capitalize on the people who turned down the extended warranty at checkout. LOL

So, this could just be random hardware failures, which happen with any electronic. XBOX, PS3, phones, etc......

Just my 2 cents.
[Thunderbolt Android Development] mackentosh:
Is this Crap still Bricking
[Thunderbolt Android Development] Shiftyshadee:
So if people think it's just hardware failure, then why isn't CM 7 bricking phones? It's gingerbread, only difference is it's currently using a froyo radio.

My 2¢ :)

Sent from my ThunderBolt
[Thunderbolt Android Development] tazman19:
I dont believe it is ROM or OS dependent. There probably are people who were running CM7 that had hardware failure also. We should take an opinion poll and see where that stands of how many people on CM7 are not still on their first Thunderbolt.
[Thunderbolt Android Development] djkeller3:
I think by Gingerbread, it the Gingerbread radios that are believed to have brought the hardware defect to light. Those who are running CM7 are running Froyo radios, so if this theory holds water, then naturally, CM7 users would not be experiencing GB-related bricks.
[Thunderbolt Android Development] tcfrombn:
I'm not sure why people are so convinced the GB radio is bricking phones.

How many recorded bricks are there?

Were they all 'soon' after flashing the GB radio?

Why has nobody else bricked in the two weeks following this 'incident'?

I really think they aren't related.
[Thunderbolt Android Development] distortedloop:
Because all the bricks we know of had Gingerbread radio in common. No one we've seen reported with a Froyo radio, and CM7 is GB, but Froyo radio, so it's not the ROM itself.

Those in the know seem a bit tight-lipped about it for some reason. Not sure, but it doesn't seem like a lot, %-wise.

Yes, all the bricks I've read of were reported within a week of the GB radio. It's only been out 2 or so to begin with, right?

Because most switched back to a Froyo radio.

Based on your extensive analysis of the problem and actual bricked phones...?

If you don't think it's GB or the GB radio, flash the GB radio and a GB ROM and see what happens on your phone. Seems like maybe nothing will happen, based on numerous reports on the DAS BAMF 2 thread.

Part of the frustration/confusion for many is the lack of solid facts. I'm tempted to go back to DAS BAMF 2 myself at this point.
[Thunderbolt Android Development] tazman19:
Well done sir...thanks for answering his questions for us.
[Thunderbolt Android Development] kdb424:
Still on gingerbread without an issue. Hoping I can help somehow, but happy I'm not bricking. I'll keep posting in as I have.
[Thunderbolt Android Development] KDKobes:
This is where the confusion comes in.

CM7 looks like gingerbread but on the inside its still using the old Android system which is why they use the froyo radios.

Gingerbread is based on something different which is why it requires the different radio. I hope this makes sense.

This is why I said and still stand by the memory issues relating to the bricks. For instance on gingerbread there is issues with battery charging...now if you take your phone with it plugged in and restart it...it charges fine then. Why?...Its releasing memory...(and I mean this more technically than apps being just "opened".

Now as far as bricks go...there will be more mainly because I see people doing stuff that should not be done with this ROM yet. I posted my opinions if you want more info you can pm me.
[Thunderbolt Android Development] fallingd0wn:
That is completely false. CM7 IS gingerbread. It is built directly from the latest AOSP 2.3 source code. Yes, there are some hacks in place until the HTC drops the GB source and the RIL had to be built from scratch but to say that it is based on something different is totally incorrect. Cyanogen is closer to pure Gingerbread than any Sense based ROM will ever be. It is using froyo based radios because those are the current officially released radios and considered stable. That may change in the future.
[Thunderbolt Android Development] KDKobes:
I try to put it into the simplest form I could think of....figures I would have someone who just doesn't quite understand. Originally it was quite pure, but internally has been sliced up into pieces that fit if that helps you understand..

HERE'S SOMETHING FOR YOU TO READ VERY CAREFULLY AND IT WILL SHAKE THIS WHOLE THREAD..READ THIS
[Thunderbolt Android Development] fallingd0wn:
I already understand quite well. I'm not trying to explain the bricking problem. I just didn't want anyone to be confused as to what exactly Cyanogen is or why it is currently using different radios. The main reason being that the leaked ones were untested and weren't known to be safe. CM is as pure as can be expected and adds a lot of nice features. Sense is a completely different animal. I would challenge you to find anyone that would agree on a Sense based ROM somehow being more pure than CM. The link you posted covers a problem some EVO owners had. It's been mentioned before. Maybe there is a similar issue with some Bolts, maybe not.
[Thunderbolt Android Development] KDKobes:
It is a pure look and feel I never denied that..but what I am saying is there's other components that are not from this gingerbread release.

And YES these issues are quite connected...."CM" community does a great job working on their roms and address fixing them not tossing them to the side awaiting a new release.
[Thunderbolt Android Development] fallingd0wn:
I agree. I thought that was fairly obvious though. HTC does a ton of modifications to the code.
[Thunderbolt Android Development] KDKobes:
Not for some though....HTC went overboard on this one too!!
[Thunderbolt Android Development] thejondude:
its not a ginger bread radio its a ginger bread compatible radio.... google has nothing to go with radios..... o and isnt charging based in the kernel?.... which also has nothing to do with google....
[Thunderbolt Android Development] KDKobes:
Don't know why everybody's gotta argue when I try to lay it out in the simplest form for everybody to understand just because it doesn't say "recognized developer" in my stats don't mean $hit I am no fool. Yes it is compatible and it requires gingerbread to run which is why it only works with gingerbread. Yes it does have to do with the kernel and other scripts in the ROM itself which are not being released properly....$hit. Nobody really said anything about Google being a problem wtf are we talking about!?!?!?:confused::rolleyes:
[Thunderbolt Android Development] bobtheelf:
Accuracy > simplicity
[Thunderbolt Android Development] dalrym05:
Well I think the bricked phones are user error :-) and kdkobes your phone is overclocked to 1.2mhz? That must be....................

Fast
[Thunderbolt Android Development] KDKobes:
Lol no I had something totally different posted and accidentally erased it. Was trying to add to it and decided to come back to it after I was done. Testing the *EDIT* that was leaked and pulled multiple times so I was LOST in the confusion.
[Thunderbolt Android Development] dalrym05:
Can knowone take a joke Jeeez. You know I'm just messing around. I believe the bricking just don't care if mine bricks like Netflix to much to go back to Froyo. My job is boring without it.
[Thunderbolt Android Development] KDKobes:
...Seems my fingers are moving faster across the keyboard.:p
[Thunderbolt Android Development] Dstu03:
Is there a thread for the new radio
[Thunderbolt Android Development] KDKobes:
There was I don't know if there still is it was all canned and links were dropped in the frenzy....seems some got it just before it was squashed..nobody was sure if it was the real deal and hasn't been tested or confirmed.
[Thunderbolt Android Development] Chainfire:
http://xdaforums.com/showthread.php?t=1113597

Read it.
[Thunderbolt Android Development] distortedloop:
We're straying off-topic a bit, but I'll bite anyways.

I've got the latest CM7 on my Nexus S, Galaxy S i9000, Nexus 1, and my rooted Nook Color. It's definitely not stable on my Nexus S...lots of reboots (no boot loops though) on it. i9000 a few. I don't use the N1 or NC often enough to have a feel for it, but they're not rebooting randomly on their own while just sitting idle like the Nexus S does.

I wonder if we'll ever know what caused those first set of bricks; looking less likely by the day as no new bricks come forward (that we're hearing about anyways). There was a guy in the andirc chat room the other day who sounded like a real brick, but in the end, he wasn't.
[Thunderbolt Android Development] tekhna:
Meaning what, exactly? That the radio we've been mucking about with wasn't leaked, but came from a hacked HTC server?
[Thunderbolt Android Development] Dstu03:
No meaning that someone hacked stole a radio and posted it on here and xda doesnt want a lawsuit
[Thunderbolt Android Development] patalo:
Oh wow that's what that is? So, is this a stable radio? What is happening now?
[Thunderbolt Android Development] KDKobes:
I wouldn't expect anybody to even discuss this now..its all hush hush.

I am sure it will pop up again though as a few people have it.....DO NOT ASK FOR IT EITHER.
[Thunderbolt Android Development] joshw0000:
There was a thread about the new radio, not to download, just talking about why it can't be disclosed. Even that has been pulled. That thing must be hot!
[Thunderbolt Android Development] Dstu03:
It was stolen.....when you rob a bank its usually not smart to talk about it but I'm sure HTC knows where to find there stolen radio
[Thunderbolt Android Development] WorldOfJohnboy:
That or the Devs want access to DL the file first so they can work on it and test it... :D
[Thunderbolt Android Development] satseaker:
i will post it again,my first bolt died from the boot brick or what ever you wanna call it and it never had gingerbread on it just rooted stock kernel and debloated rom.
[Thunderbolt Android Development] distortedloop:
"post it again"...? I don't recall you posting it here before, but I'm old with a fading memory, LOL. I searched your post history and see one post about getting a replacement for your TB in another thread, but no description of the problem.

Could you be more specific, please? I see you were on debloated ROM, rooted, etc, but more importantly what were your symptoms? The one described here is the phone reboots with a few seconds, even in recovery...which is what makes this so scary. Is that what was happening to you?
[Thunderbolt Android Development] corenojoe:
New radio gonna fix the reboot of death problems? I knows its pretty soon to ask, but I'm wondering if we know that this new one is made specifically to fix that issue or what?
[Thunderbolt Android Development] Dstu03:
Sounds like it but no one will say for sure
[Thunderbolt Android Development] davidkim99b:
new radio rock, lot of improvements... I hope it won't have any bricking issue or else I have to go back to froyo once again =[
[Thunderbolt Android Development] Joeviocoe:
http://xdaforums.com/showthread.php?t=1115714

It's out! We shall call it MR2
[Thunderbolt Android Development] KDKobes:
Been out for a few days now...
[Thunderbolt Android Development] satseaker:
It started acting weird,wouldn't turn off,power on off more than usually so I started to return it to stock,flashed the jcase way as soon as it started up after I replaced the hboot it just started to loop

sent from a screamin' bamfed out tbolt
[Thunderbolt Android Development] joshw0000:
Were you on the old GB radio or MR2? Which files do you flash? Did you verify MD5's? Is your phone bricked or did you recover it?

Please give us more info.
[Thunderbolt Android Development] ridobe:
Well, I don't know. I downloaded Th3orys' latest this morning and did all of my backups to TiBu and sms, etc. as I wanted to do a full wipe to install. I have been running his roms for a while now. ***I in no way blame him or his rom. I only listed it for information purposes***.

I am on mr2. This morning after downloading the file I wiped data/cache/dalvic and batt statts. I chose zip and it aborted immediately. It had (bad) at the end. So I tried to flash an older rev of the rom, one that I know is good and have used before and I got the same (bad) abort. Ok, little bit of panic - so I went back to restore a proven backup and it starts to restore but only restores for about 30 seconds and then says complete/reboot. Uh oh. Stuck on splash screen.

I can't imagine that it is the sd card as I can maneuver around to my downloads, etc. I am going to need help on this one.
[Thunderbolt Android Development] KDKobes:
Try to format system, data, cache then try install. Could very well be the sdcard..if all else fails backup the card and reformat it then do a "fresh" Rom install no backup.
[Thunderbolt Android Development] ridobe:
Thank you for your help. I'm trying the first part now. Can't do the second part until I get home.
[Thunderbolt Android Development] ridobe:
It was indeed a corrupt sd card. I have a new one and I'm back up and running. Thanks again.
[Thunderbolt Android Development] KDKobes:
No problem...glad ur up and running again and not bricked.
[Thunderbolt Android Development] rhcp011235:
Im running GB / All the radios before it was posted here on XDA. Some minor issues. nothing super crazy.

I called VZW they sent me a refub phone. I just wish we could get down to what the REAL cause is. Instead of calling it radio issues and blah blah.

I dont think HTC nor VZW knows. Or they are keeping it secret.
[Thunderbolt Android Development] ch3ss:
fellas.... i am just rooted and verizon pushed an update and now it just loops it goes into my phone and hits turns off and it goets to clockwork recorvery
[Thunderbolt Android Development] nbledsoe:
This sentence makes zero sense. We need more info if you don't mind.

Mah BAMF Thunderbolt
[Thunderbolt Android Development] Philosophre:
I am thinking you aren't truly rooted. If you are, verizon shouldn't be able to push any updates on you. If you can clarify the entire process of what happen, that way we can better help you.
[Thunderbolt Android Development] bobtheelf:
If you're just rooted but still running a stock ROM sometimes you can get OTA updates. Most often they just fail without affecting anything. He just needs to download a ROM of his choice and flash it from recovery.
[Thunderbolt Android Development] revs9k01:
After this leak, has the issue been squashed?

Sorry if it has been mentioned else where. I am a new TB owner and just flashed BAMF Sense 3.0 with the MR2 Radio and love the performance thus far.
[Thunderbolt Android Development] planepilot:
I think vzw or htc know something is up. Why else would they send out another offer to extend the mfg warranty? I never got that offer with my original droid! After seeing my coworkers virgin TB bootloop was proof enough for me to buy a little extra bit of insurance.
[Thunderbolt Android Development] revs9k01:
I guess I should consider keeping that Best Buy Black Tie Protection on mine huh.....
[Thunderbolt Android Development] kpa2727:
I work for best buy , it's not a bad deal covers cracked screen,most phones are rapid exchange now aka refurbs. I went with verizon on my Bolt io had the best buy warrenty on my Incredible. Depending on the store most go Rapid Exchange and others go out to be repaired for up to a month. So pick your poison.

Btw verizon charges a 50 dollar deductable for a broken screen.
[Thunderbolt Android Development] jaysckap:
Adrynalyn got screwed with black tie
[Thunderbolt Android Development] bobtheelf:
How so? He was given the choice of a refurb immediately or a new device if they tried to repair it and couldn't. That's standard.

*edit*

Not only that, but they're taking care of him for something that technically is not covered since he rooted the phone and modified the software.
[Thunderbolt Android Development] papped:
No, some of the bricks were reported on mr2. Also likely that it has nothing to do with any of the leaks at all...
[Thunderbolt Android Development] taylorhome11:
I dunno what the issue is. I have been running the GB leak and radio 2.5 for 5 days now. Flashed over it multiple times and other than the bugs in the leak I have no issues.