lol my first sbf flashing problem. i tried flashing an old sbf, 2.2 i think, cuz... idk i wanted off of fission... 2.2.2? i think? to try tranquility, and so i got:
err:a5,70,70,00,1f
MEM_MAP Blank
Service Req'd
and then i tried the sbf for the latest update that every1 thinks is gingerbread but its not, and that just does a temp error and returns to that^^^
suggestions?
That was the error I got when the first day I brought my phone home and was playing with it lol.
Sounds like your system is jacked. Here is a link to get you to .340. SBF that baby back to the living.
RSD Lite has always made me nervous. Since back in my RAZR days hah. But you should hopefully be good afterwards.
yup it worked. then i went straight to updating it to the newest froyo with madden 2011
Nice
10 char
Related
I'll keep this short so I can get straight to the point. Was running Apex ROM on 2.3.15, and a new version is out for the OTA update that just came out, 2.3.40. Reverted back to stock everything, tried to apply the update.zip, and got an error that said "status 7." Did some reading, saw a suggestion to apply the clean Droid X image from 928droid.com. I did that, tried to update.zip, and it still wouldn't do it. I've cleared everything a couple times and keep getting the error.
So unless there's another route I can go to get the update applied (which I'd love to hear so I can avoid SBF'ing), it looks like I'll need to just SBF. Problem is, in the SBF guides I've seen, it says that the current SBF (the ~450MB one) will only work for the 30.03 bootloader, not 30.04... Well I have 30.04. So I really don't know what to do.
ANY help would be appreciated.
If you already have the 30.04 bootloader (refurb phone on 2.3.151?), you can use the system only SBF for 2.3.340.
It is a refurb that I just got with the 30.04 on 2.3.151. So I should just follow the instructions here as though I'm running the 2.3.20 leak even though I'm not?
Crap crap crap!
You can't use just the system only SBF for 340! No kernel means problems for you! Get your 2.3.151 back to bone stock and try Verizon's over the air update now that it's out. If that doesn't work I'm not sure where you go from where you are.
The OTA update doesn't work, it downloads it, goes to install it, then after getting about 1/4 of the way in it says it failed.
Try the 320 update.zip or the 320 full SBF from Team Black Hat, then do the system only SBF to 340. That should get you back to the right path.
Can you tell me where to get the 320 update.zip?
Right before the Status 7 error it says "Error in /cache/Blur_Version.2.3.15.MB810.Verizon.en.US.zip", if that matters to anyone reading.
You can look around the forums here or over at MDW, but I'm guessing all the links are long gone by now. The Team Black Hat app is a few bucks on the Market and has all the files you want, and to be honest it's worth it. Those guys do a lot for the community!
Wiped data and cache, then restored the backup from here - http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
After that I was able to update, no SBF's anywhere in the process.
Just thought I'd post because I've seen a handful of people having similar problems today.
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!
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
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
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