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.

Full 2.3.340 SBF????

Any news on when this is gonna come out so i can SBF fully back to stock any info would be appreciated thanks

You can do this currently by combining .320 and .340 SBF files. I have not heard anything yet on a full .340 being released.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.

Isn't this essentially a full SBF?
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
It contains the system-only SBF, as well as individual patches for the bootloader, kernel, and baseband.

aohus said:
Isn't this essentially a full SBF?
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
It contains the system-only SBF, as well as individual patches for the bootloader, kernel, and baseband.
Click to expand...
Click to collapse
I dont think so. I believe a full sbf overwrites the full phone image from /* in other words there is more to the OS architecture than just /system.
If im incorrect, anyone that has more info/corrections, please feel free to chime in.
Sent from my DROIDX using XDA App

NotATreoFan said:
You can do this currently by combining .320 and .340 SBF files. I have not heard anything yet on a full .340 being released.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
Click to expand...
Click to collapse
Could you explain this process? Im running rubiX Focused on my 2.3.15 version and from my understanding, having the newest system software would be beneficial in installing and using newer roms etc.
I have both a nandroid backup of my stock albeit rooted setup of 2.3.15, as well as the system 2.3.15 sbf. I also have the 2.3.32 sbf file. I realize that if I sbf back to a clean 2.3.15, I can just accept the OTA update to 2.3.34.
Two questions from here:
Which method for updating would be best? From the OTA update to 2.3.34 would I be able to sbf back to 2.3.32 or would i be stuck until a 2.3.34 full sbf is released?
Sorry in advance for jacking the thread

*bump* would like to know this as well.

ElephantGlue said:
Could you explain this process? Im running rubiX Focused on my 2.3.15 version and from my understanding, having the newest system software would be beneficial in installing and using newer roms etc.
I have both a nandroid backup of my stock albeit rooted setup of 2.3.15, as well as the system 2.3.15 sbf. I also have the 2.3.32 sbf file. I realize that if I sbf back to a clean 2.3.15, I can just accept the OTA update to 2.3.34.
Two questions from here:
Which method for updating would be best? From the OTA update to 2.3.34 would I be able to sbf back to 2.3.32 or would i be stuck until a 2.3.34 full sbf is released?
Sorry in advance for jacking the thread
Click to expand...
Click to collapse
Tge limitation on whether or not you can go back is based upon the version if the bootloader that the sbf wird I believe. I have not used anything above the 2.3.15 sbf so I'm not sure if the sbf you're speaking of includes a bootloader version
Sent from my DROIDX using XDA App

If you use your 2.3.320 SBF you said you have, you can then use this update: http://www.droid-life.com/2010/12/09/droid-x-2-3-340-system-sbf-released-for-2-3-320-leak-users/
It should get you fully updated to 2.3.340. It does involve flashing your phone twice, but after that you should be good (as far as I know with my still limited knowledge of these things...)

Can't you just flash the 2.3.13 sbf then get the OTA update again? Any risk in doing that?

TreyStyles said:
Can't you just flash the 2.3.13 sbf then get the OTA update again? Any risk in doing that?
Click to expand...
Click to collapse
I don't think you can flash 2.3.15 once you have passed 2.3.320 as your bootloader will have been upgraded.
I recently flashed a full SBF of 2.3.320, then the Kernel, Baseband and Bootloader zips, then the 2.3.340 SBF. Bam, I have a stock phone that looks like it just came from Verizon. Its got all the preinstalled apps, blur, etc... it's basically stock 2.3.340.
For about 30 seconds until I rooted it and loaded Fission 2.4.3 on it...

nvrmnd..........

jeftep said:
I don't think you can flash 2.3.15 once you have passed 2.3.320 as your bootloader will have been upgraded.
I recently flashed a full SBF of 2.3.320, then the Kernel, Baseband and Bootloader zips, then the 2.3.340 SBF. Bam, I have a stock phone that looks like it just came from Verizon. Its got all the preinstalled apps, blur, etc... it's basically stock 2.3.340.
For about 30 seconds until I rooted it and loaded Fission 2.4.3 on it...
Click to expand...
Click to collapse
I had done this also, but I couldn't see to stop the phone from booting into Clockwork on a battery pull.

Which SBF Do I need?
I just bought a DX and am coming from a D2. I know how to do everything but it is confusing finding out which SBF i need. I need to know which SBF, or SBF's i need to unbrick phone if need be. Info for phone is as follows.
Android Version 2.2.1
Official OTA 2.3.340 (Guy updated to 2.3.340 at Verizon Store before i left with it.)
Thanks for any help.

Problem solved thread can be closed.
Sent from my DROIDX using XDA App

Android Version 2.2.1
Official OTA 2.3.340 (Guy updated to 2.3.340 at Verizon Store before i left with it.)
Click to expand...
Click to collapse
I'm in the same boat willjohnson, which sbf was the correct one? TIA

If you are already on .340, you do not need anything more than the .340 System-Only SBF released by TBH. Until Motorola has a new update that modifies the bootloader, or other components, no ROM you install will change these.

Bricked DX
has anyone ever seen the following:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Ive been trying to flash this thing back to stock after botching a tranquility install and rsd lite wouldn't recognize my phone, then i tried to flash it anyway using a .340 sbf and then this is what i ended up with.
Please let me know.
thank you

That is just the system sbf, you are flashing. You need to be flashing the full sbf 2.3.32, if you are on bootloader 30.04.

Update everyone! I just started a thread in Development subfroum about a full 2.3.340 update zip that can flashed as long as you can access clockwork recovery. I recommend checking it out and downloading the file for safe keeping. It was put together by Maderschramm.

Getting ready to upload the full 2.3.34 sbf from a verizon retail store. Not sure if it's safe to put the direct link here. If not, send me a pm, should have it up by tonight at the latest. this is the official sbf and can be used with rsd lite.

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.

Accidentally flashed full sbf

So here it is, I accidentally picked the chinese JDGC_2.13.0 while flashing sbf and now my defy is a ME525 when I look into the phone information.
That sbf does not seem to be downgradable, as I only get a black screen after flashing any other sbf I used before, meaning the stock froyo or the nordic.
I seriously don't know what to do now. Is there something I can do to downgrade or make my phone a MB525 again?

I hate to break this to you,but i think you are screwed.If it is under warranty,give it to your service centre and act as if you know nothing.That is the best advice i can give you.Try to ask senior members about this and see if there is a way out of this.

you flashed a bl3 rom and now you cant downgrade to any froyo rom you flash this china rom and you need to have a froyo nanndroid buckap and an fixed sbf

tanarez said:
So here it is, I accidentally picked the chinese JDGC_2.13.0 while flashing sbf and now my defy is a ME525 when I look into the phone information.
That sbf does not seem to be downgradable, as I only get a black screen after flashing any other sbf I used before, meaning the stock froyo or the nordic.
I seriously don't know what to do now. Is there something I can do to downgrade or make my phone a MB525 again?
Click to expand...
Click to collapse
Upgrade to a non chinese BL4 Froyo. Or if you wish you may update to a GB BL6!! However then your phone will become MB526(Defy+) and you won't be able to downgrade to Froyo again!
You can find them here or go to dev section of XDA...
You may also need this Defy Image tools Use them to check the BL version... (smgver.exe)

pranks1989 said:
Upgrade to a non chinese BL4 Froyo. Or if you wish you may update to a GB BL6!! However then your phone will become MB526(Defy+) and you won't be able to downgrade to Froyo again!
You can find them here or go to dev section of XDA...
You may also need this Defy Image tools
Click to expand...
Click to collapse
He would be able to downgrade to Froyo. There is a Chinese BL6 Froyo sbf available in the forums.

niksy+ said:
He would be able to downgrade to Froyo. There is a Chinese BL6 Froyo sbf available in the forums.
Click to expand...
Click to collapse
Ya I tried that once when i wanted to try the CM9 nightly for Defy.. But its a chinese and have the potential to fry your LED!!!

[Q] HELP my defy became defy+

my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
i tried to flashed it with different sbf's found in this forum but none of it work! after flash phone wont boot unlike when you flash it with my current firmware.
i want at least to have my battery back to normal also camera if possible. i tried flashing it with other defy rom but i always got stuck. it seems that ICS was installed but the phone wont load it.
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.

Reply!
Hey there!
Before you do anything, you gotta root your phone. Then install 2ndint to get recovery mode menu. Only from there can you successfully flash roms and get it to work.

i have the same prob.
i can flash any rom for defy+
my phone is defy green.
i flash dfp 4.5.1-231 (bootloader 7)
my battery and camra not work.
any solution ?
Help

The bootloader is locked !!!
Hi ...
Is almost impossible to downgrade from 2.3.6 to 2.2.
Motorola Defy with green lens work just with 2.2. With "update" the camera will NOT work more and until now is not possible to downgrade !!!
All this, because Motorola don't want to unlock the bootloaders. I personally I have this problem and now am nervous on Motorola...
Most of HTC's and Samsung's have unlocked bootloaders. In this conditions, I wil not buy more Motorola.

gorillaz07 said:
my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
<snipped>
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.
Click to expand...
Click to collapse
If you want any help, we need to know your build number (not kernel). We can then find out what bootloader version you have (6 or 7). If you are on bootloader6 you can downgrade to froyo with a workaround, but on bootloader7, you're stuck.
Sent from my MB526 using Tapatalk 2

im on bootloader 9 i think

Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2

gorillaz07 said:
im on bootloader 9 i think
Click to expand...
Click to collapse
You're not on bootloader 9.10. That's not what we're talking about. If you find your build number under system settings -> about phone, we'll try to find out what firmware you flashed to find out what "e-fuse level" you're on. Or just give us a link to the sbf you have flashed.
pjgowtham said:
Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, we're talking about kernels here. If he is a green lens user on 2.3.6 kernel his camera will not work. He needs to downgrade to froyo. This is only possible on bl6. He can't flash a froyo kernel over bl6 or bl7 without flashing a special sbf.

Ya we can't downgrade..it's not possible..but that special sbf s not there too..an i rite?
Sent from my MB526 using Tapatalk 2

i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?

jalal-jap said:
i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?
Click to expand...
Click to collapse
Nope, sorry. No going back from there

theres rooting for bl7s i think...so the only solution would be using custom roms
Sent from my MB526 using Tapatalk 2

He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.

Oh..i didn't know that...thanks auris...that's because I'm safe on Froyo and i haven't tried bl7 in practical..
Sent from my MB526 using Tapatalk 2

I just will my battery back and charge.

yes im on bootloader 9.10 no hopes then to downgrade?

gorillaz07 said:
yes im on bootloader 9.10 no hopes then to downgrade?
Click to expand...
Click to collapse
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)

yeah i figure that our cause in flashing you will see codes and code 39 takes time i guess we cant help but wait, thanks guys if theres any solution pop out hope someone will keep us up to date. thanks!!!

fiskenigaten said:
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)
Click to expand...
Click to collapse
Thanks.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Auris 1.6 vvt-i said:
He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.
Click to expand...
Click to collapse
Thanks.