factory reset guado device

[Roger Tawa]

Hi all,

TL;DR: Trying to flash a guado device back to a standard chromebox device, but not working. Looking for some help.

Long version

I was working on a project a few months ago where I had to flash a different bios on the guado device.  We were using guado h/w but it was not a chromebox in the typical sense.  I'm no longer working on this project and trying to reset the device back to a normal cros box, but unsuccessfully.

Here is what I have tried so far:

1/ I used the chrome app to generate a recovery USB stick.  I used the device "GUADO D25-A3R-Y3V" which appears on the recovery screen of the device, and the app said it recognized this device name exactly.

2/ i removed everything from usb ports of guado device except the recovery usb stick.  I booted into recovery mode by pressing the recovery button while turning on.  I thought the device would simply boot from the usb and recover, but it does not seem to access the usb stick.

3/ I put the usb dongle for the keyboard and mouse back in.  I then booted the device normally (it's already in dev mode) and pressed Ctrl+L.  I then chose to boot from the usb stick, which worked.

4/ I started a guest session, Ctrl+Atl+T and opened a shell, then typed "sudo /usr/sbin/chromeos-install" which failed with the error:

Command: /tmp/install-mount-point/usr/sbin/chromeos-firmware --mode=recovery

Starting Google_Guado firmware updater v4 (recovery)...

 - Updater package: [Google_Guado.6301.108.4]

 - Current system: [RO: , ACT:]

 - Write protection: Hardware: ON, Software: Main=ON

 Sorry, this firmware update is only for Google_Guado plaftform.

 You system () is either incompatible or using an

 unknown version of firmware.

5/ Googling I found some commands that should force update the firmware.  I ran this:

# /usr/sbin/chromeos-firmwareupdate --sb_extract /tmp

Extracting to: /tmp

# sudo /usr/sbin/flashrom -w /tmp/bios.bin -i RW_LEGACY

Block protection could not be disabled!

Erasing and writing fhash chip... SUCCESS

However, re-running chromeos-installer still fails with the same error.

What else should I try?

(Note that in both steps 4 and 5, there is mention of some protection being turned on, so I wonder if that is the cause. How can I turn this protection off?)

Thanks,
Roger

-

[Mike Frysinger]

RW_LEGACY is for the legacy firmware image (what you get when you hit CTRL+L).  that slot is never executed otherwise, so i wouldn't worry about it.

in order to have flashed the read-only parts in the past, you would have had to disable write protect on the flash.  did you actually do that ?  are you sure you actually flashed the firmware/bios ?  or did you just change the disk image that it was booting ?

can you clarify (2) ?  if you boot into recovery mode and the process proceeds with a display saying it's recovering, then it should be using the USB stick ...

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Hung-Te Lin]

You should remove USB stick before booting into recovery mode. Then after seeing the recovery screen, insert USB stick to start recovery process.

---
You received this message because you are subscribed to the Google Groups "Chromium OS dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Roger Tawa]

Thanks Bernie, Mike, Hung-Te, Fernando!  I was able to get the box back on its feet like this:

- I made a new recovery stick on a new USB drive.  This new one behaved slight differently when booting to in recovery mode (printed a message that there was no chromeos on the stick.  The old stick just did nothing.  Still kind of strange though.)

- I was able to boot from the new USB (via normal boot then Ctrl+L) and use VT2 to get a shell

- I ran chromeos-firmware  --nocheck_platform --mode=recovery to update the firmware

- I ran chromeos-install with "skip-post-install-step" command line arg (exact name escapes me at the moment) so that the partitions would be setup, but it would skip the firmware update step

- rebooted

All came up correctly.  Device AUed to version 52 by itself.

Fernando is now trying to duplicate this process on a couple of other devices we were using a few months back.

Roger

-