yashsingh1/xdaforums huggingface dataset:
[HTC Inspire 4G] danielsaenz:
Trying to be helpful here. Yes, it is in the Market. However, the Desire HD/ Inspire 4G is not yet officially supported. If you go to market.android.com on your PC you will see it but when you try to install it on one of our devices it will have that option grayed out. When you upload an apk to the market you can set limitations such as device, OS version, carrier, etc. Hopefully it will officially come to our phones soon.

Rant mode: What the heck are you doing in XDA if you don't want a hacked solution?
[HTC Inspire 4G] phonejunkie30:
I prefer to got with the real thing before a hack if available and I am in xda for more than hacking its more info avail outside of Rom cooking I want to try it but then I read how you have to download all is these pieces to fix radios and volumes afterward and it all just seems like a lot of work I thought android was easy but its not and I use to download find to my tilt and it wasn't hard
[HTC Inspire 4G] shogunmark:
it IS in the market... https://market.android.com/details?id=com.netflix.mediaclient

just not for the inspire.... yet..
[HTC Inspire 4G] opalelement:
I understand that it is in the market but supposedly they took away the device checking and are allowing us to try it even if it isn't "officially" supported. That isn't the case with the Inspire though, contrary to what was reported in the link I posted previously.
[Thunderbolt Android Development] adrynalyne:
Please tun this command from adb shell, and report back the following information.

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

Please reply with the terminal output and whether your phone is running, or bricked. Please, we need information from both sides.

Defintion of brick:

Rebooting in normal mode, as well as recovery, and RUU does not fix the issue.

Those who are Bricked, in addiiton to posting here:

Please contact jcase at #thunderbolt on irc.andirc.net. You have ~3 seconds to perform this command while in recovery. We also need dmesg output. DO NOT RUU, IF AT ALL POSSIBLE! WE NEED S-OFF STATUS!
[Thunderbolt Android Development] adrynalyne:
I will start with mine.

Output: SEM08G

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

Status: Nonbricked

We need brickers to do this, you have about 5 seconds in recovery to do it. Please contact us.
[Thunderbolt Android Development] psicrest:
Output: SEM08G

Status: Nonbricked, running Das Bamf 2.0-5 Gingerbread Radio.
[Thunderbolt Android Development] spaghetti_monster:
k#cat /sys/class/block/mmcblk0/device/name

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

SEM08G

#

Non bricked

Running GB Bamf 2.4.1
[Thunderbolt Android Development] CorporateGoth:
SEM08G - not bricked, running BAMF 2.0b5 (GB) with imoysen's 2.5.4b4 kernel.
[Thunderbolt Android Development] avlfive:
SEM08G

Not bricked. Rooted. Running DasBAMF 1.7.
[Thunderbolt Android Development] icedmayhem:
Output SEM08G - not bricked
[Thunderbolt Android Development] Captainkrtek:
Running Gingeritis non-bricked:

SEM08G
[Thunderbolt Android Development] burkett375:
SEM08G

nonbricked. was running GB, now running FROYO
[Thunderbolt Android Development] httr_:
SEM08G

Not bricked - Running GB (don't judge me)
[Thunderbolt Android Development] PJnc284:
Output: SEM08G

Status: Nonbricked, Das BAMF 2.0-5 Remix
[Thunderbolt Android Development] tavella:
SEM08G

Non-bricked running CM7.
[Thunderbolt Android Development] tryder:
SEM08G

Bamf 1.7, was Bamf 2 beta 5

Not-bricked
[Thunderbolt Android Development] JonKyu:
SEM08G

Non bricked, Reverted to Froyo
[Thunderbolt Android Development] funkybside:
Output: SEM08G

Status: Nonbricked, running BAMF Remix 1.6.3
[Thunderbolt Android Development] djbeanpole:
NonBricked, from both 2.0REMIX and 1.6.3FROYO:

SEM08G
[Thunderbolt Android Development] libraryclg:
SEM08G - not bricked - running BAMF Remix 1.6.3
[Thunderbolt Android Development] Veridor:
Output: SEM08G

Status: running, CM7 w/ MR1 radio (reverted from Gingeritis once the notice was posted)
[Thunderbolt Android Development] ERIFNOMI:
Output: SEM08G

Nonbricked running CM7 latest official Froyo radio
[Thunderbolt Android Development] redtechjunky:
SEMO8G

still stable ;) hmmmmmm

Sent from the Swag ThunderBolt ADR6400L with some GingerLove (SuperStable Gingeritis VIII, Sense 3.0 addons = Winning) using XDA Premium App
[Thunderbolt Android Development] mkilla:
Send some donations my way and ill be the guinea pig to brick my phone! Lol
[Thunderbolt Android Development] Nikolai2.1:
Hey how do find out what brand you eMMC is? I still cant find said post
[Thunderbolt Android Development] CorporateGoth:
Nik - instructions are in the first post.

You can run the command via. 'adb shell' or in a terminal window.
[Thunderbolt Android Development] ska.t73:
It's in the OP...
[Thunderbolt Android Development] mkilla:
I was joking cause the donation thing, it was funny... Haha
[Thunderbolt Android Development] jaysckap:
Run the command in the op on adb or terminal on your phone
[Thunderbolt Android Development] inspeckta_dek:
If we can't get no one ill check tomorrow morning at my friends VZW store. He's a tech there n ill ask him if he gots any bricks.
[Thunderbolt Android Development] Smok3d:
SEMO8G w/ BAMF Stripped Edition!

Thankfully i am still good here!
[Thunderbolt Android Development] rabnud:
SEMO8G, running gingeritis VIII

No issues so far!
[Thunderbolt Android Development] Nikolai2.1:
ohh i didnt realize that the command was to get the brand...excuse my stupidity :o
[Thunderbolt Android Development] mjones1052:
so are you thinking the SEM06G or w/e it is are safe on GB? Thats what I got out of your post anyway lol
[Thunderbolt Android Development] jaysckap:
Not yet need someone with a brick to test
[Thunderbolt Android Development] tx3kgtman:
SEMO8G

Where is all the brickers?
[Thunderbolt Android Development] mjones1052:
I know right lol, wonder where they all are. Wondering what theory they are working up, although I understand why they aren't saying anything.
[Thunderbolt Android Development] two_cents:
my friend is running the same set up as me and he can't get his phone to stop rebooting 3x a day I know its not a total brick but I will do my best to get the information off of it, then revert it back to froyo

mine is the same as everyone but his has been a problem child and mine has been a champ
[Thunderbolt Android Development] zhp pilot:
I think it's time to change the OP to ask for only people with bricked phones, otherwise you're going to end up with a thread 100 pages long with SEM08G, not bricked posts.

Edit: What the hell, might as well throw mine in there too.

SEM08G

not bricked
[Thunderbolt Android Development] tecknical:
yea. seems like everyone here also has the sandisk emmc not the off brand knockoff one
[Thunderbolt Android Development] Dubin04:
I agree with that
[Thunderbolt Android Development] luigi1111:
How about, only those with bootloop bricks, or those with something OTHER than SEM08G?

(Aka, not me :D )
[Thunderbolt Android Development] StormFreak:
Might as well add one to the unbricked pot... Was on BAMF 2.0.5, now back to Froyo (Remix 1.6.3)

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

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

SEM08G
[Thunderbolt Android Development] Matthew_STL:
SEM08G

unbricked, ran gb for 40 hrs, reverted back to froyo
[Thunderbolt Android Development] Nimbus79:
SEM08G

Unbricked... Currently on ThunderROM 1.0 (froyo)

Ran pretty much all of the gingersense ROMS at one point during the last 8 days. No issues at all.. hiding out on froyo for the time being.

Thanks for saving our asses guys! Hope this is short lived... I miss my sense 3.0 lockscreen :(
[Thunderbolt Android Development] quepaso:
C:\adb\android-sdk-windows\platform-tools>adb shell

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

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

SEM08G

#

Unbricked and back on unhappy Froyo
[Thunderbolt Android Development] EEdaesung:
Output: SEM08G

status: nonbricked

^_^_^
[Thunderbolt Android Development] mrbracht:
I'm going to stay with gingerbread and see if I can't get it to brick

Sent from a cellular telephone
[Thunderbolt Android Development] joshnichols189:
You are a brave soul my friend.
[Thunderbolt Android Development] djbeanpole:
Good luck to you sir.
[Thunderbolt Android Development] gifferjesus:
Same result as every other no-bricker here.
[Thunderbolt Android Development] BurnOne77:
Same as all the others, not bricked and same name.

I ran BAMF GB and Gingerbean
[Thunderbolt Android Development] Purgatoiry:
I'll go back to GB tomorrow and see if it bricks, at least then we'll know more than we do now.

Sent from my Thunderbolt.
[Thunderbolt Android Development] djbeanpole:
What I'm hoping for is someone with a different EMMC than SEM08G, so that we can go:

And then that person will brick and be like:

So then we'll all know that what we've all been posting ***SEM08G*** (hopefully) won't brick at all, then we can all go back to GB and have:

At least... I feel like thats how I'll react.

:D

(just trying to lighten the tension ;) )
[Thunderbolt Android Development] BurnOne77:
I think i'll wait till we get a decent radio either way. My phone never technically overheated on GB but it ran hotter and use way more battery at idle.. something is going on regardless.
[Thunderbolt Android Development] djbeanpole:
The price we pay for tinkering eh?
[Thunderbolt Android Development] BurnOne77:
Fortunately I didnt pay I price because I listened and reverted. Thanks to the awesome devs here. I love froyo and 1.6.3 remix and cf 2.0 kernel are simply the best setup I have ever had on this phone so aside from no netflix I don't really care.
[Thunderbolt Android Development] djbeanpole:
Ha you and I are running the exact same setup! (sig needs updating I guess)
[Thunderbolt Android Development] nolmt60243:
SEM08G and I am not bricked.
[Thunderbolt Android Development] jaymccoubrey:
F it I'm going back to gingeritis and watching the temp on my phone. I'll send jcase the melted remains
[Thunderbolt Android Development] Richpopski123:
Non brick and same as everyone else.
[Thunderbolt Android Development] gifferjesus:
Seems the brick folks are either unable to help or unwilling to open the box for 5 minutes.
[Thunderbolt Android Development] gti3358:
Output: SEM08G

ROM: CM7 from all the BAMF GB Beta's, last one was REMIX 2.05b

Status: Nonbricked
[Thunderbolt Android Development] B3L13V3:
Output: SEM08G

Was running GB leak, reverted to Froyo

Status: Nonbricked
[Thunderbolt Android Development] xHausx:
Not sure if this will help or not but I've heard of something similar with the Evo after the misc partition gets corrupted, it gets flashed when rooting to downgrade the firmware and if it's bad the phone will not stay running for more than a few seconds. Running a RUU doesn't flash that partition so it doesn't get corrected that way.
[Thunderbolt Android Development] crackedvenom2:
So did the guy from the other thread ever get over here or irc so jcase could check it out? We only have like two brickers on here, and one doesnt want to open their box.
[Thunderbolt Android Development] ugadawg67:
Output: SEM08G

non-bricked

ROM: Gingeritis v1.0 Beta VIII

I have the extended battery and never runs hot per temp monitor, stays around 91
[Thunderbolt Android Development] djbeanpole:
They chatted on IRC and his phone wouldn't even turn on so he couldn't help the cause.
[Thunderbolt Android Development] crackedvenom2:
Damn that sucks :(

EDIT: This guy is throwing out ideas too.

http://xdaforums.com/showthread.php?t=1098531
[Thunderbolt Android Development] kurrupt_1:
Originally Posted by kurrupt_1

My bricked device is already boxed up to be sent back.

Originally Posted by dr_drache

unbox it, you can rebox it after!!!!

Here's the scoop, I bricked my TB last weekend and jcase walked me through some steps to try and recover it but nothing worked. It is currently boxed up and in my car ready to ship back to verizon. I'm currently at work and IT restrictions prohibit me from downloading anything to any computer at work. With that being said, I've been at work since 9 pm Cali time and I wont be home until 7ish am Cali time when I can actually run the command and hopefully get what people need. I'm hoping someone (jcase via gtalk) will be around to assist if I have issues. If no one is around I'm going top sleep and I wont be up for at least 6 hours. So there you have it I definatley want to help the community but my hands are tied being at work.

OH SNAP....I think i can by pass my works IT policy by tethering my BB via DM.......hmmm is someone up to help if needed?
[Thunderbolt Android Development] jasonxlee01:
Im still up but im not a dev but i can maybe help you go through with it.
[Thunderbolt Android Development] djbeanpole:
Crap on a stick someone wake jcase up!!!!
[Thunderbolt Android Development] jasonxlee01:
What did you find out? What happened?!
[Thunderbolt Android Development] ridobe:
Same.

10 char
[Thunderbolt Android Development] kurrupt_1:
downloading the sdk now.
[Thunderbolt Android Development] djbeanpole:
lol read a few posts back dude
[Thunderbolt Android Development] djbeanpole:
I'm heading to bed gents. Kurrupt I wish you luck... and hope you get some sleep soon.

Jcase... good luck to you as well sir in solving this endeavor!
[Thunderbolt Android Development] DroidTh3ory:
I didn't even have close to enough time to get into recovery, let alone get into recovery and bang out a adb command. LOL, I only could see hboot for a couple seconds before it booted me out.

Are we having a development with the issue? Man, the things that go on at XDA when you are sleeping.
[Thunderbolt Android Development] albotz21:
Output: SEM08G

Status: Nonbricked, running Froyo. BAMF 1.7
[Thunderbolt Android Development] idle0095:
how do i run the adb command?
[Thunderbolt Android Development] sublimaze:
SEM08G

Nonbricked Gingeritis VIII, extreme 1.4ghz

@idle0095

Plug phone into computer, open command prompt in your adb directory, type:

adb start-server [enter]

adb devices [enter and make sure your phone is seen]

adb shell [enter]

cat /sys/class/block/mmcblk0/device/name [enter]
[Thunderbolt Android Development] Tallica21:
Kurrupt, There are people here to help you, let's get this done.
[Thunderbolt Android Development] idle0095:
how do i run this command and ill join in.
[Thunderbolt Android Development] Tallica21:
From PC:

Make sure adb is set up>plug phone in to PC>charge only mode>open command prompt>type: adb shell>press enter>you should get a #>type: cat /sys/class/block/mmcblk0/device/name

From Terminal Emulator on your phone:

Open TE>type: su>you should get #>type: cat /sys/class/block/mmcblk0/device/name
[Thunderbolt Android Development] idle0095:
SEM086G

Gingeritis v1.0 Beta VIII

NON Bricked
[Thunderbolt Android Development] seang:
SEM08G

non- bricked.
[Thunderbolt Android Development] Kennyc11:
SEM08G

Non bricked running das bamf 1.6.3
[Thunderbolt Android Development] Tallica21:
This is a typo right, there is no 6 correct?
[Thunderbolt Android Development] crackedvenom2:
Same as everyone else
[Thunderbolt Android Development] taurus92:
Both SEM08G

Both NON Bricked.

One Das BAMF 205 ~ reverted back to BAMF 1.6.3 Remix - this is the one that lost the lock screen and any ability for screen input.

One Das BAMF 2.04 reverted back to 1.6.3 remix
[Thunderbolt Android Development] ibsk8:
SEM08G

Non-Bricked

Froyo - Das Bamf Remix 1.6.3
[Thunderbolt Android Development] JoeyDVDZ:
SEM08G, Non-bricked but experienced a couple of random boots while on GB, flashed back to froyo via Bamf 1.7
[Thunderbolt Android Development] Morkai Almandragon:
I have a friend who is suffering reboots on a stock but updated phone. I will run this on his later today.
[Thunderbolt Android Development] sting5566:
SEM08G

non-bricked, running BAMF 2.0 remix
[Thunderbolt Android Development] Dat108Kat:
Should we do this if we reverted back to froyo?
[Thunderbolt Android Development] gti3358:
Yes! (10char)
[Thunderbolt Android Development] alu1008:
SEM08G

back to Froyo
[Thunderbolt Android Development] bleeds:
And mine...

SEM08G

No Brick, Still running GB BAMF 2.0-5.0

Thanks

Bleeds
[Thunderbolt Android Development] itsDollar:
Output: SEM08G

Status: Nonbricked, running Froyo

Previously ran GB leak
[Thunderbolt Android Development] bp328i:
Did not read through all 26 pages but my phone did brick last Saturday. I tried to use adb every which way I could for about an hour and the phone was never recongnized. Even when it would sit on the bootloader screen adb still would not recognize it.

I don't have it any more so I can't try again.
[Thunderbolt Android Development] mar5hal:
that shouldn't be necessary.
[Thunderbolt Android Development] major_works:
SEM08G

Non-bricked, running Froyo, moved over from Das BAMF 2.0-5.
[Thunderbolt Android Development] Cubs2008:
I have a day one Bolt and output is same as everyone else (non-bricked.) 1.6.3 remix and updated Froyo radios.
[Thunderbolt Android Development] tazman19:
SEM08G

Running BAMF 1.7

Previously on BAMF GB 2.0
[Thunderbolt Android Development] mar5hal:
this... shouldn't be necessary
[Thunderbolt Android Development] sonofskywalker3:
I'm afraid all this topic has accomplished is to create a (possibly false) sense of security for everyone with the same emmc chip. I hope something is truly confirmed soon, for everyone's sake.

That said, I have the same result, reverted to Blackhole 1.1.
[Thunderbolt Android Development] Daswolven:
Result & Status = Ditto.

I only read the first ten and last ten pages. lol. I take it we have no different results, and no bricked phone reports....

For those who have seemed to be comforted by the thread so far, personally it solidifies that I will stay the hell away from the leak. What we have now indicates we are all vulnerable to the issue.
[Thunderbolt Android Development] Fodizzle1978:
Same, non bricked, day one Bolt, Froyo ATM
[Thunderbolt Android Development] Dat108Kat:
Ok...will do so when I get home from work. Should I be worried? Is there still a chance my phone could be bricked if I was running the GB radio at some point/time even though I reverted back to froyo?
[Thunderbolt Android Development] KDKobes:
Did u get a hold of jcase and see if there is a way???

This f_king sucks..
[Thunderbolt Android Development] HashTagHell:
Output: SEM08G

Status: Nonbricked, running Froyo.

Reverted from GB
[Thunderbolt Android Development] incredibler:
SEM08G froyo bamf remix no issues
[Thunderbolt Android Development] houseboatwayne:
Could anyone create a sticky at the top of the forum called something like brick only and make it clear only post if your phone bricks? I know a lot of us are reading through threads everywhere looking for answers. Maybe tell them report if they are on GB or Froyo, what happened, and to pull Jcase's adb request. Oh, also place the definition of brick so we don't have people posting information on a nonbrick phone.
[Thunderbolt Android Development] davidbudd1:
Mine is: SEM08G

Running BAMF 2.0 Test 5 and Imoseyon's kernel 2.5.4 test 5(AMAZING battery life on this kernel by the way)

Running very smooth, never bricked
[Thunderbolt Android Development] MechaMorph:
Mine is: SEM08G

Das Bamf 1.6.3. Was running 2.0-5 until jcase posted about the bricking issue.
[Thunderbolt Android Development] psufan5:
THis thread is completely pointless. Until someone posts that IS bricked, 100 replies with the same version not bricked proves nothing.
[Thunderbolt Android Development] chino0131:
Output: SEM08G

Not bricked, rooted currently running Perfect Storm (2nd Thunderbolt after first appeared bricked).

Dont know if it matters, but my other Thunderbolt that appeared bricked (stuck in endless boot loop and couldnt load past HBOOT or Recovery for 48 hours: see thread here:http://xdaforums.com/showthread.php?p=14194462#post14194462) took the PG05IMG_MR1_upgrade.zip that had been sitting on my sd card the entire time and updated. This happened this morning. The phone appears to be up and running with no issues, but i cannot confirm if its receiving data and/or can make calls since I already bought a new TB.

Before anyone asks, i did try every option possible and every PG05IMZ.zip to get the phone up and running. However, none of the zips took initially, not even the last one I had put on the SC card that seemed to take this morning.
[Thunderbolt Android Development] Daswolven:
Not quite. :)

10 non-bricked replies with one result and one bricked reply with a different result is much more insubstantial compared to 1000 non-bricked and a single different brick.

But a bricked response would be nice....
[Thunderbolt Android Development] bighead21:
SEM086

Unbricked, rooted with MR1/OTA, running Tesla Coil with Imo's lean kernel
[Thunderbolt Android Development] currensy:
I bricked my device by deleting 00_vddlevels in root explorer. i had das bamf remix and did a custom kernel but setting my own levels and deleted the old vdd levels file and my phone kept rebooting...i already turned it in though and "manually" alter the phone volume keys so no one can get to the bootloader screen....are you figuring out how to save bricked devices....I always bricked my D1 but i could flash VZW .sbf flash file and rsd lite

will we see something like that for the thunderbolt in the future
[Thunderbolt Android Development] distortedloop:
I think there might have been better ways to collect this, like perhaps a poll with bricked/not-bricked and all the known mmc name codes, but there is some value in getting a feel for just how wide-spread the problem is by comparing how many bricked vs non-bricked.

I posted in the DAS BAMF 2 thread the other night that for all we know the problem was bad hardware, not bad radio, and that our perception might be skewed because any non-geek types who have bricked even on unmodded phones and don't know to come here or andirc chat to share the info. Seems like jcase and crew are heading down the bad hardware path as well. I hope they prove the point; I'd like to go back to GB. Not as stable as Froyo on my TB, but frickin' slick.
[Thunderbolt Android Development] currensy:
LOL I bricked my 2nd device by (I dont know how) I followed the first 4 steps and was ready to flash my next PG05IMG file...I noticed that bootloader was S On after flashing the 399MB file and it just kept rebooting...I used the same PG05IMG files to root the 1st thunderbolt i received when it first came out...(5days ago). I'm afraid to root this one and probably will never do it...I should have used androidpolice updated version but I wouldnt think it will be a problem if I didn't???
[Thunderbolt Android Development] funkybside:
That's not bricked. From the OP:

I miss the days when 'bricked' meant completely dead, unsaveable, as useful as a brick (or less). All this soft/hard brick nonsense makes me rage inside.
[Thunderbolt Android Development] dapbmonkey4u:
Output: SEMO8G

Non- bricked running gingeritis beta 8
[Thunderbolt Android Development] Daswolven:
A true brick cannot be recovered.

If you could get to the bootloader, you could have fixed your device.

There is an issue that's being investigated here, with about twenty different threads to catch you up.
[Thunderbolt Android Development] crackedvenom2:
So we've still gotten nowhere? Did that guy who was working every get back to anyone?
[Thunderbolt Android Development] WormDoes:
Whenever I do this I get cat /sys/class/block/mmcblk0/device/name not found :confused:

edit: ran it via adb and got the same as everyone else..

SEM08G

not bricked, running Stripped 1.1
[Thunderbolt Android Development] currensy:
i'll root this one now and if i mess up i'll report it just a part of my donation because i have a feeling that my phone is rigged that VZ knows that i'm been excessively tethering and waiting to void my warranty. how can i used terminal emulator or used cmd if i'm bricked and it cannot connect to the phone
[Thunderbolt Android Development] Daswolven:
Follow the Instructions + Don't be lazy and skip the checks = 99.9% chance of success.
[Thunderbolt Android Development] thewebsiteisdown:
I was on GB, reverted.

SEM08G

Wife has one now. Never touched hers but I still got the name to see if ti's a weird one or not and..

SEM08G