Skip to content

INSTALL.md: a stock (never-unlocked) unit needs fastboot oem unlock + unlock_accept, and the §1b palm gesture didn't work as written #4

Description

@mattv-nmg

Flashed a stock Nexus Q that had never been touched before. Two things in
INSTALL.md tripped me up. Everything else in the guide was accurate and the
flash itself went fine.

Device:

version: U-Boot 2011.09-rc1 (Apr 17 2012 - 00:38:59)
version-bootloader: steelheadB4H0J
product: steelhead
device_type: HS
secure: yes
unlocked: no

1. Missing unlock step

§2 goes straight to fastboot flash boot. On a stock unit that fails:

Sending 'boot' (6554 KB)      OKAY [  0.733s]
Writing 'boot'                (bootloader) fbt_handle_flash: failed, device is locked
FAILED (remote: 'device is locked')

Unlocking is a two-step with a short timeout, which isn't obvious:

$ fastboot oem unlock
(bootloader) oem unlock requested:
(bootloader)    Unlocking forces a factory reset and could
(bootloader)    open your device up to a world of hurt.  If you
(bootloader)    are sure you know what you're doing, then accept
(bootloader)    in 5 seconds via 'fastboot oem unlock_accept'.

$ fastboot oem unlock_accept
(bootloader) Erasing userdata partition
...
(bootloader) Setting device to unlocked
(bootloader) Writing to environment partition on mmc0...
OKAY [  4.846s]

You have to run unlock_accept within 5 seconds or you start over. The device
stayed in fastboot afterward, so no re-entry was needed. It erases userdata,
which doesn't matter here since step 2 overwrites it anyway.

Suggest a §1c or a note at the top of §2: check fastboot getvar all for
unlocked: no, and if so run the two commands above before flashing.

2. §1b palm gesture

§1b says to cover the sensor before applying power and keep it covered. That
never produced a red ring for me across a lot of attempts. What worked:

  1. Plug power in with your palm off the dome.
  2. The moment the centre blue LED lights, put a flat palm on the centre.
  3. Hold until the ring goes solid red.
  4. Lift off promptly. Holding past red moves it to a different mode.

The timing window on step 2 is about a second. The release timing in step 4
also matters and isn't mentioned anywhere I could find. The old nexusq.wikidot
troubleshooting page describes the power-on-then-palm ordering, which matches
what I saw.

Happy to open this as two separate issues if you'd rather.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions