Ok, So I have successfully rooted my D3 and all went fine. I installed the installed the Steel Droid Rom but later found out that I can no longer access my home email account using this ROM for some reason and stupid me didnt create a nandroid backup before installing the Steel Droid. I know, stupid. So now I want to SBF my phone and start over. However, I can find a working copy of RSD Lite. Can someone point me to a website that would have it or provide a working link for it? Also, I am trying to use the following threat:
[Recovery] RSD v5.5.0 and 5.5.184 (aka 5.6.890) fastboot partitions/flashable zip: http://forum.xda-developers.com/show....php?t=1255198
There are 3 separate sections in the OP:
Flashable File, Moto-Fast Boot and RSD Lite
In addition to needing a working copy of RSD Lite 5.5 I also dont really understand the difference in the Flashable File and Moto-Fast Boot? Will I need to do both of these steps in order to SBF my phone back to stock? Or is the Moto-Fast an alternative option to using the flashable SBF file in RSD Lite?
I hate to be demanding, and would appreciate any help I could get, but if someone could please provide a step-by-step guide of the correct SBF process that would be absolutely amazing.
Thanks.
EDIT.....I FOUND A LINK TO RSD LITE 5.5....
hey all - I got a new D3 replacement today after the touch screen stopped working on the old one. it came with 5.7.906 installed. i am confused as to weather there is a way to unbrick it if i manage to muss it up when i go back to cm9. i love cm9 and hate the stock rom but considering this is my 5th D3 i am not willing to flash roms if i have no way to return to stock in case of hardware malfunction so i can get a new one under waranty
i appreciate any information on the topic
As long as you can get to the Moto Bootloader, then it is 90% likely that you can unbrick it. The tools can be found here:
http://forum.xda-developers.com/showthread.php?t=1255198&page=23
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
ovelayer said:
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
Click to expand...
Click to collapse
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
redsox985 said:
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
Click to expand...
Click to collapse
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
ovelayer said:
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
Click to expand...
Click to collapse
Oh, ok, so these are just the 5.6.890 FXZ files?
redsox985 said:
Oh, ok, so these are just the 5.6.890 FXZ files?
Click to expand...
Click to collapse
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Q9Nap said:
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
redsox985 said:
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
Click to expand...
Click to collapse
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Q9Nap said:
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Click to expand...
Click to collapse
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
redsox985 said:
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
Click to expand...
Click to collapse
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Q9Nap said:
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Click to expand...
Click to collapse
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Q9Nap said:
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Click to expand...
Click to collapse
Nope, XT862 with WiFi tether hacked radio. Request sent.
redsox985 said:
Nope, XT862 with WiFi tether hacked radio. Request sent.
Click to expand...
Click to collapse
yeah, i'd make sure your'e on fully stock 890 with no modifications before flashing 894; it should work. request accepted.
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
nemiroG1 said:
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
Click to expand...
Click to collapse
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
redsox985 said:
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
Click to expand...
Click to collapse
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Q9Nap said:
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Click to expand...
Click to collapse
I never did get around to formatting my SD card. Stock recovery only sees the EXT SD correct?
I'm currently chatting with Moto... This is odd. I'm going to start my own thread for it to leave this one be.
Hi,
I upgrade to 906 then downgrade to 890 by using 1 click SBF method work like charm, but I can't install XT883 get error RSD lite in first step FAIL ? I think this method help to downgrade but not completely that's why I can't flash XT883 ROM. Before upgrading to 906, I can easily flash XT883 ROM with RSD lite 5.6.
And also saw this thread but I can't understand the XML coding part I'm totally new.
Can body just help me to flashing XT883, So I can run both network CDMA and GSM because there is no other ROM which can run both network in my knowledge
Close the thread issue solved myself
no need to close the thread, maybe you want to share, how you solved the problem or people with a similar issue will come along.
@NIGHTMARE-
Please help me out. I want to flash XT883 ROM on 906.
Thanks.
kapilthio said:
@NIGHTMARE-
Please help me out. I want to flash XT883 ROM on 906.
Thanks.
Click to expand...
Click to collapse
Hello, I have flashed XT883 on XT862 successfully through the following steps.
(1) Apply 1-Click flash to downgrade from .906 to .890
(2) Download MOTO XT883_ROM 2.3.6-SLNCT-60.3.250.zip. Unzip it to a folder 'A'.
(3) Unzip the 1-Click flash to another folder 'B'.
(4) Copy the content of folder 'A' to a new folder 'C'.
(5) Copy boot, cdt, recovery of folder 'B' into folder 'C' >> Replace them.
(6) Reboot into Fastboot. Check your Fastboot version is 0A.53.
(7) Flash using the XML in folder 'C'.
The screen will reboot and it will take between 10 - 15 minutes to get up.
Once up, leave the Network as 'Global' or 'CDMA'. Do not choose 'GSM'.
Go to APN and set your operator settings.
That's it!
The above worked for me. Unfortunately the network is unstable. It often switch down my 3G and remains in 2G network. Frustrating.
If someone knows how to remains in 3G network. Kindly shared with us!
soo i was wondering if theres a methood on how to get back to stock on the motorola droid? i put a gingerbread rom on it and its terrible, i would like to fully unroot it back to the way it was.
You'll need RSD Lite and a fitting .sbf file to flash your phone back to stock.
Here's a tutorial: http://forum.xda-developers.com/showthread.php?t=696845&highlight=rsd
It's for Milestone (non-US version of Droid), but the process should be identical.
You'll need to find the .sbf file yourself.
Google for "Droid sbf <your provider> <android version>" and you should find it.
For Advanced Users only till I get some feedback.
For those DX users on a non-verizon network
I removed the Radio/ Baseband files from 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf
and repacked with Portable Sbf Tool.zip
This will allow you the flash 2.3.4/4.5.621 with rsd lite, without needing to re-flash radio to cricket, metroPCS...
This will not change the radio to cricket, metroPCS...
Please Do Not Use this if you do not know how to Flash Radio to your Carrier, should this fails.
Download 2.3.4.4.5.621.no.radio.sbf.zip
Mega
Dev-Host
androidfilehost
Just Flash like the normal sbf, it just skips the reflash of the radio.
Follow my [How-To] Flash .SBF/Firmware with RSD Lite
My Testing and restoring Verizon radio settings
1. Flashed Alltel Radio with, 1FF-p3a_shadow_cdma_shadow-user-2.3.5-4.5.1_57_MX2-34-111019-release-keys-signed-alltel-US.sbf with RSD Lite
which changed Stock DX 2.3.4 BaseBand (Radio) from BP_c_01.09.15p to alltel's BP_C_02.12.00R along with changing the rest of the firmware to the Milestone X.
2. Flashed my 2.3.4.4.5.621.no.radio.sbf.zip with RSD Lite
Firmware changed back to stock Droid X 2.3.4/4.5.621 except Baseband BP_C_02.12.00R remained.
3. Flashed Verizon Radio with, Full 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf, and changed to stock Droid X Baseband BP_C_01.09.15p .
Note: Droid X screen went completely dark during this last step, but RSD Lite continued to show progress and phone booted normally.
change log:
30 March 2014 Grammer, Dev-Host link, AndroiFileHost link, Portable Sbf Tool.zip link
03 April 2014 reworded
I'm not using a network anyways so I can give this a shot
Sent from my Nexus 7 using Tapatalk
Nexus11 said:
I'm not using a network anyways so I can give this a shot
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks, but it's the network radio settings I'm not sure about.
I didn't time it,but it seemed to flash faster than full sbf.