How to get Android O beta 4 on your Pixel or Nexus (and how to roll back to Nougat)

The Android O Developer Preview 4 is here, and if you're looking to install it on your phone or tablet, you're now able to opt-in to the first public beta, which is also available as the second Developer Preview.

Which devices support the Android O Developer Preview?

The preview is supported on the following phones and tablets:

Pixel

Pixel XL

Pixel C

Nexus 6P

Nexus 5X

Nexus Player

Download the Android O beta

If you don't want to mess with unlocking your bootloader or the command line, the fourth Android O Developer Preview is part of the public beta. That means that if you have one of the above eligible devices, you can simply visit the Android Beta portal and opt-in to the beta, which will then prompt Google to send your phone or tablet an over-the-air update. If you're already in the public beta, you will receive an over-the-air update shortly.

Find the device you want to enrol in the Beta program and tap Enrol device.

Follow the prompts to accept the over-the-air download.

Note: To leave the beta program, simply press the button on the Android Beta program page to unenroll. Your phone will receive an over-the-air update to return to the stable version of Android 7.1.2 Nougat, but your phone will be wiped clean upon rebooting, so back up your stuff.

Install the Android Developer Preview from the command line

What you need to know beforehand

In order to update a phone or tablet to Android O this way, you need to first unlock your bootloader.

Before we go into these steps, it is strongly recommended that you have previous knowledge of working with the Android SDK (software development kit) and Terminal (OS X or Linux) or Command Prompt (Windows), as it is possible to harm your device if something were to go wrong in the following process.

You'll need to download an updated Android SDK that has the latest Android O tools and images, and you can grab it from the Android Development website and follow their instructions on how to install it correctly. For the following process all you will need is the adb and fastboot files which are located in the Platform Tools folder.

Additionally, all the following commands are written as they would be in Terminal on a Linux or OS X platform. If you are following this guide and using a Windows machine, you will not need to use the "./" seen in the guide.

Enable developer settings and USB debugging

Before you begin, you'll need to have a compatible Nexus or Pixel device running Android 7.x Nougat.

Go to your Settings and scroll down to About Phone/Tablet

Tap on the Build number seven times until the dialog box says you are now a developer

Go back to the Settings menu and you should find a new option called Developer options. Click into the Developer options

Make sure that the developer options are turned on and that USB debugging is checked on

Make sure Enable OEM unlock is checked.

Plug your device into your computer and click "OK" on the dialog box asking you to Allow USB debugging while connected to the computer. You can also select to always allow access on that computer

If done correctly, this will be everything you will need to do on your phone or tablet for the moment.

Unlocking your bootloader

Nexus devices and Pixel phones bought from Google directly have a bootloader you can unlock. If you want to manually flash software, you'll need to do this.

To do this you must first boot into your bootloader. You can either manually turn off your phone or tablet and hold down the power button and the volume down button to enter your device's Bootloader Menu or you can enter the following commands into your terminal or command prompt.

Run the following command to make sure your device is properly connected to your computer. If it returns a string of characters it means that you are all set to start updating your device.

./adb devices

Now to enter into the Bootloader menu just run the following command.

./adb reboot bootloader

At the bottom of the screen, there will be several things listed including the lock state of the device. This should say locked unless you have unlocked your bootloader in the past and never went back and locked it again.

To unlock your bootloader, which is required only when flashing a stock firmware image (not sideloading and update, which we'll get to soon), you must enter the following commands. Remember that when unlocking your Nexus' bootloader it will factory reset your device, so you will lose everything stored on it. If you have not yet backed up anything important on your device you can hit the power button while Start is highlighted in the Bootloader menu and this will boot you back into your device like normal. Now back to unlocking your bootloader.

Use the command:

./fastboot flashing unlock

A dialog will appear on the device asking if you are sure about unlocking. Again this will factory reset your device, so if you want to back out of the process you just need to select no with the power button. If you are ready to unlock your bootloader you press the volume up button and then the power button to confirm that you wish to unlock your bootloader.

./fastboot reboot-bootloader

It is recommended to reboot the bootloader just to give itself a check to make sure everything is working correctly before moving onto the next step.

Flashing the stock firmware image

Now that your bootloader is unlocked, it's time to flash the Android O image. To find the system images, head on over to the Factory Images page, find your device, and download the latest factory image available. It is easiest to then uncompress the file in the Platform Tools folder where the adb and fastboot files are so that you don't have to type the path to the different files when flashing the firmware. (Or if you know that you can drag a file into a terminal window to copy the path, just do that.)

To begin, make sure you are still in the bootloader menu on your device and double check that your bootloader is in fact unlocked.

First, make sure that your computer is communicating correctly with your phone or tablet. As long as your device's serial number comes back as a connected device you are ready to begin updating your device.

./fastboot devices

Now it is time to flash the updated bootloader with the following command.

./fastboot flash bootloader [bootloader file].img

You will not see anything on the screen of your device but there should be a dialog in your terminal or command prompt. When it is done flashing the bootloader you should reboot back into the bootloader as to make sure everything is still working correctly.

./fastboot reboot-bootloader

Next you flash the updated radios. This step is only necessary if you are updating the firmware of a phone or tablet that has cellular radios built into it.

./fastboot flash radio [radio file].img

./fastboot reboot-bootloader

Finally, it's time to flash the actual system image to your phone or tablet.

Warning: The following line of code will wipe your device. If you do **not* want your device to be wiped, remove the "-w" from the command. The update should still take just fine, and it will not wipe your user data.

./fastboot -w update [image file].zip

When this is done, your phone will restart itself and boot up normally. As this process clears all data from your device, it will take slightly longer for your device to boot up into Android O for the first time. Once you have been greeted with the device setup walkthrough process, you know you have successfully flashed a new version of the firmware.

If you do not want to enter the commands manually there are scripts included inside the compressed folder containing the system image that will do most but not all of the heavy lifting for you. The flash-all script files will automate the flashing of the bootloader, radios (if needed), and the system image. The problem with this process is that you must first make sure that your phone is in the bootloader menu and its bootloader must be unlocked before starting the script. Of course, if these are not already done the script will fail to run and nothing will happen.

When finding your Nougat image, make sure you are downloading the correct one that corresponds with your device. If you're running a Verizon or Rogers Pixel, for instance, you'll have to make sure you download the right one.

Should you install the beta?

Now that we're at the fourth beta, we are at a Release Candidate. Not only has Google finalized the APIs for Android O, developers can publish apps with those new features in them — you may see your favorite app compatible with Icon Badges or Notification Channels very soon.

Even without third-party app support, the overall design of Android O appears to be near final, and we've had very few stability issues with the new version. As a Release Candidate, this is pretty much what you're going to see when you get the final version in early to mid-August.

Reader comments

How to get Android O beta 4 on your Pixel or Nexus (and how to roll back to Nougat)

I really like Android O but first I had issues getting Android Auto to work again with my VW.. Now I am dealing with Samsung Pay not working with my Gear S3 anymore. Super tempted on rolling back but not sure I wanna deal with reinstalling apps and relogging into apps.

Running on my 6P. I see the aptX and LDAC options in the developer options screen, but I haven't actually tried to put them to use.
Looking back to the preceding question, which is a couple of months old and refers to a prior beta, I have no problems with messaging.

I installed Android O beta on my Nexus 6 this morning. I can no longer send SMS. I tried switching from Messeges app to Messenger App (facebook), none of them working, Messeges app shows "not send. Tap to try gain", the later one keep asking me to confirm it as default but not sending. Anyone here has these issue?

Still using my Nexus 6 and agree that it's a solid well built device. It's probably the best performing phone I've owned. Camera is just meh but gets the job done. Would be great if Google would still officially support it.

I owned and used a Nexus 6 from shortly after it's launch until shortly after the Pixel launched. I still own this phone but my younger brother uses it as a daily driver. I find this statement to be subjective. I agree that it is one of the better built Nexus devices. Mine constantly has slow down issues. I found myself having to factory reset the device even on custom ROMs. I am definitely not the only person that had/has this issue. To be honest the Nexus 6 always felt like a half baked afterthought. I only really bought it because it was the first Nexus to be released on Verizon since the Galaxy Nexus and I got tired of buying year old HTC devices that had been unlocked and had OK ROM support. I'm really not sure why people always say this because Google is pretty upfront about their guaranteed support period. I do agree that they need to start offering Apple level support going forward with their devices but that is hopeful wishing.

As bad as the 7.1.1 February and March updates have been you would have to be crazy to try 7.1.2 let alone any new dev preview. Google trying to take out the remaining Nexus 6 and 6Ps that have not bootlooped or gone the way of BSD.

I can't believe the 6p is having worse bootloop issues than the 5x. Happened to me and my wife. Hardware issue that had to be replaced by LG. Unfortunately we were just out of warranty and had to pay to fix.