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.
Here is the quick and dirty,
My dad has a Droid X. It was running Froyo rooted happily. It got updated to OTA GB (version in topic). It is now not rooted. Superuser.apk is still present. I cannot sbf through either windows or linux (no clue why, it always fails). I have tried the one click root that is supposed to work for the Droid 3 (and X running GB) - it thinks it worked but it is not rooted (verified few different ways).
Help please as I need to get my dad's droid x rooted. Need responses ASAP as they are going out of town in the morning.
You need to describe the exact steps you have taken and the exact error you get in order to get good help. Screenshots are great too.
They are back out of town now until Thanksgiving, but in windows I was getting a 0x7100 error. In linux I was getting a whole bunch of errors followed by a line saying flash failed.
A sbf shouldn't be effected by software version, as it just removes everything and starts over. I would say it was an error in setup for the sbf. Since the D3 method failed aswell, it seems that the phone isn't getting the message from the computer. But that's my two cents. You really just need to try again with the sbf.
Dispatched at the Speed of Light from my XOOM
I tried SBF from both linux and windows MANY times. Same with D3 root method. ADB works like a champ though......
Did you do a factory reset before attempting to sbf? Since there seems to be a problem with removing GB from the phone, maybe there's some error on that system that's effecting rsd's process.
Transmitted from Droid X
Tried the method on rootzwiki? I don't think I can post links yet but I had the TBH 2 part gb on my phone but I messed up and did the recent ota update and lost root.
Found this method from following a droid life link. Also a way to get rid of the old SU using adb shell if it doesn't root properly on the DX ( which happened to me)
Sent from my DROIDX using XDA App
I will look into those methods at Thanksgiving when I get another shot at that phone.
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
Hello again
So I made the mistake of accepting the .621 update after a ROM flash gone bad.
I've found the method to get root back but no matter what I do I can't get 3G back. I called Verizon, I reflashed, etc.
I keep seeing people saying not to use RSD Lite because it gets rid of a "15p" whatever that is. Maybe I got rid of that by accident? Is there some way I can put it back?
By the way, my system is 100% Linux. If you could tell me a way that's 100% Linux, I'd be grateful, otherwise I have to do it at work which I don't like.
You've SBFed to .621 with RSD Lite and have dialed activation?
Sent from my Galaxy Nexus using Tapatalk 2
Yes and yes. The SBF I used is "1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf"
EDIT: FWIW - I am unable to install the "Blur_Version.4.5.621.MB810.Verizon.en.US" zip file, the process always fails and tells me something is wrong with the zip file even though the md5 hash is correct...
Greetings,
I do not have your answer but I have the same problem. I sbf from stock .621 to the Milestone .604 then rooted and flashed the .621 stock. Tried the deodexed one as well. I deleted all things possible on this phone but all I get is voice and Verizon text. WIFI of course but no 3G.
I thought this might be because when I aquired the phone it had been flashed to Cricket. All the reading I've done indicated when you factory reset it all goes back to Verizon. My guess is the Cricket flash did something that permanently changed the phone. I wanted to copy the memory and compare it in hex editor with the memory from my fully functioinal droid X to compare. I need more research to know what memory locations to copy from using CDMA Workshop.
SH
My C&P from androidforums
The answer is...
My phone was "changed" by the Cricket flash. If a phone was Cricket and or had corrupted firmware you may loose the 3G connection.
I thought the Milestone flash was returning my phone to factory settings, most of you know of course it was not. Originally I did not sbf to .621. I did not know it was an option.
I thought we could no longer sbf in the Microsoft world with this phone at .621, wrong. I properly sbfed to .621 using information found here: SBF'd works but no data network?
RSD Lite 5.6 with the .621 sbf got me where I needed to be. I'd forgotten about the blue triangle where the 3g symbol lands after activation.
The link information woke me up as to what I was missing. The good news is if you have flashed to Cricket and wish to root with the Milestone method, you can keep the Cricket flash.
Many thanks to all the developers out there as well as, ylexot and Goose306 for your post on Droid x forums.
In defense of my own ineptitude this problem seems to be out there. I stumbled through many threads unanswered concerning this issue. If the sbf back to stock is here I missed it, perhaps it should be a sticky, or does it no longer matter for this aging/obsolete phone.
I do like experimenting with older "cheaper" technology.
Thanks again,
SH
3g fix
If you have a spare or old phone, try transferring your service to it, then back again. If still no 3g, try flashing milestone x .604 using linux method, I suggest using 1KDStaz_MX_4.5.604.iso (Milestone X 4.5.604 Gingerbread) live cd.
Hey guys, let me just preface this by saying that this was my first time trying to root, and that I am still very unfamiliar with many of the things involved in rooting. That said, here is my problem and almost exactly what I did to get there.
Alright, so I chose last night to be the night when I finally rooted my Droid 2. I had android 2.3.4 gingerbread .621 version when I started. I ran through the easy windows install instructions first on this page: well, since I can't post links, the page is http: //rootzwiki . com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/ (just remove the spaces in the web address). This didn't work because being the noob that I am, I didn't realize how to flash the .sbf file using rsd lite (now I know how to do that I guess, just a little too late).
So I said screw that, I will just run the cd. I downloaded the .iso, burned it to cd, booted to cd, and ran the program. The first time, I tried using the "Root Only" option. This ran, but didn't seem to work. So once that didn't work, I ran the first option that let you have the option to root (I have forgotten the exact wording). This worked and I got to the screen where I had to factory reset the phone. However, instead of being able to do this, I was stuck in bootloader with the error message "Err: A5,70,70,00,1F." So at this point I kind of realized that I was screwed so I tried to flash stock android 2.3.4 back to my phone using RSD Lite. I did this, and ended up changing the error message from the previously mentioned one to "Err:A5,70,70,00,00." So at this point I figured that I had a bad .sbf file and downloaded a new one and used RSD Lite to flash it. After I did this and it failed, I now am stuck in bootloader with a "Code Corrupt" message.
So basically, rooted or not, I would like to be able to use my phone again. I have seen in a couple places that the problem could be due to low battery, but I have switched to a fully charged one with no luck still.
This was my first attempt at rooting, and I am fully hating my first experience, but I'm already this far so I am willing to do the work to learn and get my phone back. If anyone can provide me with some pretty detailed instructions (remember, I'm a total noob and bricked my phone on something everyone else seems to have had no trouble with), that would be incredible.
Thank you in advance!
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http://droid.koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid. koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Yes, it is the droid 2.
bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid.koumakan. jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
xwsxlogan said:
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
Click to expand...
Click to collapse
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
bhigham said:
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
Click to expand...
Click to collapse
Yes, it was in the link listed before. The method had been cross posted on this site and on their site.
Ok, above the err message, what does the top line say?
bhigham said:
Ok, above the err message, what does the top line say?
Click to expand...
Click to collapse
The only screen that I can get reads as follows:
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Someone suggested that by holding up and power would bypass the "code corrupt" message, but that does not work. Also, the X+Power to try and wipe the phone clean doesn't work either.
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
bhigham said:
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
Click to expand...
Click to collapse
I did get an error message when trying to flash the stock 2.3.4 and it was something to do with RAM, but unfortunately this was 5AM this morning and I was beyond exhausted so I don't remember exactly.
I am using Windows 8 x64, but have access to XP, Vista, 7, and server if I need to.
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
bhigham said:
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
Click to expand...
Click to collapse
Alright, I will go ahead and get XP installed along with the drivers. Do you think that I should use a version previous to 2.3.4 then so that I have a better chance to root?
I am charging up my battery now using another phone, so I will start on it in a bit. Thank you again for answering all of my stupid questions and helping me out, I really appreciate you taking the time to do it.
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
bhigham said:
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
Click to expand...
Click to collapse
So you're saying that the only thing I will be able to flash is the 2.3.4?
xwsxlogan said:
So you're saying that the only thing I will be able to flash is the 2.3.4?
Click to expand...
Click to collapse
exactly
bhigham said:
exactly
Click to expand...
Click to collapse
Alright, I will try again tonight with a charged battery and XP and let you know how it goes.
This link here http://www.google.com/url?sa=t&sour...rICoBg&usg=AFQjCNHht4SU69VoDkBnMBCA_0uf9WYpyw. Will take you to the download for the correct sbf.
Correct sbf should read: 1ff-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_dr4-51-120117-release-keys-signed-Verizon-US.sbf.gz
Sent from my DROID2 using Tapatalk 2
Alright Update after flashing the .sbf file that was given in the previous post.
I used XP, running RSD Lite 5.6, with Motorola drivers installed. I charged a second battery up to around 70% or so to use during the process. I also changed USB cords from the previous one that I was using. I loaded the .sbf into RSD Lite, started it, and it ran flawlessly, skipping right over the RAM step in which it failed last night. Had to remove the battery and reinstall to do the manual reboot, and all of my phone settings were exactly as I had left them when I started. I had to dial *228 +1 to get the phone back on the network, but that was no problem.
So after all of this, I'm back to where I started last night haha. Special thanks to bhigham for all of the support and walking me through this today and also slogar25 for confirming that I had downloaded the right .sbf file.
So I guess my problem is solved...until I try and root it again!
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
bhigham said:
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
Click to expand...
Click to collapse
Yep, I've noticed you have been following the cross post on this site for the methods that I tried last night when I really didn't have a clue what I was doing. Do you think that I should just try the CD method again? I mean worst case I would do the same thing I did last night, but now I know how to flash it back to the stock 2.3.4. I don't mind wiping my phone, but after it survived everything I did last night, I feel more attached to my data haha.
Also, how do I mark this post as solved?