Database Users

[Q] R2D2 sbf

Does anyone have an sbf for the R2D2 Edition? I got a little too tweaky.
Thanks!

Lol.. not yet.. next time boostrap and make a back up
See if you can recover with the r2d2 rom from mydroidworld
http://www.4shared.com/file/rePStgcF/VZW_24_Full_ROM.html

I've got a nandroid backup on my SD card I jsut can't seem to get back to the bootstrapper.

Try booting up and then pull your battery and then try booting up again. See if that puts you into bootstrap.
Sent from my R2-D2 using XDA App

Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?

Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.

Try going back into bootstrap recovery and pushing the bootstrap recovery button again. Then the reboot recovery button. That should work. I had the same thing happen to me and that worked.
Sent from my DROID2 using Tapatalk

hyatari said:
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Click to expand...
Click to collapse
Yeah, for whatever reason that often does cause my d2 to boot into cwm.. I think it replaces that weird battery startup thing, did anyone else get that when they first used their d2?
Sent from my DROID2 using XDA App

rexit1982 said:
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Click to expand...
Click to collapse
If your D2 won't boot all the way up (which is what it sounds like), you may be able to get into CW Recovery by one of the methods below:
1. This is the most reliable way I've found: Boot up and pull battery when the boot animation starts (after the M logo disappears). Then reinsert battery and start up...should go to CW Recovery then. Thought I spell it out just in case you hadn't tried it that way specifically.
2. Make sure there is no 'update.zip' file in the root of your SD card - again make sure NO 'update.zip' file. Then boot into stock recovery, choose the apply update.zip option, and after it aborts, pull the battery and boot up again.
3. Another set of steps that might work:
-Boot into stock recovery by holding X while powering up
-Hit the magnifying glass on the keyboard to open recovery menu
-Highlight reboot and hit "ok" on the keyboard
-When you get the "M" screen pull the battery
-Power back up and it will go to Clockwork recovery
Good luck on that....
rexit1982 said:
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Click to expand...
Click to collapse
What makes you say that...what did you try and what happened? What version of RSD Lite did you use, and what was the failure/results, etc. This is a pretty surprising thing to hear.
R2D2 and D2 are the same HW as far as anyone has seen from specs, etc., the 2.2.20 SBF not working seems odd.
Thanks.

I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".

rexit1982 said:
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
Click to expand...
Click to collapse
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?

Redflea said:
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Click to expand...
Click to collapse
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
D2.35##
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
##Updated code
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.

If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.

newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Sounds like a good project...

rexit1982 said:
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
30.03**********
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
***I am not sure if these were the same numbers but the rest of the message is exact match
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
Click to expand...
Click to collapse
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.

Redflea said:
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Click to expand...
Click to collapse
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.

Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)

rexit1982 said:
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Click to expand...
Click to collapse
For the D2 (non-R2D2) it's 2.2.20, which is what the avaialable D2 SBF is...

bladearronwey said:
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
Click to expand...
Click to collapse
Thanks...
I believe I've also seen some comments that when flashing via a Windows box fails, that trying from a Linux setup can be more likely to be successful, but don't remember the details, so I may be garbling that info...

newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Please let me know when you have this livecd available. I too had the same response on my Droid 2. I wound up having to buy a new D2, but I'm still holding onto my old one...hoping one day I might be able to revive ut. LOL
Sent from my DROID2 using XDA App

[Q] Where Can I Get a Non Deodexed Stock Droid 2 Rom

Can someone please point me in the direction a stock, non deodexed, factory Droid 2 ROM. SBF isn't an option because that app doesn't play nice with my 64 bit version of Win7.

I meant to post this in the dev forum. Sorry mods.

Natty_lite said:
I meant to post this in the dev forum. Sorry mods.
Click to expand...
Click to collapse
No problem, I just moved it general to keep the forum order

Oh ok, guess I'm not crazy after all. Good deal.

FWIW, I had issues with the sbf from vista 64. Not sure which of these three things made it work, but I placed the sbf on my c: path, installed the very latest motorola connection app (and rebooted), and set the RSDLite executable to run as administrator. I used the version 4.8 of rsdlite. Might be worth another try...
Sent from my DROID2 using XDA App

You can also use this method which doesn't have the hassle with any drivers and can be used on any computer with a disk drive.

I have had no problems flashing my D2 on Win7 x64. You sure you have the correct drivers installed?

Yea, my drivers are fine. RSD sees my phone, but selecting the .sbf file doesn't give me the option to start, as if it is an invalid file. I can only assume its an Win7 64 problem, since it seems to be source of all of my issues.

newk8600 said:
You can also use this method which doesn't have the hassle with any drivers and can be used on any computer with a disk drive.
Click to expand...
Click to collapse
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??

Natty_lite said:
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??
Click to expand...
Click to collapse
Many see it as just stock with no adjustments. Why would you flash what you already started with or can "easily" .sbf back to?
I have Windows 7 Home Premium 64-bit and I have few issues flashing a .sbf file.
Please don't take offense - I only ask because it's orderly and even the smartest people have, admitted or not, missed some of these at one time.
Did you unzip the file you downloaded for the .sbf?
Have you tried uninstalling and reinstalling RSD Lite (Version 9)?
Where did your drivers come from?
Have you tried uninstalling and reinstalling your drivers?

Natty_lite said:
Yea, my drivers are fine. RSD sees my phone, but selecting the .sbf file doesn't give me the option to start, as if it is an invalid file. I can only assume its an Win7 64 problem, since it seems to be source of all of my issues.
Click to expand...
Click to collapse
Are you trying to flash while the phone is booted or while its in bootloader? The instructions around here recommend while it's booted, but really sbfs should be done from the bootloader.
Natty_lite said:
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??
Click to expand...
Click to collapse
ROM flashing on the D2 doesn't clear the system so you'll still have remnants from prior ROMs if they added anything.

@event121
I've installed the drivers several times. I don't think the drivers are the issue, because if they were, I doubt RSD would see my phone at all.
I've used 7,8, and 9

I just tried to do it while in the bootloader, RSD sees that the phone is connected, but I don't get the option to start after selectiong my DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file.
I had no issue doing this on my Droid 1 (using a 32 bit Win7)
**UPDATE**
The other file that's there: BL_D235_cdma_droid2_Consumer_replacer_HSPart.sbf DOES in fact give me the option to fllash. Should I go ahead and do it?

I fixed my problem for those who were interested. My solution was to use another computer. Win 7 64 bit is a crap shoot, and I'm far from the only person who has experienced difficulties.
That's what I would suggest to anyone else having problems using SBF

New GB update trouble

So i'm trying to put my friend's phone on the new update that just came out. I think i've done everything right. downloaded all the things i need; RSD, SBF, and drivers. Installed RSD and drivers, but RSD won't recognize the phone. it never pops in on the window.
The phone is currently running 2.2.1, Fission 2.5.7. i've tried rooting/ unrooting many times using z4 root.
so please anyone who can help,give me some advice.

I dealt with the same thing a couple of months ago. My problem turned out to be rsd lite version. Do you know which one you have? If it's 4.8 and it's not working, try 4.9. I assure you once you find the right version, and you're sure you have the right drivers, it will work. I almost gave up on it. Don't. I had no custom rom's, on froyo, rooted. Hope this helps.

SBF fails
I believe that means the drivers are not recognizing the phone - not sure where you got the drivers/program at but you might want to try a full flash using UNIX.
There is a thread on it stickied. You can burn a live CD of Ubuntu (means it boots from the CD and you don't lose your Windows installation) and do a full SBF from there.
Cheers.

I've tried on RSD Lite 4.8 and 4.9
and i got my drivers from the motorola site...
i'll try through ubuntu i guess. is there any way i can put it on a flash drive instead because i don't have any blank discs laying around.

Yes!!
http://www.ubuntu.com/download/ubuntu/download
Good Luck!

GolfnWrx said:
Yes!!
http://www.ubuntu.com/download/ubuntu/download
Good Luck!
Click to expand...
Click to collapse
so i downloaded and got Ubuntu running and all that.
so i'm trying to sbf via ubuntu means through the terminal and i get as far as "waiting for phone" and then i plug in and i get this:
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
[email protected]:~/Documents/sbf$
i've tried while rooted and not rooted and get the same either time.
i have no clue what i'm doing wrong and i'm getting really irritated. not only that but this isn't my phone and the owner is irritated as well.

Type sudo sbf_flash filename and that should work. Ubuntu is asking for root/admin privileges and sudo will do that. Also sudo will ask for a password-the password is what you log on with.
Hope this helps you.
Sent from my DROIDX using XDA App

did that. once it asks for the password it won't let me type anything in at all..

It won't show typing anything for security, but it is seeing what you type.
Sent from my DROIDX using XDA App

it won't even show the cursor moving?
so after i press enter what should i expect?

Hey juss wondering, if my fone is rooted, do i need to sbf it before i update to the new version?
Sent from my DROIDX using XDA App

DeriquedeCoux said:
it won't even show the cursor moving?
so after i press enter what should i expect?
Click to expand...
Click to collapse
No, it will not show the cursor moving. You just enter your password and hit enter and it will either accept it or say wrong password.

yeah i got it working.my friend is grateful, and i am grateful for your help, kind sir.

[Help] Wont boot past M

I Just bought a Droid X from my brother. I decided to root it and try to load a custom rom on it.
On to the problem...
I tried to install a rom onto the phone, but forgot to do a full wipe before I installed which caused the inability to boot past the Motorola logo.
Now here's the embarrassing part... I forgot to do a nand backup before I installed.
I've tried using RSD Lite, but it wont ever show the X. I know there's nothing wrong with the program because i connected my OG Droid to it and it showed right up.
I can boot into the stock recovery and bootloader. Is there anything that I can do to get this phone un-"bricked"
I don't really care if what I have to do will unroot my phone or take it back to its factory rom and settings or completely wipe everything. I just want it to work again. Everything else can either be redone or remade.
Thanks in advance

The only thing you can do is SBF. You can use RSD Lite or go the Linux way. (The Linux way is much easier and faster.)
You can Google for guides, and be sure that if you use RSD Lite that you have the correct drivers installed.
Sent from my DROIDX using XDA App

Mastur Mynd said:
...
I've tried using RSD Lite, but it wont ever show the X. I know there's nothing wrong with the program because i connected my OG Droid to it and it showed right up.
...
Click to expand...
Click to collapse
infazzdar said:
... You can use RSD Lite...
Click to expand...
Click to collapse
The correct drivers are installed, ive even un installed and reinstalled several times just to check. i'll be buying a linux powerd laptop from a friend here soon. Thanks for the tips

I hope you're not buying a Linux laptop especially for this; linux can be ran, without installation, through a cd or a flash drive.
There's even a Linux distribution floating around that is specifically for SBFing. Either way, good luck to you! =D
Sent from my DROIDX using XDA App

Make sure also that you are running RSD as an admin . Sometimes it will work without showing the device too

Yeah, I've been running as admin and in compatibility mode. O guess I can try to push a rom with it not showing. Could anyone link me to some details on how? or is it as simple as hook up in bootloader, select rom and hit start?
Also, I'm not buying the laptop specifically for this (the phone itself only cost me $20 with only the battery and battery cover missing). I intend on using it for the access to all of the developmental tools for Android. Thanks again to you both for the concern.
@infazzdar - What exactly is the "linux way" you spoke of in your first post? This seems like it may be the better way to do it

Mastur Mynd said:
Yeah, I've been running as admin and in compatibility mode. O guess I can try to push a rom with it not showing. Could anyone link me to some details on how? or is it as simple as hook up in bootloader, select rom and hit start?
Also, I'm not buying the laptop specifically for this (the phone itself only cost me $20 with only the battery and battery cover missing). I intend on using it for the access to all of the developmental tools for Android. Thanks again to you both for the concern.
@infazzdar - What exactly is the "linux way" you spoke of in your first post? This seems like it may be the better way to do it
Click to expand...
Click to collapse
The Linux way involves using terminal and an sbf flash script to SBF. Also, you don't have to install any drivers, it fails less, and I believe that it's faster than using RSD Lite.
Sent from my DROIDX using XDA App

I'm guessing there's a youtube video that can give me a step by step instructions to do that so I'll post back when I get the chance to do the SBF. Thanks a ton

Ok, somehow my rsdlite decided to recognise my phone now. its connecting, but when I choose the sbf, it says "chipset type 50 is not supported" in the status section
EDIT - YAY!! MY PHONE'S FIXED!!
Had to download a newer version of RSD lite and after that it worked like a charm. a HUUUUUGE thank you to you guys!!

Great to hear!
If this ever happens again and RSD lite just doesn't work you can always do the linux way like someone else said earlier. I can give you step by step instructions on that if you want, just send me a PM.

ljbaumer said:
Great to hear!
If this ever happens again and RSD lite just doesn't work you can always do the linux way like someone else said earlier. I can give you step by step instructions on that if you want, just send me a PM.
Click to expand...
Click to collapse
Yeah just use the distro! It's saved my butt plenty of times and only takes 5 minutes.

Bricked my phone trying to root-Need help getting it back to stock

Hey guys, let me just preface this by saying that this was my first time trying to root, and that I am still very unfamiliar with many of the things involved in rooting. That said, here is my problem and almost exactly what I did to get there.
Alright, so I chose last night to be the night when I finally rooted my Droid 2. I had android 2.3.4 gingerbread .621 version when I started. I ran through the easy windows install instructions first on this page: well, since I can't post links, the page is http: //rootzwiki . com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/ (just remove the spaces in the web address). This didn't work because being the noob that I am, I didn't realize how to flash the .sbf file using rsd lite (now I know how to do that I guess, just a little too late).
So I said screw that, I will just run the cd. I downloaded the .iso, burned it to cd, booted to cd, and ran the program. The first time, I tried using the "Root Only" option. This ran, but didn't seem to work. So once that didn't work, I ran the first option that let you have the option to root (I have forgotten the exact wording). This worked and I got to the screen where I had to factory reset the phone. However, instead of being able to do this, I was stuck in bootloader with the error message "Err: A5,70,70,00,1F." So at this point I kind of realized that I was screwed so I tried to flash stock android 2.3.4 back to my phone using RSD Lite. I did this, and ended up changing the error message from the previously mentioned one to "Err:A5,70,70,00,00." So at this point I figured that I had a bad .sbf file and downloaded a new one and used RSD Lite to flash it. After I did this and it failed, I now am stuck in bootloader with a "Code Corrupt" message.
So basically, rooted or not, I would like to be able to use my phone again. I have seen in a couple places that the problem could be due to low battery, but I have switched to a fully charged one with no luck still.
This was my first attempt at rooting, and I am fully hating my first experience, but I'm already this far so I am willing to do the work to learn and get my phone back. If anyone can provide me with some pretty detailed instructions (remember, I'm a total noob and bricked my phone on something everyone else seems to have had no trouble with), that would be incredible.
Thank you in advance!

Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http://droid.koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid. koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Yes, it is the droid 2.

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid.koumakan. jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?

xwsxlogan said:
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
Click to expand...
Click to collapse
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?

bhigham said:
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
Click to expand...
Click to collapse
Yes, it was in the link listed before. The method had been cross posted on this site and on their site.

Ok, above the err message, what does the top line say?

bhigham said:
Ok, above the err message, what does the top line say?
Click to expand...
Click to collapse
The only screen that I can get reads as follows:
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Someone suggested that by holding up and power would bypass the "code corrupt" message, but that does not work. Also, the X+Power to try and wipe the phone clean doesn't work either.

When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,

bhigham said:
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
Click to expand...
Click to collapse
I did get an error message when trying to flash the stock 2.3.4 and it was something to do with RAM, but unfortunately this was 5AM this morning and I was beyond exhausted so I don't remember exactly.
I am using Windows 8 x64, but have access to XP, Vista, 7, and server if I need to.

I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP

bhigham said:
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
Click to expand...
Click to collapse
Alright, I will go ahead and get XP installed along with the drivers. Do you think that I should use a version previous to 2.3.4 then so that I have a better chance to root?
I am charging up my battery now using another phone, so I will start on it in a bit. Thank you again for answering all of my stupid questions and helping me out, I really appreciate you taking the time to do it.

It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.

bhigham said:
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
Click to expand...
Click to collapse
So you're saying that the only thing I will be able to flash is the 2.3.4?

xwsxlogan said:
So you're saying that the only thing I will be able to flash is the 2.3.4?
Click to expand...
Click to collapse
exactly

bhigham said:
exactly
Click to expand...
Click to collapse
Alright, I will try again tonight with a charged battery and XP and let you know how it goes.

This link here http://www.google.com/url?sa=t&sour...rICoBg&usg=AFQjCNHht4SU69VoDkBnMBCA_0uf9WYpyw. Will take you to the download for the correct sbf.
Correct sbf should read: 1ff-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_dr4-51-120117-release-keys-signed-Verizon-US.sbf.gz
Sent from my DROID2 using Tapatalk 2

Alright Update after flashing the .sbf file that was given in the previous post.
I used XP, running RSD Lite 5.6, with Motorola drivers installed. I charged a second battery up to around 70% or so to use during the process. I also changed USB cords from the previous one that I was using. I loaded the .sbf into RSD Lite, started it, and it ran flawlessly, skipping right over the RAM step in which it failed last night. Had to remove the battery and reinstall to do the manual reboot, and all of my phone settings were exactly as I had left them when I started. I had to dial *228 +1 to get the phone back on the network, but that was no problem.
So after all of this, I'm back to where I started last night haha. Special thanks to bhigham for all of the support and walking me through this today and also slogar25 for confirming that I had downloaded the right .sbf file.
So I guess my problem is solved...until I try and root it again!

glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.

bhigham said:
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
Click to expand...
Click to collapse
Yep, I've noticed you have been following the cross post on this site for the methods that I tried last night when I really didn't have a clue what I was doing. Do you think that I should just try the CD method again? I mean worst case I would do the same thing I did last night, but now I know how to flash it back to the stock 2.3.4. I don't mind wiping my phone, but after it survived everything I did last night, I feel more attached to my data haha.
Also, how do I mark this post as solved?