256 replies to this topic

[JungleKing76]

RSD back to stock is more like 20 minutes or so. The 5 minutes was referring to the update process from 744 to 748 or from 748 to 173.

SIDE NOTE:

I noticed that the instructions for RSD say to extract the files from the zip but I just wanted to let everyone know that this is not required. I have flashed my fastboot files in RSD several times and have never extracted anything. I simply click the little box in RSD with the "..." and then select the actual zip for the fasboot file and RSD will uncompress/extract it automatically.

[SoLongSidekick]

Very thorough Matt thanks.

Once thing you might want to add is that right after you press "Start" the phone will quickly reboot a couple of times. I know that scared me the first time I used RSD haha.

[Rouger]

Great write-up.

I've used this a few times now. One thing I found is I do the optional step 9 as a mandatory step since I want the system completely clear of all past info when I'm resetting.

[powerdan74]

mattlgroff, thank you so much for the excellent write up. I was having issue with GPS not finding any satellites. I searched for any fixes without rooting in case I had to send in for warranty and this was my last ditch effort. I went back to stock 744 and also performed the optional step 9 wipe data/factory reset. It fixed the GPS issue. I have since done the OTA 748 update and GPS is still working. In step 9 the only thing the puzzled me at first was that when you get to the triangle you have to use the power button to make the selection. Thanks again, Dan.

[snives]

Ran into a new problem I hadn't seen before, so figured I would post in case anybody else runs into it.

I opened RSD, put my phone into AP Fastboot, loaded the files, selected uncompress only, then after verifying the sig it loaded from the files I started flashing. The flashing process went VERY fast (2-3 minutes tops) and failed at step 17. When trying to run again, it said "allow-mbmloader-flashing-mbm.bin" was the wrong size and failed immediately. Hitting start an additional time afterwards would cause it to sit pretending to do step 1 indefinitely (gave it ~10 minutes). Closing/re-opening RSD and uncompressing the files again netted the same problem. The issue however, was that although RSDLite said it was going to overwrite the uncompressed files, it didn't. When looking at the uncompressed folder all it contained was just allow-mbmloader-flashing-mbm.bin with the wrong file size. The 'overwrite' apparently failed even though I told it to allow. The fix was fairly simple though, just delete the uncompressed files and run it again. For reference, I have used these files a few times already, so I knew they were not corrupted. If you get this the first time you ever use RSD, verify your fastboot files have the correct hash values first! (You should be doing that before running them anyways).

[coletrane09]

WARNING: Always make sure you have PLENTY of battery power before performing any type of Fastboot restore. 70% of more is high recommended (RSD Lite and the Command Line Method both won't work if you have low battery). We at DroidRzr.com are not responsible for anything you do to your phone, including bricking it.

Note: You can also use a command line method with a smaller file-size

Please Login or Register to see this Hidden Content

Please Login or Register to see this Hidden Content

Downloads

1)

Please Login or Register to see this Hidden Content

2)

Please Login or Register to see this Hidden Content

3)

Please Login or Register to see this Hidden Content

Should look like this:


Installation

1) Install the downloaded MotoHelper USB Drivers



2) Extract the Fastboot Files ".zip" to a folder.

3) Install RSD Lite 5.6



4) Run RSD Lite 5.6 after installed.



5) Choose the extracted Fastboot ".xml" file to the folder you put it in.


Doesn't matter! As long as you can find the .xml file later for RSD Lite.




6) Put your phone into AP Fastboot mode and connect via USB.

Turn off your phone.
If your phone is frozen then hold down the Power + Volume down buttons for 8 seconds and it will turn itself off.

Please Login or Register to see this Hidden Content

Hold down both Volumes buttons + the Power button and it will boot into a black screen with white text.
Choose AP Fastboot using the on-screen instructions.
(The Volume Up button selects and your Volume Down button moves down, for those who cannot read the on-screen instructions.)
Special Note: If your device says anything other than "Device is LOCKED. Status Code: 0" then Private Message me. If it says Device is LOCKED. Status Code: 0 then that is normal! Proceed.

Plug your phone into your Windows computer's USB port. It should look like this in RSD Lite:




7) Hit the "Start" button on RSD Lite

8) Wait. Wait. Wait. Wait. Have patience. Wait. It has 18 steps of progress as shown in RSD Lite. Then it will reboot itself and install stuff. After it boots up normally you can unplug it.

9) OPTIONAL: Go back into Moto Recovery but this time choose Recovery. When you get to the "

Please Login or Register to see this Hidden Content

" with the Android press both Volume Buttons. Choose "Wipe Data/Factory Reset" (This will make sure you are COMPLETELY stock 6.11.744 with no personal data on the system. (Anything in your SD card should be safe, but apps/app data/contacts/etc. will be cleared if you do this).

Im getting an error??? following everything to a T

[coletrane09]

I have followed all these directions to a T and failed and 1/18 when pressing start??? my razr is now a retail $700 paper weight.

[mattlgroff]

I have followed all these directions to a T and failed and 1/18 when pressing start??? my razr is now a retail $700 paper weight.

Is your battery low? Is it a Droid RAZR for Verizon?

Sent from my Galaxy Nexus using Tapatalk

[coletrane09]

failed flashing process

[coletrane09]

Is your battery low? Is it a Droid RAZR for Verizon?

Sent from my Galaxy Nexus using Tapatalk

battery good droid razr I'm lost tried command method also doesnt work. Flashed theroy rom wiped everything stuck at bootloader screen

[DroidTh3ory]

battery good droid razr I'm lost tried command method also doesnt work. Flashed theroy rom wiped everything stuck at bootloader screen

Install Team Viewer.



Sent from my DROID RAZR using Tapatalk

[coletrane09]

Got it to work with command method thank god

[snives]

Got it to work with command method thank god

Try to keep yourself from getting upset next time. Remember, we are using the same method that Motorola would use to restore the system to stock. If it isn't working, then something is out of place. Once it is put back in place, it will work.

[coletrane09]

Will try rsd flash after installing team viewer....something is out of place, cannot update to 2.3.6 after using command method.

[Smacinskyjr]

ok...lets see if i can explain this right. If I put my phone into fastboot and start up rsdLITE my phone is never detected by rsdlite. If the phone is running in the "normal" mode rsdlite puts my phone into fastboot, i can physically see it happen on the phone, but rsd never recognizes the phone is now in fast boot and I get a "phone failed to boot to fastboot mode" error or something like that........any ideas what the problem may be? ive have 5.6, the recent moto drivers, the phone is build .748, I was rooted via doomlords root process, and I was usiing safestrap. |Ive been doing this stuff for quite awhile but am still a noob lol.

I'm having this same issue. I'm on a 64 bit windows 7 machine I have followed the instructions to a T, I have used several different usb ports and cables. I have tried deviating from the instructions, I have tried everything and RSD wont recognize my phone. I have gotten the command line method to work and it goes through the motions but when I try to do the OTA to 748 it fails. I really need some help, I have adb working on my machine if it matters. I would love it if someone was willing to work with me over the phone.

[mattlgroff]

I'm having this same issue. I'm on a 64 bit windows 7 machine I have followed the instructions to a T, I have used several different usb ports and cables. I have tried deviating from the instructions, I have tried everything and RSD wont recognize my phone. I have gotten the command line method to and it goes through the motions but when I try to do the OTA to 748 it fails. I really need some help, I have adb working on my machine if it matters. I would love it if someone was willing to work with me over the phone.

I can help you on Skype if you'd like. Did you see the thread in How To's called "So Your OTA Failed? Read this. (Safestrap users)" you need to say the error for OTA 6.11.748 upgrade. It can be the /preinstall/ or missing bloatware you removed/or froze.

[Smacinskyjr]

I can help you on Skype if you'd like. Did you see the thread in How To's called "So Your OTA Failed? Read this. (Safestrap users)" you need to say the error for OTA 6.11.748 upgrade. It can be the /preinstall/ or missing bloatware you removed/or froze.

PM Sent

[manny805]

this will show no trace of rooting ?

[Smacinskyjr]

this will show no trace of rooting ?

that is correct, you will have to re root afterwards

[Smacinskyjr]

I'm having this same issue. I'm on a 64 bit windows 7 machine I have followed the instructions to a T, I have used several different usb ports and cables. I have tried deviating from the instructions, I have tried everything and RSD wont recognize my phone. I have gotten the command line method to work and it goes through the motions but when I try to do the OTA to 748 it fails. I really need some help, I have adb working on my machine if it matters. I would love it if someone was willing to work with me over the phone.

On a side note I have determined that the problem that I am having is not phone related it is something going wrong on the computers end. I have come to this conclusion because I have tried more than one phone on my PC and it RSD Lite won't recognize it either. So if there is anyone out there that can shed some light on this situation I and I'm sure others would be greatly appreciative.

Thanks,

Steve