Update adb and fastboot to latest version
Reported by
rdur...@gmail.com,
Dec 7 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.5.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.11 Safari/537.36 Platform: 10176.5.0 (Official Build) dev-channel edgar Steps to reproduce the problem: 1) open crosh tab 2) enter shell (shell) 3) adb version NOTE: version 1.0.32 is seen. What is the expected behavior? Latest released version should be reported. As of now that is 1.0.39. What went wrong? Unable to connect and authorize adb debugging with newer devices (ie. Pixel 2) without newer versions of platform tools. Did this work before? N/A Chrome version: 64.0.3282.11 Channel: dev OS Version: 10176.5.0 Flash Version: Shockwave Flash 28.0 r0
,
Dec 11 2017
,
Dec 12 2017
this is already being attempted here: https://chromium-review.googlesource.com/810017
,
Dec 14 2017
hmm even that won't be sufficient as that CL is for Android 6 (marshmallow) when we really want Android 8 (oreo)
,
Jan 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/08b5a7e28d15bed756dd3b91564e0e26b42c8063 commit 08b5a7e28d15bed756dd3b91564e0e26b42c8063 Author: Mike Frysinger <vapier@chromium.org> Date: Sat Jan 06 00:42:49 2018 libpcre2: pull in latest version Newer adb/fastboot use this version of the library. BUG=chromium:792957 TEST=build for amd64 & arm works Change-Id: I0ca7bf1b4ffdf833b4fd4eb0cb9981dbb30e287b Reviewed-on: https://chromium-review.googlesource.com/851952 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> [add] https://crrev.com/08b5a7e28d15bed756dd3b91564e0e26b42c8063/dev-libs/libpcre2/metadata.xml [add] https://crrev.com/08b5a7e28d15bed756dd3b91564e0e26b42c8063/dev-libs/libpcre2/Manifest [add] https://crrev.com/08b5a7e28d15bed756dd3b91564e0e26b42c8063/dev-libs/libpcre2/libpcre2-10.30.ebuild
,
Jan 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/crosutils/+/ea59b3748b719dc637f025a93411c3bf165dc032 commit ea59b3748b719dc637f025a93411c3bf165dc032 Author: Mike Frysinger <vapier@chromium.org> Date: Sat Jan 06 05:14:18 2018 container: also mount /tmp Newer adb wants a writable /tmp, so set that up by default. BUG=chromium:792957 TEST=building newer container works Change-Id: Ib5349d21ddf0ffd65ca0ddafd6f0894891e85f2b Reviewed-on: https://chromium-review.googlesource.com/853095 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> [modify] https://crrev.com/ea59b3748b719dc637f025a93411c3bf165dc032/generic_container_files/config.json
,
Feb 7 2018
Has there been any other movement on this? adb and fastboot are the only reason I still have my old MacBook even booted because my Chromebook Plus cannot interact with my Pixel 2 XL at all (no adb authorization request and cannot flash the factory images to update every month). Thanks!
,
Feb 26 2018
Is there a timeline for when this this fix might get pushed? I'd really like to be able to use ADB on my chromebook with my pixel XL.
,
Apr 17 2018
Crickets.... Any possibility of a status update?
,
Jun 20 2018
,
Aug 6
i posted an update but it broke ARC++ hwtests. i don't have the cycles or familiarity with the ARC++ code paths to do an update, so someone who works on ARC++ will have to drive this instead. https://chromium-review.googlesource.com/810017
,
Sep 15
+some folks familiar with ARC++ to help increase visibility.
,
Jan 7
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dtapu...@chromium.org
, Dec 11 2017