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

Gingerbread 2.3 was here, then gone, now it's back

When will VZW push a fixed GB OTA

  • 10/11/11

    Votes: 0 0.0%
  • 10/17/11

    Votes: 0 0.0%
  • 10/24/11

    Votes: 0 0.0%
  • 10/31/11

    Votes: 3 2.8%
  • 11/07/11

    Votes: 2 1.9%
  • 11/14/111

    Votes: 22 20.6%
  • 11/21/11

    Votes: 6 5.6%
  • Don't care (rooted already, etc)

    Votes: 23 21.5%
  • Before Christmas

    Votes: 12 11.2%
  • Never, the lobsters ate all the testers so it got cancelled

    Votes: 11 10.3%
  • It isn't coming at all now

    Votes: 13 12.1%
  • Any minute now

    Votes: 1 0.9%
  • Immediately after Jimmy Hoffa's body is found

    Votes: 4 3.7%
  • The day after the apocalypse

    Votes: 1 0.9%
  • Sometime after the sun goes supernova

    Votes: 9 8.4%

  • Total voters
    107
  • Poll closed .
Once again, upon auto rebooting, the device hung at the "eye", and once again, pulling and re-inserting the battery let it come up cleanly.

Glad you had no problems, but I would HIGHLY advise AGAINST doing this. At the onset of the update, it indicated that it would take somewhere around 10 to 15 minutes to run and if you let the update complete itself, that's exactly how long it takes. I received both updates today as well, and while the phone stopped at the Droid "eye" for several minutes, it eventually came back up just fine.

ANYTIME you pull the battery while the phone is doing its own thing (powering up, powering down, or updating), you stand a HUGE risk of losing a LOT of information. I know - I accidentally messed with the battery during a power down and lost 90% of my apps and other info. So - DON'T DO IT!!! Let the phone do its own thing during updates. Trust me, it's NOT worth it to get impatient!


P.S. Remember to sync your apps with App-Brain on a regular basis just in case something dreadful DOES happen!
 
  • Like
Reactions: Deleted User
Upvote 0
Glad you had no problems, but I would HIGHLY advise AGAINST doing this. At the onset of the update, it indicated that it would take somewhere around 10 to 15 minutes to run and if you let the update complete itself, that's exactly how long it takes. I received both updates today as well, and while the phone stopped at the Droid "eye" for several minutes, it eventually came back up just fine.

ANYTIME you pull the battery while the phone is doing its own thing (powering up, powering down, or updating), you stand a HUGE risk of losing a LOT of information. I know - I accidentally messed with the battery during a power down and lost 90% of my apps and other info. So - DON'T DO IT!!! Let the phone do its own thing during updates. Trust me, it's NOT worth it to get impatient!


P.S. Remember to sync your apps with App-Brain on a regular basis just in case something dreadful DOES happen!

Absolutely right...it will take SEVERAL minutes of sitting on the boot screen to load. Leave it be. I'd seriously give it 30 minutes or MORE before I'd even consider pulling the battery. That's supposed to happen, and you can seriously frak up your phone by pulling the battery before it loads on it's own.
 
Upvote 0
I just got the notice for the second update, and I'm running the mcsense rom.

Was it perhaps based on the GB leak? If so, I'm not surprised. I think a lot of people will experience this since they finally have a new build not yet seen by the devs. The build.prop edit would probably work for you euph:

ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.3.4/GRJ22/222219:user/release-keys

The 222219 is the final build. If you edit to that, it should stop the nag if you're interested. That said, there will be new roms tomorrow.
 
Upvote 0
Count me as another who didn't have room for the update. 13 hours after getting the original update, I get the second and start the install. It wasn't until after it restarted that I got the message that I didn't have room.

Anyone have any ideas how I can get this update?

You can download it direct from here to your PC:

http://android.clients.google.com/pa...ase_222219.zip

Rename to update (most likely) or update.zip depending on how your computer handles file extentions (most PC's automatically add the .zip so if you add it again you end up with update.zip.zip). Place newly renamed file onto SD card, goto hboot, use volume keys to highlight recovery, the power button to select. Now press volume up to get list of recovery options. Use volume keys again to scroll to the update.zip option and press power button to select, don't interrupt the update. It would be wise once you're booted back up to do a factory reset IMO.

I think there were 3 possible updates:

1.) 4.06.605.2
2.) 4.06.605.3
3.) 4.08.605.2

You'd only use the above method if you were sitting on 4.06.605.3 already and failed the final leap to 4.08.605.2. Unfortunately, it's more confusing than usual due to the mulitple patches.
 
Upvote 0
Haven't found a spot where this question fits really well, so I'll just shove it in here.

I got the 4.06 update yesterday, and ten tonight got a notice about 4.08. I gave it the go ahead and walked away. Came back a little later to see a message saying there wasn't enough memory (on my HTC Incredible). So I dutifully moved some stuff over to the SD card. Now when I check for system updates, it says I'm up-to-date even though I still have 4.06. Did I make it mad? Is it likely it'll give me a second chance?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones