Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Page 1 of 2 12 LastLast
Results 1 to 25 of 35
  1. Thread Author  Thread Author    #1  
    TaeKwonDonkey's Avatar

    Posts
    307 Posts
    Global Posts
    419 Global Posts
    ROM
    CM7.1

    Default No OTA yet...

    Still waiting for the official FRF85B OTA on T-Mobile in Washington D.C.
    I really don't want to manually update because I've already read some horror stories of it not working out or malfunctioning and I don't want to take any chances.
    Siemens CF62T> Samsung T329 Stripe Black> MyTouch 3G Black (Android 1.6 Donut)> Blackberry Bold 9700 (5.0.0.330)> Samsung T219 Brown (backup crap dumbphone)> Google/HTC Nexus One (CM7.2)> Google/LG Nexus 4 (Android 4.2.2)
  2. #2  

    Default

    Give it time. Remember, the 2.1-update1 took about a week to get sent out to the majority of units.
  3. #3  

    Default

    I manually updated. It ran slow for 1 day. Now it is blazing.
  4. #4  

    Default

    I never did get the OTA. I got tired of waiting and ran the manual install.

    The update ran slowly at first, but now it is awesome.

    I have a few complaints about some of the stock apps (email, contacts and calendar), but the performance is great overall.

    aviduser
    1995-Newton Message Pad 2000 | 1998-Palm V | 1999-Palm V8 (upgrade) | 2000-Palm m505 | 2001-Palm m515 | 2003-Kyocera 7135 | 2004-Treo 600 (woc) | 2006-Treo 700p (wc) | 2007-Treo 680 (wc) | 2008-Another Treo 680 (wc) (unlocked) | 2010-Google Nexus One | 2011-NookColor (hacked) | 2012-Galaxy Nexus | 2012-Samsung Galaxy Tab 8.9 wifi
  5. #5  
    88 FLUX's Avatar

    Posts
    710 Posts
    Global Posts
    1,221 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by TaeKwonDonkey View Post
    Still waiting for the official FRF85B OTA on T-Mobile in Washington D.C.
    I really don't want to manually update because I've already read some horror stories of it not working out or malfunctioning and I don't want to take any chances.
    The only horror stories are from those who were rooted or from those who were doing it incorrectly (such as naming the file update.zip.zip due to them not realizing that Windows hides known file extensions by default). If you do it correctly, it is extremely simple and the process the phone goes through for installation is exactly what the OTA will do for you anyways.
    Current: Motorola Nexus 6, ASUS Nexus 7 (2013), Moto 360

    Standby:
    Motorola Moto X (2013), Samsung Galaxy S3, LG Nexus 4, Samsung Galaxy Nexus, HTC Thunderbolt, HTC Nexus One, ASUS Nexus 7 (2012), Motorola Xoom
    Thanked by:
    melwan 
  6. #6  

    Default

    Still waiting too... T-mobile Baltimore

    I cannot even find the manual update for unmodified Nexus ERE27... I find only incremental ones.
  7. #7  
    88 FLUX's Avatar

    Posts
    710 Posts
    Global Posts
    1,221 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by ikshaar View Post
    Still waiting too... T-mobile Baltimore

    I cannot even find the manual update for unmodified Nexus ERE27... I find only incremental ones.
    http://android.clients.google.com/pa...5.dc39ca1f.zip
    Current: Motorola Nexus 6, ASUS Nexus 7 (2013), Moto 360

    Standby:
    Motorola Moto X (2013), Samsung Galaxy S3, LG Nexus 4, Samsung Galaxy Nexus, HTC Thunderbolt, HTC Nexus One, ASUS Nexus 7 (2012), Motorola Xoom
  8. #8  

    Default

    I still want to do this OTA, instead of sideloading, just to see it work. I've side loaded other android devices, so the thrill of that has passed.

    But how many N1s are out there anyway that they have to push this so slowly?

    Is there any reason to keep doing checkin ? And is there any reason to believe "check for new update" actually does anything other than look for the zip on the SD card?
  9. #9  

    Default

    Thanks Ock. I took the jump. Scary and took sometimes after reboot to get back to normal, few things were hanging for a while, but seems normal now.
  10. #10  
    z0phi3l's Avatar

    Posts
    121 Posts
    Global Posts
    123 Global Posts

    Default

    Quote Originally Posted by ock View Post
    The only horror stories are from those who were rooted or from those who were doing it incorrectly (such as naming the file update.zip.zip due to them not realizing that Windows hides known file extensions by default). If you do it correctly, it is extremely simple and the process the phone goes through for installation is exactly what the OTA will do for you anyways.
    Tried it twice and always gets stuck on the second reboot, and gets stuck on static N1 logo, I know I have the correct version yet it fails, tried the original leak and twice with the official version, not really sure anymore what it could be
    Thanked by:
  11. Thread Author  Thread Author    #11  
    TaeKwonDonkey's Avatar

    Posts
    307 Posts
    Global Posts
    419 Global Posts
    ROM
    CM7.1

    Default

    Quote Originally Posted by z0phi3l View Post
    Tried it twice and always gets stuck on the second reboot, and gets stuck on static N1 logo, I know I have the correct version yet it fails, tried the original leak and twice with the official version, not really sure anymore what it could be
    This is exactly what I mean. If that happened to me, I'd probably pee in my pants. I'm not gonna do any side loading/flashing/rooting until theres a Nexus Two in my hands

    Also I've been running a checkin (*#*#2432546#*#*) everyday with no luck. It doesn't even find if I have any apps that need updating.
    Siemens CF62T> Samsung T329 Stripe Black> MyTouch 3G Black (Android 1.6 Donut)> Blackberry Bold 9700 (5.0.0.330)> Samsung T219 Brown (backup crap dumbphone)> Google/HTC Nexus One (CM7.2)> Google/LG Nexus 4 (Android 4.2.2)
  12. #12  
    kC_
    kC_ is offline
    kC_'s Avatar

    Posts
    78 Posts

    Default

    I just got ota frf91
  13. #13  

    Default

    Quote Originally Posted by kC_ View Post
    I just got ota frf91
    Pictures or it didn't happen.
  14. #14  
    88 FLUX's Avatar

    Posts
    710 Posts
    Global Posts
    1,221 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by kC_ View Post
    I just got ota frf91
    Quote Originally Posted by icebike View Post
    Pictures or it didn't happen.
    icebike, normally I'd be right there with ya calling bluff (as many have seen ) but this time, FRF91 is quite real. Found this over at xda...

    http://android.clients.google.com/pa...B.db99fdf1.zip
    Current: Motorola Nexus 6, ASUS Nexus 7 (2013), Moto 360

    Standby:
    Motorola Moto X (2013), Samsung Galaxy S3, LG Nexus 4, Samsung Galaxy Nexus, HTC Thunderbolt, HTC Nexus One, ASUS Nexus 7 (2012), Motorola Xoom
  15. #15  

    Default

    I saw it there too.
    I was mostly just pulling his chain due to the huge dustup in the forum in past days.
  16. #16  
    88 FLUX's Avatar

    Posts
    710 Posts
    Global Posts
    1,221 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by icebike View Post
    I saw it there too.
    I was mostly just pulling his chain due to the huge dustup in the forum in past days.
    haha. well in that case...........


    kC_, no, you didn't get an OTA to FRF91. But nice try trying to be the new "cool kid". I want full video proof, a copy of logcat, a blood sample, and your next child.
    Current: Motorola Nexus 6, ASUS Nexus 7 (2013), Moto 360

    Standby:
    Motorola Moto X (2013), Samsung Galaxy S3, LG Nexus 4, Samsung Galaxy Nexus, HTC Thunderbolt, HTC Nexus One, ASUS Nexus 7 (2012), Motorola Xoom
  17. #17  
    gchild00's Avatar

    Posts
    21 Posts
    Global Posts
    28 Global Posts

    Default

    Quote Originally Posted by ock View Post
    The only horror stories are from those who were rooted or from those who were doing it incorrectly (such as naming the file update.zip.zip due to them not realizing that Windows hides known file extensions by default). If you do it correctly, it is extremely simple and the process the phone goes through for installation is exactly what the OTA will do for you anyways.
    yes for windows users all you have to do is change the downloaded zip file to "update" and not "update.zip"...i was trying to change it to "update.zip" and I kept getting the error message until i simply named it "update" and all was right in the world
  18. #18  
    melwan's Avatar

    Posts
    177 Posts
    Global Posts
    472 Global Posts

    Default

    I installed 85B manually cause the OTA seemed to take 4ever. Just ran a checkin and it prompted me with the new 91 update.

    @gchild00 That's why I always set it to show extensions. It makes life easier lol
    Thanked by:
  19. #19  
    88 FLUX's Avatar

    Posts
    710 Posts
    Global Posts
    1,221 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by melwan View Post
    I installed 85B manually cause the OTA seemed to take 4ever. Just ran a checkin and it prompted me with the new 91 update.

    @gchild00 That's why I always set it to show extensions. It makes life easier lol
    I keep doing checkin but haven't gotten OTA yet. I'm gonna wait for OTA just for the hell of it. Lol

    And yeah, I agree on the file extensions. As a technician and sysadmin for a Windows environment, I never keep extensions hidden (or hidden/system files).
    Current: Motorola Nexus 6, ASUS Nexus 7 (2013), Moto 360

    Standby:
    Motorola Moto X (2013), Samsung Galaxy S3, LG Nexus 4, Samsung Galaxy Nexus, HTC Thunderbolt, HTC Nexus One, ASUS Nexus 7 (2012), Motorola Xoom
  20. #20  
    johnchen3's Avatar

    Posts
    7 Posts
    Global Posts
    11 Global Posts

    Default

    Anyone on at&t get the 2.2 update yet?
  21. #21  
    Stephman's Avatar

    Posts
    36 Posts
    Global Posts
    254 Global Posts

    Default

    Will the OTA show up on an AT&T N1 that's connected via WiFi and NO SIM card installed?

    My SIM is in another phone right now while I wait for a microSIM adaptor.

    Thanks
  22. #22  
    melwan's Avatar

    Posts
    177 Posts
    Global Posts
    472 Global Posts

    Default

    Quote Originally Posted by Stephman View Post
    Will the OTA show up on an AT&T N1 that's connected via WiFi and NO SIM card installed?

    My SIM is in another phone right now while I wait for a microSIM adaptor.

    Thanks
    You NEED the SIM to get the OTA. Some even say you need to disable Wifi, but not too sure about that.
  23. Thread Author  Thread Author    #23  
    TaeKwonDonkey's Avatar

    Posts
    307 Posts
    Global Posts
    419 Global Posts
    ROM
    CM7.1

    Default

    Quote Originally Posted by melwan View Post
    You NEED the SIM to get the OTA. Some even say you need to disable Wifi, but not too sure about that.
    Don't know the validity of your statement but I'm not turning my Wifi back on until I get the OTA update lol
    Siemens CF62T> Samsung T329 Stripe Black> MyTouch 3G Black (Android 1.6 Donut)> Blackberry Bold 9700 (5.0.0.330)> Samsung T219 Brown (backup crap dumbphone)> Google/HTC Nexus One (CM7.2)> Google/LG Nexus 4 (Android 4.2.2)
  24. #24  
    Stephman's Avatar

    Posts
    36 Posts
    Global Posts
    254 Global Posts

    Default

    Quote Originally Posted by melwan View Post
    You NEED the SIM to get the OTA. Some even say you need to disable Wifi, but not too sure about that.
    Thanks for the info
  25. #25  

    Default

    I'm pretty sure having the SIM card in is a good idea.
    I just got my FroYo update after checking in. I had tried previously, but it didn't work until just now.
    It is build FRF91.
Page 1 of 2 12 LastLast

Posting Permissions