[GUIDE] Setting up ADB and fastboot on an x86_64 Chromebook

[adame09]

Chromebook Plus is not compatible with this, that is an arm64 device, not an x86_64 device.

Is this supported on a Acer Chromebook 14?

 

[galaxys]

Is this supported on a Acer Chromebook 14?

You can enter a command from the op "Readme" instructions to find out if it's supported.

 

[Zedelot]

So I don't understand why it sees my device in fastboot but doesn't find it when doing the flash-all.sh the only thing that seems to work for me is booting any .img but doesn't work if I try to flash.... Any help?

 

[Evo_Shift]

So I don't understand why it sees my device in fastboot but doesn't find it when doing the flash-all.sh the only thing that seems to work for me is booting any .img but doesn't work if I try to flash.... Any help?

Can you use the command

./flash-all.sh

instead of the

bash flash-all.sh

that you are trying to use?

 

[Zedelot]

Can you use the command

./flash-all.sh

instead of the

bash flash-all.sh

that you are trying to use?

I actually got a reply from the dev who posted the guide. It's actually

source ./flash-all.sh

for it to work. Now I know but thanks!

 

[troymz1]

I actually got a reply from the dev who posted the guide. It's actually

source ./flash-all.sh

for it to work. Now I know but thanks!

I have been looking for this for so long now. Thank you so much!

 

[ItachiLvrX]

I can't seem to figure out github, i've always had problems with it. I know all about ADB and such, used it quite a lot, but I can't find a file to download from github. Any help? What do I need to click on?

 

[the1dynasty]

THANK YOU!!! I followed the easy steps and got it working on my PixelBook running Canary 72 w/Dev mode on... I attached an image to show it working and I confirmed it persists through reboots of both devices...

Q: Does anyone know how to get Android Studio on the PixelBook to now recognize ADB?

 

[Ducter]

After some researching, I'm more confused. I have an arm based chromebook and have read where people get adb and fastboot working but everything I have read has been older, version 1.02 of adb iirc. Has anyone with an arm based chromebook gotten adb and fastboot working properly? If so, a quick how to would be appreciated. Thanks

heres one such example but I fear it too old now.

 

[cmattern]

install.sh permission denied solution

There was a post a while back re: Permission denied when trying to run the install.sh, I hit this and found that, at least on my Samsung Chromebook Plus v2 with Chrome OS 73.0.3683.88, it was related to a filesystem mounted with noexec. Credit to Michael Kolber on Stack Exchange: https://superuser.com/questions/1264615/permission-denied-on-chromebook-even-with-sudo

 

[cmattern]

BTW @nathanchance many thanks for this!

 

[jaxenroth]

Hey, looking for some help. 2 issues, Have this guide properly set up adb/fastboot both working also have linxu beta set up w/ adb/fastboot working on my Acer Chromebook flip 15.
1st question is if using this guide, where do i place my unzipped google factory image so I can run the commands to flash it, I cant find where chromebooks local files are stored.
2nd question is if using the linux beta terminal I have my factory image in my linux / platform-tools folder I can individually flash something e.g. fastboot flash radio radio.img but I cant do the ./flash-all.sh Ive made the file executable but after the command nothing happens, no error codes, nothing. Just hangs. Thx.

 

[flash713]

You rock Nathan C!!! I just bought an Asus Chromebook released July 2021 and followed your guide here and it was of course, successful!! Appreciate you!!

 

[airtower]

Thanks so much for this @nathanchance! I recently retired my old phone and found myself needing adb/fastboot for the first time in 4 years. I don't own a personal windows device, so this was a lifesaver.

While it worked smoothly to unlock my new bootloader and flash some smaller images, I was unable to flash a large (~2.2gb) device image last week. I don't have the verbose output as I was able to resolve the issue with a borrowed windows PC, but the error was related to disk space on the local device. Being that I had just powerwashed it to enable dev mode, I had the full 16gb of device storage available minus the space taken by the OS and a handful of small apps...seems like plenty of space should have been available.

Question - when running adb or fastboot in shell like this, is there some kind of sandboxed environment that presents a reduced disk space? The image was being flashed directly from the user's Downloads folder FWIW.

 

[airtower]

Update to above in case anyone's watching: the exact error is

extracting product.img (2668 MB) to disk...ziparchive W 03-21 17:28:03 30314 30314] Zip: unable to allocate 2798404236 bytes at offset 0: No space left on device fastboot: error:

fastboot was being run from the ~home/downloads folder where the system image was located