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

Non-Bricked, and running BAMF 2.0 Remix B5

Flashed back to Froyo for a day and couldn't stand it any longer.
[Thunderbolt Android Development] JBO1018:
SEM08G

Not bricked, back on froyo

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] spartan141:
SEM08g

gingerbamf-remix 2.0-5

not bricked yet
[Thunderbolt Android Development] kdb424:
I have opted into sending HTC information both times I flashed the rom. Not the smartest thing, but I did. Not bricked yet, but if/when I do, I'll let you know. I'll be so mad if it bricks...
[Thunderbolt Android Development] voiceofid:
SEM08G

bone stock, just picked it up yesterday, about to root and put das bamf 2.0 on it
[Thunderbolt Android Development] KDKobes:
Sounds interesting...nonetheless you should contact jcase especially since your on ginger
[Thunderbolt Android Development] bdragon46:
SEM08G

Was running Gingeritis, now back on froyo.
[Thunderbolt Android Development] chkmate:
Thanks for the reply. I saw the one that thought he was bricked and wasn't. Then the other that didnt get back with his results.

//Tap'd on my TBolt while grounded\\
[Thunderbolt Android Development] dragonsportbikes:
Does anyone know when we saw the last reported brick? I think its been a few days now. Is it that we all got scared and went back or is the issue resolved? I wanna go back appointing bad. I don't think I've seen any reported bricks in a while
[Thunderbolt Android Development] KDKobes:
There aren't any new reported bricks because most people went back to froyo to be safe to keep it from happening...which is great otherwise it could have been a pandemic. Anyone who wants to continue using GB can do so

at their own risk

and most who are using it currently are taking one for the team and know the risk involved in doing so. Right now it seems kinda like a mix of a destruction derby and a race in a way...waiting to see who's phones gonna f'up first.
[Thunderbolt Android Development] jcase:
Last brick was last night, but was set s-on before I got to it
[Thunderbolt Android Development] junjlo:
Unbricked Same as everyone thus far
[Thunderbolt Android Development] jmaher1023:
Everything was working flawlessly, I switched to bamf 1.7 this morning and will attempt to run cat again.

Edit: I was able to successfully run cat after switching to bamf 1.7 and unfortunately(or maybe frotunately) I can only report the same chip as everyone else.
[Thunderbolt Android Development] rycheme:
I have not sent info to HTC.
[Thunderbolt Android Development] happimeal:
If you had a phone that was a potential for bricking for whatever reason, i wonder if you would get the same issue from the cat command whether you were on GB or froyo.
[Thunderbolt Android Development] jcase:
Its just a chip ID. We need to get one off a phone that is bricked and s-off (you have ~5 seconds to do it) before we can be certain its an offbrand emmc chip doing it.

It could just be a defective run of the sandisk chips, or it could be something entirely different.
[Thunderbolt Android Development] happimeal:
I have a question and I am just asking for my own learning.

I went to /sys/class/block/ with root explorer and noticed the properties of mmcblk0 is 0 bytes in size and there are no directories named mmcblk0 which i thought the cat command was looking for:

cat /sys/class/block/mmcblk0/device/name looks like it should be reading from a file named "name" inside of a directory named /sys/class/block/mmcblk0/device/

Only because I want to learn, what file exactly is this command reading and what is that file. I noticed all of the files in the /block/ directory are 0 bytes in size according to root explorer.

Thanks for helping a beginner broaden his knowledge!
[Thunderbolt Android Development] dahotz:
So I read the whole thread and I'm going back to gingerbread and hopefully my phone breaks. Since one person said a low internal memory could be a trigger I'm going to fill up my phone to the brim and see if it does anything.
[Thunderbolt Android Development] usafle:
I'm running G.B. fine. I'd revert back to Froyo but it seems people are having as many issues doing that as running G.B. Plus I'm not entirely sure the steps involved 100%. I just won't shut my phone off. Airplane mode, here I come. LoL

I'm keeping a close eye on this thread though.
[Thunderbolt Android Development] young0ne:
Here Is A real good question for everyone this as only happened to any that was use the GB radio right, but the CM7 people havent even seen this problem cuz they are using Froyo radio. so why not use a froyo radio in these builds?
[Thunderbolt Android Development] happimeal:
Gingerbread builds for the TBolt REQUIRE the gingerbread radio, although im not sure if they could be re-enginerred the other way, but it sounds like HTC designed the GB build this way.
[Thunderbolt Android Development] young0ne:
If thats the case why CM7 are using a froyo radio?
[Thunderbolt Android Development] midnight assassin:
Have you seen any with an alternate id? Bricked or otherwise.
[Thunderbolt Android Development] KDKobes:
CM7 isn't using the whole gingerbread rom more froyo....correct me if im wrong

I don't think so as of yet...most who bricked replaced their phones before they had an opportunity to test it
[Thunderbolt Android Development] young0ne:
Nope they are using GB 2.3. 4 so i dont know why they just cant use a froyo radio on the other roms
[Thunderbolt Android Development] KDKobes:
this is a misconception I believe also..it isn't actually..I know this was discussed somewhere, but can't remember where.
[Thunderbolt Android Development] SmiLey497:
SEM08G, reverted back to FroYo.

Not bricked.
[Thunderbolt Android Development] kdb424:
Reverting is not hard at all. If you made it to GB, you can revert. Just flash the froyo radio and install froyo ROM.

HTC reworked the way the radio "talked" to the rom in their 2.3 update. The developer making it work in cymod is hacking cymod together to "talk" to the froyo radios because that's all he had at the time. Hope that helps
[Thunderbolt Android Development] OCedHrt:
Interesting. I thought cymod was derived from AOSP? Which wouldn't be at the whim of HTC radio changes unless the OS itself has new interfaces for the radio? I did not need or get new radio on my HD2 from Froyo to GB. Of course they could've hacked something together in cymod though.
[Thunderbolt Android Development] happimeal:
Possibly because the thunderbolt radio has to support 4G LTE?
[Thunderbolt Android Development] young0ne:
Well what if we can get the dev help for the other Rom. And get the solution for this bricking
[Thunderbolt Android Development] mallen462:
Ok I had a bootloop this morning after 7 days of no restart I had to do a battery pull let it cool for a couple seconds and put it back in I'm running das bamf gingerbread
[Thunderbolt Android Development] happimeal:
Seems to me we should just be a little patient. This is an alpha radio leak, im sure HTC is still working on this as they have said the Tbolt will have official GB support this summer, and im sure a more stable version of the radio will be leaked well before then.
[Thunderbolt Android Development] woodsptw:
Data

JCase - if I'm going back to GB, I'm just wondering if there is data you want us to collect - now - ahead of a potential issue. If so, is there a utility that will gather it all.. Since my H/W Version says 0002, I'm assuming there are different versions. There is information under "Phone Identity" such as Device Serial number. I would assume the serial numbers are in sequence of the device build and knowing who has issues might help define a specific range of the devices that are prone to the defect (or point to something in HTC manufacturing process or supplier). If not h/w related there is all the software related data like ...Baseband, Kernel, Build, Software Number PRI Version PRL, ERI, etc.

Just a thought.
[Thunderbolt Android Development] dkoss:
SEM08G

Non Brick

Rooted, Stock, Debloated
[Thunderbolt Android Development] jcase:
Nope. Also the hw version number is apparently bullsh*t, it is changing between Firmware versions, and it shouldnt.
[Thunderbolt Android Development] Yufice:
Output: SEM08G

Status: Perfectly working, non bricked device.

Was on gingerbread for about a week, got scared and went back to froyo. Ran the command on Froyo to get my SEM08G output.
[Thunderbolt Android Development] zapote21:
Ran das Bamf 2.0 since it came out... No issues at all... Went back to 1.6.3 in the initial bricking panic...

But, no guts no glory, so back to Gingerbread...

WOOHOO

By the way, same result as all others on adb command...

Will advise if anything happens
[Thunderbolt Android Development] kazuma5401:
Been back on the "The ROM of Death" for 24 hrs. Did a 48 hr run before the gb melt down and switched to 1.6.3

Happy to report I get to suffer the question of impending doom for a few more min. No problems to report.... Yet. Had on random reboot after flash.... That's it

HTC thunderbolt

Das bamf 2.0-5

*DEATH ROM*
[Thunderbolt Android Development] kazuma5401:
Hey jcase, is there anything I can test or check while o await my death?

HTC thunderbolt

Das bamf 2.0-5

*DEATH ROM*
[Thunderbolt Android Development] mkilla:
Death Rom is perfect for me.
[Thunderbolt Android Development] mallen462:
+1
[Thunderbolt Android Development] jcase:
Nope, I need someone with a s off brick, who can use adb and follow directions

Sent from my Verizon Samsung Fascinated II
[Thunderbolt Android Development] doug piston:
Those on the GB leaked radio, some data for thought

http://pastebin.com/Cf7dUj5A

Line 207 = writing to the radio.

Could mean nothing, could mean time bomb no matter the emmc number.

/fear mongering
[Thunderbolt Android Development] azturbomini:
So on line 207, what am I actually looking at?

Thanks
[Thunderbolt Android Development] KDKobes:
I believe what you looking at, in laymen terms, is data being received from the network through the radio....essentially nothing...below that you see it being sent....basically uploading and downloading of data.
[Thunderbolt Android Development] oxidant11:
Can I run this in an emulator on my phone if so what do I enter?
[Thunderbolt Android Development] oxidant11:
Nvm I got it its the same as everyone's I know I'm an idiot for doing so but that's enough for me to go back gb I loath froyo now.
[Thunderbolt Android Development] midnight assassin:
Are we still at two useless bricks since this thread started?
[Thunderbolt Android Development] techspecs:
We may find that there is a strong negative correlation between having a brick and meeting your criteria. lol
[Thunderbolt Android Development] av8rdude:
GB Email from Google?

This is kinda related but I got the following email from google when I first installed a GB rom. Anyone else get this email? I do not have a Nexus S!

Cheers,

Scott

Welcome to Nexus S

Google and Samsung have partnered to bring you Nexus S, a pure Google experience phone. Learn more:

Register your Nexus S for access to premium support from Samsung

Visit our Nexus S Help page for a full list of help resources

Watch Nexus S on our YouTube channel

Once registered, you can contact Samsung directly at +1 855-EZ2NEXUSS (+1 855-392-6398) for support.

Sign up to to receive updates and promotions about Nexus S.

Enjoy!

The Android Team at Google

Google, Inc.

1600 Amphitheatre Parkway

Mountain View, CA 94043
[Thunderbolt Android Development] dlongb13:
How the heck is that related?
[Thunderbolt Android Development] piihb:
Output: SEM08G

::Status::

Nonbricked

Das Bamf Remix, 2.0-5

Imoseyon's 184Mhz-slot GB test

I ran fine on BAMF 2.0-5 for 4 days, got scured by the devs and went back to Froyo for 2 days. And I had to go back to the Gingerbread.
[Thunderbolt Android Development] Immolate:
Now I don't care who you are, that there was funny.
[Thunderbolt Android Development] currensy:
To the OP...if you want to brick you phone...unroot it S-On...

use this link http://www.androidpolice.com/2011/0...bolt-instructions-by-team-andirc-v1-20110318/

you will be bricked by step 6
[Thunderbolt Android Development] techspecs:
What? Is this supposed to be some kind of joke?
[Thunderbolt Android Development] superchilpil:
Wait.... Is that it? Is that why when someone gets a so called "brick" and recovers? And a few freaked out and tried to flash a stock ruu and it fried their phone somehow

It would explain we don't have any s-off bricks

>--The Game--<
[Thunderbolt Android Development] mjones1052:
You people are absolutely retarded, the root guide is in no way the cause of bricks. I've rooted 4 Thunderbolts without issue. And if your bricked by step 6, currensy, it's just user error and not knowing what your doing.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] tanium:
Your not the only one.

I got it as well.

Also I have this game called gangstar Miami.

After I put it back on the phone the game did a download update.

Then the world was all white.

But the update was called gangstarmiamisamsung.zip

Point is, the market or overall network some how thinks are phones are samsungs.

My thoughts are that maybe the bricks are from someone who has some odd app.

Then the phone does an update for that app and installs it and bang.

The samsung software crashes with the HTC software.

Hey it should be at least looked at.

1 some get an email saying welcome to nexus.

2 my phone downloaded an update for a Samsung phone.

It is strange guys.
[Thunderbolt Android Development] superchilpil:
Anything is possible, and that seems to also be a common step.in the bricks... They all went s-on so instead if calling people retarded think about it

I.might be wrong but prove it to.me.first :)

>--The Game--<
[Thunderbolt Android Development] currensy:
Unroot your phone; you use this method and I promise you'll brick it...download the files in this method; not your original PG05IMG files and you will be looping
[Thunderbolt Android Development] currensy:
I rooted and unrooted my thunderbolts with no problem buddy...i received a replacement that was updated to 1.13.605.7 and used this old method...I flash the first PG05IMG with S-on and then flashed the second one "S-on"when it was supposed to be S-off realizing that htc will boot then go back to hboot...got my new replacement updated 1.13.605.7 with the updated rooted method and it worked perfect...
[Thunderbolt Android Development] KDKobes:
This is where the confusion comes in...I think what currensy is refering to is more a bootloop and not an actual brick. Using that method CAN cause issues with some phones which is why it is outdated. Here's the con's...

Cons

No custom recovery [yet]

No custom kernels [yet]

The root procedure currently requires flashing a slightly older version of the firmware (RUU_Mecha_VERIZON_WWE_1.05.605.0_Radio_1.07.00.0108r_NV_8K_1.38_9K_1.54_release_166255), which could potentially have more bugs. Right now, we cannot confirm whether LTE/battery bugs are present in this version or not.

However, you can always flash back to stock, thereby losing root, if you experience problems (we will provide instructions for this very soon)

.

As you can see there was no recovery yet which would explain what he is talking about, BUT again not the issue at hand it seems. The issue we are having is the phone will reboot after so many

seconds

even if you are in recovery or hboot it doesn't matter there is no time to even let the phone run an P50IMG file through hboot before it restarts. Hope this clears it up.
[Thunderbolt Android Development] WormDoes:
Any official word yet on what's causing the bricks?
[Thunderbolt Android Development] jaysckap:
Not yet :)

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] jcase:
Instead of accusing my guide of bricking your phone, why not step back and think a little bit.

A) if you read the freaking guide on that link, you would know it says "Update: This method is outdated – please refer to this guide instead." meaning it is out of date. Learn to read, and follow directions.

B) Neither of my guides can brick your phone, unless you don't follow the guide.

No it is not possible. They went s-on after the brick, trying to fix the bricks.
[Thunderbolt Android Development] jcase:
That guide will not cause bootloops, but it is outdated and does not set the phone s-on. It is also CLEARLY marked outdated, and links the user to the new guide.

There is no way to update using that guide, and the emmc write protection is only partially disabled with it, meaning no clockwork recovery and no custom kernel.

Anyone who used that guide after release day (we had a new root on day 2 and updated that guide) is not very good at following directions, and has lost all right to complain.
[Thunderbolt Android Development] jcase:
You shouldn't be rooting your phones if you cant follow simple directions like the TWO BIG PINK WARNING BOXES on that page, saying not to use that guide as it is outdated, and points you to another one.

Still, it would not leave you with a brick, just an outdated phone that can't install custom recoveries/kernels/roms.

[YOUTUBE]JmvCpR45LKA[/YOUTUBE]​
[Thunderbolt Android Development] currensy:
if you read you will understand that I stated that I didn't use the updated version...I only said that the outdated version would brick your device...I'm not a pc whiz...i'm rooted so what???

k
[Thunderbolt Android Development] jcase:
You need to do more reading before commenting on serious subjects in the development forum with such certainty. You are only rooted because of our work, the same work you decided to falsely accuse of causing bricks.

There is no way the original guide could cause a brick unless you do something like pull the battery while it is downgrading.

again

[YOUTUBE]JmvCpR45LKA[/YOUTUBE]​
[Thunderbolt Android Development] currensy:
If you use the outdated guide for 1.13.605.7 you will be bricked...you will bootloop and there is nothing you can do about it.
[Thunderbolt Android Development] imneveral0ne:
Froyo

Working

SEM08G
[Thunderbolt Android Development] jcase:
Give me some evidence, why do you think that?

No, you will not bootloop using that guide on 1.13.605.7.

Want my evidence? I WROTE BOTH GUIDES.
[Thunderbolt Android Development] currensy:
one of the PG05IMG files may have been corrupt...i rooted with the guide that insist that you install superuser and reboot which bricked my phone, then use the guide that's already installed superuser in the PG05IMG file which was a success
[Thunderbolt Android Development] jcase:
You probably screwed up, user error was the reason I repacked the custom RUU to include su and super user. People did not follow directions, then made ridiculous complaints like you are doing. Claiming bricks, when they were not bricked.

Even if you screwed up on the root guide you linked to, you could still recover by flashing the signed 1.12.605.6 RUU.
[Thunderbolt Android Development] dino325:
You sir are a ****ing clown. Our developers such as Jcase are tirelessly searching for a answer to this bricking issue and people like you push these said developers away from the community. Need I remind you that Jcase and the other developers volunteer their time here so do us all a favor, gtfo and cease the bull**** trolling. Thanks to Jcase and the rest of the community for your efforts. Don't let trolls such as this guy lead you to believe that we all don't utterly appreciate all your hard work on this and other issues with our devices. Without you there would be no community.
[Thunderbolt Android Development] currensy:
Why did you update the guides...what was updated....Why wouldn't you use the one that isn't updated?

Could you possible brick your phone if you don't use the updated guide...Ya think?

I'm not putting your work down...I already said I screwed up not the person that wrote it..but if I screwed up anything, it's the PG05IMG file I downloaded...I didnt turn off my phone or anything...

The OP is trying to figure out why people are bricking their devices...I offer that he use that method if he wants to find out...I flash the 399MB file and it said S-On when i did it...Why would it say that...should it say S-off? I wrote everything into my ADB except for.......adb.exe to start?
[Thunderbolt Android Development] patdroid1:
even if this were true...that is still not a bricked device.
[Thunderbolt Android Development] currensy:
I don't entertain people like you scardina...keep on walking that way
[Thunderbolt Android Development] techspecs:
Fail. You need to shut your browser and enjoy your holiday weekend. You're not making yourself welcome here.
[Thunderbolt Android Development] currensy:
yea I only come here for the latest and greatest
[Thunderbolt Android Development] jaysckap:
Wow I just read your previous posts and topics, you are clueless I would just keep your mouth shut. If you want to say anything else I would thank jcase for getting root on your phone.

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] joshnichols189:
Learn to read..

Why did he update the guides? He answered your question before you even asked it.

And by the way, you don't even know wtf is going on in this thread, so why are you trying to pretend like you do? You even admitted it.

You're only half right, because if you would read the first post you would know that the brick we are looking for has nothing to do with user error, and nothing to do with the root process.
[Thunderbolt Android Development] jcase:
No you can not brick with any of my thunderbolt root guides.

The op and I are working together on this issue, I am aware of what we are doing and asking for.

Your posts are utter non-sense, and have nothing to do with any of this.

Sit back, read and learn, don't add false information to an already confusing issue.
[Thunderbolt Android Development] loonatik78:
Currensy, you sound like someone who junked their new toy cuz ya can't read, or think. Let me tell you about my rooting experience. I used a guide, presumably the outdated one, to try to root. It was posted at a developer's website, not XDA. I got a few steps in and adb wasn't replying like it should and the phone wasn't doing what the guide said it should. So, I engaged my BRAIN. I went to XDA, found the guide, noticed that there were changes, picked up where I left off with the other, and in about an hour, my 6 hour old TBolt was running Perfect Storm 1.4. I'm nowhere near being a dev, but I do know enough to know what these guys do takes time, education, creativity, and drive to do what these guys do, and to do it as much and as well as they do. I'm amazed how seriously they take their HOBBY, which is all it is. These guys pursue this hobby with a brand of passion, commitment, and professionalism often desperately lacking in those who do less challenging work for a paycheck. Even if you did brick your device by a method outlined by anyone here, you still have no right to complain for the simple fact the disclaimers are as plain as day. Pal, you're trying to defeat technology many people got paid good money to invent. That's what rooting this phone is. These guys undo that for free. Also, these guys aren't here to educate the masses. They being tools and products to the table and it is the obligation of the end user to use them correctly and to educate themselves. I'll venture a guess that's how these devs we have here earned their stripes. I doubt there's a college course out there called "Software Weakness Exploitation 312".
[Thunderbolt Android Development] mjones1052:
lmao, that post got to you, huh? Quoted me twice. Really though man, your pulling **** out of your ass and arguing with a proven developer about guides he wrote and countless hours he put in, ask the hundreds of rooted TBolt users what guide they rooted with, all his, your the exception that screwed up and can't admit it.