New issue
Advanced search Search tips

Issue 828913 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Unable to find container (ADB/fastboot)

Project Member Reported by lanemichael@google.com, Apr 4 2018

Issue description

Chrome 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.

 
Labels: OS-Chrome
Components: Platform>ARC
Components: OS>Systems>Containers
Components: -Platform>ARC
Labels: -Proj-Containers
Owner: ejcaruso@chromium.org
Status: Assigned (was: Unconfirmed)
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...
Cc: vapier@chromium.org
Labels: Pri-3 Type-Bug
Status: Fixed (was: Assigned)
latest update can find my Pixel 2 phone

Sign in to add a comment