Database Users

err:a5,70,70,00,00 for droid x

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!

Question about restoring back to 2.2 with SBF

Ok, I flashed my DX with an official sbf file (VRZ_MB810_2.3.15_1FF_01.sbf), and the Result said PASS when it completed...but then after rebooting, it just went into the Bootloader. If I restart the phone again, either with the power button or pulling the battery, it just goes back to the Bootloader. Anyone have any ideas? I saw a recommendation on another site to re-flash it to fix this problem, so I'm going to try that to see if it helps, but I wanted to see if anyone has seen this or heard of this and has any suggestions.

Did you have a custom ROM installed before doing this? If so, it may have been based on the .320 leak or .340 OTA, which has a newer bootloader and prevents downgrading the VZW ROM.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.

Yeah, ignore this...I had OTA 2.3, and didn't realize I couldn't revert back to 2.2 (still getting used to Android). I got a copy of the 2.3 sbf from someone on droidxforums and I'm all set now, thanks anyways!

[Q] Droid x stuck on a loop at boot

I downloaded rom manager and bootstrap on my droid x. I downloaded flyx rom and then after it was suppose to apply it after it booted, it became stuck on the logo, going from the "droid to red eye" over and over until I pull the battery. So every time I turn it on it does the same thing. I then tried to wipe my phone by putting it into recovery mode. It says can't open/cache/recovery/command. I tried to figure out the rsdlite solution but I couldn't figure out or find a good explanation on how to use it. My bootloader is 30.04. If there is an answer to this in this forum any where please point me to it.

flyx is an ancient rom for older version of android.
if doing a factory reset doesnt help, i suggest sbf. instructions here http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2

Ok thanks, I thought I knew what I was doing but i'm pretty positive i failed ...I'll try this out then.

you're welcome. if you need any help with sbf or anything, dont hesitate to ask.

[Q] Bricked my Dx

i used bootstrapper to go back to the first back up i made which was the day i got it out the box. well i tryed to update the phone but it said it failed the install . so I said screw it and tryed to go back to the back up i just made with my custom rom i had been useing. well tahts when it all went to crap and now im stuck on the M logo and nothing happens. when it was done with the install of the back up it was still in clockwork and i hit reboot now and it just hung at the M logo any and all help is appreciated. I KNOW I SCREWED UP.

sbf the phone
put your x into bootloader mode and download rsd lite 4.9 for windows and then find the sbf file for the droid x and run rsd with the phone connected in bootloader mode with the sbf file you want. Its worked for me countless times. If you need help with how to put it in bootloader just google it or find it on the forums.

vampiricsoul said:
i used bootstrapper to go back to the first back up i made which was the day i got it out the box. well i tryed to update the phone but it said it failed the install . so I said screw it and tryed to go back to the back up i just made with my custom rom i had been useing. well tahts when it all went to crap and now im stuck on the M logo and nothing happens. when it was done with the install of the back up it was still in clockwork and i hit reboot now and it just hung at the M logo any and all help is appreciated. I KNOW I SCREWED UP.
Click to expand...
Click to collapse
here ya go
HERE

i got it into bootloader mode and its 30.04 but when i connect it to the cable rsd does not find it

ok i think i got it i had to run rsd lite in admin to find the phone. and now i am recovering all crap to my phone now. so question is can i update my phone to the lastest software out without messing it up amymore?

that depends on what you want.....
if you want other roms that arent stock froyo then you need to root all over again and install the roms using cwm, if you mean the OTA update to GB then yes go for it

[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