yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Chris Hansen:
That's not due to the ROM, kernel, or even phone. It's the network. My colleague had that yesterday on his Incredible.

With that said, I have a point I'd like to make... But first I want to express that I'm not bashing anyone, especially the developers. They have done amazing things for us, on their own time, no less. They're trying to play it safe by warning the public about a possible and serious problem, but with it all based on speculator, all I see in this thread is mass hysteria. Nobody knows the actual cause, yet many seem to think we do. I'm not trying to start a fight nor cause more panic, but what if the radio isn't the problem? What if the actual problem were, say, flashing the radio (any version)? I've seen a few cases reported of stock phones suffering the same problem, yet those seem to be overlooked. I've seen it on rooted phones, both Froyo and Gingerbread. Yet people are still sticking to it being the Alpha radio. That's like diagnosing a patient but leaving out symptoms. Again, not trying to hate, just pointing it out in hopes of progress.
[Thunderbolt Android Development] swimminsurfer256:
In recent news, scientists tried out their new time machine. Needless to say, something went wrong.
[Thunderbolt Android Development] funkybside:
FTFY ;-)

10char
[Thunderbolt Android Development] tats_06:
Yeah, I believe there was something going on with the network. My clock dis the same thing thus morning...

Anyways, I think some of the bricks that happened were user error. Sorry, don't mean to offend anyone but a single missed or incorrect step could lead to big problems.
[Thunderbolt Android Development] joshnichols189:
The unrooted/stock/froyo phones were not suffering the same problem.. anyone with a reboot now that gets stuck at the HTC screen is going to say they have the same problem, but it's not just sticking at the splash screen. It's reboots happening when booted, while in recovery, and while in hboot.
[Thunderbolt Android Development] Chris Hansen:
Quoted from this very thread:
[Thunderbolt Android Development] 00negative:
Has anybody talked to koush about the issue? There have been some updates to both clockwork recovery and to rom manager recently..

Just an idea or maybe if nothing else to tap into his expertise in the recovery end of things.
[Thunderbolt Android Development] bolt_of_thunder:
Kind of a stupid question but just want to make sure before I downgrade to froyo: Do I need to do anything with the kernel? Like flash a different one than I'm running now with the gb radio (imos 2.5.4test4). I assume I need to flash a froyo kernel. If so, which one do you recommend using with BAMF 1.7? Thank you!
[Thunderbolt Android Development] ska.t73:
When you flash a new ROM it will have a kernel with it.
[Thunderbolt Android Development] dpdurst:
I reflashed the MR 1 rooted release and then after that I just restored one of my Froyo backups. Didn't take long and all went nice and smooth.
[Thunderbolt Android Development] droid fetish:
I think aliens are trying to take over our android phones!!!!!!!!!!!
[Thunderbolt Android Development] Makaveli1490:
Where does the brick start? Once you try to get into bootloader or does it just randomly reboot over and over
[Thunderbolt Android Development] bking_soda:
So... My girlfriends phone is also SEM08G... No dice on it being any different. Sorry guys.
[Thunderbolt Android Development] BennyJr:
http://xdaforums.com/showthread.php?t=1045081

Any froyo radio from this thread would work?
[Thunderbolt Android Development] psufan5:
Agreed. Anyone that is on 2.2 when a phone bricking 2.3.4 is out is clearly a *****. Completely 100% agree.
[Thunderbolt Android Development] dajogejr:
It's quotes like this that will make us blame you for all GB issues...related or not...

:D:D

Going back to 1.6.3 remix was like an old pair of broken in jeans yesterday. Just a great fit...
[Thunderbolt Android Development] Zarboz:
i pay asurion for a reason

just tell them you were at a theme park riding a roller coster and your t-bolt fell out of your pocket and died (sounds stupid but works ive got at least 5 G1's 3 mytouch's and 2 HD2's using that)
[Thunderbolt Android Development] dave0373:
So if I'm running cm7 with a gb radio I'm safe?

Sent from my rooted Thunderbolt.
[Thunderbolt Android Development] arcanexvi:
While I dont share your excuse, I'll also be sticking with GB for now. If something happens it'll probably just get "lost."
[Thunderbolt Android Development] trikotret:
Just wanna thanks to all developers who gave us the opportunity to play with GB.
[Thunderbolt Android Development] OldManJames:
if you are running CM7 then you are either using a froyo radio or you have no data/voice
[Thunderbolt Android Development] Cubs2008:
Here's a question. Will the devs abandon working on the GB ROM's until the radios get stabilized or will they continue to support for the people staying with GB?
[Thunderbolt Android Development] swimminsurfer256:
My bet is BAMF will stop but Chingy seems to be inclined to continue Gingeritis
[Thunderbolt Android Development] BurnOne77:
Woohoo remix 1.7 lol.

I feel bad all the devs put alot of time and effort into GB, BAMF was awesome gingerbean was awesome, was gonna install remix GB today... oh well 1.6.3 remix is the **** anyway.
[Thunderbolt Android Development] mzimand:
I just reverted back using the following:

Wiped data 3 times and dalvik 2 times

Flashed my Froyo Backup

Using ADB, reboot to bootloader type:

adb shell

reboot bootloader

If in fastboot mode, switch to bootloader mode and allow the updated radios to flash.

I actually missed Froyo and am glad to be back
[Thunderbolt Android Development] maizekidstill81:
Do we lose root when flashing this 400mb file in hboot?
[Thunderbolt Android Development] BennyJr:
When the next radio comes out they will most likely continue
[Thunderbolt Android Development] Cubs2008:
You shouldn't. This should be rooted stock MR1.
[Thunderbolt Android Development] GreginNH:
Thank you for this information and for looking out for us!

So, this file will put me back to stock...but still rooted, with the latest Froyo radio? and then I can wipe/ flash a froyo ROM?
[Thunderbolt Android Development] suzook:
Yup. Its not a true brick. Its fixable.
[Thunderbolt Android Development] maizekidstill81:
Sweet waiting for download to complete then flashing
[Thunderbolt Android Development] hydRoponic chRonic:
I'm with you on this one, I'm taking the risk. FID!

Sent from my ADR6400L
[Thunderbolt Android Development] Droid_ALM2ND:
Back to froyo I go. Neflix and cool lock screens is not worth a brick tbolt
[Thunderbolt Android Development] dakoop:
Did they ever say how many bricks?

Thunderbolted
[Thunderbolt Android Development] khanam:
What's strange is that in this survey we have not seen any non sem08g answers.

Sent from my thunderbolt
[Thunderbolt Android Development] wethead4:
If you brick your phone can't you go to verizon for a replacement? How will they know your phone is rooted if it cat get past the splash screen
[Thunderbolt Android Development] jaysckap:
The brick that is happening bootloops in recovery if they wanted they could see the radio that's on the phone (leaked radio=root)
[Thunderbolt Android Development] corenojoe:
Don't give them too much credit, the people at the store don't know enough to check that stuff and once it gets past there they don't care anyway, they'll just flash it to completely stock and resell it. I've sent back a rooted phone before, no issues.
[Thunderbolt Android Development] jasek78:
i just got this last night, i was looping and couldn't get into recovery because i still had the pmg file on my sd card, so what i did was put my sd card in my old dinc and got to the file to remove it from there, reflashed the rom and it works fine so who knows, to be safe im going back to froyo for now just wondering since i had a nandroid if i can restore that?.......

Edit: nope it still has the GB radios so gonna do the mr1 ruu i guess
[Thunderbolt Android Development] techspecs:
You can flash just the radios and use your backup...

http://xdaforums.com/showthread.php?t=1045081
[Thunderbolt Android Development] dlongb13:
If you recovered then you didn't get this. What is so hard to understand about a Brick. Its not recoverable. If you recovered it, it wasn't this problem. Did you bother to read the thread?
[Thunderbolt Android Development] jdphilly:
Well my phone is bricked I tried everthing and it just keep looping even after restoring to stock s-on ...so people this bricking stuff is the real deal ...I had went back to froyo started missing gingerbread and went back, an hour later i was bricked i just hope verizon dont find out and charge me 300 for a replacement edit: my new phone will arrive Tuesday
[Thunderbolt Android Development] tecknical:
go talk to jcase in IRC
[Thunderbolt Android Development] jdphilly:
too late i"m back to s-on
[Thunderbolt Android Development] onyx_64:
Were you undervolting or overclocking your kernel?
[Thunderbolt Android Development] jaysckap:
Did you by chance run that command to check your emmc

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] KDKobes:
+1!!!!!!! Would really like to know what it was set at too
[Thunderbolt Android Development] jasek78:
yup yup, i flashed the mr1 ruu just to be safe and then installed my backup. :)
[Thunderbolt Android Development] jasek78:
yes i did read the tread, and the part about boot looping the rom and recovery boot looping as well and that is what my phone was doing, the point in putting my post up here was so if anyone else was having the issue i had they would be able to read my post and fix the problem.....why do people constantly have to post BS about other peoples posts, if what i posted doesn't pertain to you then move on.

.........

FYI, you can recover your phone from a soft brick.
[Thunderbolt Android Development] Cubs2008:
If Sense 3 weather was a woman I would leave my wife for it. ;)
[Thunderbolt Android Development] jaysckap:
Holy ****, I couldn't have said it better

Edit: and the rest of it is like sense 3 weather's hot mom

Sent from my HTC Thunderbolt BAMF ROM OF DEATH
[Thunderbolt Android Development] oxidant11:
Yeah everyone in my store except me and one other guy wouldn't even know what a radio in cell phone is...and as far as us two I check for water damage or physical and try to hard reset because that what they ask me to do, :)
[Thunderbolt Android Development] techspecs:
I did the exact same. :D
[Thunderbolt Android Development] psufan5:
So you guys are coming out of the closet?
[Thunderbolt Android Development] Cubs2008:
LOL no...but look at it this way.

Sense 3 weather =

Froyo weather =

I'm running Bamf 1.6.3 remix and I press on the weather in the clock widget and hope for it to turn into Sense 3 weather but it never does. I have as much of a chance of seeing Sense 3 weather on Froyo as I do of hooking up with Charlize. That makes Cubs a sad panda. :(
[Thunderbolt Android Development] woodsptw:
I'd love an excuse to go back to GB. It would be nice to know something relevant/unique about one of these mysterious bricked phones.... their hardware is different or too much overclocking or ??

Thanks to all of you back on GB (and the suspect radio/hw combo). While I don't wish a brick on you... I'm glad you are willing to lay it on the line.
[Thunderbolt Android Development] Immolate:
You people with Rosanne Barr on your phone should really man up and come back.

Those pics pretty much express my before-and-after state of mind.
[Thunderbolt Android Development] djkeller3:
That, as of right now, includes me. I was looking at the screenshots of the 2.0 beta 5 REMIX and just couldn't resist (I went back to Froyo from 2.0 b5 before seeing the Remix).

No problems whatsoever, though I realize I may now have a ticking time bomb, but if I do and she bricks, then I will have done so in the name of research. I will simply send my dead TB to JCase and get another one. After all, it is a replaceable object, not quite human, albeit very close at times!
[Thunderbolt Android Development] Cubs2008:
There are a ton of good things about Froyo (Disk drive actually works without silly Internet Passthrough, Pandora has no problem, the bamf mods from zhp and butch...I mean we get that awesome clear notification bar that covers the whole top of the notifications and I just put the carbon fiber dialer on too. Not to mention Landscape Rosie...oh how I've missed Landscape Rosie) but Sense 3 weather is just too awesome.

I can say that I donated $100 to Adrynalyne for a reason. He knows what the (bleep) he's talking about. If two of the most competent individuals in this entire land of custom Tbolt work (jcase and Ad) tell us to take a break from what possibly could be an unstable leak that could brick our phone it's worth the small number of days we'll have to wait before they can give us an all clear on GB.

We were on Froyo for a long while before that leak actually hit so we should be able to go back and live with Froyo for a little while longer. Patience in the short run = winning (DUH!) in the long run. :) But damn it's not easy living with Roseanne Barr weather. *sheds tear knowing Charlize is so close yet so far away*
[Thunderbolt Android Development] dlongb13:
There is still zero proof its the GB radio that's causing the problems directly. They are just trying to.cover the angles and hopefully narrow down the suspect.
[Thunderbolt Android Development] djkeller3:
So just how many bricks have there been?

And how do you check to see which chipset you have (standard or non-standard?)
[Thunderbolt Android Development] Immolate:
The fact that it hasn't happened on Froyo or CM7, while not proof, is indicative.
[Thunderbolt Android Development] Immolate:
Check the OP and run the command in a terminal emulator (on your phone). If it says SEM08G then you have the standard chipset.
[Thunderbolt Android Development] Cubs2008:
Yeah I'm aware of that. IF it's the 3rd party EMMC then it's no wonder there were all these confirmations of the same chipset being safe. I still am holding out that somebody with a bricked Bolt will get the info to them so we can finally put the GB radios as the cause to bed.
[Thunderbolt Android Development] thewebsiteisdown:
Case;

My wife's phone is acting funny and its stock.. it just arrived here Thursday. It's been randomly rebooting and acting funny with text messages sending three at a time. I fixed the text messaging issue for her already though.

You think this might be one of the possible future brikers? I posted earlier already though that her phone has the normal chip though . Take that to thought.
[Thunderbolt Android Development] funkybside:
How did you fix the text issue? I get that sometimes...
[Thunderbolt Android Development] spartan141:
ok i guess i will take the plunge and be the test dummy. im going back to GB.BAMF remix 2.0-5. flashing it now. if it bricks i will send it off to Jcase and hopefully they will be able to find out if it is the radio that is the culprit. i currently haz S-off. will be in contact with Jcase hopefully not anytime soon.
[Thunderbolt Android Development] azturbomini:
I just flashed back to bamf gb. All is good so far...
[Thunderbolt Android Development] yareally:
If you want a nice weather screen, just get fancy widget. I dont see a point of sense just for a weather screen

https://market.android.com/details?id=com.anddoes.fancywidget

(screen is animated when viewed)
[Thunderbolt Android Development] patdroid1:
thank you for that...what a revelation...this was all about copying a weather widget and you found the key!!!!
[Thunderbolt Android Development] jdphilly:
No I didn't. See that until I restored
[Thunderbolt Android Development] jdphilly:
I was on bamf remix 2.0 b5 using tool kit overclock to 1.2 and under 245
[Thunderbolt Android Development] KDKobes:
Did you ever get random reboots?? Or ever use a Task Manager?? Since testing it I have noticed if overclocked past 1024 I would get random reboots, but realized it would only happen when a larger app was open and running for instance the browser mostly is when I would get a reboot. Since being down to 1024 I havent had a single reboot....interesting though. I have also noticed that on a froyo rom my memory wouldnt get below 200 or so and if tasks were killed average in the 260-280's...on GB it will average 190-170 with killed tasks, but will get drastically lower (80's or even lower) when not killing them. I wonder if this has anything to do with it at all.

one last question did you have fastboot on on startup???
[Thunderbolt Android Development] piihb:
I am back on the gingerbread! BAMFRemix 2.0beta5.

currently a NON-Brick.

cat /sys/class/block/mmcblk0/device/name = sem08g
[Thunderbolt Android Development] thewebsiteisdown:
As dumb as it sounds you have to pull the battery for five minutes. It fixes it so..
[Thunderbolt Android Development] jcase:
Removing the battery for any length of time does not fix these bricks.
[Thunderbolt Android Development] Cubs2008:
I already have Fancy Widget Pro (got it free from the Amazon Market.) It's not even close for me. Plus if Fancy Widget Pro could ever become a lock screen with shortcuts it might get into the same realm as Sense 3 weather. I like not even having to unlock my screen to see current weather conditions (and have a few shortcuts to work from without unlocking as well.) I also like the sense flip clock/weather widget much more than the digital flip clock that Fancy Widget Pro comes with.
[Thunderbolt Android Development] KDKobes:
Well I have had 2 random freezes while the screen is off and requires me to pull the battery to turn back on, but no bootloop yet (all in the last hour)

Running Gingersene undervolted to 245 overclocked to 1024 running 2.5.4test4 kernel...think it might be my beautiful widgets live wallpaper running on cpu hog for the animations. gonna shut it down and see if it does it again since before I had it off and didn't have this issue until I turned it on.
[Thunderbolt Android Development] seang:
i had this happen, and i reverted the day before all the chaos ensued.

i didnt like the charging issues, and then that happened. i knew something wasnt right.
[Thunderbolt Android Development] onyx_64:
ok, thanks. Perhaps there should be a separate poll on whether ppl were undervolting or OC'ing when the phone got busted. Undervolting can be equally dangerous as OC'ing, if not more! And its not about the chip getting heated up. There are limits of voltage, frequency and temperature within which the system should operate.. If you undervolt it, it may not meet its internal timing requirements and it might crap out. yes, it also depends on the ambient temerature. It may be okay for a few days, and then crap out.

And perhaps the SanDisk MMCs are more reliable to corruption being caused by OC'ing or undervolting.. I dont have knowledge of thunderbolts h/w architecture and emmc interface, so this is just my guess. I cant confirm this. But ppl should be careful of OC'ing/UV'ing beyond certain limits anyway.
[Thunderbolt Android Development] djkeller3:
I keep mine over-clocked to 1.4 Ghz all the time. Sometimes I overclock the minimum to 1.4 as well if I'm showing off the phone. I've never really had any issues keeping clock speed completely maxed out.
[Thunderbolt Android Development] KDKobes:
I cant help, but wonder either if its a combination of overclocking/undervolting and cpu usage at the time of crash causing the chip to fry essentially. just an opinion though. maybe someone with more knowledge on this could shine some light on it.
[Thunderbolt Android Development] djb28:
I do not know where the HTC weather app pulls from, But it is always 12 degrees off from what my current weather is. Its crap!
[Thunderbolt Android Development] KDKobes:
well since removing cpu hog option from weather widgets it hasn't froze up again...very interesting...undervolting issue I wonder?? Since this occured when the phones screen was off I would assume its not getting enough juice that it requires during this time and causes a freeze which might reiterate the theory of undervolting/overclocking and massive cpu usage at the time of crash.
[Thunderbolt Android Development] BennyJr:
Looks like ppl are turning back to gb.....
[Thunderbolt Android Development] azturbomini:
Just throwing information around.

Running BAMF 2.0beta5 and IMO's 2.5.4test4 kernel.

I have SetCPU set to 1.4Ghz, 245Mhz interactiveX

I also have the CPU settings in the toolbox set the same. (I have not tweaked the the kernel)

My battery life has been great. No rebooting etc...
[Thunderbolt Android Development] jcase:
Maybe someone will get a brick, and not flash an RUU then. So we can investigate this more.

s-on prevents us from looking at it
[Thunderbolt Android Development] happimeal:
Jcase,

How are people getting bricks, then able to flash the RUU.

Also I posted this in the other bricking thread but hope maybe someone can shed some light on it here. I have googled the different directory names, I have googled different "mmcblk" combinations hoping to find answers on my own but most of my results seem to be related to SD card mounting and partitioning which doesnt seem like this is what were doing here.

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.

I realize the answer may be over my head, but if I want to know more, will give me a place to start.

Thank You!
[Thunderbolt Android Development] psicrest:
I have a very strong feeling that the brick issues are directly related to battery or overheating of the phone.

It just happen that the trend when people are having bricks is when the GB leak was at its peak.

Also there are known issues about battery charging and phone overheating on GB i praise imoseyon for working on his kernels and patching those issues.

Im still on my GB and just recently installed imoseyon's latest kernel. I do have some random reboots from time to time, but it doesn't bother my day to day phone operation. But if ever i get bricked, i will send you my dmesg before i bring my phone to verizon.
[Thunderbolt Android Development] happimeal:
Downloading BAMF remix for GB now, if I get bricked, will keep it until testing is done!
[Thunderbolt Android Development] Jaxidian:
Some system components can be accessed in a way that to you or me would make it look like it's a file on the file system, but in fact you're actually triggering some hooks into some part of Android (the kernel, perhaps? I'm too ignorant to talk too much about this) that actually talk to system components. Windows does this too with LPT and other things. Again, somebody more familiar with these things than me can explain it much better, but that's what this is doing.

Sorry for such a crappy explanation there. :p
[Thunderbolt Android Development] happimeal:
Thank you.
[Thunderbolt Android Development] mp3sum:
Me.

/10 chars 10 chars 10 chars
[Thunderbolt Android Development] djkeller3:
Does that mean you bricked?
[Thunderbolt Android Development] Jaxidian:
I turned back to GB with the intention of either having a very pretty lockscreen or bricking and helping out (yes, keeping S-Off). I'll take either.
[Thunderbolt Android Development] happimeal:
Same here, I have no developer experience but if my contribution can be a test subject for figuring this problem out, than so be it.

EDIT: officially back on GB bamf remix.
[Thunderbolt Android Development] Jaxidian:
You do realize that you're about to trash a $400 phone, right? I recommend you stick to Froyo and do NOT follow my lead.
[Thunderbolt Android Development] happimeal:
Not following anyone, already was downloading Bamf Remix when I posted.