Separate names with a comma.
Discussion in 'Droid X Tech Support' started by 66racer, Sep 22, 2010.
I'm having this same exact issue. man this blows.
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.
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.
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.
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.
Re: errors from above posts...
Could a simple boot into recovery and clear cache help ???Maybe there are some junk files leftover..
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.
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
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.
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.
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...
No, it's definitely not. Here it is one more time, with feeling: