yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] Matt4542:
Good post. Just saw this haha. You should probably update the links for the people who used the OTA because if they use the current sbf you have posted they will end up looping and you will get people saying "zomg my phone wont bootz!!" haha. Here is the download link http://bit.ly/dir7fq :)
[Droid 2 Android Development] newk8600:
yes good point I haven't been on my computer for a few days I reinstalled linux on my laptop and it was messing with stuff. The post has been updated with 2.2.0 and 2.3.2 versions.

Edit: Also updated with how to update baseband with download link if baseband doesn't update with the 2.3.2 sbf
[Droid 2 Android Development] MattHorner:
Ok I tried the cd-r but idk why its not working =/ I have an asus running vista and my bios is, ade by a company called ameribios I believe and I have an internal drive
[Droid 2 Android Development] newk8600:
Ok what are you using to burn the disk? Are you burning the .iso onto the disk or are you making it a data cd and placing on it?
[Droid 2 Android Development] MattHorner:
Im pretty sure I am burning it... How would I know the difference? =/ sorry if that is kinda duh-duh-duh and do I need linux already on my computer? Oh and my phone system version is 2.2.20.A955.Verizon.en.US is that gonna effect the sbf file you have posted?

Edit: Nevermind just got 2.3.2
[Droid 2 Android Development] newk8600:
No linux needed to burn disks. In windows I use dvd decrypter but nero, active iso, imgburn and a plethora of other utilities burn disks you just need to be sure the application you are using is burning the iso to your cd-r and not just making a data disk. If you just took the iso and dropped it into your disk through windows you aren't burning it.

Use the 2.3.2 sbf then if you use the 2.2 you'll brick your phone

If you put the cd in while booted into vista does it see it as anything if you go to My Computer>>"your-disk-drive".

This can be a confusing thing if you haven't done it before. I know I had trouble when I first messed with iso's I burned a few coasters before I got working disks. (The slower the burning the less chance of data corruption.)
[Droid 2 Android Development] MattHorner:
Oh ok well yeah I just got the 2.3.20 and ill check it out in my computer once i re-burn using IsoBurner. SOrry for all the questions I just really want this is work and its frustrating slightly lol. THanks for all the help so far! Great guide btw I just fail a little lol
[Droid 2 Android Development] newk8600:
No problem. A few questions don't bother me one bit. It's no good if I can't explain the parts that don't make sense or don't work for you. I'm here to help that's all.
[Droid 2 Android Development] MattHorner:
JUST ACCOMPLISHED! Thank you so much for the guide and for all the help! Yay for my old phone =P
[Droid 2 Android Development] newk8600:
Awesome. So what was wrong? Bad cd-r?
[Droid 2 Android Development] MattHorner:
I think it was I was not "burning" like you said to but right after i used IsoBurner the disc came up as Ubuntu and ran perfectly!
[Droid 2 Android Development] grimmy311:
To be sure if you are currently on 2.2 you have to sbf to 2.2 then do the ota or can you go straight to 2.3?
[Droid 2 Android Development] newk8600:
Yes you can sbf straight to 2.3.2 I did.
[Droid 2 Android Development] grimmy311:
Even with a custom rom sorry forgot to mention running fission 2.0
[Droid 2 Android Development] newk8600:
Yes the sbf will load a clean version of your phone (like if you just got it from the store). Afterward you'll have to reroot then install the ROM you want (Don't forget to make a backup after rooting).
[Droid 2 Android Development] newk8600:
Just make sure if you want to go to 2.3.2 you have to use the 2.3.2 sbf.
[Droid 2 Android Development] JonandRoid:
I tried the update for the baseband only and it said there was a problem with the syncandsettings.apk. is this due to running a custom rom or what? Im not too sure..and btw..what's so speicial about the update? Idk what a baseband even is?..like does this baseband do something different and the 2.3.2 seems the same as 2.2.2...so maybe some more elaboration on what this even does for the droid 2.
[Droid 2 Android Development] newk8600:
Sorry I should have said the update needs to be done prior to loading a custom ROM because the update needs the blur on the phone or it will error out. So you'll have to reload the backup made before you installed the ROM (you made a backup, right?) then you can update. Then I'd reinstall the ROM with a clean version and not to use a backup or things might no go right.

The baseband from my understanding has to do with the radio so updated baseband means improvement in calling and receiving data. I don't remember what's all in the update but Verizon has some documentation on it HERE.
[Droid 2 Android Development] JonandRoid:
Oh cool. Yeah I accidentally made an update when I was trying to restore so that was a good accident lol. Thanks for the help and that's what I was thinking but I wanted to make sure. And I appreciate the help and link too :). I learn something new every day especially through my handy xda forums. Lol
[Droid 2 Android Development] newk8600:
Lol no problem glad to help.
[Droid 2 Android Development] JonandRoid:
You rock!...restored to the previous blurd version and used the update.zip and it worked. I am so happy now! Lol. Thanks. That really worked out great. I only have one problem though. When I restarted the phone the superuser app wasn't working that came with the root when I rooted it and I tried installing an updated one and that wouldn't work. So I restarted the phone and got into clockwork recovery so that means that root is still available and I just flashed to the back up that I made 5 minutes before I did the update.zip. everything is working fine within the rom and it still shows the .07 baseband (:D) but every time I flash back to this rom which I've done quite a lot lately the normal touch screen keyboard never works and it gets me so frustrated I wind up factory reseting or sbfing...idk y it never works again after I flash..and I even replace the latinIME.apk in system and it opens and the force closes..idk I know I should have re installed the entire rom but I didn't seem to have root capabilities and didn't want to have to set up everything again so I know this is not your problem but I am just curious to see what you think might be wrong. And once again thanks a ton :). Btw..I just figured...why didn't I just install my rom after rebooting into clockwork...idk its been a long day..lol
[Droid 2 Android Development] newk8600:
Well I'd say try wiping data and cache in clockwork and then try to reinstall the ROM lol. That's probably your best bet. btw which ROM?
[Droid 2 Android Development] soleicey:
i am not successful when doing this, this is what comes up

bryan@ubuntu:~$ chmod +x sbf_flash

bryan@ubuntu:~$ sudo ./sbf_flash VRZ_A955_2.3.20_1FF_01.sbf

[sudo] password for bryan:

sudo: ./sbf_flash: command not found

help?
[Droid 2 Android Development] newk8600:
If this is your own linux setup you need to have the sbf_flash file on your computer. If it's the livecd then make sure th sbf_flash file is in the home folder.
[Droid 2 Android Development] JonandRoid:
Fission 2.0.1, yeah I flashed back to the blurred rom and installed a fresh copy of the fission and it works now. Thanks for the help. And btw, the new baseband seems to have a little better service/ reception and a little faster downloading of webpages and what not.
[Droid 2 Android Development] soleicey:
where do i get the file? i have the 2.3.2 file
[Droid 2 Android Development] newk8600:
Sorry about the wait you can get it here.
[Droid 2 Android Development] mike3702:
I've tried doing the plugged in reboot many times with no luck. So now I think that it's time to flash. I just have the one question about entering the codes. After I enter the first one do I hit enter or do I enter the first then the second then hit enter. I really want to thank you for all the help that you've given me.
[Droid 2 Android Development] newk8600:
Yeah type (or copy and paste) the first command then press enter and then do the same with the correct command. No problem just trying to help you.
[Droid 2 Android Development] mike3702:
Thanks bro you rock!!!!!!! I'll let you know how it all turns out. Hopefully for the best. lol
[Droid 2 Android Development] grimmy311:
I've been trying to do this method with my own Ubuntu install. Keep getting this... Any ideas?

dshrout@shrouthdx16:~$ chmod +x sbf_flash

dshrout@shrouthdx16:~$ sudo ./sbf_flash VRZ_A955_2.3.20_1FF_01.sbf

Segmentation fault

dshrout@shrouthdx16:~$

Phone is plugged in sitting at Boatload D2.35 Battery OK OK to Program: Transfer Mode: USB
[Droid 2 Android Development] newk8600:
Do you have the sbf_flash file? A segmentation fault means the program is trying to access memory that it isn't allowed to access which confuses me because I've used this method on my own ubuntu setup and have never seen that before. I would shutdown and reboot your computer and try it again. But make sure the files are complete and they are in your Home folder.
[Droid 2 Android Development] grimmy311:
Yep, I downloaded the sbf_flash from post #78 in this thread. Ill try to reboot and rerun.
[Droid 2 Android Development] grimmy311:
Same error
[Droid 2 Android Development] grimmy311:
I am going to try the LiveCD and see what I get.
[Droid 2 Android Development] newk8600:
Sounds good because that error is stumping me.
[Droid 2 Android Development] mike3702:
I was going to flash last night and when I ran the Ubuntu disk all went good. Then I went to add the sbf file to the home folder and it said that there wasn't enough room for the file. Any ideas?
[Droid 2 Android Development] newk8600:
Just leave the file on your flash drive it's a livecd environment so It's trying to put the file on your cd which it can't so try it with the file on you flash drive.
[Droid 2 Android Development] newk8600:
Or you don't have enough swap memory for it to store the file.
[Droid 2 Android Development] defunkreeus:
Problem with chmod

Hi, I am having a similar issue with the first command. I drag and dropped the sbf file into my home folder in Ubuntu then in the terminal, I changed to that directory. When I do this, I still get:

chmod: cannot access `sbf_flash': No such file or directory

Do I have to rename the file? Am I going about this wrong? Please help! My phone has been out of commission for 24 hours now!
[Droid 2 Android Development] newk8600:
Try it without cd-ing to the home folder.
[Droid 2 Android Development] defunkreeus:
Yea, I originally just attempted the instructions without changing the directory. When I list services I can see that the sbf file is there. I don't see any files in that directory named "sbf_flash" so is this a hidden file or something? Also, this was done in Ubuntu 10.10 so maybe that could be it?
[Droid 2 Android Development] mike3702:
I've tried to install from the flash drive but it still says that the file can't be found. I'm trying not to bother you with this as much as possible but I must have eaten my "I can't figure it out medicine" lol, this is frustrating. What do you think I'm doing wrong?
[Droid 2 Android Development] mike3702:
Do you think that I would have a better chance with rsd lite?
[Droid 2 Android Development] newk8600:
You could definitely try. When I have time I'm gonna flash to see what the problem is. I'll get back to you.

Also don't worry about bothering me I'm just trying to make this work for everybody you included. If there's something wrong on my end I want to fix it and if it's on your end I just need to instruct better. So when I help you I help me too and others with similar problems you can PM me if you want but I get instant notifications about posts on this thread and your information could help somebody else.:D

EDIT:Well I tried the LiveCD and I had no problems other than my computer being slow (that's what happens when your diskdrive is connected to a USB 1.1 port, all of my laptop's USB's are shorted down to 1.1)

@ mike3702 when you navigate to the home folder: places>>home folder. How much free space do you see at the bottom of the folder window? mine read about 1.4GB and in order to have the sbf file on there you need at least 500MB of free space.
[Droid 2 Android Development] newk8600:
I'm on 10.04.1 and the Livecd is the same. But if you open up a clean Terminal just type "ls" and either post the output or tell me if the sbf_flash file is listed because it should be. The only reason it wouldn't be is that it isn't in the home folder.
[Droid 2 Android Development] mike3702:
In the home folder I have 379.7 MB of free space. How do I get more free space?

Sent from my Droid
[Droid 2 Android Development] newk8600:
I believe you have to have more RAM on your computer how much RAM do you have installed? I've got 4GB I'll assume you have 2GB or less.

If you don't have enough RAM I did make a version with the sbf file on it but it will only fit on a DVD not a CD because of the space constraints. I didn't want to put it out for simplicity that way we all would have the same cd and it would fit on a cd (which is cheaper and usually faster because the DVD would have a lot of free space (like 3GB of empty disk)) (LOL sorry for being a parenthesis freak)
[Droid 2 Android Development] mike3702:
I do have emty dvd disks, is there a link to that file or a way for me to get it?:D

lol its all good.
[Droid 2 Android Development] newk8600:
Uploading as we speak I'll post when it's complete.
[Droid 2 Android Development] mike3702:
Thanks I appreciate it.

Sent from my Droid
[Droid 2 Android Development] newk8600:
UM...you need the 2.2.0 sbf right? because I made the cd when there wasn't even 2.3.2.
[Droid 2 Android Development] mike3702:
I had already recieved the update. If I go back to the 2.2 and have the update on my sd card will I be able to get the update, or will I recieve the update ota again?
[Droid 2 Android Development] newk8600:
No once you have the update the bootloader is changed and you can't go back. Well you'll have to wait until I can make another livecd (it's not hard it's just tedious and my computer isn't the best. I say that because the disk drive doesn't work and all of the USB ports are SLOW and the sound card goes out and sometimes it doesn't boot correctly).
[Droid 2 Android Development] mike3702:
Thanks, I hope that this works. You have been extremely helpful.
[Droid 2 Android Development] :
First of all, thanks to the OP and all those involve in validating and providing the SBF installation instructions. :)

I find it ironic that the day I decide to install Ubuntu on my PC (goodbye Windows!!! :D) the same day I "bricked" my D2. I already had subscribed to this thread so all I had to do was download the SBF file and the sbf_flash tool. My storey:

Everything had gone fine with my installation (i.e. I got the "rebooting" message on the terminal window) and it just so happens that my phone barely had any charge left when the install was completed. The phone re-booted and I got the Motorola logo and then the screen went off. I tried to do the "boot loop instructions" (i.e. pulling battery, x+power, etc) and nothing worked. However, I noticed that the white light next to the phone's USB connector was on. It was at this moment I figured that I figured out that my phone did not had more charge to boot up. I kept the phone plugged to the computer for a bit and try again but the phone wouldn't turn on. I finally said "It must be charging the battery, let me try the wall outlet". As soon as I plugged the phone to the outlet the Motorola logo came up followed by a big battery logo showing 10% charge. At this point I was finally able to do the "x+power followed by search" sequence to get the boot menu and wipe data/cache. After that I was able to boot the phone successfully.

I don't know what might have happened if the sbf flashing had not completed before I ran out of battery. My suggestion to anyone following this thread's instructions: Make sure you have a fully charged battery before proceeding. :o
[Droid 2 Android Development] newk8600:
good point on serveral occasions I've thought about putting that in there. I know that sbf ing and restoring backups can take a lot of battery power. Much more than one would normally expect. I'll edit the the post.
[Droid 2 Android Development] mike3702:
Thanks again for all your help. I finally got it figured out. I used rsd lite and now I'm back up and running and all is good as far as I can tell. :D For some weird reason I just couldn't figure out ubuntu, but this is something that I want to learn more about.
[Droid 2 Android Development] newk8600:
No problem sorry I couldn't get it working for you. Once my linux setup is fixed I'm going to supply a new livecd with the new sbf for people who have your problem.

I'm glad you got your phone fixed!
[Droid 2 Android Development] mike3702:
All the info that I got from you helped very much. Like I said I'm very interested in ubuntu so if there is anything about that you feel like sharing lol I'm all ears.:D

Or if there is anything that I find out I will let you all know. Thanks again.
[Droid 2 Android Development] :
Thanks again for posting this thread. I've never messed my Dinc when installing ROMs, so I'm glad I found this thread to help me get my D2 back in working order :)
[Droid 2 Android Development] darkonion:
How to video on how to SBF your phone!

http://kimete.com/blog/2010/12/16/how-to-unbrick-your-droid-2x-using-sbf-recovery/
[Droid 2 Android Development] newk8600:
This is awesome hopefully after I can fix my linux setup I'll be able to make a new live CD with some updates.
[Droid 2 Android Development] darkonion:
Yeah. Let me know. I should put together a DarkOnion Super Pack or something. ROOT, BOOT, SBF, and FM Radio!!

Hahaha.
[Droid 2 Android Development] Ronbo85:
hi, if you remember me from the other thread I was having problems flashing my phone. you recommended this thread try using linux.I downloaded your ISO and burned it to disc. it works fine and following your instructions I can flash my phone. the complete the process and reboots back to the bootloader every time. I tried wipe all factory reset but it still boots to the bootloader.I noticed still when I connect it to rsd lite I still do not see the e s n number in the status window. I am beginning to think this phone maybe a paperweight. any ideas? thank you once again for your help
[Droid 2 Android Development] Ronbo85:
here is a screen grab of the process. I forgot to note this recognizes my phone as a droid X and its a droid 2.

SBF FLASH 1.08 (mbm)

Index[0]: Unexpected chip 32

Index[1]: Unexpected chip 2b

Index[2]: Unexpected chip 2b

Index[3]: Unexpected chip 32

Index[4]: Unexpected chip 32

Index[5]: Unexpected chip 32

Index[6]: Unexpected chip 32

Index[7]: Unexpected chip 32

Index[8]: Unexpected chip 32

Index[9]: Unexpected chip 32

Index[10]: Unexpected chip 32

Index[11]: Unexpected chip 32

Index[12]: Unexpected chip 32

Index[13]: Unexpected chip 32

Index[14]: Unexpected chip 32

=== 23.sbf ===

00: RDL03 0x82000000-0x8204CFFF B717 AP

01: RDL01 0x00150000-0x001FFFFF 13EA BP

02: CG03 0x00000000-0x008F7367 1C3E BP

03: CG31 0xB0280000-0xB02847FF 3B80 AP

04: CG33 0xB1900000-0xB24C07FF 3B0A AP

05: CG34 0xB0700000-0xB07047FF 8464 AP

06: CG35 0xB1000000-0xB13FFFFF E51E AP

07: CG39 0xB2A00000-0xC41C07FF C81B AP

08: CG40 0xC4200000-0xC4200FFF FDFF AP

09: CG42 0xB0800000-0xB083FFFF 7479 AP

10: CG47 0xB1400000-0xB18FFFFF 4EFC AP

11: CG61 0xB0B00000-0xB0B7FFFF 7486 AP

12: CG64 0xB0000000-0xB00047FF A169 AP

13: CG65 0xB0180000-0xB01847FF D9A2 AP

14: CG66 0xD0000000-0xD7B327FF 47D7 AP

Droid X found.

>> uploading RDL03

Uploading: 100% OK

>> verifying ramloader

-- OK

>> executing ramloader

Droid X found.

>> sending erase

>> uploading CG31

Uploading: 100% OK

>> uploading CG33

Uploading: 100% OK

>> uploading CG34

Uploading: 100% OK

>> uploading CG35

Uploading: 100% OK

>> uploading CG39

Uploading: 100% OK

>> uploading CG40

Uploading: 100% OK

>> uploading CG42

Uploading: 100% OK

>> uploading CG47

Uploading: 100% OK

>> uploading CG61

Uploading: 100% OK

>> uploading CG64

Uploading: 100% OK

>> uploading CG65

Uploading: 100% OK

>> uploading CG66

Uploading: 100% OK

>> verifying CG31

-- OK

>> verifying CG33

-- OK

>> verifying CG34

-- OK

>> verifying CG35

-- OK

>> verifying CG39

-- OK

>> verifying CG40

-- OK

>> verifying CG42

-- OK

>> verifying CG47

-- OK

>> verifying CG61

-- OK

>> verifying CG64

-- OK

>> verifying CG65

-- OK

>> verifying CG66

-- OK

>> rebooting
[Droid 2 Android Development] newk8600:
That shouldn't matter as long as it flashes all the way. Have you tried it again maybe? Or making sure you have the whole 2.3.20 SBF the one on this tutorial.
[Droid 2 Android Development] Ronbo85:
Ok, even tho I have a few copies of the sbf file I will dload that one to be sure I have a good one and try it. I found another sbf thats a system only and about half the file size but havent tried it.

What do you think about the string of "Unexpected chip 32" messages at the start of the flash process?
[Droid 2 Android Development] Ronbo85:
"Now your phone should start flashing. Let it go and it should reboot in 20-30 minutes. That should be it let me know what problems you have."

I dloaded the 2.3.2 sbf for this thread. Same results verbatim as posted before. You say in my quote above it takes 20-30 min but this is only taking about 5 min tops, then reboots back to the BL with OK to program screen.

Edit: Also an interesting note that after the flash the power light next to the charge port is on but prior to the flash process its not.
[Droid 2 Android Development] newk8600:
The 20-30 minutes is a buffer so people don't mess with the phone before it's finished I probably should've put 10-20 but sometimes it takes longer for some people. I'm still not sure why your phone reboots to the bootloader after flashing. It should be fine you might try reflashing the bootloader, either should work with the 2.3.20 sbf. Your issuse is kinda stumping me I'm not sure exactly what to do.
[Droid 2 Android Development] Ronbo85:
Ok I will try reflashing the BL. It currently has D2.35 on it. I have the sbf's for D2.35 and D2.37. Which do you recommend?
[Droid 2 Android Development] newk8600:
Either or, both will accept the 2.3.20 SBF.
[Droid 2 Android Development] Ronbo85:
yeah I tried it still a no go. I'm looking at some threads in other forums with similar problems. what the heck maybe I will try a droid x sbf since that's what this thing thinks it is. not much to lose at this point but thank you for your help

sent via droid incredible xda app
[Droid 2 Android Development] Ronbo85:
Since my wife returned with her Win 7 laptop I tried rsd lite 4.8 on it. It works better less errors. If I try and flash the full 2.3.20 sbf I get same results as my vista laptop but the "2.3.20 System Only" sbf from MDW flashes OK with a 100% finished success reported but the phone still boots str8 to the BL and I tried the wipe all etc from the recovery menu too. After this I tried running the the 2.3.20 update.zip from MDW on my SD Card to see what happens but get a signature verification error when it runs. I still notice RSD shows this phone has N/A in the ESN/MEID status.
[Droid 2 Android Development] newk8600:
The update.zip isn't signed by moto so it won't go through the stock bootloader that's why that error occurs. I'm stumped on the esn meid stuff not sure about that. Maybe if we new more history but I think you said all you know is the esn is clear with VZN. The system sbf is if you wanted to update from 2.2.0 to 2.3.20 but it doesn't include everything and since you don't have any other software on there it's not sure what to run even though you have the system 'updated'. This is truly a weird occurance.