[Q] Droid X Bricked

[iamz3r0]

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

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.

 

[iamz3r0]

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.

 

[chrisgriner]

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.

 

[ylexot]

Boot into recovery and do a factory reset.

 

[tehashi]

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?

 

[ylexot]

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

 

[crazymonkey05]

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