Categories
Design

How to use adb and fastboot on a chromebook

Cameron Summerson is the Editor in Chief of Review Geek and serves as an Editorial Advisor for How-To Geek and LifeSavvy. He’s been covering technology for nearly a decade and has written over 4,000 articles and hundreds of product reviews in that time. He’s been published in print magazines and quoted as a smartphone expert in the New York Times. Read more.

How to use adb and fastboot on a chromebook

For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.

First: Your Device Needs to be in Developer Mode

First things first: ADB and Fastboot are technically considered “developer” tools, so your Chromebook will need to be in Developer Mode before you’ll be able to access them. Just to make it clear, we’re not talking about the developer channel here—every Chromebook can be put into a sort of “unlocked” mode that allows for deeper system access and tweaks. This is called Developer Mode.

Fortunately, enabling Developer Mode is pretty straightforward and simple. There is one caveat, however: it will powerwash your device, so you’ll have to start over. The good news is that it’s a Chromebook, so this really shouldn’t take that long.

If you’re cool with that, hit up our guide on enabling Developer Mode. That should get you rolling and ready to go in a matter of a few minutes.

Second: Get Your Crosh On

In order to use ADB and Fastboot on your Chromebook, you’ll need to use something called Crosh—short for “Chrome Shell.” Think of it as a sort of lightweight terminal just for Chrome OS.

There are a couple of ways to access Crosh. To open it in a full browser window, just hit Ctrl+Alt+T on your keyboard.

If you find yourself using Crosh fairly often, however, and would like it in a popout window (like a “real” terminal) there are two extensions you’ll need: Secure Shell and Crosh Window. With both installed, you’ll have a Crosh entry in your app drawer that launches Crosh in a nice, tidy little window. Personally, it’s my preferred method of using Crosh.

How to use adb and fastboot on a chromebook

With a Crosh window fired up, you’re ready to rock and roll. You can’t just jump straight into ADB and Fastboot, however—you’ll need to enter one command to get a shell window first. Type the following:

The prompt should change to read “[email protected],” after which ADB and Fastboot should both be available to use like normal.

How to use adb and fastboot on a chromebook

Optional: What if it Doesn’t Work?

When I first tested this out, I couldn’t get it to work. ADB could see my Android devices, but it never requested access. Turns out Chrome OS still runs an old version of ABD/Fastboot (because Google, right?) so you’ll need to update it.

How to use adb and fastboot on a chromebook

But that’s where the problem comes into play: you can’t just update ADB and Fastboot like on a normal computer. There is, however, a solution. If you have an Intel-based Chromebook, a script exists that will update ADB and Fastboot to the newest versions, as well as move them to the “correct” location. After that, everything should run fine.

The script itself is pretty straightforward, and all the instructions are posted on the GitHub page. We suggest reading through them before you start so you know exactly what’s going on behind the scenes. Everything is also open source, so if you’d like to look through the code, you can do that too.

How to use adb and fastboot on a chromebook

With ADB and Fastboot updated and moved, both commands should work flawlessly. I tested this on a Pixelbook (i5, developer channel) by flashing a stock ROM onto my Nexus 6 and it was perfect.

ADB and Fastboot are tools that every Android developer and power user should be intimately familiar with. They’re powerful command line programs that allow you to use your PC to interface with your smartphone, whether it be for app debugging or modifying the software. Setting up ADB/Fastboot is fairly simple if you have a PC running Windows, macOS, or a GNU/Linux distribution, but Chromebooks running Chrome OS have a little trouble doing so. Thankfully, Chrome OS 67 brought support for ADB in Developer Mode just as we expected, meaning it’s now possible to set it up without needing Crouton. If you have a Chromebook with an x86_64 chip, then you can take advantage of a script that handles everything for you.

There aren’t a lot of steps involved and the process is fairly simple—you just need to copy and paste commands from the tutorial into the Chrome OS Shell. XDA Recognized Developer nathanchance‘s guide covers the steps needed to install ADB and Fastboot on Chromebooks with the x86_64 architecture. The process of installing ADB and Fastboot includes power-washing (AKA completely wiping) your device. In addition, your Chromebook will be less secure as you need to enable Developer Mode. If you have a Chrome OS tablet like the HP Chromebook X2, then you can follow the guide here to enter Developer Mode.

The install script from the repository does most of the heavy-lifting for you, and Nathan has included the steps required to utilize the script as well. If you run into issues while running ADB and Fastboot like the lack of a verification prompt on your smartphone or Chrome OS not being able to recognize your device, restarting both your Chromebook and your smartphone should do the trick. Let us know whether you were able to install ADB & fastboot successfully!

ADB andВ fastboot are both incredibly handy and easy-to-use options for manipulating your device, and we’ve mentioned both here on the Portal on several occasions. Whether you’re using Windows, Linux, or OSX, it’s generally not too difficult to get either of these set up and begin tinkering with your device. One thing I hadn’t previously seen though, until now that is, was how to set up ADB and fastboot В on Google’s increasingly popular Chrome OS or its open source sibling, Chromium OS .

Once regarded by some as little more than a web browser in a box, Chrome OS and the ChromeBooks that ship with it are becoming increasingly popular. Thus, many people now seem quite content to replace their larger more capable notebooks with these highly portable and affordable devices. The downside to that of course is that a slimmed down operating system means less flexibility and features. For those of you who cannot go twenty minutes without messing about with a mobile device, this might make ChromeOS seem like a little bit more viable on-the-go option.

XDA Recognized Contributor Quinny899 has written a guide covering the steps required to enable ADB andВ fastboot В commands on Chrome andВ Cromium OS. There aren’t many steps and the process is fairly simple. After downloading the appropriate files and entering a few terminal commands, you should be good to go. You’ll need a ChromeBook (or something running Chrome/Chromium) and a little Linux knowledge or the ability to copy and paste terminal commands. A little knowledge sure does come in handy, though, if and when things don’t always go to plan. You’re also advised to have a hot beverage of your choice on hand while those files download.

If you’re running Chrome or Chromium OS and would like to try this for yourself, check out the tutorial thread for more information.

How to set up ADB and fastboot on an x86_64 Chromebook

1. Check to make sure you actually have an x86_64 Chromebook

Open crosh by hitting Ctrl-Alt-T. In the window that opened up, type uname -m . If that spits out x86_64 , you are good to go. You can also use this website to figure it out.

2. Put your device into developer mode

Accessing the USB ports requires root access, which can only be accessed through developer mode.

THIS WILL MAKE YOUR CHROMEBOOK LESS SECURE. Developer mode turns off verified boot and enables the root shell by default. Unfortunately, if you need adb/fastboot access like I do, you’ll have to make this sacrifice. Additionally, this WILL powerwash (wipe) your device. I recommend doing this as soon as you get your Chromebook if you know that you want it.

To put your device into developer mode, find your device on this website, click on its name, and follow the “Entering” section. Read the entire article to familiarize yourself with developer mode so you do not accidentally reset your device by hitting space bar during boot.

3. Familiarize yourself with crosh

crosh, the Chrome OS shell, is your gateway to adb/fastboot. To open crosh, hit Ctrl-Alt-T. By default, crosh is a sandboxed shell, meaning you have a limited number of commands and access to the unlying filesystem. We need to go into the next level so to speak. Next, you will type shell ; this is a true command prompt where we are going to run all of our commands.

At this point, I will recommend setting a sudo password so that if your device is ever compromised, there is some level of protection. Type sudo su – to get into a root shell (this should require no password), type chromeos-setdevpasswd , set your password, then type exit . After this, sudo commands will require that password.

4. Run the setup script

The script in this repo will do two things:

Download the binaries and move them to the appropriate location ( /usr/local/bin ).

Download and install an adb / fastboot wrapper that saves you from having to type a long and arduous command every time you want to run adb and fastboot .

I have commented the scripts so that you know they are doing nothing nefarious.

To install, run curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash in your shell prompt.

Alternatively, if piping things from curl to bash scares you, you can run cd $/Downloads; curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh -o install.sh , inspect it with more or vim , then run chmod +x install.sh; bash install.sh .

To verify the installation was successful, run adb –version and fastboot –version . These should say they have been installed to /usr/local/bin . If there is an issue with running adb / fastboot (like not seeing a verification prompt on your phone/getting an unauthorized device with adb devices , be sure to reboot both devices before reporting any issues.

  • Home
  • Forums
  • General Development
  • Hardware Hacking
  • Chromebooks

Breadcrumb

nathanchance

Senior Recognized Developer / Contributor
  • Jun 19, 2018 at 8:19 PM
  • #1
  • I know that one of the biggest barriers for completely ditching my MacBook Pro for my Pixelbook was the ability to use ADB and fastboot (upgrading Android versions, flashing TWRP, factory resetting). ADB and fastboot are installed on later versions of Chrome OS; unfortunately, these versions are too old for devices like the Pixel 2 (XL) and there isn’t a ton of information on how to get them updated and working properly.

    As such, I created an installation script that will push the latest versions of the platform tools to the local binary directory and install a small wrapper script so you can use the commands as you normally would. The scripts should be fairly easy to read if you have a basic understanding of the command line, I have commented them so it’s clear what is going on.

    The installation script can be used to install the tools for the first time as well as upgrading to newer version as they come out. The changelog for each version can be found here.

    Please see the README for the full instructions and let me know if you have any questions, enjoy!

    zarthan

    Senior Member
    • Jun 20, 2018 at 5:32 PM
  • #2
  • nathanchance

    Senior Recognized Developer / Contributor
    • Jun 20, 2018 at 5:36 PM
  • #3
  • firegoblin

    Senior Member
    • Jun 20, 2018 at 6:04 PM
  • #4
  • nathanchance

    Senior Recognized Developer / Contributor
    • Jun 20, 2018 at 6:18 PM
  • #5
  • In theory, it should work for both.

    Please see the README as it answers the second question.

    firegoblin

    Senior Member
    • Jun 20, 2018 at 6:27 PM
  • #6
  • In theory, it should work for both.

    Please see the README as it answers the second question.

    firegoblin

    Senior Member
    • Jun 21, 2018 at 12:59 AM
  • #7
  • In theory, it should work for both.

    Please see the README as it answers the second question.

    nathanchance

    Senior Recognized Developer / Contributor
    • Jun 21, 2018 at 5:58 AM
  • #8
  • Going to have to give me more details, like the stuff I request in the README.

    Sent from my Pixel 2 XL using XDA Labs

    zarthan

    Senior Member
    • Jun 22, 2018 at 3:37 PM
  • #9
  • nathanchance

    Senior Recognized Developer / Contributor
    • Jun 22, 2018 at 4:32 PM
  • #10
  • For me personally, I bought a Chromebook for Chrome OS, not the hardware, so Crouton wasn’t really an option.

    You don’t need to reinstall these as they are in /usr/local/bin so they’re not touched during a Chrome OS upgrade.

    zarthan

    Senior Member
    • Jun 22, 2018 at 8:46 PM
  • #11
  • nathanchance

    Senior Recognized Developer / Contributor
    • Jun 22, 2018 at 9:05 PM
  • #12
  • zarthan

    Senior Member
    • Jun 23, 2018 at 3:16 PM
  • #13
  • nathanchance

    Senior Recognized Developer / Contributor
    • Jun 23, 2018 at 8:04 PM
  • #14
  • smartymcfly

    Senior Member
    • Jun 25, 2018 at 12:08 AM
  • #15
  • If you mainly just want command line to install packages.

    There is also chromebrew, almost a chromeos version of homebrew on mac.

    Intelli69

    Senior Member
    • Jun 25, 2018 at 9:28 PM
  • #16
  • First off I would like to thank you very much for making this installation script! I’ve been waiting the whole time since I bought my Chromebook about 3 weeks ago for somebody to post a script to install ADB/fastboot since the recent added support of the 2 to ChromeOS. ADB/fastboot support is the entire reason why I bought this Chromebook, if it did not have it, I would of been stuck buying a Windows laptop. I was really excited when I read they just added support recently for ADB/fastboot! I have a couple of small problems and if anybody can help me out, it will be greatly appreciated.
    1. I cannot get ADB to work yet on my Pixel 2 XL, but fastboot works no problem. When I try to use ADB, it says device is “offline”. Sometimes it says “unauthorized” when I’ve accepted permissions and click ‘always allow from this computer’ etc etc. Do I have to use a root shell to run adb/fastboot or can i use a regular shell like on my old windows laptop? Do i have to use sudo before every single command as well or just ‘adb devices’ like I would on a windows. I know these are noob questions but it is because I am a noob and have only used ADB/fastboot on a WIndows 7 laptop before this.
    2. My other question is when I powerwashed and it booted to the user sign in screen, I tried to click enable debugging features but it said not all of the features could of been enabled. Wth does that mean? How can I fix it? Does the chromebook stay in developer mode after I powerwash it if it was in dev mode before I powerwashed it? I did return it back to the dev channel after the powerwash bc I noticed it was back on stable.

    Do I have to install a custom version of Chromium OS before this will work?
    Thank you guys so much, and thanks again @nathanchance for making this script. Also thanks for your Pixel 2 XL kernel, I use that as well. Cheers!

    My device is the Acer Chromebook R11 .. 32 GB HD / 4 GB RAM with a 64 GB sdcard in it .. 2 in 1 tablet/laptop .. x86_64

    How to use adb and fastboot on a chromebook

    ADB & Fastboot are one of the most important tools for Android app development. While Chromebook can run ADB quite smoothly, but not before it makes you go through a few hurdles. It requires you to install a third-party set of scripts named crouton in order to run a Linux environment inside the Chrome OS. ADB then runs on your Chromebook from inside the Linux environment. But not anymore!

    Chrome OS recently got updated to version 67, bringing in a lot of key improvements and new features to the platform. A few improvements highlighted by Google on the press release include support for Progressive Web Apps as stand-alone apps and Split Screen support in Tablet mode. However, somewhere secretly, Google has also enabled Chromebooks with an x86_64 chip to officially support ADB if you are in developer mode. Here’s how.

    Make sure you read the whole catch before you proceed further on your Chromebook.

    First thing first, you’ll be putting you Chromebook into developer mode. And if you’re not aware, doing so will make your Chromebook less secure , as it disables a few security features like the verified boot, and enables the root shell by default. Furthermore, it will also perform a factory reset on your Chromebook. So make sure to create a backup of your important data.

    Now that you’ve been warned, you may proceed. And hey, take a breath. It’s an incredibly easy process.

    Install ADB on your Chromebook without Crouton

    As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. If you’re not sure, press Ctrl + At + T to launch a crosh terminal, and type uname -m . If the crosh terminal displays x86_64, you can proceed.

    Next up, you need to put your Chromebook into developer mode. Now the catch here is that the method for enabling developer mode is pretty much unique across different Chromebook models. It’s not possible for us to provide a step-by-step tutorial here for every Chromebook model. So we need you to go Chromium.org, and look for your Chromebook model on the Chromium OS devices page. Once you see your model, click on it, and there you’ll find what you need.

    Now that you’ve enabled the developer mode on your Chromebook, you’re almost there. To download and run the script for getting ADB & Fastboot tools setup, you first need to elevate your crosh privileges to access the deeper commands. As you already know, press Ctrl + At + T to open a crosh terminal, and type shell . Now create a sudo password by typing the following command.

    Doing so means sudo commands will require password input from now on, giving you back some of the security sacrificed in enabling developer mode.

    Now you’re all set to download and run the script for getting ADB & Fastboot tools setup. It is done through the crosh terminal using the following command.

    Alternatively, you can also use this command:

    However, if you this second command, you need to inspect it with more or vim, then run the following command. Remember, you don’t need to do this if you use the first command.

    Now to verify everything went successfully – in the crosh terminal, type:

    If you see them installed in /usr/local/bin, you’re good.

    If there’s any problem, like you don’t get ADB notification on connecting your Android device to your Chromebook, try rebooting your Chromebook. You may also try rebooting both the Chromebook and the Android device together.

    How to use adb and fastboot on a chromebook

    Android development on Chromebooks could soon be easier, as Google looks to make two key features of the Android SDK available on Chrome OS images by default.

    Both the Android Debug Bridge (‘adb’), used for a multitude of activities, including sending data to a connected device, and the recovery/flashing tool ‘fastboot’ are being considered for inclusion in Chrome OS, accessible through the Chrome Shell (‘crosh’).

    The news come through an update to an older bug report on a related ADB issue, now renamed ‘install adb and fastboot on chromeos images’.

    While the idea being proposed is short of offering a full Android development environment to Chromebook developers, the additions would make life easier.

    As newer APIs and features like the ‘Android Runtime for Chrome’ plugin mature, and as Google starts to pushes the capabilities of “Chrome Apps on Android“, it makes sense to bake in key developer features.

    There’s no indication when (or, as with everything planned, if) ADB and fastboot features will arrive in Chrome OS, but you can be sure you’ll hear about it when they do.

    Development solutions are already growing fast on Chrome OS. The Chrome Dev Editor (beta) continues to improve each month and already lets developers build, deploy, debug and publish applications to mobile devices over USB.

    Developers can already use adb on a Chromebook using a third-party app and, through “Crouton”, access the full Android SDK.

    But nothing beats native, right?

    How to install the Android SDK, ADB and Fastboot on your PC (Juli 2021).

    Inhaltsverzeichnis:

    How to use adb and fastboot on a chromebook

    Chromebook-Benutzern, die auch Zugriff auf das Android Debug Utility (ADB) und Fastboot für Android-Geräte benötigen, blieb lange Zeit nur eine Option: Crouton. Nun sind jedoch sowohl ADB als auch Fastboot in Chrome OS enthalten. So können Sie darauf zugreifen

    Erstens: Ihr Gerät muss sich im Entwicklermodus befinden

    Das Wichtigste zuerst: ADB und Fastboot sind technisch gesehen “Entwickler” -Tools. Daher muss sich Ihr Chromebook im Entwicklermodus befinden, bevor Sie darauf zugreifen können. Nur um es klar zu machen: Wir reden nicht über den Entwickler Kanal Hier kann jedes Chromebook in eine Art “entsperrt” -Modus versetzt werden, der einen tieferen Systemzugriff und Verbesserungen ermöglicht. Dies wird als Entwicklermodus bezeichnet.

    Zum Glück ist das Aktivieren des Entwicklermodus ziemlich unkompliziert und einfach. Es gibt jedoch eine Einschränkung: Ihr Gerät wird unter Strom gesetzt. Sie müssen also von vorne beginnen. Die gute Nachricht ist, dass es sich um ein Chromebook handelt. Es sollte also nicht so lange dauern.

    Wenn Sie damit zufrieden sind, lesen Sie unseren Leitfaden zur Aktivierung des Entwicklermodus. Das sollte Sie zum Rollen bringen und in wenigen Minuten einsatzbereit sein.

    Zweitens: Machen Sie Ihren Scheißer an

    Um ADB und Fastboot auf Ihrem Chromebook verwenden zu können, müssen Sie eine so genannte Crosh – kurz Chrome Shell – verwenden. Stellen Sie sich dies als eine Art leichtes Terminal nur für Chrome OS vor.

    Es gibt mehrere Möglichkeiten, auf Crosh zuzugreifen. Um es in einem vollständigen Browserfenster zu öffnen, drücken Sie einfach Strg + Alt + T auf Ihrer Tastatur.

    Wenn Sie Crosh jedoch häufig verwenden und es in einem Popout-Fenster (wie einem „echten“ Terminal) möchten, gibt es zwei Erweiterungen, die Sie benötigen: Secure Shell und Crosh Window. Wenn beide installiert sind, haben Sie einen Crosh-Eintrag in Ihrer App-Schublade, der Crosh in einem schönen, aufgeräumten kleinen Fenster startet. Persönlich ist dies meine bevorzugte Methode zur Verwendung von Crosh.

    How to use adb and fastboot on a chromebook

    Wenn ein Crosh-Fenster hochgefahren ist, können Sie rocken und rollen. Sie können jedoch nicht direkt in ADB und Fastboot einsteigen – Sie müssen zuerst einen Befehl eingeben, um ein Shell-Fenster zu erhalten. Geben Sie Folgendes ein:

    Die Eingabeaufforderung sollte sich in “chronos @ localhost” ändern. Danach sollten ADB und Fastboot wie üblich verfügbar sein.

    How to use adb and fastboot on a chromebook

    Optional: Was ist, wenn es nicht funktioniert?

    Als ich das zum ersten Mal getestet habe, konnte ich es nicht zum Laufen bringen. ADB konnte meine Android-Geräte sehen, forderte jedoch nie Zugriff an. Es stellt sich heraus, dass Chrome OS immer noch eine alte Version von ABD / Fastboot ausführt (weil Google dies ist, oder?). Sie müssen sie also aktualisieren.

    How to use adb and fastboot on a chromebook

    Aber hier kommt das Problem ins Spiel: Sie können ADB und Fastboot nicht einfach wie auf einem normalen Computer aktualisieren. Es gibt jedoch eine Lösung. Wenn Sie über ein Intel-basiertes Chromebook verfügen, gibt es ein Skript, mit dem ADB und Fastboot auf die neuesten Versionen aktualisiert und an den “richtigen” Speicherort verschoben werden. Danach sollte alles gut laufen.

    Das Skript selbst ist ziemlich unkompliziert und alle Anweisungen sind auf der GitHub-Seite veröffentlicht. Wir empfehlen, sie durchzulesen, bevor Sie beginnen, damit Sie genau wissen, was sich hinter den Kulissen abspielt. Alles ist auch Open Source. Wenn Sie also den Code durchsehen möchten, können Sie dies auch tun.

    How to use adb and fastboot on a chromebook

    Wenn ADB und Fastboot aktualisiert und verschoben wurden, sollten beide Befehle einwandfrei funktionieren. Ich habe dies auf einem Pixelbook (i5, Entwicklerkanal) getestet, indem ich ein aktives ROM auf meinen Nexus 6 geblitzt habe und es war perfekt.

    How to use adb and fastboot on a chromebook

    很长一段时间,同时需要访问Android设备的Android调试实用程序 (ADB)和Fastboot的Chromebook用户只剩下一个选项:Crouton。 但是,现在,ADB和Fastboot都包含在Chrome OS中。 以下是访问它们的方法。

    第一:您的设备需要处于开发者模式

    首先要做的事情是:ADB和Fastboot在技术上被认为是“开发人员”工具,因此您的Chromebook需要处于开发者模式才能访问它们。 为了说清楚,我们不是在谈论开发者频道 – 每个Chromebook都可以进入一种“解锁”模式,允许更深入的系统访问和调整。 这称为开发者模式。

    幸运的是,启用开发人员模式非常简单明了。 但是有一点需要注意:它会为你的设备提供电源,所以你必须重新开始。 好消息是它是Chromebook,所以这真的不应该花那么长时间。

    第二:开启你的Crosh

    有几种方法可以访问Crosh。 要在完整的浏览器窗口中打开它,只需按键盘上的Ctrl + Alt + T.

    但是,如果你发现自己经常使用Crosh,并且想要在弹出窗口(如“真正的”终端)中使用它,那么你需要两个扩展: Secure Shell和Crosh Window 。 安装完成后,您的应用程序抽屉中将有一个Crosh条目,可以在一个漂亮,整洁的小窗口中启动Crosh。 就个人而言,这是我使用Crosh的首选方法。

    How to use adb and fastboot on a chromebook

    在Crosh窗口启动时,您已准备好摇滚。 你不能直接跳到ADB和Fastboot,但是你需要先输入一个命令来获得一个shell窗口。 输入以下内容:

    How to use adb and fastboot on a chromebook

    可选:如果不起作用怎么办?

    当我第一次测试时,我无法让它工作。 亚行可以看到我的Android设备,但它从未请求访问。 事实证明Chrome OS仍然运行旧版本的ABD / Fastboot(因为谷歌,对吧?)所以你需要更新它。

    How to use adb and fastboot on a chromebook

    但这就是问题发生的地方:你不能像在普通计算机上那样更新ADB和Fastboot。 但是,有一个解决方案。 如果您使用的是基于Intel的Chromebook,则会存在一个脚本,可将ADB和Fastboot更新为最新版本 ,并将其移至“正确”位置。 在那之后,一切都应该运行良好。

    脚本本身非常简单,所有指令都发布在GitHub页面上。 我们建议您在开始之前阅读它们,以便确切知道幕后发生了什么。 一切都是开源的,所以如果你想查看代码,你也可以这样做。

    How to use adb and fastboot on a chromebook

    随着ADB和Fastboot的更新和移动,两个命令都应该完美无缺。 我在Pixelbook(i5,开发人员频道)上通过将一个库存ROM闪存到我的Nexus 6上进行了测试,这非常完美。