yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] bp328i:
I really miss my OG Droid sometimes, that thing was bullet proof. I remember running sbf once and my dog ran by and ripped the usb cord out of my PC right in the middle of it. Just started over and ran the sbf again.

But to answer your question using an RUU is the same thing as sbf (for the most part).
[Thunderbolt Android Development] jcase:
sbf doesnt fix a physically damaged phone
[Thunderbolt Android Development] ERIFNOMI:
That pretty much it. From what I understand, RUU and SBF are just HTC and Motorola's abbreviation for ROM, in the most basic sense. RUU and SBF contain the ROM and other FW like radios.

So, flashing an RUU in hboot is like Moto's SBF.

EDIT:Others have said the same thing before me, my bad. Had this open in a tab before those people added that.
[Thunderbolt Android Development] hydRoponic chRonic:
where were you 2 1/2 hours ago!?! lol its all good. i shouldve just done that anyways. im a knuckle head.

downloaded from the first link. like i just said, im a knuckle head.
[Thunderbolt Android Development] crackedvenom2:
Lol. It happens.
[Thunderbolt Android Development] natenate360:
Stinks that I see this only shortly after finding or about the netflix patch only on GB.... Guess I should try CM7 then....
[Thunderbolt Android Development] nmtuna:
If I was running a GB rom, can I just flash a nandroid of a Froyo build and flash the old radios and be ok???
[Thunderbolt Android Development] CJeep:
Yes. That's what I did.
[Thunderbolt Android Development] sonofskywalker3:
If the bricks are cause by emmc corruption (which hasn't been proven yet, right?) then I think the questions you need to ask are these:

How often would the emmc normally be written to?

How often was the broken GB radio writing to it?

How many write cycles could a typical emmc chip handle?

If for example emmc is normally written to on average once per day, and can handle an average of 10,000 write cycles, but the GB radio was writing to it once per minute, then if you ran GB for 2 days, that would be 2 * 24 * 60 = 2,880 writes, leaving about 7120 days (or 19 1/2 years) left.

These numbers are totally made up, as is the concept. This wild theory is only valid if frequent emmc write cycles are actually causing the issue, AND emmc average life is measurable by X number of write cycles to total failure, and not bit by bit corruption.

The point of this post is simply to say, if you don't have issues, don't trade your phone in. that simple. It is a real problem, and reverting to froyo is the right thing to do, but statistically the number of people actually affected so far is insignificant.
[Thunderbolt Android Development] dc8783:
Same here im not going anywhere I had my phone rooted to GB for a while so it isnt bricking on me......
[Thunderbolt Android Development] joshnichols189:
While a concept, this is a good way to think about it if this is in fact the cause. Being as how each phone is going to always be different, maybe some can handle less writes to total failure (like you said, average of 10,000). But using this model would mean that if everyone that had the alpha radio was receiving more emmc writes than normal, eventually every phone running the alpha radio would experience this problem.

To the person above me.. your mindset is the reason there is so much flaming regarding this.. "I've had no problems so far" means NOTHING. Everyone who's phone has been stuck in this endless loop has had thought their phone was running fine until BAM. And to the person you quoted, no this did not happen to you because the problem people are experiencing is reboots in hboot. So this did not happen to you, and you were not able to flash a stock RUU to get out of this problem, as you had a completely different one.
[Thunderbolt Android Development] jcase:
I really don't care if people revert or not, but your logic is seriously flawed.

The other user's phones had GB on them for a "while" too, and were perfectly fine, until they bricked. Lets also consider, the leak hasn't been around even 2 weeks now, so unless you have the hookup and are holding out, you haven't been running it that long.
[Thunderbolt Android Development] crackedvenom2:
Ah man. I hope this gets fixed soon. Ive only been back on froyo a day and i dont like it at all
[Thunderbolt Android Development] LTL11:
So if I am reading all of these posts correctly as long as I have been running GB fine up until now I will not brick.

If I do go into the bootloop of death then as long as I have an RUU on my sd card I can fix it.

And if the above is wrong it is Jcase and Adryn's fault.

Got it. :rolleyes:
[Thunderbolt Android Development] joshnichols189:
+1

Your sarcasm makes me laugh. :)
[Thunderbolt Android Development] jcase:
Bricks are random, you can be fine for any length of time then brick.

Flashing an RUU does not fix this, those that claim it does, were more likely to have a a) bad rom flash of some kind or b) needed to wipe data/cache or c) maybe a bad recovery of some kind?
[Thunderbolt Android Development] LTL11:
I was completely kidding because those two items keep popping up over an over even though they have been debunked many times.

I reverted back as soon as you recommended.
[Thunderbolt Android Development] fronc:
Can anyone post a stock boot animation? If we have that, there's no way for Verizon to know for sure that we bricked this ourselves, and we'll all be covered under our warranties. Then we can take our chances...
[Thunderbolt Android Development] crackedvenom2:
http://xdaforums.com/showpost.php?p=13158067&postcount=10
[Thunderbolt Android Development] Carnage9270:
Mmmm not so sure about them not knowing. I think I read something posted around here somewhere that they are actively looking for signs of root (the insurance carriers). Not sure how they truly go about this but seems to me there would be signs of it in emmc etc.
[Thunderbolt Android Development] crackedvenom2:
But if the phone is bootlooping, are they going to sit there and try and figure that out, or just give you a phone?
[Thunderbolt Android Development] joshnichols189:
They'll give you a phone, then when they find out that you're rooted by digging deeper charge you full price for the one they gave you.
[Thunderbolt Android Development] crackedvenom2:
Good point
[Thunderbolt Android Development] whytecountry:
They're just going to give you a phone.

I took my phone to a verizon rep a couple weeks ago to get a new sim card, while he had the phone it booted into the bootloader for some reason, and he said "do you get this error screen often?" I said "let me take a look", quickly rebooted the device and said "no, never, that was weird..."

The moral of this story is that they don't know wtf is going on. Just hope you don't get that ONE rep who actually give a **** about their job.

If you're in an unrecoverable bootloop how are they going to find out you're rooted...? I GUESS there's a small chance they'd know to hold power and down button to get into bootloader...

Haha whatever I don't have manufacturer warranty because I bought mine on craigslist so I uninstalled last night!
[Thunderbolt Android Development] probotic:
my insurance is with BestBuy, good luck charging me for a new phone once you give me a new one.
[Thunderbolt Android Development] fronc:
I see your point, but why would the phone go through insurance carriers if under warranty?

Plus a busted EEMC or whatever you call the internal memory would only yeild data after a bit-for-bit sweep, no? How often do you really think they're going to do that to returned devices?

I'd much rather take my chances with this boot screen showing no signs of damage. Might not be 100% safe, but it'll get a new device in my hands immediately, and i'll be damned if Verizon's going to charge me after telling me in-store the swap is free. I'm sure I can wiggle out of that one if pressed..

Thanks for the feedback and cautious warning, though.
[Thunderbolt Android Development] fronc:
Just install this from recovery?

Edit: The bootaimation is located in systems/media/bootanimation.zip you just have to place your new bootanimation.zip over the old one. (use root explorer)
[Thunderbolt Android Development] joshnichols189:
I'm not sure how that shows he doesn't know what he's talking about, referring to the bootloader as an error screen isn't technically wrong, since you're not supposed to know how to get to that screen anyways, and it's a lot easier for them to say "error screen" than to say bootloader and have a customer ask a lot of questions..

besides, it's not the reps that actually look at the phone that gets replaced, it's the insurance companies.. so just because they give you a new phone doesn't mean you're off the hook.
[Thunderbolt Android Development] Carnage9270:
I think it's their insurance carriers that check. The rep will give you one no problem, that's their job to keep you happy. But I think if the insurance carriers perform their checks after receiving the phone from Verizon there could be some repercussions. Like a follow up phone call to notify you that you had voided your warranty and will be charged on your next statement.

Not saying that is what's going to happen, but as an insurance carrier I'd definately want to know why a phone failed. Especially if they are receiving an abnormal amount of them or if a rumor is in the mill about people flashing a Gingerbread leaked radio :P

I strongly doubt that the insurance companies themselves do the "checking". I'm sure they are sent back to HTC to be "resolved".
[Thunderbolt Android Development] luigi1111:
Hmm, OR we could stop being so silly about "needing" to keep our Gingerbread, because apparently there's some magical features in it that it has become impossible to live without, and just revert as JCase suggests.

Shoot, we've been on Froyo for a 1.5 months+ (with much of that time being on lesser ROMs than BAMF 1.6.3, etc.), and have only been on GB for a week or so. Going back (to Froyo, with a good selection of great ROMs) for a few days/a week/whatever 'til they figure this out isn't going to kill anyone, but it just might save your phone. :)

+1 to LTL11's post.
[Thunderbolt Android Development] joshnichols189:
Dude don't anger the mob.. those CRT animations and the lockscreen with four app shortcuts are srs bsns
[Thunderbolt Android Development] jcase:
Who cares if they revert, if they can take the risk and want to, let them.

My concern is the people that are unaware of how risky it is, or the morons claiming since they haven't bricked they wont.
[Thunderbolt Android Development] fronc:
To each, his own. Are the bootanimation.zip permissions supposed to be rw-r--r-- ?
[Thunderbolt Android Development] fronc:
Sometimes I need the rush of living dangerously. What can I say? :cool:
[Thunderbolt Android Development] jmotyka:
Really we shouldnt be worried about how we are going to pull an insurance scam we should all do without root and without s-off for the time being just to be on the safe side. I mean really how important is it for everyone to have root for everyday use, 90% of the people here want root cause they are flash happy, not because it benefits them in any way.
[Thunderbolt Android Development] jaysckap:
Me too, but is it really worth it? I knew about this problem i saw people coming on IRC with bricked phones but i didnt care, it couldnt happen to me. I have a company phone so a free replacement is not an issue for me. I just went back to Froyo acouple hours ago, not very happy about it but i feel better. We will be back on GB soon enough. So thanks Jcase for lookin out :)
[Thunderbolt Android Development] sublimaze:
I use AdFree, Autostarts & Bloat Freezer daily
[Thunderbolt Android Development] kdb424:
Shouldn't rom developers post warnings in their threads, or remove downloads? I mean, users can do what they want, but I'd like to have a warning if I find a thread linked to from google. Reverted myself, and lookin good thus far, hope it gets resolved.
[Thunderbolt Android Development] mastibeta:
You don't have to give up root and s off to roll back...read the whole root thread...that file takes you to rooted and s off bloated Rom
[Thunderbolt Android Development] corenojoe:
I have sent back a rooted phone after an insurance claim, as have several other people I know. Never had any issues, don't give them too much credit or believe that they really go in depth. They probably just hook the thing up to a computer and flash it right back to complete stock. How else have we never heard anything back at all?
[Thunderbolt Android Development] craighwk:
So I tried searching this thread but didn't see anytihng.. Ever since performing this procedure last night, I am getting a "General Error" when trying to send an SMS message. If I click details I get "Cause Code 65535" and "Error Class 3"

Any idea what that is or how I fixed it? I've tried power cycling the phone but same deal. I followed the instructions in the OP as listed.
[Thunderbolt Android Development] jaysckap:
Did you wipe everything and reflash
[Thunderbolt Android Development] bobby janow:
That is a judgement call on your part. It's not fair of you to say why or why not people flash. If it's because they are flash happy then so be it. If it benefits them to flash, whatever the reason, then that's all that matters. Even deleting a single app with root is valid.
[Thunderbolt Android Development] 00negative:
True.. but with out my question we wouldn't of got to hear the epic tale about a boy, his OG droid, and his dog
[Thunderbolt Android Development] crackedvenom2:
Haha! Thats funny.

EDIT: Is it me or are the pictures taken with froyo crappier? I thought my phone was taking pretty good pictures on GB. Ive taken like 5 today and they dont seem that great. Maybe its just me. Im not sure. Could just be a placebo effect lol
[Thunderbolt Android Development] dahotz:
Just reverted back to froyo. Thanks jcase for the warning. I mean, I know that we can do an insurance claim and get a new phone, or there is a "rush" living on the edge, but I will stick to the philosophy, "an ounce of prevention is worth a pound of cure". BTW, I love reading the community's comments. they are enjoyable, make me laugh, and think :)
[Thunderbolt Android Development] crackedvenom2:
Let us know how you are doing in a day or so. Id like to know. Very eager to get back to GB.
[Thunderbolt Android Development] albotz21:
what are you using 56k modem?
[Thunderbolt Android Development] psicrest:
Im just wondering if those people who got bricked has a Hardware version 0003.
[Thunderbolt Android Development] crackedvenom2:
It would be great if all of these people would get on the forums and give some details so were not all sitting here wondering and not have any clue about what they are running and doing, etc etc
[Thunderbolt Android Development] boingboingbilly:
Meh, I'm staying on GB. I know I shouldn't but I am. Finally for once everything on this phone is working perfectly for me...everything.

Btw - not that it is relevant, but I have never had an unsolicited reboot of my phone. I rooted the day I got it and have installed just about every radio, ROM, and Kernel created for this phone (some many times).

Hopefully this good fortune will continue, but I am going to take my chances.
[Thunderbolt Android Development] apthirdeye14:
This is the mind set that's gonna keep Verizon doing whatever it takes to squash the rooted community. Thx for doing your part to bring the heat from the carriers.

Just a thought or more like a conspiracy theory. What if this was an intentional leak on Verizon's part to eff us. Then when all u people that think ur gonna just take it in for warranty and get ur new phone, Verizon smiles and throws a fat charge on your bill after u get ur new phone. Just sayin. This is the weirdest full brick problem which causes me to think conspiracy. It's probably not the case, but its something to think about.
[Thunderbolt Android Development] jcase:
UPDATE

We might have a way to figure out who may brick and who may not, however I need a user who HAS bricked and who still has their phone to PM me or contact me on IRC
[Thunderbolt Android Development] joshnichols189:
There would be no point in them doing that and if proven they would be sued because it's illegal
[Thunderbolt Android Development] crackedvenom2:
Please someone have their phone readily available!
[Thunderbolt Android Development] psicrest:
How many are bricked?

This thread is getting long but theres only like 1% that posted that their phone got bricked. No exact details if they really tried a freshly charged battery from either external charger or swapped a battery from a froyo or stock Tbolt.

I believe there are also some tbolt that has hardware revisions, not sure if that data is relevant but that might be another thing to consider.
[Thunderbolt Android Development] boingboingbilly:
Yes, because it is in Verizon's best interest to bring (more) negative publicity to their flagship device to prevent the false replacement of less than 1% of the sold devices.

L

O

L

A bit penny wise and pound foolish, no?
[Thunderbolt Android Development] apthirdeye14:
They may be sued, but they might not lose. Would be hard to prove and its not an official release of software. It was a leak. Again I really don't think Verizon or any carrier would do something like that. Just my mind wondering on "what if's." What is for sure though is the carriers hate the rooted community. One of those reasons is bricking our phone and then claiming warrant. We need to be responsible with this. Otherwise they will keep chipping away at destroying this community.
[Thunderbolt Android Development] psicrest:
LOL only few people got bricked and they probably replaced their phone already.
[Thunderbolt Android Development] adrynalyne:
http://xdaforums.com/showthread.php?p=14181993#post14181993
[Thunderbolt Android Development] kdb424:
They possibly are using us as test subjects and seeing what happens. Just a though, though not likely.
[Thunderbolt Android Development] jcase:
UPDATE

We need info from brickers and non brickers please see

Please see here http://xdaforums.com/showthread.php?t=1098363
[Thunderbolt Android Development] boingboingbilly:
HATE?

I think hate is a bit strong. I realize you were saying carriers, but they are really a two-headed beast in the US.
[Thunderbolt Android Development] apthirdeye14:
Look, my point isn't Verizon trying to eff us. Conspiracy theories are very rarely true. My apologies to the thread for putting it in my post. I'm just frustrated that so many people are of the mindset to just stick to GB and if their phone brick they will just warranty it. We are hurting our own community with this mindset. If u don't think so, I suggest u read this article by p3droid. http://www.mydroidworld.com/forums/...otloaders-rooting-manufacturers-carriers.html
[Thunderbolt Android Development] poontab:
Oh Gawd p3? No thanks
[Thunderbolt Android Development] boingboingbilly:
That, my friend, is what society is filled with now - people who refuse to take personal responsibility for themselves and their actions. Blame is the game and when in doubt sue.
[Thunderbolt Android Development] trusteelfan:
Im playing it safe as well. Im reverting back to froyo. Cant risk bricking when this is my primary phone lol.
[Thunderbolt Android Development] Dstu03:
It is not illegal to root a device. Also it is illegal for any carrier to make a rooted device non functioning on their networks. Where they will crackdown on is tethering along with making devices harder to root. But there will always be a way to root.
[Thunderbolt Android Development] bigmew22:
My Thunderbolt bricked yesterday morning. The phone was fully charged and I recieved a phone call and than it just went crazy. It was force closing every application and i rebooted maybe 3 times and than it would not come on anymore. Changed batteries, let it charge, pull the battery. Nothing work. No bootloader or recovery mode available. Just would not come on. Sometimes i get a charge light and than it goes away. I was on gingeritis rom. Please revert back if you still have gingerbread
[Thunderbolt Android Development] biggiephat:
do you have this phone available... we need a bricked device to confirm something
[Thunderbolt Android Development] psicrest:
do you still have your phone?
[Thunderbolt Android Development] Dstu03:
Mine did the same this morning but it actually bootlooped til I pulled the battery
[Thunderbolt Android Development] jaysckap:
Is it bricked? If so we need your help
[Thunderbolt Android Development] bigmew22:
I still have the phone
[Thunderbolt Android Development] biggiephat:
please get in contact with jcase. we need to to run a command
[Thunderbolt Android Development] gregnice37:
I pm'd you, please go to that thread in the pm and help the devs out. The whole community would appreciate it.

Here's the thread again:

http://xdaforums.com/showthread.php?p=14186023&posted=1#post14186023
[Thunderbolt Android Development] jaysckap:
Join us on IRC please chat.andirc.net

#thunderbolt
[Thunderbolt Android Development] bigmew22:
How do I get intouch with jcase. Sorry but i dont do this thread thing much and do i need adb on my pc cause i need to install it. I just got a new laptop
[Thunderbolt Android Development] bigd5783:
I have just the radio if anyone wants it. I cant upload it here though.
[Thunderbolt Android Development] gregnice37:
jcase is the guy who started this thread. If you go to his name and click on it, you can send him a private message. Title it bricked phone and hopefully he can help you out. You will need adb since you are bricked, but they need a small piece of info that would be a huge help
[Thunderbolt Android Development] jcase:
http://chat.andirc.net:9090/?channels=#thunderbolt

follow that link and ask for me
[Thunderbolt Android Development] gregnice37:
Also, jcase is at this website where you can chat with him and other devs. Please go here:

Join us on IRC please chat.andirc.net

#thunderbolt
[Thunderbolt Android Development] jaysckap:
http://chat.andirc.net:9090/?channels=thunderbolt

please join us
[Thunderbolt Android Development] bigmew22:
Ok I will. I just Joined the other thread
[Thunderbolt Android Development] Carnage9270:
He's in the other thread Jcase.
[Thunderbolt Android Development] apthirdeye14:
It is definitely legal to root, however I do believe a carrier has the legal right to either throttle down rooted phone speeds or disconnect service to rooted phones. The Verizon tou does say they can terminate service if the device is altered from its manufactured specs (including software). So once you've signed the agreement, they can legally disconnect service to rooted devices and possible terminate service while charging a termination fee. I hate the fact this could happen. I am rooted and will stay rooted. I just want all those who will freely warranty their phones when they themselves fubar'd the device to know you are hurting yourselves and everyone else in the community.
[Thunderbolt Android Development] crackedvenom2:
This guy is throwing out ideas too.

http://xdaforums.com/showthread.php?t=1098531
[Thunderbolt Android Development] Bxrider117:
I noticed something today. I'm running Bamf remix GB and aside from heavy battery drain, my clock jumps ahead about 10 minutes periodically. I have it set for the system to figure out the time for me. I just find it weird and figured I would share this information.
[Thunderbolt Android Development] PJnc284:
Mine did that this morning. The alarm went off at 7am like it should have and a couple minutes later when I picked up the phone it said 7:15. Had to manual set the time and then set it to automatic and it seems to be working fine now.
[Thunderbolt Android Development] 66dude:
That's strange... mine did that this morning, too! I didn't try to set the clock manually, as I just woke up and was too tired to do anything. I checked the time about an hour later, and it resolved itself. I am running Remix 1.6.3 with the default 4.4.7 kernel.