Froyo OTA bricked phone?

[66racer]

Need some help

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, was able to make a call. Couldnt enter recovery mode, same M and tried to navigate it blindly with no luck (assuming it was entered with M present).

In the past did do to the leaked froyo (1st one) and had the same thing happen but eventually got it to boot. At the time went back to 2.1 through bootloader procedure sbf install. So i tried it again, this time I get error codes after sbf installs and is stuck in boot loader. any help please?

error a5,70,70,001f

 

[Sydman]

Do you still have the update zip on your sd card? Some people were having issues doing the over the air with that still on the sd card.

 

[ig88b1]

Im having the same issue. the bootloader says MEM_MAP blank, with error codes a5,70,70,00,1f. I removed the SD card completely.

 

[Sydman]

I think SBF is in yalls near future.

 

[ig88b1]

I restored from SBF, thats what started it.

 

[66racer]

I cant recall if the update was in, but I tried the sbf recovery with it removed after the fail and no change. This has worked before a few times when playing with the first froyo leak, Im guessing something changed on the OTA version that doesnt allow sbf recovery? My bootloader says 30.03 also

note: on win7 32bit, made sure to use admin rights too

 

[66racer]

I restored from SBF, thats what started it.

exacally, after the M symbol failure i did sbf recovery and it got even worse with the described problem. Now i dont know if i should go to a verizon store and have them void warranty even though the OTA failure prompted me to do it

 

[ig88b1]

Not sure, it seems like the OTA changed something so we can't go back to 2.1.

 

[66racer]

Not sure, it seems like the OTA changed something so we can't go back to 2.1.

agree, im sure someone will figure it out soon but till then will suck without a phone. I work on the go....

gonna go to verizon since their ota started it, worst case i fix with the help of the guy that figures this out or pay thr $50 for my aftermarket insurance on this and get it replaced

 

[bmwrin1990]

im having the exact same issue...gonna go to verizon tomorrow and hopefully figure it out

 

[Sydman]

Oh yeah I see, SBF should come first then upgrade OTA.

 

[bmwrin1990]

to me, it seems like the phone was flashed but didnt restore the software, so it has nothing to boot...
so hoping that vzw will have something that can reload the software...other than that, i think the phone is screwed

 

[djjsin]

I'm having this same exact issue. man this blows.

 

[Phoxus]

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.

 

[MotoCache1]

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.