yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] Disko:
Hi, I followed all the steps to the letter. I'm currently on the step where I find the sbf file and press start in rsd lite to flash.

My phone is currently in bootloader mode and the flash process says failed.

"Phone{0000} Phone not compatible with multi-interface superfile..."

Do I retry? Should I disconnect? Is my sweet cool phone lost to the abyss?

I'm running windows 7 and I had rooted my phone using "Easier 1-2-3 Droid 2 Root" batch method.

Any help would be appreciated!

Edit:

I attempted to reload the file and it failed again. After waiting for a few moments I stopped and closed Rsd lite and rebooted my phone. I did not loose any data or root. I still don't know exactly what went wrong. Hopefully some digging around will lead to a answer.
[Droid 2 Android Development] darkonion:
Sorry, not sure. Hopefully someone more experienced than I will be able to help you.

-Kevin
[Droid 2 Android Development] fuglybadger:
I have the droid 2.jpg file downloaded but it won't let me extract it. Also when i downloaded it, 230mb was the file size but it showed finished at 178mb? did i screw up somewhere?
[Droid 2 Android Development] darkonion:
Right click the file and open it using WinRar or equivalent.
[Droid 2 Android Development] event121:
Windows 7 64bit

Flashed first and got Result: Failed after phone rebooted at the end.

Then RSD wouldn't grab the MEID from the phone.

Flashed again after manual reboot of phone and changed compatibility of RSD to XP SP2 and run as admin.

Same result. Phone boots, but result says failed.

I moved on and flashed the second sbf. It did it's thing really fast and I see:

Status: Internal Error While Programming Phone. Result: Failed.

RSD still shows the device as A955, but MEID is n/a.

*22899 is the code VZW uses to program data cards. It's fine for phones but recommended to *228 SEND choose option 1 after you're back up to normal.

I did *22899 for step 12a. and am not roaming or no service. I was not roaming before *22899.

Factory Reset and... I'm guessing this worked??

I don't have root. I have all the correct items in About Phone.

Everything looks like I just got it except the wallpaper is still Boba Fett..

Also my "DROOOIDDDD" doesn't sound when it boots only when it gets to my home screen and the SD card notification goes off. Which I guess is normal.

Thoughts? Comments?

Update:

Found an extremely helpful post by Redflea over on droidforums.net

See POST #9.

http://www.droidforums.net/forum/droid-2-hacks/80915-droid-2-unroot.html

No reason to flash back unless we install a rom or theme?
[Droid 2 Android Development] julidelara:
So lets say I use the Droid 2 Recovery Bootstrap to install custom roms and one day I need to send my phone for warranty reasons. Will this method remove the custom bootstrap or will I need to do something else? Thank You in advanced.
[Droid 2 Android Development] inxane805:
ok i cant seem to get my rsd lite to read my droid2 any help.. and yes i tried running it as admin.. any other suggestions
[Droid 2 Android Development] haincha:
I want to thank you for this! Even though it says it fails, it restores my phone. Has saved my phone from a few messed up flashes.
[Droid 2 Android Development] tgwaste:
getting this error then FAIL.. any ideas?

22:40:49, September 17, 2010

Line: 587

ERROR: Flash failure: Interface AP-OS: Error verifying Code Group 39 checksums. File: 0xAD28, Phone: 0xE045 (Error Code: 31),

Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=39

File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp

Device ID: 0
[Droid 2 Android Development] chrstdvd:
Followed inst to letter thru step 11. "Droid2_X6_2.2...SECURE.sbf" failed but I could not expand it to find what error. So I did it again. It failed again, went thru to 100% then just said "failed".

So I flashed , "BL_D235...HSPart.sbf" and it passed. The phone rebooted and nothing has changed.

I am using Windows 7. Wonder if I should try it again, or leave well enough alone?

I rooted my phone and then uninstalled the messaging app after I loaded Handcent and now I can not MMS send or receive.

I thought I could follow this tutorial and get things back to square one and start over.

Appreciate any advice.

Update 1

using-rsd-lite-flash-sbf-file-correctly

I read this at the above link(I am new, they won't let me post a link): "Also, be sure your SBF file is good. If your file was originally zipped, then unzipping it would have given an error if it was corrupted so you're OK. " So I decided to use 7 zip on the jpg file again.

It said there was an error with that first sbj file. I deleted the jpg file and downloaded it again. Then I 7 zip'ed the new file and had no error messages.

Then I went through the processes again and it all worked. I am at the *22899 part now it has been doing something for about 15 min now. The call is still in progress and the notification bar is flashing green/grey. I will just have to leave it alone, I guess.

I did notice that all the bloat is back on the phone before I started the current call.

I noticed a few posts that mentioned "failed" so maybe this info will help someone else.

I will update whatever happens.

Update 2

I was supposed to listen when I dialed *22899 but the dial pad went away and the notification bar started blinking. So after about 30 min I got back to the dial pad and there was a message that activation failed. I hit a "next" button, the phone dialed, operator gave choices to reactivate phone or upgrade roaming. I chose 1. and the phone reactivated. I have my 3G and am un rooted. So I stop after 12 a in tutorial. I have all the original apps back and can MMS.

This means I now have a backup on the computer to get back to stock. Now I will root again, and make sure I pay attention to what I am uninstalling.

Thank You and I will hit your paypal link.
[Droid 2 Android Development] gfrancis306:
has anyone tried flashing this .sbf with sbf_flash (a program for Linux to, obviously, flash .sbf files) it worked fine with flashing the D1, but I haven't seen any information confirming it will on the D2.

thanks in advance! looking forward to my new shiny D2
[Droid 2 Android Development] darkonion:
Yup. Matt4542 started another thread here on how to sbf recovery using that method.
[Droid 2 Android Development] facelessuser:
I have only flashed with linux, and have done it multiple times. It is as easy as you can get.
[Droid 2 Android Development] KingLo:
You should also mention that the sbf can be loaded from Bootloader mode and also how to get into bootloader mode (hold up on physical dpad while powering on)

For all of you getting failed try reloading into bootloader mode when it resets. it'll give you failed sometimes just because it didnt go back but it still will work
[Droid 2 Android Development] gfrancis306:
awesome! so what we're saying is (aside from modifying an sbf file and bricking it that way) the droid 2 is about as safe as the droid 1, as far as failsafe methods to restore to working status.
[Droid 2 Android Development] CrypticDroid:
So I've attempted following this method on a Windows XP 32 bit computer available to me. I got everything installed on the computer that I know of.

I plug in my phone, open RSD lite, it shows up, I choose the first file for flashing and I hit 'start'. It takes about 2 minutes to tell me it's failed.

This is the message I get: "unable to retrieve interface handle (0x7027)"

Any ideas? My phones been acting SUPER funky lately. Lots of FC's and general wonkiness.
[Droid 2 Android Development] walcs:
Thank god for this, otherwise my phone would be totally F*cked :D

You guys are magical!
[Droid 2 Android Development] chaosz3ro:
worked great, thank you for the files and tutorial! If I wasn't so broke I'd donate.
[Droid 2 Android Development] THCtextbook:
im trying to flash my phone, firstly when it connects to RSDLite it isnt recognized as A955 or whatever its recognized as S Flash OMAP3630. Will this cause problems or should it not matter? after attempted flash it said that device isnt compatible with rsd lite multi-flex? HELP!!!
[Droid 2 Android Development] Coderedpl:
Can someone upload the RSD Lite?

The link attached doesn't work anymore.

I'm guessing its with the co downloader.exe thing?
[Droid 2 Android Development] Terri M:
I don't know how to use linux or ubuntu, and RSD kite keeps giving me a fail response. My original Droid 2 is definitely bricked. :-(
[Droid 2 Android Development] darkonion:
That sucks. Ubuntu is awesome! wubi-installer.org

That will install Ubuntu on your Windows machine, so you can dual boot. Just need to learn some simple commands.
[Droid 2 Android Development] darkonion:
I'll see if I can re-upload it. My internet is stupid slow right now. :(
[Droid 2 Android Development] darkonion:
I put a new link up for RSDLite.

-Kevin
[Droid 2 Android Development] Terri M:
What are the simple commands

?
[Droid 2 Android Development] newk8600:
Custom ubuntu LiveCD coming real soon (completed actually) for people without linux in need of a hassle free sbf flash (without fully installing linux). I'll get it out ASAP just a little busy at the moment.

From newk8600's Droid2
[Droid 2 Android Development] Coderedpl:
Im getting phone is not compatible with multi-interface super file

EDIT: I was getting: "phone is not compatible with multi-interface super file" in RDS Lite 4.7. With the patch provided somewhere here it didnt even recognize my device as connected.

I installed 4.8 and it worked, went right through with the SBF.
[Droid 2 Android Development] darkonion:
Do you think you can post a link to the 4.8 version?
[Droid 2 Android Development] mgalceran:
Hello,

I've been working on this for hours upon hours and I'm ticked. I followed everything just right (to my knowledge) but the 'start' button doesn't appear so I can't move forward. I've updated and re-updated the drivers just to make sure I'm good there, my phone is in pc mode with debugging enabled, but it still isn't working. Please help! Thanks.
[Droid 2 Android Development] darkonion:
Did you patch 4.7? Did you install latest drivers? I am sure you probably did, but just checking.

Have you considered trying the linux method? You should try that. A lot less headache. You don't need linux on your computer. You can use the LiveCD and boot from the CD and go from there.
[Droid 2 Android Development] Terri M:
Try using newk8600's Ubuntu LiveCD. It's very easy and believe me, it worked wonders for me!
[Droid 2 Android Development] darkonion:
Here is the link to the tutorial. RSD Lite 4.7 and 4.8 isn't easy to get or use. I'd rather do the Ubuntu LiveCD method.

P.S. I can probably write a small script to streamline things.
[Droid 2 Android Development] mgalceran:
So how do I get to the Ubuntu LiveCD method? I didn't find a link on the post. Thanks for the help!
[Droid 2 Android Development] darkonion:
Look up newk6800 thread. I forgot what it is called. It is here in development.
[Droid 2 Android Development] pbonello:
So my phone is stuck at the Moto boot logo. I want to try this method but I don't know where to get the two firmware files, also my phone is now out of battery and I can't connect it to my computer to charge, and it won't charge in the wall because it just tries to boot. Can someone help?
[Droid 2 Android Development] newk8600:
http://xdaforums.com/showthread.php?t=804088 here's the link and good luck. Post any and all questions or comments in the ubuntu section for quicker response.
[Droid 2 Android Development] theecho:
Any files needed for the sbf are located at droid2files.com. I will keep the sbf up as long as possible and would recommend downloading and saving this somewhere on your computer. Please let us know if you have any other issues or questions and we will see what we can do to assist.
[Droid 2 Android Development] aplus01:
Thanks for putting this together. It really saved my bacon yesterday. The instructions are great and were really helpful. One shortcoming is that the instructions are aimed at phones that are working rather than phones in distress.

One thing I'd consider adding to the instructions would be that for boot looping phones you'll need to hold down the up key on the physical keyboard before powering on in order to get to the boot loader. Otherwise your computer and also RSD Lite will not recognize you've connected your phone.

Also, for semi-bricked or boot looping phones when RSD does finally list your device it may not be listed as a A955 (mine was not). Instead you may see a device with a model of "S Flash OMAP3630 MI". After the first .sbf installed though my phone displayed the correct device model of A955 in RSD Lite.
[Droid 2 Android Development] theecho:
Thank you for the information. This will be considered for editing.
[Droid 2 Android Development] mgalceran:
So I just tried the Ubuntu method and failed again. The command prompt wasn't recognized. A more detailed version of what I did is posted on that thread. The only thing i can think that maybe messed up is that my sbf file doesnt have those two spaces in its name like the command does ('P2 _USERBLD_ SECURE' before and after the underscores of USERBLD).
[Droid 2 Android Development] aplus01:
@mgalceran

I didn't use the ubuntu method. Finally got the windows method to work. I doubt there would be spaces in the file name but if there are you usually wrap the name in quotes i.e. "file name with spaces"

Sounds like your attempt with RSD Lite was similar to mine in that it didn't recognize your phone. Try rebooting while holding the up key on the keyboard. Then try the steps in the tutorial. RSD should work from there on out.

Good luck

Edit: just saw you got some help with the live CD route.
[Droid 2 Android Development] SerialKilla:
I have an issue I don't see here,and I fear the worst... I wanted to flash the .sbf,full factory restore to return my D2. Have all necessary files and drivers,ran RSDlite,all went well until bootup,it was at 100%,and just started bootlooping. I have tried every solution I could find on the forums to no avail. Any ideas? Or am officially bricked... Thanks in advance.
[Droid 2 Android Development] newk8600:
The command for the ubuntu method was updated and shouldn't give errors now. If you get errors please post them in the Ubuntu tutorial section here so we can get them answered faster. thanks.

@SerialKilla Have you tried the Ubuntu LiveCD method? It's worth a shot if you haven't. just go here Also make sure the .sbf file you have is the right one and it's the whole thing.
[Droid 2 Android Development] SerialKilla:
Thanks for the reply. I actually did the x and power mode into recovery,then hit the hourglass button on the keypad,got into factory recovery mode and reset from there and all is good! Ubuntu LiveCD will be what I use next time tho...lol
[Droid 2 Android Development] sikbrik:
Thank you so much to the OP and to aplus01!!! :D I was stuck at moto screen (and I'm a n00b). This extra step was the difference between RSD lite seeing my phone vs. not seeing it. Well, I also had to choose the 'first come first serve' option in the settings on RSD. The only other thing that might help n00bs like me is that my sbf had to be in the root directory on my PC (C:) for it to work. Any other folder and I got a 'fail'.

Thanks so much for this post and the followups that helped me restore my 'brick'. :D
[Droid 2 Android Development] texmex7265:
hey do you guys think a 2.4.5 sbf will ever be released for r2d2 droid 2s? i stupidly tried and flash a rom that didnt work and caused a boot loop. im hoping for a 2.4.5 sbf to be released
[Droid 2 Android Development] hondurianman15:
rsd

how do i get it in usb debugging. its stuck at the M logo so i cant get in.
[Droid 2 Android Development] hondurianman15:
failed

it doesnt start. what do i do. it just says "failed flashing process (0x7100) phone connected". im trying to do it from the bootloader becuase my droids stuck on the M logo
[Droid 2 Android Development] StirCwazy:
Here's how my story goes.

I got a Droid 2, ended up being a bad ESN, that's another story. Figured I would mess around with flashing different ROMs to it since it's useless at this point. I decided to return it back to stock and toss it on eBay. Following the guide I downloaded/installed everything needed. Extracted the SBFs and proceeded to flash the phone. It fails with the following error.

"Failed flashing process. Failed flashing process. Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address 0x16F800 Command: ADDR (0xE02320F); phone disconnected."

After that the phone has done one of two things. 1, gets stuck in a boot animation loop (or boot loop I guess) or sits at the screen saying "SW Update in progress..." The memory address' change each time it fails of course, but the message in general is the same.

I've forced it into recovery mode, if that's what you call it, D-Pad Up + Power, and tried doing the flash again, same fail. In case of a corrupt SBF I've extracted the JPG with 7zip as suggested by someone else, same fail.

The system I'm running RSD Lite on is a Windows 7 64 Bit system, RSD Lite was ran as Administrator each time.

Ideas?
[Droid 2 Android Development] newk8600:
What version on RSDlite? Some versions work better for others.

Also you can try it in linux with a live cd I made. There's a link on the previous page of posts or look in android development for the droid 2. The title is ubuntu flashing for windows.
[Droid 2 Android Development] StirCwazy:
2.7 from the OP along with the patch. I'll try 2.9, also in the original post and see what happens.
[Droid 2 Android Development] StirCwazy:
Same error as before, I'll try the Live CD and see what happens I guess.
[Droid 2 Android Development] newk8600:
I think the most recent version is 4.9 if the livecd method doesn't work (it should work just fine.) I'd update RSDlite to that version.
[Droid 2 Android Development] zibrah3ed:
MD5

Is it just me or have there been constant problems flashing the SBF? What I haven't seen discussed is a MD5 sum for the SBF file to ensure it wasn't corrupted on download. Maybe this has already been discussed.
[Droid 2 Android Development] newk8600:
I haven't heard that either. That sounds like a good idea. I don't think it will solve all of the problems but it's something to look into.
[Droid 2 Android Development] newk8600:
Okay if you use this download link for the sbf I have an MD5 checksum for it: 20A9ED36F997D7C18E7FD287AE49CDA6 (theech0 got the checksum I'm just posting it here.)

This will ensure that you have the entire .sbf and it hasn't been corrupted by the downloading process.
[Droid 2 Android Development] zibrah3ed:
Very good, quick response think this can only improve support for people having issues with the sbf.
[Droid 2 Android Development] theecho:
Zibra, can you verify that checksum for me please?
[Droid 2 Android Development] zibrah3ed:
Sure will but not until the morrow. The generated md 5 I have is on my work computer 45 minutes away :)
[Droid 2 Android Development] theecho:
oh come on just download it again and verify it now lol
[Droid 2 Android Development] zibrah3ed:
I would but if you have hughesnet internet like I do that file will kill gour internet for a day. Limited to only 200mb download in any 24 hr period. My wife would kill me if I downloaded it tonight and throttled our internet.
[Droid 2 Android Development] theecho:
wow yeah that sucks wait til tomorrow lol
[Droid 2 Android Development] StirCwazy:
I brought in an older laptop to work, running Windows XP, and decided to give that a go first. Of course it flashed properly, no errors, but the phone still gets stuck in what is I'm guessing a boot loop simply playing the boot animation. You see the white Droid then the red eye over and over. I'm downloading the custom ubuntu live cd and sbf from your other thread and will try that. I just think it's weird that it went through the process yet still does the same thing.

In following instructions on your flashing in linux post I also noted that it says to wipe cache if you're in a boot loop. I did, same thing.
[Droid 2 Android Development] zibrah3ed:
20a9ed36f997d7c18e7fd287ae49cda6 DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf

Match!
[Droid 2 Android Development] theecho:
Thanks for the verification zibra!
[Droid 2 Android Development] spaceape99:
Just wanted to post a success - my phone was working but was rooted and I wanted to get the OTA update (and not have root issues afterward). Since rooting didn't really gain me much anyway (work pays for wifi tether), I opted to flash back. I followed all instructions and had no difficulties at all, and no data or settings loss.

One question though, after dialing *22899 and reactivating, I'm good to go (have 3G service, SMS, phone). I don't see a need to perform a factory reset - all seems normal to me. Does that sound normal? I'd rather not do a reset if I don't have to.
[Droid 2 Android Development] joshschlenker:
Issues brick phone!!!!

Did the process as listed above and when I did the first .sbf file this is the error that came acroos so I went onto the next file and it said Finished/ Pass but my phone went into a brick and kept bootloading any ideas im trying the new DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf. from this post

Was using another file called the same but got it from the first post that told me where to download it

Any Ideas

23:16:31, October 29, 2010
Line: 518
ERROR: AP Die ID: 141001154f885d010000f8ff0100

23:16:31, October 29, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000d96532890485

23:16:31, October 29, 2010
Line: 532
ERROR: AP Public ID: b4859574dc46d2eb5035ee47a2128cdb3062d5dc

23:16:31, October 29, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff0000f9113289

23:22:21, October 29, 2010
Line: 919
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command: ADDR
File: D:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0

23:22:21, October 29, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

23:22:21, October 29, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

23:22:43, October 29, 2010
Line: 518
ERROR: AP Die ID: 141001154f885d010000f8ff0100

23:22:43, October 29, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000d96532890485

23:22:43, October 29, 2010
Line: 532
ERROR: AP Public ID: b4859574dc46d2eb5035ee47a2128cdb3062d5dc

23:22:43, October 29, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff0000f9113289
[Droid 2 Android Development] droid2andyou:
Did you hold X first on the keyboard and then hold power, it should show you a little android guy, hit the search key on the keyboard and wipe data and wipe cache. I had the same problem i believe but util i did this it wouldn't boot
[Droid 2 Android Development] ffsmith20:
question about this file "BL_D235...HSPart.sbf" what does this file do another forum has an 2.3.20 sbf file and was wondering if i need this file you posted.....
[Droid 2 Android Development] cellzealot:
No, you do not need that file with the 2.3.20 SBF.

The SBF will update those components with newer versions as well as a new kernel and baseband as long as the flash completes successfully.

It needs to load the BP pass through interface to flash the baseband.

BP= Baseband Processor= Radio