Getting stuck on M Logo and get this when trying to SBF. Google has failed me can't find anything relating to the Droid X2 and this error.
Edit: I updated RSD Lite to 4.8 and updated Moto device manager and now it does not even show up in RSD Lite.
Edit2: What I did was format system before I went to flash CM9 and it errored because nowhere on the OP of that ROM does it say you need to be on 2.3.4 instead of 2.3.5
Your following the instructions in the how to sbf sticky? You have the correct Motorola drivers installed? Your entering rsd mode before attempting to sbf? I'm assuming your following all the instructions but if you could post your exact process that would help.
Enter Fastboot mode via power + volume down then volume up
Connect phone via usb to computer
open RSD Lite
Click [...] select sbf
Decompress and flash
I downloaded these versions...
http://www.droidforums.net/forum/droid-hacks/84923-rsdlite-v4-8-a.html
https://motorola-global-portal.cust...e-can-i-obtain-the-usb-drivers-for-my-device?
Windows 7 x64 Ult
The new install of RSD does not see the Droid X2 it does however the bionic.... I just looked at it and now it finally shows up "battery to low to flash" That might be why it is not showing up...
Will it boot past the moto logo when plugged in to the charger? If it boots past the moto I believe it will charge.... If not see if you can borrow a battery or get an external charger. I have only used the sticky in this section of the forum but have never had a issue sbf'ing. I have always unzipped before sbf bit I doubt that's the problem.
Sent from my SCH-I535 using xda premium
It is actually Power Button and Volume up not down....
With that aside and having to get around a bug with RSD Lite (start button disabled, had to shorten sbf file name) it shows up...
Now I am getting... "Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected"
Not sure if this matters but why not try a newer version of rsd lite as posted in the sbf sticky? The only thing I did was uncompress the zip into a folder the directed the program to the sbf file. I would try using files only from the sticky. What windows version are you using?
Sent from my SCH-I535 using xda premium
Also, quite sure volume down while holding power gets you to rsd.... Your not trying this in fast boot, correct?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sorry, did not see you tried a newer version of rsd..... Try on another pc of possible.
Sent from my SCH-I535 using xda premium
I downloaded RSD Lite 5.7 and it works now. *shrug* It is flashing now.
I really miss my OG Droid. So much simpler and never had any problems.
Thank you very much for your help!
No problem. Hope sbf flash is successful.
Sent from my SCH-I535 using xda premium
Related
So playing around with a modified Atrix rom... I am now locked. Trying to get the phone back up and running using the SBF and RSDLite but having problems getting the software to recognize the phone.
As the phone sits, it now reads at the initial boot.
Code:
Failed to boot 2
Starting RSD mode
I've tried to take it into recovery mode (created a nandroid backup already to the external microSD) without any luck.
I installed the atrix clockwork recovery (I thought I read somewhere that the atrix CWR worked on the X2) FAILED
Mine now reads same as the OP. Im having to redownload the SBF as Im on Vacation away from my PC that has everything on it.. SO, Ill post if I have additional issues
Hi, I am sorry you are having so much trouble. Hopefully I can provide the steps and help to guide you into successfully recovering your phone from this boot error.
From what I understand you're receiving the following error: "failed to boot 2. starting rsd mode"
I have encountered this error a few times while developing MinimalX. Fortunately, you should be able to recover this using the proper method.
First, turn off your device and plug it in. You will need a certain amount of battery life to perform an SBF without error, so, take advantage of these download times to increase your charge using a wall charger.
Next, you will need to download and install DX2 Drivers and RSD Lite.
You will also need the SBF file, which can be downloaded here:
SBF File
(note: be sure to unzip the file)
Once everything has downloaded and installed successfully, unplug your device from the USB. Plug your USB into your computer only. Then, run RSD Lite with administrator permissions. Browse to and select your SBF file (VRZ_MB870_DTN-14.8_1FF_01.sbf). Then turn on your device, and when you get the "starting RSD mode" prompt, plug in the usb cord from computer to phone. RSD Lite should then recognize your phone, and from there, simply, press start and leave the device and your computer alone until completion (not necessary, but extra precaution). Once this finishes and the phone boots, I highly recommend also doing a factory reset in settings > privacy.
I hope you the best and that this is able to restore function toyour phone. If you need any additional help, feel free to PM me or post in this thread.
Happy DROID-ing!
Sent from my DROID X2 using Tapatalk
Ran into this problem yesterday. Had issues with RSD Lite. Make sure you have the latest version or it will fail. Has to be version 5.3.1 and NOT 5.0 or whatever.
then it should work without a hitch.
Just a reminder, you will have your apps and stuff still installed including SuperUser. You will have to run Gingerbreak again to reroot to add the files back into the proper location, SuperUser doesn't work even with the .apk installed by itself. Just fyi.
Follow instructions here and download files from links provided...
http://forum.xda-developers.com/showthread.php?t=1175300
Yeah Don't Try And Flash The Atrix In Rom Manager, It Will Give You That Error Too.
Apparently there's a link floating around pointing to RSDLite 5.0 renamed and hacked to show 5.3.1. While the download says 5.3.1, the install says 5.3.1, it's still only 5.0.
Thanks again to those working to make the X2 a better phone. Perhaps we can get GB up and running on this thing before the OTA is released. Wouldn't that be egg-on-the-face.
So I have been trying a bunch of different roms for the RAZR today and I was having problems with the keyboard not working. I decided to try to load CM9, so I read I need to use "safestrap" and not "bootstrap" that I had been using. I downloaded it, installed then tried to boot into recovery and load CM9.
Now the safestrap boot screen appears and says "safe system disabled" "hit search to continue / hit the menu button to boot into recovery" if I hit the menu button it just reboots, if I hit search the screen just goes blank and I have to do a reset to get it to start the process again.
I have RSD but I have never used it before. I have my phone plugged into my computer but my computer doesnt see it.
Help!
dreamsti said:
So I have been trying a bunch of different roms for the RAZR today and I was having problems with the keyboard not working. I decided to try to load CM9, so I read I need to use "safestrap" and not "bootstrap" that I had been using. I downloaded it, installed then tried to boot into recovery and load CM9.
Now the safestrap boot screen appears and says "safe system disabled" "hit search to continue / hit the menu button to boot into recovery" if I hit the menu button it just reboots, if I hit search the screen just goes blank and I have to do a reset to get it to start the process again.
I have RSD but I have never used it before. I have my phone plugged into my computer but my computer doesnt see it.
Help!
Click to expand...
Click to collapse
Whats your razr. Its verizon? If not you should use bootstrap.
Safestrap is for verizon razr. But some uses bootstrap on it.
You have to put ur razr in ap fastboot mode: power+vol up+vol down in order to flash with rsd lite
Choose a stock rom to your razr and flash it. Make sure flash correct rom
Cheers
Sent from my XT910 using Tapatalk 2
I have the Verizon RAZR.
So my computer does not recognize the phone when in AP Fastboot, but it does recognize it when its in BP SDF flash. What am I doing wrong?
dreamsti said:
I have the Verizon RAZR.
So my computer does not recognize the phone when in AP Fastboot, but it does recognize it when its in BP SDF flash. What am I doing wrong?
Click to expand...
Click to collapse
Uninstall all motorola software, reinstall motocast 1.29 or newer then connect ur razr.
Use rsd lite 5.7 and make sure you got correct sbf file
You may have corrupted drivers.
Cheers
Cheers
Enviado de meu XT910 usando o Tapatalk 2
Do I need to install anything else other than those 2 things? It still doesnt work.
Would having Samsung drivers effect anything? I have a Galaxy Nexus too.
dreamsti said:
Would having Samsung drivers effect anything? I have a Galaxy Nexus too.
Click to expand...
Click to collapse
Sometimes it brokes motorola drivers. Doing what I said should work.
Edit:
BTW what's the version you were and what's the version you're trying to flash?
Some versions cannot downgrade when the one you're trying to flash have a lower security.
I was running Gummy when everything went wrong. Loading safestrap is when I started having the current problems.
I uninstalled the Samsung drivers, and loaded both RSDLite 5.7 and the Moto driver you suggested and RSD will not see my phone in AP Fastboot, but it will when in BP SDF flash. Very confusing.
I will load the latest version of GB when I can get my computer to see my phone in AP Fastboot.
Now my computer is trying to install the flash MZ600 driver and error's out. I googled MZ600 and it says its a Xoom driver???
dreamsti said:
Now my computer is trying to install the flash MZ600 driver and error's out. I googled MZ600 and it says its a Xoom driver???
Click to expand...
Click to collapse
Yup. You've a driver problem, better unistall others devices you may have.
Or, do it in other pc, like a notebook.
So I finally got the drivers working and now RSD see's my phone when in AP Fastboot, but I get an error when flashing the file. This is the error I get.
"Failed flashing process. 22/23 flash "radio.img" -> Phone returned FAIL."
It was flashing for about 5 minutes before I got this error.
Edit: I'm using the file from this thread.
http://rootzwiki.com/topic/13566-droid-razr-fastboot-file/
Blur_Version.6.12.173.XT912.Verizon.en.US
I think the battery went dead, ugh. Ill recharge and report back.
When attempting to SBF to upgrade to Cyanogen 10 A2 something went wrong.
Ive tried several versions of RSD Lite and several SBF Files.
Currently I am using RSD Lite 5.7 with the 2.3.4 SBF File
This is the error message on the phone
Download code Started...
rsd mode...
Partition Tables did not match: Backup PDS and repartion memory...
ERR: hardware/tegra/prebuild/make/../../core/system/rdl/rdl_main .c: 492 StartPartionConfigurion( 25 ): 3
When booting up i get the message Failed to boot 4 -
The phone then automaticlly starts up RSD mode
When holding the volume down or up key while powering on nothing happens... no fast boot and no recovery.
So any advise would be much appreciated. Ive found a few other posts that people have have similar issues but none exactly the same.
Im interested in any advice on which RSD lite version.. which SBF file... and anything else.
Until I get some help my next thing will be to try to SBF using linux.
And obviously Id like some help with repartioning the internal phone memory, it does the same thing whether the phone has the sd card in it or not.
Solved!!!
Apparently the partitions got screwed up so that when rsd tried to write the sbf to the phone it couldnt.
After MUCH time messing with it i discovered if I held volume up while booting even though it would still stay "failed to boot 4" I could get into fastboot mode
using ADB commands in a terminal I flashed a boot.img file that i extracted from an update.zip file i found here http://forum.xda-developers.com/showthread.php?t=1703640
from there it let me get into recovery and then the sbf worked
What version were you running before you tried to SBF?
Pull your battery and leave it out for a few minutes. Put it back in and hold volume up and then hold power. When the screen turns on release power but continue holding volume up until starting rsd appears... still nothing?
Sent from my MB870 using xda premium
---------- Post added at 05:49 PM ---------- Previous post was at 05:31 PM ----------
If you can get that fr try a diff version of RSD Lite.
Sent from my MB870 using xda premium
Also make sure your SBF file is good. I've used these https://sites.google.com/site/motosbf/droid-x2-sbf-files and have never had any problems.
possibly a pad SBF file?
I'm new to this, but I experienced a similar issue this morning.
What ended up fixing the issue for me was downloading a fresh SBF file for 2.3.4. I had a copy of 2.3.4 from when I did the original SBF from 2.3.5 that I figured would work, but something had gone bad with the file. I went here: http://forum.xda-developers.com/showthread.php?t=1317707 and downloaded the 2.3.4 again. That seemed to have fixed me up.
I've also had to run RSD Lite "as administrator" in Win 7 before as well.
I hope this helps
Thanks for the Replies.. I tried another SBF file from the link suggest but it does the same thing.. RSDlite says Phone[0000]-Interface AP-OS: Flashing Code Group 3 but stays on Executed 2% forever and the phone has the same message I originally posted about the Partition Tables not matching...
When I hold The volume up or down while i boot up nothing happens like its supposed to
I was running Cyanogen 10 A1 before this issue.
Does anyone have any idea how to repartition the memory, from the little ive been able to find on it it sounds like ill need to use gparted in linux.. i just havnt tried it yet.
attempted to sbf using linux and the same thing happens
Heres what it shows when i try to sbf from linux
=== VRZ_MB870_4.5.1A-DTN-150-30_1FF_01.sbf ===
00: RDL03 0x00000000-0x002FFFFF 3395 AP
01: RDL01 0x00800000-0x00850457 B203 BP
02: CG05 0x00000000-0x018BBF4F 5EC1 BP
03: CG02 0x00000010-0x0000580F 92DB AP
04: CG03 0x000000A0-0x0008009F 4034 AP
05: CG39 0x00000020-0x0030001F 07B9 AP
06: CG42 0x00000050-0x0030004F 1180 AP
07: CG47 0x00000070-0x0008006F 67FA AP
08: CG56 0x00000100-0x000320FF 1A99 AP
09: CG58 0x00000120-0x0080011F 20DF AP
10: CG59 0x00000130-0x0080012F 1B2D AP
11: CG60 0x00000140-0x1C20013F 9D10 AP
12: CG62 0x00000160-0x0140015F C718 AP
13: CG65 0x00000190-0x12C0018F 6209 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG02: 100.0%
-- OK
>> uploading CG03: 0.0%usb_bulk_read 0
!! unexpected response
-- ACK BIN
RX INX
>> uploading CG03: failed at 000000a0/000800a0
!! failed
>> rebooting
usb_bulk_read 0
Just to check, are you using a Verizon Droid X2? Or a Milestone X2?
Verizon X2
tbodary said:
Verizon X2
Click to expand...
Click to collapse
Ok. Well do you have the right drivers? What kind of computer do you have? 32 bit or 64 bit? And do you have the right motorola drivers for your computer?
Sorry, I'm going back to square one just to make sure you have EVERYTHING.
ive tried it from both my desktop running windows 7 and laptop running windows vista and i booted my laptop into ubuntu and I tried the X2 SBF disk which is basically the same as doing an SBF in linux. All with the same result.
So Im pretty sure that the issue is the memory with the phone since it gives that message saying i need to repartition the phone.
In the linux terminal the phone does show up using the list usb devices and RSD lite does detect it so i think there is still some hope. But its worrisome that I cannot find ANYTHING online about redoing the partitions. But the message its gives me makes it sound like its something thats doable.
tbodary said:
ive tried it from both my desktop running windows 7 and laptop running windows vista and i booted my laptop into ubuntu and I tried the X2 SBF disk which is basically the same as doing an SBF in linux. All with the same result.
So Im pretty sure that the issue is the memory with the phone since it gives that message saying i need to repartition the phone.
In the linux terminal the phone does show up using the list usb devices and RSD lite does detect it so i think there is still some hope. But its worrisome that I cannot find ANYTHING online about redoing the partitions. But the message its gives me makes it sound like its something thats doable.
Click to expand...
Click to collapse
Im no developer or anything. But from what I understand, an SBF is basically just flashing an image to your device. Wether the device is low on memory shouldn't have an effect on it. It should wipe everything and start fresh. Its like taking a blank hard drive and installing Ubuntu on it. Thats how I view it anyways. I know nothing about partitioning the device. Sounds to me like a way to mess up the phone even more unless you know what you are doing. The best thing I can say is just make sure you really do have the right stuff. The right SBF file, the right RSD lite version, the right motorola drivers installed and start again. Maybe try windows XP if you have access to a computer with it on it.
EDIT: Actually I just did it on a Windows 7 computer last week and it worked fine so I dont know.
It shouldn't matter, but try a 2.3.5 sbf?
Sent from my DROID X2 using xda app-developers app
So I discovered if I power on while holding the up button the phone still says failed to boot 4 but then it starts fastboot support.
IN adb using "fastboot device" the phone does show up and I can send commands to it.
i found a post about manually flashing a recovery.img but i cant find one for the x2
anybody have any ideas?
Solved!!!
Apparently the partitions got screwed up so that when rsd tried to write the sbf to the phone it couldnt.
After MUCH time messing with it i discovered if I held volume up while booting even though it would still stay "failed to boot 4" I could get into fastboot mode
using ADB commands in a terminal I flashed a boot.img file that i extracted from an update.zip file i found here http://forum.xda-developers.com/showthread.php?t=1703640
from there it let me get into recovery and then the sbf worked
after flashing 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US i get failed to boot 4
tried http://androidforums.com/4545287-post3.html with no rezult
tried to flash SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US , rds lite 5.6 writes - waiting for re-enumeration,
phone writes - svf : 106:1:2 sec_exeption: b655, eddc, eb
plus nothing hepens when i try to power on phone with vol-, vol+ and both keys
i have already delete rsd and drivers and reinstall them
please help me
you cant flash 2.3.4 on a phone with 2.3.5. it does not work. not sure where to start but can you get to fastboot or rsd mode?
---------- Post added at 07:59 PM ---------- Previous post was at 07:49 PM ----------
also was your bootloader unlocked? any customizations at al re.....recovery or rom etc....can you give a lttle more info.
If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct? If so you are pretty much S.O.L. When you flashed the 2.3.4 sbf it tried to revert your locked bootloader back to 2.3.4 which is a no-no on a locked 2.3.5. Your best bet is to start coming up with a good excuse and take it back to sprint.
Truely need more info. I just a week ago did the same thing to an electrify. I at this time cant tell you the exact steps i took took fix it but it can be fixed. You are not completly screw as of yet and if you look around you will find all you need to fix this but it comes from different sources and some of the info was for different phones but worked on the photon which made it work on the electrify.
Like i said the given info is not enough to give you what you need to do and although the mopho and electrify are similar in almost every way there are a few things that differ.
I dont believe that your "S.O.L." because i just did the same thing and brought it back.
Open a command prompt as administrator and plug your phone into you computer and see if its recognized by fastboot or adb or rsd lite.
hoslayer13 was helping me with this issue and had a lot of info that helped. maybe he will chime in who knows.
More info!!!!!
After the phone says failed to boot 4 if you leave it at that screen for about a minute does it say "starting rsd mode" under failed to boot 4? If so your best bet would be to follow the steps here: (http://forum.xda-developers.com/showthread.php?t=1798145) as long as you originally started with a Photon running 2.3.5. I you can flash via rsd, make sure you remove your sd and sim card. For some reason it seams to work better. Also plug the USB cable directly to the computer (no hubs, no usb extension cables) they can cause issues with rsd. I hope you've already resolved the issue and I'm giving you advice you don't need.
@ rhewins2268. That is exactly the reason I asked "If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct?" If he can boot to rsd then the link I provided is a fix. Which by the looks of it may be what he was trying to do in the first place considering the electrify sbf he mentions is the first step in bringing a Photon back to stock, or back from a soft brick. You are correct more info would be helpful, but by reading what he did it sounds like more than likely he was on 2.3.5 which is an unlock-able bootloader (for the time being) and trying to downgrade (SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US) on a locked 2.3.5 bootloader can and more than likely will perma brick the photon. If when booting he can not see the boot options, i.e. fastboot, android recovery, rsd mode etc. he's bricked. There is no way to flash anything if the device has no, or a corrupted bootloader to start those processes.
OK, So I believe I soft bricked my Droid X2. It started like this, Modem did not power up (3). I connected to RSD protocol, attempted to flash sbf. The process got to 99% and the device failed to switch to BP pass through. My PC attempted to download the driver "QHSUSB_DLOAD", and failed. I am at a loss... Can someone please walk me through a fix?
Often a failed switch to bp, is a drivers error
After you get that error, leave phone connected, and check windows device manager for errors
If no errors try my img files using moto-fastboot.exe method in my list
sd_shadow's [Collection] of Links for Droid X2
Sent from my XT862 using Tapatalk
Thanks sd_shadow. I was looking for these exact files too!