Separate names with a comma.
Discussion in 'Droid Bionic Hacks' started by SamuriHL, Jul 2, 2012.
had the same issue... boot into fastboot mode and itll take off
Another issue. Anyone got stuck on "writing preinstall"? Not sure what to do here. It's been on this step for 10 minutes and I'm freaked that if I unplug the phone now it will be bricked. I did have SafeStrap installed on my device, could that be killing the process? Should I wait for it to time out?
Just wait. Did the same thing to me also
Patience is a virtue.
O.K. I had a failure to write cdt.bin, logo.bin and ebr even though they were right there in the directory with all the other files.
This resulted in a general failure.
I got stuck on the dual core screen, pulled the battery and rebooted into recovery, sideloaded .902, side loaded.905. Both loaded fine.
Tried to load the .230 file and got a signature failure - abort.
So I rebooted and now seem to be on 230. I have no idea whether or not it worked, but handset resports that it did.
Very strange issues some of you are having with flashing. I'm wondering if it's a USB port and/or cable issue that's causing some weird issues. I've not had any problems and lots of others have used it successfully, as well. Really not sure where these differences in experience are coming from.
Yes, I cannot imagine why it chose not to write three files which were present in the directory.
The biggest issue I face now is vetting the various upgrade files floating around.
They came so fast for a while and I dropped off line for several weeks.
Now I have a variety of "blur" files on my HD that are likely useless at best and dangerous at worst.
Failed, now stuck on Fastboot screen
Help please!!! My install failed after waiting for an hour on the 'writing preinstall step' and now I can only get to the fastboot screen once I do a battery pull. What can I do to unbrick this phone? Thank you.
You will now need to use RSD Lite and the full 902 FXZ to restore your phone. This will wipe your data.
So I've gone through everything and as my phone is trying to loud up the new leak I keep getting the "Unfortunately the process com.android.phone has stopped" message along with 4 or 5 other different process stopped messages after that. Any tips on what to do now? I've rebooted and gone through the entire process multiple times now.
I've seen other people report that kind of issue even not using this procedure. I dot not know how to fix it. Have you wiped the cache?