Database Users

2.3.23 Full SBF on MDW Now

http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
I've not flashed it, but the links are currently working.

There's An App For That
For those of you who don't make it in time to get the SBF before it's taken down, don't worry. If you have the TBH app, you are good to go. Not only do they have the 2.3.32 update, but also the 2.3.32 SBF in case you wish to go back. Thank God for TBH. Way to go guys - don't know what I'd do without you.

Enjoy everyone! You're welcome.
We normally discourage openly posting the content from the TBH app but this is an exception in order to make this file available to anyone who might need it.
Thank you for posting links back to MDW and promoting the use of the TBH app.
Good luck and happy droiding!

does anyone have the 2.3.23 update.zip, all the links are dead on MDW. i got the new 2.3.23 sbf file but need the update.zip so I can get onto 2.3.23

I need that zip too. I was able to sbf to 2.3.32 but the bootloader version stays on 30.01.
Sent from my DROIDX using XDA App

email me if you need the update file, i think it was pulled

You can also get it from the TBH app, with the nice upside of supporting TBH

Does the tbh app have the full. 320 sbf available?
Sent from my DROIDX using XDA App

yep
(10 char)

z4 worked for me after i flashed the sbf if it helps anyone.

bal1985 said:
does anyone have the 2.3.23 update.zip, all the links are dead on MDW. i got the new 2.3.23 sbf file but need the update.zip so I can get onto 2.3.23
Click to expand...
Click to collapse
just flash the sbf without updating, worked like a charm coming from my bricked DX.
remember to pull the battery after you update when the droid x animation begins to boot loop. then hold the home button when booting up again, then data/factory reset from the recovery and select reboot system now.
z4root works, confirmed. just installed Fission 2.3 just minutes from sbf'ing 2.3.23.

It's important to remember that flashing the SBF will not update the bootloader whereas the update.zip will update to 30.04 but will not update the baseband.
That is the primary difference as well as the update.zip being rooted and deodexed with busybox installed.

cellzealot said:
It's important to remember that flashing the SBF will not update the bootloader whereas the update.zip will update to 30.04 but will not update the baseband.
That is the primary difference as well as the update.zip being rooted and deodexed with busybox installed.
Click to expand...
Click to collapse
what baseband? there is a baseband update in one of these? why not do the update.zip and sbf in that case?
i thought p3 posted on twitter there was no baseband update in either of them.

not true, sbf coming from 2.3.15 updated it all.

GoldenCyn said:
not true, sbf coming from 2.3.15 updated it all.
Click to expand...
Click to collapse
did you confirm that by going to stock recovery? i have not experienced that myself. only way to update bootloader was with update.zip

cray1000 said:
what baseband? there is a baseband update in one of these? why not do the update.zip and sbf in that case?
i thought p3 posted on twitter there was no baseband update in either of them.
Click to expand...
Click to collapse
The SBF has a baseband update in it, but for almost everyone it won't matter because the baseband hasn't changed from 2.3.15. I think only people still on eclair or the froyo leak were the only ones who are behind on the baseband.

[Q] ROM updating with 2.2.1 (system 2.3.340)

If you are running version 2.2.1 (system 2.3.340) on your DroidX can you and what ROMs can you safely flash that are out? for instance dark slide? Or Fission?

both of those will run on the droid x but really look into the two best apex and gummyjar....
good luck just do some searching you will be alright...

Ive used a few TranQ which was horrible on my device 2 others that didn't work for beans and dark slide im on now. DS actually worked for a while but it has a memory leak and now with age its getting more unstable.
I wanted to go ahead and upgrade to the current basis of 2.3.340 system SBF but as warned " attempt to wipe with an old SBF, you WILL brick your phone." But I am a little confused on what classified as an older SBF at this point?

iceblue11 said:
Ive used a few TranQ which was horrible on my device 2 others that didn't work for beans and dark slide im on now. DS actually worked for a while but it has a memory leak and now with age its getting more unstable.
I wanted to go ahead and upgrade to the current basis of 2.3.340 system SBF but as warned " attempt to wipe with an old SBF, you WILL brick your phone." But I am a little confused on what classified as an older SBF at this point?
Click to expand...
Click to collapse
2.3.315 is old . Do Not use it if you go higher .320 or .340
look at Fission new version may be coming soon .

kdkinc said:
2.3.315 is old . Do Not use it if you go higher .320 or .340
look at Fission new version may be coming soon .
Click to expand...
Click to collapse
Dont use what? Im on 2.3.315 now with android 2.2 on DS

ARHicken said:
both of those will run on the droid x but really look into the two best apex and gummyjar....
good luck just do some searching you will be alright...
Click to expand...
Click to collapse
Highly subjective, I for instance think Fission is the best, and for those who want some blur, ApeX is my choice.

bouchigo said:
Highly subjective, I for instance think Fission is the best, and for those who want some blur, ApeX is my choice.
Click to expand...
Click to collapse
I like the blur, and looking for the apex rom still. So i should download the 2.2.340 and install it then flash apex?

iceblue11 said:
I like the blur, and looking for the apex rom still. So i should download the 2.2.340 and install it then flash apex?
Click to expand...
Click to collapse
You can't just apply 2.3.340 over non-stock 2.3.15.
Make sure your bootloader is 30.03, if it is, then:
The easiest thing to do (in my opinion) is to flash the 2.3.15 full sbf with RSD Lite to get back to stock. Once that is done, then just do the OTA update on your phone to get to 2.3.340. After you've done that, you can use z4Root to get root access again and install bootstrapper, etc.
Now you can apply ApeX 1.3.1; you can get ApeX 1.3.1 here:
http://androidforums.com/droid-x-all-things-root/234360-rom-apex-1-3-1-droid-x-running-running-fast-can-12-16-10-a.html

Now thats what i needed to know. Thank you bro!

bouchigo said:
You can't just apply 2.3.340 over non-stock 2.3.15.
Make sure your bootloader is 30.03, if it is, then:
The easiest thing to do (in my opinion) is to flash the 2.3.15 full sbf with RSD Lite to get back to stock. Once that is done, then just do the OTA update on your phone to get to 2.3.340. After you've done that, you can use z4Root to get root access again and install bootstrapper, etc.
Now you can apply ApeX 1.3.1; you can get ApeX 1.3.1 here:
http://androidforums.com/droid-x-all-things-root/234360-rom-apex-1-3-1-droid-x-running-running-fast-can-12-16-10-a.html
Click to expand...
Click to collapse
I need some help understanding what the benifts are and how to upgrading the kernal with benift
Also do I need to upgrade
I have 30.04 bootloader and my kernal is 2.6.32. Can anyone send me a link and why is mine a 2.6 and all the forms say 2.3?

Bc we were talking about the system file 2.3 not the kernal im on 2.6.32.9-gca646b6 kernal

Aww how do u check which "system" file you have?

4.5.602 official ota sbf

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

Milestone X - C-Spire: Custom ROMS? Droid X Bootstrapper Working

Anyone with luck flashing a Milestone X w/ a custom ROM?
Running Rooted 2.3.5 w/bloatware removed (but backed up) along w/ DROID X Bootstrapper.
Have made my first full system backup using this tool.
If complete ROMS could not be used, what components would I need to modify, replace, ... exchange to get it to work on C-Spire (say, Verizon).
I've heard that there are some ROMS that don't mess with the baseband and other communications settings, files, frequencies, protocol, etc... What are these type called if they exist? Where can I find them? Are these a safer alternative to full ROMS?
Will DX Bootstrapper get the job done? Reports ClockworkMod REcovery v2.5.0.6.

I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.

Rocheforte said:
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Click to expand...
Click to collapse
agreed. [10chars...............

another thing to consider, since we cannot sbf at this time, is that the bootstrapper will break your ability to install any future ota updates. it modifies the logwrapper and makes a copy called logwrapper.bin, however, uninstalling the bootstrapper and restoring the logwrapper file does not correct the problem. best i can tell the only answer that i can find when this happens is to sbf back to stock... well you see where this is going.... currently we cannot do this, so unless you never want the ota upgrades i do not recommend installing the bootstrapper on cspire's milestone x.
oh well nevermind went back and re-read your post, you already have the bootstrapper installed. (at least you did it after ota)

here is a link to the post that has the sbf that is reported to work with cell south (cspire) http://forum.xda-developers.com/showthread.php?t=1117885
maybe someone else can try it again and report back.
daywalker04 said:
SBF flash for MB809 - Milestone X Generic North America
SHADO_X6_3.1.39_SHADOW_BP_C_02.06.00R_AP_BP_Flex_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
http://www.filesonic.com/file/11766...x_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
Compression MD5 - BF942D55992C774446F24B56116649A1
SBF MD5 - 2EAEBD1540D563114523BEB09539A8AF
Click to expand...
Click to collapse
abcleanonme said:
Well I can confirm it works on Cellular South.
Sent from my MilestoneX using XDA Premium App
Click to expand...
Click to collapse

I can confirm that the old sbf it does not work after ota update. I had to get a new phone. I have rooted, but I am not installing a bootstrapper until a working sbf is available. Hopefully that will happen soon.

I am on C spire out of Byram, MS and can in fact confirm that "Droid X Bootstrapper" from the market indeed works like a charm on the Milestone X with stock versions 2.2.2 and 2.3.5.
I use "Super One Click" to root, then the same prog to "Allow non market apps" then buy "Droid X Bootstrapper" from market, run it. Reboot while holding camera button and power button,,,,voila
Confirmed roms that I have and currently run or ran: CM 7 nightlies, Liberty 1.5, and Fission 2.5.7 DroidX
---------- Post added at 07:12 AM ---------- Previous post was at 06:57 AM ----------
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...

Brickster said:
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Click to expand...
Click to collapse
i tried that too it didn't work for me.

I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App

Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
is there a reason that your not using the new liberty rom and used 1.5?

tylorjefcoat said:
is there a reason that your not using the new liberty rom and used 1.5?
Click to expand...
Click to collapse
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.

Brickster said:
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Click to expand...
Click to collapse
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?

Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.

thenig said:
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
Click to expand...
Click to collapse
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.

tylorjefcoat said:
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Click to expand...
Click to collapse
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.

Brickster said:
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
Click to expand...
Click to collapse
Open the updater-script with notepad (new to this) and found no mention of kernel assert. Almost there...a bit more help would get me in.

It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App

Brickster said:
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
Thank you sir! I'm gonna try that.

Brickster said:
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Click to expand...
Click to collapse
I despised that phone lol, wait i take that back, i guess i had "phone" envy lol Mine was a rom whore as well, it was rooted almost immediately after i got it with the ole gold card method.
the ota 2.3.5 is actually a good CLEAN rom, i do like the fact that it is so clean, just need a few tweaks as you said from the cm7 build, status bar tweaks ect..
may build up one.
built a rom for a tablet we are selling here, BIG learning curve but the locked boot-loader throws a real curve ball
now, have you gotten it to overclock?

Brickster said:
. Hell, if I mess something up bad enough , just sbf back.
Click to expand...
Click to collapse
that still amazes me. i haven't tried it on 2.3.5, but when i did it from stock 2.2.2 it was a no go.... maybe it will only work if you are already on 2.3? hell i dunno... motorola has me chasing my tail.... like everyone else, i came from the hero too, that was one awesome little phone. i read somewhere that the motorola bootloader had been cracked by someone on here but..... not sure what ever happened there.....

Firmware AT&T Gingerbread 2.3.6

Credits Total to daywalker04
Original Gingerbread SBF 2.3.6 for ATRIX 4G AT&T USA
For AT&T DEVICES ONLY
DO NOT FLASH TO A DEVICE WITH AN UNLOCKED BOOTLOADER. ATTEMPTING TO DO SO MAY RESULT IN A BRICK !!!!
Upgrading to 2.3.6 will more than likely prevent you from downgrading to any previous version of Gingerbread.
Blur_Version.4.5.141.MB860.ATT.en.US
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz
DOWNLOAD
Compression MD5 - 78CBE2314D76016A12118B30655A3451
SBF MD5 - 0BC556A7FD949317F061E29D88632242​

Hey arent this the soak? Man it will put you in troube...
Sent from my MB860 using XDA App

I am waiting for the fruitcake to upgrade. But with the CM9 project almost ready as a daily driver I wonder if it is best to skip it.

Hello, Could you let me know the process of upgrading, i am currently on 2.3.4 version, thanks for your support in advance

is this the OTA update that will be coming out once the soak is done? Do you update just like you would with a regular OTA? This is the US ATT English version correct?

i am also waiting for fruitcake

Anybody been brave enough to confirm if this will indeed brick a device with an unlocked bootloader?

jgc121 said:
Anybody been brave enough to confirm if this will indeed brick a device with an unlocked bootloader?
Click to expand...
Click to collapse
As with most of these awesome STOCK firmware sbf's this will most likely brick your device if you don't know what your doing and have an already unlocked boot loader.
If your running locked tight boot loaders flash away, I'm ripping this sucker apart for the webtop that we lost in the fruitcake posts.
THANK YOU OP!!!

Djazin said:
As with most of these awesome STOCK firmware sbf's this will most likely brick your device if you don't know what your doing and have an already unlocked boot loader.
If your running locked tight boot loaders flash away, I'm ripping this sucker apart for the webtop that we lost in the fruitcake posts.
THANK YOU OP!!!
Click to expand...
Click to collapse
I do know what I'm doing - I'm just not going to carelessly flash something thats rumored to cause a brick - the only way to brick with an sbf before this came out was downgrading from GB to Froyo....

jgc121 said:
I do know what I'm doing - I'm just not going to carelessly flash something thats rumored to cause a brick - the only way to brick with an sbf before this came out was downgrading from GB to Froyo....
Click to expand...
Click to collapse
Granted but also flashing anything with a not unlocked Boot.img file or I belive it was the CG51.smg within the sbf will make you have to jump hoops to get it back up and running. Using fastboot and another pudding reflash.
Ive done this with the 2.3.4 sbf just for kicks due to me not having that burnt efuse its still a pinta using stock sbfs best thing to do is unpack then flash the correct CG's needed via fastboot, or unpack and repack the whole think. I couldn't break the repacking part on custom sbf's.

Djazin said:
Granted but also flashing anything with a not unlocked Boot.img file or I belive it was the CG51.smg within the sbf will make you have to jump hoops to get it back up and running. Using fastboot and another pudding reflash.
Ive done this with the 2.3.4 sbf just for kicks due to me not having that burnt efuse its still a pinta using stock sbfs best thing to do is unpack then flash the correct CG's needed via fastboot, or unpack and repack the whole think. I couldn't break the repacking part on custom sbf's.
Click to expand...
Click to collapse
Would it be possible to swap the bootloader in the 2.3.6 sbf with the 2.3.4 unlockable bootloader in Edgan's sbf ? hmmm...

Im all stock. I just want the new OTA update and not have to wait for the soak test to be done.
Sent from my MB860 using XDA App

jgc121 said:
Would it be possible to swap the bootloader in the 2.3.6 sbf with the 2.3.4 unlockable bootloader in Edgan's sbf ? hmmm...
Click to expand...
Click to collapse
No but there is a tread about sbf's and fastboot linked in the pudding thread that has alot of good information on both subjects check it out you can how ever repack an 2.3.6 sbf with a 2.3.6 boot.img (from one of the roms out there converted to .smg ofcourse) and repack it that should work.

Another question - Does anyone have a FULL 2.3.4 sbf file that I can swap the 2.3.4 unlockable bootloader into? I've got a service 2.3.4 sbg - But i need a full one.... anyone? please?

jgc121 said:
Another question - Does anyone have a FULL 2.3.4 sbf file that I can swap the 2.3.4 unlockable bootloader into? I've got a service 2.3.4 sbg - But i need a full one.... anyone? please?
Click to expand...
Click to collapse
the2dcour said:
Unlock:
links down in pudding
Look at the pudding thread..
Click to expand...
Click to collapse

Are there any obvious advantages to this update? I'll probably just wait for the OTA

Any word on root for this version? Have you tried anything yet?
Sent from my Motor Atrix 4G using xda premium.

Someone make a fruitcake!
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone

Preinstall/fastboot method still works.

Root
das8nt said:
Preinstall/fastboot method still works.
Click to expand...
Click to collapse
That's good, I was just hoping someone had tried the 'One Click' method found > HERE < and it still worked for this version as well.