Does anyone know if the new gingerbread release changes the bootloader making it impossible to sbf back to froyo or if there is an sbf file for gingerbread?
I'm just asking because I realized that if gingerbread changed the bootloader version and flashing the file had an error somewhere I would be completely screwed
Jmoney47 said:
Does anyone know if the new gingerbread release changes the bootloader making it impossible to sbf back to froyo or if there is an sbf file for gingerbread?
I'm just asking because I realized that if gingerbread changed the bootloader version and flashing the file had an error somewhere I would be completely screwed
Click to expand...
Click to collapse
yes you can its and says so in the OP from p3
Ok thank you. I just wanted to make sure before I flashed it
Related
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.
I want to get off 2.3.13 and go to back to OTA updates, Ive tried searching and finally gave up........I want to download a SBF to get me back to stock so i can get the latest version. I believe my phone was on 2.2 OTA, bootloader version is 30.03.
I have RSD 4.8, Im rooted, have root explorer.
Long story short I deleted some factory .apk's and I flashed this SBF (2.3.13) to update OTA......not realizing it wouldnt fix my problem. Learned my lesson and to turn them to .bak's next time.
please help!
If it's some bloatware you can always get it back on the moto page
Sent from my DROIDX using XDA App
I have all the bloatware on and working.......i think that 2.3.13 is one of the leaked versions and it wont allow me to OTA update......it doesnt even show me an update is available now with the 2.3.13 build
If you're on the froyo leak, you need to flash back to 2.1, then take the OTA updates
If you are on boot loader 30.03, then you need to flash the sbf 2.3.15
oops, didn't see the bootloader was posted, my mistake, 2.3.15 is the correct sbf
I thought there was some bootloader problem thats why i put the info in the post.
Thank you guys, can someone PM me some info on where to find the SBF for 2.3.15.........Ive had no luck googling it.
now officially bricked the phone trying to fix this.
Im in need of some serious help here. I can still flash SBFs but it says mem-map blank service req'd. I downloaded the SBF from
from phoxus gift 2
I have no idea what to do now
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
1KDS said:
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
Click to expand...
Click to collapse
+1 on that
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.
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.
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!!!