Unable to find container (ADB/fastboot) |
|||||
Issue descriptionChrome Version : Chrome OS 64.0.3282.190 URLs (if applicable) : https://chrome.google.com/webstore/detail/adbfastboot-android-debug/kmbodfbmeooklnjdldfoelenpeljgjll/related?utm_source=chrome-app-launcher-info-dialog What steps will reproduce the problem? (1) Installed ADB/Fastboot via URL above. (2) launch crosh and type c adb (3) What is the expected result? adb container would be executed. What happens instead? get message, unable to find container. Please provide any additional information below. Attach a screenshot if possible. This did work originally when installed... However I ran into an issue which caused the system to lockup and reboot. since then I can't get it to work. The last thing I did was try running "c fastboot devices" (I think that was the command). Fastboot printed a message saying it was waiting to connect to a device. I tried to hit ctrl-c to cancel fastboot when the system crashed.
,
Apr 5 2018
,
May 9 2018
,
May 9 2018
,
May 9 2018
The ADB/fastboot extension is still installed after the system lockup/reboot? I could imagine that if the image got corrupted and CrOS booted into the other partition, the extension might not be available if it hasn't synced...
,
Aug 6
latest update can find my Pixel 2 phone |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Apr 4 2018