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!
Related
I just want to remove the clockworkmod recovery to regular or stock recovery? I found the info for EVO 4g and it said not to use for anything else. Could someone, please tell me how to remove clockworkmod recovery and change it back to stock?
First- this applies if you are on 2.2 ota- not 2.1 or leaked 2.2
The easiest way now might be simply starting from scratch. The 2.2 ota sbf was released last night so you can use it to restore your phone to factory state. You will need the SBF and the latest version of RSDLite. Google...
VRZ_MB810_2.3.15_1FF_01
and something should come up. It is a large file. 430mb or so. (unzipped)
Also google rsdlite 4.8 it is not a very large file. I have never done the sbf before- but there is a guide on the droid x rootzwiki...
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
WARNING!!! make sure you are using the FULL SBF for 2.2! there is a sytem sbf for 2.2 that you don't want and there is the 2.1 sbf that you definitely don't want.
There may be just a simple uninstall- but I don't know how. I am a newb. Maybe a veteran will chime in with some help?
Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.
Cyc323 said:
Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.
Click to expand...
Click to collapse
Cool. Since I have never done it before- did you just follow the rootzwiki guide? And was it pretty straight forward? And- how long once you actually started RSDLite did the process take (assuming you used RSDL)?
thanks.
It wasn't painful. I used rsd lite 4.8. I searched for info on 4.8 but everything is on 4.7, even on rootzwiki . On 4.7 you are suppose to move an .ini file to another place. I saw a similar file but without the .ini extension. I thought maybe this is one of the improvement of 4.8 over 4.7. You also have to do the bootloader thing. The whole process took about less than 10 minutes. I was surprised that nothing on the phone was erased other than titanium backup. Wallpaper and Launchpro's settings were still intact.
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.
Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch
This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.
Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.
I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
bricked, verizon is overnighting one, should have a good clean one tomorrow.
SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.
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.
Sorry guys I searched and searched but the keywords are too common and giving results not suited for my situation.
I'm new at this so help is appreciated.
My Droid X is running 2.3.15MB810 Android 2.2 (came like this when I bought it)
I did 1 Click root (doroot)
I removed some bloatware, and froze some with Titanium Backup.
I've since unfrozen the bloatwares, and reinstall what else I could remember.
Now I can't do OTA update.
Now...which route should I take from here? What's the cleanest route to take taking future upgrades in mind without having to do multiple patches?
I have the the_gift.zip (Android 2.1?) Should I flash that sbf first?
Or...
Should I flash the 2.3.320 sbf, then update?
Flash the 2.3.15 sbf and then do the OTA.
the_gift.zip that I downloaded is 2.3.13 I believe. Where can I get 2.3.15?
thanks again
It's called the the_gift2.zip
Head here
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
Or you can go here
http://www.928droid.com/DroidX.htm
Download the "Droid X Official OTA 2.2 Froyo 2.3.15 "Back to Stock"" file (be sure to select the odexed version)
D.
thanks debaucher,
The first link gave the full SBF, but the 2nd link is only a 'patch' only I believe..just FYI for others.
Much!!!! appreciated. I try not to modify too much to avoid hassles like this since my original Droid. But even freezing bloatware causes problems. Sigh...
Is it possible/safe to go BACK from 2.3.320 leak to stock 2.3.15 if I use RSDLite to sbf?
I had to ask because according to this:
mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32
there is NO way to go back to 2.3.15. But what if now that I have the 2.3.15 full SBF?
Nope there is no way to go back. Once you are on 2.3.32 or 2.3.340 you can only go forward. However the sbf for 2.3.32 works on 2.3.340
thanks...making progress..thanks everyone.
Now I just SFBed I'm on 2.3.320..trying to patch to the 2.3.340 but the RSDLite application is telling me 'failed'
What to do? Rebooted and tried several times.
UPDATE:
Ok Windows 7 giving me too many problems. Moved to Windows XP and 2.3.340 SBF with RSDlite worked.
But now..why am i getting a 'roaming' indicator? Is there any separate baseband I need to load. I'm on BP_C_01.09.07P
Ok..finall update:
Had to reactivate the phone with *228..
All is good now..thanks for the file links guys.
Glad you got it all sorted out.
In your original post you did not mention being on 2.3.320 so I did not think to mention the warning (about going back to 2.3.15).
Also, there are a LOT of downloads on the 2nd link I gave you and the one I told you to download will put your phone (if not already at 2.3.320) back to 2.3.15 "stock" and odexed so you can get the ota update.
(I prefer the sbf method... but some have problems which is why I gave the 2nd link)
D.
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