Ok, So - to begin at the begining, I've had my Bionic since January.
Sometime in February (maybe March?) I rooted it, and about a month later installed some crap application that accidentally deleted some essential component- can't remember what, or why it happened, but that would be irrelevant, as I managed to Use RSD Lite and Flash what I thought was a stock ROM onto it.
It worked aces, except for one particular problem: It wouldn't perform the OTA updates. I would either get the notification that an update (.893) was available, I would download it, I would click to install it. Phone would power down, reboot and it would tell me something like "The Update Failed to Install". I also tried manually downloading and installing the update, but no good.
So I did some searching around, and found a couple of posts from people having the same issue - the common suggested diagnosis I saw was that if a rom was flashed based on a Leak, it would have trouble doing an OTA update. I figured since I had that first problem, and I flashed the "stock" ROM, I must have unknowingly used one based off of a leak. I figured, no big deal, Just find a real stock one and flash that sucker on there.
First thing I did was re-root the little bugger with the MotoFail method (originally used TehRoot, but when I went searching for it again, it said it was deprecated and to use MotoFail.) Next, figured I got to flash this thing.
So, I fired up my virtual machine running XP (Same thing I had to do the first go round - RSD Lite wouldn't work on my host Win 7 x64 Ultimate)
Went through the same steps I went through last time, this time with the .886 build in this thread: http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html
I'm guessing it must have been a bad download, or maybe something happened in the interim to the file while sitting on my HDD waiting to be used, I don't know. But It got all the way to something like "Step 13: Flashing System" or system.img or sys.img... can't remember. Then it stayed there... for about 2 1/2 - 3 hours. I knew after about 10-15 mins, something was up, but I let it be. Anyway, at about the 3 hour mark, I tried picking up my laptop (was gonna do some searching and see how long this should take, and what to do if it hangs) and I accidentally disconnected the little bastard in the process. Said Flash failed. I cursed. A few times actually.
So, I calmed a bit. Picked the phone up and hit power. I see this:
AP FastBoot Flash Mode (S) (Flash Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
Which I found odd, since I know I had the battery fully charged before starting this whole fiasco. Figured, no big. I plugged it back into the USB port and waited... and waited...apparently it doesn't charge when its stuck like this.
Decided to try using the wall-wart charger (Micro USB joint from my girlfriends old LG phone.) Must be wired differently, because when I turn it off, plug it in there, and turn it on I get
AP FastBoot Flash Mode (S) (Flash Failure)
0A.61
Battery OK
Ok to Program
Connect USB
Data Cable
So I figure "Aces!" and I go searching for another rom to flash. I tried:
the .893 version here http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html ... no good
The Minimal jammy here: Download DroidBionic/unroot/DroidBionicUnroot.zip at DownloadAndroidROM.com ... No Good
and one or two more, all same result.
Quick breakdown of what happened with each of them:
First problem, RSD Lite wouldn't recognize the phone when it had the "Battery Low" message, So I had to turn it off, plug into the wall wart, turn it on, leave it on, disconnect it, and connect it to the USB port. Then RSD Lite picked it up.
Decompress the archive containing the ROM, and flash it. Problem was it would turn the phone off, and reboot it, and when it rebooted flashing would fail again, since it would give the battery low message. Found a workaround for that: when it went to reboot, I disconnect it from the usb cable as it was off (mid re-boot), then make sure its off and connect it to the wall wart. I would get the "OK to Program" readout and plug it back into the USB cable, and RSD Lite would continue. It would get to the system flashing step for each of the ROMS and just chill out there for a bit, maybe taking in the scenery or grabbing a leisurely nap, I don't know, but it sure as hell wasn't installing that's for sure. But After it hung, sometimes it would fail on it's own, or after I go tired of waiting 2+ hours and disconnected it (figured, hey it's bricked already, what am I gonna turn it into a cinderblock next?)
Only thing is, when each of the ROMs failed, I'd get this kind of nonsense:
AP FastBoot Flash Mode (S) (Boot Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG OTV (CG: System): Invalid SP Data
Invalid CG Version (CG: System)
Invalid CG OTV (CG: System)
Now, I have no idea what CG is, besides my initials, and I didn't think the phone was calling me an invalid, so I'm completely baffled and confused.
Any pointers here? I see people were able to get this very issue resolved, however everyone that I found with success attributes it to a file that is now a dead link
Sometime in February (maybe March?) I rooted it, and about a month later installed some crap application that accidentally deleted some essential component- can't remember what, or why it happened, but that would be irrelevant, as I managed to Use RSD Lite and Flash what I thought was a stock ROM onto it.
It worked aces, except for one particular problem: It wouldn't perform the OTA updates. I would either get the notification that an update (.893) was available, I would download it, I would click to install it. Phone would power down, reboot and it would tell me something like "The Update Failed to Install". I also tried manually downloading and installing the update, but no good.
So I did some searching around, and found a couple of posts from people having the same issue - the common suggested diagnosis I saw was that if a rom was flashed based on a Leak, it would have trouble doing an OTA update. I figured since I had that first problem, and I flashed the "stock" ROM, I must have unknowingly used one based off of a leak. I figured, no big deal, Just find a real stock one and flash that sucker on there.
First thing I did was re-root the little bugger with the MotoFail method (originally used TehRoot, but when I went searching for it again, it said it was deprecated and to use MotoFail.) Next, figured I got to flash this thing.
So, I fired up my virtual machine running XP (Same thing I had to do the first go round - RSD Lite wouldn't work on my host Win 7 x64 Ultimate)
Went through the same steps I went through last time, this time with the .886 build in this thread: http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html
I'm guessing it must have been a bad download, or maybe something happened in the interim to the file while sitting on my HDD waiting to be used, I don't know. But It got all the way to something like "Step 13: Flashing System" or system.img or sys.img... can't remember. Then it stayed there... for about 2 1/2 - 3 hours. I knew after about 10-15 mins, something was up, but I let it be. Anyway, at about the 3 hour mark, I tried picking up my laptop (was gonna do some searching and see how long this should take, and what to do if it hangs) and I accidentally disconnected the little bastard in the process. Said Flash failed. I cursed. A few times actually.
So, I calmed a bit. Picked the phone up and hit power. I see this:
AP FastBoot Flash Mode (S) (Flash Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
Which I found odd, since I know I had the battery fully charged before starting this whole fiasco. Figured, no big. I plugged it back into the USB port and waited... and waited...apparently it doesn't charge when its stuck like this.
Decided to try using the wall-wart charger (Micro USB joint from my girlfriends old LG phone.) Must be wired differently, because when I turn it off, plug it in there, and turn it on I get
AP FastBoot Flash Mode (S) (Flash Failure)
0A.61
Battery OK
Ok to Program
Connect USB
Data Cable
So I figure "Aces!" and I go searching for another rom to flash. I tried:
the .893 version here http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html ... no good
The Minimal jammy here: Download DroidBionic/unroot/DroidBionicUnroot.zip at DownloadAndroidROM.com ... No Good
and one or two more, all same result.
Quick breakdown of what happened with each of them:
First problem, RSD Lite wouldn't recognize the phone when it had the "Battery Low" message, So I had to turn it off, plug into the wall wart, turn it on, leave it on, disconnect it, and connect it to the USB port. Then RSD Lite picked it up.
Decompress the archive containing the ROM, and flash it. Problem was it would turn the phone off, and reboot it, and when it rebooted flashing would fail again, since it would give the battery low message. Found a workaround for that: when it went to reboot, I disconnect it from the usb cable as it was off (mid re-boot), then make sure its off and connect it to the wall wart. I would get the "OK to Program" readout and plug it back into the USB cable, and RSD Lite would continue. It would get to the system flashing step for each of the ROMS and just chill out there for a bit, maybe taking in the scenery or grabbing a leisurely nap, I don't know, but it sure as hell wasn't installing that's for sure. But After it hung, sometimes it would fail on it's own, or after I go tired of waiting 2+ hours and disconnected it (figured, hey it's bricked already, what am I gonna turn it into a cinderblock next?)
Only thing is, when each of the ROMs failed, I'd get this kind of nonsense:
AP FastBoot Flash Mode (S) (Boot Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG OTV (CG: System): Invalid SP Data
Invalid CG Version (CG: System)
Invalid CG OTV (CG: System)
Now, I have no idea what CG is, besides my initials, and I didn't think the phone was calling me an invalid, so I'm completely baffled and confused.
Any pointers here? I see people were able to get this very issue resolved, however everyone that I found with success attributes it to a file that is now a dead link
