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
Related
ok so after the new ota update my phone was running slower so i flashed it back to VRZ_MB810_2.3.15_1FF_01.sbf or at least thought i did. well it says its finished in rsd lite but the phone is stuck on boot loader with error err:a5,70,70,00,00. Is there a rom i can use to flash to unbrick? would the vrz_a955_2.3.20_1ff_01.sbf work despite being for the d2? any help, ideas, or suggestions would be appreciated.
You must use the 2.3.32 sbf now, its on mydroidworld
thank you very much
since i cant post links just google "droid x 2.3.32 sbf" and its the 1st result
downloading now
ouch.. you went backwards. Never good to go backwards on a DX due to the locked bootloader. A full SBF of 2.3.340 may be your only hope. Unfortunately not available yet.. Is clockwork mod gone too? If not you can try the kernel/system updates that TBH just produced. Here is the link
mod edit from Sleuth
Thanks to mob87, I now understand that the 2.3.32 full SBF can be used. Once complete, install clockwork mod then flash the 4 TBH update.zip files (bootloader, kernel, system, baseband) from the above link to restore your phone to the full 2.3.340 OTA.
Whew. Nice to know we have a safety net on 3.2.340.
end mod edit
yup i am stuck at the bootloader screen
boatloader
30.04
err:a5,70,70,00,00
mem_map blank
service req'd
battery ok
ok to program
transer mode:
usb
this is all i see
im hoping this works
Droid X: 2.3.32 Full SBF
Team Black Hat does not normally release full sbf files, but today we have received permission to release one. Please do know, that this is not the normal operating procedure and will most likely not be repeated in the future.
and im in the middle of a snow storm and my net keeps going in and out, normally have 20 down and pulling .5 down right now so a hour to dl a simple 200mb file, life is great right now.
Sleuth255 said:
ouch.. you went backwards. Never good to go backwards on a DX due to the locked bootloader. A full SBF of 2.3.340 may be your only hope. Unfortunately not available yet.. Is clockwork mod gone too? If not you can try the kernel/system updates that TBH just produced. Here is the link
Click to expand...
Click to collapse
2.3.32 sbf works fine if you updated to the OTA so no need for a 2.3.340 sbf
got both downloading now, thank you for you help, now if only i could get some dl speed, lol, i hate snow.
so 2.3.340 would be pointless? the reason i ask is it only has 5 minutes left and the happy_holidays_from_tbh.zip has 27 minutes.
by the way you guys are great and i truly appreciate your help. i cant contribute much but i will give what i can. still a n00b and am learning more and more.
i see now that dl is done 2.3.340 is a update and i cant load the stupid phone so i cant get to bootstrap so im stuck for another 12 mintues till the 2.3.32.sbf is done.
2.3.32
sw update
in progress..
tick tock tick tock
at least i no longer have a brick got the M now and waiting the droid eye, there it is, back in biz. thanks for all the help from everyone. do i need to do anything else now?
You aren't on the official OTA now. If you want to be flash all the patches posted on mydroidworld
mob87 said:
2.3.32 sbf works fine if you updated to the OTA so no need for a 2.3.340 sbf
Click to expand...
Click to collapse
Good to know we have a safety net for 2.3.340. Previous post updated with method. Thx!
I have a droid x "obvious" after updating fission to 2.4 it was all jacked up and crazy. So I tried to use the sbf I used before to get the orginal fission which is.
sbf 2.3.15
Rsd says everything took, but it's stuck in a boot loop.
I'm on bootloader 30.03.
any advice/ help on how to get it out of the boot loop?
Pull your battery, and while powering back up hold the home key until the exclamation mark pops up, and then do a factory reset / wipe data. I get a boot loop every time I sbf and have to do that to get it to boot up.
alright got the explanation point... but how do i do the rest?
edit: found it! //hasn't looped back yet but still loading.... and during this edit it popped back up... THANK THE HELL OUT OF YOU!!!! haha
you really need to move from 2.3.15.
Verizon did.
Check team black hat for tons of sbf info . MyDroidWorld
don't you have to be on boot loader 30.04 to update to the latest?
The newer fission builds are based off of 2.3.34 so the components from .15 will cause issues. You need to upgrade to the current Verizon Kernel, Baseband, and Bootlaoder for Fission 2.4 to work properly. Check Angdroid's post here for the pieces.
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.
I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...
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
Has anyone figured out how to unbrick the droid 2 after that spring ota update from verizon?
I bought a few droid 2's online for almost nothing, attempting to revive them. But one was stuck in bootloop (couldn't see system properties before it rebooted) and wouldn't recover after a hard reset. I tried downgrading to 2.3.20 sbf (oops) which made me go to bootloader every time I started up. From then, I presumed that it received the new ota update already.... I tried using the new sbf's, but I still get error messages when powering up, which directs to bootloader after seeing the red m logo. The latest sbf released in may yields this:
Bootloader
D2.35
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
Maybe there is an ezsbf iso for the latest sbf? Anyways, I couldn't find it. I also tried to look for a valid bootloader sbf, but also to no avail...
Do you not know there is a search function? Look around.
Sent from my Droid Incredible using xda premium
It seems like a lot of other people are dealing with bricked droid 2's so far, no real fix yet unfortunately....
I'm 90% sure you can flash the 2.3.4 sbf
Sent from my Droid Incredible using xda premium
bobkameron said:
Has anyone figured out how to unbrick the droid 2 after that spring ota update from verizon?
I bought a few droid 2's online for almost nothing, attempting to revive them. But one was stuck in bootloop (couldn't see system properties before it rebooted) and wouldn't recover after a hard reset. I tried downgrading to 2.3.20 sbf (oops) which made me go to bootloader every time I started up. From then, I presumed that it received the new ota update already.... I tried using the new sbf's, but I still get error messages when powering up, which directs to bootloader after seeing the red m logo. The latest sbf released in may yields this:
Bootloader
D2.35
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
Maybe there is an ezsbf iso for the latest sbf? Anyways, I couldn't find it. I also tried to look for a valid bootloader sbf, but also to no avail...
Click to expand...
Click to collapse
This will unbrick it http://forum.xda-developers.com/showthread.php?t=1662091
enjoy. Also no root for 621 so enjoy stock
Still a no go unfortunately. I've been trying everything lately. I'm beginning to suspect some innate hardware fault as the cause of the bricked phone...