January 29, 2015

Froyo Build FRF83 Now Available for Nexus One Users

Another incremental Froyo build is being pushed out to Nexus One users.   This time it’s build number is FRF83.  If you are getting tired of FRF50, download the OTA right here and manually install it.  I should note that you must be running the FRF50 update.   The update will simply fail for users running FRF72 who try this.

Oh, and let us know if you find anything new!

Source: xda-developers



42 Comments

  1. Josh
    Reply

    Still waiting on a version of FroYo I can use on my AT&T Nexus One… I'm getting jealous of you guys with your FroYo goodness!

    • DarthDroid
      Reply

      just google it and download it yourself then update the phone. there are many websites that will show you how to do it step by step if you dont know how to do it yourself

    • daveloft
      Reply

      At least your running Froyo. I'm stuck with EPE54B 2.1update 1 build. Everyone running the T-Mobile version 2.1 has gotten 2 updates already and this third one. I'm done with being patient.

      If the source code is out, Froyo must be done. Just put all the versions for download on your site Google and be done with it.

  2. Dan
    Reply

    Others who are running FRF72 are reporting that they are getting FRF83 over the air. Keep an eye out for it over the next few days.

  3. Julius
    Reply

    "You know, I know this steak doesn't exist." I know I would be happier not knowing and just receiving the OTA update… or having a certain date which is probably unrealistic. :) Ahh the anticipation.

  4. James
    Reply

    I was on 72 and just manually updated to 83. Here's what I did.
    1. Download and rename "update" and copy to SD card. http://android.clients.google.com/packages/passio
    2. Turn off phone. Hold down trackball and power button.
    3. Select Bootloaded and Recovery. When shows logo press power and volume up and select "update.zip."
    That's it. No need to revert to 50 or 2.1. Now have FRE83.

    • dave
      Reply

      I tried it but it didn’t work with package from XDA developers and the link you put up is down…any way you can send me the package?

  5. staid
    Reply

    I just updated from 72 to 83 and now the market is showing me apps that have been missing since I went to FRF50. The FRF83 update also seems to have fixed the sluggish performance issue I was having with my Nexus, so far so good. I noticed that the FRF72 to FRF83 build was pretty small (under 700k), so I am assuming it was only some code fixes, but I am not sure.

  6. Mahama
    Reply

    yes, can confirm the update from frf 72 to frf 83
    protected apps are now visible!

    • James
      Reply

      I just manually did the FRF 83 zip from FRF72 and I can still not view protected apps… I think something is not so official about this "final" update.

  7. rolly
    Reply

    Followed James' instructions from 72 to 83….works fine…..: ) thanks! Now let's find out what is new.

  8. Ryan
    Reply

    Wondering if anyone that upgraded from 72 to 83 is experiencing trouble downloading apps from the market.

    I keep getting "Download Unsuccessful" when updating or downloading apps.

  9. mob
    Reply

    i had to reinstall swype after going from 72 to 83 again, but no big deal…haven't noticed anything else new…anyone else figure out any new features? and the real question is will t-mob or att block or disable any features when they ota it? i'll keep my 83 if they try to block mifi!!

    • Andy
      Reply

      I had swype running just fine, then updated to 83 and it stopped. The keyboard works in tap-tap-tap mode; but not in slidy-swype.

      Is that what you saw? And all it took was a re-install?

  10. mola
    Reply

    So much info about people wanting to get the update and no info on what the update even provides to see if it is worth the effort. Anyone have any info to share on experience, features or enhancements?

  11. James
    Reply

    I don't know if this is actually the final release since Google has not issued an official announcement. Makes me think it may not be the final release. We'll see.

POST A COMMENT.