yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] oscar925:
:( ya i like everything about GB but cant afford a new phone in this ****ty economy lol
[Thunderbolt Android Development] jcase:
Read the theories in my OP, this one was debunked.
[Thunderbolt Android Development] joshnichols189:
This has to be different.. What we're talking about is endless rebooting.. even in recovery, and even at the splash screen..
[Thunderbolt Android Development] kazuma5401:
I wonder if there's any way to determine exactly which radio the crashed tb's were running. I understand they all had the leaked gingerbread radio but did they download from a certain source?

HTC thunderbolt

Das bamf 1.6.3
[Thunderbolt Android Development] micompcs:
I know what we're talking about. The post I quoted was fairly vague, but I had to question.
[Thunderbolt Android Development] dragonsportbikes:
Ok gang, now that ive read all 1,000,000,000,000 posts on this issue :) I am gonna just provide my two cents:

First off, there are 4 developers I swear by and trust (Adrynalyne, Butch, Jcase and Chingy). of course I mean no offense to others out there, these are just the ones I have always stuck with. So in my opinion, I would take there advice. Idont belive that Chingy has commented on this issue yet but the others have and thier recomendation is to go back to Froyo.

So opinions are gonna vary. I personally flashed back to Froyo about an hour ago. Do I miss GB? Being quite honest GB is great, but we all know (whether you admit it or not) that 30 days ago, we swore by Roms like Bamf Remix 1.6.3 and kernels like 4.4.7. So some are making it seem like its an earth shattering event to have to do this. I loved GB and my preference would be to get back to GB as soon as possible, however our fellow developers work around the clock to make cool sw for our phones and im sure they are trying to cook up a fix or work around for this issue as I sit and type this post. I flashed back to the 605.7 radio and restore from a previous Remix 1.6.3 backup. My phone is still running AWESOME and now that I have played with it for about an hour, I have to say, Froyo with the right Rom and Kernel is just as good as GB if not better. Yes, there are some cool bells and whistles on GB, but nothing that would make me take the risk of bricking my phone. I only say this because I have flashed this thing about 150 to 200 times testing out new roms and mods and never once has it failed me. I have seen many posts that state that the reulst will vary from on phone to another, so obviously, I have a good device in my hand that i dont want to break and then have to get a replacement phone that may not work as well. Call me supersticious, but I like my Tbolt, and I mean "my tbolt" as in this particular one. So to me, the risk is just not worth it.

The reality is that this device is just a couple of months old and definately one of the best android devices on the market if not the best, so chances are that: A. Our great developers will find out what is causing this and develope a fix. or B. there will be an official GB release via OTA or otherwise that developers will build from and things will be 100% fine. Until then, is Froyo that bad... HELLLLL NO!! My Tbolt is still running AWESOME!!!!!

So each is entitled to your own opinion and if you have the means to buy a new phone or file an Ins claim, then make your choice and stay GB. I mean no disrespect to anyone at all, just stating my thoughts. Personally, being a very experienced user, flasher, helper, contributor, researcher and supporter of our XDA community, if your asking for my advice, go back to Froyo, (Bamf Remix 1.6.3with the 4.4.7 kernel preferably) and you should not be dissapointed. I am sure our community will figure this out very soon and we will be back to GB goodness in no time.

You choice folks...

As always, Thanks to all and especially my developers of choice. You guys are the F$#%ing best!!!
[Thunderbolt Android Development] ska.t73:
Yea that was a bit out of line an I'm sorry about that. I have no beef with you. I was just trying to stop that guy from spreading some babble about it not being the radio. There is already enough speculation out there.

I do agree with you that this isn't something that will effect most people. I'm going to play it safe but that doesn't mean everyone else has to, they just need to be aware that it can happen on any GB rom.

Again sorry for the name calling, hopefully I will be back on a GB rom soon.
[Thunderbolt Android Development] joshnichols189:
I know, I wasn't quoting you because you were wrong I was quoting you because you were the last post in the series of posts about a certain post..

:)
[Thunderbolt Android Development] psicrest:
But how they repacked it could affect the integrity of the file.
[Thunderbolt Android Development] DroidTh3ory:
Thanks, I appreciate that. And I could have been a little more tackful in my response. :)

It is just getting VERY old, as long as people know the risk (as is with ALL modding processes) in staying or jumping to GB Sense then........ Good.

It doesn't need to be spread into all the ROM threads. Vote for Anti-polution. LOL
[Thunderbolt Android Development] joshnichols189:
I agree.., I just guess that it's only happening because there is currently no fix.. unlike other "bricks" that happen on the droid 1, inc, etc there is usually a surefire way to revert the changes that caused it you know?
[Thunderbolt Android Development] Ghost401:
Sorry Noob Question, How do you "check the md5sum" and what does it mean?
[Thunderbolt Android Development] ska.t73:
Agreed :)
[Thunderbolt Android Development] dragonsportbikes:
Vote for anti polution = priceless.... thanks for that!!!
[Thunderbolt Android Development] djkeller3:
Question... to go back to Froyo, can I just restore my BAMF 1.6.3 backup, or do I have to also re-flash a Froyo radio as well?
[Thunderbolt Android Development] gifferjesus:
Yes you have to reflash the radio.
[Thunderbolt Android Development] dragonsportbikes:
Flash the Froyo radio (yes you have to) then boot back into the GB rom and reboot into recovery and restore 1.6.3.

I just did this an hour ago = flawless
[Thunderbolt Android Development] bamaredwingsfan:
Im not sure i follow what you mean?
[Thunderbolt Android Development] tsachi:
Yes, flashed the downgrade and now waiting for the modified MR1 to download so I can finish the rooting process.

I am not sure if it is exactly the same thing or not, I saw others say they went into endless white screen before the reboots. In any case, I was not able to get into recovery, only into boot-loader - which as I understand it - the endless looping also enables. My thought was t try a full restore (radio, kernel, rom) through the boot loader. May not work in the infinite loops, but worth a try.
[Thunderbolt Android Development] djkeller3:
I jumped the gun by restoring my 1.6.3 first, then read your post and some others suggesting I do what you did.

So, while my phone was still in recovery (I had not booted out of recovery yet), I pulled the battery and my SD card and popped the SD card into a card reader and connected to my laptop and downloaded the newest Froyo radio in JCase's thread on reverting back to Froyo from GB and put it on my SD card, then put the SD card back in my TB and booted HBoot and let it do the update. Of course, had to restore my 1.6.3 backup all over again, but no biggie!
[Thunderbolt Android Development] distortedloop:
Thunderbolt's already taken a backseat to my Droid Charge as the daily driver for most uses, but I'd gotten very fond of BAMF 2.0+ and Sense 3 features the last 6 days.

Not fond enough to go through the hassle of replacing a bricked phone though.

I took the path of reversion that goes flash the radio from hboot, reboot, reboot recovery, wipe/factory reset, restore my nandroid backup of BAMF 1.6.3 that I made just before trying GB, then wiped dalvik and battery stats just for good measure.

Safely back on a solid well-cooked ROM in 20 mins or so.

Disappointing to see how viscous some folks can get around here still.

Thanks to JCASE for bringing this to our attention, and thanks to ADRYNALYNE for pointing in this direction from the BAMF 2 thread.
[Thunderbolt Android Development] Asmodeus6:
Anyone notice the GB radios work better? Especially in areas where 4g service isnt great? It doesn't seem as fast, but certainly more reliable.

Now I remember why I left froyo... The froyo radio sits in 1x at my house which gets full 3g service... And moderate to low 4g service.

I flash back to GB, voila... 4g all the time.

If the phone bricks, it bricks. I'm not dealing with the other radios. ****ing phone is useless with them at my house. I set my womans D2 next to it and it's pegged 3g. I can't get out of 1X. I tried 2 Froyo radios. Same bull****. I'm staying on GB with the xbox radio of death.

At least it lets me on the internet.

~ Posted via my surely doomed Thunderbolt running gingerbread and an alpha radio that is going to blow up into a fireball and kill all the starving children in Africa.
[Thunderbolt Android Development] corenojoe:
Meaning? Lol
[Thunderbolt Android Development] tenyrnote:
Can someone help? I am on the GB leak with Das Bamf 2.0-5 and cant get my PC to recognize my phone when in Disk Drive mode? My plans were to revert back to froyo Going into CWM recovery and flashing Das Bamf 1.7 then going into Hboot and flashing froyo radio, then reboot. I wont be able to get into hboot w/ADB cause my phone isnt recognized by my PC? Any suggestions
[Thunderbolt Android Development] kdb424:
Remove the SD and put it in a card reader and move the file that way, or any other way that works for you. With the phone completely off, hold volume down and turn the phone on. Hold the volume down until you see the bootloader (hboot) and you can flash it there.
[Thunderbolt Android Development] tenyrnote:
Thanks kdb424, if I flash the radio first I will still have an incompatible rom with it right? so how could i flash radio and rom without rebooting inbetween?
[Thunderbolt Android Development] corenojoe:
You obviously don't know how sarcasm works lol.

And, no, I'm not dumb enough to work for Verizon..
[Thunderbolt Android Development] drago34:
My phone started boot looping after I went back to froyo... fml
[Thunderbolt Android Development] chrisjm00:
Here is my view on it. The devs have a general agreement that continuing to run the leaked radio could cause your phone to get into an endless bootloop that has no fix right now. Here is an idea. Just listen to them. I reverted back as soon as I saw this thread. Because what is gonna happen? The same people who said that they were gonna stick it out on the GB radio, the ones laughing at us playing it safe, they are going to wake up one day with an inoperable phone. Then we are gonna hear "my phone is bootlooping and I can't get into recovery to fix it, helllpppp!!!!" And at that point, I'm not a big fan of saying I told you so, but that is going to be the only answer for them. Moral of the story, GO BACK TO FROYO UNTIL GB HAS A SAFE ROM.

/rant
[Thunderbolt Android Development] taurus92:
Read this last night and was debating of reverting then or waiting until this morning. Well the wifes phone lost the lock screen and would not take any screen input at all. Phone worked just a few minutes before and was just sitting on the counter. Rebooted and still no go, Rebooted to Hboot go to recovery tried wiping the cache / davlvic and more. Reboot again . No lock screen or screen input still.

Popped battery puled out SD card and put the radios and 1.6.3 on the card since her phone went from new to GB in one day. That was enough of a warning for me to get off GB on our phones.

Just reverted radios and installed the 1.6.3 remix backup on my phone. Not worth tempting fate as the GB radios / internals are not fully baked yet.
[Thunderbolt Android Development] mojonation1487:
I was :( hahahahaha
[Thunderbolt Android Development] mdeblaz:
***News Flash*** Listen to the developers when they tell you to do something. They're trying to HELP the community.

Those "risking it" by staying with GB roms will regret it one day. Would you do the same if you wanted to update your video card in your computer but the new firmware was known to burn out after a few days of use? Would you "risk it"?

I didn't think so...
[Thunderbolt Android Development] corenojoe:
Lol I was more just trying to be funny by mirroring exactly opposite of his post, but if u had a poor employment experience there I'm sorry lol
[Thunderbolt Android Development] turpintb:
No

-10 chars
[Thunderbolt Android Development] sonofskywalker3:
Agreed completely. I'm going to continue to work on the tweaks and Rom Manager extras for the GB version of Blackhole, but I won't be releasing it until we've got a compatible radio with no risk of bricks. I believe anyone who is running GB and willing to take the risk now that it's clearly known is fine, just know your phone is a ticking timebomb, especially if you tether.

But if any of you who know the risks, brick your phone, and get a warranty replacement should be flogged in the street. People like you are why we can't have nice things (e.g. unlocked bootloaders)! If the root community didn't drive up replacement rates for stupid crap then carriers wouldn't be pressuring manufacturers to lock down their phones.

And I was stupid enough to work for Verizon Wireless Tech Support, but smart enough to get out right when they announced the iPad/mifi combo deal. Was not about to start supporting the iDiots over the phone.
[Thunderbolt Android Development] Character Zero:
Sorry if this may have been covered.

So I read about the low battery theroy being debunked. It seemed the argument was that HBOOT would have complained about a low battery before attempting to flash. But where does HBOOT get its battery information? Is it possible that HBOOT is looking at OS files to get the current battery state?

So lets say the GB OS is reading the battery level wrong and thinks a 2% battery is charged to 90%. It starts to bootloop. HBOOT doesn't throw an error. Now I guess the tricky part is that HBOOT thinks the battery is ok, user tries to update radio or OS and then gets a reboot and that might really brick the phone.

I would think, and sorry if this has been proven, that you have a phone exhibiting the exact symptoms of this problem. Don't try to flash anything and try to charge the battery with an external charger and then see what happens.

Just putting it out there and I again apologize if this has been proven incorrect.
[Thunderbolt Android Development] turpintb:
Buy a micro SD reader. Like $8-10 at Wallie World.
[Thunderbolt Android Development] SubliminalME:
Ha!

That's exactly why I don't mess with my wife's phone. If I broke it...whoa. lol

Also, I reverted immediately after reading the first post in this thread. I keep good backups and keep copies of the radios on my sd card...which I organize quite meticulously, I might add. ;)
[Thunderbolt Android Development] R_Corbijn:
Can't force your help on someone

I've worked with many different populations and this applies to EVERYONE, you can't force someone to get help.

Devs put out the warning, those that want to listen will. Those that want to risk it, or be "faithful" to GB, or stick with a crowd, or whatever their justification, those folks you can't (and really shouldn't be trying) to help.

If I tell you not to play in traffic, and you decide to play in the slow lane because the risk is low, don't be surprised when you get hit. I myself will be their uploading the pics & video, but I'm sure not doing a thing to help you.

Luckily, there are better folk than me out their, and I'm sure someone will stop and scoop you up.

My 2 cents.
[Thunderbolt Android Development] doodoostains:
Not quite sure why Verizon would care if we brick our phones and file a claim? For most, isn't Asurion the ones who pay for your phone? Verizon gets money for it, they should welcome unlocked bootloaders.
[Thunderbolt Android Development] PJnc284:
They wouldn't because they wouldn't want to see the backlash that would inevitably come from it. It's just tinfoil hat speculation
[Thunderbolt Android Development] KDKobes:
Been wondering the same...I'm sure it was tossed out with reason....maybe big A can shed some light on that issue
[Thunderbolt Android Development] scottricketts:
I thought about it overnight and bottom line, jcase and team got us this far, if he's reverting, I'm reverting. Sucks, going to really miss Sense 3.0 on BAMF 2, but I'd rather still have a phone at the end of the day.
[Thunderbolt Android Development] sonofskywalker3:
If you make an insurance claim that's one thing, replacing phones outside of warranty is what insurance is for. I'm talking about walking into a Verizon Wireless store and ordering a CLNR free warranty replacement device because your phone has a "manufacturers defect". That's the problem, not insurance claims. If you load unapproved software and brick your phone it's the same as dropping it in the toilet IMO.

^ THIS!! +1
[Thunderbolt Android Development] Character Zero:
I just wonder how they debunked it other than "HBOOT would have complained". The only real way to know is on a "new" brick. It seems the troubleshooting thus far has involved trying to flash in HBOOT. It is my understanding that if you try to flash in HBOOT and it reboots in the middle you have a true brick, and there is no coming back from that. In that case a fresh battery wouldn't prove or disprove anything( ie. we tried that on the bricks thus far and it didn't fix it).

EDIT: Don't want to come off as doubting, just the engineer in me trying to understand the issue.
[Thunderbolt Android Development] erishasnobattery:
At jcase's request, I'm going to post my experience with this.

Here's the situation:

My brother and I have identical set-ups. I did the entire setup on both. Alpha GB radio, running BAMF 2.05 and latest CWR.

Both phones worked great for 3 days. On Sunday, he powered down his phone to board a plane. Approximately 3 hours later, he turned it back on and it hung at the White HTC screen.

We got it into clockwork to attempt a restore, only to discover CWR would reboot after 8~10 seconds. I had him attempt to reflash the GB radio in fastboot to no avail. We then tried flashing the stock RUU at jcase's suggestion, also to no avail.

After flashing a few more RUUs that were suggested, we ended up on a phone with the SHIP bootloader S-ON and hboot 1.4.000 and had to turn it in for warranty.

My phone worked fine until yesterday when I flashed back to stock. I'm not going to risk it.

Bottom line, there is no rhyme or reason for what happened. Get back to Froyo as soon as you can, as there is currently no fix for this.
[Thunderbolt Android Development] swimminsurfer256:
I'll take the risk!!! Meet challenge head-on!! ;)

Wait... does this mean dev for GB is going to stop??

I wonder if it has to do with the new CWR...?
[Thunderbolt Android Development] psufan5:
Yikes... going back to froyo
[Thunderbolt Android Development] adrynalyne:
K guys, I reverted to froyo last night, but for different reasons.

Here is what I did.

1. Flashed froyo radio in Hboot.

2. Booted back up once to GB, ignored errors, and rebooted back to clockwork.

3. I wiped data.

4. I flashed bamf 1.7 (not out yet).

Thats it.
[Thunderbolt Android Development] Bimmer323:
It will put you back to unrooted froyo.

I had to do this yesterday as I lost all data connection with GB rom, I guess now I feel really lucky to "only" have lost data. Re-flashed the "upgrade" ruu, with advice from JCase, and all is good for me know.. good luck all.
[Thunderbolt Android Development] WormDoes:
I'm in the process of doing this. Flashed froyo radio and am watching my stripped 1.1 backup restore as I type
[Thunderbolt Android Development] WormDoes:
You tease :)
[Thunderbolt Android Development] BennyJr:
Link to said radio? Is it the one that is like 400mb?
[Thunderbolt Android Development] shelooga:
Ditto. Ill be Mr guinea pig
[Thunderbolt Android Development] mrbracht:
you TEASE!!! :P
[Thunderbolt Android Development] BurnOne77:
That's all I did when going back to froyo and back to GB, i would just flash the radio then the nandroid. I was thinking we needed to do something different because of the circumstanced with GB'd phones bricking.
[Thunderbolt Android Development] psufan5:
lol tease!
[Thunderbolt Android Development] Hellzya:
I could use a new phone
[Thunderbolt Android Development] suzook:
*******. I'm staying on gb. **** that Froyo ****.
[Thunderbolt Android Development] howarmat:
i need step 4 please :)
[Thunderbolt Android Development] MrCapcom:
Yea I was able to get into the recovery gonna mid GB and Sense 3.0 Elements ill just flash back the radio I had before bamf 1.6.3:cool:
[Thunderbolt Android Development] adrynalyne:
It would have been out today but the machine I do my rom stuff on died.
[Thunderbolt Android Development] richB7:
I've a copy of the older non-GB radio on my SDcard. Put it on SD root, flashed it and rebooted into GB again to restore older ROM backup (of course I didn't have data at this point but so what). I don't have a data cable at work so this was the most expedtious method for me.
[Thunderbolt Android Development] MrCapcom:
Really? I usually just

Backup GB, Wipedata/cache/davlik

Install or restor backup of a rom

ADB shell

adb reboot bootloader

flash froyo radio

then reboot all in recovery
[Thunderbolt Android Development] Zarboz:
damnit i wondered why my t-bolt kept hangin at white htC screen in reboot and system boot
[Thunderbolt Android Development] htowngator:
No kidding. If the devs are abandoning ship then I'd suggest doing it too.
[Thunderbolt Android Development] Character Zero:
At least the brick has 4G, I don't even have that yet.
[Thunderbolt Android Development] spimonkey34:
This is all very interesting. My wife had a stock Thunderbolt, not rooted. After she received the MR1 OTA hers started bootlooping in the exact manner. It would reboot in the bootloader as well. Verizon replaced it no problem and she hasn't had issues since.

I'm still playing it safe and reverting though.
[Thunderbolt Android Development] mrjinglesusa:
Thanks for the warning JCase. It is MUCH appreciated that you are looking out for the community, despite what some a-holes think.

I was running BAMF 2.0-5 on the GB radio and things seemed to be running great. I didn't even have many of the issues others were reporting.

After I saw this thread, first thing I did was DL the Froyo radio, boot into recovery, wipe, and restore my BAMF 1.6.2 backup. Booted up, powered off, and reboot into HBOOT and let the Froyo radio install. Rebooted, restored missing apps, updated apps, and updated to BAMF 1.6.3.

Took all of 20 minutes and I feel much better now knowing that I am not risking a brick by running an ALPHA radio.

BTW, to all the complainers, remember that before the GB radio was leaked, you were LOVING the Froyo ROMs we have available to us thanks to the great developers on this forum.
[Thunderbolt Android Development] nerozehl:
"You can pry my Gingerbread from my cold, dead hands.." seems like some people here are pretty hardcore. As for me, if I were running an Alpha radio and was told by a developer to drop it like it's hot, I'd be on the first plane to revert-land.

Anyone stupid enough not to heed the warning deserves what's coming to them.
[Thunderbolt Android Development] KDKobes:
This is just a hunch, but I would assume it got debunked after so many people came forward with the brick issue and new batteries had been tried and didn't work still.
[Thunderbolt Android Development] dragonsportbikes:
Ok for the sake of asking. I have head back when the new froyo radio leaked that VZW can see your radio version. I am wondering if they have something to do with this. If they can see our radio version, can they see you tethering. I am asking because thy were offering the hotspot free till may 15th and it seems this bricking issue has started recently (right after may 15th)

Related maybe? Can VZW do something to influence bricking symptoms? Personally I reverted to froyo, but I am very curious about this.