Is there fix for mistake on 2.2ota to 2.1sbf?

[66racer]

Hey guys,

Scanned the pages a few in and didnt see anything really related. I now have recieved my replacement droid x but like many I got stuck on the M logo, but this happened to me the night of release before it was known that 2.1sbf was a mistake, well i attempted to 2.1sbf after it being impossible to get into recovery mode. Now the phone is bricked, stuck in bootloader. Is there a fix for these phones? Curious on trying it out before sending the phone back.

I did notice the leaked version acted the same way as the OTA version did on my original phone, got stuck on M logo with beta leaked version too, except with leak I was eventually able to get it to boot, but half the time it didnt boot if shut off, so I reverted thinking it was just beta issues, well OTA was worse because I couldnt access recovery, I think motorola used various vendors to supply the internals on the phones, thats why some failed and others didnt. I saw this when I was a technician at mercedes benz, a few manufacturers made the same component so when flashes came out, some cars freaked out and others worked flawlessly. My replacement phone took beta version just fine, so I will be rolling back and trying the OTA version soon. Just need to do it a day I can afford not having a phone in case it goes down again lol

 

[xliderider]

There is a 2.2 sbf file, but it isn't a full operating system. It may be a little hard to find though.

 

[66racer]

There is a 2.2 sbf file, but it isn't a full operating system. It may be a little hard to find though.

Yeah I downloaded that in case is disappears but when they released it they said in the file description it wouldnt fix the 2.1sbf mistake. I think they said its in case while messing with themes or certain files and the os goes bad the new 2.2(2.3) sbf would fix it. Correct me if im wrong though.