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

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.

phone boots straight into bootloader and will not flash

I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks

You are going to need to charge your battery before you can sbf again. You might want to redownload the sbf again. If you go to droidxforums there is a linux distro that you download and burn as an iso to a cd that is really easy to run. First get your battery above 80 percent before you flash again. When I get to my computer I willingly post the link.
Sent from my DROIDX using XDA App
update: here is the link for the linux distro......http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html

It sounds like you are missing a driver that installs towards the end of the flash. Sorry I can't post the link, but you can google moto driver download. It's the 4.90 drivers.
Sent from my DROID X in Western Illinois

Xodus83 said:
I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks
Click to expand...
Click to collapse
When you get your battery charged SBF again, when it fails do the "SYSTEM" only SBF and it will work. I believe the error (err: a5,69,35,00,27) you are getting has to do with the stock GB recovery. I had that problem but I was still able to boot into CWR and install a recovery patch by TBH. Let me know if this works for you.

I was wondering if there was a resolution to this issue. I am getting the exact same issue, Err:A5,69,35,00,27 and I have done everything but stand on my head. Previous to reading bigshotrob22's post, I had re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
Again, I goto a new version and I go right back to original error though.
I tried bigshotrob22's suggestion and downloaded the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

You could try taking it to a VZ store and telling them that this happened after the OTA. Seems to me that this is their fault and they should fix it.

[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...

re: 2.3.6 Upgrade issue.

re: 2.3.6 Upgrade issue.
I may have made a mistake.
I recently updated my atrix to 2.3.6. It installed successfully but I decided to flash it back to 2.3.4, which I'm currently regretting.
When I turn my Atrix 4G on, It says 'failed to boot 1'.
If I hold the Volume up and power buttong it says:
'Failed to boot 1, PwrReason: Power_cut, Starting fastboot protocol support'.
Im tried to flash the roms using RSDLite:
att-2.3.4_pudding_preroot and also the
official 2.3.6
The error is:
Failed flashing process. Unable to retrieve interface handle.
I tried to unlock bootloader cmd, but wasn't successful.
Any ideas guys?

As an update, i tried to use fastboot to load images.
Instructions to root Atrix 4G running Gingerbread:
-----------------
Download and Extract Fastboot Files to your C: drive (Download Link)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
---------------
it says:
sending preinstall OK
writing preinstall... Failed remote 00180004.
I can't see to write to boot, system or any component?
Do I need to unlock the bootloader? Sorry this stuff is all new to me, and trying to piece it together.

Please use the search, I faced the same issue, you will have to create a factory cable and using RSDLite, flash the 2.3.6, you cannot flash the 2.3.4
Sent from my MB860 using Tapatalk

Hi Tommy,
I saw you're thread but it wasn't clear what steps you took.
Did you modify the Atrix USB Cable in order to install a 2.3.6 sbf file using rsdlite?
I'm wondering if there is another way.

OP - Flash the 2.3.6 sbf file with RSD lite 5.6 - should get you back up and running just fine...

I tried flashing the:
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012
and got this error in rsdlite
internal error while programming phone.
Then after that if I try it again, or try the pudding 2.3.4 one the error changes to:
Failed flashing process. Unable to retrieve interface ahndle 0x7027.

re: 2.3.6 Upgrade issue
First off let me say I know absolutely nothing of development but I figured I'd be brave enough to experiment any way. So I tried upgrading yesterday with partial success, there was no separate .img files at the time though . I'm rooted and have an unlocked bootloader; what I did was extract the zip file from the cache folder onto my PC then removed ap20bl.img seeing that I read all the horrors of possibly re-locking bootloader and bricking I then zipped the file and named it update.zip and booted the phone to CWM Recovery and tried installing that way. I realized after failing the install since it prompted that it couldn't find the ap20bl.img that there must me a script. Knowing that there'd probably be a size check I did this any way....used a bl.img from the 2.3.4 fruitcake and renamed it to ap20bl.img still failing therefore I assume that it really did check the file size. I then located the updater script and removed references to the ap20bl.img file. I tried install again this time saying something about E:\ unfortunately I don't recall exactly what.....so to take care of that I deleted the cache (probably a bad idea). That got rid of that error but from that point I got an error 6 ever since. I decided to reboot the phone which booted fine. Checked "About Phone" and it said the current version was 4.5.141, I was very happy about that; checked that the phone was still rooted and it was. Calls worked, bluetooth worked.....BUT ....it came time to check the wireless....."ERROR". Yip, no more WiFi. I rebooted to CWM and did a factory reset...rebooted again checked WiFi...now said "Turning on, Turning off, Error". So.......I rebooted to fastboot and sent the 2.3.4 radio (.91), rebooted and still got the error. I decided even though I read not to, to go back to 2.3.4 so I rebooted CWM, did the necessary wipes and reinstalled the 2.3.4 fruitcake then checked WiFi which now worked (or so I thought)....the connection dropped after a while then said error when I checked its status so I rebooted and it worked fine only to have the same issue again. I then did necessary wipes and tried Neutrino 2.1 EE seeing that it was the only ROM I had with me at work still having the same WiFi issue. At this time I haven't done anything else with the phone but hopefully this information will help developers or anyone else

Your only hope is the Motorola Factory Cable, yes it is configured differently, in it the red and brown cable are joined, please see my thread for reference, also you will find lot of articles on the internet, you will not be able to flash without it, been there, done that
Sent from my MB860 using Tapatalk