Froyo OTA bricked phone?

Discussion in 'Droid X Tech Support' started by 66racer, Sep 22, 2010.

  1. djjsin

    djjsin New Member

    Joined:
    Jan 14, 2010
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I'm having this same exact issue. man this blows.
     
  2. Phoxus

    Phoxus Member

    Joined:
    Jan 22, 2010
    Messages:
    207
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    San Antonio / Austin Texas
    Ratings:
    +0
    Until further investigation I Highly recommend not flashing the 2.1 SBF if you've updated to the official over the air 2.2 for the Droid X.

    Heed the warning.
     
  3. MotoCache1

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    If someone has been clever enough to save off a copy of the OTA that will help clean this up. It's not a big deal, but having a copy of the OTA will help. I'm sure the VZW stores have an SBF of the current build and can get you back up and running. If you have the OTA file, PM me where to get it and I'll take a look at it. My DX won't receive the OTA, so I won't get it OTA.

    You guys have probably already figured this out, but they changed the signatures in everything from mbmloader forward. All your old code groups are useless now for going backwards. They were serious about this. Kudos to them for a clever chess move.
     
  4. aut0tek

    aut0tek New Member

    Joined:
    Apr 3, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Many of us have had the problem BEFORE the ota. All 2.2 updates cause this on some phones. Not many ppl are researching it. To get the phone to boot, remove battery for 45 secs (Yes, i must be left for quite a while. at least 30) and then put battery back in.

    Sometimes it takes more than once.

    Again, this has happened to SOME phones since the old 2.2 stuff came out weeks ago.
     
  5. MotoCache1

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    Pretty sure this isn't what you've seen before. They've actually changed the signature that the HAB will recognize. If you SBF back to a prior build, where the CG's are signed with a key that is now no longer valid (to mbmloader and mbm that aren't replaced by most SBFs) then your phone is very toast as not even your CDT is valid anymore. Easily fixed by flashing the current CG's with the new, valid signatures back on - if you've got them.
     
  6. kdkinc

    kdkinc Member

    Joined:
    Dec 20, 2009
    Messages:
    323
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Inverness,FL
    Ratings:
    +0
    Re: errors from above posts...

    Could a simple boot into recovery and clear cache help ???Maybe there are some junk files leftover..
    :icon_eek::icon_eek:
     
  7. aut0tek

    aut0tek New Member

    Joined:
    Apr 3, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    No, it is:

    "Did the ota install of froyo from 2.1 rooted, when rebooting (install was done unattended) phone was left with the motorola M symbol and appeared functional...."

    I'm talking about this. You're talking about his 2nd part, which isn't really a MALfunction at all.
     
  8. aut0tek

    aut0tek New Member

    Joined:
    Apr 3, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    no kdk, trust me, a number of us have tried MANY things... I personally have sbf'ed and retried different methods 9x now, and always get the M logo on boot with 2.2
     
  9. MotoCache1

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    OK, cool. Yeah, there are two different issues going on here. Some folks just have trouble after the OTA with bootloops and such and clearing cache, battery pull, etc. would probably fix them right up.

    For the folks that got adventurous and tried to SBF back to a prior build, they are in trouble at the moment.
     
  10. aut0tek

    aut0tek New Member

    Joined:
    Apr 3, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    No, you must pull battery EVERY boot for the problem he/I have. Trust me. It's EVERY reboot. I know about 6 other ppl with it.
     
  11. bmwrin1990

    bmwrin1990 New Member

    Joined:
    Sep 22, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    dude what are you talking about??
    like the guy said before, we have 2 different things going on here...
    the original issue what the phone staying in bootloader after trying to SBF the phone after the official OTA...
     
  12. aut0tek

    aut0tek New Member

    Joined:
    Apr 3, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    No, it's definitely not. Here it is one more time, with feeling:


     
Search tags for this page
a5,70,70,001f
,
bootloader 30.04 err a5 70 70 1f mem map blank
,
droid 2 boot err a5 70 d2.37 battery low
,
droid pro mem map blank
,

droid x err:a5,70,70,001f

,
mb810 bootloader 27.01
,
mem map recovery mode
,
motorola droid x err a5,70,70,001f new map blank
,
motorola mb810 error a5.70.00.00.23
,
my droid2 global says new map blank