Database Users

OH NO! Another messed up Droid X

A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?

check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html

After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.

Let us know what you did fix your situation.
Sent from my DROIDX using XDA App

Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/

It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!

My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community

Any Success @ SBF 2.2.2 Cellular South Milestone X (FROYO)?

As the title asks...
Has anyone been able to SBF back to 2.2.2 Froyo from the OTA update? If so, please advise all details. Thanks.
Much of the software conveniences I use, are better working in 2.2.2 especially screen lockers, unlockers, blockers, and Wireless Tethering.
W/ 2.3.5, I change the hotspot info to that of Wireless-Tether's and use it, but that's annoying...
Feels like two different setups.

i tried once... didn't go so well, ended with warranty replacement.
downloaded sbf that indicated it was for cell south(cspire) from here. everything appeared to go just fine. until the phone rebooted. gave me a message that said something like MEM_BLANK or something similar. i will admit that i am not very proficient with motorola's yet, and may have done something wrong, but i followed the steps that i found posted here on xda. if you find any more information i would love to hear it.

I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.

Rocheforte said:
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Click to expand...
Click to collapse
exactly. i came to the same conclusion. makes me wonder why the motorola roms aren't more like the htc roms where they are not carrier specific.
edit: did you manage to get past the MEM_BLANK and SERVICE REQ'D errors on your own? and if so, how?

No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.

Rocheforte said:
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Click to expand...
Click to collapse
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.

ngholson said:
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
Click to expand...
Click to collapse
Yeah, I had used the Droid 2 bootstrapper at that point. Has anyone tried using the Verizon Droid X sbf's since apparently they are supposed to be very similar to the Milestone X's?
Sent from my Milestone X using xda premium

[Q] Droid X Bricked

So a Droid X is stuck at the dreaded "mem_map blank" bootloader screen. Everywhere I can find says its bricked, but there seems to be some hope. The DX was running the most recent OTA from Verizon, but was rooted before the update. After the update it still had SU, but it wasn't functional.
On another DX, I had the same issue. I used the 2.3.3 System Version 4.5.605 SBF and took it back to stock, rerooted, and installed a custom ROM just fine. This time things blew up.
The error I get after I flash ANY SBF is:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Click to expand...
Click to collapse
I know there's rules against going from the OTA to 2.2/2.1 or something, but from 2.3 to 2.3? Anyway, any help is GREATLY appreciated. Is there any way to fix it?
EDIT: I'm getting "Unable to retrieve RAM Downloader for Flash Bootloader checksum." at the end of my SBF.

The person that owned the Droid X told me they didn't take the OTA. I believed them. Lesson learned.
I used the most recent SBF I could find (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-VERIZON.sbf) and it came right out of the bootloader.

I am getting the same error when trying to SBF to Android 2.3.3 System Version 4.5.605 (VRZ_MB810_4.5.605_1FF_01). The user told me they did not take the OTA update.
Bootloader 30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
I am downloading the newest SBF as suggested by iamz3r0. Will report my findings.
---------- Post added at 10:19 AM ---------- Previous post was at 09:39 AM ----------
Well, my reason for wanting to SBF the user's Droid X was because he reported to me that his phone was stuck at the Motorola Logo. I confirmed this and thought it would just be a simple SBF.
With the latest SBF (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-VERIZON.sbf) the flash works but the phone gets stuck at the Motorola logo again.
I do believe the original error was in regards to the OTA update the user took, but my issue of the device being stuck at the Motorola logo must be due to a device problem.
I will try to flash a few more time just to make sure there wasn't any issues with the flash of the newer sbf.

Boot into recovery and do a factory reset.

I'm getting this error too (stupid me for not reading enough about the new OTA update before trying to SBF) but now the phone won't charge and it says the battery is low and it cannot connect.
If i plug the phone into the wall, it won't charge, it just goes straight to the bootloader screen and this error message, so i can't sbf back to the right version.
Any idea how to get it to take a charge?

find someone else with an X to charge it for you, or get a Verizon store to charge it for you.
Sent from my Transformer Prime TF201 using Tapatalk 2

I was at the same point you were my friend flashed the ntelos rom then I sbfed without knowing this and bricked it but he sbfed back to 1FF–p3a_shadow_cdma etc.... And it booted right up btw if you stuck at Motorola logo just do a factory reset and it should boot plz thanks
Sent from my DROIDX using xda premium

Attempting to fix a friends VZW Droid 2...

Hello all,
So I have in my hands a Droid 2 on VZW which is currently not working. All I know is this:
It was rooted when my friend bought it. He received a notification for an update sometime today, installed it, and now it seems to only boot to the bootloader.
The screen basically just says:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
So, I've never used a Motorola phone before, and I'm not sure where to start. Can anyone guide me with a little hand holding to get this thing working for him again?
Thanks all.

As an update. Read around a bit, tried clearing cache, then did a full wipe, and it still ends up at the same screen each time.

did you try, rerunning the update, from recovery
not sure where it's stored or if it would be gone, from data wipe
if that doesn't work, take to verizon store, if that is an option
there is a fix for the, Droid 2 Global, here [How-to]unbricking downgraded 629 & root normal function OTA 629
someone I'm sure will, use the method, for fix for the D2
they will need a copy of the update

looks like the update is saved in the cache
so if you wipe cache or data, it should be gone
so it's verizon, wait for SBF (official or repacked)
or update failed, maybe just use old SBF 2.3.20,SBF Mirror
Tutorial/Walkthrough for flashing an .sbf to Droid 2 (rooting/factory restore)
Sbf will ether work, or bootloader will change to MEM-MAP Blank error

Is it advisable to try the old sbf, or will that be bricking his phone permanently?
Thanks!

sbf will brick phone, till correct sbf is found
Sent from my DROID X2 using xda premium

xiton said:
Hey shadow,
Did the newest sbf ever come out? I'm still trying to fix this VZW Droid 2
Click to expand...
Click to collapse
no SBF yet
does phone still say
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
if so can you get to android recovery?
Booting into Recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the lock/power button.
Once you see a warning sign with an android robot appear, press Volume Up and Down buttons.
Click to expand...
Click to collapse
DROID Wiki.
maybe you can install update, unlikely but worth a try, need to be able to put it on sd card, and rename update.zip
then select apply sdcard:update.zip in android recovery
maybe you'll get lucky

xiton said:
Hey sd_shadow,
I see the sbf file finally came out for me to fix my friends phone. I have one problem though. The battery is almost dead and I can't get the phone to charge. What can I do to get it to charge?
Thanks!
Click to expand...
Click to collapse
safest way is to buy a $5 spare battery charger like http://www.amazon.com/MOTOROLA-Droi..._1_6?s=wireless&ie=UTF8&qid=1338740850&sr=1-6
take to verizon store to charge battery,
or use the MacGyver method but I do not recommend, because you can fry your phone
edit: changed link

[Q] I've Bricked another one!

Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA

I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks

Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2

yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.

I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.

Sbf

Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium