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.
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.
Found this on my twitter feed just spreading it around.
http://www.droid-life.com/2010/12/0...3-340-coming-madden-2011-to-be-pre-installed/
Sent from my DROIDX using XDA App
I'm on the 2.3.320 leak, not going to .340 until an SBF comes out.
Sent from my DROIDX using XDA App
gio2005 said:
I'm on the 2.3.320 leak, not going to .340 until an SBF comes out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
if you're on tranq 3.5.1 you're already on .340
I guess I am glad I didn't upgrade to .320
Sort of....
I had no idea Tranquility 3.5.1 had 2.3.340. I donate to several ROM teams (why not) and I am looking to see what Team DeFuse does with Fission 2.3->2.x build, hopefully it will include 2.3.340 soon. I really like the speed of their ROM.
so basically this .340 update is the same as the leak version? so if i manually somehow updated to this .340 am i able to use the latest sbf file?
3.40 is not the same as 3.20!
Personally, I'd like to know what the difference is between the two. I have the 3.20 leak and the 3.20 sbf but can I use them once i go to 3.40?
If there is any difference in .320 and .340 (beyond Madden of course) it isn't readily apparent. Someone can try doing a diff on the system files between Tranq 3.5.1 and stock .320, but the bootloader and kernel are the same. The baseband hasn't changed at all since 2.3.15.
When is the update going live?
Sent from my DROIDX using XDA App
As per Droid Life>>> DROID X 2.2.1 Update Will Be Available Tonight?
My question is, will I see the update?
I have flashed the leaked VRZ_MB810_2.3.32_1FF_01.sbf, I am not rooted and haven't removed any apps.
If u updated with TBH leak version you will have to wait for there patch or fix or whatever it is they are doing before you will be able to get the OTA.
I just got the DX update. I never signed up for the feedback network either. I pulled it.
Anyone know if we should hold off? dont want to lose root for good....
can you post the zip please?
Installed the update and lost root. It's also rebooting into clockwork recovery after powering down and back up. Reboot system option works. I was just rooted, no ROM or themes.
mochamoo said:
Installed the update and lost root. It's also rebooting into clockwork recovery after powering down and back up. Reboot system option works. I was just rooted, no ROM or themes.
Click to expand...
Click to collapse
if clockwork mod is working then maybe you can reroot with an update.zip?
someone i follow on twitter @bandroidx says he has the update.zip
thanks but I mean a download link for the update.zip like @ megaupload/etc. He just says he got the update thats all. I keep getting download check not available.
cray1000 said:
if clockwork mod is working then maybe you can reroot with an update.zip?
Click to expand...
Click to collapse
Afraid I don't have this. I do have a nandroid backup and the .320 sbf. Can I restore the backup or flash the sbf if need be? Don't want a bricked phone...
Am pretty sure that I am booting into recovery because of how koush's bootstrap works. It was installed and since I don't have root it can't complete it's thing. In this case it might be a good thing
Z4root is supposedly working, try that.
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
Wow, so there is all sorts of GB info running around, and I'm not entirely sure what route to take.
I was running Liberty 1.5 until earlier today and I SBF'd back to .340 a few hours ago with the intent of updating OTA. I decided to look around and see if someone already had the official OTA that I could just manually update, and I came to a post from p3Droid that has left me scratching my head.
From this thread:
http://www.mydroidworld.com/forums/...-5-596-release-thread-something-everyone.html
So right now I am 100% Stock. To update to .596 manually, I'd need to use the Full signed version? If I did this, wouldn't it be the same as waiting for the OTA?
Also, why is waiting for the OTA not recommended? Is it because root currently isn't available? Then wouldn't using the full signed version be not recommended?
If so, I can just root and use the PART 1 and PART 2 to get to a rooted version of .596, is this correct?
I'm a bit confused as to what the best course of action would be right now.
if you use p3droid's gingerbread ota rooted roms, you'll have the latest gingberbread build with root. otherwise just wait for OTA into gingerbread if you dont care much for root
Honestly what's important is that it's the latest official build. Root is second on the list, so it guess I'll do that. That's the one that requires part 1 & 2 and the D2 bootstrapper, correct?
yeah, you need the DROID 2 bootstrapper (not the droid X bootstrapper) just to reassure.
1 you should be on stock .340 (cannot be madderstock or you will have bootloader stuck)
2 have it rooted on .340 (z4root is an easy way to do that)
3 run droid 2 bootstrapper
4 install part 1, followed by part 2 WITHOUT rebooting
5 reboot
Awesome.
What's the difference between the unsigned version and the signed version? Will it make a difference down the road if I need to SBF to stock for a return or SBF for a future OTA?
EDIT:
Also, is there any difference between the part1 part2 and the full signed stock other than the signature?
you can SBF back to .340 stock from GB root, I have done this to go back to froyo, but ended up going back to GB root.
GB root ROM is the same as OTA, except it has root. If you want to go back, just find the SBF full .340, and then update through OTA for gingerbread stock
So i screwed up i tried using maddstocker's .340 zip and now i'm stuck at the M boot logo. Can i still SBF back to .340?
Yes, in my experience SBF is the failsafe course of action for all bootloops/softbricks.
EtherBoo said:
Awesome.
What's the difference between the unsigned version and the signed version? Will it make a difference down the road if I need to SBF to stock for a return or SBF for a future OTA?
EDIT:
Also, is there any difference between the part1 part2 and the full signed stock other than the signature?
Click to expand...
Click to collapse
Ones signed and the other isn't. Unsigned could potentially cause problems in recovery
Can someone point me in the right direction?
I am at .596 and running Liberty GB v.09
Just want to get back to stock and decide from there if I want to root or just stay stock
I understand I will probably have to SBF but do I go to .602 or .605 (SBF available?)
Do I need to go to something before .602 and update OTA?
Thanks
SBF to .596 or .602, then update to .605.
I recommend SBFing to .596 just to be safe, although SBFing to .602 shouldn't give you any problems.
Sent from my DROIDX using XDA App
I would SBF to 2.3.340 Froyo then take the large OTA then factory reset. This has worked well for me.
There is now a 605 sbf file that was released by Motorola on 10-5-2011.
Here is the exact file name for those who may know someone with RSD access:
1FF-p3a_shadow_cdma_shadow-user-2.3.3-4.5.1_57_DX5-35-110820-test-keyssigned-Verizon-US.sbf.gz
drkcobra said:
There is now a 605 sbf file that was released by Motorola on 10-5-2011.
Here is the exact file name for those who may know someone with RSD access:
1FF-p3a_shadow_cdma_shadow-user-2.3.3-4.5.1_57_DX5-35-110820-test-keyssigned-Verizon-US.sbf.gz
Click to expand...
Click to collapse
Come on, some Verizon employee, grab this file please!
MrMorganUSC said:
Can someone point me in the right direction?
I am at .596 and running Liberty GB v.09
Just want to get back to stock and decide from there if I want to root or just stay stock
I understand I will probably have to SBF but do I go to .602 or .605 (SBF available?)
Do I need to go to something before .602 and update OTA?
Thanks
Click to expand...
Click to collapse
Just go sbf to 602 and take the 605 ota. use the latest one click to root if you want. The one click root also works on stock 605....I'm running it now and a 605 based rom called icx.
Giggity.