yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] robsonline:
I installed MR2 and Gingeritis yesterday. I don't want to brick my TB. Should I roll it back to MR1, or can I stay with MR2 and run Planejane? Let me know. Thanks!
[Thunderbolt Android Development] jaysckap:
I wouldn't blame MR2, he flashed a kernal and then it bricked. IMO the tbold is a time bomb, not saying all of them but I think if its gonna brick its gonna brick regardless of weather its rooted or not.

Sent from my BAMF Thunderbolt powered by Sense 3.0
[Thunderbolt Android Development] MrKleen1:
I hope this doesn't get blown out of proportion like it did last time.

To me it seems like the Thunderbolt is a phone that can brick no matter what radio is being used. Actually that may be worse than being able to blame it on a radio.

By reading it seems difficult to find those that actually bricked their phone. The percentage is very small. Oddly it seems there were a couple higher profile bricks... (Adrenalyne, and Erishasnobattery friend? ) Because of this everyone is going to freak out again.

The percentage and odds are low to brick. I just hope we all continue to enjoy our Thunderbolts and not get overly concerned with this. You have better odds of getting your girlfriend pregnant while wearing a condom.

And if by some chance the condom breaks or your phone goes into endless bootlooping... A new phone will show up in a few days with insurance.

Please let the progress with these roms continue!
[Thunderbolt Android Development] adrynalyne:
I agree its a timebomb, but to clarify, it wasnt during the flash. It was a reboot or two after.
[Thunderbolt Android Development] michaelkahl:
Thats a scary thing.
[Thunderbolt Android Development] amosavitas:
hmmm... What's that ticking noise?
[Thunderbolt Android Development] edjm711:
I have been running gingeritis since last week, latest radio, no issues other than the random screen not waking up. Don't know if that is a precursor to something or a known issue.
[Thunderbolt Android Development] azturbomini:
When are you and the "ball and chain" headed to BB to bust some heads?
[Thunderbolt Android Development] amosavitas:
Well **** I guess that's the end of the "operator error" theory.
[Thunderbolt Android Development] KDKobes:
Raise your damn underclock its too low
[Thunderbolt Android Development] edjm711:
Lol. Thanks. I didn't mess with any voltages though, only flashed rom. So does gingeritis have a low clock by default? I had set cpu back in the day, so I can re download it and set my clock speed.
[Thunderbolt Android Development] KDKobes:
Most are set to 245...that's too low...368 and above is best...try that if it freezes go up again...
[Thunderbolt Android Development] adrynalyne:
Went today. Ended up with a choice of a refurb now, or a new device in two weeks.

Le sigh.
[Thunderbolt Android Development] bp328i:
Sorry to here about your Thunderbolt, this phone is really making me worry about flashing anything. Funny how the Black Tie Program works, isn't it. Sounds just like what I was saying a few weeks ago.

So which one did you pick, I waited the two weeks.
[Thunderbolt Android Development] azturbomini:
I have no issue with a refurb especially if I'm able to handel it before walking out of a store.
[Thunderbolt Android Development] edjm711:
Thank you. I'll give it a go
[Thunderbolt Android Development] djkeller3:
I for one never was comfortable setting my low at 245, though I have done that at times. As for undervolting, I've never tried it and would never want to, purely from a performance standpoint... I don't see the purpose. The little bit of battery it might save, to me, is worthless if it hampers performance.

I have my high clocked at 1.4 and my low clocked at 1.4 in Performance mode and I've been running that way for weeks now. My TB loves it, and so do I. And it doesn't seem to have affected my battery whatsoever.
[Thunderbolt Android Development] azturbomini:
Your running at 1.4 besides when the phone sleeps and it doesn't hurt your battery life? My battery life would suck doing that.

I have no issue at 245 for my low setting even while using live wallpaper.
[Thunderbolt Android Development] adrynalyne:
I waited. I almost had them reconsidering, but after an hour of fighting, it just wasn't worth it anymore.
[Thunderbolt Android Development] bp328i:
I feel your pain, I did the same thing, I fought with them for about an hour but was on my way to take my wife and mother to dinner so just gave in. They have nothing better to do so I was done wasting my time there.

They should have gave you your sdcard, battery, and battery cover to hold on to as they only send back the phone it self. The good thing about waiting is when you go back to pick up the new one don't take any of that stuff back in with you and now you have a spare sdcard, battery, and battery cover, oh yeah an extra charger as well.
[Thunderbolt Android Development] distortedloop:
What is the clock frequency range on a stock phone? ??? to 1024.
[Thunderbolt Android Development] xsparky83x:
I also recently experienced a hardware failure (camera).

The camera app was only showing a black screen (could see the backlight on) which could only be exited with the home button. A reboot helped at first but eventually not even that would help. Flashed back to stock as a last-ditch effort hoping it was software/ROM related; with no luck. Replacement on order.
[Thunderbolt Android Development] yakitori2:
Adrynalyne ..what kernel was it that u flashed and ended up with a brick...just in case I am using it now...or anyone else is
[Thunderbolt Android Development] spursrchamps2007:
@ adrynalyne

@ adrynalyne sorry about the brick, but its the risk we all take. I wish you lived near NYC my friend works as a black tie at the BB im my town, he would've hooked you up. Anyway big fan of your work currently flashing your continuum rom on my wifes phone as she had enough with bing and asked why I was dragging my feet lol. Anyway thanks again for the work and sacrifice
[Thunderbolt Android Development] adrynalyne:
I'm not about laying blame on a dev. That wouldn't be right of me to do, nor would it be accurate, as I am sure it was just a coincidence.
[Thunderbolt Android Development] adrynalyne:
Thats something I guess ;)
[Thunderbolt Android Development] xdviper:
Wait, we might have something here, I have a MyTouch 4G, and we have two different chips in these phones as well, the eMMc looks like it's the problem and keeps dying randomly.

We have the SEM04G chip which is the good chip, which we found through a poll I've created, that has the LEAST amount of failures if not, very rare to have the eMMc chip gone bad. And then we have the M4G2DE chip, which has been dying a lot.

Now we also have two different methods of rooting (S-OFF) on these phones, both the myTouch4G and the G2 use the same locked bootloader so same expolits were used on both phones. One method involves just exploiting the bootloader into S-OFF with the ENG H-Boot, and the other is gfree. Both work the same way, except gfree is much easier and doesn't require you to have the ENG HBOOT, and also gives us true S-OFF with radio off, CID unlock and also SIM unlock.

I have a thread in the general section, with users posting their results and their chip type and which method used to root.

I think we may have something here....
[Thunderbolt Android Development] dpdurst:
I read through the thread I got something different could be because the phone is different as well.

Rooted with Jcase 7 step method (sounds like an AA slogan (no offense to anyone))

<6>[ 15.715606] sdio_al mmc0:0001: Probing..

<6>[ 15.716369] mmcblk0: mmc0:0001 SEM08G 4.17 GiB
[Thunderbolt Android Development] bagsofcole:
How many MR2 bricks are out there? When the first bricks started popping up, I had no choice but to revert. I am on the road and use my phone for everything, gps, email, internets, camera, and oh yeah, a phone. So I can't take a chance of being lost out here in Podunk, SC. But I am starting to suffer from the DT's. I needs my fix! I am sorry to hear about Adrenalyne's paper weight, but has anyone else suffered from problems with MR2?
[Thunderbolt Android Development] tekhna:
I think he's the only one, and if I recall correctly, it was probably a processor failure unrelated to the radio.
[Thunderbolt Android Development] xdviper:
Could be, but now that the emmc is dying it could be a probable cause. Plus I just got the sensation today, the s-on is really great. Ughhhh
[Thunderbolt Android Development] awwilson21:
I'm actually hoping that all of our TBs brick so Verizon is required to issue a recall. This phone is junk and if It weren't for the devs great work I wouldve already thrown this thing off a bridge and bought a new phone off contract...
[Thunderbolt Android Development] USSENTERNCC1701E:
Seriously, what is it people expect their phones to do, perform fellatio? I remember the first time I hard modded a slocket to get my PIII running at 1 GHz. Now I have a phone that runs neigh that speed stock. This phone's emmc has a greater capacity than my first two mp3 players, let alone the 32 GB SD card it came with. Its screen has a greater pixel density than most HD TV's. And it has faster internet than some cable connections. What about this phone is so terrible?
[Thunderbolt Android Development] awwilson21:
I think for the price of the phone we deserve something that is reliable and doesnt die in 6.5hrs.

Imagine you are getting robbed and when you go to call 911 the phone bootloops..

I'm not asking too much of it at all, why do people act like everything is ok instead of demanding more is what you should be asking.

Your excuse (which i dont get, do you own HTC stock?) Is that its fast, so being crap is ok. Cmon man.

If you really thought everything was hunkydoory you wouldn't feel the need to defend a device!!!
[Thunderbolt Android Development] Forgetfull:
If you're getting robbed having the cops show up 3-5 minutes later is going to do nothing for your well being. Should have brought a gun. I see you're point though.

I don't think this phone is junk. The issues I see are the odd performances with LTE (but we knew this coming into a beta network) and reboots that some people have. Unfortunitly I'm starting to think that the reboots are partly tied into the hardware since there are so many variations to reboots.
[Thunderbolt Android Development] adrynalyne:
Aren't you the troll who said we were all committing fraud?
[Thunderbolt Android Development] gsxraddict:
Lol yes yes he is.
[Thunderbolt Android Development] planepilot:
So I had a co-worker come by yesterday to show me his phone. It was doing the bootloop of death! This guy has never thought of rooting his phone so it most certainly appears to be hardware related. His had been doing the random reboots about 2-3 times a week prior to the death.
[Thunderbolt Android Development] phoney6:
You should get his serial number and post it here: http://xdaforums.com/showthread.php?t=1130407
[Thunderbolt Android Development] fixxxer2008:
so i just upgraded to gingerbread with the mr2 radio. should i be ok or do i have to worry about bricking my device? sorry if this has been asked 1000x.
[Thunderbolt Android Development] kingofyo1:
anytime you change a radio, there's a possibility (no matter how slim) of bricking.
[Thunderbolt Android Development] distortedloop:
Technically you're correct, there's a risk of bricking if the flashing goes bad...but I believe the question you responded to was more directed at whether there's a risk of the random bricking phenomenon that started all the uproar with the particular radio he flashed.
[Thunderbolt Android Development] scotty1223:
apparent new brick: http://androidforums.com/thunderbolt-all-things-root/362893-bootloop-death-cm7.html (im not sure if he can post here)
[Thunderbolt Android Development] fixxxer2008:
okay this is enough for me to go back to froyo for now. this doesn't sound radio related at all, more like gingerbread related.
[Thunderbolt Android Development] djbeanpole:
I'm staying. Bricking is part of the risk we assume the moment we've rooted and start fooling around...
[Thunderbolt Android Development] fixxxer2008:
no typically the only time you can brick your phone is by flashing an incorrect radio or during the process of rooting. root itself nor running roms will brick a phone. that's whats concerning to me right now, whats causing this to happen? is it radio related or not?
[Thunderbolt Android Development] djbeanpole:
Thats my point. We don't know. There's a reason why your warranty goes out the window once you step beyond that point ;) Its not so much rooting, but what we do after :p
[Thunderbolt Android Development] :
Well the only other thing left in common is clockwork recovery...

Edit: correction, and the engineering bootloader
[Thunderbolt Android Development] scotty1223:
just thot id mention for those that havent actually gone to AF and read the thread... he was on cm7 and the mr1 radio. its somewhat of a relief to me... if its gonna go up in smoke it seems its gonna do it no matter what rom/radio your on.

so still we dont really have any idea whats going on... ima continue flashing like its 1999 tonite :D
[Thunderbolt Android Development] TheOnlyOne93:
We have one other thing in common with almost all the bricks, overclocking. I've been helping a few of the devs narrow down causes, and a good portion have been overclocked to at least 1.4, clockwork has never caused a brick... in any phone out there ever that I know of.. and the eng hboot could possibly be a casue.
[Thunderbolt Android Development] scotty1223:
that would suck... id hate to give that up :p
[Thunderbolt Android Development] TheOnlyOne93:
like I said we don't really know the casue I doubt it's the end bootloader though, I think personally think it's either a bad lot, or overclocking and the cpu just fries.
[Thunderbolt Android Development] scotty1223:
or a combination of those things... im not OCed,and my phone does some kinda flaky things that make me think it may not be long for the world.
[Thunderbolt Android Development] :
The extra heat from the oc and the radios in this thing combined could certainly do it. The inspire has the same CPU and oc's nicely...but doesn't generate the same heat as this device. I haven't oc'd for that very reason. This thing can get hot enough stock.
[Thunderbolt Android Development] USSENTERNCC1701E:
The only time I've had mine overheat is if I'm charging while streaming music in my car, so I've lowered the OC and stick the phone in the AC vent :)
[Thunderbolt Android Development] Wayloss:
SEM08G

Non-bricked, Gingeritis 1.0, leankernel 3.4.0
[Thunderbolt Android Development] :
Hahaha the same thing I do, I just mounted my car dock between two vents and when it starts to get toasty I blast them both until its back down around 25 cel. :p
[Thunderbolt Android Development] destroyerbmx:
I have OC'ed mine from the first day it was available, I only go to 1.4 as the chipset is designed to go to that. Maybe that has something to do with it, mine has never over heated or really gotten that hot.
[Thunderbolt Android Development] kawfeegod:
I have two TB's in the house.

SEM08G , non-brick, CM7 MR2.5

For both...
[Thunderbolt Android Development] whoamanwtf:
I have a rebooting one, is this what you mean by bricked?
[Thunderbolt Android Development] scotty1223:
does it just continually bootloop wether attempting to boot into the OS,or recovery,msking the phone unbootaable to the OS,and wont stay in recovery for more than a couple of seconds? if so then yes,thats what is being discussed.

or is it rebooting eveey now and then and funtional between reboots?
[Thunderbolt Android Development] ILMF:
SEM08G

Gingeritis 3D v1.0 Beta VI

I'm pretty sure I'm bricked. Can't stay in recovery long enough to do anything. Will stay in HBOOT forever though. The brick occurred when I attempted to turn it back on after having it off, but on the charger. Powering it on, it just rebooted time after time. Went into recovery but it won't stay in recovery long enough to flash a rom, do anything.
[Thunderbolt Android Development] mmobley:
Output: SEM08G

NON BRICK

I ran every GB rom on XDA to try them out.

The only rom I could say I downloaded every update and ran is BAMF -GB-

Currently running CM7 test 1 GB.
[Thunderbolt Android Development] Jlluna87:
SEM08G

Not Bricked

Running Das BAMF 1.6.3

Was running BAMF 2.0-4
[Thunderbolt Android Development] Kroaker:
Just giving you the facts. It had all the other probs currently being listed for bricking, but I fixed it with a fresh battery and reflashing a kernal.
[Thunderbolt Android Development] BryanP:
SEM08G Running.

My phone lost it's virginity to Virusx, tried bamf then was on the cm7 the first day it hit the forum. Tried Bamf 2.05 then back to CM7 same day. Currently flashing Bamf 1.7 because of data & mms issues on CM7.

If we only post bricked to describe bootlooping bolts then the thread would be easier to search.
[Thunderbolt Android Development] jwterminator:
SEM08G

Non bricked - running froyo after reverting from bamf 2.0-5
[Thunderbolt Android Development] gsxraddict:
SEM08G

Running bamf 2.0 beta5

Non bricked
[Thunderbolt Android Development] onsht1kll:
SEM08G

not bricked
[Thunderbolt Android Development] onyx_64:
SEM08G

Not bricked.
[Thunderbolt Android Development] rhcp011235:
# cat /sys/class/block/mmcblk0/device/name

SEM08G

# uname -a

Linux localhost 2.6.35.13-imoseyon-2.5.3test6-hg005e98d44f45-dirty #113 PREEMPT Fri May 20 14:39:56 PDT 2011 armv7l GNU/Linux

Running Bamf leaked GB radio etc.

No brick
[Thunderbolt Android Development] corenojoe:
Output: SEM08G

status: not bricked reverted to froyo from GB
[Thunderbolt Android Development] KDKobes:
Non-Brick

SEM08G

damit where are all the bricked devices at!!! everybody is so quick to replace them it seems.....at least it was caught before it got out of hand
[Thunderbolt Android Development] tekhna:
Isn't that what we're trying to find out, if there are any hidden bombs waiting to go off?
[Thunderbolt Android Development] psicrest:
We all got bricked rolled guys... It was well played... well played indeed...

never gonna give you up..

never gonna let you down..

never gonna run around and desert you.
[Thunderbolt Android Development] Makaveli1490:
SEM08G

non bricked
[Thunderbolt Android Development] nerozehl:
SEM08G - Nonbricked.

Latest CM7.
[Thunderbolt Android Development] 3083joe:
still on GB leak

Not Bricked

output: SEM08G
[Thunderbolt Android Development] Araya213:
SEM08G

Nonbricked

Froyo
[Thunderbolt Android Development] Mr. Toad:
Not-Brick

SEM08G

Currently on BAMF 1.7

Came from BAMF 2.0-5 and Gingeritis v1.0 Beta VIII before that.
[Thunderbolt Android Development] awtenterprise:
SEM08G

not bricked

AdamT
[Thunderbolt Android Development] craighwk:
Has anyone actually bricked their phone? SEM08G not bricked.
[Thunderbolt Android Development] scotty1223:
yup sounds like you are bricked... go to the andirc chat(link in jcase sig on first page) and see if they are still looking for info from s-off phones. if they are not,you can flash a stock ruu,wich will not fix your prollem if youre truly bricked,but youll have to to get the phone back to s-on and return it.

then i would go to the serial numbers thread,and report that you are bricked and what your serial# is.
[Thunderbolt Android Development] ILMF:
Ill check in with them tomorrow. Amazingly, my Dinc came back to life after a thorough drowning in the pool. Typing on it now. Missed this phone. Hopefully I can get a credit on my account for something else. All in all the bolt was/is for me like my wife. High maintenance.

Edit: Not bricked, reverting using JCase's return to stock method fixed it. MR1 RUU with the May OTA booted right up. I wonder if CWR somehow became corrupt?
[Thunderbolt Android Development] bimrluvr:
Is this a brick

With the sd card removed, I can get in to recovery by powering on with the VolDown pressed - but then I'm stuck with no way to flash.

When I put the sd card, it will only do HBOOT to do an update or, if I select reboot, it freezes at the initial HTC splash screen.

This all started when I tried to switch kernels using Rom Manager under Liquid Thunderbread 2.6. The only issue I was having at the time was that Adobe Flash Player gave audio, but no video. Can't switch back to the original kernel without flashing can I?
[Thunderbolt Android Development] scotty1223:
no,thats not a brick. you just need to restore a backup or flash something else.

my personal advice would be to stop using rom manager. use recovery to do things manually,its much safer,IMO.

you just need to stick your sd in a card reader and delete the PG05IMG file. and from now on,always delete or rename them for this reason. do not ever leave PG05IMG files lingering on your sd card after youve flashed them.
[Thunderbolt Android Development] tokafondo:
Hello all.

I have a Samsung GT-i9000, SEM08G chip, FwRev 0x90, date 04/2011.

The /data and /sdcard partitions are READ-ONLY. I cannot format them, delete them, erase them, nuke then... Nothing.

All the operations seem to be done, but when I restart the phone, all the info is still there.

No matter what do I do, and from where: the info still is there and...

Whatever 2.x.x rom I flash, I always get a lot of FC errors from apps in /data/app I cannot delete.

So for me, it's bugged.

Thanks.
[Thunderbolt Android Development] HOOKEDONDROID:
You'll probably have better luck asking for help in the appropriate forum. This is for the HTC thunderbolt...fyi
[Thunderbolt Android Development] 335Deezl:
SEM08G

NuSenseROM ReBorN 2.8 Android 4.0.4.

Running like a raped ape!
[Thunderbolt Android Development] joshnichols189:
Would this be happening if they didn't..?
[Thunderbolt Android Development] djbeanpole:
Think the better question is...

For anyone that has bricked, have they kept their phone so they can attempt to pull their number!
[Thunderbolt Android Development] houseboatwayne:
Non brick bamf 1.7 Froyo

SEM08G
[Thunderbolt Android Development] Zalyia38:
SEM08G

Was on 2.0-5, went back to 1.6.3 yesterday and stock radio then flashed 1.7

edit: not bricked
[Thunderbolt Android Development] dpadaddict:
Help

Can someone please help me?

I am trying to perform the command and this is what I get.

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd C:\android-sdk-windows\platform-tools

C:\android-sdk-windows\platform-tools>adb devices

List of devices attached

C:\android-sdk-windows\platform-tools>adb shell

error: device not found

C:\android-adk-windows\platform-tools>

I have not been to command prompt since flashing my very first ROM (Gingeritis), so I am not sure what I am doing wrong.

I rebooted the phone - debugging is checked.

THanks for the help
[Thunderbolt Android Development] boristhebladexx:
try rebooting your computer or phone then go back into adb and type "adb devices" it should be there now
[Thunderbolt Android Development] gsxraddict:
Try just running it in terminal I'm not at a computer and I did it that way.
[Thunderbolt Android Development] Zalyia38:
just open windows explorer and make sure you've got the right location of adb.exe.

Mines c:\android\tools cuz I wanted it shorter :)
[Thunderbolt Android Development] mar5hal:
SEM08G

Not Bricked

stock s off
[Thunderbolt Android Development] rycheme:
$ export PATH=/data/local/bin:$PATH

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

SEM08G

Not bricked, BAMF Remix 2.0.5.
[Thunderbolt Android Development] tylerkd07:
SEM08G

nonbricked

1.6.3 from ginger remix
[Thunderbolt Android Development] Araya213:
Same thing happened to me, I had to uninstall the adb driver and then rescan and install driver from HTC sync. Real pain in the butt but I think I remember getting new drivers to try to make GB disk mode work better.
[Thunderbolt Android Development] tanium:
Output: SEM08G

Posted from the thunderbolt.

Used Bamf toolkit terminal

Bamf 1.7 froyo

Was on Bamf gb remix before the fear set it.
[Thunderbolt Android Development] Jrocker23:
Output: SEM08G

Status: Nonbricked, Stock w/leaked update & radio with adrynalynes 4.47 kernal