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

Issue 762726 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Kevin fails to convert to Developer mode from Normal mode

Project Member Reported by jingwee@chromium.org, Sep 6 2017

Issue description

Chrome Version: M61.0.3163.80 beta kevin
OS: ChromeOS 9765.53.0

What steps will reproduce the problem?
(1) Device was converted to Normal/verified mode due with FRE policy.
(2) Moving device to a non-FRE OU.
(3) Verify that DeviceBlockDev = false.
(4) Press Esc+Refresh+Power and initiate turning OS verification off.


What is the expected result?
Conversion to Developer mode should proceed.


What happens instead?
Upon press ENTER to start confirm to turn OS verification off, the screen went black for a second and presents two unexpected and contradicting messages:

1. In the middle of the screen it says "OS verification is OFF. Press EBTER to confirm you wish to turn OS verification on ..." as if it is already in Developer mode.

2. On the top left of the screen was "Developer mode is disabled on this device by system policy. For more information, see ...".

The only option is to press ENTER to go back to Normal mode and stays in Normal mode.

This does not occur on a blaze device with the same build.
 
6284216184493965995-account_id=3.jpg
283 KB View Download
678406434540414387-account_id=3.jpg
743 KB View Download
6174531673565524285-account_id=3.jpg
533 KB View Download
Status: WontFix (was: Available)
Sorry it was my mistake. The device was never enrolled thus the policies had not be updated on the device thus Developer mode was still blocked.

Closed invalid.

Sign in to add a comment