Related
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
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 have yet to see a 2.2 SBF released into the wild yet. anyone seen it?
There is a system only sbf that is for OTA2.2 have heard a few people that had good luck with it. Rootzwiki has all the info on it
Sent from my DROIDX using XDA App
woah.. what is this .. $BF you speak of??
its a unicorn of the intertubes.
System only SBF didn't work it would appear to be using the old bootloader and only the full one uses the new bootloader.
I have used the 2.2 SBF that TBH released and I can say it does work. Keep in mind that its only a System SBF and wont fix all your problems.
http://www.mydroidworld.com/forums/droid-x-mods/4818-tbh-announces-froyo-system-sbf-rsdlite-4-8-a.html
I am not clear on what would be expected after flashing a system sbf instead of a full. Also, I have been seeing some comments advising people to go to the rooted deodexed OTA version from 2.3.9 or 2.3.13. What would be the benefit with the currently locked bootloader and no full sbf?
I tried to install Tranquility but was not deodexed and they said it would be fine, but it was not. I then tried a reset which went to 2.1 instead of 2.2 and bricked the phone. I'm told that the full SBF would fix that issue since it works off of a new bootloader.
I did the same thing I've been looking everywhere for information on a full 2.2 sbf, but I can't find anything. I'd just like to know an eta, but I know with leaks we usually can't ever be certain. I guess my phone's bricked for the long haul.
is there one out?
i dont want to have to sbf to 2.3.340 or sbf 4.5.596 just to do the ota to get back to 4.5.602 each time?
there should be a 4.5.602 by now shouldnt there?
There's never an alloted time between when an update gets released and when we get the SBF file.
We can hope that it will be leaked soon; however, it may just be as well that you use the .596 SBF then update as the update file isn't large, and you wouldn't be able to obtain root either way.
If you're interested though the hour that one becomes available I will announce it here on Droid X General =D
Sent from my DROIDX using XDA App
I am turning purple...
I am turning purple holding my breath...
(Gosh, arent the vultures here so ungrateful!)
infazzdar said:
There's never an alloted time between when an update gets released and when we get the SBF file.
We can hope that it will be leaked soon; however, it may just be as well that you use the .596 SBF then update as the update file isn't large, and you wouldn't be able to obtain root either way.
If you're interested though the hour that one becomes available I will announce it here on Droid X General =D
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
yea im intrested.
with all the flashing i would like it to be as simple as possible.
one sbf file to get back to stock would always be great.
Google 602 without SBF.
Sent from my DROIDX using XDA App
mav3rick478 said:
Google 602 without SBF.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
but i want the sbf
i dont want the root (at this point anyhow)
is there really gonna be an SBF for such a small update? It's an 11mb zip file that mainly updates the baseband.
mav3rick478 said:
is there really gonna be an SBF for such a small update? It's an 11mb zip file that mainly updates the baseband.
Click to expand...
Click to collapse
i dont know.
if you are on 2.3.340 (OTA) and you then check for updates....does it find the .602 update and update you directly from there or dies it update you to .596 first then restart your phone and check for updates again and finds .602 and updates you and restarts your phone again?
if it goes straight to .602 from 2.3.340 with only one restart then that would mean there is a single sbf for .602 that is probably around 110MB wouldnt it?
m16-maniac said:
i dont know.
if you are on 2.3.340 (OTA) and you then check for updates....does it find the .602 update and update you directly from there or dies it update you to .596 first then restart your phone and check for updates again and finds .602 and updates you and restarts your phone again?
if it goes straight to .602 from 2.3.340 with only one restart then that would mean there is a single sbf for .602 that is probably around 110MB wouldnt it?
Click to expand...
Click to collapse
I agree with the above post, it doesn't seem that a large SBF file would be released for such a small update; however, with Big Red you can never be sure. Until someone such as p3droid can confirm or deny that we will be getting an SBF file we will just have to wait.
m16-maniac said:
i dont know.
if you are on 2.3.340 (OTA) and you then check for updates....does it find the .602 update and update you directly from there or dies it update you to .596 first then restart your phone and check for updates again and finds .602 and updates you and restarts your phone again?
if it goes straight to .602 from 2.3.340 with only one restart then that would mean there is a single sbf for .602 that is probably around 110MB wouldnt it?
Click to expand...
Click to collapse
it should be an easy test*
do what i just mentioned in this quote
I don't think it will jump you from Froyo to 602 GB. The OTA download time was really fast so its really a minor update. But stranger things have happened.
Sent from my DROIDX using XDA App
mav3rick478 said:
I don't think it will jump you from Froyo to 602 GB. The OTA download time was really fast so its really a minor update. But stranger things have happened.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
your download time was QUICK because you were on 4.5.596
try it from 2.3.340
no offense but if i'm going back down to 2.3.340 i might as well install CM7 so i'd rather not.
I did notice a strange thing though, the white 3G icon is useable since I updated to 602. Its almost like its a weaker 3G indicator but still 3G and then there is the normal blue 3G icon. and yes the 1X still shows up so its not a replacement for that.
m16-maniac said:
your download time was QUICK because you were on 4.5.596
try it from 2.3.340
Click to expand...
Click to collapse
mav3rick478 said:
no offense but if i'm going back down to 2.3.340 i might as well install CM7 so i'd rather not.
I did notice a strange thing though, the white 3G icon is useable since I updated to 602. Its almost like its a weaker 3G indicator but still 3G and then there is the normal blue 3G icon. and yes the 1X still shows up so its not a replacement for that.
Click to expand...
Click to collapse
well then dont imply that since the update was a small update that it must be 2 seperate updates and then i wont say go back to 2.3.340 to see if there is only one update to 4.5.602
i already know that.
that is why i started this thread.
no need to get snippy, I can imply what everyone is saying and has posted, its a minor 11mb update for GB. So if you are on Froyo it will do nothing because it updates issues within GB. Just like if you were on Windows XP and a minor update for Windows 7 came up it would not affect you or bring you up to Windows 7.
http://www.verizon-phones.org/verizon-releases-a-new-update-to-fix-droid-x-android-2-3-gingerbread-update-issue.html
http://www.electronista.com/articles/11/08/16/verizon.pushes.bug.fix.for.droid.x.users/
http://www.droid-life.com/2011/08/15/droidx-gingerbread-bug-fixer-is-now-live/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+DroidLife+(droid+life)
When .602 first came out it was a seperate 11 mb file for anyone coming from 2.3.340.
So if you checked update on froyo you downloaded the large .596, rebooted, checked again then it downloaded .602. Now if you do the same, it will download the large combined .602 directly if your are on froyo.
I would like an SBF also.
rocko73 said:
When .602 first came out it was a seperate 11 mb file for anyone coming from 2.3.340.
So if you checked update on froyo you downloaded the large .596, rebooted, checked again then it downloaded .602. Now if you do the same, it will download the large combined .602 directly if your are on froyo.
I would like an SBF also.
Click to expand...
Click to collapse
now thats what i am talking about
we want the sbf
dont know if its right place but plz help with my .602
i had 4.5.602 on my droid x i was using apex for .602 then i lost my google talk after trying to switch to another rom still with no google talk i decided to spf i use .596 to try all over then my battrey died so i had to cut my wire do the whole black to neg red to pos got by battrey back up but all i get is bootloop tryed sevral sbf files on rsd lite 5.3.1 tryed sbf 2.2.34 sbf for a 4.5.596 a 1.13.6.2 all did nothing
plz help me only phone i have cant replace im broke
m16-maniac said:
i dont know.
if you are on 2.3.340 (OTA) and you then check for updates....does it find the .602 update and update you directly from there or dies it update you to .596 first then restart your phone and check for updates again and finds .602 and updates you and restarts your phone again?
if it goes straight to .602 from 2.3.340 with only one restart then that would mean there is a single sbf for .602 that is probably around 110MB wouldnt it?
Click to expand...
Click to collapse
It now goes straight to .602 from Froyo. The first week or so it went to .596 then .602.
rocko73 said:
It now goes straight to .602 from Froyo. The first week or so it went to .596 then .602.
Click to expand...
Click to collapse
I can confirm this.... I've now taken the .602 ota update straight from an sbfed .340 twice on my way to CM7 DX GB.... and the Droid 3 root method (on linux or windows) works flawlessly on the .602 ota
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.