yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] currensy:
How??? I forgot to delete the PG05IMG file that updated das bamf radio so i couldnt get into clockwork and had now way of deleting my PG05IMG file
[Thunderbolt Android Development] distortedloop:
They said in one of the first few posts that you only have ~2-3 seconds to run the command in adb, so it's definitely a small window, but adb access to the phone does come fairly early in the CWM process.

This is why you should do it from adb, so you have time to pre-load the commands and just hit enter, and you won't lose the results on a reboot.
[Thunderbolt Android Development] crackedvenom2:
Sd card reader or a laptop/computer that had those slots
[Thunderbolt Android Development] RobbyRob:
I think this is getting pointless.. I think there was just a few unlucky people who had hardware failures now we are all paranoid. Unless I missed it no one has supplied technical evidence for how this is happening... Are we going off some developer's gut feeling or what?

What I get from reading is that software is causing hardware failure... Well... Corrupt sectors on re-writable media can be replaced. If it is not corruption then there must be voltage or heating issues causing internal damage... I would like to see how people are coming to the conclusion that a radio is causing a REAL non fixable issue. If I missed it I am extremely sorry and would like to be corrected.
[Thunderbolt Android Development] capflya:
From terminal emulator only type in "cat /sys/class/block/mmcblk0/device/name"

This worked for me. I got same results as everybody else so far.
[Thunderbolt Android Development] currensy:
what i don't understand is why's the md5sum for the custom PG05IMG from xda is different from the one posted by android police...talking about rooting of course...xda and android police has the same method of rooting...the first PG05IMG image is the same and the exploits but the last one PG05IMG is different.
[Thunderbolt Android Development] PJnc284:
File might be different. The link on android police is probably the original exploit. MR1 has been pushed out since then and the root thread was updated with a custom RUU of MR1 instead of the custom factory firmware that it was shipped with
[Thunderbolt Android Development] funkybside:
I believe the purpose of this thread is to check the manufacturer of the eMMc chips. AFAIR, the chips most people have are manufactured by SanDisc. It is possible that the people who have experienced bootloop-bricks have phones that were manufactured with a different brand eMMC chip, one that could have poorer tolerances.

Knowing this information would provide us with a way to make an educated guess at who is at-risk for future bricking, and who may be safe to run the GB radios. Just an idea at this point...
[Thunderbolt Android Development] currensy:
ok i'm bout to root...if i dont respond i'm bricked
[Thunderbolt Android Development] funkybside:
Not in the context of this thread you aren't...unless of course you also flash a GB rom/radio and end up bootlooping...
[Thunderbolt Android Development] KDKobes:
You have missed something. They are unlucky though for sure. Not to out anyone, but to give a perfectly logically example DroidTh3ory was one who stayed on GB and was having absolutely NO ISSUES and then all of a sudden BAM phone rebooted itself and hasn't been able to get it running since. The voltage or heating issue is debunked as I don't think he had any heating issues at all, but it does seem to be when a large amount of internal memory is being used by the device and the memory gets low and forces a reboot, but doesn't return...

Please try to keep on topic though..this thread has become long enough. If you want to discuss it go HERE
[Thunderbolt Android Development] bamaredwingsfan:
Output: SEM08G

Status: Nonbricked

Reverted from Chingys gingeritius VIII back to BAMF 1.6.2remix.

I wiped data, cache, an dalvic 3times in recovery. restored a nandroid of bamf1.6.2 and then did a battery pull before booting out of recovery and then booted into hboot, an restored my last froyo radio that worked good. All is well so far.:rolleyes: I had ran the GB rom for about 4 or 5 days i guess.
[Thunderbolt Android Development] Zenak:
SEM08G - non bricked
[Thunderbolt Android Development] want a droid:
SEM08G, not bricked
[Thunderbolt Android Development] 00negative:
SEM08G

Still running

On the mr1 update rooted.
[Thunderbolt Android Development] Morkai Almandragon:
Same results as everyone else on friends stock updated phone that has reboot issues.
[Thunderbolt Android Development] psufan5:
Same results as everyone.. was on GB now back to froyo...

Does anyone have fastboot enabled that is bricked? I had major issues with fastboot trying to get the phone to start... could be a compounding factor?
[Thunderbolt Android Development] woodsptw:
BAMF 1.7

Was running BAMF 2.0-5; currently running 1.7

Not bricked.

SEM08G
[Thunderbolt Android Development] capflya:
Is he on a GB ROM/Radio? Or Froyo with one of the Froyo radios? You say stock updated so I'm assuming he's just rooted on Froyo with the updated froyo radio (1.13.605.7).
[Thunderbolt Android Development] Richpopski123:
I'm pretty sure " stock" means froyo. :p
[Thunderbolt Android Development] techspecs:
Not sure how valuable this is any more but...

SEM08G

Working fine, reverted to FROYO radio and BAMF_Remix 1.6.3
[Thunderbolt Android Development] 00negative:
Weird..That is exactly opposite of what I experienced..my idle battery drain was tons better on a gb sense Rom than it has been on froyo or on cm7
[Thunderbolt Android Development] tats_06:
Well, more posts like this and HTC might reconsider leaving bootloaders open. I firmly believe that if people brick their phone because they were rooting (which voids warranty), then they need to step up and take the loss and not go to vzw for a replacement. Urgh
[Thunderbolt Android Development] madroix:
I got the basic and normal

SEM08G

Running Bamf Remix 2.5 GB radio.
[Thunderbolt Android Development] azturbomini:
SEMO8G

Non bricked
[Thunderbolt Android Development] adrynalyne:
Responses like these are worthless. If you don't want to participate, then don't. We are looking for solid answers and without data, we cannot find them. You guys have NO idea what is going on behind the scenes. I have been helping jcase and do.
[Thunderbolt Android Development] RobbyRob:
So why don't you explain what is going on? So much for a open development community. I sit here everyday and read through stuff to better understand what I am looking at. And I notice you like to talk down to everyone on here that don't make a ROM. I'm not dumb by any means and would just like you guys to share with us why you need this data so we can understand also. You never know I could have some knowledge that could help, but being as your posts are superior to mine I guess we will never know.
[Thunderbolt Android Development] sammyboy405:
Reverted back to Froyo BAFM 1.6.3 2 days ago.. I hate Froyo My Phone randomly reboots all the time.

And the output was

SEM08G
[Thunderbolt Android Development] kurrupt_1:
ok I have a bricked TB hook up but device not seen in adb. Currently "FASTBOOT" is highlighted on the screen.

What next...............
[Thunderbolt Android Development] DizzyThermal:
Radio Information:

1.12.605.6 CDMA/LTE radio combo.

CDMA Radio version: 1.16.00.0223r

LTE radio version that came with 1.12.605.6

MD5 - A740031D09FC97D1B48FBEDFE73FDD24

ROM Information:

CyanogenMod-7.1.0-RC0-Thunderbolt-KANG (GRJ22)

5/17/11 - 02:28AM 2.3.4 Test1

Kernel Information:

Imoseyon's GB leanKernel: minimalistic kernel @ 1408 MHz

(2.6.35.13-imoseyon-2.5-hga8e22bdf1e24-dirty)

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

Output: SEM08G

Status: Nonbricked
[Thunderbolt Android Development] psufan5:
And boom goes the dynamite.

Seriously.. everyone is looking for some incredibly elaborate reason for this to be happening when not a SINGLE person has posted in this thread getting reboots...

Sounds to me like 10 out of the thousands of phones rooted are getting this issue.
[Thunderbolt Android Development] Araya213:
Changed my mind, spill it!
[Thunderbolt Android Development] erishasnobattery:
Hop in the IRC channel. Jcase or Adrynalyne can walk you through the steps to get the necessary data.
[Thunderbolt Android Development] tats_06:
Does the phone reboot in bootloader?
[Thunderbolt Android Development] :
Yeah kinda weird how there is not one person who has a bricked device now...
[Thunderbolt Android Development] patdroid1:
k so i got two "like new" replacement thunderbolts in front of me...

both not bricked-SEM08G

one i had run gingerbread on for a couple days, got tired of it running hot and having spotty 4g so switched back to froyo. a day later my microphone stopped working, only way i could talk to people was through bluetooth (yes i tried a data wipe...i even restored back to stock MR1...no dice). i assume it is coincidence but nonetheless that's what happened. recieved replacement phone and the bottom left corner of screen is peeling off the chassis so immediately called verizon and i will be receiving another phone this afternoon.

will report back the eemc# on that phone once i recieve

good luck guys
[Thunderbolt Android Development] funkybside:
from a few pages back...

Doesn't mean much until we see the device names for some bricked devices, but to me it seems plausable and worth checking out. I also don't think this would be the first time we've seen variance in hardware components used on a model...aren't there also two brands of LCD in these things?
[Thunderbolt Android Development] zhp pilot:
It's sad. And it all stems from most people not knowing a damn thing about what's going on or what they are actually doing/changing with the phone. Or not READING directions.
[Thunderbolt Android Development] erishasnobattery:
There were only a handful to begin with, and since this has been going on since Sunday, most were already replaced before this theory was postulated. Not everyone has a bin of spare phones around for testing.

As far as I'm concerned, 1 is enough for me to avoid the risk. $250 is a very expensive paperweight.
[Thunderbolt Android Development] Chris Hansen:
I hate to say it, but Rob has a point. You guys have already created mass hysteria without releasing ANY facts other than some phones have been bricked. You're continuing this panic by withholding information from the very people you have alerted. You don't need to share technical details, but one of the beauties of an open community is that it is very much like distributed computing. What if you guys were stuck at some point and one of us community members had the answer you were looking for? Are you guys too stubborn for that because you want the credit yourselves? I'd rather we fix the problem by working together than trying to hide all the info, then throw it back in people's faces because they don't know what's going on. That won't get us any further forward, and has actually literally moved us backward.
[Thunderbolt Android Development] adrynalyne:
You are abosulutely right. You interfereing with an investigation into a problem by insenuating that its a waste of time and is just some blind hunch from a developer should be met with happoiness, joy, and moar unicornz.

I only talk down to those who deserve it, and I think the majority of the forum would agree there. As for open development community? Its pretty open. I explain what I to anyone who asks me directly, and I see it. I post my GPL'ed source code. I will not, however, post inside conversations that are between two individuals just because you think I should. When findings are conclusive, THEN a statement will be made.

I am done though. I was trying to help, but if you guys don't want definitive answers or possibly a way to avoid bricks...

Fine...not my problem. Its not worth the crap like some people like you give me.
[Thunderbolt Android Development] kurrupt_1:
I need the irc info.........................please.
[Thunderbolt Android Development] RobbyRob:
I am sorry Officer Adrynalyne I will know my place and shut up and quit interfering with your investigation...
[Thunderbolt Android Development] LTL11:
After all the crap they have gotten for letting us know there may be a bricking issue with GB radio I would not share any information either.
[Thunderbolt Android Development] erishasnobattery:
+1

10Chars
[Thunderbolt Android Development] tats_06:
irc.andirc.net #thunderbolt
[Thunderbolt Android Development] erishasnobattery:
http://chat.andirc.net:9090/?channels=thunderbolt
[Thunderbolt Android Development] quepaso:
What kind of douchebag are you? You're just making people who are helping others more pissed off. Unbelievable.
[Thunderbolt Android Development] Tallica21:
Come into IRC in the OP

Andirc #thunderbolt
[Thunderbolt Android Development] :
http://chat.andirc.net

Channel: #thunderbolt
[Thunderbolt Android Development] mrbracht:
offensive, yes... making my point, very clear.. ;)
[Thunderbolt Android Development] JaydenR:
Could the bricks be related to people running their chips to 1.9 and frying them?
[Thunderbolt Android Development] Zalyia38:
I agree. What a freakin idgit!
[Thunderbolt Android Development] adrynalyne:
I would ASSume that the phone would become too unstable to run properly beforehand. We are looking at all avenues.
[Thunderbolt Android Development] KDKobes:
Actually they did come out and say late last night that they are going to keep them unlocked from here on out.
[Thunderbolt Android Development] JaydenR:
Also could a corrupt radio cause this? I mean a corrupt download. There were several radio downloads available.
[Thunderbolt Android Development] Dnakaman:
Translation:

Man you guys suck big ones! I hate you...

Oh, by the way, you think you could add that cool battery animation to the notification bar, since I have no idea how to do it myself?

LOL
[Thunderbolt Android Development] JaydenR:
I really don't know what I'm talking about I'm just bored :p
[Thunderbolt Android Development] georgepink:
Adrynalyne- Please understand that 'RobbyRob' does not speak for the rest of us. I know you do not see my name constantly on these forums because I can usually find my own answers and have NOT the knowledge to support others.

Anyway, I have seen your name Adrynalyne, linked to possibly HUNDREDS of posts that HAVE helped many or dare I say almost all in this community, so from the 'appreciative' ones....Thank you, and please don't give up on us for one persons ignorance.
[Thunderbolt Android Development] Zalyia38:
+1 zillion
[Thunderbolt Android Development] mikalem:
Output: SEM08G

Status: Non-bricked, running Gingeritis Beta VIII with imoseyon's 2.5.4test6 kernel in battery saver mode
[Thunderbolt Android Development] Shiftyshadee:
I can speak from personal experience. Adrynalyne and Doug Piston saved my Incredible.
[Thunderbolt Android Development] anothen:
yes, but usually that has very specific immediate results like not being able to turn the phone on period. (this is the case with most other phones.) In our case, the phones reported 'bricked' had been runnin fine for several days. That is not to say that something could not have triggered it after running the radio for a few days (most likely the case)
[Thunderbolt Android Development] swimminsurfer256:
Alright time has come.

IF YOU DON'T HAVE SOMETHING DIFFERENT FROM "SEM08G NONBRICKED" TO SAY DON'T SAY IT AT ALL
[Thunderbolt Android Development] RobbyRob:
I never claimed to know how to "add the cool battery animation to the task bar". I was simply wanting to know the details behind why they are collecting this information and I get blown up on. Holy S***. All I keep seeing is we are not releasing information to the public and then... Hey guys can you run this command in terminal and help us? I just wanted to know why I was running that... And someone explained it and I was good... I don't even know why the rude comments from Adrynalyne had to even come about...
[Thunderbolt Android Development] Morkai Almandragon:
Sir you are in direct violation of forum rules. They specifically say that until 40 pages of the same crap is posted, you may not interfere with said postings!
[Thunderbolt Android Development] Shiftyshadee:
Look guy, let them do their thing. They said when there is something found they'll tell us. Why is that not good enough?

...........and do you maybe think the "rude" comments were due to the fact that you were acting like a total a$$hat?

Signs point to yes.
[Thunderbolt Android Development] Chris Hansen:
The problem is we can't help troubleshoot when we have no information to go off of. First step of troubleshooting is identifying the problem. Since I don't have any problems, and nobody is telling me exactly what the issue is, I can't move on to the next steps of troubleshooting. I can't look for possible causes without knowing the root issue. Basically I'm being told "My computer doesn't work" or for the gear heads "My car doesn't work" and being given no further information. That's not enough information to go off of.
[Thunderbolt Android Development] swimminsurfer256:
I would gladly take a ban or whatever as long as I don't have to read another SEM08G NONBRICKED!!!!!!!!!!!!!!!!!! ;)
[Thunderbolt Android Development] jmotyka:
SEM08G

Not Bricked

Das BAMF 1.6

imoseyon kernel,

swap enabled
[Thunderbolt Android Development] swimminsurfer256:
I will kill you.
[Thunderbolt Android Development] ska.t73:
Right now all the information they need to give out is in this thread. Jcase is not going to say it is something until they have solid proof. Right now the theory is that the eMMc in the bricked devices is off brand. However they can't prove that until they can find out what a bricked device is running.

A couple of people have posted now with bricked devices, however they are going to need help from IRC to run the command.

Now if it is off brand eMMc that is going to be a pretty big deal and means HTC is doing something really stupid. Do you think Jcase should level that accusation with out facts?

I understand that people want to know, but the information that we have available as to what they think is happening is in this thread if you look for it.
[Thunderbolt Android Development] Shiftyshadee:
Truth

<10chars>
[Thunderbolt Android Development] xEVILFREDx:
Jcase, I don't know if my device is going through a semi brick but I never in Froyo leak radio had issues of rebooting. Now when I downgraded from GB to Froyo my deivce is doing it a lot. Other issues I have been expercing are hot phone "48.7 C = 119.66 ºF", Bluetooth error " connection with my device shows as still connected when its off. This happens with my Jawbone , and my car built in bluettoth" , Radio issues "3G and 4G will not be found in a area that has towers all over Orlando and I use to get 4G @ 15-20 MB down" and lastly phone will reboot and all data on device will be blank" for example txt messages, and icons on htc sense missing like a brand new flash"

Once I get home tonight I will run the command on this thread to see what I get. Unfortunally I am at work right now.

Thanks.
[Thunderbolt Android Development] xEVILFREDx:
I also have a battery monitor app that shows all the details on my battery getting hot.
[Thunderbolt Android Development] tats_06:
I know that...but that's why I said "reconsider"...Although my main point was people not taking responsibility for their actions. If I were VZW, I would make people sign a contract and hire someone who is a root expert to check every phone that comes in for replacement. If proven to have been rooted, to charge those people for replacements. Because people that take advantage like that screw things up for everyone else :rolleyes:
[Thunderbolt Android Development] mastibeta:
do me a favor bud, hop in the market and download android terminal emulator.

Then open it...type su (hit enter)...then input said command from 1st page.
[Thunderbolt Android Development] Taykiin:
Try running that command in terminal emulator. Open it up and type su then enter the command to get the results...
[Thunderbolt Android Development] mastibeta:
smoked

although more than likely he just needs to wipe and reinstall a froyo rom.
[Thunderbolt Android Development] PJnc284:
@Adrynalyne or jcase- For those of us who are remaining on Gingerbread for the sake of science, is there any other device information that we should get now while our devices are up that might be helpful in the event that ours bite the dust?
[Thunderbolt Android Development] Taykiin:
Lolzzz...nice!!! Man hoping to narrow this issue down! Thanks for everyone's hard work (especially Adryn and JCase) on the issue at hand!
[Thunderbolt Android Development] gsxraddict:
Keep in mind these guys don't get paid to do this. They are troubleshooting this on their own time and owe us nothing. If they knew what exactly the issue was they would tell us just like they brought this to our attention in the first place. It's simple they asked to run a command run it post the info. For myself reading through pages of the same info is enough we don't need to read complaints over doing something simple to narrow this down.
[Thunderbolt Android Development] inline6power:
phone is running.

SEM08G
[Thunderbolt Android Development] swimminsurfer256:
I wish there was a no thanks button.
[Thunderbolt Android Development] Araya213:
Yeah man, I changed my mind and edited my post a while ago. I'm all for them being open about it and would love some more info. I'm not going to be a **** about it though, that's just not my style. I think they could be a little more forthcoming with info in this case. There is more info in the IRC though.
[Thunderbolt Android Development] mkilla:
Been watching this thread since it started but had to sleep, someone please bring me up to speed on what 10chars is, ive been scanning through threads but didnt see it. thx
[Thunderbolt Android Development] ska.t73:
A post has to be 10 characters long for it to be posted on XDA...
[Thunderbolt Android Development] Shiftyshadee:
LOL :) A post has to be at least 10 characters long. People add that to the end of ones that aren't.
[Thunderbolt Android Development] Dnakaman:
That's the minimum amount of characters you need to post a message
[Thunderbolt Android Development] anothen:
10 characters. the minimum to be counted a post
[Thunderbolt Android Development] xEVILFREDx:
Thanks mastibeta , and Taykiin .

I used the terminal app and got SEM08G.
[Thunderbolt Android Development] lilcdroid:
SEM0G8

Radio Version 1.16.00.0223

Non bricked. Froyo BAMF Remix 1.6.3

Reverted from GB BAMF 2.0-5 yesterday. Thanks for the heads up.
[Thunderbolt Android Development] burkett375:
all the same so far...looks like i'm in the clear! :)
[Thunderbolt Android Development] rotarydial:
SEM08G

Non-bricked BAMF remix 5/23 nightly 0002 hardware
[Thunderbolt Android Development] breakerfall:
SEM08G

Reverted to froyo (bamf 1.7)
[Thunderbolt Android Development] ProTekk:
SEM08G - not bricked
[Thunderbolt Android Development] Tallica21:
Output: SEM08G

Status: Nonbricked, running Froyo.
[Thunderbolt Android Development] jcase:
That is a silly assumption at this point.
[Thunderbolt Android Development] kdb424:
Output: SEM08G

Status: Nonbricked, running Froyo. (reverted)
[Thunderbolt Android Development] otto888:
SEM08G

Not bricked, running CM7 with Froyo Radio.
[Thunderbolt Android Development] Florynce:
SEM08G - Not bricked

GB Das BAMF 2.05
[Thunderbolt Android Development] burkett375:
it was a joke...
[Thunderbolt Android Development] thejondude:
SEM08G not bricked running bamf remix 1.6.3 as of yesterday caem from 2.0 bamf GB
[Thunderbolt Android Development] DarwynZ:
SEM08G

Running perfect storm 1.4

Just rolled back from gingeritis till whatever this is blows over
[Thunderbolt Android Development] tekhna:
SEM08G

Not bricked, reverted from BAMF 2.0.5.
[Thunderbolt Android Development] jmiller98:
SEMO8G

CM7 imoseyon sp kernel

Non bricked
[Thunderbolt Android Development] inzandity:
SEM08G

Not bricked, reverted from BAMF 2.0.5 yesterday. On remix 1.6.3 right now
[Thunderbolt Android Development] Wildcat117:
SEM08G

Running BAMF REMIX 2.0 beta 5

Non-bricked