Upgrade Nexus 5X to Oreo?

I have a Google Nexus 5X with a Ting GSM SIM. I'm still running Android Nougat (7.1.2) and when I check for updates the phone cheerfully tells me it is up to date. (My wife has the same phone on Verizon and was updated weeks ago.) The update has been out about a month and I believe I should have gotten it. Is the delay the result of the carrier (TMO?) I thought the Nexus phones purchased from Google got updates directly from Google? Any insight into getting Oreo on my phone is most welcome! (I still have a Ting CDMA sim and could switch to that if it would make a difference.)

I've also tried sideloading this following directions at https://developers.google.com/android/ota but when I put the phone into recovery mode it does not appear in the ADB device list.

 

Thanks!

0

Comments

8 comments
  • Hank,

    You're right that updates are delivered directly from Google for your Nexus 5X. Updates aren't instant though, and can take more than a month to populate across all devices so as to not cause the servers to go down when everyone tries to get it at once.

    Your SIM shouldn't make a difference, and it's likely your IMEI just has not gotten the green light from Google to get the update. It should happen shortly, though.

    As for side-loading, you'll need to remember to turn on ADB debugging and grant access on the phone when the computer prompts for it.

    0
    Comment actions Permalink
  • Hi Mitch, thanks for the reply. I know that Google stages the updates (first for a post beta test and then later to spread out the load on the servers.) I would have thought that everyone would be updated by now.

    For sideloading, I have enabled developer mode and USB debugging. I can put the phone into recovery mode but it then no longer appears in the device list. If you have any insight into this, please see my post at XDA forums. https://forum.xda-developers.com/nexus-5x/help/adb-lists-device-phone-recovery-mode-t3680181

     

    0
    Comment actions Permalink
  • Several older posts suggest it because your device drivers are out of date, but that makes no sense on Linux. As you're using Linux, you don't need to update the drivers. BUT i did find something that suggests you use a community-maintained set of adb tools:

     

      • Ubuntu Linux: Use apt-get install to install the android-tools-adb package. This gives you a community-maintained default set of udevrules for all Android devices.

        Make sure that you are in the plugdev group. If you see the following error message, adb did not find you in the plugdev group:

        error: insufficient permissions for device: udev requires plugdev group membership

        Use id to see what groups you are in. Use sudo usermod -aG plugdev $LOGNAME to add yourself to the plugdev group.

        The following example shows how to install the Android adb tools package.

        apt-get install android-tools-adb
    0
    Comment actions Permalink
  • Thanks for the additional followup. I've installed the package and confirmed I'm in the plugdev group. I even rebooted to be certain that all changes are complete. I can now execute the 'adb' commands w/out being root but the behavior is otherwise unchanged. Once in recovery mode, the phone no longer shows up in the device list.

    OK, made some progress. I unlocked the bootloader in Developer options. (I'm not sure if this matters) The device still didn't show up in recovery mode. At that point I started poking at the switches (power and both volume switches) and suddenly there was a menu of options, one of which was "apply update from ADB". I selected and executed that and it prompted me (on the device screen) to execute the "adb sideload <filename>" command. At this point the phone did appear in the ADB device list on the PC and I executed the command. Download has finished, bottom of screen (on phone) says "Install from ADB complete." and the menu entry "Reboot system now" is selected.

    Rebooting now (fingers crossed. ;) )

    0
    Comment actions Permalink
  • Update is complete - thanks for your help.

    I snagged a picture of the recovery menu (post download) if you're curious 
    about what it looks like.

    0
    Comment actions Permalink
  • Odd that it required the sideload command, but glad it worked! Do you have a favorite feature of Oreo yet?

    0
    Comment actions Permalink
  • No favorite features yet. (Other than new and shiny. :) ) Two areas I hope to see improvements in are battery management and RAM usage. I bought this phone when it first became available and at nearly two years old the battery is getting weak. I usually need to charge it in the evening as well as overnight these days. RAM seems to be becoming more of a problem. It used to be that when I started navigation on the phone and switched to another app, I could always return to navigation from the notification shade. That is no longer true. If I open the MP3 player or look at Now cards and open a browser, Nav gets killed. To get navigation back I need to open maps and start from the beginning. There is frequently a 5 second or so delay when returning to the home screen and I just know that in the background Android is juggling activities and finding enough RAM to restart the home screen. It was a bad decision to cripple the phone with insufficient RAM, but I guess that's a discussion for another day.

    0
    Comment actions Permalink
  • I suppose I'll wait to upgrade my phones to Oreo till they squash a few of those bugs. Thanks for being a software guinea pig.

    0
    Comment actions Permalink

Please sign in to leave a comment.