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

Issue 639132 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Some MP recovery images are not accepted

Project Member Reported by victorhsieh@chromium.org, Aug 18 2016

Issue description

I'm able to use some MP recovery images for some board but not the others.

For example, I tried several version of cyan's, but none of them work for recovery.  Here is an example.
https://storage.cloud.google.com/chromeos-releases/canary-channel/cyan/8705.0.0/chromeos_8705.0.0_cyan_recovery_canary-channel_mp.bin

But it works for veyron_minnie on 8718.0.0 and 8709.0.0, but NOT 8710.0.0.  8710 was when some signing change started to be effective.  Note the MP image of cyan didn't work for me all the time.
 
Cc: yusukes@chromium.org

Comment 2 by vapier@chromium.org, Aug 18 2016

please clarify "does not work" or "is not accepted".  show the exact commands you're using, and then the exacts things you did after that (e.g. usb stick/recovery method/etc...).
1. dd into USB stick.
$ sudo dd if=canary-channel%2Fcyan%2F8705.0.0%2Fchromeos_8705.0.0_cyan_recovery_canary-channel_mp.bin  of=/dev/sdd bs=4M oflag=sync

2. Power up Chromebook and hit ESC-Refresh-Power to enter recovery screen.
3. Insert USB stick.

Expected: see progress bar of recovery.
Actual: "The device you inserted does not contain Chrome OS."

Comment 4 by vapier@chromium.org, Aug 18 2016

can you verify what keys your cyan is using now ?  i assume that info will be available if you hit tab at the recovery screen.

i have a minnie & samus myself, but that's it.
gbb.rootkey: feb7dd4fc.....
gbb.recovery_key: 6a0de832ff.....
Something is not right for that, my Cyan has attached. 
IMG_1353.JPG
347 KB View Download
Is the WP screw in your unit?

If not you can flip it to dev mode, then enable cryssystem dev_boot_usb=1, then ctrl+u boot that recovery image and it should rewrite your firmware to the matching keys in the recovery image.
Is there an easy way (e.g. command line) to tell if hardware WP is on or off?  We have at least two instances here with the same problem.
Yea, try `crossystem | grep wp`, that should give you the different values (sw, boot, current).
I didn't flip WP but the problem now is only reproducible on 8710, but not 8705 and 8718.  The Android signing change was enabled from 8710 to 8717(?), but I have no idea why it would affect the recovery, since the Android image should just be a file inside CrOS image.

Mike, are you able to flash with your manually signed image?
Status: WontFix (was: Untriaged)
Everything seems to work now.  Closing...

Sign in to add a comment