Bootloader 30.04 ER:A5, 70, 70, 00, 00 Mem_Map Blank Servc Req'd

[Charlie03]

So this previous week was a true test of patience.
I flashed an incorrect .sbf (I believe it was the droid x 2.1 full sbf) trying to recover my droid that was fully bricked. No recovery screen at all (no clockwork and no stock recovery) due to flashing the incorrect sbf through rsd lite (4.7 w/ patch). Never downgrade from 2.2.1 2.3.340 to 2.1. YOU WILL SUFFER! When the stress was toomuchi brought the phone to a corporate dealer and pretended I had no idea what was wrong with it. Yes I do feel guilty.... but since the service tecs were unable to even get intothe recovery screen they were none the wiser. They gave me a new droidx and I promised I was nevergoing to rom again.... well what do you know, by that next evening I relapse and return to active flashaholic mode. I flashed a new market theme on apex 1.4.1 and again stuck at the honeycomb boot. (Of course my modifying addiction displayed with cynicism at its best. So again im unable to get to clockwork and failing to load signature verification with an update.zip of apex 1.4.1 I had on the root of the sd I was having de ja vi. I plug this poor thing into pc and ran rsdlite under command prompt to flash sbf. Just as im jumping with joy when I see the flash process actually working and the re-enumeration was a success. I see the o-so-horrifying ER: A5, 70, 70, 00, 1F (the final 2 digits vary depending whether its pouted into your pc or not, if not it reads 00 for the last two. Im pretty sure) so I am with no stock recovery screen what so ever just the bootloader screen. I learned out that I flashed the incorrect sbf again. From what I believe it was the same 2.1 full sbf I did the first time. I know, rediculous right? Ii ended flashing the correct one which took me so long to come across due to very poor download speed and numerous issues with damn red lite. It is very picky on windows7. So I flashed the correct 2.2.1 full sbf. And miraculously I see the most beautiful Motorola boot logo. I think I actually kissed the logo for about 20 seconds. So I sit on my rooted apex1.4.1 droidx ha typing up some expierience that may well help others. I may post the full sbf I flashed to a download linksometime when I get home.
Lesson: control your flashaholic behaviors/ know what the **** your doing!

 

[dvader]

These problems are all avoidable if you do some light reading on the subject.
I feel like if you jump out in front of a bus, then you should get what's coming to you.

 

[Charlie03]

Wellll, maybe if life came with 25 year warranty I would. I've been in and around rooting and flashing since the original droid came out. This half-rooted temporary deal is the thing thars causing frustration. Not having a full root on the x makes things just a tid bit different. Ii thank all the developers and android wizzes for their knowledge and experience to share. I just struggle it seems to grab the concept behind full sbf's and system onlys, and why people post links of the same file but have different checksums. Well I know I wad in a pretty rare state of btickage and there was limited information. So I hope that if there is someone with this same issue, I can help them!

 

[wildman]

Wellll, maybe if life came with 25 year warranty I would. I've been in and around rooting and flashing since the original droid came out. This half-rooted temporary deal is the thing thars causing frustration. Not having a full root on the x makes things just a tid bit different. Ii thank all the developers and android wizzes for their knowledge and experience to share. I just struggle it seems to grab the concept behind full sbf's and system onlys, and why people post links of the same file but have different checksums. Well I know I wad in a pretty rare state of btickage and there was limited information. So I hope that if there is someone with this same issue, I can help them!

This is why I do not download from mirror sites or file sharing sites for files as important as a SBF or Root, if I cant get it from the developer then I guess I dont need it.... I am not going to risk a corrupt or modified version of something that once it is installed I have no control of what is going on in the background.

 

[upgradde]

This is why I do not download from mirror sites or file sharing sites for files as important as a SBF or Root, if I cant get it from the developer then I guess I dont need it.... I am not going to risk a corrupt or modified version of something that once it is installed I have no control of what is going on in the background.

Wait....was the full SPF on the sticky of this forum legit? That's the one I have loaded on my comp, just in case. I also have the one From Team Black Hat loaded onto my SD card if i can do it that way? Am I good you think?

 

[ultravisitor]

Wait....was the full SPF on the sticky of this forum legit? That's the one I have loaded on my comp, just in case.

I've used it; it's fine.

 

[wildman]

Wait....was the full SPF on the sticky of this forum legit? That's the one I have loaded on my comp, just in case. I also have the one From Team Black Hat loaded onto my SD card if i can do it that way? Am I good you think?

No the one posted here is fine, that's what I use but I was responding to the user reporting a file not matching the valid sum size.

I just struggle it seems to grab the concept behind full sbf's and system onlys, and why people post links of the same file but have different checksums.

 

[upgradde]

LOL cool. Thanks man.

 

[JkdJedi]

These problems are all avoidable if you do some light reading on the subject.
I feel like if you jump out in front of a bus, then you should get what's coming to you.

LOVE IT!

 

[Charlie03]

Yeah the .sbf i used was the one stickied here on androidcentral. It did the trick for me.

 

[wildman]

Glad that you got it resolved..

 

[Charlie03]

Thanks wildman, I certainly learned alot of useful information in the process. In a way Im kind of glad I was irresponsible at the time, I wouldn't of learned anything about rsd lite and sbf's. Although I don't wish it upon anyone to learn the way I do.

 

[Silverag08]

Hey Charlie03,
I just ran into this problem tonight and was wondering if you wouldn't mind outlining for me how you dug yourself out.. I miss my OG Droid things were never this difficult with it.

 

[bkcugs24]

Re: Bootloader 30.04 ER:A5, 70, 70, 00, 00 Mem_Map Blank Servc Re

So this previous week was a true test of patience.
I flashed an incorrect .sbf (I believe it was the droid x 2.1 full sbf) trying to recover my droid that was fully bricked. No recovery screen at all (no clockwork and no stock recovery) due to flashing the incorrect sbf through rsd lite (4.7 w/ patch). Never downgrade from 2.2.1 2.3.340 to 2.1. YOU WILL SUFFER! When the stress was toomuchi brought the phone to a corporate dealer and pretended I had no idea what was wrong with it. Yes I do feel guilty.... but since the service tecs were unable to even get intothe recovery screen they were none the wiser. They gave me a new droidx and I promised I was nevergoing to rom again.... well what do you know, by that next evening I relapse and return to active flashaholic mode. I flashed a new market theme on apex 1.4.1 and again stuck at the honeycomb boot. (Of course my modifying addiction displayed with cynicism at its best. So again im unable to get to clockwork and failing to load signature verification with an update.zip of apex 1.4.1 I had on the root of the sd I was having de ja vi. I plug this poor thing into pc and ran rsdlite under command prompt to flash sbf. Just as im jumping with joy when I see the flash process actually working and the re-enumeration was a success. I see the o-so-horrifying ER: A5, 70, 70, 00, 1F (the final 2 digits vary depending whether its pouted into your pc or not, if not it reads 00 for the last two. Im pretty sure) so I am with no stock recovery screen what so ever just the bootloader screen. I learned out that I flashed the incorrect sbf again. From what I believe it was the same 2.1 full sbf I did the first time. I know, rediculous right? Ii ended flashing the correct one which took me so long to come across due to very poor download speed and numerous issues with damn red lite. It is very picky on windows7. So I flashed the correct 2.2.1 full sbf. And miraculously I see the most beautiful Motorola boot logo. I think I actually kissed the logo for about 20 seconds. So I sit on my rooted apex1.4.1 droidx ha typing up some expierience that may well help others. I may post the full sbf I flashed to a download linksometime when I get home.
Lesson: control your flashaholic behaviors/ know what the **** your doing!

I have the MEM_MAP blank problem that seems to be exactly what you had. Cant get out of the same bootloader. Where can I find the correct SBF to flash via RSDlite? preferably the one you also used.

Thanks for your help and great thread.

 

[vampireizzy00]

Omg im stuck with the same problem myself. could u share the link from where u got the sbf. that worked for you. i would really really appreciate it! im quite desperate here. :S

 

[sd_shadow]

'MEM_MAP blank' means SBF was incompatible
the latest system version 2.3.4/4.5.621 can not be downgraded
4.5.621 sbf can be found www.1kds.tk
full name 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf
download and verify md5: 06bbf7ee86c0ed64654e14bcb84c4aed
[How to] Verify that your download is complete with MD5/SHA-1 Hash Checksums
download rsd lite
How to use RSD Lite
if you want to root
DX (MB810) Root 2.3.4/4.5.621

more links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs

 

[Mike Green_49]

https://sites.google.com/site/motosbf/droid-x-sbf-files