Stuck at bootloader menu

Discussion in 'Android Tech Support' started by XxSeiFeRxX, Nov 20, 2010.

  1. XxSeiFeRxX

    XxSeiFeRxX New Member

    Joined:
    Nov 20, 2010
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I recently dropped my Droid X (fully submerged) in water. I immediately pulled the battery and let dry for 2 full days. When I turned it back on it was stuck in the bootloader menu:

    Bootloader
    30.03

    Battery Ok
    Ok to program
    Connect usb
    Data Cable

    The phone was rooted after the new 2.2 update.

    I searched around and got the new sbf 2.0 (VRZ_MB810_2.3.15_1FF_01.sbf) and RSD lite 4.7 with ini patch file, and motorola drivers (v4.8.0).

    I installed the moto drivers (win XP 32), RSD lite (overriding the existing ini with new one).

    I loaded up RSD lite and sbf, connected my phone in bootloader menu, pressed start and everything seems like it was working until the very end. RSD was at 99% (Switching device to BP pass through mode) and the phone shows SW update complete.
    The phone then restarts and moto logo shows up then goes back to bootloader menu. RSD then shows error switching device to BP pass through mode. Result = Fail.

    Device Properties: (Before Flash)

    EMEI/ESN: N / A
    Technology: N / A
    Software Version: N / A
    Flex Version: N / A
    Boot Version: N / A
    DRM Version: N / A

    Device Properties: (After Flash)

    IMEI/ESN/MEID: N / A
    Technology: N / A
    Software Version: N / A
    Flex Version: N / A
    Bootloader Version: v0x003003
    DRM Version: N / A
    AP Die ID: <Various Numbers)
    BP Die ID: <Various Numbers)
    AP Public ID: <Various Numbers)
    BP Public ID: <Various Numbers)

    RSD Error Log
    08:32:40, November 20, 2010
    Line: 518
    ERROR: AP Die ID: 146003154b475a010000f07f0000
    08:32:40, November 20, 2010
    Line: 525
    ERROR: BP Die ID: 0000000000000000b55432890485
    08:32:40, November 20, 2010
    Line: 532
    ERROR: AP Public ID: 02231e31ec89fc4a7299974da3d8bce966334af2
    08:32:40, November 20, 2010
    Line: 539
    ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
    08:40:14, November 20, 2010
    Line: 1834
    ERROR: Phone[0000]: Error switching phone to BP Pass through mode
    File: D:\test_dev_usb\flash\code\flashdll\FlashOp.cpp
    Device ID: 0
    08:40:24, November 20, 2010
    Line: 700
    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:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
    Device ID: 0
    08:40:24, November 20, 2010
    Line: 587
    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:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
    Device ID: 0

    I tried multiple combinations of things. I did a data/cache wipe before the flash, after the flash, no data/cache wipe, and it still goes back to the bootloader menu.

    Please let me know if there is anything I can do. Any suggestions? Do you think this may be a hardware failure at this point?
     
    Last edited: Nov 20, 2010
  2. Abe21599

    Abe21599 DF Super Moderator Rescue Squad

    Joined:
    Dec 22, 2009
    Messages:
    6,334
    Likes Received:
    30
    Trophy Points:
    163
    Location:
    Ohio
    Ratings:
    +30
    did you actually replace the flash.ini file in RSDs directory with the one that came with 4.7?
     
  3. XxSeiFeRxX

    XxSeiFeRxX New Member

    Joined:
    Nov 20, 2010
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I downloaded the RSDLite-4.7+patch.zip file which comes with RSDLite-4.7 and pst_flash.ini file. I copied that ini file to the RSD directory and I overrode the existing ini file.
     
  4. Abe21599

    Abe21599 DF Super Moderator Rescue Squad

    Joined:
    Dec 22, 2009
    Messages:
    6,334
    Likes Received:
    30
    Trophy Points:
    163
    Location:
    Ohio
    Ratings:
    +30
    hmm.. it might be jsut a hardware issue now...
     
  5. XxSeiFeRxX

    XxSeiFeRxX New Member

    Joined:
    Nov 20, 2010
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    So if it is a hardware issue... I don't have insurance and I know that the stickers inside are pink because of the water damage. Am I able to sign up for insurance now and then come back in a couple weeks and say that its not working? Any suggestions on how to deal with it? Does insurance cover water damage?
     
  6. brando56894

    brando56894 Active Member

    Joined:
    Mar 9, 2010
    Messages:
    1,217
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New Jersey
    Ratings:
    +0
    nope, youre pretty much screwed.
     
  7. Droid DOES!!

    Droid DOES!! What iDoesn't Theme Developer Premium Member

    Joined:
    Jun 12, 2010
    Messages:
    6,375
    Likes Received:
    35
    Trophy Points:
    163
    Ratings:
    +35
    If you've had it for less than 30 days, insurance CAN be added to your device but can take up to 30 days to become effective. Insurance is usually a good idea with as expensive as these phones are!



    Sent from my Droid using DroidForums app (free in market)
     
  8. Abe21599

    Abe21599 DF Super Moderator Rescue Squad

    Joined:
    Dec 22, 2009
    Messages:
    6,334
    Likes Received:
    30
    Trophy Points:
    163
    Location:
    Ohio
    Ratings:
    +30
    but, to add insurance after the initial purchase, ur gonna have to take it into an authorized store to get it checked out. so its not going to work
     
Search tags for this page
android fell in water stuck in bootloader
,
android stuck in bootloader without menu
,

droid razr bootloader menu

,
i stuck in bootloader without menu
,
motorola android pro bootloader error after water damage
,
xoom rsd stuck at switching device