*LOOK* Trying To Fix a Droid that wont boot up.

---

i purchased this motorola droid from a friend for 20 bucks, anytime u plug it into an outlet and try to power it on it comes up and says Battery To Low To Program on the boot loader screen, well i got past this by cutting up a USB cable and connecting the positive and negative to the battery connectors inside the phone like this...




Now im at the boot loader screen that says...



I have installed the RSDLITE 4.9 and the latest Motorola Drivers from Motorola, and i cant get RSDLite to find my phone at all, even if i check the first come first serve option under config, the only way i can get it to recognize it is to roll back from RSDLite 4.9 back to 4.5.3 and then it will recognize it and say its connected but when i add the .sbf file and hit start i get this error...

"Device SE flash OMAP3430 MI is not supported
Failed flashing process unable to find initialization values INI file (0x7029)"

Im not a beginner in anyway when it comes to android ive been messing with them for about a year now started out with a droid and then moved over to sprint where i have a rooted EVO that i mess with alot, if there is anything anyone can think of to help id really appreciate it im out of ideas and i hate to just throw in the towel and say its broke, the phone will go into recovery when i try to do a factory wipe it just gives me a bunch of E: open dev then says it ran out of trys, clears my cache and data and thats it, i still get the white M screen and all that just when i try to power it up it goes straight to the bootloader 2C.7C screen. Ive uninstalled and reinstalled each version of RSDLite from 4.5 all the way up to 4.9 as well as old and new motorola usb drivers as well as rebooting my machine each time. When i plug the phone in after holding Up + Power my computer does recognize the Motorola SE Flash interface or whatever it says when you plug them in and load the boot loader so idk please help...


**EDIT**
As far as i know this phone was not rooted when i got it and is not the phone in my signature, the guy said one day it just started giving him the low power cannot program screen.

really? no one has any ideas?

The first thing I would do is find out if the phone had been rooted. If so the answer could be as simple as flashing a rom onto it if you can get to recovery. I'm pretty new to working with rooted devices and it seems you've come to the wrong place to discuss this phone as it seems not many people care about the Droid. Its more about the Milestone here.

If the device isn't rooted and you do decide to break down, you could call Verizon or Motorola (depending on who you want to deal with) and see about getting a replacement phone.

The droid is pretty fun to mess with and it seems that there are a lot of cool things you can do with it. It doesn't have some of the hardware that the newer phones have, so some of the apps/mods/addons wont work the way you want them to, but its still fun to have a phone around that you can constantly test on and work with.

I wish you the best of luck with this my friend and I hope that some how I helped with this. I'm looking forward to finding out if you got your "Dinodroid" running again lol.

Originally Posted by Mastur Mynd

The first thing I would do is find out if the phone had been rooted. If so the answer could be as simple as flashing a rom onto it if you can get to recovery. I'm pretty new to working with rooted devices and it seems you've come to the wrong place to discuss this phone as it seems not many people care about the Droid. Its more about the Milestone here.

If the device isn't rooted and you do decide to break down, you could call Verizon or Motorola (depending on who you want to deal with) and see about getting a replacement phone.

The droid is pretty fun to mess with and it seems that there are a lot of cool things you can do with it. It doesn't have some of the hardware that the newer phones have, so some of the apps/mods/addons wont work the way you want them to, but its still fun to have a phone around that you can constantly test on and work with.

I wish you the best of luck with this my friend and I hope that some how I helped with this. I'm looking forward to finding out if you got your "Dinodroid" running again lol.

Considering this is the section for droid its the right place to come. Just because more user have milestones does not mean theres not someone willing to help.

As for the droid what .sbf file are you trying to flash? You just said you flashing a .sbf file you didn't say exactly what? I'm guessing a custom rom image or a stock version of the droid. You might wanna double check the sbf your using to make sure its for the droid and not milestone. Don't know much about the droid but thats the first thing Id check.

well i have made some progress, my cousin has a moto droid 1 and i swapped his battery in with mine and what do you know, phone fired right up! I took the phone home, plugged it into a charger with the original battery and it worked, battery even started charging. Well... Soon after me messing with it for probably an hour or 2 the phone starts randomly rebooting and now will only start up to the bootloader screen. Im thinking the battery could be bad and its maybe sending mixed voltages to the phone and making it operate radicly? I know these phone are suppose to operate at a certain "safe" voltage in order to work correctly and im thinking that may be why cutting up the USB cable and connecting it to the battery terminals of the phone may have not worked? Im thinking the battery may be bad and the phone is trying to protect itself from being shorted out? Idk just an idea. So i ordered a brand new droid battery from amazon so we will see what happens once it gets here.

And for Mastur Mynd, thanks for the advice, thankfully this isnt my main phone, i have a evo 4g on sprint and this phone is just for tinkering i figured i could fix it and if not im only out 20 bucks and my time. Hopefully the battery works tho because the phone is MINT and it worked perfectly for the short time i got it to fire up.

TaintedCross - as far as i know the phone wasnt rooted, the guy said he spilt water on the table the phone was on and the water ran underneath the phone and didnt actually get on it, so thats why im thinking its just the battery shorting out. I doubled checked the .sbf files like 10 times downloading them from differnt websites and stuff so i know thats not the problem.

I had an incredibly similar problem trying to repair a friend's Droid X. It was water damage to the boot sector. If you can get it to boot up again, I suggest flashing a new ROM via ClockworkMod. If you're lucky, it may fix the problem by overwriting the kernel, system, etc. where the problem could be located. If that doesn't work, try to .sbf about a hundred times. I spent a good 12 hours .sbfing over and over until it stuck. The only thing is that you HAVE to have +80% battery before attempting an .sbf flash because the phone doesn't charge while in the bootloader. Hope this helps.

Sent from my Droid using XDA Premium App