yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] adrynalyne:
I personally went back to Froyo. Not because of this issue, but because I couldn't get battery life under control, and the camera issues were causing me issues with my wife and daughter ;)

That said, as long as everyone is aware of the risks, it is their choice on what to run.

There is no empirical evidence that this FOR SURE is due to the leak. However, because so many are running it, it sure seems like it is.
[Thunderbolt Android Development] papped:
I got stuck in a reboot loop about 10x the other day... Eventually recovered, but this is enough to get me to switch back to Froyo for now...
[Thunderbolt Android Development] adrynalyne:
Insurance companies bend people over all the time. Morals and insurance have no place on the same page, much less in the same post. There is nothing wrong with them receiving the cornholing, rather than doling it out without vaseline, as they do so often.

I agree with you about going to Verizon with it. Insurance? Not so much.

PS--Insurance has no bearing on locked bootloader policies. Increased rates, maybe, but thats it.
[Thunderbolt Android Development] MrHawaii:
True, but what does it actually do? My experience, I power down the phone like normal so that I can boot into bootload by holding volume down and power button. I forgot to uncheck fast boot so as I am holding down the volume button I hear the beeping sounds like I am lowering the volume. Then the phone vibrates like I just turned it down to vibrate only. All the while screen us off and light for standard buttons is off. So is the phone still kind of on if someone has fast boot checked and powers down using the power button. Reminds me of BlackBerrys, when you power down using power button it boots fast, but if you pull battery it takes longer.

So if the TB is not fully turned off by using fast boot and someone pulls the battery (for some reason), could that corrupt files?
[Thunderbolt Android Development] want a droid:
Around $89 for me is worth it when the bootlooping problem is only happening to this little amount of people.
[Thunderbolt Android Development] lootnplunder:
Do you have a link to the radio or is it included...I guess I am going to do the same but I don't see that radio anywhere... I got to use Gingerbread just long enough to get it setup the way I like...damn
[Thunderbolt Android Development] doug piston:
Like I said before, same isues on the Incredible right now and throughout the life of the phone. Bricks are just on the rise on that device for the moment. I have many examples of what seems the same exact issue.

Mind you it is a different device but I think HTC is having some hardware issues.
[Thunderbolt Android Development] MrHawaii:
I think I remember users stating this in the general forum. Let me go dig through them and find them. Sorry I am on mobile so might take me awhile.
[Thunderbolt Android Development] adrynalyne:
Are you familar with suspend to ram? Same idea, except it closes down currently running apps.

If you pull your battery, I bet fast boot will not work when booting back up.
[Thunderbolt Android Development] tu3218:
Oh okay, didn't realize it hasn't been that long. I didn't initially flash so probably why it seemed longer to me. thanks for the clarification
[Thunderbolt Android Development] kyrumo71:
I'm gonna take a chance and stick with GB, something tells me that HTC and Verizon wants to put the Thunderbolt on lockdown, I didn't see to many cases of GB bricking phones.
[Thunderbolt Android Development] joshnichols189:
Here is your thread.

http://xdaforums.com/showthread.php?t=1090666

Different circumstances.
[Thunderbolt Android Development] DroidTh3ory:
Well, when Asurion took my money and signed my up to take my money every month.... They NEVER asked me if I was a dumbass.

I learned in life... Always ask questions, bonus if they're the right ones. :)

Anyway, back to the topic at hand.
[Thunderbolt Android Development] adrynalyne:
#tinfoilhat
[Thunderbolt Android Development] MrHawaii:
Right, they were non rooted and getting boot loop issue. (I think). Let me see if I can find those threads. I am just saying I think I remember reading that.
[Thunderbolt Android Development] miketoasty:
Then why would you stay with the radio bricking phones? Are you trying to say that Verizon forced Jcase to post this here? I really don't think anything of what you said makes sense.
[Thunderbolt Android Development] joshnichols189:
I linked your thread above^
[Thunderbolt Android Development] miketoasty:
Now would be THE perfect time for Slayher to release a new CM build. :p
[Thunderbolt Android Development] bp328i:
This is based off what a Best Buy manager told me when I brought my bricked GB Thunderbolt in. But he said that he has had three other Thunderbolts brought in that were doing to same this as mine. He did not say when they were brought in and he said he "thought" they were not rooted, but really how could he tell?

And to everyone saying things like oh it's showing no signs of bricking, or I will just flash the stock RUU if it bootloops. NO, NO, you won't just flash the stock RUU because if it happends to your phone you can flash anything you want and it won't help because this is not just a bootloop!

And what are the signs of bricking because mine was running like a champ when I went to mow the yard and then come in to fine it "bootlooping", guess I should say bricked. Mine went last Saturday.

I'm without my Thunderbolt for up to three weeks while it's being repaired. I rooted it so I did not call version and have them send me a refurb.
[Thunderbolt Android Development] bagsofcole:
Does it matter how we revert?

O.k. I read all 19 pages and haven't found an answer. Does it matter how we revert back to froyo? Earlier today before I noticed this thread I just happened to reflash the froyo radio and my backup of the bamf stripped (awesome) because i use my phone for work and need a reliable camera and internets in the field. So then i see the recommended revert is to use the mr1 ruu in the OP……

so:

1 does it matter how we revert back to froyo?

2 if I'm all ready back to froyo with a froyo radio via manual method, can i still flash the ruu or will that brick the phone because it's the same radio?

ps

i will miss sense 3.0, it was so sweet, but not worth the risk. reminds me of miui lockscreen but like butta!
[Thunderbolt Android Development] rsmiff:
adrynalyne. has this bricking happened to anyone you know to be credible??
[Thunderbolt Android Development] gobluejd:
One word!

RAPTURE :)
[Thunderbolt Android Development] MrHawaii:
Thanks, so I guess a little different but non rooted stuck in boot (HTC white screen) and unable to resolve via adb or hboot.

Here is the other one. He was rooted and when took it to BB manager said they are getting multiple instances.

http://xdaforums.com/showthread.php?t=1090531
[Thunderbolt Android Development] joshnichols189:
As you can see they are completely different. The first one fixed his, but the second did not. The second was on 2.3.4 with the alpha radio. In fact, he posted right above you.
[Thunderbolt Android Development] adrynalyne:
I guess it is how "credible" is defined. Some of these users with bricks have been regular IRC members. Those tend to be more...technologically inclined than a lot of forum posters. No offense intended towards anyone.
[Thunderbolt Android Development] dbu:
This can't be a serious question.
[Thunderbolt Android Development] erishasnobattery:
I'd like to think of myself as "credible". And although it wasn't my phone, it was my brother's, while he was sitting next to me.
[Thunderbolt Android Development] adrynalyne:
Dude, if my phone has a soul, I am going to an exorcist.
[Thunderbolt Android Development] ibsk8:
thanks for the heads up, i was having some serious bootloops issues the other day. Not in recovery though.

I have since loaded the 605.7 cdma/lte combo radio and reverted to a backup.

I had been contemplating going back to froyo because of bugs and battery issues, I'll be looking forward to a future GB radio as I really dig some of the sense 3.0 elements.

Thanks to all of the devs for your time and hard work, openness and honest.
[Thunderbolt Android Development] dbu:
Facepalm...
[Thunderbolt Android Development] bagsofcole:
wtf? ah!

(10)
[Thunderbolt Android Development] 00dvanmeter:
is it possible they are pushing an ota to see if the radio's match what they should be? if they dont match it causes a bootloop?

Guess I have to change my signature too lol
[Thunderbolt Android Development] adrynalyne:
No, that wouldn't be it.
[Thunderbolt Android Development] Dstu03:
I think this is just away for verizon to boost its phone sales. Brick a couple of t-bolts with a bad gb leak. Good thing I bought the insurance..If it happens to my I will be heading to the shooting range and putting a bullet through it. I am sure verizon will love exchanging the phone for me.
[Thunderbolt Android Development] adrynalyne:
Some hilarious theories being posted here, LOL.
[Thunderbolt Android Development] MrHawaii:
Thanks, no I am not familiar but that makes sense. Did you ever get to look into when I posted about files being leftover when wiping ans flashing a GB rom? I am in no way a software dev or coder and would not begin to pretend that I am. I am however a user and have had experience flashing Android and WinMo for a few years now. Never made my own rom but for WinMo did use kitchens to build a rom to my liking. I also did skins for PCM keyboard (I think it is still up on their site). I also have worked in the wireless industry for almost 6 years now and have worked in retail and held positions from rep to store manager.

So not a dev, just a user who probably understands wireless a little better than the n00best of the n00bs. Just trying to give you all feedback so you can pump out the best goods for us.

I would love to hear your thoughts on the files being leftover. I don't think I got a sufficient response yet. Even if I got no MrH you're a dummy and you're doing it wrong would suffice.
[Thunderbolt Android Development] DroidTh3ory:
Its the Government.
[Thunderbolt Android Development] miketoasty:
Thats actually quite funny. I would love to see the store employee's face when you hold up your TB and are like "Ya uh, I accidentally shot it". Thanks for the laugh at the end of my work day.
[Thunderbolt Android Development] houseboatwayne:
I would like to know the numbers on this. Seems like people would have been kicking screaming in the forum before this alert. I'm pretty fed up with the software that was release with the Thunderbolt. My phone is just now where it should have been out of the box. It's the whole reason I'm always hanging around.

If it bricks I'll go back to my Incredible and wait till I can upgrade, then buy something besides HTC.
[Thunderbolt Android Development] joshnichols189:
The people it's happened to were smart and went to IRC instead of complaining on the forums.
[Thunderbolt Android Development] DroidTh3ory:
Makes you wonder... How many of the brick incident victims had CM7 on them prior to the GB flash.

CM7 has been known to leave its laundry laying around after it has been moved out.
[Thunderbolt Android Development] themobijew:
so, whats are the devs doing? u guys back on froyo or livin' the risky life?
[Thunderbolt Android Development] 00dvanmeter:
I'm going back to froyo as soon as das bamf 1.6.3 remix is done downloading..which is now :) ohhhh wellll.....
[Thunderbolt Android Development] 92slammer:
i would think it would be alot more than just a "few" for jcase and others to alert us like this.
[Thunderbolt Android Development] Hagbard57:
The part that is killing me (well along with the conspiracy stuff) is that people are looking for any reason to doubt jcase and not revert. I think someone said it before, it is a lockscreen with cool stuff that has wonky wifi and and usb that might or might not mount depending on if it is the second Tuesday of the month.

So we get "numbers?" or asking for "credible" stories. If you want to revert do it, if not don't ***** if (or when) your phone bricks. And please tell more stories of the insurance fraud you are going to commit so I am extra pissed when my premium goes up again.
[Thunderbolt Android Development] MrHawaii:
Um, the first one did NOT fix his. He had to get it replaced. The difference I was referring to was that obviously GB peeps are getting this issue but maybe non rooted devices are having the issue also. Maybe we aren't seeing them here because the average user would go to VZW and have it replaced.
[Thunderbolt Android Development] erishasnobattery:
I don't think numbers have anything to do with it. I think it's the severity that is the concern. At this point, it literally un-recoverable. Period.
[Thunderbolt Android Development] ipawd1:
Let me know if I'm wrong in advance for wondering if... I stay and chance it with GB on my thunderbolt and it bricks... and I just simply go back to Verizon and say i updated their OS to my phone and it's bricked/fc... since I mean.. XDA and other droid forums have told me they are honoring the same type of issue thanks to the "fix" update they gave.

let me know...:confused:
[Thunderbolt Android Development] joshnichols189:
Sorry, you're right he didn't fix it. But they're still different. The first one is hanging at the HTC splashscreen.. he is by no means rebooting endlessly.
[Thunderbolt Android Development] doug piston:
+1

And I am not doubting Jcase nor anyone. Just expressing an observation that the Incredible has been having the same style issue.
[Thunderbolt Android Development] albotz21:
My gb was working great 4g and everything. Guess ill puss out and go back to remix. Thanks for the heads up
[Thunderbolt Android Development] montavious:
I'm at work right now until 9pm, I saw this thread and need to return to froyo. My question is since i'm stuck at work, can't dl the MR1 ruu until i get home later (3g only in Binghamton NY...) Does anyone recommend leaving the phone on/shutting it down for now until I can get home to put Froyo back on it? Don't want to brick it somply because I got stuck at work, lol. Thanks for the heads up jcase, just like the old Eris days :p
[Thunderbolt Android Development] Zarboz:
i know ill be reverting when i get home this afternoon from work

sucks but o well
[Thunderbolt Android Development] psufan5:
Its not going to happen dude... just revert when you can.
[Thunderbolt Android Development] erishasnobattery:
I would leave it on until you're ready to revert.
[Thunderbolt Android Development] Mystery252:
I guess it's true, you really can't catch the gingerbread man :(

shot from a Thunderbolt!
[Thunderbolt Android Development] MrKleen1:
I am concerned about the new Clockwork Recovery. After reading this I thought I would do a backup and then see what happens. I flashed the new recovery that I noticed and as soon as I did this I got an error upon rebooting. It said unclean shutdown, settings not applied.

I've never had issues until I just flashed this new clockwork recovery....
[Thunderbolt Android Development] MrHawaii:
If anyone is interested, here was my thread about the files being leftover and the process I do to wipe and flash. I never use Titanium or other type of backup program to restore apps. And again if I am doing it wrong, please call me an idiot and tell me how to do it correctly.

http://xdaforums.com/showthread.php?t=1088238
[Thunderbolt Android Development] qumahlin:
Unless i'm wrong you still seem to be able to get into hBoot so why is everyone reverting back even if they aren't having issues? I just downloaded the RUU and threw it on my SD card so in the event the issue does happen to me i'm all set to fix it.

Bamf 2.0-5 has been running better for me than any Froyo rom i've ever had. I don't get random reboots, my GPS lock rarely takes longer than 5 seconds, my phones speed and battery life is better.

Quite frankly reverting to stock or a froyo ROM means i'd be back to dealing with a mess of issues that the GB rom's have fixed for me. The only issue I have with my GB rom is the phone force closes if I have twitter hooked up to sense and try to call a linked contact, but that was an easy thing to fix.
[Thunderbolt Android Development] joshnichols189:
hboot reboots.
[Thunderbolt Android Development] doug piston:
Because it won't stick. You will still be eating bootloops.
[Thunderbolt Android Development] want a droid:
This^

+1111111
[Thunderbolt Android Development] houseboatwayne:
I know Jcase is serious. I'm just asking the amount he is seeing? It's an honest question so please don't troll me.
[Thunderbolt Android Development] qumahlin:
That just means that for some reason your phone didn't do a full clean shutdown so whatever program you're using to apply settings (i'm assuming you're using the bamf toolkit based on the message you got) played it safe and didn't apply any CPU changes to avoid it being the culprit.

It's basically "The phone rebooted, couldn't detect why, so lets not mess with CPU Speed / Governor changes in case its the culprit"
[Thunderbolt Android Development] ska.t73:
yes you are wrong, the problem is that you can not fix it with the RUU. That is why JCase posted the thread. If it could be fixed then the thread would say how to fix it. Since they have not been able to fix any of the phones this has happened to, JCase is advising to revert to the Froyo radio for now.
[Thunderbolt Android Development] JBO1018:
Thanks for the heads up Jcase. Already got her back to Froyo. Loved the GB roms but they are not worth a brick.

On another note...why are people freaking out about making an insurance claim on a bricked phone? I understand that it IS fraud if you WARRANTY your bricked phone by lieing and saying "durr it just stopeded workin" but insurance is insurance. It doesn't matter if I brick it flashing or throw it off the empire state building, thats why you pay a free every month plus a $100 deductible. So if you break/lose your phone you can get a replacement without having to shell out $600. How is that fraud?

And by the way the bricks are most definitely cause by the government sponsored alien invasion. Just so ya'll know.
[Thunderbolt Android Development] Mustang02:
Back to crappy GPS lock....bummer.
[Thunderbolt Android Development] dalrym05:
This is just because you were using the CPU settings in bamf tools and it didn't go through the full sshutdown after flashing the new clockworkrecovery. Its normal. Its a fail safe just invade your overclock and governed settings is was caused the reboot. That's all.
[Thunderbolt Android Development] suzook:
LOL...Ill keep enjoying my GB. What other people do is their choice. *****:p
[Thunderbolt Android Development] rsmiff:
completely serious and valid
[Thunderbolt Android Development] mrsmith35sg:
Do we have to revert to the MR1 radio? Or is going back to the stock one work perfectly fine too. Thanks
[Thunderbolt Android Development] NoRegrets78:
Haven't had the nerve to move up from bamf 1.6.3 but I ALMOST pulled the trigger, then I saw this.

My sympathy to all who have been affected, even with the warnings that every rom has about bricking and the such.
[Thunderbolt Android Development] houseboatwayne:
Let me throw something out here. I did surface mount component level repairs on the first large display device Motorola came out with years ago. In about 4 or 5 months large numbers of them started coming back due to stress cracks. We reflowed the parts and fixed the problem until they came out with a rev B pcb board.

No one wants to tear there Thunderbolt apart. But I wonder if there is any place on the internet where HTC board revisions could be found. It could be the answer.....just a long shot.
[Thunderbolt Android Development] stagejuan:
im on a GB ROM and saw this... guess ill be trying the 1.6.3 BAMF

Can someone please tell me (or possible link) to which Radio I need to use to go back to that ROM?
[Thunderbolt Android Development] mariol90:
nooooo... that was one thing i really liked. it took less than 5 seconds to get a GPS lock indoors.
[Thunderbolt Android Development] want a droid:
First radio:

http://xdaforums.com/showpost.php?p=13093559&postcount=1
[Thunderbolt Android Development] oxidant11:
so I have a question... why do people keep saying your lucky to have insurance, you know you can just call or go to verizon store and get it replaced under warranty, 90 percent of verizon employees dont even know what root is so all you have to tell them is its rebooting, they may try to hard reset which wont work obviously and then they will send you a warranty replacement.
[Thunderbolt Android Development] GutterIsATool:
Well, if nothing else, my brief stint on a Gingerbread based ROM fixed my GPS locking issue.

I had been on the fence about flashing back, but this was enough to get me to jump.
[Thunderbolt Android Development] rmoffitt321:
I gave myself a little bit of a scare

So I read this and said, "sure I'll go back to froyo until the figure this out, no problem." But I thought I'll back up my ROM so when the radio thing is figured out I can get right back to where I left off (gotta love Netflix and Hulu). After the backup I decided to let it boot back to GB while I waited for the old radio to download and I thought I'd simply mount my SD card to my computer and drop it on my SD card. Randomly my phone reboot and I started freaking out (the sky is falling, the sky is falling). When the phone didn't get caught in a boot loop and loaded up fine, I rebooted into recovery and decided and I'll just put the old radio on through recovery and then go straight to HBOOT.

I've never had a random reboot scare me so much in my life and I've been rooting phones ever since the OG Droid days.
[Thunderbolt Android Development] dm5363b:
I'LL say that I had to revert to version 7 because of a similar issue, not sure it's the same, regardless I wish all including myself luck as I am staying on version 7 as It's awesome .....
[Thunderbolt Android Development] CBMC:
You can use hulu on froyo (check the hulu patch thread), but how I am going to miss my netflix.
[Thunderbolt Android Development] joshnichols189:
CM7
[Thunderbolt Android Development] CBMC:
But are the 4g problems worked out yet?
[Thunderbolt Android Development] stagejuan:
Thank you sir:cool:
[Thunderbolt Android Development] SirVilhelm:
I am wondering this too
[Thunderbolt Android Development] SirVilhelm:
^Word from IRC is NO
[Thunderbolt Android Development] TheLoonyRebel:
4G does work on the current CM7 but you have to go into network settings then switch to CDMA with EvDo. Let it sit for a minute or two. Then you can switch it to CDMA + LTE/EvDo (or even LTE only if you prefer).
[Thunderbolt Android Development] andrewc513:
Can this become a retroactive issue? As in, if I'm on the GB radio and a GB rom now and not experiencing issues, could the issue still happen later on even after reverting back to a Froyo radio/rom?
[Thunderbolt Android Development] jlevy73:
I have lots of respect for jcase, adrynalyne, thedudebutch etc etc. That being said, besides the statement that some phones have been bricked due to gb radio, what other proof does anyone have. I remember another reputable developer getting lambasted over posting certain information without facts. So where's the evidence besides take my word for it. If I've missed that in reading over the last 30 pages of posts my apologies
[Thunderbolt Android Development] decaturbob:
Goes back if you value a dev's opinion. His warning is pretty clear. I've reverted back to bamf 1.63 remix in about 20 mins and when the issue is worked out, I'll go back to GB in 20 min. Dont want to lose my phone.
[Thunderbolt Android Development] joshnichols189:
I understand where you are coming from but the reasoning is no one is aware of this happening on Froyo.. ever.. and due to the alpha nature of the radios this is what the devs have reduced it to
[Thunderbolt Android Development] erishasnobattery:
Well I can certainly take a screenshot of a my non-booting phone, but that just proves I can take a picture of the splashscreen?
[Thunderbolt Android Development] Mustang02:
Only reason why I was on GB. That GPS not locking on froyo makes me want to punch babies.