I recently put a custom rom on my wife's D2G. Long story short, she doesn't like it and wants her phone back to stock.
I followed the directions in the thread Reverting To Stock , downloaded all necessary files but I am running into a problem.
When I load the DROID2WE_X6_2.4.29_FULL.sbf file into RSD Lite 4.9 nothing shows in the file properties box and the start button is not highlighted. The phone is detected, as it says in RSD Lite but yet I can't select start.
Any suggestions would be great before my wife kills me.
Thanks
Try following http://droid.koumakan.jp/wiki/SBF — if something goes wrong, tell which step exactly it was.
I can load the SBF in to RSD Lite. I can select start. The phone is detected and in Boot Loader Mode.
The problem i run into is:
1. There is no info displayed when I load the SBF
2. RSD starts but does not finish. The following message is displayed:
Failed flashing process. Fialed flashing process. Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone connected
Let me quote what you apparently have missed on the page I linked.
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Click to expand...
Click to collapse
His problem is more likely a corrupted DL of the SBF file.
RSD lite should not need a connection to the phone to be working to display the SBF info, only the Phone info.
I suggest you re download the SBF file
Problem could be also coming from the location where the sbf file is saved. RSDLite is quite picky on that too. Make sure you save in a directory with short name and no spaces in it - for example C:\temp\ You can rename sbf to something like droidwe.sbf from the original very long name.
You can also avoid the issue of RSD not finding the file by dragging the file into the right pane of RSD lite. Also make sure you have chosen to run as administrator on the properties tab of the swdl.exe.
Related
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!
So about a month ago I rooted my Droid X2 to CM9. Recently, my X2 has been rebooting itself at random times, so I want to sbf back to factory settings. My internet was down for about a week and I couldn't stand my phone rebooting itself anymore. I found a forum thread (on another website) that said you can unroot your phone without a computer (bad decision on my part). After reading numerous posts saying that it worked, I did it. Well here's the kicker, it unrooted itself but I'm still on CM9. Now that I have my internet back in operation, I can now sbf my phone... well that's what I thought. I downloaded RSD Lite and the sbf files for the X2. The problem with this is, now I can't install RSD Lite. When I double click on the file, it asks me to pick a program from a list. I also downloaded and burned 1KDS iso. After restarting my PC and I boot into his script, it asks me if I want to SBF with the possibility to root later, I select that option. I also put my phone into RSD protocol support. After the script starts, it'll either say a file was killed or a bunch of errors will show up. Does anyone have any idea how to fix this?
Any advice would be REALLY appreciated...
I was updating the firmware on my bro's g2x, and it gave me a connection error at 4%.
I started it again, and now here's where I'm at:
the phone starts up in S/W Update (I can get it to boot to recovery, but not 'boot up').
When I run the update utility, it tells me, "problem with comminication between cell phone and pc" before it even starts updating.
I don't know what to do...and I'm supposed to leave town in an hour!!!!!!! Help!
bongostl said:
Any advice would be REALLY appreciated...
I was updating the firmware on my bro's g2x, and it gave me a connection error at 4%.
I started it again, and now here's where I'm at:
the phone starts up in S/W Update (I can get it to boot to recovery, but not 'boot up').
When I run the update utility, it tells me, "problem with comminication between cell phone and pc" before it even starts updating.
I don't know what to do...and I'm supposed to leave town in an hour!!!!!!! Help!
Click to expand...
Click to collapse
Make sure the USB cable isn't bad.
You'll want to do what's suggested in this thread too: http://forum.xda-developers.com/showthread.php?t=1601918
I've attached all the tools that I used to update my baseband, I'm assuming that's what you're doing since you're using the kdz updater.
use nvflash to revert to stock recovery and stock 2.3.4
If you're on windows, do this step as well: go to windows/system32/drivers/etc
there you'll find a file named hosts, open it in notepad and add this line to the bottom (if it's not there already) 127.0.0.1 csmg.lgmobile.com and save
Now extract the attached zip and open the instructions document and follow it.
You should be good.
Note: the attached files are not mine and i take no credit for them, I only have them saved on my HDD in case needed later.
Edit: this is exactly the same as what the above post suggested, sorry for the double reply, I was in the middle of typing my reply when the above one was submitted!
also, make sure your drivers are all installed, both the regular ones and the ones that install when you are in fastboot (adb) mode.
There really is no bricked if it's not a hardware problem, just bjorked. Keep trying options and you'll get it unstuck and going again.
So I was trying to flash the correct factory firmware onto my phone, using this guide. The sparsechunks all failed, but I still continued. Now my phone only halfway has the bootloader working. As I said in the title, it connects to my PC as a device but I can't use the cmd commands that the guide showed anymore. In the bootloader, only half the commands show properly. Power off, Recovery mode, Start and Qcom. I can also look at my phone information (IMEI, serial number, etc.) Any option (excluding info) besides power off makes my screen flash for a second every couple seconds. Also, plugging my phone into a computer instantly turns it on (to the flashing screens). Any help to factory reset my Moto G 2015?
If your Moto G is in the bootloader (fastboot mode) and you plug it in to your PC, can you type fastboot devices and see your device? If so, you should be fine. You need to go through the process that you tried earlier. I'm not sure why your sparse chunks failed because you gave no error message. Did you grab the correct factory images? If you go through it again and get an error message at any point, just stop and ask here... You are leaving too much information out of your post for anybody to really help you. What model of Moto G do you have? XT??? What factory images did you download? Please give the error messages when something fails.
lease give more info:
but if you can acces fastboot modus and you still getting the same error, just boot or flash twrp recovery and flash cyanogenmod
that's the best option
I fixed it with RSDlite and the .xml file, but I'll put more info in case someone else has the problem. I have an Xt1540 and I had the correct newer version images. The error was simply, "Invalid Sparse Image." After continuing and trying a reboot, I couldn't see my device when I checked adb devices. But, some commands would still go through. None of the flashing worked, but erasing did. The bootloader was obviously quite bugged-out, but I could still see the log. That gave me hope that I could still edit my phone's insides! The reboot command failed here, but atleast it didn't go back to the annoying screen flashes. So I figured I would try something besides the CMD which didn't recognize my phone. So I just clicked around on RSDlite and it worked! I suppose it auto found my device, because I didn't do anything but browse for the .XML file and double click it. Thanks for the help!
I'm going to try and encapsulate everything that's going on into this initial thread but I'm sure I'll miss something.
Basically, I undertook to root my phone last night. I followed all the steps in the root thread, and I thought it worked, but then when I went to the root checker to see if I was successful. The test couldn't get a result the first time, and then failed the second time. I've known my phone to be a little temperamental when it comes to stuff like that, so I shrugged it off. Then, everything started running with so much lag that my only option was a reboot. It came back up just fine, but then, apps wouldn't open anymore. Since a reboot fixes everything, I rebooted AGAIN... except no I didn't, because I couldn't move past the white splash screen.
After some time hacking around with TWRP, system restoring my phone and the like, I finally managed to actually load the OS again. I think the phone was rooted at that time, but I don't know for sure, because this was the drawback: I couldn't install ANYTHING. My idea is that the system was rebooted into read-only mode. I tried everything I could think of to revert the system to rewriteable again, but nothing ever panned out. There was just one thing that stood out to me: "Your phone worked properly when it wasn't rooted." So, I got the brilliant idea to use SuperSU to unroot my phone. Stupid, stupid move, because now my phone can't boot past the white splash screen again. As a last ditch effort, I decided that it was time to flash the stock system to the phone. Except I probably did it wrong.
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery system.img
Code:
fastboot flash recovery boot.img
And where I stand now is that my phone will not boot past the white splash screen, and I can no longer access either TWRP or Fastboot.
Is my phone fooked, or can anyone save this?
#1 You can't flash system image via fastboot - it's semi-locked.
#2 You can't use 'flash recovery' command for boot and system images.
#3 For restoring your phone use SP Flash Tool - there's a thread in the General section called 'How to unbrick'.
Try it and let us know.
Cheers
Yeah, I realized afterward that if I were trying to flash the image of the system, I should not have used the "flash recovery" command because I disabled access to the other recoveries, lol. I have tried to use the SP Flash Tool in the past few days, but I could never get any download progress. I think my computer isn't making the VCOM drivers accessible to be able to flash those things to my phone. Do you have any advice on that end? Because I have seen that thread and tried those steps but I'm just not successful.
You should also read all replies to this thread - there are people who solved their problems with SPFT in their own way, that's how I've revived my phone from hardbrick.
Make sure you're phone is disconnected when you start the flash. AFTER you hit the download button in SPFT... then connect your phone...
Fantastic advice from both of you. I'm ready to revive my phone!
Okay, I think I'm making good progress on recovering my phone. I have managed to get back the stock recovery onto my phone, which I then used to install TWRP. But I'm not out of the woods yet. I used fastboot to flash the boot image onto my phone also, but when it came to the system image, I'm having a lot of trouble. The only ROM I can find for the Blu Pure XL is a 7z file. Now, I know how those work, I have 7zip and I extracted it for the system image. When fastboot was available to me, I couldn't push the system image to the phone. Now that I have TWRP and I have no more access to fastboot, I've tried to load the system file onto my phone through my SD card in four different ways:
As a .img file
As a .7z file
As a .zip file that I created by zipping up the image file
As a .zip file that was .7z, but I changed the extension
None of those methods worked. The Blu development thread doesn't point me to a zipped ROM file. One person there said that they had a backup of their files and provided a link, but those images seem to have been removed.
I'm so close, I can see this phone working again in the near future, I just need your help to get me there. Please! :'(
Edit: Also, keep in mind, I'm dumb. I don't think I really did anything super wrong, but I may be missing something ultra obvious. So if you could just keep your answers dumb for me, it would help even more.
I would stop trying to use all of the methods you are using I believe you are slightly confused by them at this time..
At this point what you have done with the random image flashing is get damaged partitions..
Get SPFT. Turn off you phone completely.
Download the full Scatter file for you phone. (put it aside).
Download a file called ALL MTK driver install. ( or something to that effect). Search for it on Google. You will find it. Run it and then reboot your PC completely.. (if you have windows 8 or higher look online on how to install unsigned drivers) --THIS IS THR BIGGEST PROBLEM PEOPLE HAVE--
Extract your full downloaded scatter image to a directory.. (you can download the Gionee E8 image if you want) it is what I am running on my Blu..
Run SPFD read the thread that they pointed out to you. Find the scatter and point SPFD.. Once it is loaded on the program UNCHECK the PRELOADER check box.. (if not you can cause problems) ..
click download and after 10 seconds or so plug in (you completely powered off) phone into the computer..
.Then wait..... and wait... It will tell you it's progress..
Keep trying it, it WILL work.. and ALWAYS unchecked preloaded when flashing with spdf...
I did follow all the steps in the original guide, and I followed the steps that you gave me too, down to using the advanced device manager to remove any MediaTek drivers from the computer and restarting the computer with disabling the driver signature verification, but when I click download, wait, and plug my phone into the computer, just nothing happens. The computer says it's an unrecognized device, and the download never progresses.
I see also that you said keep trying, but every time I try the SPFT, it never sends anything to my phone. And I don't even know how to tell if I'm missing some important step.
OK this happens sometimes. plug the phone in with device manager open.. plug the phone in when it is off..
When it says unrecognized device double click on it really fast( it will disappear fast, try it a couple of times if you don't get it the first time) then hit update driver.. point it to the MTK drivers folder (unzip the MTK drivers folder). It will pick the proper driver. on some computers it loads up so fast it has no time to recognize the driver..
After you load the drivers power off your phone again and follow the instruction I gave.. After you do this once it will load the drivers right after this..
When I double click on the unrecognized device button, it just brings up a notification that my device wasn't recognized because it malfunctioned. I don't have an option to install any drivers.
My problem is finally solved. After starting up SPFT and clicking download, I held Vol - and Power and then connected it, and that pushed the download forward. I got to the Blu animation screen, and it stayed up FOREVER, but then the next time I looked over, it was on the initial setup screen. Good as new.
Thank you guys for all your help. This forum really is an amazing place.