Database Users

Droid X actually bricked?

My Droid X is special... It boots into bootloader automagically every time i turn it on. It says its ok to Program when the battery is charged so I have successfully linked it to RSD lite following the documented steps and have run it 4 or 5 times, getting the same result each time. It gets all the way through and then reboot the phone which immediately goes back into bootloader. RSD lite then errors out with a FAIL. The message says
'unable to switch phone to BP pass through mode' or something to that nature.
I have also run it on an ubuntu linux machine where it runs successfully but with no real results.
I have tried so many things, including trying to flash the newest froyo update.zip through the stock recovery. I've wiped multiple times, rebooted etc... running the update.zip gets all the way to updating radio image where it errors out.
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", /tmp/bp.img")
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
is it possible I have a hardware issue?
I have followed rootz wiki to a T with no results
Do I have a fix?
I've searched and searched and found no fixes for the errors i've encountered. Thanks for any help

Same thing happened to me when I tried to apply the SBF. I was trying to use a virtual machine and it just wouldn't work. I loaded a boot camp partition on my macbook pro, installed 32bit WinXP, booted into XP and it worked the very first time.

I've tried it on a 32bit xp machine, a 64bit win 7 machine, and an ubuntu machine. The 2 windows/RSD sbf installs gave me the same error... the Ubuntu runs everything, goes to reboot phone.. and the phone just reboots back to bootloader... am i missing a step?
i somehow managed to change the bootloader from 29.01 to 30.01 if that means anything.. man this is frustrating

this should fix all
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html

Gman25 said:
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
Click to expand...
Click to collapse
Negative... followed this to a T. Really i need someone to address the errors i've described since they seem to be rare

trillonometry said:
Negative... followed this to a T. Really i need someone to address the errors i've described since they seem to be rare
Click to expand...
Click to collapse
Well, Like I said, I had the same exact error you are having. Perhaps try re-downloading the SBF file or get it from a different source.
If nothing else, take it back to VZW. Don't lie, but just tell them you were trying to restore your phone and this is what you got.

mrnosox said:
Well, Like I said, I had the same exact error you are having. Perhaps try re-downloading the SBF file or get it from a different source.
If nothing else, take it back to VZW. Don't lie, but just tell them you were trying to restore your phone and this is what you got.
Click to expand...
Click to collapse
Yeah that looks like my last resort. unfortunately I bought it as a brick off ebay thinking i could get it working since it was booting into bootloader so i dont know how much help verizon will be since i didnt purchase through them

trillonometry said:
Yeah that looks like my last resort. unfortunately I bought it as a brick off ebay thinking i could get it working since it was booting into bootloader so i dont know how much help verizon will be since i didnt purchase through them
Click to expand...
Click to collapse
Just covering all bases here, but are you *sure* you are using RSD Lite 4.7 and dragged the .ini patch into its program folder? A lot of people forget that last part.
And if it really is a brick, hope you didn't pay much for it =/.

I had a similar problem with the switching to BP bypass mode on a Win 7 64-bit system, I had done this before on the same system a couple of weeks ago successfully. I ended up switching to an old system I have with a fresh 32-bit XP install, everything went without a hitch the first time after accepting the firewall alerts that popped up around the time that the phone switched to the BP Bypass mode.
There may be firewall issues, I've seen a post on it, but can't for the life remember where.
Hope it helps.

i had the same problem. i got to the error message saying something about Loading RAM or something idk. i was trying to apply BigX's theme over an old one via ADB cuz im having mounting issues on CM.
but anyways. after the 4th time it finally went threw. im running Win 7 64-bit Ultimate. i was watching a movie at the sametime on my comp(2 screens) and i closed all my backgrounds besides those two and it worked. as soon i clicked start on the RSD, i went back to the movie and didnt mess with it at all. dont really know if doing any of dat helped but it worked for me. good luck with ur troubles. if u find a solution post it up just incase this happens to me again and i dont get it fixed this time lol

djtoonjr said:
i had the same problem. i got to the error message saying something about Loading RAM or something idk. i was trying to apply BigX's theme over an old one via ADB cuz im having mounting issues on CM.
but anyways. after the 4th time it finally went threw. im running Win 7 64-bit Ultimate. i was watching a movie at the sametime on my comp(2 screens) and i closed all my backgrounds besides those two and it worked. as soon i clicked start on the RSD, i went back to the movie and didnt mess with it at all. dont really know if doing any of dat helped but it worked for me. good luck with ur troubles. if u find a solution post it up just incase this happens to me again and i dont get it fixed this time lol
Click to expand...
Click to collapse
Yeah I am definitely going to redownload the sbf and try again in the morning too late to get into it now for me. IF i ever get it fixed then I will post what I did so here's hoping... I got the same set up too so I will throw on some iron man2 and tinker with a brick all day!

trillonometry said:
My Droid X is special... It boots into bootloader automagically every time i turn it on. It says its ok to Program when the battery is charged so I have successfully linked it to RSD lite following the documented steps and have run it 4 or 5 times, getting the same result each time. It gets all the way through and then reboot the phone which immediately goes back into bootloader. RSD lite then errors out with a FAIL. The message says
'unable to switch phone to BP pass through mode' or something to that nature.
I have also run it on an ubuntu linux machine where it runs successfully but with no real results.
I have tried so many things, including trying to flash the newest froyo update.zip through the stock recovery. I've wiped multiple times, rebooted etc... running the update.zip gets all the way to updating radio image where it errors out.
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", /tmp/bp.img")
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
is it possible I have a hardware issue?
I have followed rootz wiki to a T with no results
Do I have a fix?
I've searched and searched and found no fixes for the errors i've encountered. Thanks for any help
Click to expand...
Click to collapse
Device ID: 0
13:54:14, October 16, 2010
Line: 713
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
13:54:14, October 16, 2010
Line: 589
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
13:54:38, October 16, 2010
Line: 518
ERROR: AP Die ID: 20700014ed845d010000f8ff0100
13:54:39, October 16, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
13:54:39, October 16, 2010
Line: 532
ERROR: AP Public ID: 30efc09241ed7c2c973d65140aecb2a2b2d655d8
13:54:39, October 16, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
14:02:04, October 16, 2010
Line: 1836
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:02:14, October 16, 2010
Line: 713
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
14:02:14, October 16, 2010
Line: 589
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

ok- I am sure you all ready know all this but I just wanted to double check. You said that you followed the instructions on rootzwiki to the T? Well the only instructions I see on the rootzwiki are for the 2.1 sbf. So here is what I am wondering... are you using the 2.1 sbf or the 2.2 sbf? Bc the rootzwiki is a link to the 2.1 sbf not the 2.2 sbf. the name of the 2.2 sbf is...
VRZ_MB810_2.3.15_1FF_01
You said you bought the phone bricked. I was thinking that maybe it was one of those cases where the guy had 2.1, then got the 2.2 ota, decided he wanted to go back to 2.1, tried to sbf and bricked his phone. If that is the case then you need the newly leaked 2.2 sbf and not the one linked to from rootzwiki.
Like I said - I am sure you know all this- but just in case I thought I would ask if you are using the new 2.2 sbf.
just trying to help.

just to update everyone on the issue here. I am intelligent enough to have tried everything findable on the internet to try and solve my issue. I came to the conclusion that it was an internal hardware issue and the device was not fixable. It has since been put on eBay for parts.
I have replaced it with a working DX so all is well though!
thanks for everyones help

Would this work to SBF my phone iwith Linux??? COPIED and made file name change from Rootzwiki.
I would try it on my phone but I just SBF'ed using windows/RSD method . Got my phone where I like it ,for now...
Linux Instructions:
1.Download*sbf_flash*(credit [mbm])
2.Unzip the SBF*(Download Above)
3.Put your Droid X into bootloader (turn phone off and hold volume down and the camera button while pressing the power button)
4.Connect your USB
5.Open a terminal window.
6.Run "cd*Downloads"
7.Run*"chmod +x sbf_flash"
8.Run "sudo*./sbf_flash*VRZ_MB810_2.3.15_1FF_01.sbf"
9.Wait and finish!
Thank You

I know this is an old thread but I'm going to add my solution just in case it happens to someone else and they have to go on a google journey that yields nothing.
you need:
2.3.320 recovery only SBF
1.connect phone to RSD Lite 4.8
2.select 2.3.320 recovery only sbf
3. flash it
4. phone will now reboot hooray
5. turn off phone and boot into recovery
6. wipe data/factory reset and you should be good to go.
I was so scared that I had bricked my 800 dollar phone but shes back now (best buy purchase)

.... And I'll add mine just in case. (I know, several months later.)
I had the same issue with the "BP passthrough" error. Tried several SBF files multiple times with the same (failed) results. I did a fresh installation of drivers and RSD Lite on another machine, and voila! It worked!
Hope this helps someone!
Andy

[Q] Help with either update.zip to 2.3.40 or SBF?

I'll keep this short so I can get straight to the point. Was running Apex ROM on 2.3.15, and a new version is out for the OTA update that just came out, 2.3.40. Reverted back to stock everything, tried to apply the update.zip, and got an error that said "status 7." Did some reading, saw a suggestion to apply the clean Droid X image from 928droid.com. I did that, tried to update.zip, and it still wouldn't do it. I've cleared everything a couple times and keep getting the error.
So unless there's another route I can go to get the update applied (which I'd love to hear so I can avoid SBF'ing), it looks like I'll need to just SBF. Problem is, in the SBF guides I've seen, it says that the current SBF (the ~450MB one) will only work for the 30.03 bootloader, not 30.04... Well I have 30.04. So I really don't know what to do.
ANY help would be appreciated.

If you already have the 30.04 bootloader (refurb phone on 2.3.151?), you can use the system only SBF for 2.3.340.

It is a refurb that I just got with the 30.04 on 2.3.151. So I should just follow the instructions here as though I'm running the 2.3.20 leak even though I'm not?

Crap crap crap!
You can't use just the system only SBF for 340! No kernel means problems for you! Get your 2.3.151 back to bone stock and try Verizon's over the air update now that it's out. If that doesn't work I'm not sure where you go from where you are.

The OTA update doesn't work, it downloads it, goes to install it, then after getting about 1/4 of the way in it says it failed.

Try the 320 update.zip or the 320 full SBF from Team Black Hat, then do the system only SBF to 340. That should get you back to the right path.

Can you tell me where to get the 320 update.zip?
Right before the Status 7 error it says "Error in /cache/Blur_Version.2.3.15.MB810.Verizon.en.US.zip", if that matters to anyone reading.

You can look around the forums here or over at MDW, but I'm guessing all the links are long gone by now. The Team Black Hat app is a few bucks on the Market and has all the files you want, and to be honest it's worth it. Those guys do a lot for the community!

Wiped data and cache, then restored the backup from here - http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
After that I was able to update, no SBF's anywhere in the process.
Just thought I'd post because I've seen a handful of people having similar problems today.

jacked up my gingerbread

was attempting to maderstcok then apply new ota zip.
So I was thinking about doing this, but it would mean running madderstock (sp I know) first and I read his instructions and not only does my file size not match, astro won't give me an md5 sum. So I am not comfortable with proceeding.
crap
i did it, but i didnt do it right. phone comes on says
bootloader
30.04
Err:A5, 69, 35, 00, 27
battery okay
ok to program
connect usb
data cable
HELP!!!
update - going to attempt full flash w rsdlite.
than how to get to 2.3?
please advise

marculous said:
was attempting to maderstcok then apply new ota zip.
So I was thinking about doing this, but it would mean running madderstock (sp I know) first and I read his instructions and not only does my file size not match, astro won't give me an md5 sum. So I am not comfortable with proceeding.
crap
i did it, but i didnt do it right. phone comes on says
bootloader
30.04
Err:A5, 69, 35, 00, 27
battery okay
ok to program
connect usb
data cable
HELP!!!
update - going to attempt full flash w rsdlite.
than how to get to 2.3?
please advise
Click to expand...
Click to collapse
update - fixed it. now back where i started,only i dont want to update to 2.3 at this time.
unless you know how or just want to sbf your phone, dont do what i did -
i had 2.2.1, rooted, running apex 1.4.1, applied maderstck .340 to restore stock so i could apply the new 2.3 update, but that update stuck my X in bootloader.

[Q] [URGENT] [HELP REQ] Err: A5,70,39,00,27

Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?

AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.

bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.

I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App

http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...

Problem with RSD Lite?!

Hey all,
I'm trying to downgrade to 1.2.6 via RSD Lite and I am getting this error at 93%
22:38:29, July 21, 2011
Line: 958
ERROR: Phone[0000]: Multi Interface threads timedout and did not complete the flashing operation
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
22:40:29, July 21, 2011
Line: 2008
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 767
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 1194
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 610
ERROR: Flash failure: Phone[0000]: Multi Interface threads timedout and did not complete the flashing operation (Error Code: 8c),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
22:50:50, July 21, 2011
Line: 1506
ERROR: Error getting subscriber unit information.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Click to expand...
Click to collapse
It seems to try to 'Switch phone to BP Pass through mode' at 93%... fails to do so, and times out. Anyone else had this happen?
I can still start the phone, get into the OS, it says 1.2.6...so I thought maybe it did work...however, when i then try to update after rooting, the update fails to install. Thoughts?!?! Thanks!

Crymson said:
Hey all,
I'm trying to downgrade to 1.2.6 via RSD Lite and I am getting this error at 93%
It seems to try to 'Switch phone to BP Pass through mode' at 93%... fails to do so, and times out. Anyone else had this happen?
I can still start the phone, get into the OS, it says 1.2.6...so I thought maybe it did work...however, when i then try to update after rooting, the update fails to install. Thoughts?!?! Thanks!
Click to expand...
Click to collapse
try flashing to .83 maybe where you unlocked bl or on a different ota?

I got my phone with 1.8.3 on it and was trying to downgrade to 1.2.6. The downgrade failed, however, the phone does start, and it does say 1.2.6 and I can root...I just can't perform system update, as the install fails.
You are saying I should root, and then go to 1.8.3 via RSD Lite, and not through the system update?
Also, I have not unlocked the bootloader yet, is that needed for this? I thought it was only needed for CWM?

If the ota updates aren't working I would use rsd. You do not need an unlocked bootloader I was asking if u have one cause it could have affected the phone
Sent from my MB860 using XDA Premium App

If i root in 1.2.6, then use rsd to update to 1.8.3, wont superuser be gone, and won't I lose root?
Will the afterupdate.bat in gladroot still work if i use rsd to update and not ota?

When I get home, I'm going to try to flash 1.2.6 again, using some of the tips and tricks for flashing SBFs. Shorten the name, put it in C:, run RSD as admin, and update to v5.3.1 (was using v5)
Hopefully this will stop the RSD error

Try rebooting your computer, and reinstall drivers from Motorola.
If that fails use another computer.
Sent from my MB860 using Tapatalk

Try the new rad and update drivers
Sent from my MB860 using XDA Premium App

Yes! Thanks to everyone for their help! I updated RSD Lite, and switched computers, and it flashed perfectly now. I have since unlocked the bootloader, went to 1.83, and got root. Now to pick what rom i want, any suggestions?

Crymson said:
Yes! Thanks to everyone for their help! I updated RSD Lite, and switched computers, and it flashed perfectly now. I have since unlocked the bootloader, went to 1.83, and got root. Now to pick what rom i want, any suggestions?
Click to expand...
Click to collapse
I suggest deleting RSD. Now that you have the unlocked bootloader using it will brick your phone. I unlocked mine and have not tried any gingerbread roms yet. I am still running 183 with ginger blur. Everything works great on it, and I want to let the new roms develop for a while and work out the kinks before I jump in. Just an option.

plasticglock said:
I suggest deleting RSD. Now that you have the unlocked bootloader using it will brick your phone. I unlocked mine and have not tried any gingerbread roms yet. I am still running 183 with ginger blur. Everything works great on it, and I want to let the new roms develop for a while and work out the kinks before I jump in. Just an option.
Click to expand...
Click to collapse
No. I've unlocked my bootloader and I've successfully flashed the 1.8.3 SBF multiple times with no issues.
If you flash the HKTW Gingerbread or 4.5.91 through fastboot, you won't have to worry about bricking your device.