Do not sbf!!!!!!!!!

Discussion in 'Team DeFuse' started by AngDroid, Oct 28, 2010.

  1. AngDroid

    AngDroid Premium Member
    Premium Member Developer

    Joined:
    Apr 20, 2010
    Messages:
    759
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    Do not SBF after OTA UPDATE. I repeat DO NOT SBF AFTER UPDATE!!!
     
  2. Cloppy

    Cloppy Member

    Joined:
    Nov 2, 2009
    Messages:
    159
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    What happened?
     
  3. AngDroid

    AngDroid Premium Member
    Premium Member Developer

    Joined:
    Apr 20, 2010
    Messages:
    759
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    my device is now bricked :)
     
  4. bladearrowney

    bladearrowney New Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    He bricked his dev device :(
     
  5. AngDroid

    AngDroid Premium Member
    Premium Member Developer

    Joined:
    Apr 20, 2010
    Messages:
    759
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    It was a development device...I still have personal phone to use but will not be using it a lot to develop.
     
  6. mrjaydee82

    mrjaydee82 Member

    Joined:
    Mar 10, 2010
    Messages:
    48
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Fort Myers, Fl
    Ratings:
    +0
    Not good :-(
     
  7. cboes19

    cboes19 New Member

    Joined:
    Oct 28, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    First time posting. If you used sbf and are stuck in death loop,enter into bootloader and wipe cache and data and then reboot. That's what worked for me
     
  8. mrjaydee82

    mrjaydee82 Member

    Joined:
    Mar 10, 2010
    Messages:
    48
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Fort Myers, Fl
    Ratings:
    +0
    That most likely not work. The ota update made some kernel changes and etc which maybe playing a big effect that the old sbf file will not work :-(
     
  9. cboes19

    cboes19 New Member

    Joined:
    Oct 28, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I did the sbf using 2.3.15 sbf and got the boot loop. So I went and flashed again with the same result so after freaking out for 20mins. I went and entered the bootloader. Went and did a wipe n puff like magic it reset. After you boot up you have to dial ##7764726 and re-enter you number into the first setting for data tranfer. Do a reset again and your back to stock 2.3.15
     
  10. mwhartman

    mwhartman Super Moderator/RS
    Premium Member

    Joined:
    Jan 15, 2010
    Messages:
    10,737
    Likes Received:
    12
    Trophy Points:
    453
    Location:
    South FL
    Ratings:
    +12

    This is a FIRST!
     
  11. mikeeg02

    mikeeg02 Member

    Joined:
    Oct 19, 2010
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Donated $20 towards you getting another dev device..... from theecho
     
  12. yuusharo

    yuusharo Member

    Joined:
    Oct 19, 2010
    Messages:
    32
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Exactly how are you bricked? Is this similar to the Droid X OTA update last month where it updated the phone's bootloader keys and locked out the old SBF? I mean, if you're stuck in a boot loop that should be easy enough to fix, but if you're stuck in bootloader with the "MEM_BLANK" error, then yeah, you're screwed until a full SBF of the new build leaks out... assuming it will be =(.