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
Related
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.
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.
I am in between going to GB and staying where I am at.
My issue is that I am on a version of 2.2.1 Stock that I obtained through TBH around the holidays....file was literally called "happy holidays from TBH" however, this was the 2.3.320 version of the OTA update, not the 2.3.340 version that everyone seems to have.
So the real question is, can I jump straight from 2.3.320 to GB? OR do I need to flash to 2.3.34 since when I check for OTA updates the phone tells me that I am currently up to date.
If I flash to 2.3.34, then I should probably just go straight to gingerbread rooted. However, how would I get the OTA gingerbread when it comes out? Otherwise I would be right back where I am now in about a month or so.
I need to either update to the current froyo and wait for the OTA release of GB, or update to current froyo (2.2.34) and then update again to the new rooted 2.3.3? Right? can someone confirm?
PS. I already have the 2.3.340 .sbf file (445MB) and the 2.3.3 rooted file from p3droid so I am good to go there if necessary.
if you have the 2.3.340 sbf go ahead and flash it first just to be sure...then gingerbread the whole process will only take u 30 minutes its really not that big of a deal
I might as well go ahead and update to 2.3.340 however, I am now seeing on droidxforums that there is another version of 2.3.340 called maderstcok...can't post a link but here is a partial url: droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
The one that I have is from xda via the noobs guide (links to mydroidworld), so I trust that one more... however, this file is an update.zip, not an .sbf. So it could potentially be easier to do?
I would also like to know if it makes any difference if I use the 4.8 version of RSD lite versus 4.9
I am currently using the 4.7.1 drivers as well, pretty sure that that is right, but if there is a newer version, let me know
bump, just want a second opinion
Maderstckok will get you to where you need to be (2.3.340) I've used it 10+ times it's a great file. Then reboot, reroot, and flash GB.
SOCOM-HERO said:
I would also like to know if it makes any difference if I use the 4.8 version of RSD lite versus 4.9
I am currently using the 4.7.1 drivers as well, pretty sure that that is right, but if there is a newer version, let me know
Click to expand...
Click to collapse
I used 4.8. It'll work fine.
Sent from my DROIDX using XDA App
Ditto - 4.8 worked like a charm.
thanks guys, downloading now and will update to 2.3.34, gonna check around for some more ideas on whether or not to go ahead and get GB or wait for the OTA...i have seen some threads with issues with wireless tether, which is one of my reasons for rooting in the first place
so far so good, rooted with z4 after updating to 2.3.34 with maderstock....awesome file, best experience yet with the clockworkmod going to stock. Will update to GB tomorrow. Some of the deodexed roms look really good!
done...on GB, added the deodexed and got the stock BWC theme which is working great. Will maybe flash more custom roms later as they become more mature for GB. otherwise, freezing bulr apps.
US Verizon Droid X running Froyo
Rooted last year using z4root.
Now I want OTA Gingerbread.
unrooted using z4root.
Check for updates. Download. Reboot. Shows Android unpacking animation, then yellow !. Reboots into Froyo. Update failed.
I have never frozen anything. I'm going to try setting keyboard back to stock (update: update still fails). Do I need to uninstall any root apps (Wireless Tether, Titanium Backup, Swype beta, AdFree, Webkey)?
I don't want to do a factory restore if possible.
=====================
System version
Version.2.3.340.MB810.Verizon.en.US
Model number
DROIDX
Android version
2.2.1
Baseband version
BP_C_01.09.07P
Kernel version
2.6.32.9-g55626e1
[email protected] #1
Build number
VZW
ERI version
5
PRL version
52644
The files are more than likely still there from when you rooted.
Backup the thing you need (not including system data) and SBF back to 2.3.34.
From there you SHOULD be able to restore your backed up things, or you can take the OTA then restore.
WARNING: If you take the OTA it may take you to .621 which I DONT recommend. You shoud probably just SBF to .602, reroot, and stay there.
Sent from my DROIDX using Tapatalk
Thanks!
I found this guide to SBF from 2010... is there a more current process you recommend?
droidforums.net/forum/droid-x-rooted-help/100038-complete-droid-x-sbf-flashing-guide.html
Can you explain a little bit why not go to .621?
HighTechGeek said:
Thanks!
I found this guide to SBF from 2010... is there a more current process you recommend?
droidforums.net/forum/droid-x-rooted-help/100038-complete-droid-x-sbf-flashing-guide.html
Can you explain a little bit why not go to .621?
Click to expand...
Click to collapse
You can't flash any roms or root from .621. And it is impossible to downgrade from .621 to any other firmware.
Sent from my DROIDX using Tapatalk
Can you point me to a current step by step guide of how to SBF to .602?
From what I've read in the 2010 posts, it seems pretty advanced and didn't always work. Maybe it's been streamlined by now?
infazzdar said:
You can't flash any roms or root from .621. And it is impossible to downgrade from .621 to any other firmware.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
He could SBF to .602, run OTA Rootkeeper, then take the .621 update.
Andy
AndreXX said:
He could SBF to .602, run OTA Rootkeeper, then take the .621 update.
Andy
Click to expand...
Click to collapse
yes but thenwhat if while flashing roms he happens to bootloop... then it is sbf to .621 and no more root. The general consensus is to avoid .621 like the plague until an exploit is discovered.
Thanks everyone. I think I'll try SBF to .602. I found a video tutorial here:
youtube.com/v/QkYsD4w8rHg
I'm still not sure why I can't get the OTA .605. It downlaods and reboots, but keeps failing to install. Otherwise, my phone is relatively fine (currently on Froyo). I am having trouble getting root back since I removed root (used z4root). I just wanted to backup some things before going to .602
Hello XDA, it has been a very long time since I have upgraded my droid x, and I have decided to finally take action.
I am currently running an old build of Liberty Mod that I installed a very long time ago for Android 2.2.1.
I have heard negative things about the newest update, so I was just wondering where I should find the correct update file for upgrading to the current rootable OTA and installing cyanogen.
All help is appreciated.
I was in a similar situation myself so I might've able to help. What I did was sbf to 2.2 (not sure of the sbf file name) then took the OTAs till I got to .605 (this was before the .621 was in soak test). Then I rooted and flashed cm. now since the .621 OTA is live you will have to be careful. I would suggest doing what I did except watch the name of the OTA VERY CAREFULLY. If you get prompted for the .621 do not take it as it is unrootable currently. I can get you links later when I'm at my computer if needed.
twisted_58 said:
I was in a similar situation myself so I might've able to help. What I did was sbf to 2.2 (not sure of the sbf file name) then took the OTAs till I got to .605 (this was before the .621 was in soak test). Then I rooted and flashed cm. now since the .621 OTA is live you will have to be careful. I would suggest doing what I did except watch the name of the OTA VERY CAREFULLY. If you get prompted for the .621 do not take it as it is unrootable currently. I can get you links later when I'm at my computer if needed.
Click to expand...
Click to collapse
Thank you for the response. I see what you did worked, but I also found an interesting post on rootzwiki that would imply all you have to do is wipe, install the .605 AIO and then install the current CM4DX-GB. Should I just follow that guide?
Upgrading to .605 is really unnecessary. You can flash all Gingerbread and ICS roms from .602.
You just need to SBF to .602. From there you will be able to root and install CyanogenMod.
Sent from my DROIDX using Tapatalk
infazzdar said:
Upgrading to .605 is really unnecessary. You can flash all Gingerbread and ICS roms from .602.
You just need to SBF to .602. From there you will be able to root and install CyanogenMod.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. I went ahead and formatted, installed the team black hat .605 AIO, and then wiped again and installed cm4dx-gb. I'm really loving CM7 and Gingerbread. Thank you very much for all of the responses. This thread can be closed now.