Similar issue
Hello. I'm having a very similar issue. My post is here:
http://xdaforums.com/showthread.php?p=23921408#post23921408
but I will copy pasta it at the end of this post because I'm cool like that.
I have a fully stock Droid R2D2 that I never screwed with, I tried to run the OTA update, and now I am stuck at the boot loader screen described below. After reading this entire thread, am I correct to think that if I copy this file:
http://www.mydroidworld.com/topic/4...present-droid-2-2320-triple-threat/#post37316 that you mentioned, to my sd card and then do the hold-x while booting and go to the recovery bit, I will be able to restore my device?
My original Post:
Hello! I have been searching through the forums and have found several similar issues to mine, but I have some questions/concerns as to whether the solutions mentioned apply to exactly my situation.
I have a Motorola Droid R2D2 edition. I Did not do anything to it. I did not root, I did not side load anything, I did not try to roll back anything. I was minding my own business and received a message regarding a firmware update OTA. I assumed this was going to fix the horrible behavior introduced by the previous OTA, (random reboots etc) So excitedly.. I let it do its thing.
Big Mistake...
I think THIS:
http://support.verizonwireless.com/p...droid_r2d2.pdf is the update I was installing.
Now it is stuck on a black boot loader screen. Here are my concerns about the other post.
1.) A similar problem was had with a normal Droid 2, but his boot loader was version D2.35 Mine says D2.37 Can I use the same tools that were mentioned here:
http://xdaforums.com/showthread.php?t=849658 ?
2.) My error code is different, his says Err:A5,70,00,1F Mine says A5,70,00,00,23
What does this code mean? These kinds of things intrigue me
3.) I do not have that mem_map message.
My screen looks exactly like this:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
Can I just do what the other guy did in the above mentioned post? Or do I have to do something else? I'd prefer not to take a 25 mile drive to the nearest Verizon store to beat them..err I mean.. ask them to re-flash it, if I can just do that myself.
P.S. Already tried a battery pull no luck :'(