yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Franzie3:
I hate to just "add another post" but jcase and others have helped all of us in some way. They gave me help as a first time ADB noob when i rooted my tbolt and I

HAD NO PROBLEMS.

For people with problems....instead of complaining...ask for help...don't be ashamed to ask, unless you want a pwned phone...Many people have asked and are always very happy they did..

I know its unfortunate that no brickers have showed but i would trust the judgement of jcase and the rest of the developers here in the tbolt thread because quite simply, they have invest the time and effort to give us the best advice...

So in turn, do what mama always taught you, if you don't have nothing nice to say, don't say nothing at all....let's all work through it and have a better tbolt community
[Thunderbolt Android Development] mallen462:
+1 people who complain annoy the **** out of me
[Thunderbolt Android Development] SUB-dawg:
OUTPUT: SEM08G

RUNNING: cm7 with a froyo radio
[Thunderbolt Android Development] -Gilgamesh-:
Output: SEM08G with GB Rom.

Question: My understanding is that the general theory at this point is a hardware issue. If that is the case, couldn't this easily start happening on any ROM, not not GB roms?
[Thunderbolt Android Development] Franzie3:
Seriously...if you want to offer an opinion, fine...i'm sure all the dev's would like to hear it, just have some backing on it....

but if your gonn keep complangin....go get an i*hone
[Thunderbolt Android Development] Immolate:
Now I agree that the devs are worthy of our respect and support, and that those of us who can afford it should send a little something their way when we can to take care of them while they're taking care of us. I also get that a lot of us feel a strong impulse to defend them when we fee they are under attack.

I think it is also important to be judicious in our defense. The developers don't need a bunch of sycophants or yes-men to protect them from scrutiny. Admittedly, most of us here aren't developers and don't understand half of the magic these guys do, but we all have brains and experiences that make our perspectives valuable. Our devs need our opinions and observations to keep them grounded and provide them with inspiration. Even a total newb can ask a question or spark an idea that leads to a solution.

So what exactly am I saying? I'm saying that we need an environment where people aren't afraid to ask questions, even challenging ones, for fear of being castigated by everyone on the forum. I know there will always be a few who will reflexively try to protect the devs, whether they need it or not, and there isn't much we can about them. It's the regular Joes I'm concerned about, guys like you and me. We need to sort the asshole posts from the worthy questions and opinions, and give people the benefit of the doubt when we're not sure.

That doesn't mean we should be tolerant with people who spam their favorite conspiracy theories based on whacked-out illogic that has been disproved or hostile asshats whose only purpose is to beat up the developers and who only serve to demotivate them. There are some genuine bad guys here and they should be dealt with as they deserve.

Developers aren't delicate flowers. They can handle themselves in the arena of debate. They're good at it usually and all of ours seem to be excellent at it.
[Thunderbolt Android Development] fooshack:
bricking - reboots

Does anyone suspect the bricking is kernel/voltage related? Why is the radio suspect? I ran Gingeritis VIII for a week with no problems. Installed Gingeritis IX and ran it for a couple days with no freeze up problems or reboots and then went into the terminal emulator and changed the default settings of the kernel with the "speedtweak.sh" script and that is when my problems started. When I first looked at my settings it said I was running in "safe mode" and using "interactiveX" for a governor. I have no idea how it got set to "safe mode" as it was not 1 of the options, but as soon as I changed it to one of the other options I started getting freeze-ups and reboots, regardless if I changed the setting to something else. I had just enough time to make 1 change and the phone would lock up and reboot. Went back to froyo......imo GB sucks anyway.....don't see what the big deal is.....loving ThunderRom....smooth, and quick settings are quicker....you don't have to drag down a screen, click on a tab and then make your selection....seems like GB is moving backwards to me....like going from Windows7 to Vista..
[Thunderbolt Android Development] biggiephat:
no one bricked person has posted yet....cmon we wanna see!
[Thunderbolt Android Development] gregnice37:
SEM08G

Not Bricked, Running Bamf Stripped 1.1, was using Bamf GingerRemix 2.0 until I reverted last night
[Thunderbolt Android Development] chingy51o:
# cat /sys/class/block/mmcblk0/device/name

SEM08G

Not Bricked Running Gingeritis
[Thunderbolt Android Development] alexdw369:
Output: SEM08G

Status: Non-bricked, running BAMF 2.0 Beta 4.1 :D
[Thunderbolt Android Development] Stevez48:
Output: SEM08G

Non-bricked Currently running Froyo (Das BAMF 1.7) Was running BAMF 2.0 beta 5
[Thunderbolt Android Development] Taykiin:
**SEM08G - Not Bricked**

***Reverted to Bamf Remix 1.6.3 Froyo from Bamf GB***
[Thunderbolt Android Development] :
SEM08G - Not Bricked
[Thunderbolt Android Development] lanceman5000:
Output: SEM08G

Status: Nonbricked

Currently running VirusROM. Dabbled in BAMF 2.0, GingerBean, & Liquid Gingersense.
[Thunderbolt Android Development] AddisG:
SEM08G

Not bricked, and still on Gingeritis.
[Thunderbolt Android Development] jaysckap:
SEM08G

Non Bricked
[Thunderbolt Android Development] djbeanpole:
I'd like to hear Adrynalyne's (and others) theories about this! :)
[Thunderbolt Android Development] inspeckta_dek:
Cat/sys/class/block/mmcblk0/device/name: not found

Not bricked reverted back to froyo
[Thunderbolt Android Development] doug piston:
SEM08G

Not bricked
[Thunderbolt Android Development] will9512:
SEM08G

not bricked
[Thunderbolt Android Development] thejondude:
u need a space Cat /sys/class/block/mmcblk0/device/name not

Cat/sys/class/block/mmcblk0/device/name
[Thunderbolt Android Development] Kroaker:
SEM08G

Mine was bricked, but fixed with battery replacement. Currently running Froyo, BAMF 1.6.3.
[Thunderbolt Android Development] cowboys4life22:
Currently running BAMF 2.0-5 gingerbread leak radio

SEM08G is what is displayed

non-brick running perfect
[Thunderbolt Android Development] inspeckta_dek:
Thanks SEM08G
[Thunderbolt Android Development] jcase:
Then it wasn't bricked

Brick == not fixable by ordinary means
[Thunderbolt Android Development] :
Defintion of brick:

Rebooting in normal mode, as well as recovery, and RUU does not fix the issue.
[Thunderbolt Android Development] Franzie3:
yes i do agree with you...i am by no means a dev of any sorts...i do work on some of my own minor mods but am no way near any talent level these guys do...

I've asked my questions and thrown my theories out there (which i thought sounded legit) and most of the time they are answered with a logical explanation of why or why not...and i agree, mostly because i can only offer a theory without solid evidence...but i just like to get it off my chest to see if it helps, not to talk down someone else idea who has far more experience then I do.

on that note...everyone enjoy the holiday weekend
[Thunderbolt Android Development] patdroid1:
Very well articulated, I hope people on both sides of the fence take the time to read.
[Thunderbolt Android Development] Immolate:
To the extent that overclocking problems related to heat, I would expect those problems to abate temporarily if the phone is given time to cool, unless the heat actually causes physical damage. I would expect errors due to physical damage to be variable from phone to phone, although that might not be the case if there is a weak link the the hardware that is a lot more vulnerable to heat than the others.

But mostly, I expect that the ROM, Radio and kernels in use are standard questions being asked when a brick is discovered, along with the state of overclocking. The fact that all phones were on a GB radio is indicative, if not conclusive. But as you are probably aware, there have been a flurry of kernels in use on the various GB ROMs. It would be very difficult to isolate kernel issues beyond noting that, say, all kernels on bricked phones were from Imo or some other kernel developer. If it were as easy as finding a commonality (other than the GB radio) among the obvious properties, they'd have found it right away.

Is it possible that they are focusing too much on the radio because of the mysteries it holds along with the evidence of all bricked phones being on the GB radio? Of course, and it's good for other avenues to be explored. But after spending eight years resolving technical problems for a large corporation, I know that once the experts get their teeth in a theory, they'll follow it to hell and back, usually until it is proved or disproved, before spending much mental capital on pursuing other possibilities, unless they are re-tasked by someone they consider to be a better expert.
[Thunderbolt Android Development] jcase:
Many devs (me obviously) don't care if we offend others, and the "yes-men" really don't matter to us. Don't get me wrong, the "Thank Yous" are great, but pretty much entirely agree with your post.

Issue with this person, was his theory was illogical, had no backing, had nothing to do with this and completely wrong.

With that said, do your own research, trust who you believe you should.
[Thunderbolt Android Development] TMYINC:
Anytime you load a Rom with Netflix support you will get this email. The build.prop has to be modified to support the Netflix app which means "Nexus S" will be added to some parts. Alot of people are adding this support to their roms so I do not think this would cause any of the bricking issues. Just my thought though.
[Thunderbolt Android Development] jaysckap:
I have Netflix on my tbolt 2.3.4, incredible 2.3.4 & nook 3.0 and have never gotten that email

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] Immolate:
No man is an island, but this is a philosophy I can warm to. In the end, after all the arm-flapping and yelling and crying are over, it is you, your phone, and your judgement. Nobody will accompany you to the store with your smoking brick.
[Thunderbolt Android Development] jcase:
Build prop was edited with the nexus s fingerprint, to allow 2.3.4 compatible apps.

Sent from my Verizon Samsung Fascinated II
[Thunderbolt Android Development] TMYINC:
Well I was a little off lol. Thanks for the clarification.
[Thunderbolt Android Development] crackedvenom2:
Can we stop with the drama please? This is a thread to try and solve a problem.

Ps. I am also a test subject. If I brick ill get ahold of you jcase.

Sent from my hopefully not soon to be bricked Thunderbolt
[Thunderbolt Android Development] KDKobes:
Reboots were caused from over-clock past 1024Mhz.....freezes were caused from too low of an under-volt. AGAIN OBVIOUSLY JUST MY OPIONION.
[Thunderbolt Android Development] spursrchamps2007:
My phone had the same info as everyone else, and like a few others I'm loading the GB on it now we'll see what happens.
[Thunderbolt Android Development] fooshack:
I was able to change the setting to every available option which and still got the reboots and freeze ups in terminal emulator, so something doesn't make sense? How do you even set Imoseyon's kernels to safemode? Is there a kernel written that will not allow an over/under clock, or is that what safemode does? Does it limit maximum math requests to CPU thereby preventing overheating?

foos
[Thunderbolt Android Development] Tbolt101:
Non Bricked Htc Thunderbolt running BAMF GB

# cat /sys/class/block/mmcblk0/device/name

cat /sys/class/block/mmcblk0/device/name

SEM08G :cool:
[Thunderbolt Android Development] Morder Chemiker:
Like everyone else I'm getting SEM08G, currently running BAMF remix 1.6., non-bricked
[Thunderbolt Android Development] kdb424:
Checking in, still on GB leak and not a brick (SEM08G as stated before)

I'll keep you informed!
[Thunderbolt Android Development] jcase:
Wondering if the bricks were the first batch, or an early one (mine has a manufacture date of early feb). The other devices getting this issue seem to date from late last year, and were relatively small batches.
[Thunderbolt Android Development] onyx_64:
Hmm.. sounds like you have a sensitive processor that doesnt like to be overclocked! Someone correct me if i am wrong, but safe mode is nothing but normal mode, except that the max freq is capped at 1024MHz. Pretty much the config the phone came with. If you have ur freq-Volt values when you were in safe mode, you can verify it with 'normal' mode to see if I am right. Just change your max-freq cap to 1024 and you should be okay.

EDIT: This post is best asked in Imoseyon's kernel thread since you've been using that..
[Thunderbolt Android Development] bobtheelf:
Where does one check the manufacture date?
[Thunderbolt Android Development] CodedChaos:
Output: SEM08G

Running Froyo, mine is stable in recovery but shuts down moments after booting into android.
[Thunderbolt Android Development] jaysckap:
inside battery cover and I got january
[Thunderbolt Android Development] KDKobes:
......December for me....been running fine since release under my setup.....seems I have that batch.....not to bash the theory
[Thunderbolt Android Development] major_works:
Maybe that just tells you when the battery cover was made? It's not clear that it applies to the whole phone.
[Thunderbolt Android Development] azturbomini:
I have DT10-12-30 So that would be Dec 30th 2010 right?

Shot from my BAMFing Gingerbreaded (Rom "O" Death) T-Bolt
[Thunderbolt Android Development] theryanguy:
+eleventybillion

Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
[Thunderbolt Android Development] gsxraddict:
Looks like mine has a few dates on it either way all are January.
[Thunderbolt Android Development] gsxraddict:
Or the Rom o death hasn't stuck yet :) just kidding don't wish that on anyone.
[Thunderbolt Android Development] zapote21:
Now back on das bamf 2.0b5 for a couple of days... NO issues whatsoever...

All is still running smooth, no reboots, no heat, no anything...
[Thunderbolt Android Development] Busphan:
There's also a date on the phone. All my battery cover dates are Jan 2011, but the one on the phone is 30 Dec 2010.
[Thunderbolt Android Development] :
SEM08G

Not Bricked
[Thunderbolt Android Development] jaysckap:
Same here as far as both dates
[Thunderbolt Android Development] currensy:
Need to meet some friends outside XDA
[Thunderbolt Android Development] -Gilgamesh-:
I have a thought. On my TB, running both the BAMF rom and Gingeritis, when charges, it charges incrediblely slow. Like, maybe 5~10% per hour, even on a rapid wall charger. (When it would previously charge from stone dead to 100% in well less than an hour.)

What the hell could it be doing with all that extra energy? Could it possibly be frying one of the internal boards or chips due to improper power handling?
[Thunderbolt Android Development] techspecs:
Unless you've measured the current draw in both scenarios, you don't know that it's dealing with "extra" in the slow charge scenario.

./adb signature
[Thunderbolt Android Development] -Gilgamesh-:
Well, I am no electrical engineer, but I would imagine a wall charger would output a constant voltage/wattage/etc regardless of phone, rom, etc. Could be wrong tho.
[Thunderbolt Android Development] Character Zero:
Voltage is applied but current is drawn. So even though a wall charger can supply 2 amps or whatever, the load has to draw that current. So based on the resistance that the phone is using as it's load it can draw different amounts of current. Something like that.
[Thunderbolt Android Development] -Gilgamesh-:
Ah, well, either way, there is something that isnt right about the charging. It sat on the charger from about 4:45 to 7:45 and went from around 17% to about 45%, and then from 7:45 to 8:30 it went from 45%ish to 97%. That cant be right. Donno if it's in any way related to the bricking, but there def is a problem there.
[Thunderbolt Android Development] strongergravity:
Output: SEM08G

Device: non-bricked froyo
[Thunderbolt Android Development] Asmodeus6:
Mine did the same thing. It was annoying as can be. When I flashed back to Froyo on LTS (see sig) the charging BS stopped. I know they discussed it, and the cause of it in a few of the GB threads. I think it is kernel related. (Could be wrong)
[Thunderbolt Android Development] kazuma5401:
Day 4......

ROM of Death running great. Heats up while watching netflicks. Or while doing a long haul of several processes. No random reboots or severe hicups.

Although yesterday after missing a call I picked up a voice mail. Received it. Notification stayed in status after and would not leave.

Rebooted, came up fine but after a few seconds it rebooted itself again. Came back up. Ran laggy for a min, has been fine since.

Keep up the great work devs!!!!

HTC thunderbolt

Das bamf 2.0-5

*DEATH ROM*
[Thunderbolt Android Development] kevinshumway:
im bricked

ok so my phone has been great but now is in reboot mode. it gets to the home page and then reboots. I dont know how or what info you need. I have not flashed over it so ask away.

ps. try to make it so i can understand i dont know everyting.

also im on gingeritis
[Thunderbolt Android Development] kevinshumway:
when reading the problem it seems that people that are bricked reboot quickly but mine are not the same everytime. some times it will last 15 min before it reboots.
[Thunderbolt Android Development] doug piston:
http://irc.lc/andirc/thunderbolt/Android@@@

Click that link please. Change your screen name and we will see what someone can do for you.
[Thunderbolt Android Development] -Gilgamesh-:
Is it just rebooting randomly or fairly exact intervals? From what I've read the "GB Brick" usually reboots about 5 sec from initial power on. Thus, wouldn't have time to actually fully boot. Thus, the issue your having MAY not be related. Tho I'm not 100% sure.
[Thunderbolt Android Development] dc8783:
I been on the Gingeritis Rom since it came out and havent had any bricking problems.....Its running perfect for me.
[Thunderbolt Android Development] djbeanpole:
So I've been out of the loop for awhile since this issue has surfaced. Did anything come of it? Did we find someone who was bootlooping that had a different EMMC?

Have most reverted back to GB and have been ok?

Sorry if things have been discussed just wanted a little "update" on the situation ;)
[Thunderbolt Android Development] distortedloop:
No one bricked reported here with a different emmc, but several bricked mentioned who had flashed to an s-on state and they can't gather the needed information.

Multiple people reporting running on GB roms with no issues. (Personally, I think they're safe, but they don't seem to understand that for some of the bricks there was no warning before the problem occurred - a fine stable phone one minute was a rebooting brick the next if I understand the original issue correctly. Saying I've had no problems doesn't mean they won't if the original theory of the radio corrupting emmc is accurate.)

Jcase mentioned in this or the other thread a suspicion that the bricked phones might be original or early batch of builds as indicated by the manufacture dates on the devices all being in 2010.

I think that sums up the last couple of hundred posts well enough. LOL.
[Thunderbolt Android Development] djbeanpole:
Thank you, kind sir.
[Thunderbolt Android Development] TheLoonyRebel:
Code: SEM08G

Device: Currently running Das BAMF 1.7 with Froyo Radio (1.13.605.7)

In other words I got what most people have. Any idea if this means my TB is safe to use the leaked Gingerbread?
[Thunderbolt Android Development] bking_soda:
Hmmm... That's an interesting thought about early build phones. I got mine the day it released, first one activated in my area from what I understood at the time. This phone has had zero issues, froyo or gb. Been running gingeritis since it dropped and haven't had an issue. Did recently realize that anytime you restore or flash new gb roms, if you don't 3x wipe the phone WILL randomly reboot a few times until it settles. I really hope we do have a clear answer for the bricks one day, just to put everyones mind to rest.
[Thunderbolt Android Development] kdb424:
Almost thought I had a brick tonight on the GB ROM. I had it almost dead (battery vise) and then put it on the charger. It was charging, but after 20-30 seconds it would just shut off if I turned it on. Resolved the issue by plugging it into my PC. That makes no sense to me really as I know the charger was charging, but fixed it for now. Charging on the charger fine now (Every time I plug it in the PC, it turns on car mode no matter the ROM, stock, 2.3 leak, or cymod 7. Ideas?)
[Thunderbolt Android Development] iOSh8er:
Im down for the cause... Reverting back to GB and looking for a brick. ;)
[Thunderbolt Android Development] JWMayes:
I have been on GB for about 60hrs now since I switched back to it. No problems reported here.
[Thunderbolt Android Development] vypurr:
Damn. I wish I had seen this yesterday. I just handed my bricked phone to FedEx this morning!
[Thunderbolt Android Development] beavis1226:
Not sure if this has been mentioned but my phone's battery drained from 100% to 0 in about 90 minutes with no usage and then again it went from 39% to 0 with no usage. After that I pretty much said f*** it and went back to froyo. My two cents on the leak is stay away until somebody figures out what the deal is.
[Thunderbolt Android Development] 00negative:
Maybe someone else can put their 2 cents in but that almost sounds like a kernel overclock/undervolt setting that your phone doesn't like that is set up to be set at boot.

Doesn't sound like the bricking reboots that others have described.
[Thunderbolt Android Development] luigi1111:
I'm being somewhat of a test dummy as well: I've been back on GB for ~3.5 days, bootloop of death hasn't occurred yet.

If it bricks, it bricks. Plus, we'd then have confirmation on whether it is indeed an off-brand eMMC issue. (I have SEM08G)

Speaking of bricking, I need to do another Titanium backup...*runs off* :D
[Thunderbolt Android Development] jaysckap:
Witch emmc chip do you have?
[Thunderbolt Android Development] beavis1226:
I hadn't messed with any of those settings It was running at stock speed.
[Thunderbolt Android Development] luigi1111:
Same as everyone else. (added to other post)
[Thunderbolt Android Development] Sweeny Russ:
I don't know if this will be of any use, but here goes it....

In fear of bricking my phone I went from Bamf 2.0-5 (I had been running previous builds of Bamf GB up to that point) to a nandroid backup of Bamf RMX 1.6.3. When I restored the rom, I then flashed the stock OTA radio via bootloader. Worked fine and I plugged it in for my normal overnight charge, when I got up in the morning the device was warmer than usual. I reboot it and didn't pay attention to it till I got to work and noticed I was running in 1x data. Also severe battery drain (maybe searching for better connectivity). I then flashed stock rooted after 2 hrs. of letting it sit, battery pulls, and sim pulls. Tried different radios, no dice. After spending time with verizon try and get a replacement they said I must try a new sim first. On the way to the store, got out of work early, picked up 3g, then died. Turns out the sim was fried and I'm back up and running, rooted again, and running bamf stripped.

Anyway don't know if this helps at all or is a unique case. But I will wait a little while on GB.
[Thunderbolt Android Development] Franzie3:
I'm running back to GB....

im just like everyone else, same identical emmc, My phone looks liek ti was manufactured in feb 2011 and i have bought my bolt the day it dropped...so i'll risk it and try and help out