yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] lpd0084:
Output: SEM08G

Status: Nonbricked running cm7

Pity the noob as u were pitied in ur noobishness
[Thunderbolt Android Development] ska.t73:
Mine said "That's highly irregular Dave..." which is weird cause my name isn't even Dave...

:P

But seriously

SEM08G

not bricked and running DasBAMF 1.6.3 Remix....
[Thunderbolt Android Development] starscream86:
Output: SEM08G

non-bricked

ROM: Gingeritis v1.0 Beta VIII

Baseband:1.39.00.0430r, 0.01.69.0501r

Sense: 2.1

Android: 2.3.4

Kernel: imoseyon 2.5.4 test1

flashing back to Froyo now just to be safe :)
[Thunderbolt Android Development] zhp pilot:
Since everyone else is bashing you I'm going to throw in my support for you. I agree that it would be nice to know more details or even the theories being tossed around. I too would like to understand more about what's going on.

However, with that said, it is a

bad idea

to post stuff like that because so much misinformation gets spread around all forums because people don't take the time to read. Most forums I visit regularly are filled with total BS because someone thinks they know what they are talking about. They believe that everything they read on the interwebz must be true and they start spreading that information thinking they will be someone's savior.

So, I can appreciate what adryn and jcase are doing by holding back until a more conclusive result is derived.
[Thunderbolt Android Development] Dnakaman:
jinx! 10chars
[Thunderbolt Android Development] mkilla:
ughhhh duhhhh maybe i should go back to bed, i thought maybe the bricked phones were spitting out 10chars ... oh well nothing new then eh
[Thunderbolt Android Development] gatorhater73:
HA!!! +1 funny stuff...... I'm no dummy, but I'm certainly in the learning phase of this development stuff, and have no problems admitting when I'm stuck. The devs have been more than willing to help and have been seemingly happy to do so. I'd give them the benefit of the doubt, and if you have input, just contact them rather than openly flaming them for not asking for your help.
[Thunderbolt Android Development] jcase:
Problem:

Phones brick randomly

Symptoms:

Bootloops

mounting errors in recovery

Now you have as much solid info as I do.
[Thunderbolt Android Development] TheScribbler:
SEM08G

dasBAMF 1.7 now. Was on GB with the GB radio and went back using RUU from root method.
[Thunderbolt Android Development] jcase:
We think htc screwed up big time, but without info were not going to publicly accuse them, or get a bunch of people worked up over it.
[Thunderbolt Android Development] Chris Hansen:
I'm not asking "what is the problem?" I know they don't have a solid answer, but they could very simply state "after reviewing xxxxx, it seems the problem resides in hw/sw/fw/etc, but we need people to check for xxxxx to confirm." Sorry, but I'm not a sheep. I don't just do things because someone asked me to. I'd like to know what I'm doing and why. It helps prevent the problem from reoccurring in the future if it's preventable. It helps me to learn about what I'm doing. It helps me progress and advance myself, which would help me help others advance since I would be able to help them. But when I don't know what I'm doing or how I'm helping, none of that happens. And as I stated before, what if someone here already had the answer, but they were never asked the question?

I appreciate the work and dedication that devs put into their work. I don't appreciate them keeping everything a secret. You want my help, then tell me what I'm doing. I don't care if you don't have proof of the source of the issue, but if you have several theories as to what the problem is, we can keep an eye on those things and others could venture deeper into the problem instead of just waiting on a solution or their phone to fail. I don't think that's too much to ask.

What if this command were something that could potentially brick people's phones and they wanted to see if that's what was part of the problem? I know the command posted is not, but what if it were? What if the devs were frustrated and having a bad day and decided to use us as guinea pigs? Does that make it ok?

Regardless, there is still enough data here for non-bricked phones. This thread should be closed and a new one for only bricked phones should be opened.

Thrown by Zeus himself
[Thunderbolt Android Development] mkilla:
So in reality here is what we have....

We are waiting to see if a bricked phone gives a different response in the terminal compared to what all of ours is.

And if this is the case, we all can move back to 3.0 without worrying.

Considering we have had little or no bricks post, im thinking of moving back already, screw it. if it happens it happens... there will be new phone out by fall anyhow, lmao
[Thunderbolt Android Development] Shiftyshadee:
Really?

<10chars>
[Thunderbolt Android Development] noobfarm:
Output: SEM08G

Status: non-bricked

Was running BAMF 2.0-beta5 with the GB alpha radio. Now back on BAMF 1.7 FROYO
[Thunderbolt Android Development] fronc:
Or just don't do it. Would have saved you a bunch of time typing your response which lacked any form of utility, whatsoever.
[Thunderbolt Android Development] cfairchi:
+ 1 zillion as well

Ditto here, thanks a bunch Adrynalyne and all the others working on this problem!
[Thunderbolt Android Development] happimeal:
Would just like to throw in that I have seen Jcase and Adrynalyne help people whenever they can. They have the highest thank meters I have seen, which when considered all together with there contibutions to this community and the fact they do it for free, I for one appreciate there hard work and do not think they believe they are above anyone, or that they are trying to be secret.

ZHP Pilot made an excellent point, to throw out a bunch of theories just tends to spread/create more theories that are usually irrellevant.

Look at the BAMF threads, hundreds of posts and thank you's, Jcase's easier rooting methods, the ability to even have the priveledge to try leaked alpha GB roms and radio's.

There contributions are substantial.

I also am curious as to there theories, and im sure when they have some kind of proof to substantiate them, they will share.

Jcase, Adrynalyne, thanks for your hard work and your commitment to help solve this problem, you do it all for free and im sure I can speak for 99% of us when we I say your work is appreciated.
[Thunderbolt Android Development] adrynalyne:
So we have run into a problem with reading bricked devices. If you are bricked, please, please, please! do not run the stock RUU until we have attempted to read the emmc name. If you are s-on, we are stuck.
[Thunderbolt Android Development] jaysckap:
Once again I just gotta say Thank You
[Thunderbolt Android Development] bking_soda:
Okay... So I've stayed quiet so far watching this very closely. First of all, a VERY big thank you to the devs working to find the cause of this. Second... I'm at a loss with all the arguing and flaming going on throughout these threads. We all have one thing in common, we own a tbolt. I would think this would go way easier and faster if more people worked together to try and find a solution instead of wasting thread space acting like ass clowns. Again... Thank you jcase and adrynaline. Your hard work is appreciated. I do plan on getting the numbers from my girls phone when she gets off work. Hope its the same but would be interesting to see if its different. She has never had GB on her phone.
[Thunderbolt Android Development] tedkord:
I've not run any of the GB ROMs or radios, currently on the DasBAMF 1.7 (1.63 until yesterday). I'm not sure if my info is useful since I've never run GB, but here it is: SEM08G

I haven't read the whole thread, but I didn't see any posts from bricked users. Have any been posted yet?
[Thunderbolt Android Development] techspecs:
It's 40 pages now... just saying. :D
[Thunderbolt Android Development] inzandity:
Should be posted in the OP of this thread and the MR1 thread IMO. I think this would be peoples first instinct before running to the IRC channel...
[Thunderbolt Android Development] psicrest:
This is a little bit off topic, but this is my feeling when i got stuck in a bootloop and figured i need to replaced the battery and everything went well ---> http://www.youtube.com/watch?v=xos2MnVxe-c
[Thunderbolt Android Development] ska.t73:
There have been a couple but from what Adryen just posted it seems they are having problems running the command from the bricked phones that they have found.
[Thunderbolt Android Development] g00s3y:
Really... Really... REALLLLLLLLLY :mad:

I believe this is the dumbest thing ever posted on xda...
[Thunderbolt Android Development] mmobley:
Better catch it!

Sorry had to be done.

Happy times! Thanks for all your free computer engineering time guys.

"Software publishers 87,450$ annually". <== Average

"Computer systems design and related services 84,660$ annually". <== Average

Just to show you what your getting from these guys.

So anyone that has a problem helping these two fine gentleman. I'll tea bag your drum set.
[Thunderbolt Android Development] KDKobes:
Well I guess if my phone bricks I will be the first to keep it and try to help..still running liquid gingersense for now. LOL...hope I don't have an issue though.

Lots of frustration going on though damn its ridiculous.
[Thunderbolt Android Development] happimeal:
Does the problem with reading the bricked phones seem to stem from not having enough time to get command entered?
[Thunderbolt Android Development] mallen462:
I appreciate all your hard work and efforts you put in, I think a lot of people on this thread may be confused as to what info you were looking this regarding ginger radio only because that's what's causing bricked phones start a new thread for general discussion
[Thunderbolt Android Development] xEVILFREDx:
Like the sig about brick thunderbolts.
[Thunderbolt Android Development] Wkd1:
I just went back to GB Bamf 2.0-5. Before flashing back to froyo I did have one serious overheating issue followed by resetting only by pulling the battery. I'm willing to take the chance with this for now, and should it brick, I'll post my results.

Output: SEM08G
[Thunderbolt Android Development] periclytes:
SEM08G

Not Bricked. Running Das BAMF 1.7
[Thunderbolt Android Development] kdb424:
After work I'm back to 2.3 even though I can't afford a brick. Just bought $300 in a liquid cooling system for my PC, so it better not brick. If it does I'll put 100% effort in keepin you not bricked. *crosses fingers*
[Thunderbolt Android Development] tats_06:
Adrynalyne, but why would people try to update/change radios with s-on? Isn't that already user error? Or does it change itself to s-on somewhere in the process?
[Thunderbolt Android Development] Shiftyshadee:
If you flash the RUU it puts you back to s-on
[Thunderbolt Android Development] Asmodeus6:
Ran gingeritis for a few days.

Flashed back to froyo. Got pissed off... Flashed back to GB...

Flashed a medley of Froyo radios, went back to Froyo to wait it out.

Heh... I even flashed the GB radio twice by accident. (serious)

SEM08G

Non-brick

*On a side note. I have no idea why j case or adrenylyne puts up with 40 pages of this bull****. Do what you're told, or stfu and make your own thread to ***** about what they are asking to be done. Between the whining, conspiracy theories, and accusations I'm surprised these guys haven't found a way to ota brick your devices at will. I would have. Just to shut you up.
[Thunderbolt Android Development] gsxraddict:
+1 totally agree this thread would be 20 pages if you eliminated the bs.
[Thunderbolt Android Development] dlongb13:
Isn't that (and this) adding to the useless crap itself?
[Thunderbolt Android Development] KDKobes:
Reminds me of the lady years ago that spilled her coffee in her lap in the car and went on to sue McDonalds because they made it....society is f'd anymore.
[Thunderbolt Android Development] gsxraddict:
Yep but if enough say stfu maybe people will get the hint and keep it on point.
[Thunderbolt Android Development] crackedvenom2:
So we have like 5-10 bricks out off 500?

Also it doesn't seen like they have much to say so when they do I'm sure we will know
[Thunderbolt Android Development] tornadog:
too bad I cant give my feedback, just shipped out my bricked device back to verizon this morning. The replacement is running fine, of course its unrooted. Will give it some so all this drama settles down.
[Thunderbolt Android Development] anothen:
Slightly off topic

A friend of mine just unknowingly bricked his phone after having it for 20 minutes. Not by doing anything with rooting/flashing... It looks like his phone started a Auto-Ota while he was charging the phone (he claims he didn't select an OTA or anything). When he went to turn the screen on, it was in the common green arrow cirle update looking black screen. His bright idea was "what the heck is this screen?!" so he decided to pull the battery. He then came running to me after his phone is stuck at that screen lol - I guess I shouldn't be laughing but it lightens the mood around here :D (and yes, I tried to help the poor guy but the phone is not responding to any adb commands... pretty bad)
[Thunderbolt Android Development] tats_06:
But...we have an RUU for gb...and people shouldn't be flashing it unless they don't want root, am I correct? If they flash the RUU, then they should go thru the root process again. :confused:
[Thunderbolt Android Development] BurnOne77:
http://youtu.be/j5mJQGMqJvw
[Thunderbolt Android Development] will9512:
http://i.imgur.com/qlRu3.gif
[Thunderbolt Android Development] jcase:
No we don't have an RUU for GB, we have a pre-build zip
[Thunderbolt Android Development] kdb424:
Alright guys, it's time to forgive them for one mistake. Bashing done please. If you feel the need to bash, do so on me and via PM. Now lets get cracking on why this is happening. Flashing GB back and if I brick I'll help out a ton. Can't afford it, but the devs have done more than I can I ever can, so call this my contribution to pay them back.
[Thunderbolt Android Development] Andrew C:
Output: SEM08G

Status: Nonbricked, Das BAMF 1.6.3
[Thunderbolt Android Development] bootywarrior321:
how did u get a replacement if u were rooted? i thought verizon was against root?
[Thunderbolt Android Development] nepperz:
Bricked phone, unless they take the time to actually go bit by bit through the phone... they wont know
[Thunderbolt Android Development] bowtieduece:
Output: SEM08G

Status: Nonbricked, running Froyo.
[Thunderbolt Android Development] hackercity:
Output - SEM08G

Nonbricked -Running - Froyo
[Thunderbolt Android Development] 00negative:
What is it?
[Thunderbolt Android Development] happimeal:
Wonder if the replacement companies or HTC have a way to interface with the bricked phones and re-flash them, or if they just toss them.
[Thunderbolt Android Development] jcase:
Refurb shops will pull the suspected bad part and test them, replace if possible.
[Thunderbolt Android Development] sonofskywalker3:
Lupus.... read the picture.
[Thunderbolt Android Development] kazuma5401:
I'm flashing back. If I brick, jcase you will have a test subject. I'll bite the bullet, I have no insurance, and I'm not under warenty.

Let's do this!

HTC thunderbolt

Das bamf 2.0-5 * Rom of Death *
[Thunderbolt Android Development] 00negative:
Ah... Hilarious... No really it was
[Thunderbolt Android Development] kazuma5401:
Lol my paypal I'd is kazuma5401@yahoo.com

Donations welcome and thanks for the support!

*my wallet is about to get hurt* Lmao

HTC thunderbolt

Das bamf 2.0-5 * Rom of Death *
[Thunderbolt Android Development] kdb424:
*sigh* We don't have an answer. They were joking.
[Thunderbolt Android Development] pulser_g2:
Do we seriously have someone here saying the command

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

is dangerous?

Let's have a little lecture on what this does.

cat is the linux command to return the contents of a file. So that's READING from a file.

The remainder of the command has no spaces in it, so is one term. Most people will recognise this as being a type of path to something in the filesystem.

Therefore, this is reading from an item in the filesystem. If might not be a file as such (it's not), but it's a system flag that you can read. The key word being READ.

cat is a perfectly safe command unless its output is being piped.
[Thunderbolt Android Development] EvilDobe:
Cats are dangerous animals. They meow, scratch, and hiss. This is all very unfriendly.

Also:

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

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

SEM08G

#

Status: Running
[Thunderbolt Android Development] onsht1kll:
No no no .. even worse is ..

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

Now that is dangerous!
[Thunderbolt Android Development] crackedvenom2:
You guys brought some fun into this thread.
[Thunderbolt Android Development] tats_06:
Jcase, I guess what I am trying to say is that I believe that some, if not most bricks were due to user error.
[Thunderbolt Android Development] Immolate:
True, but if you give them a pipe, they mellow. Fact.

Wait he said they're more dangerous if they're piped. Dude I'm confused.

.... oh and SEM08G, and my phone is not bricked, though I think I might be.
[Thunderbolt Android Development] joshnichols189:
This is incorrect.
[Thunderbolt Android Development] JaydenR:
Proof? How do you know they did not over-clock to 1.9 and fried the chip overnight while it charged. I recall at least one case of someone saying when he looked at his phone that had charged overnight it was boot loop brick.
[Thunderbolt Android Development] patalo:
SEM08G

Nonbrick, Gingerbread(Gingeritis)
[Thunderbolt Android Development] patalo:
whenever people flashed gingerbread how many agreed to send in information to htc?
[Thunderbolt Android Development] Magnus_CA:
+1

10char....
[Thunderbolt Android Development] mzimand:
SEM08G

Non-Bricked. I did switch back to Froyo after being on Gingerbread

I did have one strange thing happen while on GB. The second day on GB my phone rebooted and my screen was unresponsive and all the icons were gone. I tried calling it and the phone would ring but the screen was dead so I could not answer the call. I tried everything from flashing the kernel to wiping cache. But each time the phone would reboot and the screen was dead and the icons still gone. I had to reinstall the ROM to get back up and running. I was running Bamf 2.0 with Imos Kernel OC 1.4

My phone was running perfectly when this happened I never even had a reboot on GB until this happened. It is what made me decide to revert back to Froyo once jcase made his post.
[Thunderbolt Android Development] Asmodeus6:
I did not.
[Thunderbolt Android Development] Makaveli1490:
I didn't. When I first seen it, I was like wtf is this
[Thunderbolt Android Development] skaterpunk0187:
I was having this issue on froyo too, I could feel it in my pocket getting warm then I started trying new roms and have not noticed it since. didn't notice on gingeritis
[Thunderbolt Android Development] SKumar26:
SEM08G

Not Bricked

Went from PlainJane > Gingeritis > MR1 > Das BAMF 1.7
[Thunderbolt Android Development] Jaxidian:
Add me to the group flashing back to GB for posterity's sake. I can [unpleasantly] suffer a phone outage over the next week or so.

(ADB command was identical to everybody else)
[Thunderbolt Android Development] 00negative:
I might too.

To quote Rocky 4... If it dies... It dies
[Thunderbolt Android Development] dpdurst:
SEM08G

Not Bricked
[Thunderbolt Android Development] albotz21:
im in! im goining back to ginger...ginger
[Thunderbolt Android Development] gabeevans88:
SEM086

Froyo, Bamf, Non-Bricked
[Thunderbolt Android Development] stanlalee:
SEM08G

not bricked. froyo to gingerbread and curently back to froyo and pissed. cant wait to flash a brick free gb radio and throw the gb nand back up
[Thunderbolt Android Development] pitchblack86:
Output: SEM08G

Status: Nonbricked. on bamf 1.6.3, previously bamf 2.0-5 and bamf gingerremix
[Thunderbolt Android Development] skeeter123:
Have backup, will stay BAMF'd...until...I change my mind..

Got an old Moto flip Ve5 (or some such beasty) if the TB goes north on me. Been w/BAMF long time. Yes, me luv you long time..

SEM08G for me.

If it bricks, we have a cadaver....GBdaver...sorry....I need help...

...
[Thunderbolt Android Development] mallen462:
Agreed but again what I would like to see is results only from gingerbread we should start a new thread for general discussion
[Thunderbolt Android Development] Bern612:
I'm on Sem08g. Before I flashed mine back mine became unresponsive also. I could see the wall paper and when I hit the home key it would show my home screen fot a second then lock up again. i was getting high temps also. And the worse part was my my phone reboot and corrupted 32g sd card. Recovered most of files except cwr backups. I had just chalked it up to user screw up. But you know how this works.....a sniffle.fever lost of appetite and we all have swine flu. Just putting this out there. Maybe just maybe mine was warning me. I am about to go back to gb as a test dummy after I find my i920 for a back up
[Thunderbolt Android Development] DROIDNP:
Output: SEM08G

Non-bricked Currently running Froyo (Das BAMF 1.6.3) Was running BAMF 2.0 beta 5
[Thunderbolt Android Development] inspeckta_dek:
My phone went crazy for a minute. 4 random reboots so I did a factory reset. I notice that the 4G goes on n off to 3g even though the 4G has full signal.

I'm on froyo bamf 1.7 and I got the same result from the adb command.
[Thunderbolt Android Development] mkilla:
How can you tell it has a full signal?
[Thunderbolt Android Development] inspeckta_dek:
Bamf 1.7 has the 6 bar signal icon. It was steady 6 ,5
[Thunderbolt Android Development] mkilla:
Those bars are for voice signal strength only I believe.
[Thunderbolt Android Development] _AI_:
Yes they are.
[Thunderbolt Android Development] allareconnected:
SEM08G

Running BAMF 1.7 - Was running and severely miss GB!
[Thunderbolt Android Development] MadWicket:
SEM08G

Running BAMF 2.0 REMIX
[Thunderbolt Android Development] Immolate:
Went back to Gingerbread today. The Mayans called and said they'd cancelled next year's end of the world in celebration. They said they could not destroy a planet that had GingerBAMF in it.

Don't think of it as taking a risk. Think of it as performing a valuable service for your community. In fact, it may be your DUTY to go back to GB.

As Conan's girlfriend said, "do you want to live forever?"
[Thunderbolt Android Development] EEdaesung:
Wasn't that the terminator?

^_^_^
[Thunderbolt Android Development] Immolate:
Are you saying the terminator was Conan's girlfriend? Kinky.
[Thunderbolt Android Development] Turb0wned:
Im sorry, new to this... How do I do this on a mac?
[Thunderbolt Android Development] Smok3d:
Or you can open Terminal Emulator on your phone and type in that code, works the same.
[Thunderbolt Android Development] chkmate:
SEM08G non-brick

Bamf Remix 1.6.3

Couldn't read anymore after 20 pages. Is there even 1 brick in here? I'm tempted to run GB till I brick just to see.
[Thunderbolt Android Development] trunklips:
Output: SEM08G

Status: Nonbricked

Running: BAMF 1.7

I miss 2.0-5
[Thunderbolt Android Development] jmaher1023:
So I typed this command in my terminal emulator as root and all I get back is "IntxLNKtoolbox: not found"

I'm running BAMF GB remix
[Thunderbolt Android Development] onsht1kll:
Actually i think that was Starship Troopers lol
[Thunderbolt Android Development] two_cents:
my friends phone shuts off and reboots constantly... but its the same number as everyone else... no clue what may be causeing the bricking of the phones but mine is running flawless on gingeritis and I'm keeping it that way i'll pay the 90 bucks for a new phone if I have to
[Thunderbolt Android Development] jaysckap:
Sounds like a root issue is everything working correctly

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] k2trill:
Output: SEM08G

Status: Nonbricked

Running: BAMF 2.0-5 (see signature)
[Thunderbolt Android Development] gsxraddict:
I've only seen 2 so far.