yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] major_works:
First, thanks to the developers for all the hard work on GB (and everything else), and thanks for looking out for us with the notice. I appreciate the candor.

I had flashed the GB remix in the morning and saw the notice yesterday afternoon (around 3:30 pm ET). I figured these guys know better than I do and I'd best get back to Froyo pronto.

Coincidences are weird things... as I was about to download the RUU in the thread's OP, the phone decides to reboot itself. And again. And again. Mild freakout ensues. Meanwhile, I D/Led the file on the PC. Pulled the SD card, transferred the file over with a card reader, put the phone back together, booted into HBOOT and got it flashed. Whew. Then I rebooted my heart. :p

A few people in this thread have mentioned incidents where their phone died and nothing but a battery pull could get it to kick over. This has happened to me, too, not to mention scattered random reboots. It seems that the GB ROMs/radios are all just a little too flaky for general consumption.

I'm now back to Remix 1.6.3, which, frankly, I was sorry to leave for GB and have realized that I really like it. The landscape Rosie thing is way cool. I'm new to all this and I think maybe I've been scared straight. ;-)
[Thunderbolt Android Development] KDKobes:
Little harsh, but everyone is entitled to comment. This tread is getting rather large though from comments like this..kinda need to stick to the issue at hand..I think "most" of us at this point who have decided to stick it out know the risks we are taking and doing it for good reason...its all for testing and gingerbread has been from the start. I think most of us who continue to go on with it have the means to get it replaced without a big deal.....again there are some who will come complaining when it does happen to them though too.

If you pay extra for the warranty its not that hard to smash the phone, drop the phone...etc. and get the replacement. Quite sturdy phones though..dropped this thing twice on concrete and the damn thing has just a minor scuff..normally my luck it would have shattered...usually I baby the damn things..pissed me off had it for less than a week and I dropped it more than other phones I had for a year. Well at least it still works!
[Thunderbolt Android Development] tornadog:
I have completely unrooted the phone after experiencing lockups and reboots which continued even after flashing back to MR1. I flashed the unrooted bootloader to return the phone for replacement. But so far, the phone has been working great. I will check it out a few more days to see how it behaves.
[Thunderbolt Android Development] SCDroid:
So can i wipe, flash dasbamf1.7, pull battery go to hboot and flash the PG051IMG that i downloaded from the dasbamf OP thread and i'll be good to go?
[Thunderbolt Android Development] htowngator:
No kidding, but some mofo's always trying to ice skate uphill.
[Thunderbolt Android Development] Franzie3:
Quick Question, might deserve some thought.....maybe it was already asked....sorry if it was...

back to jcase's battery theory...

Has anyone had their battery at a high charge, lets says between 70-100%, revert back to froyo radio and which ever rom, and when booted up notice their battery practically in the toilet (less then 25%).

I've seen reboots drain like 5% of the battery maybe more but if this might help in anyway, maybe we should report. I am about to revert back shortly (Bamf 1.7) and i'll report my findings, i'll try and get my phone to 100% before i do it.

thanks to all dev's involved...this is the reason we're here honestly. If it wasnt for any of you and your support we would all look like zoolander and hansel trying to get files out of the computer (movie reference =D)
[Thunderbolt Android Development] htowngator:
there's a 1.7?
[Thunderbolt Android Development] psufan5:
I am not a pro by any means, but I would put my money on this being a battery charging issue. I had boot loops just like this because of a battery not charging properly. I have not experienced it on GB yet..

Anyone had a failed attempt at using a different battery to solve this issue? Im also using the extended battery if that makes any difference... I generally have a ton of battery power left over where maybe the GB roms wont fault with it.
[Thunderbolt Android Development] droid fetish:
Ok if we reloaded the froyo radio and loaded rom from backup are we ok? or should we flash the file in the op and do it that way? Since going back to 1.6.3 it has worked flawlessly like it always has, But I want to be sure. Jcase? Ad?
[Thunderbolt Android Development] spigatelli:
The file in the OP is the froyo radio. You are fine.
[Thunderbolt Android Development] TheDanimal:
nothing to see here, move along.
[Thunderbolt Android Development] JBO1018:
Well the hotspot has been extended to June 15th so that's kind of irrelevant. In any case Verizon would not go around intentionally bricking peoples phones. That would cause some serious backlash plus I'm fairly certain it would be illegal.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] BobVS:
Shelooga: I had the same problem the other day trying to load BG. I went to best buy and picked up a $25 Micro SD Card reader, and plugged the SD Card into it and deleted the file from my computer. It's probably a good investment if you plan on flashing a lot, it made the process very easy and beats trying to edit crap on a TB.
[Thunderbolt Android Development] Character Zero:
I was just wondering about how valid that is. I mean from what I have read it seems people say "I got boot loops and then got into HBOOT and was able to flash a radi or RUU", so it seems the first thing someone is going to try is to get into HBOOT and flash something. If HBOOT reboots while flashing, then you have a brick. So what I am saying, when the bootloops happen, don't try to flash anything, just try a frash battery. Maybe observe the bootloops, see how long you can stay in recovery or HBOOT. If you don't boot loop after a minute in HBOOT, then maybe it is safe to flash. Otherwise flashing when HBOOT is looping seems to brick anyway.
[Thunderbolt Android Development] KDKobes:
I agree, but I have only seen a couple people who said by replacing the battery with a new one did actually work, but to say it is the cause I don't know. Anything is possible and a good argument which is why I question if "Dock Mode" is a contributing factor to any of those issues. After removing it my phone charges like normal. It would pop up in the background every time the device gets plugged in even though you don't actually see the change.
[Thunderbolt Android Development] Zalyia38:
lol! I only need one warning!

And yes if jcase told me my TB was waterproof...I'd believe him! :P
[Thunderbolt Android Development] MechaMorph:
Exactly. My phone has actually bootlooped twice running the Das Bamf. Luckily for me it wasn't the bootloop of death. Who knows how close I was to having a $250 paperweight. Boy the wife would have been pissed.

So as soon as I saw this thread and saw the word bootloop I gulped. I flashed back to Das Bamf 1.6.3 about 2 minutes later. I always keep a backup of the previous ROM I was running on my SDCard for these types of things. ;)
[Thunderbolt Android Development] BobVS:
Reflash a Froyo Radio in HBOOT
[Thunderbolt Android Development] thedefectkid:
Thanks for looking out jcase I downgraded but cant wait to get back on the gingerbread road.
[Thunderbolt Android Development] BobVS:
You might also want to try connecting your phone to the PC with 'Internet Pass Through' mode. This will load the new GB drivers on your PC and you should be good to go in disk mode after that
[Thunderbolt Android Development] zeekaway:
In my case I was stuck in a bootloop running DasBamf 2.0-5 and I did a battery pull and went into hboot and reflashed the GB Radio..Now I have 12hr batterly life and everything works exceptional except txt message times are kinda wacky (hour behind whomever I'm texting)-Also takes abt 5-6 hours to fully charge.
[Thunderbolt Android Development] LTL11:
Wow, just wow.

First off, thank you Jcase and Adryn for the warning. Your involvement and time spent on our phones is very much appreciated.

I reverted back to Froyo last night, took me 15 minutes and had my BAMF Froyo nandroid back up and running.

I really, really loved GB, liked netflix, sense 3.0, and it ran much smoother imo but totally not worth the risk of a hard brick, even if it is a small risk.

For the record I was running gingeritis and did not have the bootloop issues resluting in a brick but twice over the past two days I have had the phone become completely unresponsive and nothing but a battery pull would allow me to reboot.

Something is definetly messed up with the gingerbread leak regardless of ROM.
[Thunderbolt Android Development] lokirevamped:
Thanks for looking out JCase

I only have one question before I flash back to Froyo. Where is the picture in the Gingeritis ROM stored (Lady in the Green Wrap) on the phone so I can back that picture up to my sd card?
[Thunderbolt Android Development] KDKobes:
I would be interested in knowing how many people who got the death boot were in 4G area vs 3G area..
[Thunderbolt Android Development] ska.t73:
There were a couple posts back a few pages about it happening in both areas.

IMO I really wouldn't worry about it. I would suggest just reverting back for now, according to HTC and VZW we are supposed to have GB by the end of June anyway. I'm pretty confident that we will be seeing a better leak comming out in a few days or weeks. Remember this leak had a lot of problems with it other then this boot loop thing. We were able to ignore or work around most of them but the leak was definetly an early alpha and not ready for prime time.

I reverted back and will just wait a couple weeks for the next leak.
[Thunderbolt Android Development] Ghost401:
I was wondering the same thing, I live in a 3G only area so it would be good to know if its only a 4GLTE problem.
[Thunderbolt Android Development] fkfmfz:
if you can afford to risk your phone to stay on GB, is all up to the end user.

also this is not rom releated, is more of a bad radio we are using and might work for some and maybe not for others.

use at your own risk.

is noone fault if you decice to stay on ginger leak and your phone bricks a week

from now. you been warned. thanks jcase for the headsup...;)

going back to froyo until it all gets sorted.
[Thunderbolt Android Development] bp328i:
I'm one of the un-lucky ones who Thunderbolt has gone to the great beyond. My work is 4G but my home (where the bricking happend) is 3G only. I'm about 15 miles outside of 4G at my house.

Hope this helps with your question.
[Thunderbolt Android Development] Morkai Almandragon:
Are you still able to get into the bootloader at all?
[Thunderbolt Android Development] bp328i:
I can pull up the bootloader just fine. It does not reboot on the bootloader, it's just when you go anywhere else that it starts rebooting.

I was able to flash the stock RUU from the bootloader without issue. Once flashed and try to start the phone that's when you get to the splash screen and loop.

I even was able to flash the stock recovery and hboot and got the phone back to Ship S-ON. I tried to bring up the stock recovery and it opens for maybe 2 - 5 seconds then loops.
[Thunderbolt Android Development] scottricketts:
Consider me scared straight. I need a phone that works and can't afford a replacement. *****en Sense 3.0 isn't worth it.
[Thunderbolt Android Development] trikotret:
That sucks. Are you getting a replacement through insurance?
[Thunderbolt Android Development] trikotret:
I think its just a matter of time when a new GB radio leak will come out since we are close to June. Then let all the GB roms pour out :D
[Thunderbolt Android Development] DroidTh3ory:
http://www.engadget.com/2011/05/26/htc-thunderbolt-issues-abound-but-a-fix-is-on-the-way/

Anybody see that?? :)

___

Sent from my HTC ThunderBolt 4G LTE on XDA Premium.
[Thunderbolt Android Development] drago34:
Ok, so my phone randomly reboots while I try to do anything in recovery now, however sitting on the hboot menu I am not getting a reboot... the question I have is should I boot into hboot with the mr1 and install it?
[Thunderbolt Android Development] Asmodeus6:
It's in htc wallpapers. So it should be in the resource folder or media if you use root explorer to extract it.

I just looked. It is in resource folder.
[Thunderbolt Android Development] psufan5:
This probably has nothing to do with the GB leak... just saying. Everyone would have the issue, not just a few.
[Thunderbolt Android Development] seanheng:
I've had random reboots at least once a day since flashing the GB rom, but that seems like the bug that Verizon and HTC is working to resolve.

After flashing the v2.5.4GBtest6 and running the speedtweak.sh to remove the setting so i can use SETCPU and using SETCPU for max, min, and governor I havent had a reboot yet and everything seems more smoother.

I am using das bamf 2.0-5

latest kernel v2.5.4GBtest6

I just love my hulu and netflix and sticking with GB

btw I've been using das bamf since day 1 release and updating as it comes out.. very nice work
[Thunderbolt Android Development] adrynalyne:
Then continue to use GB.

It really is that simple.

If you brick, then you can add your voice.

We all make decisions in life.

While you are doubting the validity of this thread, remember, we are all looking for the truth and the cause. Don't diss the message because you do not like it. If GB is killing the phone over time (what if its continually writing to emmc over and over and causing early failure), if this message saves just one phone, then its worth it.

While you may doubt, lets remember how many Samsung updates have been pulled in the past due to killing internal storage.
[Thunderbolt Android Development] drago34:
The funny thing is GB was running amazing... why oh why did I try to play it safe.

Edit: I'm going to go put my head underground for 10 minutes and hope it works.
[Thunderbolt Android Development] tekhna:
so my question is, should those of us who were able to revert to froyo return our phones anyway? if its corrupted memory it may bork our phones down the road, even on froyo, right?
[Thunderbolt Android Development] onyx_64:
Just a thought - Does extreme overclocking/undervolting (which many of you have tried) cause eMMC corruption? We already know that it can corrupt the SD card ;) So why not the emmc as well?
[Thunderbolt Android Development] twistedumbrella:
Pull the battery, pull the SDcard, load hboot, use fastboot. Already happened to me where it wouldn't go past the splash and hboot froze when it did the pg loads. Can't promise, but it worked for me.
[Thunderbolt Android Development] bp328i:
My phone was running AWESOME when I went outside. When I came back in...not so much.
[Thunderbolt Android Development] erishasnobattery:
Drago, have you flashed anything yet?

And it's definitely bootlooping clockwork?
[Thunderbolt Android Development] miketoasty:
psufan I usually agree with you but not this time. Anyone who is even remotely interested in computers knows that no 2 devices built EXACTLY the same using parts built at the same plant in the same machine work the same. Look at OCing some people can get their phones to run 2.0GHz when my phone usually craps out at 1.6GHz.

This problem so far is completely impossible to predict, and until further knowledge anyone can face the reboots of death. Noone knows why its happening but unless you dont mind insurance fraud stay with Froyo or CM7.
[Thunderbolt Android Development] lokirevamped:
Thank You, I love that picture. :D
[Thunderbolt Android Development] lokirevamped:
Thanks

Thank You, I am now back to Bamf 1.6.3 I am trying to get teh 1.7 that the one user has. :D
[Thunderbolt Android Development] DroidTh3ory:
Just bricked... http://xdaforums.com/showpost.php?p=14166175&postcount=2301
[Thunderbolt Android Development] KDKobes:
I am running 2.5test4 kernel on extreme mode since day 1 of install so I guess we will find out!! Someones still got to test it....cant help myself...just not a big deal to me to get a new one.
[Thunderbolt Android Development] mar5hal:
i am sorry if this is a dumb question, i'm not as up to date with the radios as others and couldn't fully understand some of the posts in this thread but if i am running gingeritis viii and everything is running smoothly, am i still at risk for the brick? i haven't had a problem with anything yet but if im not mistaken that doesn't mean im in the clear so to say. any info on this would be greatly appreciated. pm me to keep the thread clear if the answer is somewhere i've overlooked, thanks
[Thunderbolt Android Development] Taykiin:
sorry to hear...
[Thunderbolt Android Development] kriskmk:
mission aborted! back to froyo for now. Can't take a chance.
[Thunderbolt Android Development] psicrest:
I also called 611 today, I kinda lied to them that my phone keeps on rebooting even though my phone is perfectly running without any problems. I just want to know how easy it is to replace my phone.

After some few questions from the operator, i was transferred to a higher level support and told me that random reboots/ boot loop is a known issue for thunderbolt and they are happy to send me a phone replacement.

F.Y.I i bought my phone 2nd hand, i didn't bought it directly to vzw.

Now they are sending a new phone on my mail and told me that they have attached a prepaid envelope there so i can send them my old phone. The whole process took probably 10-15 minutes.

It looks like the bootloop of death also happens in froyo roms so were not safe even if we revert back to stock.

I also saw this in endgadget : http://www.engadget.com/2011/05/26/htc-thunderbolt-issues-abound-but-a-fix-is-on-the-way/

I have a feeling that blaming the GB radio is kind of a witch hunt since we dont have enough proof to pin point the radio is the cause. At the end of the day it is still your choice whether to revert back or to stay in GB.

I went back to CM7 froyo last night and decided that i rather take the risk and try to find out whats causing the boot loop so i went back again to GB/das bamf.
[Thunderbolt Android Development] bp328i:
There is no sign of the phone bricking. My phone never, I mean never had any kind of reboot prior to the brick.

I was seeing people talking about phones rebooting on their own and was thinking I was lucky as I did not have the issue.
[Thunderbolt Android Development] bp328i:
There is a big diference between random reboots/ boot loop and the bricking that has happened to some of us.
[Thunderbolt Android Development] freebird_78:
Sooo tempted to go back to BAMF 2.0.5....

As good as BAMF 1.7 is, especially over stock, I have to say after being on BAMF 2.0 since it's inception, anything less SUCKS.
[Thunderbolt Android Development] Asmodeus6:
What I want to know is; if the emmc being corrupted by the radio is the cause. Does that somehow go away when I flash a Froyo radio? Or is this going to be hanging over all of our heads for months to come...

I can't wait to see if people reverting end up with bricked phones that went back to Froyo.
[Thunderbolt Android Development] vdefender:
HOLY CRAP! JUST NOTICED THIS ON ENGADGET! AAHHH!! THE STOCK RUU DOWNLOAD IS GOING TO TAKE 8 HOURS!!! AHHH!!!

Mirror anyone?? PLZ?!
[Thunderbolt Android Development] tbhall77:
Bug probably got introduced when they pushed out the MR1 radio. There were already reports of issues on the MR1 even on stock. Bug must of got worse in the alpha radio.
[Thunderbolt Android Development] kdb424:
Flashing them at different times won't damage your device, or stop your ROM from working. The only thing it does is "break" your radios (wifi, bluetooth, 3g, ect) when your in a wrong ROM. You can reboot, then boot into recovery and just flash then (you can enter recovery from bootloader if you can't get to a ROM.
[Thunderbolt Android Development] hydRoponic chRonic:
downloading this reminds me of the days of aol 2.5
[Thunderbolt Android Development] Asmodeus6:
This is correct. I have done it twice now going back and forth.
[Thunderbolt Android Development] probotic:
haha AOL. I still have video@aol.com , don't use it, but keep it on principle.
[Thunderbolt Android Development] vdefender:
Alright I finally got it downloaded and I'm flashing back to Froyo :( :(

Ggrrrr, Gingerbread was SOOO FReaKin NIIIICE!
[Thunderbolt Android Development] MattCropley:
oh my, i think i might take the risk of bricking my phone... im back to froyo. but i miss das bamfs gb so much. everything else sucks lol ;p
[Thunderbolt Android Development] Chris Hansen:
The bricking that is discussed in this thread/the OP is a result of perpetual boot loop. They can't boot into recovery/HBOOT since it keeps rebooting, so the phone is bricked at this point.

I believe that is what the post you quoted was referring to.

Thrown by Zeus himself
[Thunderbolt Android Development] sublimaze:
If your theory is correct, the GB radio is corrupting emmc, the bad areas will never be useable, right? Will everyone that flashed GB radio eventually get the reboot of death, even if they reverted to froyo?
[Thunderbolt Android Development] joshnichols189:
I'm going to say no, because if it's caused by corrupted writing to Emmc then if you stop the corrupted writing you should be fine
[Thunderbolt Android Development] jawa5636:
Been wanting to ask this for a long time. Are all the folks wanting GB over Froyo just obsessed with the latest, greatest or is it really THAT heads or tails over Froyo? Not looking for a long debate or to piss anyone off. I just don't see why folks want it so bad.

I am currently on the BAMF remix 1.6.2 and it's damn near flawless. No FCing. No OC'ing needed to get things to run smooth. No reboots. Only thing I can see that doesn't work is Netflix and it can't only be about that. Can it?
[Thunderbolt Android Development] mar5hal:
i can't seem to locate my emmc folder. instead i see asec, obb, sdcard and secure. normal or am i screwed?
[Thunderbolt Android Development] sublimaze:
emmc is the flash memory, not a folder. Flash memory has a finite number of times it can be written to, then it fails and is no longer useable. Kinda like bad sectors on a hard drive. One theory being tossed around is the GB radio alters emmc memory beyond its reliable limit, then the system requests data in these bad areas, which results in infinite bootloop. At least that's my understanding, anyone correct me if I'm wrong
[Thunderbolt Android Development] kdb424:
It adds a lot of new things (some with sense 3 stuff) I personally loved it for the lockscreen as I use 160DPI so it breaks most of the rest of sense. It does however add a bunch of stuff assuming it doesn't break our phones.
[Thunderbolt Android Development] SCDroid:
it's awesome. Quicker, more options and sense 3.0 lockscreen is the shhh.
[Thunderbolt Android Development] 00negative:
Coming from a Motorola phone is there not a way to sbf a phone through adb.. or is it not possible due to the fact you would have to get phone to stay in hboot while doing it?
[Thunderbolt Android Development] hydRoponic chRonic:
a whopping 2 hours and 15 mins to download this nonsense! well thanks.
[Thunderbolt Android Development] joshnichols189:
I'm under the impression that flashing an RUU in hboot is the equivalent of an sbf.. though I could be wrong, but I've never heard of anyone sbf'ing an HTC phone it was always flash an RUU in hboot..
[Thunderbolt Android Development] SCDroid:
download the radio in the bamf1.7 thread and flash bamf1.7 and then the radio. gets you back to froyo too
[Thunderbolt Android Development] crackedvenom2:
Where is this download at that you are talking about?

Edit: If you are talking about the one in the first post, use megaupload. Mine downloaded real quick

Also noticed i have great battery life today. Not sure if its Froyo or because i redid the battery stats.