Droid 2 stuck at bootloader, sbf flash doesnt work HELP!

Discussion in 'Android Tech Support' started by jrichardson, Dec 14, 2010.

  1. jrichardson

    jrichardson New Member

    Joined:
    Dec 13, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Hey,
    I have a Droid 2 that I can't seem to get the OS flashed back onto it. at first it gave the 'batt Low' msg then I got a charger and then 'batt ok ok to program'
    I have tried in RsdLite and ubuntu sbf_flash to get every relevant .sbf file to work and so far have gotten nothing except back at the bootloader. I also tried loading the sbf's onto the sd card and it gives me a 'signature verification failed' here are the sbfs i have tried:

    <<VRZ_A955_2.3.20_1FF_01.sbf>> the only one that appears to flash correctly yet fails and gives a 'failed to swutch to BP passthrough mode' or similar error.

    <<SHADO_X6_2.3.13_SYSTEM-ONLY.sbf>> Fails, gives critcal error FEBE 0047

    <<DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf>>
    gives:
    ERR: A5,70,70,00,1F
    MEM_MAP BLANK
    SERVICE REQ'D

    any thoughts, suggestions?
     
  2. teddyearp

    teddyearp Senior Member

    Joined:
    Jan 13, 2010
    Messages:
    1,806
    Likes Received:
    10
    Trophy Points:
    83
    Location:
    Randle, WA
    Ratings:
    +10
    Current Phone Model:
    Motorola XT1103 (Nexus 6)
    :welcome:

    I don't know much about the A955 Droid 2, but I do know that loading the .sbf files to your sdcard is pointless. And not only that, but the second two are NOT for your phone model. So to sum up, as you already should know from your post, if the .sbf file is not for your phone model and your phone model only do NOT try to use it. Unless you just want to potentially turn your phone into a paperweight.



    Sorry I had no real solution for you and good luck
     
  3. pc747

    pc747 Administrator
    Staff Member Rescue Squad

    Joined:
    Dec 23, 2009
    Messages:
    22,699
    Likes Received:
    4,182
    Trophy Points:
    1,123
    Ratings:
    +4,690
    with a full battery use the sbf from here:

    TBH & MyDroidWorld Present: Droid 2 (2.3.20) Triple Threat

    and follow this video...ignore the part about the patch and just follow the steps after booting into the bootloader which is power on + physical up button.




    I know the video shows a droid x but the device is the same and the steps are the same except you will use a different file and how you get into the bootloader.

    Afterwards when it tell you to wipe you do so by powering on and hold x and hit the search button on the physical keyboard.
     
  4. pfilly

    pfilly New Member

    Joined:
    May 16, 2010
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    So how do you get into the bootloader?
     
  5. jrichardson

    jrichardson New Member

    Joined:
    Dec 13, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    When powering the device on hold the 'x' key and wait for the ! android symbol , then hit the magnifying glass search key and it will take you to the recovery console. I am droid exactly what is presented in that video but when i goto 'wipe data/factory reset' i doesn't load anything.....goes to the 'reboot system' option......and then back to the 'OK to Program' :(
     
  6. UrbanBounca

    UrbanBounca Rescue Squad
    Staff Member Rescue Squad Premium Member

    Joined:
    Sep 25, 2010
    Messages:
    2,733
    Likes Received:
    196
    Trophy Points:
    143
    Location:
    Virginia
    Ratings:
    +237
  7. mattv111

    mattv111 Member

    Joined:
    Dec 21, 2010
    Messages:
    254
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Greenville, NC
    Ratings:
    +0
    that's def not how you get to the bootloader. That's how you get to recovery mode
     
  8. jrichardson

    jrichardson New Member

    Joined:
    Dec 13, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Yeah, I got them mixed up.

    This is the error message Rsdlite is giving me when I flash <VRZ_A955_2.3.20_1FF_01.sbf>.

    07:25:42, January 04, 2011
    Line: 527
    ERROR: AP Die ID: 1a00011648a45d010000f8ff0100

    07:25:42, January 04, 2011
    Line: 534
    ERROR: BP Die ID: 0000000000000000d56532890485

    07:25:42, January 04, 2011
    Line: 541
    ERROR: AP Public ID: 36b3b02d8266e31ee9c7d5d7a3832ff706661eda

    07:25:42, January 04, 2011
    Line: 548
    ERROR: BP Public ID: 040000000500000002000000ffff0000f5113289

    07:33:01, January 04, 2011
    Line: 1836
    ERROR: Phone[0000]: Error switching phone to BP Pass through mode
    File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
    Device ID: 0

    07:33:11, January 04, 2011
    Line: 719
    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:\GitProjects2\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
    Device ID: 0

    07:33:11, January 04, 2011
    Line: 597
    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:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
    Device ID: 0

    Can anyone make sense of this? I'm thinking at this point the unit has an issue with the logicboard that won't allow the rom to load. I would love it if someone could suggest something more.
     
  9. sikbrik

    sikbrik New Member

    Joined:
    Oct 21, 2010
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Did you ever get this to work? I've SBF'd about 20 times previously but I'm getting the same set of errors this time. :icon_evil: I'll check back if I get it working. Curious to know if someone else already figured it out, though.

    To sum it up:

    -SBF file is correct one from TBH
    -RSD Lite 4.8 on Windows 7 (not the issue - fails from command line with admin rights, as well)
    -flash fails immediately
     
  10. jrichardson

    jrichardson New Member

    Joined:
    Dec 13, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I am assuming that my board has a bad NVRAM, and the flashing doesn't stick due to this. Are you sure you have the updated drivers installed and the .ini patch? look at the error log and see what it says.
     
  11. sikbrik

    sikbrik New Member

    Joined:
    Oct 21, 2010
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Got mine working again this afternoon. First tried flashing bootloader sbf...that downgraded the bootloader version. Still no joy, but new errors. Then had to uninstall all moto drivers, motoconnect, motorola devices from device manager, and rsdlite. Reinstalled drivers and rsdlite and then it worked. Yay!

    Hope this helps someone else someday but my issue might have been a one-off flukey thing.
     
  12. furbearingmammal

    furbearingmammal Super Moderator
    Staff Member

    Joined:
    Jun 16, 2010
    Messages:
    11,163
    Likes Received:
    372
    Trophy Points:
    513
    Location:
    Anywhere you're not
    Ratings:
    +455
    Current Phone Model:
    32GB Moto X Developers Edition
    Twitter:
    furryvarmint
    Actually, uninstalling and reinstalling the drivers are a troubleshooting thing for RSD Lite. Normally, though, RSD Lite just won't install anything rather than erroring out. :) Glad you got it working!
     
Search tags for this page
bootloader file for motrorola droid2
,

critical error febe 0047

,
droid 2 and stuck in bootloader
,
droid 2 bootloader
,
droid 2 bootloader error
,
droid 2 critical error febe 0047
,

droid 2 stuck in bootloader

,
droid 2 stuck on bootloader
,
febe 0047 critical error
,
motorola droid 2 stuck in bootloader