How to install Android O on your Pixel or Nexus




Android O was amazingly declared nowadays. beside a inordinateness of latest options, Google has additionally free industrial plant pictures for the developer preview. the simpler to put in beta unleash won’t be on the market till someday in might. If you’ve got a probing for some Oreo/Oatmeal Cream Pie/Orangesicle/O-whatever, you'll install the industrial plant pictures on the picture element and Nexus devices.

Prerequisites

Common understanding and knowledge victimization tools that area unit given the automaton SDK like Fastboot and ADB.

Fastboot and ADB put in on your system and PATH variables updated consequently.

Understand that this may wipe all of your device information which you may 1st have to be compelled to backup any files, apps, etc that you simply don't wish to lose!

You will additionally clearly want a picture element, Pixel XL, Nexus 6P, Nexus 5X, Pixel C, or Nexus Player. don'tstrive any pictures on devices they're not meant for because it can cause problems and not work!

WARNING putting in a system image on your device can take away all information from the device. Please confirm that you simply backup your information before you proceed. Also, confine mind that these picturesaren't final releases and will have bugs or unfinished options. These area unit Developer Previews and not meant for the common client.

Step one – Unlock your bootloader in Developer choices

Please still subsequent step if you have already got your bootloader unfastened. If not, otherwise you forget whether or not or not it’s unfastened, i'll walk you thru the method.

Enable OEM unlocking (aka unlock your bootloader)

Go into Settings -> Developer choices on your device.

If you are doing not see Developer choices listed during this list, please click on concerning phone and keep sound on Build range till you see “You area unit currently a developer”. What this suggests is you currently have a Developer choices in your main Settings list. Please move to Settings -> Developer choices currently.

Once you're in Developer choices, rummage around for OEM unlocking. this is often a straightforward switch or checkbox that you simply have to be compelled to alter. it'll prompt you to permit OEM unlocking and provides you a warning message. Please click the alter to just accept and continue.

Step a pair of – transfer your device specific image

Below area unit direct links to transfer the automaton M preview pictures. Please confirm you transfer the right one to avoid any major problems.

Pixel

Pixel XL

Nexus 6P

Nexus 5X

Pixel C

Nexus Player

Step three – Decompress the image file :

All of the required image files that you simply can want area unit placed during this “zip” compressed file. Extract the nothing file and you must see these files:

Now extract the nothing file within that folder. you must see these files inside:

Please Note

Depending on that device you're flashing, you'll see slightly totally different files.

Step four – resuscitate bootloader and flash

Assuming that you simply have fastboot and adb already established and prepared to use, simply follow the commands below so as.

adb resuscitate bootloader

This will restart your phone into the bootloader mode. this may solely work if your phone is connected and you've got USB debugging turned on.

fastboot oem unlock

If your phone is already OEM unfastened, you'd not have to be compelled to try this, however it wouldn’t hurt if you're unsure.

bash flash-all.sh

This will run all of the fastboot commands required for the entire image flash. If you're victimization Windows, instead of a bash script you may use the flash-all.bat (batch) file. One common issue of this not operating is that you simply don't have fastboot setup properly ANd isn't set as an surroundings variable (a variable that works system wide).

For Windows users

There area unit reports from some Windows users that the flash-all.bat fails. It looks that it’s a bug with the fastboot.exe and the way it inefficiently allocates memory. Some users tell strive {a totally different|a special|a unique|a distinct} usb port or different usb cable, that they claim doing therefore resolved their problems. If this works for you, please allow us to understand within the comments below. Otherwise, please follow the workaround below that KingofPing has on condition that can possibly solve your problems. What this will is break down every step manually that the batch file ought to have mechanically in deep trouble you. (if you open the batch move into a text editor, you may see these same commands)

Make sure that if you've got an additional nothing move into your directory that you simply extract it and place it’s contents in your operating directory.

After flash-all.bat errors out, please follow these instructions:

—Don’t “press any key” – which will shut the window – simply hit Ctrl-C.—

fastboot flash boot boot.img

fastboot flash cache cache.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash userdata userdata.img

That’s it!

Once the scripts end it'll do a final resuscitate and also the solely factor left is to finish the traditionalautomaton setup wizards and revel in. If you've got any problems be at liberty to comment and that we canassist you out as needed!