yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] rhcp011235:
Hey Guys,

I've been dealing on andirc.net with people with bricks. some guys have bricked on fryo and others on GB.

You can find your S/N under your battery. or by typing adb devices

it should show your serial number.

If you have bricked. Please post your serial # / rom / radio

also, if you are not bricked, please just post your serial #.

Im going to make a DB of this. To see whats up.

The decoding process:

HTYMDAABBBBB

HT = Vendor HTC

Y = Year (9 = 2009)

M = Month (hex 1...C = 1 - 12 months)

D = Day (hex 1...9A..Z = 1 - 31 days)

YY = Part Code -> S0 = Thunderbolt

ZZZZZ : Identification Number (decimal)

UPDATE: I wrote some code to decode these serials. Im going to be putting up a site. where people can enter their serial and it will keep it in a db. and people can see it.

Here is the src: http://mrcellphoneunlocker.com/decode.phps
[Thunderbolt Android Development] rhcp011235:
Reserved for later
[Thunderbolt Android Development] EEdaesung:
Ht12ns002761

^_^_^
[Thunderbolt Android Development] KGBxxx:
1800 superbeer
[Thunderbolt Android Development] happimeal:
Ht12ss007714
[Thunderbolt Android Development] Zabii:
ht14xs000098
[Thunderbolt Android Development] Yufice:
never bricked, been running GB since it first leaked

HT11VS010272
[Thunderbolt Android Development] Xirix12:
HT12JS001455

Not bricked right now running BAMF GB Remix beta6 but have been back and forth from froyo to GB about 5 times.

Sent from Tapatalk using my das BAMF REMIX'd ThunderBolt.
[Thunderbolt Android Development] tazman19:
HT11LS000549

Unbricked on GB BAMF Remix 2.0-6 beta.
[Thunderbolt Android Development] Nikolai2.1:
Is there a point to this thread? What exactly do you plan on accomplishing with this information?
[Thunderbolt Android Development] ThunderStick:
stop the insanity now...

Damn it, not another one of these... SERIOUSLY
[Thunderbolt Android Development] rhcp011235:
The point is to try to figure out what phones are effected. We can decode the serials and see what dates seem to be effected. and then maybe get more info as i go.

I have many dmsgs and last_kmsg from bricks. Trying to get down to real reason of these bricks.
[Thunderbolt Android Development] bisco3214:
HT121S005999

Not bricked, running bamf remix 2.0 beta 6.
[Thunderbolt Android Development] Nikolai2.1:
Then what? No use with this, no one can fix the bricks, and if they get bricked, then they knew what they were doing.
[Thunderbolt Android Development] DroidTh3ory:
You ROOT, hack and flash so much your Volume keys wear out... **** bricks. LOL, Simple as that. No conspiracy, no nonsense.
[Thunderbolt Android Development] EEdaesung:
It was nice knowing my phone is old as dirt.

^_^_^
[Thunderbolt Android Development] Nikolai2.1:
Did you brick? and if so what were you running? Regardless, there's not really anything anyone can do
[Thunderbolt Android Development] nerozehl:
You can have my serial number when you pry it from my cold, dead phone.
[Thunderbolt Android Development] avlfive:
Also, please post your credit card information and security code on the back. Or PM them to me. Thanks.

Lol.
[Thunderbolt Android Development] rhcp011235:
It's nice to know a date range of people who have bricked vs others.

People say nothing you can do. This comes from a person who is ignorant.

There is plenty that can be done. If we can figure out what the TRUE cause is.

Plenty of TB's dont have EEMC failures and can write to partitions with no issue.

others have eemc issues.

Cant rule out everything until we find the info out.
[Thunderbolt Android Development] SiL3nTKiLL:
keeping an eye on this topic....
[Thunderbolt Android Development] rhcp011235:
If people think you can 'something' with a serial #. You cant.

Im not here asking for ESN and IMEI. Im simply trying to determine the cause.

Others want to say radio hardware blah blah. I want the real reason.

*so what i can get a new phone if i brick. I still want to know WHY*
[Thunderbolt Android Development] Nikolai2.1:
I still don't understand, do you plan on fixing these bricks?
[Thunderbolt Android Development] jaysckap:
Dude, let it go.

HT11MS003927

Sent from my BAMF Thunderbolt powered by Sense 3.0
[Thunderbolt Android Development] ProTekk:
HT12NS003449

What I got
[Thunderbolt Android Development] bart77:
I work in manufacturing, so if it is hardware related you could find out if it were a bad lot of eemc used during the production run. It may only be a few but, if u had one close to the same serial of one that has bricked, your Rom swapping days may be limited. I'm sure HTC and VZW already know this info but us end users will never know.
[Thunderbolt Android Development] jcase:
These responses are ridiculous, he is doing a logical thing trying to pin down if bricks are coming from the same phone lots.
[Thunderbolt Android Development] rhcp011235:
This is true. Im sure they know. thats why i am info collecting. I'd love a few people who bricked to post their S/N as well. and yes i do plan to fix the bricks IF i can find the real cause.
[Thunderbolt Android Development] cferra:
HT11TS005289

Have not bricked (crosses fingers)
[Thunderbolt Android Development] avlfive:
Just throwing it out there but wouldn't it be easier to get the numbers from just the bricked devices and then see if there's any similarities?

Like get all the bricked folks together and then compare all the numbers that you can until you find a pattern?
[Thunderbolt Android Development] jcase:
You need both to even get anywhere near an accurate sample.
[Thunderbolt Android Development] jakaro:
Ht14ds001307
[Thunderbolt Android Development] chriskader:
I know it is not accurate, but the poll you have set up has 1 brick, 52 no bricks. I really think this bricking thing is getting blown way out of proportion. Also, these phones are not made to be flashed OVER AND OVER like most of these people, including me, are doing. It comes with the game. Once you root, you have a chance of loosing it all.
[Thunderbolt Android Development] TheOnlyOne93:
chriskader incase you haven't heard people ahve bricked without flashing or anything we have had people brick on MR1, MR2, GB, on all radios and versions, we even had someone brick just trying to root even with Jcases help. Soo it's not really blown out of proportion it's a real problem, and what RHCP is trying to do is a logical and very reasonable idea, me and him had talked about it last night.
[Thunderbolt Android Development] chriskader:
Like I said, its part of the game. Everything you said in your post is people bricking from FLASHING leaked, unsupported and ROMs that ARE NOT ready for production of daily driver use. I appreciate the effort, but it seems pointless since it is people doing things that has a chance of bricking the phone. I love flashing ROMs and I love having custom ROMs, but you have to think about it: All of the roms you listed are all ones that are LEAKED. The reason we do not have these officially given to us is because they are not going to work, there is going to be issues. Just my $0.02.

Also, seems like the wrong section. Maybe this should be in General or Q&A
[Thunderbolt Android Development] rhcp011235:
Thanks jcase for the support. If we can get enough info from this. we can pin-point where its taken place.

We have seen bricks on MR1/MR2/GB (So the whole GB radio/rom thing is totally debunked now)

If we can collect enough info. Maybe we can figure out which lot/shipment is bad. or maybe force HTC to tell us the truth here.

And, for those saying people are blowing bricks out of preparation. I've personally seen 4 bricks on andirc.net and some are bad, some are readable. But, so far none are recoverable. So, if ive seen 3-4. I want to know the true # and Also, I dont think this is possible without some news interaction.

Find out if anyone NOT rooted bricked. (That would be a major stepping stone) - as it would point directly to hardware 100% and we might have something on HTC.
[Thunderbolt Android Development] TheOnlyOne93:
MR1 is not a leaked rom, and someone has bricked on it normal stock mr1 not rooted. So it is needed information. MR1 is the update that verizon pushed OTA. Soo it has nothing to do with flashing unsupported unfished productes
[Thunderbolt Android Development] rhcp011235:
Correct and spoken correctly.

And, ID love to get some press out. To some major sites. to see if anyone has a VIRGIN NON ROOTED BRICK!
[Thunderbolt Android Development] adrynalyne:
Thanks for this rhcp.
[Thunderbolt Android Development] jaysckap:
+1

Sent from my BAMF Thunderbolt powered by Sense 3.0
[Thunderbolt Android Development] Jrocker23:
Im running Stock MR2 with 2.5 radio at the moment, I have also run original stock & original stock root & mr1 root with adrynalynes kernals.

Never bricked or had any of the issues that have been reported. Call, video volume all good, no reboots and good gps

S/N HT11XS012752

Thank you for looking into this....
[Thunderbolt Android Development] Mistar Muffin:
Bricked this morning after choosing reboot into recovery from CM7 power menu:

HT12FS008345

It was a refurbished unit from VZW if that makes a difference. It was a replacement that was sent under warranty for a different issue.

Oddly enough the above device bricked on the same day it's replacement (phone #5) came in the mail. Here is the SN of the newly arrived, non-bricked (but VZW refurbished) Thunderbolt:

HT12DS000131
[Thunderbolt Android Development] gsxraddict:
Ht12ts000125

Not bricked
[Thunderbolt Android Development] CPCookieMan:
I decoded the brick unit's serial, if it helps at all.

2/15/2011

Part Code: S0

ID Number: 8345

My launch day nonbrick is:

SN: HT11ZS016087

1/35/2011 (2/4/2011?) ???

Part Code: S0

ID Number: 6087

Ummm... 9+26 is 35. I'm confused.

And there seems to be an extra 1 in there that's not used?
[Thunderbolt Android Development] rhcp011235:
Well,

Thanks for the serials guys. From the 2 bricks. Here is the info.

HT121S000528	2/1/2011

HT12FS008345	2/15/2011

I wish more people would report bricked S/N's. The idea of the above person bricked on a refurb is kind of scarry. You'd think they would fix it.

More info please.
[Thunderbolt Android Development] CPCookieMan:
They didn't brick on a refurb, the original bricked as soon as the refurb came in.
[Thunderbolt Android Development] rulevoid:
HT121S003688

No brick, been on Gingerbread for a week now and 3 days a couple weeks ago.
[Thunderbolt Android Development] thoerr:
HT13ZS001565

No brick, Mr2 when it came out and now mr2.5
[Thunderbolt Android Development] ska.t73:
Read it again, he said the refurb that he was sent for a different issue just bricked...
[Thunderbolt Android Development] toomie05:
never bricked yet *Knock on wood*

running gingeritis and MR2 skipped MR1 cuz it seemed to sketch but all is well

S/N= HT12SS006911

good luck!
[Thunderbolt Android Development] Beastclaw:
HT12RS008492

MR1 (Had weird issues with MR2)

Not Bricked
[Thunderbolt Android Development] rhcp011235:
More more.

I want to reach 100 total. I need some bricked S/n TOO! I only have 2 bricks

31 total
[Thunderbolt Android Development] qumahlin:
Don't you get it yet from your own stats? Barely anyone has experienced this issue and some who have are on stock ron's

Its clearly some faulty hardware. HTC is probably investigating themselves.

Sorry to be a downer but this thread is pointless and quite frankly eople shouldn't be giving out their serials.
[Thunderbolt Android Development] rhcp011235:
Pardon me. If i go by your post count.

But what do you think the serial can do? Its not an ESN or a IMEI.

Even IF i worked for HTC. I could do 0 with it. Id have to go to VZW and and do all kinds of fun stuff. Im trying to help. I have easier ways to brick or kill accounts. To be quite honest.

So, dont down. You have already seen respected people post on this thread saying its a good idea. This is why XDA gets a bad name. and im sorry to say you are one of the users who cause it. Not trying to cause drama. Just keeping it real.
[Thunderbolt Android Development] 52brandon:
how is trying to find a similarity in bricked phones pointless? When 2 of the best known thunderbolt devs appreciate his work, I'd say it's relevant. I'm curious about his findings as well

and mine is HT12NS007439, have used every radio and not bricked
[Thunderbolt Android Development] rhcp011235:
Bump Bump Bump
[Thunderbolt Android Development] planepilot:
My coworkers that bricked with stock build. He did the ota update only. No attempt to ever root his phone.

HT127S002265
[Thunderbolt Android Development] gsxraddict:
Don't you have something better to do if you had no intentions on posting the sn why even come in the thread.
[Thunderbolt Android Development] rhcp011235:
Hey. I am very interested in your post here. This is the first report of a NON root brick.

Can you tell me in details how it bricked? be as detailed as you can be. Dont be shy to show noobness or anything :) Everystep. if possible.

Please explain in detail
[Thunderbolt Android Development] rhcp011235:
Also if so, If you can have your co-worker who bricked come on IRC @ irc.andirc.net #thunderbolt or #bricked and msg rhcp/jcase.

We would really like to talk to the person.

Thanks!
[Thunderbolt Android Development] planepilot:
I would be at his desk talking with him and his phone would just reboot! Here are the details when it died. His battery was low so he plugged the phone into the charger. After a few minutes he looked down and saw the boot screen. He didn't touch or do anything to it when it started. Unfortunately he has already returned it! I finally got in touch with him to get the serial number before he boxed it up.
[Thunderbolt Android Development] rhcp011235:
Crazy so now we know we have virgin bricks. I'm up to 45 or so serials need more.
[Thunderbolt Android Development] rhcp011235:
Bump bump bump bump
[Thunderbolt Android Development] vinylfreak89:
HT12ES006653

not bricked.

seeing a virgin brick is scary
[Thunderbolt Android Development] kingofyo1:
HT14KS015298

Unbricked on OMFGB
[Thunderbolt Android Development] rhcp011235:
Bump guys. Over 100 voted. Let's get those serials. Don't want them public pm me them.

I got 47 or so. Need a lot more.

Mod: can you sticky this please
[Thunderbolt Android Development] scotty1223:
i didnt vote,cause i have 2 serial numbers for you:

mine: HT126s005970

not bricked(yet)

ibrick on AF: ht11ys013963

bricked- running cm7/402 radios :eek:

yes,its the same bootloop of death,and officially bricked.

do you have a spreadsheet or other info somewhere public? or willing to email/pm the info to me? if its build date related,mine seems to be within a couple days of ibricks (feb 3 and feb 6)

thanks for collecting this info,despite the criticism and negativity.
[Thunderbolt Android Development] rmcomer:
HT12TS003010

Not bricked and hope to stay that way
[Thunderbolt Android Development] bgc123:
HT14BS009272

not bricked! :D and currently on BAMF GB Sense 2.1. Running MR2 radios. Only thing I've noticed was my phone just shuts off while on the charger after it has died. But it turns back on fine.
[Thunderbolt Android Development] Cadillac Johnson:
Voted, Scotty posted the serial of my bricked phone below.

Thanks for the help earlier on IRC. Definitely appreciate it.
[Thunderbolt Android Development] scotty1223:
thanks cadillac. hope its cool i posted for you. wasnt sure if you posted here or not :)
[Thunderbolt Android Development] PapaDroid:
Ht11zs006664
[Thunderbolt Android Development] philhyde:
Ht12es021169
[Thunderbolt Android Development] cypherx82:
Never bricked, ran GB leak, several ROMs, and all leaked radios.

HT12HS002880
[Thunderbolt Android Development] rhcp011235:
Thanks guys keep them coming.

If someone wants to write some PHP I'm willing to host the DB for viewing and adding online.
[Thunderbolt Android Development] rhcp011235:
B u m p b u m p
[Thunderbolt Android Development] TheOnlyOne93:
Bump for good messure
[Thunderbolt Android Development] beyondyourscope:
HT12CS003782, never bricked
[Thunderbolt Android Development] psychomaniac189:
Did Not Brick: HT11NS005448
[Thunderbolt Android Development] ricwhic414:
No Brick here.

HT14XS005567

Running Froyo Das BAMFv1.8
[Thunderbolt Android Development] soulesschild:
HT12NS001720 No brick so far. Knock on wood.
[Thunderbolt Android Development] Omen87:
No brick.

HT126S003585
[Thunderbolt Android Development] KGBxxx:
Wtf!!!
[Thunderbolt Android Development] JuniorSpades:
HT121S005416

No Brick yet...
[Thunderbolt Android Development] ibsk8:
You realize this is old?
[Nook Color Q&A, Help & Troubleshooting] Elegy:
Hi guys, since a couple days im the proud and happy owner of a Nook color. Before this I had an Archos 70IT, but the nook kicks its ass any day of the week.

But... i am having a bit of a hard time getting familliar with all the terms and policies that come in play when "hacking" the nook.

Mine is rooted using the "burn SD card method". I downloaded a copy of CWM and burned it to my SD, along with the uIMage and uRamdisk files and the latest version of Phiremod. Booted up in recovery, flashed Phiremod and set everything up.

Now, on the forum i see a lot of talk about EMMC and SD cards and running the ROMs from them.

What exactly do these two things mean? Where do I run my ROM from? Which is the preferred/fastest/most stable method?

What is the overall preferred method of flashing/running ROMs?

For example, i cannot seem to boot into recovery anymore because i formatted the "boot SD card" after flashing the ROM. On my phone I am used to just hold vol down and power on to boot into recovery.
[Nook Color Q&A, Help & Troubleshooting] Taosaur:
This blog may help you sort things out:

http://quinxy.com/guides/how-to-pick-your-nook-color-operating-system-and-install-options/
[Nook Color Q&A, Help & Troubleshooting] nook-color:
EMMC = internal memory ( Electronic Multi Media Card ) it's basically a SD card that's installed inside your device from the mfr. It's the 8GB of memory your Nook color has

SD - is your microSD card

You can run your ROM from either place. Depending on where you have it installed - but the NC - boot priority starts with the SD card - so if you've got a boot ROM installed on your SD - you'll boot from there. Otherwise it'll boot to your NC EMMC - and the SD card will be data.

Right - you booted off your SD card - and then erased it - so now there's no longer a boot file on your SD card - and now run off EMMC for boot ROM.

You can choose which memory to boot from - if you have a quality brand - fast SD card - the speed difference is minimal from what I've read. So far, I've kept the Nook software in tact for Warranty reasons - and it's easy to reformat a SD card if I want to get the memory back after a ROM install makes the drive " TINY " for storage purposes.

Check out the development section if you want to read more about SD card options - or EMMC ROM installs.
[Nook Color Q&A, Help & Troubleshooting] fattire:
It's actually "embedded" multimedia card...but yeah...
[Nook Color Q&A, Help & Troubleshooting] Elegy:
I found out my Nook cannot be registered because I live in holland. You need a United Stated IP address to be able to register. Something with license to buy ebooks online.

So the Nook stock software is kinda useless in Dual boot for me.

I burned a CWM recovery SD card, flased the latest Phiremod and formated the SD so I am assuming im running off of the EMMC...
[Nook Color Q&A, Help & Troubleshooting] nook-color:
If your machine can boot into Phiremod - with no SD card in your nook - when you power it up - then you're running off the EMMC.
[LG Optimus 2x] XT69:
Hi!

I'm on stock uk v10d, and I just downloaded today's amazon free app of the day, Jenga but I have problems with starting it. Whenever I start it, it gets stuck at the developers logo...

Anyone else with the same problem?

edit: Finally it started, as i left it for five minutes, but now I can't seem to exit it... back button doesn't work... however, great game, just buggy :(
[LG Optimus 2x] tonywaouw:
Mine is working but it starts after ~30 sec. And I'm on cm7
[LG Optimus 2x] XT69:
I figured out that if i turn off the screen and right after it i turn it back on, the game starts...

There is the same issue on the Xoom... can this be a kind of incompatibility with Tegra2?

anyway now i can play the game, runs great, but the only way to exit it is to kill the process... i can live with it but i think i‘ll send feedback to the developer :)
[Android Software/Hacking General [Developers Only]] AYahoo:
Playing QMG

Hi All,

I've been woundering, it should be possible to play qmg one the device no? can some one explain to me how can I play a QMG file on my device? clearly the device "know" how to play it....

Thanks,

AYahoo.
[Android Software/Hacking General [Developers Only]] AYahooo:
Header info

I don't know if it interesting for anyone, but after looking at the bootsamsungloop.qmg, I've analyzed some of the data, and it seems like the file is animation file, with 30 frames, the first 32 bytes of every frame looks like a header of the frame, putting all the headers one after another, I was able to understand some of the data, I'm attaching the file.

AYahoo.
[Android Software/Hacking General [Developers Only]] (•.•):
I think it is interesting, but not many here are into it like you.

You should directly contact developers here via pm or checkout github to get some professional help for your problem. ;):p
[Android Software/Hacking General [Developers Only]] mohtaprashantrocks:
wow

i found these same files too today on my galaxy tab 2 in system/lib , seems this is what makes it tick eh?now i need some help .... could you get some devs on to this post from

http://xdaforums.com/showthread.php?t=732311&page=17

and

http://xdaforums.com/showthread.php?t=792953&page=4

?

because turns out i can't post there i dont have permission or sumthing
[Fascinate Q&A, Help & Troubleshooting] neotrixy:
OMG, please help!

I was using the upgrade modem guide over in Development section:

http://xdaforums.com/showthread.php?t=1097355

I was odining the dl09 modem only file to my ComRom 2.0 with EC01 so I could upgrade through CWM to ED01.

However, Odin hung up for hours and did nothing, so I disconnected. Got the screen with picture of Phone - Exclamation Mark - Computer. And I can't get out of it! I've tried holding volume up and powering on with usb to computer plugged in, same screen. Tried volume down while powering on, same screen. Tried both bottoms, while powering on, same screen.

I understand that theres a link error, but, what the hell? I've been searching online with no luck.

Please help me fix my phone!!!
[Fascinate Q&A, Help & Troubleshooting] lord dredd:
well

chk this - http://xdaforums.com/showthread.php?t=1026746

OR you can try these :P i aint no specialist :P but these are harmless things.

TRY REMOVING the battery and then booting

1.. remove battery > hold vol down and plug usb in

it should be in download mode ( u alreday know that

) and try flashing the dl09 modem again

( i am assuming your odin .exe is not crrupt and you are using PDA option )

2. otherwise odin the stock dl09 ROM

I am not a specialist but thought of helping
[Fascinate Q&A, Help & Troubleshooting] efan450:
Try this...go here--->http://www.multiupload.com/I9HBT8MXN1 its the eb01 tar..use the atlas 2.2 pit with this and repartition checked and you push it with odin...i use odin v1.7 try that and then let it boot up.... you can always just flash the dl09 radio after if you really want that radio...for me the dl09 package wouldn't flash either but eb01 worked fine and will get your phone recovered, completely stock and un rooted, after that you can go about flashing whatever rom you want in the regular fashion...i hope this works and if not find dalev's method to recover any bricked fascinate...the link in the previous users post above mine