• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

2.3.340 is here! Post your experiences

Got the update over Wifi and it installed fine here in SoCal.
 
With my update failing, can I sbf to 2.3.31 or 320 and then update?

Should that definitely work? That gives me a totally stock phone? Do I have to use 310, or is the update working from 320 too?

How do I do that?
 
AshG said:
Quick update, didn't take too long to download over wifi and the install went just as quickly. Lost root in the process; Z4 still works for rooting so they haven't patched the exploit.
Click to expand...



Thats strange because I didnt loose my root with the update, I also used z4.


BKVic
 
Checked for update about 5 a.m. EST, it was available. Took less than a minute to download and 3 or 4 minutes to install. No problems. I'm on a stock DX
 
My update went without a problem. I was rooted and didnt loose root during the update. Dont know why others are.


BKVic
 
Cetrian said:
Just did the update. Downloaded quickly over WiFi and took about 2min to install.
I was: Rooted (Universal Androot) and with Rom Manager, Koush Bootstrap, but otherwise 2.3.15.

[Results]
All looks good! Except I lost root. (no surprise).
Universal Androot (1.6.1) does NOT work.
Z4 Rooted just fine :)
Clockwork Recovery still installed and working (!?)
Boots 4 seconds faster.
Seems to take longer to load widgets (never timed my time-to-fully-booted)

[Versions]
System: 2.3.340.MB810.Verizon.en.US
Android: 2.2.1
Baseband: BP_C_01.09.07P
Kernel: 2.6.32.9-g55626e1, w30471@il93lnxdroid08 #1
ERI: 5
PRL: 52105
Click to expand...

I got the same results. I was originally rooted with Z4 Root (not Universal Androot). After I re-rooted with Z4, the phone rebooted and when right into Clockwork Recovery v2.5.0.6. Making a back up right now.

One question though (and I have not checked my Bootloader #), does this mean that we can or can not use the newest SBF file. I while probably be able to answer this when my phone finishes with the back up and I can boot to the bootloader screen. Just curious...

One difference that I have noticed is that my PRL is 52189 not 52105.

Okay, Bootloader is 30.04, so I am quessing that that means the newest .sbf file release a couple of days ago is fine to use. That means that everyone that updates should delete all of the backups prior to their update to 2.3.340. Any attempt to flash a back up will not have happy results.
 
Updated my X this AM. Installation went perfectly on stock X.

The phone is much smoother and slicker. Going left and right on the home pages is much faster. Overall, very good.

One issue however. I watch a local news channel on my X via streaming the video from their web site. I go to the web site, log in, click the video and, make it go full screen via holding the video tile and choosing the full screen button in the upper left hand corner. Now, when I do that, the video is very choppy and barely plays.

Now, I need to use the full screen button in the lower right corner of the video for it to play properly. The full screen button that's part of the web page as opposed to the one that pops up when you hold the video down. Very strange.

I also noticed that Flash was updated, I wonder if the Flash updated hosed something.
 
Makes ya wonder if this update fixes the SMS issues of them being out of order and receiving duplicate messages? The release notes do not mention that however that doesn't mean anything......
 
AshG said:
A link to Madden 2011 is perma-installed. LauncherPro will hide the link, or use your favorite root tools to make it go away more permanently. This is a practice Verizon needs to stop.
Click to expand...

That is complete bull****. If I want to delete something on MY phone I shouldn't have to root or install another program to remove it. I might download Launcherpro, I t hought you had to pay for it though.
 
I am rooted and deodexed, running the Black Glass 928 theme...other than that I am stock running OTA froyo.

I understand that I will lose root with this .340 update, but it appears that root can be reinstated with Z4 Root.

The question is will I have to go back to being ODEXED prior to installing this latest update? ...or should the fact that I am deodexed be a non-issue? :confused:

Thanks,
Kevro
 
I woke up this morning with the update waiting on my phone. I'm rooted but no custom ROM's (my build.prop, boot logo, and "DROID eye" have changed though).

It looks like it does some type of "sanity" check when the update starts. Mine had barely started and it rebooted again (and then I got the update failed message).

Question though, does it just wipe out the update if it fails? Shouldn't the "update.zip" still exist on the phone to update manually?
 
crboone said:
No update even available for my phone whatsoever yet. I'm in NC.
Click to expand...

I'm in Hickory, NC and the update was available for me when I woke up at 6:30 this morning. Installed no problem (stock Droid X). Overall seems smoother, and the screen lock slider seems to work more smoothly as well (finally!).
 
TLDspectre said:
I'm in Hickory, NC and the update was available for me when I woke up at 6:30 this morning. Installed no problem (stock Droid X). Overall seems smoother, and the screen lock slider seems to work more smoothly as well (finally!).
Click to expand...

Wonder why mine would tell me I'm up to date when I'm still on 2.3.15? It's like it just bypassed my phone for some reason. Or my area maybe? Might have to get the file when it's available online. (Or maybe they push it out according to some other grouping method).
 
Downloaded this morning...I am rooted, but have not done the rom and all that. as the only thing that I use my root for is tethering no problem...root still intact...after work will play some more.
 
I had to pull the update, I tried it 4 times and I got the software updat failed message, WTF? I called verizion and the tech said that I have mto wait till the update is pushed to the phone rather than pulling it manually? So, I sit here waiting for them to puch it to my phone... but Icant honestly see that it matters which way I get the update? Like I told the teck... I still download the update, the phone re-boots then I get that stupid error message........

Frustration.....
 
Now that I think about it -- when I received the Froyo update I was one of the last ones. I got mine on the way home from vacation, and when I checked online at AndroidForums, others had gotten it during that week. So I may not receive it for a couple of days yet depending on how they push it out.

Just curious -- but do I need to rename my .bak files back to .apk in /system/app in order to update successfully? I've seen this asked several times but I don't think I've seen the answer yet.
 
You must log in or register to reply here.
Back
Top Bottom