SBF fails on "Error switching phone to BP pass through mode (0x70BE)"

Discussion in 'Droid X Tech Support' started by caesar1018, Sep 18, 2012.

  1. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    This is my first time posting on this site, so if this is the wrong area to post this issue please let me know.

    I have a Droid X MB810 that is stuck in Bootloader mode as shown:

    Booloader
    30.04

    Battery OK
    OK to program
    Connect USB
    Data Cable

    I do not know what version was on this phone prior to it becoming a brick
    (I believe it was 4.5.621 OTA because the phone was recently activated 3 months ago)

    I have loaded ALL sbf files in order from oldest to newest. Starting with 1KDS's files
    2.3.340 full, 4.5.596, 4.5.602, 4.5.605 and finally the last one 4.5.621. I realize this last one is the point of no return
    and I can no longer use the others (previous ones didn't work anyhow and gave error messages above "Battery OK" on the phones screen)

    I am running Win 7 64-bit Ultimate w/ rdslite 4.8 and current drivers ( I assume the drivers are current as I have another fully functional Droid X that is being recognized fine by PC via the Motorola USB cable) Battery is a 100%.

    Questions about the drivers????
    Visually I see the following differences when hooking up both phones via USB:

    The working phone when plugged in via USB shows the following info in the "driver software installation" window:
    USB Mass Storage Device Ready to use
    Motorola MB810 USB Device Ready to use
    Motorola MB810 USB Device Ready to use


    When I plug in the bricked Droid X it shows the following on the PHONES screen:
    The last 2 lines of text change? Is this an issue?

    Bootloader
    30.04

    Battery OK
    OK to Program
    Transfer mode:
    USB


    Also, when I connect it to the PC via the Motorola USB cable I get the "driver software installation" window but it says the following:
    Motorola Flash Interface Ready to use

    (I don't see any other info listed as with the fully functional phone)


    I have even "wiped data/factory reset" and "system reboot" the phone each time after every sbf above with no luck either.


    Any help here would be greatly appreciated.
    Thanks
    JT
    Last edited: Sep 18, 2012
  2. leftspin
    Offline

    leftspin Active Member

    Joined:
    Jul 27, 2011
    Messages:
    1,128
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    New Jersey
    I'm a little confused by your post, could you clarify a few things?

    -Does the SBF flash finish, or does it fail somewhere along the way?
    -What are you using to flash the SBF? RSDLite? Linux boot CD?
    -Are you able to successfully flash the working phone?
  3. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    SBF looks to finish with 100% showing in "progress" field.
    Throws the error "Error switching phone to BP pass through mode(0x70BE)phone connected" in the "status" field.
    and shows FAILED in the "results" field.
    I have used both RSDlite 4.8 and 5.7.
    I have not tried a Linux boot CD as of yet.
    Not going to flash the working phone as I need it to make phone calls.
  4. leftspin
    Offline

    leftspin Active Member

    Joined:
    Jul 27, 2011
    Messages:
    1,128
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    New Jersey
    In that case I would try the Linux boot CD method, and if that doesn't work then I have a feeling it would definitely be an issue with the device and not the computer.
  5. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    Did the Linux boot CD method using the 1KDStaz_MX_4.5.604.iso (Milestone X 4.5.604 Gingerbread) - since I believe my phone was on 4.5.621.
    All files loaded and verified fine but I ended up back at the bootloader screen after all was said and done.
    I think the phone is bricked PERIOD!
    Unless someone has some obscure method to fix this issue that I'm unaware of.
    Let me know would ya.
    Thanks
  6. leftspin
    Offline

    leftspin Active Member

    Joined:
    Jul 27, 2011
    Messages:
    1,128
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    New Jersey
  7. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    I doesn't go into safe mode because it is stuck in bootloader mode.
    I can get into recovery mode because I am able to wipe cache, files, and reboot. But all this still only leads to a bootloader screen.
  8. themib
    Offline

    themib Well-Known Member

    Joined:
    Mar 7, 2011
    Messages:
    1,446
    Likes Received:
    27
    Trophy Points:
    48
    Location:
    South Dakota
    usually a bp switching error, is caused from a driver issue
    this is the recommended fix, for the d2

    "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."
  9. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    To get around this issue, once you get a Device driver could not be installed message from Windows (I don't get this error at all), don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. (Done this and still FAILS) Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. (Did this as well and still FAILS) It should now install normally. (IT DOES NOT)If RSDLite timed out and you got an error from it, just repeat the SBF process. (Did this and still FAILS) The driver should now be present, and the flashing process will finish normally. (Nope!)

    I have tried this several times to no avail.
    Thanks for the suggestion.
  10. clueless77
    Offline

    clueless77 New Member

    Joined:
    Sep 16, 2011
    Messages:
    853
    Likes Received:
    7
    Trophy Points:
    0
    Location:
    North Carolina
    I think you might have the first ever hard bricked Droid X, and let me tell you that is hard to do.
  11. themib
    Offline

    themib Well-Known Member

    Joined:
    Mar 7, 2011
    Messages:
    1,446
    Likes Received:
    27
    Trophy Points:
    48
    Location:
    South Dakota
    have you tried, on a different pc or mac?
  12. caesar1018
    Offline

    caesar1018 New Member

    Joined:
    Sep 18, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    0
    Tried it. Still a brick. Thanks for all the suggestions. I hope one works one day.
  13. tbrown2012
    Offline

    tbrown2012 New Member

    Joined:
    Mar 25, 2013
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Texas
    A fix

    Go To this Page: http://www.droidforums.net/forum/re...96&i=1dd460dffac4bfba08b006dabf78082543dcd994
    And Download the android system file 2.34 4.5.621 because your phone has had the .621 ota update and will only work with the file on the bottom of the page. Once you download the file reflash the phone with RSD lite 5.6 or newer. http://goo.gl/NPB7Z
  14. AECRADIO
    Offline

    AECRADIO Member

    Joined:
    Sep 2, 2013
    Messages:
    368
    Likes Received:
    24
    Trophy Points:
    18
    Location:
    Mesa, AZ.
    I finally took the leap, and flashed my DX.
    I was a bit nervous, as I was not excited to see a 'fail' indicator show up in RSDLite, but the entire process worked flawlessly, and applied the .SBF as hoped.
    I made changes to the build.prop Editor, and reset the media.stagefright.enable-record to 'true', as well as themedia.stagefright.enable-rtsp as well. Rebooted and they stayed.
    Since I am a newbie to flashing, I could not control the urge to photograph the task, maybe this might help others, and show them what to expect/look for as the flash this, or other .SBF files to their phone.
    View attachment 66382
    View attachment 66383
    View attachment 66384
    View attachment 66385
    View attachment 66386
  15. AECRADIO
    Offline

    AECRADIO Member

    Joined:
    Sep 2, 2013
    Messages:
    368
    Likes Received:
    24
    Trophy Points:
    18
    Location:
    Mesa, AZ.
    More flashing pics..

    A few I could not upload due to max limit.
    View attachment 66387

    Poor shot, taken too fast...sorry!

    BUT.....the process was a success, and that, means a lot!
    Last edited: Sep 18, 2013
  16. AECRADIO
    Offline

    AECRADIO Member

    Joined:
    Sep 2, 2013
    Messages:
    368
    Likes Received:
    24
    Trophy Points:
    18
    Location:
    Mesa, AZ.
    I had a failure of the phe phone, using this .sbf:[ http://goo.gl/NPB7Z]
    The flashing worked fine, but I lost use of the phone, text was dead, and my number changed to 000 000 6778!
    I had to perform the dreaded *22898 and re-flash BACK to the original .621.
    Now I have to delete the same garbage I dumped the first time I took the phone from stock to root.

    I find I was 'saved' by TB, but not happy tobe back with .621 .sbf. I wil be daring and redo this again soon, I now know this flash was not a workable solution.
    Just wanted to inform people about the potential troubles.
    My system: 4.5.621.MB810.verizon.en.US
    Version:2.3.4
    Build: 4.5.1_57_DX8-51
    ERI: 5
    PRL version: 53269
    Baseband version: BP_C_01.09.15P
    Kernel version: 2.6.32.9-g1282440 mcbk83@il93lnxdroid08 #1
    Droid X on VZW.
  17. themib
    Offline

    themib Well-Known Member

    Joined:
    Mar 7, 2011
    Messages:
    1,446
    Likes Received:
    27
    Trophy Points:
    48
    Location:
    South Dakota
    After flashing a sbf you have to reactivate, every time, and why is it dreaded, it only takes a couple of mins

    did you verify the md5: 06bbf7ee86c0ed64654e14bcb84c4aed
    for Android 2.3.4 System Version 4.5.621 (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf.zip)

    edit: looks like 1KDS site is down
    I have mirror for 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf.zip
    here http://www.androidfilehost.com/?fid=22979706399755132
    Last edited: Sep 18, 2013
  18. AECRADIO
    Offline

    AECRADIO Member

    Joined:
    Sep 2, 2013
    Messages:
    368
    Likes Received:
    24
    Trophy Points:
    18
    Location:
    Mesa, AZ.
    I never received any upgrade/update notification by VZW, the phone just showed the updated file without my interaction.....which sucks, I really would like to request such things, not be forced to accept them as they sneak in and do so during the night.
    At least in the radio business, any flash updates are provided on as-requested basis, and my batch of ibuttons are preloaded with specific uplifts for the platform firmware being updated, which I prefer, not OTA as I do often with AES-256 encryption.

    I just made my own menu widget for such things, and have saved my trial by fire data as a sticky to refer to.
    I never read the comments about losing our phone number after a firmware change, maybe I did not see those posts, and I have ready hundreds prior to my doing such a thing.
    Live and learn, I will take the plunge again, but since I recovered (sort of), what I did not notice, was what such a alteration actually did for me.

    I did note one item a bit odd after the operation, and that was the inclusion of the blue triangle on the display. Was this an indicator that there was a problem, or is this a normal occurrence?
    View attachment 66396
    This of course, is no longer showing after making the 'call of death' to VZW and getting my number reactivated.

    Can I expect to have to call VZW again if I attempt another SBF programming excursion?

    If these were two way radios, this would be a simple matter for me, but nope, I had to dabble in another 'radio-related' field, but happy to do so.
    This is THE learning curve!

    Thanks to ALL that made education fun, once more!
  19. themib
    Offline

    themib Well-Known Member

    Joined:
    Mar 7, 2011
    Messages:
    1,446
    Likes Received:
    27
    Trophy Points:
    48
    Location:
    South Dakota
    Was it this upgrade?
    http://forum.xda-developers.com/showthread.php?t=2447299
    2013 Update System Version: 45.621.10.MB810.Verizon.en.US

    If so you flashed the 4.5.621 sbf and didn't brick?

    Yes after flashing a sbf on any motorola android phone you have to reactivate
    Sent from my DROIDX using Tapatalk 2
  20. AECRADIO
    Offline

    AECRADIO Member

    Joined:
    Sep 2, 2013
    Messages:
    368
    Likes Received:
    24
    Trophy Points:
    18
    Location:
    Mesa, AZ.
    I used this .SBF--->http://goo.gl/NPB7Z], and everything was going according to 'plan', but after the final reboot, I did not need to use he phone, so I did not check on connectivity, or send/receive texts, until the wife showed up and asked me why I never responded.
    But as far as bricking it, no, I performed a reload of TB, RTB, root checker and the 'usual' complement of tools, none of which indicated trouble, except that pesky blue triangle (which is no longer on the status bar).
    I even had WiFi access, so nothing appeared out of place...
    I know I did something improper, but I have no idea what that might be.
    And yes, I used .621 flash...So that was NOT the thing to do.
    This is the file: https://sites.google.com/site/motosbf/droid-x-sbf-files/1FF-P3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-verizon-us.sbf.zip<-----I take it this was a dumb thing to do?
    Last edited: Sep 18, 2013
Search tags for this page
0x70be
,
b.p.pass
,

bp pass through mode

,
error switching phone to bp
,

error switching phone to bp pass through

,

error switching phone to bp pass through mode

,

error switching phone to bp pass through mode (0x70be)

,
error switching phone to bp pass through mode 0x70be
,
error switching to bp pass through mode
,
switch device to bp pass through mode
,
switching device to bp pass through mode
,

switching device to bp pass through mode failed