New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 627904 link

Starred by 2 users
Status: Fixed
Owner:
█ pschmidt@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Couple N5Xs on build38-b1 in funky state

Project Member Reported by bpastene@chromium.org, Jul 13 2016 
010370e89f5323d2 and 01027c338170c679 are reporting "Your device can't be checked for corruption. Please lock the bootloader." Could we get someone to take a look at them and reflash if necessary?

Comment 1 by pschmidt@chromium.org, Jul 13 2016

Owner: pschmidt@chromium.org
Status: Started (was: Untriaged)
You get that message on devices that reboot with unlocked bootloaders on Marshmallow.

Anyway these two devices are truly hosed.  They constantly are in a tight boot loop.  I've flashed a couple of new ones but am waiting on them to fully charge before adding them back.

Comment 2 by pschmidt@chromium.org, Jul 13 2016 

New devices attached.  Effective with https://uberchromegw.corp.google.com/i/chromium.android/builders/Marshmallow%2064%20bit%20Tester/builds/2880

List of devices attached
01024cde8138b879	device
010248270fc626d8	device
01024a870e6c8f49	device
01036bb19fc34dd1	device
0103695081b89e79	device
0128930612c994ed	device
010243fa2132b5ca	device

Comment 3 by bpastene@chromium.org, Jul 13 2016 

Any plans for the boot-loopers? We've got our hands on a uart headphone jack debugging cable, and it might be interesting to see if the kernels on those guys are yelling about anything.

Comment 4 by pschm...@google.com, Jul 13 2016 

Come and get them if you want 'em

btw, I did manage to re-flash them both and they are doing the same boot loop trickery.

Comment 5 by pschmidt@chromium.org, Aug 15 2016

Status: Fixed (was: Started)
Closing out old bug.
►

Sign in to add a comment