stuck in bootloader / sbf not taking

Discussion in 'Droid X Hacks' started by jwewing, Jul 14, 2011.

  1. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    I need some help SBFing my DX. Screen shows Bootloader 30.04 err.A5,69,35,00,27 I have been trying to SBF using RSD Lite 4.9 4.8 and 4.7, Linux, and also a Linux boot disc for SBF. The SBF file that I am using is VRZ_MB810_2.3.34_1FF_01.sbf. Each of these ways to SBF says that it completes without any problems but I am still stuck at the bootloader screen. I have tried different downloads and also rand MD5 checksum on the files. Battery is full power. When using RDSLite I get these in the log files:
  2. PARick
    Offline

    PARick New Member

    Joined:
    May 18, 2010
    Messages:
    726
    Likes Received:
    0
    Trophy Points:
    0
    Have you tried a battery pull, and reboot?
  3. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    That error message likely results from one of 2 things. One is bad drivers and the other is the actual phone is damaged not allowing the install. When you connect to RSD Lite and click show device does it show up all the correct info?

    I would first try the battery pull and also a different USB cable before blaming the phone. Even a different USB port or computer may help.
  4. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    PARick, yes I have tried the battery pull including holding power and home to get into recovery. Doesnt work.
    ABQNM, Drivers should be fine Ive downloaded them several times. What would the correct info be in RDS Lite? This is what I am getting when connected
    I have tried other computers including ones running Linux and XP. Later today I will try a different usb port and different cable, I havent thought of that.
  5. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    Out of curiosity if it comes to it, if I took this to Verizon would they be able to tell it was rooted since I am only getting the M boot screen and the bootloader? I was reading somewhere they they are charging full phone price to fix/replace rooted phones?
  6. ldopa
    Offline

    ldopa New Member

    Joined:
    Jan 4, 2011
    Messages:
    4,742
    Likes Received:
    2
    Trophy Points:
    0
    Location:
    Rochester NY
    I would stay clear of VZW. If you can get into Bootloader mode and it says ok to program etc.. you can get it back. It would then be a usb, driver, rsd, pc system or sbf file issue which can be resolved.

    Droid 2 Liberty GB v0.9
  7. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    RSD seems to be seeing the phone correctly, and it has the correct bootloader. It could be a communication issue, ie the cable or usb, but it may be the phone itself is corrupted. As far as them telling if it was rooted, they likely will not look into it because if they can't even get to the stock recovery, their first course will be to SBF it. That will wipe traces of root. If they can't get it to take, they will likely not go further since it is a hardware issue at that point. The chance exists, but the effort involved to check would be more than it is worth.
  8. ldopa
    Offline

    ldopa New Member

    Joined:
    Jan 4, 2011
    Messages:
    4,742
    Likes Received:
    2
    Trophy Points:
    0
    Location:
    Rochester NY
    I had an issue once where the sbf just wouldn't take. I couldn't understand why. It turned out to be my usb port. I was using an old laptop with a 1.0 USB. I went to a friend's house and tried it on his 2.0 USB and it worked fine. So, just try everything before taking the potentially expensive risk of taking it to VZW

    Droid 2 Liberty GB v0.9
  9. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    I tried a different cable and different usb port, still keeps going to the bootloader.
    Idopa, I have tried everything I can think of: 3 different computers including one with Ubuntu and XP and also tried the live Linux boot with sbf, download all files from other places several times and ran md5 checksums on them, different usb ports and cables, diferent versions of the live cd and rsd lite, battery pulls and after putting battery back in I hold the power and home keys, made sure the battery was fully charged, run as admin, and even tried changing the the device id and flash/flex options in RSD Lite. I dont see what else I can try other than unfortunately going to Verizon unless you may have more ideas?
  10. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    Unfortunately, I think Big Red is your only option here. And obviously, don't mention anything you did.
  11. ldopa
    Offline

    ldopa New Member

    Joined:
    Jan 4, 2011
    Messages:
    4,742
    Likes Received:
    2
    Trophy Points:
    0
    Location:
    Rochester NY
    Thats a first for me. I've seen people with corrupt bootloaders, but this is new. I was always taught that if you can access the bootloader and it isn't corrupt, there is a way out. I'm sorry, you may be boned.

    Droid 2 Liberty GB v0.9
  12. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    I know not to tell them it was rooted. Do you think its best to tell them that I was getting non stop force closes so I decided to try the factory reset and thats when I started getting the bootloader screen or simply tell them I started getting the bootloader screen?
  13. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    If you pull the battery and boot up, you just get the red M, right? Don't mention bootloader at all unless that is the only thing that comes up on screen.
  14. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    One thing that could possibly work, but if the phone is definitely broken then it won't. You could try to use the gingerbread SBF first. It is not rooted, but it is a different file and may go through. If it works, then try to SBF back to froyo again so you can get root.

    P.S. I sent you 2 private messages.
  15. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    When the phone starts it shows the M logo for about 10 seconds then goes straight to bootloader.
    I did try the Gingerbread SBF. That changed the white or silver M logo to red but the problem still persisted. I then tried the Froyo SBF again, it went back to the white/silver logo and still only get bootloader.
  16. ABQNM
    Offline

    ABQNM New Member

    Joined:
    Oct 12, 2010
    Messages:
    502
    Likes Received:
    1
    Trophy Points:
    0
    Sounds like the bootloader is working but it just can't write to the actual system memory, whether it is corrupt or just broken, who knows. It seems like it is in a failsafe mode as though it cannot find the OS at all. I think you will probably be OK at Verizon.
  17. jwewing
    Offline

    jwewing New Member

    Joined:
    Jul 14, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    0
    Thanks to all for the help and suggestions. I am heading over to VZ sometime this week.
  18. ldopa
    Offline

    ldopa New Member

    Joined:
    Jan 4, 2011
    Messages:
    4,742
    Likes Received:
    2
    Trophy Points:
    0
    Location:
    Rochester NY
    All the best.

    CM74D2
  19. sqchram
    Offline

    sqchram New Member

    Joined:
    Nov 18, 2009
    Messages:
    185
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    Salt Lake City, UT
    Apologies if i missed it but are you using the maderstock file?
  20. perezil
    Offline

    perezil New Member

    Joined:
    Oct 9, 2011
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    0
    It drives me nuts when people don't return back to the forum the asked help from and post their results.

    I too am running into the same issue and would like to know if the visit to VZW was fruitful.

    I have an open ticket with VZW and an RMA to send the phone in. Sadly, somewhere along the way, the moisture indicator has activated, and although I did tell the phone agent about this, she still proceeded with creating the RMA. Seems something is going on with an update that occured sometime before/after the change of DST. Thus, I think there were some updates that may be to blame here.

    I've tried SBFs via RSD and the Linux ISO from 1KDStaz (which I have to say, is really slick). The 4.5.xxx 1KDStaz stopped the ability to use the Camera button to select (when in PWR + Home mode). So I am in the 2.3.340 from 1KDStaz. ADB does not detect THIS phone (prob due to it not being able to boot).

    I suspect there is something else corrupted (Bootloader? Radio? et.?) but since I can't ADB it, my options are either SBF or an update.zip file that has the proper signature.

    I am at the point where I am considering sending it in on the RMA, but have no idea how the phone will be treated. Yes, they know about the Moisture Sensor issue, but I was talking to a Motorola Representative (not employee) overseas, so I am reluctant to believe that anything she has offered or expects will or, is reality.
    :serious:
    Last edited: Nov 26, 2011
Search tags for this page
error bp die id error ap public id rsd lite
,

getphoneid failed error rsdlite

,
motorola droid 3 usb host
,
rsd lite getphoneid failed: error
,
rsd lite motorola droid x sbf fail
,

rsdlite getphoneid failed

,

the+flashlog+key+is+turned off.