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!
Related
So my phone originally had the 2.2OTA, however my phone got stuck on the M logo when theming so i SBF'd it.
However now my version number says: 2.3.9. My assumption is that the SBF i used wasn't truly the OTA 2.2, and actually just the leaked 2.3.9 version
So from what i can see I'm looking at a few options to get back to the latest OTA version.
Either do this: http://www.droid-life.com/2010/09/21/how-to-return-droid-x-back-to-android-2-1/
and return to 2.1. Then get the 2.2OTA, and from there wait for the latest OTA 2.2.1
or
Flash this 2.3.15 leak. And from there manually flash the latest 2.2.1
http://androidforums.com/droid-x-all-things-root/179646-new-froyo-2-3-15-a.html
or
Flashing this 2.3.15 SBF
http://forum.xda-developers.com/showpost.php?p=8630797&postcount=17
So which is gonna be the safest route for me to go? Also will bootloader versions come into play at all? I've seen stuff saying downgrading back to 2.1 from the OTA 2.2 is not possible. So I'm wondering if i'm going to have problems because i was originally OTA 2.2 and now I'm 2.3.9 leaked.
My bootloader version says 30.03
Since you seem comfortable with SBF files, get the real 2.3.15 SBF (Android 2.2) and flash it. From there you should be able to OTA (wait or get the update.zip) your way to 2.3.340 (Android 2.2.1). That is the safest and easiest route.
alright thanks. That's the route i was looking to go.
I'm gonna install rsdlite 4.8, however do you know if i need to replace the .ini file like version 4.7? Or can i just install it and run as is?
rsdlite 4.8 is good to go out of the box, no updates like 4.7 needed. Just make sure you're also on the latest Motorola drivers. I'm at work, but off the top of my head they are 4.7.1 I think.
cool, thanks for the quick reply.
this will be my project tonight. Hopefully i don't lose everything when i SBF. I was quite pleased when i originally SBF'd and the only thing i had to do was re-root and re-theme
If I were you I would make Titanium Backups of everything you want to save! I've gotten stuck in bootloops before when doing SBFs, and then had to wipe data/cache to get out of it. Always backup important things before stuff like this!
oh most definitely. I got more backups than you can shake a stick at.
I had actually managed to restore a clockwork backup after i originally SBF'd. I'm kinda surprised i didn't run into any problems considering it was a backup of ver 2.3.15 with my theme.
Yeah, luckily enough there aren't enough changes to the kernel and how the system interacts with it to really mess up things when you restore a 2.3.15 nandroid on a 2.3.320/340 kernel. Still a bad idea, but at least it isn't catastrophic.
so out of curiosity i decided to try 928droid's "back to stock 2.3.15 odxed" and guess what.....it changed my version #
So i guess the SBF file i flashed wasn't the problem (double checked the file name and did it does indeed say 2.3.15) turns out the theme i had installed changed the version number.
It was either incognito....or more likely was this theme i put over the top of incognito: http://www.droidforums.net/forum/droid-x-hacks/99795-theme-black-juice-v3-stock-2-2-ota.html
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.
Hello, I just got a Motorola Milestone X. Its running on ACS alaska network. From reading I've done this phone appears to be the moto x but just not the vws branded phone? My question does anyone know of a way to root it and or any custom roms for it? Its filled with bloatware and no way to remove it and the stock rom is very ugly.
Ive tried z4root, superoot, androot and various other rooting guides that were supposed to work on the Moto X but all have failed me. Its running 2.2.1 and from what I gather this might be the problem?
Any help or info from anyone else familiar with this phone would be greatly appreciated as I hate it in its current stock form and would like to at least be able to remove the bloatware and crap I dont use even if there arent any custom roms for it. Thank you
Possible root
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
thank you very much for the information. I tried super one click but it would always lock up but maybe i'll give it another try. Is your phone running 2.2.1? Thanks again for the reply.
Inciner8Fire said:
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
Click to expand...
Click to collapse
I must have used a older version of SuperOneClick before. This one you linked worked with no problems at all. Thank you so much!
No prob, glad it worked for ya.
Thanks for the post. I was going through the same frustrations with my new ACS Milestone X. I see now that there is a new version of SuperOneClick ... anybody else trying to make this work, make sure you use v1.7.
So back to JDinAZ74's second question ... now that we've rooted are there custom roms for our CDMA version of this phone? I see tons of roms but none that I've noticed specify GSM or CDMA, which usually means it's GSM. Anybody know for sure?
the dx is on verizon, so its all cdma. i not sure it would matter though...
Yeah I'm not sure it matters either ... I know on my HTC Desire it mattered. If I flashed it with a GSM rom it would not boot.
Okay so somewhat unrelated ... i've got bootstrap installed and was able to do a rom backup via clockwork recovery. Is there a way to boot into recovery from the device being off? I tried every combination of buttons while pressing the on button but nothing works. I've looked all over the forum (and googled) but can't find anything.
I want to start installing custom roms but am affraid of something going wrong and me not being able to reflash my backup.
Then again maybe I'm just confused because I'm coming from a Desire which I've discovered Motorola and HTC modding differs significantly.
Im still looking for roms as well and kinda afraid to just start trying things like you said. If you come across anything that works let me know and ill do the same.
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Wouldn't the SBf only work on a Droid x?
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Fantastic! Thank you.
I don't know that they could do an sbf being on a non Verizon carrier. The sbf files out are all for Verizon. If you do screw up your phone you would have to take it into the store and have them sbf it. And they might not. I think you guys just need to be a little careful. Unless you can find an sbf file from your carrier. Try apex, rubix, or liberty roms for flashing. All the roms are cdma. Good luck and be careful.
Sent from my DROIDX using XDA App
The milestone x uses the same RSA key for its bootloader as the original Droid X. You CAN flash a Verizon SBF into it and it will work, HOWEVER, it will NO LONGER work with your carrier. It is also important to note that ANY SBF will overwrite the baseband AND the baseband configuration (unless specifically noted NOT to do so) rendering the phone useless, requiring re-programming, which for the voice part is no big deal, but to get EVDo working again you'll need to edit some non-user accessible parameters with QPST and what not to get it to connect back to the non verizon carrier.
What you CAN do with this phone is non-baseband patching updates/roms. If you've got a Milestone X you're not on verizon, so you're not able to use the leaked SBF's and what not, which removes a decent safety net. So flash with caution. If your carrier is small enough they are likely to re-sbf your phone for you if you brick it.
One last word of caution.. Verizon's DX on leaked GB's updates the BL to a newer version than is on the Milestone X. This will turn your phone into a Droid X, with no ability to go backwards until the same BL is available on the Milestone X.
In short, we non VZW DX owners have a lot less fun..
Bollocks to that.
really wish I knew if someone had tried, I really want to try that leaked gingerbread.
went ahead and took the plunge with... SUCCESS. I installed Liberty 2.0.1 and nothing went wrong, you just got to be more careful than others who have the sbf backup.
Went to ACS today because i'm considering this phone, ACS is partnering with Verison(GSM), and GCI is partnering with Sprint (CDMA).
Just incase it's not clear i'm sure roms for Verizon will work for ACS and roms for sprint should work with GCI.
Double check incase i have the two "bands mixed up" i know i have the carrier relationships right.
Does anyone know if we can overclock with out romming?
I tried droid overclock a few times which always sent the phone into a boot loop. Id have to pull the battery and do a factory reset to get it running again.
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