Would anyone be willing to explain the process completely with explanations of each step? I'm no noob to flashing but I am rough around the edges with Android.
I know there are guides already telling you how to do this but nothing written for 'pre-schoolers' like myself. It would be greatly appreciated.
Anyone up for it?
You want a guide because you can't handle following a guide?
You're pretty much gonna need to SBF Flash.
The fun part is that Motorola went down and did takedown notices on the SBF file pretty much everywhere.
The file you need is VRZ_MB810_1.13.6.2_1FF_01.sbf, which is 439 MB.
This seems like the best place to go:
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
Go to my thread CLICK
Go here - Return back to stock Android 2.1 and follow the instructions; its pretty simple.
Not Simple If you was on OTA 2.2 and you did try to get back to 2.1 sbf and brick your phone than use a 2.2 sbf to fix you will not be able to get back to 2.1.
I hope this help others that had the same problem i had, if is a way to do it i want to know i have a sbf 2.2 that i want to downgrade to 2.1 sbf or any other 2.1 in my situation.
Just so this is clear for other people visiting this thread -
You cannot downgrade to 2.1 if you took the 2.2 OTA*
*-Yet
LexusBrian400 said:
Just so this is clear for other people visiting this thread -
You cannot downgrade to 2.1 if you took the 2.2 OTA*
*-Yet
Click to expand...
Click to collapse
Quick question, I did the leaked 2.2 update some months back, but afterwards installed various custom ROMs. It is correct that I can still sbf back to 2.1 and then upgrade to OTA 2.2 via 'System Update'? I want to do this to update the baseband/radio kernel. As of now, current ROM offerings on the Droid X does not update the baseband unless you take the 2.2 OTA update correct? Thanks.
Step would be to:
SBF to 2.1 stock
Take 2.2 OTA update
Related
ok, so currently i am on flyx 2.2 based on teh leak. i would like to update to the official or a rom based off it. so i am assuming i have to sbf to 2.1, ota to 2.2, then flash a custom rom? do i have to sbf? i thought i read somewhere it would be possible to update leaked 2.2 to official with a custom rom. so yeah, just before i get started i wanted to make sure i was doing the right things and no unnecessary steps.
thanks for the help.
really? 56 views and no one knows? i know it's not the smartest question, and really i am just trying to confirm that i need to sbf to get to 2.2?
Can do it both ways but one you go official you can not flash back to 2.1.
I personally suggest flashing then getting the ota. After that apply which ever rom you like. I'm sure others have diffrent opinions.
Good luck either way
Sent from my DROIDX using XDA App
I haven't seen anyone else with this problem yet, so sorry about the new thread.
I have a Droid X that came straight from Verizon with 2.1, and was delivered a the day the official OTA for 2.2 went live. I always intended to run the leaked version of 2.3.15, but out of curiosity I went to the update page on the phone and asked it to check for an update just to see what it said.
It of course said that an update was available and then started a countdown saying it was going to begin the update momentarily. I hit the button to cancel the immediate update and then proceeded to go through all the steps that ended up with me having a phone running the leaked, rooted 2.3.15 version. It was supposed to be the DeOdexed version, but because I never formatted the system during the update the Odexed files remain. THAT I know how to fix.
My problem is that apparently because I "started" the OTA update process, Verizon wants to STILL update, even though I am already running the leaked 2.2. So multiple times a day now a little window pops up telling me "Download of update failed" and there is nothing I can do but back out of the window. I can't stop the update process anywhere, and if I go to the "Check for updates" window again it says "update in progress"
Anyone have any ideas short of clearing everything and starting all over again (which I will do if I have to, but this seems like an interesting unique problem that some of you might want to know about or tackle.)
Thank you
Look on your sdcard for a folder named "cache" and delete it. That MIGHT fix it. This is just a guess.
couldnt find it. any other ideas?
How about you SBF back to the 2.1 and then update to OTA 2.2 and check this thread out here for - OTA 2.2 Deodex'd
dr154 said:
How about you SBF back to the 2.1 and then update to OTA 2.2 and check this thread out here for - OTA 2.2 Deodex'd
Click to expand...
Click to collapse
so if i downloaded the 2.2 ota update in rom manager i can still sbf down to 2.1? just wanna make sure its ok before i brick my phone. lemme know thanks
Hey man, I'm completely a guide-following noob here, but I've got to tell you...I'm not sure you can do that.
I know the OTA changes the bootloader, which means if you sbf back then the efuse will be triggered and brick you. I'm not sure how far the update has to go before it makes that change. It doesn't sound like it's done anything on yours, but I'd ask some more knowledgeable people here first
tdrake2406 said:
so if i downloaded the 2.2 ota update in rom manager i can still sbf down to 2.1? just wanna make sure its ok before i brick my phone. lemme know thanks
Click to expand...
Click to collapse
If you have the official OTA 2.2 then no you can't downgrade back to 2.1 though the means of SBF because OTA 2.2 changes the kernel and baseband of the device which are not compatible with 2.1.
Question to everyone worried about receiving the OTA 2.2 and keeping the leaked 2.2, your getting better performance from the OTA 2.2 then the leaked 2.2 version, just my thought.
if only someone had the answer!!!!!
I've read some Android Forums but I can't seem to get my answers...
I need help updating to 2.3.340
I'm new to rooting and deoxeding my phone so I apologize If I have alot of questions....
I am currently on 2.3.15 , rooted and deoxed. My phone keeps prompting me to updating to 2.3.340.
Questions:
1. Should/Can I allow the update to take place automatically?
2. Will I lose my root access and will my phone not be deoxed?
3. Do I need to revert my phone back to stock then update automatically?
4. Is there a link on how to update to 2.3.340 when you have a rooted phone?
Any help is appreciated, thanks!
I'm also curious. I'm on the 2.2OTA-Rooted and my phone wants me to update.
1. Should/Can I allow the update to take place automatically? NO!!! not while it is as you have it now.
3. Do I need to revert my phone back to stock then update automatically? YES and be sure to uninstall any program related to rooting your phone before reverting to stock.
Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.
Not at all p3p... ask as many questions as you can... helps me out too..
I too would like to know what .Sbf and the other one stand for... lol I can't remember what it was...
So after we revert back to Stock.. (any link as to where to find the stock file?) Update automatically... then we follow the same procedures to re-root the phone?
purplem3pursuit said:
Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.
Click to expand...
Click to collapse
Hey wassup man? No ban stick here??
I also have the same questions...
m3n00b said:
Hey wassup man? No ban stick here??
I also have the same questions...
Click to expand...
Click to collapse
Nice to see great minds thinking alike The ban stick will rise again..
Bump to top to help myself and OP.
Any help is greatly appreciated.
Kapi187 said:
I've read some Android Forums but I can't seem to get my answers...
I need help updating to 2.3.340
I'm new to rooting and deoxeding my phone so I apologize If I have alot of questions....
I am currently on 2.3.15 , rooted and deoxed. My phone keeps prompting me to updating to 2.3.340.
Questions:
1. Should/Can I allow the update to take place automatically?
2. Will I lose my root access and will my phone not be deoxed?
3. Do I need to revert my phone back to stock then update automatically?
4. Is there a link on how to update to 2.3.340 when you have a rooted phone?
Any help is appreciated, thanks!
Click to expand...
Click to collapse
What I would do is SBF using the full .320 file and then do the .340 system only SBF and you will be on the most current version. Then download z4root its a one click root app which will give you root obviously. Then customize your phone to your liking.
joebob296 said:
What I would do is SBF using the full .320 file and then do the .340 system only SBF and you will be on the most current version. Then download z4root its a one click root app which will give you root obviously. Then customize your phone to your liking.
Click to expand...
Click to collapse
Um - if you are running 2.3.15 I would not recommend doing the sbf with the .320 file. I am just trying to be helpful -not a butt.
I would use the full sbf released for 2.3.15 which can be found at...
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
I just posted the guide I used to sbf here for another member...
http://forum.xda-developers.com/showthread.php?t=901934
Here is my understanding of your situation. You are getting prompted for the update. I THINK that even if you said yes and tried to run it - that you would just end up with an error - because the update checks your system to see if all the proper files are there and if they are not it will not run. I think.
So I think the best thing to do is sbf then take the update. You will loose root. and you will not be de-odexed. You will have to reroot. But like the other member said - get z4root (link in the other thread with the sbf instructions) and run it after you do the over the air.
I make no guarantees. Just sharing to the best of my knowledge.
thepolishguy said:
Um - if you are running 2.3.15 I would not recommend doing the sbf with the .320 file. I am just trying to be helpful -not a butt.
Click to expand...
Click to collapse
Flashing the .320 full SBF then the sys only .340 SBF would be the same as the .15 SBF to OTA. Six of one, half a dozen of the other.
purplem3pursuit said:
Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.
Click to expand...
Click to collapse
SBF stands for SmartBroker Data File, but that doesn't matter, it's simply a backup file. It's not necessary to upgrade to .340 unless you use custom ROMs, because anything made for .320/.340 isn't compatible with .15. The Nexus One doesn't have a system version because it's pure android; the android version is the system version. Other phones have a separate system version because the carriers feel the need to bog the phone down with bloatware and their custom launchers.
SBF files can be found here, and make sure you make a backup immediately after you're re-rooted, so you can just restore it to accept the next OTA.
mlclm said:
Flashing the .320 full SBF then the sys only .340 SBF would be the same as the .15 SBF to OTA. Six of one, half a dozen of the other.
SBF stands for SmartBroker Data File, but that doesn't matter, it's simply a backup file. It's not necessary to upgrade to .340 unless you use custom ROMs, because anything made for .320/.340 isn't compatible with .15. The Nexus One doesn't have a system version because it's pure android; the android version is the system version. Other phones have a separate system version because the carriers feel the need to bog the phone down with bloatware and their custom launchers.
SBF files can be found, and make sure you make a backup immediately after you're re-rooted, so you can just restore it to accept the next OTA.
Click to expand...
Click to collapse
Excellent information! So when utilizing my own backup (or the SBFs presented above), do I need to uninstall clockwork or root before going after the OTA? I am figuring the OTA isn't looking for that information but want to avoid the infamous brick situation at all costs.
No, you can leave everything installed. An SBF is similar to the factory reset disc that comes with computers; it formats everything and then installs the OS on a clean slate. An OTA won't check for root, but it does check for the bloatware. If any of it is missing/renamed, it won't install the update.
I am in between going to GB and staying where I am at.
My issue is that I am on a version of 2.2.1 Stock that I obtained through TBH around the holidays....file was literally called "happy holidays from TBH" however, this was the 2.3.320 version of the OTA update, not the 2.3.340 version that everyone seems to have.
So the real question is, can I jump straight from 2.3.320 to GB? OR do I need to flash to 2.3.34 since when I check for OTA updates the phone tells me that I am currently up to date.
If I flash to 2.3.34, then I should probably just go straight to gingerbread rooted. However, how would I get the OTA gingerbread when it comes out? Otherwise I would be right back where I am now in about a month or so.
I need to either update to the current froyo and wait for the OTA release of GB, or update to current froyo (2.2.34) and then update again to the new rooted 2.3.3? Right? can someone confirm?
PS. I already have the 2.3.340 .sbf file (445MB) and the 2.3.3 rooted file from p3droid so I am good to go there if necessary.
if you have the 2.3.340 sbf go ahead and flash it first just to be sure...then gingerbread the whole process will only take u 30 minutes its really not that big of a deal
I might as well go ahead and update to 2.3.340 however, I am now seeing on droidxforums that there is another version of 2.3.340 called maderstcok...can't post a link but here is a partial url: droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
The one that I have is from xda via the noobs guide (links to mydroidworld), so I trust that one more... however, this file is an update.zip, not an .sbf. So it could potentially be easier to do?
I would also like to know if it makes any difference if I use the 4.8 version of RSD lite versus 4.9
I am currently using the 4.7.1 drivers as well, pretty sure that that is right, but if there is a newer version, let me know
bump, just want a second opinion
Maderstckok will get you to where you need to be (2.3.340) I've used it 10+ times it's a great file. Then reboot, reroot, and flash GB.
SOCOM-HERO said:
I would also like to know if it makes any difference if I use the 4.8 version of RSD lite versus 4.9
I am currently using the 4.7.1 drivers as well, pretty sure that that is right, but if there is a newer version, let me know
Click to expand...
Click to collapse
I used 4.8. It'll work fine.
Sent from my DROIDX using XDA App
Ditto - 4.8 worked like a charm.
thanks guys, downloading now and will update to 2.3.34, gonna check around for some more ideas on whether or not to go ahead and get GB or wait for the OTA...i have seen some threads with issues with wireless tether, which is one of my reasons for rooting in the first place
so far so good, rooted with z4 after updating to 2.3.34 with maderstock....awesome file, best experience yet with the clockworkmod going to stock. Will update to GB tomorrow. Some of the deodexed roms look really good!
done...on GB, added the deodexed and got the stock BWC theme which is working great. Will maybe flash more custom roms later as they become more mature for GB. otherwise, freezing bulr apps.
I'm planning on putting CM7 on my Defy, but before I do that I want to make sure I can go back to the original OS.
The problem is, I can't find a full SBF for my current ROM version (T-Mobile US 34.4.9, build 3.4.2-107_JDN-9) to use if something goes wrong. My Defy came with this when I bought it, so presumably I can't downgrade to an Eclair SBF and update from there. I've found the two other official Froyo SBFs though: the 3.4.2-107_JDN-3 and 3.4.2-107_JDN-4 SBFs. I read that the -3 one is a dev build and doesn't easily update, so I don't want to use it. But I'm not so sure about the -4 SBF. Can I just flash that with RSD and then use an OTA update to get back to my -9 build back?
I'm very new to this (first post!) so please tell me if I'm wrong.
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
glycolysis said:
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
Click to expand...
Click to collapse
Can you help me revert back to stock, I look everywhere and nothing seems to work for me, try to flash 6.36 but I just get a black screen!
thanks!
Um, Me Too?
glycolysis said:
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
Click to expand...
Click to collapse
I know, this is a really old post, but I have the same exact situation (except I want to try CM10 not CM7) and want to make sure I can go back to my stock T-Moble Froyo if something goes wrong. Can anyone confirm that going back to Eclair and then doing the OTA update back to Froyo works? I've seen other posts indicating that there are problems with this method.