Database Users

Question about updating to 2.3.340

I've read some Android Forums but I can't seem to get my answers...
I need help updating to 2.3.340
I'm new to rooting and deoxeding my phone so I apologize If I have alot of questions....
I am currently on 2.3.15 , rooted and deoxed. My phone keeps prompting me to updating to 2.3.340.
Questions:
1. Should/Can I allow the update to take place automatically?
2. Will I lose my root access and will my phone not be deoxed?
3. Do I need to revert my phone back to stock then update automatically?
4. Is there a link on how to update to 2.3.340 when you have a rooted phone?
Any help is appreciated, thanks!

I'm also curious. I'm on the 2.2OTA-Rooted and my phone wants me to update.

1. Should/Can I allow the update to take place automatically? NO!!! not while it is as you have it now.
3. Do I need to revert my phone back to stock then update automatically? YES and be sure to uninstall any program related to rooting your phone before reverting to stock.

Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.

Not at all p3p... ask as many questions as you can... helps me out too..
I too would like to know what .Sbf and the other one stand for... lol I can't remember what it was...
So after we revert back to Stock.. (any link as to where to find the stock file?) Update automatically... then we follow the same procedures to re-root the phone?

purplem3pursuit said:
Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.
Click to expand...
Click to collapse
Hey wassup man? No ban stick here??
I also have the same questions...

m3n00b said:
Hey wassup man? No ban stick here??
I also have the same questions...
Click to expand...
Click to collapse
Nice to see great minds thinking alike The ban stick will rise again..

Bump to top to help myself and OP.
Any help is greatly appreciated.

Kapi187 said:
I've read some Android Forums but I can't seem to get my answers...
I need help updating to 2.3.340
I'm new to rooting and deoxeding my phone so I apologize If I have alot of questions....
I am currently on 2.3.15 , rooted and deoxed. My phone keeps prompting me to updating to 2.3.340.
Questions:
1. Should/Can I allow the update to take place automatically?
2. Will I lose my root access and will my phone not be deoxed?
3. Do I need to revert my phone back to stock then update automatically?
4. Is there a link on how to update to 2.3.340 when you have a rooted phone?
Any help is appreciated, thanks!
Click to expand...
Click to collapse
What I would do is SBF using the full .320 file and then do the .340 system only SBF and you will be on the most current version. Then download z4root its a one click root app which will give you root obviously. Then customize your phone to your liking.

joebob296 said:
What I would do is SBF using the full .320 file and then do the .340 system only SBF and you will be on the most current version. Then download z4root its a one click root app which will give you root obviously. Then customize your phone to your liking.
Click to expand...
Click to collapse
Um - if you are running 2.3.15 I would not recommend doing the sbf with the .320 file. I am just trying to be helpful -not a butt.
I would use the full sbf released for 2.3.15 which can be found at...
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
I just posted the guide I used to sbf here for another member...
http://forum.xda-developers.com/showthread.php?t=901934
Here is my understanding of your situation. You are getting prompted for the update. I THINK that even if you said yes and tried to run it - that you would just end up with an error - because the update checks your system to see if all the proper files are there and if they are not it will not run. I think.
So I think the best thing to do is sbf then take the update. You will loose root. and you will not be de-odexed. You will have to reroot. But like the other member said - get z4root (link in the other thread with the sbf instructions) and run it after you do the over the air.
I make no guarantees. Just sharing to the best of my knowledge.

thepolishguy said:
Um - if you are running 2.3.15 I would not recommend doing the sbf with the .320 file. I am just trying to be helpful -not a butt.
Click to expand...
Click to collapse
Flashing the .320 full SBF then the sys only .340 SBF would be the same as the .15 SBF to OTA. Six of one, half a dozen of the other.
purplem3pursuit said:
Kapi187.. Hope you don't mind if I add some questions to your thread... It seems our questions are running along the same lines.
I too have been reading quite a bit about the upgrading process and am trying to figure out a few things.. Likewise, some of them may sound "noobish" but please bare with me...
My understanding is that the 2.3.34 update is available OTA (I am currently running 2.3.15 as well).. Is it necessary to revert to a stock sbf (what does sbf stand for?)?
A breakdown of my current setup:
system version 2.3.15
Android version 2.2
Running JRummy V1.0 Rom
Odexed
rooted (obviously)
clockwork recovery installed (also obvious)
image available from pre-rom condition
How should I go about updating to 2.3.34? Is it necessary/ is there a purpose? What are the advantages to doing so?
I have a friend with a Nexus One and he doesn't need to update any system version so we have been discussing back and forth trying to understand the droid x/verizon system.
All help is greatly appreciated... And hopefully this will help others.
Click to expand...
Click to collapse
SBF stands for SmartBroker Data File, but that doesn't matter, it's simply a backup file. It's not necessary to upgrade to .340 unless you use custom ROMs, because anything made for .320/.340 isn't compatible with .15. The Nexus One doesn't have a system version because it's pure android; the android version is the system version. Other phones have a separate system version because the carriers feel the need to bog the phone down with bloatware and their custom launchers.
SBF files can be found here, and make sure you make a backup immediately after you're re-rooted, so you can just restore it to accept the next OTA.

mlclm said:
Flashing the .320 full SBF then the sys only .340 SBF would be the same as the .15 SBF to OTA. Six of one, half a dozen of the other.
SBF stands for SmartBroker Data File, but that doesn't matter, it's simply a backup file. It's not necessary to upgrade to .340 unless you use custom ROMs, because anything made for .320/.340 isn't compatible with .15. The Nexus One doesn't have a system version because it's pure android; the android version is the system version. Other phones have a separate system version because the carriers feel the need to bog the phone down with bloatware and their custom launchers.
SBF files can be found, and make sure you make a backup immediately after you're re-rooted, so you can just restore it to accept the next OTA.
Click to expand...
Click to collapse
Excellent information! So when utilizing my own backup (or the SBFs presented above), do I need to uninstall clockwork or root before going after the OTA? I am figuring the OTA isn't looking for that information but want to avoid the infamous brick situation at all costs.

No, you can leave everything installed. An SBF is similar to the factory reset disc that comes with computers; it formats everything and then installs the OS on a clean slate. An OTA won't check for root, but it does check for the bloatware. If any of it is missing/renamed, it won't install the update.

Anyone manual root .596 yet?

I would like to use this post to document any way to manual root .596 gingerbread. I know p3droid is doing awesome work building prerooted updates but having a manual route is always nice.
Thank you everyone.
Edit...mistyped version number.
Sent from my DROIDX using XDA App

....
Its .596 ................

I did. Since I was on the .595 and I had the older radio, I had to SBF back to 2.3.340 first and because of that I had to lose my recent data (last froyo nandroid was two months ago). Anyways it seems to be nearly identical to the .595 once it is up and running. My two cents

I have an X that's running stock Gingerbread, and I'd like to root it. So a manual root method that doesn't require SBFing back to Froyo would be very welcome...

Why does everyone act like SBF'ing is so hard? It takes ten to fifteen minutes and has the same amount if not less risk than flashing a rom

It's not that it is hard, but at least I would hate to loose all my data & time spent setting up the phone.
But if this is the only method of getting root I will be sbf'ing soon. But I wonder what this means for the Droid X2 which I assume is already on GB 596 out of the box. So can the X2 not ever be rooted since there is no 340 to go back too???

I am also curious about manual rooting. I don't have a problem SBF'ing and have done it many times. I would like to learn more about Android and its internals.
Sent from my DROIDX using Tapatalk

cspell said:
It's not that it is hard, but at least I would hate to loose all my data & time spent setting up the phone.
Click to expand...
Click to collapse
I used Titanium Backup to backup all apps and user data, then restore after the upgrade to GB. Don't have to spend a ton of time setting up the phone.

It's the configuring the phone, not the SBF that's the issue
I concur -- SBF is simply, straight forward and quick. The problem is the amount of time it takes to get the phone set up again, especially moving from one flavor of Android to another. I've got 15 minutes to SBF. I don't have the hour or two to fiddle with the apps, configurations, etc.
So I second the call for a method to root stock Gingerbread. I miss my ad blocker...

I have read that gingerbreak works intermittently on some but not all .596 droid x's.
Current method to root works fine thanks to P3droid method 2. If you already have a prerooted 2.2 running the latest OTA you just need two files to install and you will have a .596 rooted droid x. If you jumped the gun and installed the OTA... then yes you need to find a way to root your .596...
Setting up SBF for the first time is not difficult just a little scary. Luckily there are alot of guides out there to help and the bootloader didn't change. Good luck!

cspell said:
I
But if this is the only method of getting root I will be sbf'ing soon. But I wonder what this means for the Droid X2 which I assume is already on GB 596 out of the box. So can the X2 not ever be rooted since there is no 340 to go back too???
Click to expand...
Click to collapse
its kinda weird but the droid x2 shipps with 2.2.2, just the newer form of blur like the gingerbread droid x has. Also, it has been able to be rooted by gingerbreak so i guess there's some hope.

[Q] Going from 2.2.1 to Gingerbread

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.

[Q] Updating to .621 OTA?

Hi my friend's droid x was on a leaked version of gingerbread (4.5.588) and since it's been incredibly buggy I convinced him to try to update it to the latest version. Being a leak, obviously system updates won't work.
I found this file online of the .zip: http://dl.dropbox.com/u/60354155/Blur_Version.4.5.621.MB810.Verizon.en.US.zip
The thing is it's only 15 MB, which makes me a little hesitant if it's a good .zip
If not, could anyone direct me to the official .621 update.zip? Thanks.
Edit: Actually, does someone have a link to the .602 official update? I can't find it anywhere online since a lot of the links were removed or on megaupload.

Actually, you should probably SBF to .602.
It will make sure that your phone won't have any leftover files after upgrading, and will ensure optimum perforemence.
Just Google "1kds 602 Linux SBF" and it should lead you to the files and instructions you need.
One last thing, instead of upgrading to .621, you should stay on .602, root, and flash one of the many great roms available.
Sent from my DROIDX using Tapatalk

infazzdar said:
Actually, you should probably SBF to .602.
It will make sure that your phone won't have any leftover files after upgrading, and will ensure optimum perforemence.
Just Google "1kds 602 Linux SBF" and it should lead you to the files and instructions you need.
One last thing, instead of upgrading to .621, you should stay on .602, root, and flash one of the many great roms available.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Well I'm updating him to .596 right now. Will that allow system updates since that's official?

[Q] 2.3.4 sbf for D2 or R2D2

Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
****SOLUTION POSTED AT THE END*****
The sbf has been leaked, and is available:
Here:
http://sbf.droid-developers.org/
and Here:
goo.gl/9SdIy

JerrytheGreat said:
Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
Click to expand...
Click to collapse
I think I'm in the same boat.

Hey guys I can upload a .sbf later tonight.
Sent from my DROID2 using xda premium

Where did you get it?
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg

JerrytheGreat said:
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg
Click to expand...
Click to collapse
I have the gingerbread sbf for the droid2

Gingerbread 2.3.3 will not work-MUST be 2.3.4
Thanks for the offer, but the Gingerbread 2.3.3 floating around the Internet will not work- the SBF MUST be 2.3.4, what was just realeased as an OTA 1 week or so ago.
Now, if someone stumbles across this thread, please note you CANNOT "downgrade" the R2D2 after the 2.3.4 OTA, as Verizon also updated the bootloader. If you try to downgrade to 2.3.3, you will brick the phone until the 2.3.4 sbf gets leaked.
From what I have seen, I am one of 3 people to create bricked R2D2s trying this, now waiting for a 2.3.4 leak to bring his/her phone back from the dead.
If you are indeed looking for the VZW 2.3.3 sbf, stockroms.net has it.
-jtg

same, identical problem!!!!

Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481

MissionImprobable said:
Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481
Click to expand...
Click to collapse
Thats 2.3.3
Not 2.3.4
So it's actually not amazing.

Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...

JerrytheGreat said:
Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...
Click to expand...
Click to collapse
sadly i do believe my r2d2 has suffered the same fate as yours.. ive tried updatubg with both of the available from
stockroms . net/ file/ Droid2/ Droid2R2D2
Bootloader
D2.37
Err:A5,70,70,00,1F thou ive had several variations
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB Data Cable
this is what i get when i connect it.. it acts like its flashing but never does.... when it reboots it goes right back to the loader with same mem_map blank error
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00D237

Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.

chasehammer said:
Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.
Click to expand...
Click to collapse
Thank you, Captain Obvious, for restating the subject of this thread..

Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.

MissionImprobable said:
Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.
Click to expand...
Click to collapse
A. My batt life and stability tanked after the update, and I was fed up
B. Didn't think it through
C. I thought I could easily download the most recent sbf and reflash-but didnt check first to see its wasn't available.
D. I have a spare phone, so knew if I bricked it, I would be OK
E. I'm not shocked or mad, I'm already married, so enough told-you-so's

Same problem
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!

korydak1lla said:
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!
Click to expand...
Click to collapse
Ummmmm they dont want people to be able to root their phones.

Don't expect the sbf anytime soon as the Droid 2 is dead and pretty much nobody cares about it. :/

That's why I love me some MIUI. Also why Moto is on the bottom of my list for future upgrades. Sony is looking dead sexy about now.

Please Keep an Eye Peeled--Lots of People need this
Well this thread and about 4 others all drill down to the same issue.
We are all looking for a leaked 2.3.4 sbf for Verizon Droid2 or R2D2. Please all you people in the know keep your eyes peeled for a leak, and post the second it appears (if ever).
jtg