Can't get RSD lite to work - keeps failing!! - RAZR HD Q&A, Help & Troubleshooting

I bought a used razr hd today and am trying to flash the 4.1.2 file. Reason being as when I power on the phone it goes right to fastboot mode.
I have the most current RSD lite and correct 4.1.2 files. I've removed the getjar lines and when I try to use rsdlite the second I press the start button I get a FAIL. It says phone won't go into fastboot mode.
Any suggestions on why it's not working??
If anyone can PM me or post what else to do, I'd appreciate it.
Thanks!

Related

[Q] Bricked in RSD Mode 2 and PC cannot detect XOOM - help

My XOOM is bricked and show RSD Mode 2 when power on, I can go into the fastboot mode by press VOL UP + Power button, and plan to do fastboot process to restore the system.
However, my problem is the Computer cannot detect XOOM, when I input "fastboot oem unlock", then the command stopped at a "Waiting for device" reply, so I cannot go to next step.
I have installed all of the needed software I see in this forum. Moto USB driver, Android SDK, Java, fastboot.
I have tried the RSDlite 5.0 but with the same reason, the RSDlite cannot detect device so it cannot work out.
anyone with the same problem and how to solve it? Do I need to send back it to Motorola for restore?
Thanks a lot for your help, It is too bad to stay with a bricked XOOM.
Xoom stuck in RSD mode 2
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Unbrick RSD Mode 2
I don't know what version xoom you are using, or under what circumstances you bricked your xoom under, but I managed to get mine (3g, USA) out of RSD 2 this way after it wouldn't boot coming out of a botched automated unroot/relock procedure. You may want to try this to get back to stock and working again, and then redo all the rooting and tweaks. I am going to go on the notion that you use windows (I use windows 7 64bit, but the steps should be the same or similar for other versions), have android sdk installed, and know what fastboot is.
... but first a few disclaimers!
1) If everything is fine now, disregard this reply!
2) I am in no way an expert in unbricking xooms, this is just how I figured it out for my situation.
3) Again, this is how I unbricked MY xoom, it may or may not work for you. If something here doesn't work for you, I really can't help.
4) I am not as big of a douche bag as I sound like in the last couple of disclaimers. If you are stuck and there is something I forgot to mention, I'll try to help.
4) You are probably having the same problem as someone else. As much as I hate to say it... GOOGLE IT! Just make sure you have all the error codes and include how you bricked your device. Horrible example: " R2D2 mode after I tried to turn my xoom into an autonomous killing machine by feeding my device crepes error code xx42" Bad example, yet it's very (odd) specific.
5) Don't be offended if I go into details that seem way below you. Someone else may need to read this, and may not understand everything you or I do. I try to break everything down as much as I can. Also, if I didn't go far enough into detail, let me know.
6) I inserted two 4's to see if you are really taking the time to read the entire post so the first 4 may not be true!
7) Once you get fastboot working, and the bootloader unlocked, the brick may be undone. I have you get the stock images just in case. Following the last part of the post will wipe your data.
Now back to our regularly scheduled programming...
1) Download the correct stock system software (wifi/3g) from motodev.
motorola.com/products/software/?utm_campaign=xoomsoftware&utm_medium=motorolacom&utm_source=supportforums&utm_term=unlockboard&pubid=987654
You have to register on the site. I would attach the files, but I agreed to a nice end user agreement saying I will not redistribute them. Also, I can't post links yet since I am still new so the beginning of the url is missing. There are posts in the xoom development forum that link to the file.
2) Unzip the contents to the folder where fastboot is located. Usually located in C:/program files/android/android-sdk/tools, or C:/program files (x86)/android/android-sdk/tools if you use a 64bit version of windows.
3) Power on the xoom and get into fastboot by holding the volume down button as soon the moto logo shows. I noticed it took a little while longer than usual for fastboot to show up. I noticed in the original post that the user said Volume up + Power. That is how you hard reboot... or do a dragon punch...I forget.
4) Once the device shows fastboot is running, Open a command prompt ( start, all programs, accessories, command prompt, or type cmd in the search bar ). Next type/copy these commands minus any comments marked by "<---". Note that every new line is a new command:
ON THE PC:
cd c:/program files/android/android-sdk/tools <---May be different depending upon what version of windows you are using. Replace 'programs files' with 'program files (x64)' if using 64 bit windows. If all else fails, type cd then copy one of the paths from step 2.
fastboot oem unlock <---This MAY solve your problem right here
should say check your device for instruction. On the xoom, hit volume down, then volume up, voulme down again, and volume up again to confirm the unlock.
When I did that my xoom rebooted, and I was back in business; however, if the unlock worked and you are still not able to boot, let's get back to stock. Get the xoom back into fastboot again by holding the volume down button while it starts.
ON THE PC:
You should still be in the same command prompt from earlier.
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will wipe your xoom completely, but your nice shiny paperweight should be less paperweight like. I do the relock for good measure just because I think I left it unlocked, then I received an OTA update, and got good RSD Mode 2 again for some reason. If you want, try it without the fastboot oem lock command in case you want to get right back into rooting, flashing recoveries, etc... Well, hope all this helped. Again if clarification is needed, let me know and I will try to help. Hope this works. Take it easy!
zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
I have the same issue. Looks like I now own a brick!
zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
1) Turn the xoom on and leave it plugged into USB.
2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\
*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked
it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
This doesn't work!
i have two motorola xoom, one of them have the failed image sos 0x0002 starting rs mode 2.
When i plug in the bricked motorola xoom nothing respons in the computer. i have the fastboot on with the waiting for device activated with fastboot oem unlock and RSD Lite v4.9 or 5.0 doesn't detect it too..
What can we do? i'm from spain and i bought the tablet in new york. Can i send it to the garanty?
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
csseale said:
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
Click to expand...
Click to collapse
i believe there is no SBF file for wifi xoom right now.
So I haven't had a chance to try anything you all have said since I've been at work all night. I have to agree with the last post though. I have looked everywhere and cannot find the.sbf I hope it leaks soon though so I dont have to deal with the shame of sending it to moto.
I still can't get the xoom to receive commands. I need that .sbf. I'll definitely be checking every minute for the wifi version leak.
The above means does not work.
I end up with a RSD re-enumaration failed error.
I'm on wifi xoom and can make it into "Starting Fastboot protocol support" but when i attempt to flash any of the images posted above or do a fastboot oem unlock I simply get <waiting for device> and nothing responds. Help?
Your Xoom is completely Bricked
At this point there is nothing you can do. You can A. wait patiently for .SBF for wifi only xoom or B. explain to motorola what happened and if it is under warranty they will replace or repair your xoom in 1 week.
Mayday
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
BlueEditionE6 said:
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
Click to expand...
Click to collapse
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
rockhumper said:
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
Click to expand...
Click to collapse
As long as you didn't reformat your internal sdcard you're probably not really bricked. It's not impossible but is really hard to brick the Xoom. I would suggest you go to the IRC #[email protected] freenode and see if any of those guys can help you. If anyone can, they can.
Good luck!

[Q] How to Unbrick A XOOM? Hellllppppp!!!

J decided yesterday to run the update and all was working spectacularly. I had everything I needed and all my apps came back. However, I was feeling good about myself and decided that I wanted to do the overclocking as well. So I flashed that part of the update, the XOOM rebooted (partially) - it never left the big red M screen. I have tried to SBF (which isn't working - the process fails before it even starts). I can get to fastboot, but once there, there isn't anything that I can do to bring the XOOM back to life. It looks like I'll be paying Verizon a visit unless some supergenius dev has a 're-animation' method that I have not yet considered. I'm currently going through very painful withdrawal symptoms and would really appeciate the help of anyone else who has been through this.
Many many thanks in advance.
If all you did was flash a new kernel, then you should be able to flash the stock kernel from fastboot and that should get you fixed. If you're still on 3.0, then you can get the stock images from Motorola (I don't have the link handy). If you're on 3.1 then I'm sure someone can get you a copy of the stock boot image.
myersn024 said:
If all you did was flash a new kernel, then you should be able to flash the stock kernel from fastboot and that should get you fixed. If you're still on 3.0, then you can get the stock images from Motorola (I don't have the link handy). If you're on 3.1 then I'm sure someone can get you a copy of the stock boot image.
Click to expand...
Click to collapse
At the time this all happened, I had just successfully upgraded to 3.1. However, when I tried to use RSD Lite 4.9 and the HR139 image to perform the normal SBF procedure, it kept failing out with a message referring to the fact that it cannot find some type of initialization in the INI file. I'm totally lost and feeling somewhat depressed and stupid.
If you can get to Red M you should be able to get into get into bootloader by powering on by holding power and volume down. Then as long as adb recognizes device follow this.
http://www.xoomforums.com/forum/mot...s/2788-how-restore-3g-4g-system-boot-img.html
It just pushes stock images with adb and not rsd
Edit; in your case hold power + volume up to reboot device, then immediately hold volume down until Rsd protocol words come up then hook xoom to computer. Don't follow first step in guide because you are already in bootloader.
GulMiguel said:
At the time this all happened, I had just successfully upgraded to 3.1. However, when I tried to use RSD Lite 4.9 and the HR139 image to perform the normal SBF procedure, it kept failing out with a message referring to the fact that it cannot find some type of initialization in the INI file. I'm totally lost and feeling somewhat depressed and stupid.
Click to expand...
Click to collapse
As far as I know, there are no overclock kernels that work with 3.1, which is why you had the trouble you had. You'll either have to flash back to completely stock 3.0 or you'll need the boot img out of the 3.1 update.
Help
I tried overclocking my xoom with this link h t t p://w w w.dkszone.net/overclock-motorola-xoom-1.5ghz-detailed-guide[/url]. I did step 3 and it got stuck in "starting RSD mode 3". adb wont recognize my device. Please help.

[Q] Droid 2 Global stuck on bootloader

i have a rooted droid 2 global and when i tried to flash the 2.3 gingerbread it rebooted and came back to the bootloader and now thats what im stuck on, please help?!
I feel so bad for you, because I did the same freakin thing. I tried to figure things out forever, but luckily, I believe I can help you. What you need to do is, if you have not already, get the motor drivers for your phone. Google moto helper. After that Google the program rsd lite 4.9 and download it. Open it up and plug your phone in, and make sure rsd lite recognizes your phone. If not then you need to redownload the drivers. Next go on line and look up Droid 2 global sbf file. You should end up at team black hats website. The file you download should be called droid2we_x6_2.4.29.full.sbf. open up my computer, click on the c drive, click on program files, click on Motorola, right click on rsd lite and run as administrator.put your sbf file on the desktop. On rsd lite click on the elipse, and find the sbf file. Click start, and hopefully rsd lite will begin flashing your phone. Once it reaches 100%your phone should reboot and start up. If not, and this is once rsd lite is 100% done, pull the battery and wait 5 seconds. Hold in the power button and the x button. You should eventually see an android with an exclamation mark. Press the spy glass button and a menu should come up go down to ease data/factory reset with the volume buttons and enter with the camera button. Then wipe cache and reboot. With luck your phone should work again
l
Did this get resolved? I have the same issue. It just won't work with any SBF.
Mine is doing the same now.

[Q] bricked my phone? help

so guys i have an atrix 4g that i had originally installed a rom to that was all working fine until i did some kind of an update that messed up the phone completely. now my phone won't boot past the screen that says
"failed to boot 2"
starting rsd mode
however once on that screen i can't access any of the menus and the phone never
starts rsd mode. I've tried all the manual boots into recovery and fastboot and not luck. so if you guys know how to work around this or fix it plz let me know
i've looked at some guides like the moto-fastboot method to fix your phone
however all of these require you to be in the rsd mode which i can't access!!
OMG!! guys im sorry for the useless thread now but i found the guide using rsd lite flashed sbf and fixed everything im so happy now

Motorola Razr HD LTE XT925 4.1.2 boot loop

I'm stumped with this issue of my Motorola Razr HD LTE XT925 Rogers version 4.1.2 being in a boot loop. It started when I did a factory reset to try and fix some camera issues that I was having it started up with the Motorola red M icon then went to proceed with the factory reset with the android icon with the spinning blue object then restarts and just does a loop I have tried some steps that I found that I will list but all are unsuccessful and I did try them several times. It is stock firmware but was rooted with one click rooting program can't remember the name I did nothing else to the firmware.
Power + volume down for 10 seconds (simulates a battery pull)
Stock recovery tried wiping data and cache and then rebooting
Tried to use the boot menu normal start up and factory options
I did however get it to boot to the Rogers logo screen once but it just froze and had to restart it
I am currently trying get ADB tool to installed and get it working to see my phone as well as RDS Lite 6.1.6 it wont show any info about the phone but when in fastboot mode RDS Lite see it as connected in fastboot but no info about the phone shows up in the top left box as it has shown before also tried Super ADB Tool it show nothing at all I will continue to try and get the tools working.
Any help in getting the phone to boot normally is greatly appreciated.
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
OK so I have ADB installed and working I think put my XT925 in fast boot mode then I put in code adb devices in to the windows command console but show nothing listed and my phone says it is in fastboot mode and usb is connected and windows sees it as well but not ADB. There is no errors ether I am so confused as to why ADB and RSD show no info about my phone? I will see if its any of my drivers that are missing.
I went ahead and tried to flash my phone with RSD lite 6.1.6 with no luck the boot loop is preventing it from proceeding with the flash is this just a lost cause and there is no fix for it. The only thing I can think of is that I have to unlock the boot loader is that even an option when I can't even get boot into android? Any one got any ideas?
I was messing a round with my phone and try to get it working with any of the tools and had turned of the phone to stop it from constantly showing the red M icon and the android icon with the blue spinning object over and over but still had the phone plugged in to the computer and was looking in device manger in windows and seen this QHUSB_DLOAD with no drivers for it and looked at the VID & PID ids (USB\VID_05C6&PID_9008
) and searched for drivers thinking that is what is missing for my phone as I have never see it before and it is Qualcomm modem flashing port I don't know what to do did really mess up my phone by just doing a factory restore?
Some help or clarification would help a lot now as it is a bit troubling that I am unable to fix the Motorola Razr XT925 and might be bricked just by doing a factory restore. :silly:
OK I am getting desperate here I will do anything to stop it from looping I have even tried house of motos way just the same thing still if I can stop it from looping I can get it to work but does anyone knows a way to wipe the phone completely or stop it from this infuriating loop???
Just as a side note I found that forcing it in to normal start up with the wall charger plugged in it will charge when done then it will show the rogers logo like its booting but does nothing.
I have searched the forms and google now for 2 days about any way to fix the boot loop but all just say to do things that I have tried many different ways many times and the tools don't work or will work like RDS but it is unable to continue do to the loop of it doing a factory restore then restarts.
If any body has any ideas at all or can at least point me in the right direction would be a life saver I will even jtag the phone if i have to, if even that's possible
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Darbness said:
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Click to expand...
Click to collapse
Thanks for the reply, I have gone into fastboot mode and used RSD to try and flash the stock rom but when it restarts the phone its unable to countiue becuse it is uable to get past the bootloop
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
OK, not able to take it to Rogers some issues with doing that but will try RSD lite 6.1.4 besides that no other ways?
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
xaneth said:
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
Click to expand...
Click to collapse
Thanks for the reply, I was thinking along the same lines as that but trying it on a freshly installed windows plus on different computer and just have RSD lite 6.0 and my Motorola drivers for my phone installed. I was thinking that it was my current motherboard that has a Intel usb 3.0 controller on it and my old motherboard did not as I manually updated my phone from 4.0.4 to 4.1.2 before on my old motherboard and had no issues and will fallow the instructions to the letter and will triple check as well. I will see how this goes and hope it works as its my last option to get it working.
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
osalot said:
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
Click to expand...
Click to collapse
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Hydr0id said:
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, The steps I take to flash my phone is to first put my phone in to fast boot mode then connect my phone to the back of my pc then start up RSD Lite and add the latest firmware for my XT925 in RSD then let it load the firmware and it restarts the phone. it starts up to the non animated red M icon then the android with the spinning blue object in its chest comes up but then shuts off and restarts and have left it for several hours until it died and had to recharge it up.If I can I will post a video of how I flash it and what the phone does.
also is it normal for RSD Lite not to show the imei number of the phone or any thing about it in the top left box (Device properties) when you click on the modal?, all I get is N/A in Device properties box.
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
thanks for the reply, I have just tried the the steps in the link you provided and I used RSD lite 6.1.4 and got the 4.0.4 Rogers firmware for my XT925 that it originally came with and waited an hour but just did the same thing, I don't get any errors when flashing although RSD displays to start the phone up manually and I have a locked boot loader (Device is LOCKED: Status Code: 0) I can how ever get it to go to the animated red M icon and then the rogers logo by selecting normal power up from the boot menu but doesn't boot in to android.
osalot said:
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
Click to expand...
Click to collapse
http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/
Ok, so I think I maybe doing something incorrectly so I will put all the steps I did to reflash my phone and will add some pics and a video if possible.It took me a few days to get another phone to use for vids and pics the phone I used to for video and pics Samsung Captivate, unbrickable ya can't kill it.
1. I have installed RSD Lite 6.1.4
2. Installed the latest Motorola drivers by down loading the Motorola Device Manager
3. Down loaded the firmware for my phone android 4.1.2 full file name ---> 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
4. Put my phone in fast boot mode then connected my phone to my netbook on the side or on the back usb 2.0 port on the PC with the original Motorola usb phone cable tried both to be sure
5. Started up RSD Lite 6.1.4 and load the firmware and selected Decompress only
6. Checked RSD Lite to make sure my phone is connected and showing up and RSD Lite shows (Fastboot VQUISH_U S USB N/A Connected)
7. I then selected start button on RSD Lite and it flashed the firmware with out issues or errors
8. phone restarts fine from fastboot left it for 1:30 RSD displays to reboot the phone manually but the phone does not do anything else but reboot constantly left the phone doing that until it ran out of battery
Pic of XT925 in fastboot mode not connected
Pic of RSD with phone connected in fastboot mode ready to be flashed
Video of phone restarting after being flashed and looping (click the link below)
http://s1295.photobucket.com/user/Osalot-Ruin/media/RSDandphonevideoCapture_zpsff85211b.mp4.html
Pic of RSD after leaving the phone for 1 hour and 30 minutes
In the steps I don't see the XML file editing, did you deleted the getvar line in the XML file?
Sent from my RAZR HD using XDA Free mobile app

Categories

Resources