• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help BootLoader Stuck

Hey Everyone, new to these forums. I've owned an OG droid (rooted/custom rom'd etc...) and now a droid 2 since i finally tore up my first droid, so my experience with the X is just what i've read lately.
----Intro Over------

Anyways to the point, my aunt just recently dropped some water on her phone and stuck it in rice for hours and when rebooted the bootloader popped up. I told her I could probably get it since w/ RSDLite and flashing its really hard to brick your phone.

I've tried flashing a new .sbf but nothing works. I've also used the bootable linux script and that too doesn't work. What's happening is after it is finished I can't reboot into recovery no matter what I try. The boot loader just keeps popping up.

She has no way of knowing what OS or anything she was on so its all guesswork. But, I can't get her out of the boot loader and with water damage her warranty won't cover it. Any help is appreciated!

Oh yeah, no worries about battery because friends can charge them for us... and I was going to place this in Root forum but figured it was support and she had not had her phone rooted.
 
CaligulAvid,

I'm fearful that a few hours might not have been enough...only because of what you are experiencing and from what I've read others suggest before about trying to dry it out for a longer duration (i.e., a few days; although I've also read posts by users that had run their HTC Droid Eris through a complete washing cycle and it came out okay :eek: ...it surely depends on the phone).

I've read that getting the battery/power removed as quickly as possible after exposure makes a big difference. Also, the amount of minerals in the water also is apparently what really jams-up the phone since its these little guys that do the damage to the circuitry.

I also think there's more than one .sbf file that you could try. I don't know which one you flashed, but it probably couldn't hurt to try one of the "other" ones. I've yet to have to SBF, so I'm not the best resource re. that, but I think that the bootloader version determines which .sbf file is right to flash.

Cheers and good luck to you.
 
If water damage is the problem... would the boot loader even come on? The reason I ask is because I ruined my droid 1 with water damage and nothing would come on... it was truly bricked.

I'm going to try and load another .sbf because thats all I know to do. The current version of the bootloader is now 340 because that's what the linux script i ran set it to.

Anybody have any other suggestions... a Droid X hangs in the balance :P
 
If water damage is the problem... would the boot loader even come on? The reason I ask is because I ruined my droid 1 with water damage and nothing would come on... it was truly bricked.

I'm going to try and load another .sbf because thats all I know to do. The current version of the bootloader is now 340 because that's what the linux script i ran set it to.

Anybody have any other suggestions... a Droid X hangs in the balance :P

Don't know for sure, but I've read a lot of threads over in the HTC Eris section re. varying levels of functionality post water exposure.

Here's a fairly recent water-related DX thread that might help a little (no real SBF discussions in there, but the folks that did post there are very SBF-conversant):

http://androidforums.com/motorola-droid-x/380080-my-x-went-swimming.html

Good luck!
 
I appreciate the link. Read through it and it was mostly all insurance related questions and which phone they should get.

Did read the 48hrs of rice instead of the 3 she used but not much I could do about it, apparently she just spilled water on it while it was powered on and didn't think it would be that bad hence just a quick little dip in the rice.

I'm still playing with it, if I could just get it to boot once... :)
 
Water damage can do all sorts of things to a phone.

If it was a tiny amount of water, the damage could be isolated to just that part it touched (LCD, digitizer, charging circuit, speaker, etc).

If it was a large amount of water, the phone can be completely dead or actually revived (until it rusts to death) after drying out. It all depends on what touches the water first... ie. if the battery circuits makes contact first, the power could shut down and your phone never damaged, if a main chip drawing lots of power touches the water first, that power blows up a bunch of things and the phone is dead.

Edit - if the phone tries to boot and something doesn't start right, it goes to the bootloader... that is why some damaged phones will power up to the bootloader, but no amount of sbf'ing will fix it.

If water damage is the problem... would the boot loader even come on? The reason I ask is because I ruined my droid 1 with water damage and nothing would come on... it was truly bricked.

I'm going to try and load another .sbf because thats all I know to do. The current version of the bootloader is now 340 because that's what the linux script i ran set it to.

Anybody have any other suggestions... a Droid X hangs in the balance :P
 
Back
Top Bottom