Related
Ok, so after scanning through the SBF thread and a few others and finding instructions all over the place, I decided to bring them all together in one post. Sorry if I don’t mention everybody that contributed these instructions by name but there were a lot of instructions on how to flash the SBF to our phone. You know who you are and I personally thank you and believe everybody else does also.
To begin, download the necessary files and drivers:
Froyo 2.2.2 SBF File
Gingerbread 2.3.3 SBF File
Gingerbread 2.3.4 SBF File
RSD Lite 5.3.1 and Drivers
RSD Lite 5.4.4
1. Reboot your computer and your phone after downloading and installing everything and before you go to flash the SBF file. Use 7-zip to extract the SBF file...
2. Once you have rebooted your computer, go ahead and start RSD Lite and point it at the SBF file and plug your USB cable into your computer ONLY!
3. Turn your phone off.
4. Turn the phone on by pressing and holding the POWER AND VOLUME DOWN buttons until you see FASTBOOT. Press volume down until you reach RSD and press volume up once.
5. Plug your phone into your computer and wait until you see it in RSD Lite and click Start.
6. Your phone will reboot when the process is complete. DO NOT UNPLUG YOUR PHONE FROM UNTIL THE COMPUTER UNTIL THE PROCESS IS COMPLETE.
7. If the phone boot loops pull the battery and boot into the stock recovery by pressing and holding power and volume down until the phone says FASTBOOT, once the phone says FASTBOOT, press volume down until you see ANDROID RECOVERY, once you see ANDROID RECOVERY, press BOTH the volume up and the volume down buttons. You will see the familiar triangle with the exclamation point and the Android. At this point press volume up and down simultaneously again and select “wipe data/factory data reset” by pressing the power button.
8. Reboot your phone and you should be back to full factory default, like new out of the box.
If you have any other problem with RSD Lite, try running it as administrator in Win 7/Vista...
Thank you, very helpful and thanks to everyone involved. Let's get this ball Rollin baby!
Sent from my DROID X2 with that v6 son using XDA Premium App with
You first link does not work properly. I found a working link in the SBF thread and wanted to confirm that it's 482mb?
Don't actually remember... But I believe so.. I will update the link sortly thanks tho...
EDIT: Yes it is 482MB Link has also been updated...
Sent from my DROID X2 using Tapatalk
Thanks for putting every thing together and thanks to everyone who contributed. This should make it easy for everyone to understand.
Sent from my DROID X2 using XDA Premium App
Added to the roll up sticky, thanks.
Mr. Clown said:
Added to the roll up sticky, thanks.
Click to expand...
Click to collapse
Thank You! Mr. Clown!!! I have been trolling xda since my A&TT Tilt and have become very involved with this phone and am glad to actually help and contribute!!
any guide as to how to unpack the .sbf and reveal its contents
slowz3r said:
any guide as to how to unpack the .sbf and reveal its contents
Click to expand...
Click to collapse
That is actually a great question Slowz3r.... I would love to know how to open that SBF, but I really have no clue... I will try and see if maybe I can open it in Linux. If anybody around here has any ideas or has already tried this, please let me know...
TIA
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Anyone else notice that to the right under platform it says 4G Tegra? Some also stated that their computer detected a 4G Modem when the phone was in a certain mode.
uhh186 said:
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Click to expand...
Click to collapse
Believe it or not I, of all people(the person writing the tutorial), had the same issue last night.... I just reinstalled like you said and all worked fine....
zakth said:
Anyone else notice that to the right under platform it says 4G Tegra? Some also stated that their computer detected a 4G Modem when the phone was in a certain mode.
Click to expand...
Click to collapse
Yes, I have also seen this in the options before you get to rsd mode... Don't know what that means or why its labelled that way but it is definitely interesting... It would be great to find out what motorola might have to say about this and if that may be why we have been waiting so long for an update!!! I highly doubt it tho, but still nice to think about...
uhh186 said:
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Click to expand...
Click to collapse
This happened to me also, i found out after two hours of forum searching, that you need 5.3 rsd lite, the one in the download worked for me, but maybe its your operating system, i had to use my xp computer because it would not work on my Win. 7 machine. Hope this helps.
gageoliver said:
This happened to me also, i found out after two hours of forum searching, that you need 5.3 rsd lite, the one in the download worked for me, but maybe its your operating system, i had to use my xp computer because it would not work on my Win. 7 machine. Hope this helps.
Click to expand...
Click to collapse
It should work with Win 7 as that is what I am running... The link I have posted for rsd lite is 5.3... Maybe if you run rsd lite as admin??? I didn't have to but that might be a solution....
It Works!!
This is the first Sbf download that worked for me, i noticed that this one was over 700 mb in size. All the other ones were 482 mb. I guess those were just the partial Sbf. Thanks for this, i really needed it!
I had to do a factory reset of my phone the other day. I used RSD5.3.1 and the 482 mb SBF.
I bootlooped initially on the reboot but after doing a battery pull and then going into recovery, everything worked. I did get a couple settings wrong on setting up the phone but fortunately, there is a Verizon store very close by.
All the bloatware that TB had backed up up prior to me uninstalling came back. After the reload, I re-rooted but haven't uninstalled or frozen anything yet.
gageoliver said:
This is the first Sbf download that worked for me, i noticed that this one was over 700 mb in size. All the other ones were 482 mb. I guess those were just the partial Sbf. Thanks for this, i really needed it!
Click to expand...
Click to collapse
Actually the sbf included here is also 482 mb... Maybe the other downloads got corrupted?? However, I'm just glad it worked for you!
DAG425 said:
Actually the sbf included here is also 482 mb... Maybe the other downloads got corrupted?? However, I'm just glad it worked for you!
Click to expand...
Click to collapse
New Links I Just Uploaded Yesterday.
http://www.droidforums.net/forum/droid-x2-hacks/156070-sbf-file-rsd-lite-drivers-instructions.html
ok, just sbf'd my phone... hooked up rebooted blah blah blah... now im ****ting my pants... rsd says Results Fail and in the status says Disconnected.... idk why... all i know is that it was up for like the first phase... rebooted and says switchin ti BP mode... did that... then rebooted at 99% and then this.....
Phone is stuck on Moto Dual Core screen... and doing nothing... some please tell me i didnt mess this up.
Edit: Ok, i rebooted did the recovery thing and data wiped, got it working and now configuring the phone.. sorry for this post, was jus scared i guess >.<
Hi,
With ATT 4.5.91 rooted unlocked phone upgrading to 4.5.141, the process failed after RSD lite 99% completed, the atrix stoped there with the message as follows:
"fail to boot 1 PwrReason: PWR_KEY_PRESS
Starting fastboot protocol support", and I re-fastbooted and
found out "recovery error 0x180004" and "OEM unlock is not implemented".
Please help. Thanks a lot.
If you still have full battery life you will need to flash 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011-unlocked.sbf. I'm guessing you flashed 1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf....I had this exact issue just yesterday. But you have to have a full life battery or at least enough to fully flash otherwise you're in serious trouble after that. By the way, what method were you using to upgrade to .141? It's not recommended on an unlocked bootloader though I tried it over Moto software update and it worked fine (only tried this cus the OTA update screwed up my wifi and bluetooth). Hope the info helps, good luck!
weisey9 said:
If you still have full battery life you will need to flash 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011-unlocked.sbf. I'm guessing you flashed 1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf....I had this exact issue just yesterday. But you have to have a full life battery or at least enough to fully flash otherwise you're in serious trouble after that. By the way, what method were you using to upgrade to .141? It's not recommended on an unlocked bootloader though I tried it over Moto software update and it worked fine (only tried this cus the OTA update screwed up my wifi and bluetooth). Hope the info helps, good luck!
Click to expand...
Click to collapse
WEISEY9 thanks, I failed the OTA to 2.3.4-4.5.141, so I used manual update using sd card to update.
Sorry I can't find out the unlocked.sbf you mentioned above. Can you inform where I can download it. Thanks again.
This happened to me before, just open rds lite, connect ur phone yo ur PC, if is not!! It might be detected like fast mode on rsd lite on ur PC!! Pull out the battery, till fastmode(status) disappears from rsd lite! ( u can try power button + volume up key I don't remember how I get it) then just use pudding (the small file, ) ..
Sent from my MB860 using XDA App
fail to boot 1 updating to ATT 2.3.6 4.5.141
narezese said:
This happened to me before, just open rds lite, connect ur phone yo ur PC, if is not!! It might be detected like fast mode on rsd lite on ur PC!! Pull out the battery, till fastmode(status) disappears from rsd lite! ( u can try power button + volume up key I don't remember how I get it) then just use pudding (the small file, ) ..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes that is the reason I request for help to get pudding or UNLOCKED.sbf to flash back to ATT 2.3.4 4.5.91.. As in China I can't access to those websites that provides said file as below (don't know what is the reason).
"1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011-unlocked.sbf."
Please help if you can acess the file please send to my email below
"[email protected]" Thanks.
The file size is big
So, I followed everything the briefmobile guide that was linked to from the greyblur xda page.
It said it installed, so I rebooted my Atrix and never made it past the "Dual Core Technology" boot screen.
I went into fastboot, then recovery mode (android guy by the triangle with the "!" in it). I reset the phone. Didn't work.
It was running 2.3.4.
I've read something about romracer, but I don't know what that is, where to download it, or how to use it. Please explain in depth if it is relevant.
Please help me. I just got this phone (my first smartphone) today and was really excited to start messing around with Android. I'm probably going to be too nervous to do anything for a while after this. I just want the stock os back. Anything that could get my phone back to where it was is GREATLY appreciated.
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Greyblur is only for froyo ROMS. That's why you have a nonbooting phone.
Sent from my MB860 using xda premium
Dark9781 said:
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Click to expand...
Click to collapse
Thank you! So do I just drop this onto my SD card then?
Njl6705 said:
Thank you! So do I just drop this onto my SD card then?
Click to expand...
Click to collapse
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Dark9781 said:
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Click to expand...
Click to collapse
Ok. I ran it, it said it was successful, I restarted it, and now I have:
Failed to boot 4
Starting RSD Mode
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
...first day of owning this phone... I think I'm done with this stuff after this. >.<
If you are trying to install ROMS you need to unlock the bootloader first... Check out the Noobs Guide in the general section.
Dark9781 said:
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
Click to expand...
Click to collapse
You're sure that if I flash this it won't get bricked further? SBF is firmware, right? I meant my phone was running OS 2.3.4.
I can't get get into rsd or fastboot now. All it says is
Failed to boot 4
Starting RSD mode.
I plugged that into my computer, it recognized my Atrix as SE Flash Olympus, instead of NS flash olympus, so I tried to flash it anyways and it failed.
Please guys. I'm getting desperate here. Please tell me I don't have a $250 paper weight.
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
sheeparecurious said:
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
Click to expand...
Click to collapse
2.3.4, what my phone was originally running.
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
sheeparecurious said:
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
Click to expand...
Click to collapse
Ok. So I'll try flashing it a couple more times. My battery should have a decent charge still, so that shouldn't be a problem.
Thanks.
I really need to just calm down and stop loosing my head over this.
UPDATE: When the flash fails, the phone's screen reads:
Failed to Boot 4
Starting RSD Mode
sec_exception: febe, 35, 35
RSD Lite also says
Flashing failed process. Phone did not re-ennumerate after RAM downloader was sent (0x703e).
What does this mean?
Hmm. I'll admit I don't know what that means, so all I can do is help you troubleshoot.
I did some searching, and another user hit this problem when using a USB port on the front of his PC (which is not powered as strongly as one on the back). Did I mention RSD Lite is a finicky beast?
If you're on a desktop machine, try switching to a USB port at the back. If you're on a laptop, try a different port. I'll keep looking for anyone with a similar problem.
EDIT: One last question. You extracted the file before flashing, right? The extension is .sbf, not sbf.gz?
Hmmm... Yeah, I guess all I can do is keep looking.
My battery is now too low to flash, and I don't have a friend who has an Atrix.
I might just sent this into mobiletechvideo's debricking service. This is my first android phone and I'd rather not mess it up anymore.
Yes, it's an SBF file.
Fair enough. Sorry this wound up being a pain. I know full well that sick feeling when you think something's messed up, but your phone is still only in a "soft brick" at this stage and can be recovered.
Keep in mind these things really can be modded safely, but you have to do a LOT of reading at the outset, and stick with roms made very recently. (Last August? ancient history.) It's an interesting technology intersection; these things are proper computers which should be readily customizable, but they're also phones which tend to be locked down by the manufacturer/carrier. By analogy, I can wipe my computer's hard drive and install XP if I want, even though I'm currently on W7. But if I try to install an earlier Android version on my phone, it bricks.
anyway, good luck with getting your phone up and running again.
Thanks. I actually did a decent amount of reading before I got this phone, but it seems I'm more of a kinesthetic kind of learner. I probably should have gotten an older, cheaper phone to play around with before I went all out and got an Atrix.
It really is an interesting intersection. It's too bad the manufactures feel the need to put any restrictions on.
I guess I'll just read some more n00b guides and try again when I have a little more confidence. $50 doesn't seem so bad to get the phone debricked compared to the $250 I payed for it. I don't really have a choice either, since the only means of charging it is thirty miles away at the nearest AT&T store.
Anyways, thanks for helping me troubleshoot. Hit me up if you have any problems. I'd be happy to dig around in the forums and see if I can find anything.
You could have avoided all these problems if you had read the entire thread about greyblur, because it specifically states that it is only for froyo phones. But, as many say, you live and you learn, then you aren't a noob anymore.
Also, if you have warranty on your phone, you can send it in and Motorola should fix it for you from what I've heard.
Sent from my Xoom using XDA Premium HD app
Before some of you gets upset with me posting the same kind of question, please know that I looked at the forum everywhere plus some other forums and tried almost everything. Here's the summary.
I recently got Droid Razr Asia version and I upgraded to EU Retail rom n rooted it.
There was one problem that I noticed that only bluetooth was not working.
Checked online, and found out that it's the radio mismatch b/w EU and Asia version.
So I downloaded RAZRX rom and was trying to flash it again with bootstrap.
So the process started and in 10 seconds it failed.
So I tried to search other forums ...
at some place i found that ... after Hard Resetting, clearing catche; I am also supposed to format the system.
So I followed the whole procedure, and turns out that again it does not get FLASHED. So I downloaded the ASIA version again and tried to format. It did not work. I tried with EU version, it did not work.
So after getting tired, I tried with RSDLite to flash through PC.
That's when I found out that ...
It detects the phone ... but the phone has no EMEI, software version or any other details. Everything is n/a.
Still I tried, and it said "fastboot installation failed" or somethin like that.
And now my phone is stuck on red motorola logo.
I tried to power off and go to bootloader fastboot ...
and it says "Fastboot Locked ... Press power button to power down."
I tried with the DroidRazrUtility1.4 also ...
But it does not detect the phone.
I tried other few things I found online. But nothing worked.
I also drained the battery by keeping it aside to see if the fastboot gets unlocked, but it didn't work.
However, I haven't removed the battery yet. Cause I do not have the tools.
Please can somebody tell me step by step approach how to do this?
Because I haven't found out where I am going wrong in the given methods. and btw, I have followed everything exactly step by step.
Really appreciate any kind of help.
Thank you very much.
Try to flash with RSD Alternative
http://forum.xda-developers.com/showthread.php?t=1453660
Thanks a ton.
But will it still work if my AP FATBOOT mode says that "Device is Locked"
And the battery is on low?
samthehell said:
Thanks a ton.
But will it still work if my AP FATBOOT mode says that "Device is Locked"
And the battery is on low?
Click to expand...
Click to collapse
Probably not. I read on one of the forums there might be a way around the battery being low. I think it was here in xda. Do a search for fast boot install or battery, something like that. If you find that doesn't work you would have to make the tbh cable which allows power to the phone without a battery, or in your case a near dead battery.
Sent from my Droid Razr using Tapatalk
"Device is locked" is natural, (almost) all of our bootloaders are locked. Nothing to do with flashing official ROMs.
You'll need to make a factory cable if the battery is low, search the development forum for a guide.
Sent from my XT910 using xda premium
Thank you all ... Just ordered the cable. Hope it works.
Appreciate all the help.
samthehell said:
Thank you all ... Just ordered the cable. Hope it works.
Appreciate all the help.
Click to expand...
Click to collapse
Here is where u can find full 2.3.6 Asian fastboot file, so you can use rsd for flashing 2.3.6 but for flashing 2.3.5 you have to use Alternative rsd because of bl version
http://forum.xda-developers.com/showthread.php?p=22821170
Sliced by my Razr on Tapatalk
My droid x2 freezes on the dual core start up screen every time i try to turn it on, i pulled the battery out the first time this happened, and I've already went into recovery mode and did the (wipe data/factory reset) option, and i also wiped my cache partition, but still my phone freezes on boot. my phone started doing this when i was using "mcTweaker" and a notification popped up and it said i need to reboot, but as the same time i hit reboot system in the options menu. when i did this the phone cut off and since then it always freezes on the dual core screen when i start it up. i am also still on the stock rom and am rooted. any help or tips on how to fix this is highly appreciated.
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
:/
sd_shadow said:
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
Click to expand...
Click to collapse
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Oops
sneaker14 said:
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Click to expand...
Click to collapse
Ok my bad, i feel lyk such a noob... i just wasnt waiting long enough for the starting RSD protocol support thing. Problem solved
great, just don't flash wrong sbf
Droid x2 and Milestone x2 have different sbfs, because they are different devices, different radios
ok for some reason it stays on the (Starting RSD Protocol Support) screen and never advances onto anything else D: is there a fix for this or is my completely screwed. i thought since the thread i read said it takes 3-5 minutes to start it up thats what my problem was, but i was wrong, the thing just simply wont start up... sorry for false assumption
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Ok thank you sooo much, this was frustrating me since last friday and i think the rsd lite i had was the problem, i went and downloaded a different one and now its working ... once again thanks for your help, ill get back to ya if i mess anything else up haha
sd_shadow said:
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Click to expand...
Click to collapse
now when i try to do it it says (error switching phone to BP Pass through mode) idk what to do or why its doing this
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" 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. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
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.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" 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. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
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.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
so i installed the device manager 2.2.28 and installed the drivers, and im using rsd lite 5.7 and im still getting the error D: so do u know why its still doing this?
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" 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. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
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.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I installed the drivers and im still getting the error for some reason D: i used motorola device manager 2.2.28 to install the drivers. and am using rsd lite 5.7
use ezSBF for x2, no drivers needed
sd_shadow said:
use ezSBF for x2, no drivers needed
Click to expand...
Click to collapse
alrighty im bout to try that, but if that doesnt work is it the last option for me... and if i brought it back to the store would they fix it?
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
sd_shadow said:
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Whoa are you telling us ezsbf didn't work?? Is this the first "actual" bricking of a x2?
Sent from my MB870 using xda app-developers app
sneaker14 said:
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Click to expand...
Click to collapse
your holding volume up, when powering on, to boot to 'starting rsd support'?