What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Complete Droid X .sbf Flashing Guide

I'm currently on 2.3.340 using fission and looking to try out Tranq. Before I venture into that, I want to make sure I know which SBFs I should be using in case of a brick.

If i wanted to completely clean everything out back to stock, do I need to flash the full 2.3.320 then the system only 2.3.340? Or can I just flash the system only 2.3.340 with a wipe data/cache a few times?

When reading through all these threads, I information for both, so I'm not quite sure. :icon_eek:

To get back to 2.3.340, the Three ways I know of:
-- Since ROMs only replace system stuff (well, MOST ROMs, some are now replacing boot logos, and putting files on other parts of the phone)... flashing the /system only .sbf should clean you up.
--FULL .sbf to 2.3.320, THEN flashing up to 2.3.340 via the 4 patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
The FULL 2.3.320 .sbf also changes your bootloader/kernel/baseband back to 2.3.320, so you need to re-update them back to 2.3.340.
--Maderstcok has an update that .sbf's to 2.3.320, then 2.3.340 all in one update. Still fairly untested, but might be an all in one solution for ya. Search for it on the boards if you decide to try it, you'll find it.

HTH!
 
Help with Droid X in Buffalo NY

Nah, getting into the bootloader doesn't do anything; it just interrupts the boot cycle. Now, if you get STUCK in the bootloader then ALL software on the phone (not the SD card) is gone and you're pretty boomed.

ive tried everything I could for almost a week now.... Stuck in Bootloader Screen 30.04 Err A5,70,70,00,1F MEM_MAP Blank Service Reqd Battery Ok OK To Program..... I came to a Droid X last week from a Rooted for over a year Droid 1 with never a problem flashing... With new Droid X tried to flash Gummy Jar last sat without a wipe ( I know my stupidity thought coming from stock phone could get away with it trying to rush but boy was I wrong) after being stuck at loading gummy jar icons tried to factory reset... been stuck at the bootloader screen since.. tried flashing 1.13.6.2_1sbf and 2.3.32_1FF sbf... got newest drivers and rsd 4.8... ran as administrator... phone never shows either... got it once to do something in rsd saying phone was being programmed with 2.3.32 but when it said finished waited hours never rebooted .... stuck dont know what to do....anyone local want to give it a go email me please [email protected] or try to walk me through what i have to do step by step.... thanks
 
You installed the wrong version of the ROM on your phone in the first place. Now you need the right SBF. You've tried two wrong versions. Do you remember what system version you had before you tried to install the ROM?
 
You installed the wrong version of the ROM on your phone in the first place. Now you need the right SBF. You've tried two wrong versions. Do you remember what system version you had before you tried to install the ROM?

version 2.3.340.MB810 any thing you know that might help is greatly appreciated.. thanks

also 2.2.1...baseband version BP_C_01.09.07P
kernal 2.6.32.9-g5562e1w30471@il93lnxdroid08 # 1
ERI 5
PRL 52189
thats everything I know ... hope to hear you know how i can restore this after my mistake for trying to rush....
 
You installed the wrong version of the ROM on your phone in the first place. Now you need the right SBF. You've tried two wrong versions. Do you remember what system version you had before you tried to install the ROM?

can you please tell me what is the right version of the ROM I need? Thank You
 
You need the .340 version of the ROM. Also remember to do a full wipe before installing ANY ROM.

Did you flash the full .320 SBF successfully? You'll need to flash that then redo the .340 updates before proceeding.
 
You need the .340 version of the ROM. Also remember to do a full wipe before installing ANY ROM.

Did you flash the full .320 SBF successfully? You'll need to flash that then redo the .340 updates before proceeding.

nothing ive done flashes anything in rsd 4.8 with newest drivers and fully charged battery.... the full .320 and .340 im finding are zip files which due me no good cause i cant get past bootloader 30.04... and cant wipe anything either from where im at... any help to get me out of this bootloader ???
 
You need the .340 version of the ROM. Also remember to do a full wipe before installing ANY ROM.

Did you flash the full .320 SBF successfully? You'll need to flash that then redo the .340 updates before proceeding.

nothing ive done flashes anything in rsd 4.8 with newest drivers and fully charged battery.... the full .320 and .340 im finding are zip files which due me no good cause i cant get past bootloader 30.04... and cant wipe anything either from where im at... any help to get me out of this bootloader ???

More info please.

When you say "nothing I've done flashes anything"... what happens when you try?
List the steps you're taking (from the guide), and what happens? Error messages? The more detail you provide, the easier it will be to help.

Pretty sure you don't just happen to have a phone that is completely different from the rest of us.. one that just doesn't work with RSDLite/.sbf s.

:)

You need to .sbf. We just need to figure out what is going wrong.
 
You need the .340 version of the ROM. Also remember to do a full wipe before installing ANY ROM.

Did you flash the full .320 SBF successfully? You'll need to flash that then redo the .340 updates before proceeding.

nothing ive done flashes anything in rsd 4.8 with newest drivers and fully charged battery.... the full .320 and .340 im finding are zip files which due me no good cause i cant get past bootloader 30.04... and cant wipe anything either from where im at... any help to get me out of this bootloader ???

More info please.

When you say "nothing I've done flashes anything"... what happens when you try?
List the steps you're taking (from the guide), and what happens? Error messages? The more detail you provide, the easier it will be to help.

Pretty sure you don't just happen to have a phone that is completely different from the rest of us.. one that just doesn't work with RSDLite/.sbf s.

:)

You need to .sbf. We just need to figure out what is going wrong.

i have a motorola droid x less then 2 weeks old... had a year motorola droid 1 for over a year... rooted for over a year with diff rom prob every week... this x is so much diff im actually kind of scared to do anything if it gets up and working ever. originally rooted my x with z4root everything went well.. tried to rush one day thinking that if i was just coming from stock root wouldnt have to wipe... tried to install gummyjar got stuck in the gummyjar icons loading... got into recovery wiped cache and data rebooted to bootloader 30.04 screen been stuck like that now for just about 2 weeks... every sbf i flashed and i think i flashed almost all of them... the bootloader screen says:
Err: A5,70,70,00.1F
MEM_MAP Blank
service Reqd
battery OK
Ok to program
transfer mode
USB
when i hook up the phone to rsd 4.8 phone doesnt show... when i click start nothing happens.. i got the latest drivers installed on my computer... vista...the phone wont do anything... i cant do anything with zip files others have told me about to recover with those...
 
You could try RSD Lite 4.9 to see if it'd work then. If you're getting a PASS in every SBF flash and you're flashing the full .320 SBF then you might have to take it to Verizon. Got insurance?
 
You could try RSD Lite 4.9 to see if it'd work then. If you're getting a PASS in every SBF flash and you're flashing the full .320 SBF then you might have to take it to Verizon. Got insurance?

tried downloading rsd 4.9 but its in a rar format and asks for a password? and what do i tell them at verizon? what will they do and cant they tell if it was rooted if i bring it to them?
 
if you're stuck in the bootloader then you /system is destroyed so you're not really rooted lol - they'd have to flash your system to re-ship it out

You could try RSD Lite 4.9 to see if it'd work then. If you're getting a PASS in every SBF flash and you're flashing the full .320 SBF then you might have to take it to Verizon. Got insurance?

tried downloading rsd 4.9 but its in a rar format and asks for a password? and what do i tell them at verizon? what will they do and cant they tell if it was rooted if i bring it to them?
 
Back
Top