Tutorial/Walkthrough How to update your Droid R2D2 Phone using 2.2 if it fails to update to Gingerbread 2.3.3 Build 4.5.1_57_DR2-32
After spending a few days dealing with my phone automatically downloading and trying to install the updating and failing at 25%. I had to fix this since it will killing my battery.
With the instructions below this should restore your phone to the stock version of your Droid R2D2. This method will not delete anything on your phone. I would recommend backing up everything before you proceed just in case something does go wrong but I didn't have any issues. It will only restore all the original settings on your phone. This includes unrooting your phone and restoring all apk's and system files edited/removed from your device.
WARNING : This must be done using your PC. Do not attempt this using your cell phone
This information is provided without warranty. I cannot be held responsible if you brick or damage up your cell phone. I simply wrote a walkthrough/tutorial to help deal with an update issue on your Droid R2D2. I did not produce the procedure or the steps below. I just simply consolidated all the information from multiple sources to make it easier to understand and execute. You are welcome to share this information anywhere you want. If needed I will reformat the instructions so it's easier to understand.
1) First download and install the Motorola RSD Lite v5.5 (I attached the file at the bottom of this thread)
2) Download the Motorola 5.2.0 Driver with Motohelper and install from the link below
Motorola Drivers - http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
3) Download the SBF Droid R2D2 file VRZ_A957_2.4.5_1FF_01.
http://www.multiupload.com/8XGQBDG3GV
4) Once you download the VRZ_A957_2.4.5_1FF_01 file. Unzip the file into a folder. You will be using this file shortly
5) Launch RSD Lite. Once the application is launched click on the button with the 3 dots.
Navigate to the SBF file you just unzipped and once you find it click open.
You will see on the right side in the File properties window
Filename: VRZ_A957_2.4.5_1FF_01.sbf
Creation Date: 09/15/2010 03:16:26
File size: 455655933
RAM DL Version: N / A
Bootloader Version: N / A
Platform: 4G OMAP
HAB Type: Signed Production
This is a video to give you an idea how to use RSD Lite. I used this as a guide to make sure I was doing everything in the correct order.
http://www.youtube.com/watch?v=9udWx-KXwGY&feature=player_embedded#!
6) (This step isn't necessary, but you can do it.)
Back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
7) Plug the USB cable into your cell phone and Power off your phone. Once your phone is powered off, Slide out your keyboard and hold the Up Arrow and press the power button. You will see a boot loader screen pop up and it will say Battery OK, Transfer mode USB. You will see the computer detect the USB device and install the new drivers onto Windows.
If the drivers in Windows Fail DO NOT PROCEED. Reinstall the Motorola drivers and try this again
8) Once you see the Transfer mode say USB. Go back to RSD Lite and click Start. You will see the progress bar Executing and slowing moving up to 100%. Your phone will eventually Power on.
Do not unplug or touch it until it hits 100% if you unplug the phone early you risk screwing up the system files on your phone.
You'll know when it is done when the Progress field in the table of RSD Lite says complete. This will take between 5-10 minutes to complete
9) Once it hits 100% you will see the status change and say Please manually power up this phone.(You phone should be already powered on if not you could power it on). Once this is completed you could either turn off your phone and power it back on or you could click Close in RSD lite. A pop up window will appear saying Application is currently busy. Do you wish to continue click Yes.
UPDATE 10/27/11
After your phone reboots and doesn't get past the boot animation
1) Turn off your phone
2) Hold down X on the keyboard
3) Turn on your phone while continuing to hold X( it will boot into the recovery mode after the Motorola logo disappears)
4) When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
5) Select both 'wipe cache' and 'wipe data' from the menu.
6) Select Reboot your phone
10) Once you unplug your phone you should see all the apks or applications which were removed originally off the device back on the device (I removed practically everything and everything was restored). If you have used z4root you will notice if you open the application it is no longer rooted.
I had a Blue triangle in my notification bar. To clear this you will need to reactivate your phone. Dial *228 and press send. Once you hear the options press 1 to activate your phone. Once this is completed you get a message saying your phone is activated and to wait up to 15 mins. You will also see the blue triangle disappear and will see the 3g reappear.
11) Once you are connected start downloading over the air the new gingerbread update to your phone. Once it is complete your phone will reboot and start installing the file and once it completed you should have the new gingerbread update on your phone
To Root your Droid R2D2 Please follow the directions below (Special Thanks to psouza4 for creating this program) http://www.psouza4.com/droid3/
NOTE: Do this at your own risk. I am not responsible for any damage caused.
1. First step is that you need to make sure if all Drivers are installed.
2. Once that is done, download and install
(Windows) http://www.mediafire.com/?g226n7as6cb1y6e
(Mac/Linux) http://www.mediafire.com/?2ugcdue4cw7dtc5
3. Now, go to Settings > Applications > Development on your Droid R2D2 and enable the USB debugging option.
4. Now connect your device to the computer and make sure you select the ” Charge Only ” mode.
5. Go the folder where you extracted the zip and run MotorolaOneClickRoot.exe (Windows) or run_to_root_your_droid3.sh (Mac/Linux).
6. Once it finished just click any button to exit the program and you will see superuser installed on your Phone.
Thats it. Hopefully this was easy to understand and works for everyone.
I cannot even root my phone. It will not go past the first rebooting stage. Any advice?
Are you currently on 2.3.3 or you still on 2.2?
Also make sure debugging mode is on and you have the correct motorola drivers installed.
Cant get VRZ file to work.
Hello,
I am trying to run threw this to reset my R2D2 Droid 2. When I try and download the VRZ_A957_2.4.5_1FF_01 file from the the link you provided all I get is a rar file that doesn't work on RSD Lite. Am i missing something on the download sight for the VRZ file?
---------- Post added at 08:41 PM ---------- Previous post was at 08:09 PM ----------
Hello again,
Sorry for my stupidity I forgot a rar file is a compressed file and I had to download win zip to decompress it. Don't deal with a lot of compressed files. Thank you for all this info will post if I got it to work.
all good. let me know if it works or if you get stuck
ok so i've been working at doing this for roughly an hour the damn drivers won't install on my computer...
Where you able to install Download Motorola 5.2.0 Driver with MotoHelper or are you getting stuck when your phone is connected to the pc?
Worked for me
Awesome, worked for me from my mac. I did get an error between phases 2 and 3 of the root process, but it worked anyway:
* Running exploit [part 2 of 3]...
*
* Rebooting the phone... when the reboot is complete, you may need to unlock the phone to continue.
*
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Running exploit [part 3 of 3]...
remount succeeded
Does this only work for the Motorola Droid R2D2 or will it work for the Motorola Droid 2 with the Gingerbread 2.3.3? Which I thought are the same phone except for the R2D2 add-on's.
ehrune - I am glad it worked for you. I will write a email to psouza and see what he says on it or ill look for an new update maybe it was a known issue which is now fixed
dfthompson - I own a droid R2D2 phone which is technically a Droid 2 with all the add-ins as you stated. I wrote the instructions because if you were like me and deleted all the bloat and junk off your phone (when you originally purchased it) you are unable to do the OTH gingerbread update because it will fail once you are doing the installation.
The file is for 2.2
thank you for posting this. my phone has been trying to update for weeks every night around midnight and failing, this is a huge help.
I must admit, after using it for a week, this update sucks big-time. Everything is much slower, button presses take a second or two to register, etc. Anyone else seeing this?
well said, guys these instructions are flawless. basic computer skills required
Ok so does this exe file get run from the computer or launch it from the phone?
Sent from my DROID2 using XDA App
Everything is done using the PC the only thing you need to do with the phone is plug it into the computer and to turn it on to go into the boot screen as instructed.
Ehrune - Yes i notice a few things running slower. i removed a ton of apk's and changed some settings and it works a lot better
boot loop
the flash was 100% successful, but now my phone is stuck in a boot loop. should I try reflashing?
edit: I ended up booting into recovery & doing a factory reset. I was able to boot & run the update from there. Good thing I backed up first..
still locked! afther full flash & no way to factory reset on my phone
i only need to factory reset ive try any times with
---------------------------------------------------
Power down the DROID 2 by holding the power button and then selecting Power Off
Hold the X key on the keyboard and turn the power back on, keep holding down the X key until you see a yellow triangle icon
Now close the slider and hold down the Volume Up button, then press the Camera button while still holding volume up
A menu will appear and one of the choices will be "wipe data/factory reset" -- use the direction pad on they keyboard to select this option
Scroll down using the direction pad to the "yes" option and select it with the d-pad select key
---------------------------------------------------
& with
---------------------------------------------------
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
---------------------------------------------------
the hard reset no work for my with any form (& the keys7Buttons are working properly)
i been full flashed Thanks to your tutorial
But still locked
Too many attempts
any ideas¿?
I lost my SBF file for R2-D2, and the link not available for now (multiupload). can anyone help me where I can find the file?
Thanks
I'm also looking for the r2-d2 sbf. All the links I come across are 1 of 2 dead links. Either the multiupload or the adrive links. None of which are standing today. Am I to believe that no one has a copy to upload elsewhere? So can someone please point me in the right direction.
I already found the file.
u can email me for the link, I don't have any right to post the link here
my email: [email protected]
Related
Last night I tried using this thread http://forum.xda-developers.com/showthread.php?t=853209, to update my epic's software.. I got the phone in download mode no prob, had it hooked up, had the .pit file supplied in the download in its' spot and the .tar file in the pda spot. I had read that I need to have both reboot and reset time checked (although I had also read to only have reboot checked and NOT reset time, so I sorta need advice on that part..). Anyways, everything was in it's place, the phone showed up in com1, I clicked "start" and nothing happened... I walked away from the computer since it was taking a while thinking that maybe it was just a slow process (even though most posts are talking about how quick and easy it was...). When I came back, it said that it had failed, and that whatever had been done was removed. Now, my epic doesn't boot up... I can still get into the yellow download screen with the digging android that says clearly "downloading..." under it, so I know it's not completely bricked.. and I can get to the android recovery (2e) screen SOMETIMES, but that really doesn't help since there's only the option to "reboot", "install sdcard:update.zip" , and wipe data/factory reset along with wipe cache.. and install sdcard doesn't do anything. It just fails. If I try to boot the phone normally, it goes to the screen with the phone and computer connected by a yield sign. Does that mean connect phone to computer?
That's about all that the phone is able to do... (at least, that's all I can get it to do).
when I plug it into the computer, it picks up that I plug something in, but then comes up with the message "unrecognized device". Some other people have had this problem and were told to reinstall the drivers. I tried and now, because my phone doesn't boot up, it can't reinstall the drivers.. nice. (sidenote, what drivers are usually used? Just the one off Samsung's website? (about 9.5 mb?)
Anyways, that's about all that I can do. I need some advice on what exactly to do with this.. can I do anything? I should be getting a hold of a friend's laptop tonight with the samsung drivers on it from the last time I used it so I'm probably going to see if odin will pick up my phone on that..
If I were you here's what I would do:
Step 1 ) Return everything to stock epic: http://forum.xda-developers.com/showthread.php?t=773032
Step 2) Consider flashing to the new froyo only if you want to dedicate the time it requires in learning the process.
If step 2 yes then:
* One Click root / cwm
* Put Desired ROM (that includes kernel) onto SD CARD
* Install D17 Modem using ODIN
* Boot into CWM (power, down volume, bottom on bottom right)
* Wipe everything 3 times
* Install ROM using CWM.
arsenik13 said:
If I were you here's what I would do:
Step 1 ) Return everything to stock epic: http://forum.xda-developers.com/showthread.php?t=773032
Step 2) Consider flashing to the new froyo only if you want to dedicate the time it requires in learning the process.
If step 2 yes then:
* One Click root / cwm
* Put Desired ROM (that includes kernel) onto SD CARD
* Install D17 Modem using ODIN
* Boot into CWM (power, down volume, bottom on bottom right)
* Wipe everything 3 times
* Install ROM using CWM.
Click to expand...
Click to collapse
Already had phone rooted about as soon as I got it.. I tried the whole process again on a different computer and it worked like a charm. Was just the computer I used before was basically crap. Thanks though
AS OF RIGHT NOW THIS WILL NOT WORK FOR 32A DEVICES WITH THE 6.35 RADIO
I AM NO LONGER SUPPORTING THIS THREAD SINCE I HAVE MOVED ON TO THE HTC SENSATION AND NO LONGER HAVE A MYTOUCH 3G TO MESS WITH. THIS DOES NOT MEAN THAT YOU CAN NO LONGER POST ISSUES IN THE THREAD SINCE OTHER MEMBERS WILL HOPEFULLY STILL HELP OUT.
As Amon Ra put it:
"The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!"
There's been a lot of questioning about how to root the new 2.2.1 updates that have rolled out for myTouch users to get a custom ROM loaded. So I decided to create an updated guide. I'm writing this as I'm rooting my own myTouch 1.2 so it should be pretty accurate, but we'll find out. Please please please read through this whole post before doing anything! Without further adu, let's begin.
1. First thing you need to know is what kind of myTouch you have. With the phone turned off, boot into fastboot by holding (back+power). You'll get something that looks like this:
Code:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
What your looking for is whether you have 32A or 32B in the first line and what you've got in the radio line. Write this down for reference later on. (If you have a myTouch with the headphone jack on top, you need to read this first.)
2. Let's go ahead and get all the downloads out of the way since this is probably the single longest step. Download each of the following items:
Everyone - AndroidSDK
Everyone - SuperOneClick, just download the latest version at the bottom of the first post.
Everyone - CyanogenMod 5.0.8-DS
Everyone - Google Add-on for CM 5.0.8
Only if the first line in fastboot says 32A and you DO NOT have a headphone jack - EBI1 Port for CM 5.0.8
Only if the radio line says 2.22.27.08 or 2.22.28.25 - New Kernel for New Radio's
It may make it easier to put all the files in the same folder once downloaded. For example, open "My Documents" and make a new folder called "Phone Stuff" and put everything in there.
3. Extract the contents of the "android-sdk_r08-windows.zip" files to any folder (just make sure you know where). After extracting, using file explorer find the file called "SDK Manager" and open it. When it starts up a window will pop-up with "Choose packages to install" in the upper left-hand corner, just click Cancel. In the left pane, select "Available Packages", then in the right pane, expand "Third party add-ons", then "Google Inc. add-ons", and finally check "Google USB Driver Package". In the bottom right-hand corner, click "Install Selected". In the window that opens, make sure "Accept" is selected, then click install. Select "Yes" in the next window and close everything out.
4. With the phone powered on and sitting at the home screen, press Menu->Settings->Applications->Development->Look at "USB Debuggin" and make sure it is turned on. Now, plug the phone into the computer with your USB cable. Mount your SD card to the computer using the option in the notification bar. Copy over the CM 5.0.8 and Google Add-on to the root of your SD card.
5. Back on the computer, locate the SuperOneClickv*.zip file and extract it to a folder (make sure you know where). Navigate to that folder, and open the SuperOneClick.exe. Once it starts up, hit the "Root" button.
Here's the tricky part, if you see a line saying "***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***" then do as it says and turn off "USB Debugging" on the phone. Wait until the program shows "Waiting for device..." and turn USB Debugging back on. It may take a few tries before the program finishes. Your phone may do some funky stuff, such as the screen going black showing "Android System" at the top, just let it sit and once it starts responding again, turn USB Debugging back on. Once the program finishes, it'll say "Root files have been installed! Would you like to run a test?" click yes. In the next prompt, click OK. Once you get a pop-up saying "Your device has been rooted! Would you like to donate?" click yes to donate to the program's creator or click no to continue on. If you get "failed" whenever running the root test from SuperOneClick, you need to run the program again.
5a. Reboot the phone.
6. Now, from the phone, download ROM Manager and SuperUser from the market and install them.
7. Once they both are installed, open ROM Manager. Click "OK" to both the prompts that come up. At the top, click the "Flash ClockworkMod Recovery" button. A prompt will come up asking you to confirm your phone model. If you have a 32B phone or the myTouch 1.2 (headphone jack), select "ION/MyTouch 3G". If you have a 32A phone without a headphone jack, select HTC Magic. Once it has finished flashing, click OK. Scroll to the bottom of the ROM Manager menu and select "Flash Alternate Recovery". If you have a 32B/1.2 phone you should see "RA Recovery v1.7.0G". If you have a 32A without a headphone jack, you should see "RA Recovery v1.7.0H". Once verified to be correct, select that option and then click OK. Once completed click OK again. Power off your phone.
NOTE: I use these steps to get Amon Ra's Recovery installed since the steps in this guide will be using it and not Clockwork Mod. If, after getting more familiar with using recovery, you want to use ClockworkMod recovery instead, the steps are the same, just don't select the "Flash alternate recovery" option.
8. With the phone powered off, hold down (home+power) to get into your new custom recovery. Here you'll use the trackball to navigate the menu's, press the trackball to select, and the back button to go back. From the main menu, select "Backup/Restore", then select Nand backup and press the home button to confirm. Once it's completed the backup, use the back button to get back to the main menu. Select the "Wipe" option, then select "Wipe data/factory reset", press home when prompt, then press "Wipe cache", hit home when prompted, then select "Wipe Dalvik-cache", hit home when prompted, and finally back out to the main menu. Select the "Flash zip from sdcard" option, first select the CM 5.0.8.zip and hit home to confirm, then the Google Add-on file and select home to confirm.
8a. If you have a 32A device WITHOUT a headphone jack, you'll now also flash the EBI1 port (boot-cm_2634.7_ds_32a-oc-uv-xtra-fp-091310) and hit home to confirm when prompted.
8b. If you have either of the new radios (2.22.27.08 or 2.22.28.25) then flash the new kernel (ezBiffTestKernel20110222-2708_S.zip) and hit home to confirm when prompted.
NOTE: If you don't get into the custome recovery (you get a picture with a phone and a triangle with exclamation mark) boot back up as normal and repeat step #7.
NOTE 2: The backup you make is in case anything goes wrong and the ROM doesn't boot. Go back into recovery, select the "Backup/Restore" option, then select the "Nand restore" option. Just click the trackball throught the menus and hit home to confirm when prompted, then reboot.
9. After flashing all the files, back out to the main menu again and select "Reboot system now". It will take about 5-10 minutes for your phone to boot the first time. Once your in, enjoy.
If you need help and I'm not on here, feel free to try and get up with me on Google Talk or MSN at [email protected].
Thanks to Amon Ra for his recovery images!
Thanks to the Cyanogen team for an awesome ROM!
Thanks to Pershoot for his awesome kernels!
Thanks to CLShortFuse for his awesome app!
Thanks to the ClockworkMod team for their awesome app!
Thanks to MarcAntonyy for pointing out I'm a retard!
Resources:
SuperOneClick
Kernels
CyanogenMod
OK, I've updated the original guide with ezTerry's kernel that will work with the 2708/2825 radio's, which should completely alleviate people running into bootloops.
Things I deem important.
1. CLShortFuse is rolling out updates for SuperOneClick, so now the link directs you to his post instead of being a direct download.
2. I updated the guide to flash CM 5.0.8 instead of CM 6.1. Some people are having issues getting CM 6.1 flashed, plus CM 5.0.8 (for me at least) is much more stable than CM 6.1.
3. Added steps to take if the first guide ends with you being in a boot loop in the second post.
4. First guide updated to hopefully keep users from running into the boot loop.
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
Is this normal?
No, try running the program again.
Did you get my PM, the one I sent you isn't showing up in my "Sent" items. For some reason your /system partition is full, so SuperOneClick is failing trying to push the SuperUser.apk. Try installing SuperUser from the market and then running SuperOneClick.
Yeah. Still nothing. Could the update possibly lock me from rooting?
Sent from my T-Mobile myTouch 3G using XDA App
No, I did this guide from the 2.2.1 update. Did you pull it OTA or did you manually do the update? Just to be sure, it's still failing after installing SuperUser from the market, correct?
Got root, but cant install recovery
Used superoneclick and all went well. I cant get a alt recovery on my phone though. once i reset the phone, holding the home button I get the green screen with th fastboot usb in the right corner. I have full sdk with limited adb skills. I need Clockwork or preferably AmonRA. I get superuser permissions and all but I am trying to avoid re-partioning my card. Is there a way around this?
Installing a recovery will not repartition your SD card. Actually, nothing in this guide will partition or require that you partition your SD card.
It was the manual update.
Sent from my T-Mobile myTouch 3G using XDA App
Something might have been hosed. Do you have the 3.5mm jack? You may want to try booting into recovery, do a data wipe/factory reset, reapply the update, then try rooting again. You should be out of system memory. Another quick thing you can try is turn your phone off and start the program. When it gets to "waiting for device" turn your phone on with USB debugging on. Yeah...try that first, then reapplying the update.
On a side note, the developer of SuperOneClick is working on version 2.0, which will hopefully fix the issue your experiencing plus the issue with having to toggle USB debugging, but for the time being, let's get this figured out.
I am going to try this guide, this will be my first time rooting as i have a 2.2 fender mytouch will this guide work?
how long will this take? i have to work in an hour lol
Assuming everything goes smoothly, about 30 minutes. Honestly though, nothing in the guide will prevent you from using your phone until you start flashing the custom ROM. Furthermore, once you get rooted with the program and get ROM Manager working and move the files, you won't need a computer anymore.
Maybe print the directions and take them with if you can use your phone while at work. Yes this will work on a Fender with the new update. I made it using my 1.2 on the update, which is pretty much the exact same thing.
it would be hell of alot easier with a Youtube Video guide? that way we can follow exactly step by step without messing up the phone! also will i be able to sign in using WIFI? beause there is no data coverage in my area of living. if i user superoneclick will that reset my phone to factory settings and make me sign into google again? lol i dont wanna drive 2 hours to the nearest data coverage area. pain in the ass lol
SuperOneClick just roots the 2.2.1 ROM to allow you to use ROM Manager so no data reset in that part. You will be doing a factory reset when you flash CM 6.1, however CM 6.1 will allow you to update over wifi. Even if something happens when you start flashing CM 6.1, you can restore your backup that you make following the guide, which will still be activated. Are you living on the top of a mountain or something? I haven't been anywhere that gets a signal without data coverage (at least G).
lol check my zip code 50501 you'll see i have no data coverage for miles lol its ridic. and we use a partner web with t-mobile.
Dude, that sucks, I think you went with the wrong carrier, lol. Are you in the Army? Navy here.
Ahhh, your roaming on AT&T's network. You just need to enable roaming data. Go to Menu->Settings->Wireless & Networks->Mobile networks->And check "Data roaming". T-Mobile doesn't charge for domestic roaming, so as long as your in the US, you'll be good.
OK , cool but,
still an issue with recovery. I try to install a recovery image via fastbooot and it wont read it. wiping my card is redundant. but if I must? Then I willThat is an excellent tool though.
I had apex 1.4.1 on my Droid 2 and I had the green evolution theme on it. I went to reinstall the 1.4.1 so I would have it without the green theme because I had other mods to install to it. I did what I wanted to and then I rebooted, It was stuck at the apex boot screen which is extremely annoying and it kept replaying and the phone simply would not turn on. So I reluctantly wiped the phone. I start it normally and it shows the motorola logo and then the screen stays black. So I'm guessing there is literally nothing on the phone. When I go to bootloader, my computer recognizes it as an OMAP flash drive. I'm completely lost and I don't know if there is anything I can do to fix this. Can someone please help me? Thanks.
SBF is your best friend for Motorola phones.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
Latest Moto Drivers:
http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
If you can get to the bootloader, then your phone is not bricked.
Also, before I ever attempt to root a device I've not rooted before, I always search and find a recovery method for that phone. In Motorola's Case, it is SBF files. In HTC's case, its RUU files.
ALWAYS ALWAYS ALWAYS find a recovery method for your phone before you root it. Also, read EVERYTHING you can about rooting your particular phone before rooting it, that way you would already know how to fix it if you mess up.
My computer won't let me transfer files to my phone, will this help?
I tried to follow what it said and I have no idea what I'm doing. appreciate the help though.
jakeg2012 said:
I tried to follow what it said and I have no idea what I'm doing. appreciate the help though.
Click to expand...
Click to collapse
Well, I don't see you being able to get your phone back in working order otherwise.
Its really easy to do.
1. Download and install RSDlite 4.9 on your computer. (download from here h t t p://www.mobile-files.com/forum/showthread.php/763-RSD-Lite-4.9)
2. Download the latest Moto drivers and install on your computer.
3. Download the SBF file and put on your desktop.
4. Plug your phone into your computer, and your phone should turn on and be in bootloader mode (black screen with white text)
5. Run RSDlite.
In RSDlite, there should be a box with "..." Click that, and then choose the SBF file from your desktop. Hit start, and let it work. DO NOT shut off your computer or unplug your phone while this is running.
When RSDlite says its finished, unplug the phone, turn it off.
Now you need to boot into recovery. To do this, hold "x" on your keyboard and the power button. When a screen with the triangle comes up, hit the search button on your keyboard (magnifying glass). Choose "wipe data/factory reset". When thats done, select "wipe cache".
Now reboot the phone, and it should boot up normally. You will need to reactivate your phone, which you should be prompted to do in the setup.
I did everything. Everytime I put the sbf file (which shows up as a zip file) into a folder I look for it through rsd lite and I can't find any zip files/sbf files I've downloaded. What do I do now? Am I doing something wrong? sorry for being a pest btw.
Your not being a pest
You need go extract the .sbf file from the zip folder to somewhere like your desktop. Then find it in rsdlite
Sent from my Liberated DROID 2
I can't find a working sbf file. Every time I use it I get FAIL.
Here is a link to download the Froyo software so you can do it via the sdcard instead of thru motorolas update program.
http://www.motorola.com/staticfiles...dcards/US-EN/flipside/index.html?pubid=987654
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
pamaguin said:
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
Click to expand...
Click to collapse
What was the setup on his phone before the update? Rooted, how much memory avail, etc. Also, did you try both methods, or just this one?
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
pamaguin said:
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
Click to expand...
Click to collapse
I wish I had the answer to this. It baffles me as so many have had luck. Hopefully someone will come along that knows more than I.
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Where can I find on how to use RSD lite? And I've tried renaming the file to update with no luck; "installation abort".
JBallin4life27 said:
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Click to expand...
Click to collapse
Sent from my Xoom using XDA App
Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
You can get a stock AT&T ROM here (2nd post) or here (2nd post). I believe that they both point at the same file.
I can state that when I DLed that file it did work for my Flipside.
The hashes for the file I tested were:
CRC32: 92E73801
MD5: 7B529FE7D732EC4E71F5955C887E33A5
SHA-1: 7B49401A107F6DD779DBA0F55DECF473501E554A
Filesize: 196 MB (206,426,725 bytes)
This hashes/filesize are for the extracted sbf file.
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
*you can find RSD Lite by just googling and downloading it*
Will post instructions for using RSD Lite in a second
This guide is for anyone who:
Has ever used RSD Lite, given up at the "Please Reboot this Phone Manually" status, and closed RSD Lite despite being warned: "Application is currently busy. Closing application may DAMAGE the attached device. Do you wish to continue?".
Has never used RSD Lite, but are going to, and want to do it right when you do.
The action described in the first bullet is quite common, so if you've done it, you're not an idiot. I think pretty much every RSD Lite YouTube video shows it being done that way, and it doesn't seem to cause any trouble, so who cares, right? Maybe it's just me, but I'd rather see a result of "PASS" when doing something this critical if at all possible. Here's how to do just that.
Proper RSD Lite flashing procedure:
1. Be sure you have your SBF file somewhere that you can find it. 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. Otherwise, hopefully the source of your file lists its MD5sum. If so, you should verify the MD5sum of your file to make sure it is not corrupt. You can permanently brick your phone with a corrupted SBF (if it's corrupted in just the right place).
2. Plug your phone into a USB cable attached to your computer. Depending on whether or not you have USB debugging turned on, have had your phone attached to the computer recently, etc., you will at least probably hear the "device insertion tone" in Windows, and you may see the New Hardware Wizard install the drivers for your phone. Wait until your computer settles and looks bored before continuing.
3. Power down your phone. Once your phone is all the way "off", slide your keyboard open (on the phone).
4. Summon your best contortionist skills, and press on the "up" direction of the directional keypad rocker (the direction toward the screen -- which could really be to the right depending on how you're holding the phone) [pic]. While holding the dpad in the up direction, simultaneously press and hold the power button of the phone. When you see the backlight of the screen come on you can release the power button and the bootloader screen should appear (it will say "Bootloader" in the upper left corner). You can release the dpad. At the bottom of the text on the screen it should say "Transfer Mode: USB" if your cable is properly connected. If it says "Connect USB Data Cable", then you need to do so.
5. Run RSD Lite. If you're on a version of Windows newer than XP, remember to run RSD Lite as administrator by right clicking its menu choice and choosing "Run as Administrator".
6. At this point the phone should show up in the grid in the bottom half of the RSD Lite window. Give it a minute or two if it doesn't show up right away. Sometimes it takes Windows a minute (or 2 or 3) to let go of the phone and pick it back up again after rebooting into the bootloader. If after a couple minutes your phone still isn't listed in the "Model" column of the bottom section, in RSD Lite, click Config, Device Id Options, and choose "First-Come-First-ServeDeviceId Mode" and press "OK". RSD Lite may say you need to restart RSD -- if so, do so.
7. Assuming that you now can see your phone listed, click the "..." button to the right of the "Filename:" box. Find the SBF file you intend to flash on your hard drive. After choosing the file the right hand File details pane will fill in.
8. OK, this step is where you are going to press "Start" in RSD Lite, but don't do that yet. Before you press Start, read step 9. Step 9 has some timing sensitive tasks. If you do step 9 wrong it's not going to break anything, but you'll waste some time going through an un-needed boot and shutdown of the OS. Once you've read Step 9 and know what you'll be doing next, go ahead and press Start.
9. So far this has all been routine and you're thinking "so what?". This next part is what will get you a result of PASS instead of a warning about destroying your phone. After clicking Start the flashing process goes through several distinct steps. At some point there will be a bit of a delay with RSD Lite showing a status of "Phone[0000]: Waiting for re-enumeration". After that is when the actual flashing happens. When the flashing has completed, RSD Lite is going to issue a "reboot-bootloader" command to your phone. Unfortunately the Droid does not appear to implement the reboot-bootloader command correctly and does a normal reboot instead. If you don't "catch the boot" by holding up on the dpad key the OS will boot. Just before sending the reboot instruction to your phone the status in RSD Lite will change to "Phone[0000]: Phone is being rebooted". On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter. You want to be already holding the dpad key up when this happens. If you followed the instructions for Step 8 you have pre-read this step and knew to be ready for this. If not, your phone is probably already rebooted into the OS. If you miss it and the phone boots the OS it's no big deal (unless the instructions for the particular SBF you're flashing say otherwise). If that happens, let the phone finish its boot, and then just do a shutdown like normal. Then press/hold up on the dpad key and power back on. RSD Lite is patient and will wait.
10. You should now be looking at the bootloader on the phone, and RSD Lite should still be saying "Phone[0000]: Phone is being rebooted". If too much time has passed RSD Lite may be saying "Please manually boot the phone". The "Progress" value on the screen will keep incrementing, and at some point before, or at, 100% the result should change to "PASS". You can now click Close to exit RSD Lite without getting any disturbing warnings.
Congratulations. You've just done a proper SBF flash! The result is not simply cosmetic. RSD Lite is doing a final integrity check after rebooting clean into the bootloader. If you do it the old way (just unplug after the reboot and ignore the warning about destroying the device) you may be just fine, but you may also miss the chance to know your flash didn't go quite right and needs to be redone.
Installing RSD Lite:
First you're going to need a Windows workstation. There is a utility called sbf_flash for Linux that will let you do it with Linux, but that is not the subject of this guide.
Next, grab RSD Lite 4.6 and the appropriate Motorola drivers (32-bit or 64-bit) for your machine. In addition to the preceding links you can get them by going to this link, then double clicking on "rsd_lite" in the right side panel (or single click in the left side panel). [Older versions of the drivers here in case they be useful to anybody: 32 bit or 64 bit.]
Install RSD Lite and the drivers on your computer. If you're running Windows XP, life is good. If you're running Vista or Windows 7 you need to be sure to run RSD Lite as Administrator (by right clicking on the choice in your Start menu and choosing "Run as Administrator"). Hopefully your computer isn't too old. Some machines with older BIOS (like 2002 era) have been known to have USB issues that cause trouble with flashing using RSD Lite.
That's all there really is to installation.
I just posted the 2.2.2 Froyo SBF file in the Flipside Development section. Check that out and use RSD Lite to flash the file...you shouldn't have any problems if you do it correctly. Let me kno if it works or you need more specific instructions
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
thehotrod11 said:
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
Click to expand...
Click to collapse
Anytime man!
any one get the white notification led working after upgrade?
data2318 said:
any one get the white notification led working after upgrade?
Click to expand...
Click to collapse
YES OMG its so damn annoying. I thought I had turned it off, but it still shows when getting an incoming call. Turning it off in settings did stop it from flashing if I have a missed call or voicemail tho.
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
ssfirme said:
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
Click to expand...
Click to collapse
Press both volume buttons on the screen with the android and exclamation mark. That'll take you to stock recovery where you need to wipe data and factory reset.
If you have to flash the sbf again, try using sbf_flash on Linux. It'll flash in times where RSD won't recognize your phone.
Linux Live\sbf_flash tut
sbf_flash binary is in attachments
Only use Defy 2nd-init for recovery
(and once its installed, steal /system/bootmenu/* and /system/bin/bootmenu from Defy CM9 from June 5th on up -- touch bootmenu is pretty awesome; replacing the bootmenu isn’t for the feint of heart.)
the only problem is i dont have linux i have windows 7
Use rsdlite sri I don't have a link on me
Sent from my Galaxy Nexus using XDA
Had same type of problem on Friday. Followed this post http://forum.xda-developers.com/showthread.php?t=1559109 now I'm back up and running.
ssfirme said:
the only problem is i dont have linux i have windows 7
Click to expand...
Click to collapse
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
yes i have it in bootloader mode
Did you install everything before plugging phone in?
Try uninstalling everything motorola related and reinstalling just the drivers....On a previous Win7 install nothing was recognized, but on a reinstall of the entire system it worked fine and still does. I still recommend the Linux way over RSD because it will flash your phone regardless, provided you can access the loader.
I still haven't gotten native tethering to work with Windows, but then again, I quit trying sometime around December or January.
ssfirme said:
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
Click to expand...
Click to collapse
This is for all those people who are having trouble flashing with RSDlite in Vista & WIndows 7.
If I am right, RSD lite does not seem to recognize the sbf file after you select it and instead the "start" button remains grayed out.
If that's the case, here the solution:
I had a similar problem and sucessfully used the command line parameters for RSDlite to force a flash. I managed to get a signed/unsigned firmware installed.
You need to copy the firmware you want to flash into the RSDlite directory in your program files folder.
Make sure you are in bootloader mode first.
Then, open command prompt and "cd" to the RSDlite directory
eg:
> cd C:\
> cd Program Files
> cd motorola
> cd RSDlite
>
now for the flashing type:
> SDL.exe -f xxxx.sbf -t 2
where xxxx.sbf is the firmware you are flashing to the phone.
flashing will begin shortly afterwards.
It worked for me, but in the end, show FAIL STATUS.
skeevy420 said:
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
Click to expand...
Click to collapse
Thank you sooooooooooooooooo much!
After several hours of messing with my brothers Bravo, I finally got it working by following your instructions.
Really: I'm speechlees man.
hard bricked my phone
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
dzdonce said:
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
Click to expand...
Click to collapse
Not sure if this will help since I did not watch the video myself, but a quick Google search gave me a video describing how to take a Motorola USB cable and modify it to unbrick a phone. I did not watch the video yet so I don't know how relevant it is to your problem. But just by looking at the video preview it looks like the difficulty level may be pretty high... Here is the link:
http://m.youtube.com/watch?v=XwwI_6doBWk
Sent from my LG-D415 using XDA Free mobile app