I unfortunately ran into this problem last night...
To start off, I used EasyRoot to root the phone, installed Koush's bootstrapper and ROM Manager (all on 2.1). I then booted into recovery and made a backup of the system, just in case I needed to back out of the 2.2 install. Once the backup was finished, I used the recovery to install the ROM Manager version of the 2.2 update.zip file. Everything worked fine - 2.2 came up, played around with it for a while, but then let my wife have her phone back... The Swype keyboard changed colors/themes and the 2.1 version and the size of the DX screen were the major reasons for getting the phone (vision problems).
So, after having my 5 minutes of joy with 2.2 on the X, I decided to revert back to 2.1. I rebooted into CM recovery, and foolishly tried to restore. I don't know if a data wipe beforehand would have saved me, but I even forgot to do that (done it a million times on my D1, but forgot for some reason on the X). Then the problems began.
After the restore to 2.1 finished, it rebooted and hung at the M logo - wouldn't go any further. Having read all of the unbrick guides before taking the plunge to 2.2, I went and followed all of the directions to a T. Even had to switch from a Vista machine to XP because of all the damn permissions - RSD Lite and the SBF wouldn't work properly.
Finally got the SBF installed and rebooted the phone...everything came up fine, but then I noticed a "star" in the notification bar. The error said:
"blur service username or password incorrect"
It wanted me to enter a password on a screen with the phones ESN/MEID as an email address (I think the rest was @svc.moto.com or something along those lines. I rebooted. Same thing. Rebooted again, same thing.
Each time I tried the OTA activation (#228, 1 and #22899) - the phone activated fine, but eventually I saw the blur error.
Then I decided to go ahead and do a factory reset (via the Settings - Privacy) interface. Phone rebooted - all was well, until I started getting random reboots. My wife or I can be swiping on the screen - lock and spontaneously reboot. Or browsing the web - lock and reboot. So far it has happened at least a half dozen times.
Honestly at a loss now - I'm unrooted, stock apps, nothing fancy. I'm hoping to take it back to Costco (where we got it) and see if they'll give us a new one...
Anyone else have anything remotely similar? Or have any idea if there's anything that can be done at this point besides returning it? Will they know what I've done or has the SBF flash basically wiped away all of the evidence of my screw ups?
If you've made it this far, thanks for reading the novel of a post, and if you have any suggestions, thanks for those too.
And thank you to all of the people that worked on providing the SBF last night - without that I would have been hosed. It is much appreciated.
To start off, I used EasyRoot to root the phone, installed Koush's bootstrapper and ROM Manager (all on 2.1). I then booted into recovery and made a backup of the system, just in case I needed to back out of the 2.2 install. Once the backup was finished, I used the recovery to install the ROM Manager version of the 2.2 update.zip file. Everything worked fine - 2.2 came up, played around with it for a while, but then let my wife have her phone back... The Swype keyboard changed colors/themes and the 2.1 version and the size of the DX screen were the major reasons for getting the phone (vision problems).
So, after having my 5 minutes of joy with 2.2 on the X, I decided to revert back to 2.1. I rebooted into CM recovery, and foolishly tried to restore. I don't know if a data wipe beforehand would have saved me, but I even forgot to do that (done it a million times on my D1, but forgot for some reason on the X). Then the problems began.
After the restore to 2.1 finished, it rebooted and hung at the M logo - wouldn't go any further. Having read all of the unbrick guides before taking the plunge to 2.2, I went and followed all of the directions to a T. Even had to switch from a Vista machine to XP because of all the damn permissions - RSD Lite and the SBF wouldn't work properly.
Finally got the SBF installed and rebooted the phone...everything came up fine, but then I noticed a "star" in the notification bar. The error said:
"blur service username or password incorrect"
It wanted me to enter a password on a screen with the phones ESN/MEID as an email address (I think the rest was @svc.moto.com or something along those lines. I rebooted. Same thing. Rebooted again, same thing.
Each time I tried the OTA activation (#228, 1 and #22899) - the phone activated fine, but eventually I saw the blur error.
Then I decided to go ahead and do a factory reset (via the Settings - Privacy) interface. Phone rebooted - all was well, until I started getting random reboots. My wife or I can be swiping on the screen - lock and spontaneously reboot. Or browsing the web - lock and reboot. So far it has happened at least a half dozen times.
Honestly at a loss now - I'm unrooted, stock apps, nothing fancy. I'm hoping to take it back to Costco (where we got it) and see if they'll give us a new one...
Anyone else have anything remotely similar? Or have any idea if there's anything that can be done at this point besides returning it? Will they know what I've done or has the SBF flash basically wiped away all of the evidence of my screw ups?
If you've made it this far, thanks for reading the novel of a post, and if you have any suggestions, thanks for those too.
And thank you to all of the people that worked on providing the SBF last night - without that I would have been hosed. It is much appreciated.
Just letting everyone know that I also tried to flash the 2.1 SBF after updating to 2.2 and ran into the deathly droid eye, but managed to semi-fix it.
Luckily I still had the update.zip from 2.2 on my SD card and I simply booted into recovery and reflashed that and I'm at least back to 2.2.
At least your phone will work again.
I had rooted 2.2. Then I used clockwork mod to restore a nandroid backup from 2.1 and phone wouldn't boot. Battery died in middle of SBF and got code corrupt error. Will try SBF again with full battery but have no idea what will happen. I do have update.zip with froyo in case I need to try to appy that again immediately
yeah, (as you now know) you can't do that. nandroids from 2.1 are incompatible with 2.2, and vice versa. Even though there is just a .1 difference between the OS name, they are completely different beasts in terms of how the files interact with one another. Especially since 2.1 is deodexed and 2.2 is odexed.
