computers:chromebooks:chromebooks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
computers:chromebooks:chromebooks [2020/10/01 16:42] – joncomputers:chromebooks:chromebooks [2021/01/04 16:18] (current) – localadmin
Line 1: Line 1:
 ====== Chrome OS ====== ====== Chrome OS ======
 Copied from [[https://wiki.cherryblossomfarmette.com:8443/doku.php?id=chrome|Rob Sickler]] Copied from [[https://wiki.cherryblossomfarmette.com:8443/doku.php?id=chrome|Rob Sickler]]
 +
 [[wp>Chrome_OS|Chrome OS]] is Google's fork of the [[wp>Chromium_OS|Chromium]] project which is based on the Linux kernel.  Google's first release of the OS was in the summer of 2011.  Many schools like to use [[wp>Chromebook|Chromebooks]], which run Chrome OS, because Google's ecosystem is pretty friendly and reliable.  They are also marketed toward first-time computer users due to their simplicity.  I personally have a few Chromebooks and like to tinker a bit with them. [[wp>Chrome_OS|Chrome OS]] is Google's fork of the [[wp>Chromium_OS|Chromium]] project which is based on the Linux kernel.  Google's first release of the OS was in the summer of 2011.  Many schools like to use [[wp>Chromebook|Chromebooks]], which run Chrome OS, because Google's ecosystem is pretty friendly and reliable.  They are also marketed toward first-time computer users due to their simplicity.  I personally have a few Chromebooks and like to tinker a bit with them.
  
Line 156: Line 157:
     * serial_number: <code bash>vpd -s "serial_number"="9999999999999999999999"</code>     * serial_number: <code bash>vpd -s "serial_number"="9999999999999999999999"</code>
     * mlb_serial_number: <code bash>vpd -s "mlb_serial_number"="9999999999999999999999"</code>     * mlb_serial_number: <code bash>vpd -s "mlb_serial_number"="9999999999999999999999"</code>
 +      * The ''mlb_serial_number'' entry is typically found to be something other than the serial number when you dive into machines fresh out of the box.  However, I've been making the same as the serial number without any issues when doing my repairs.
   * Might as well verify the serial number again: <code bash>vpd -l</code>   * Might as well verify the serial number again: <code bash>vpd -l</code>
   * If you've **messed up**, like I've done with a random capital letter in the entry, you can remove the entry with a command like: <code bash>vpd -d "serial_Number"</code>   * If you've **messed up**, like I've done with a random capital letter in the entry, you can remove the entry with a command like: <code bash>vpd -d "serial_Number"</code>
Line 178: Line 180:
   * Specify the asset tag: <code bash>vpd -s "asset_tag"="IT-12345"</code>   * Specify the asset tag: <code bash>vpd -s "asset_tag"="IT-12345"</code>
   * Specify the machine type: <code bash>vpd -s "mtm"="81QC"</code>   * Specify the machine type: <code bash>vpd -s "mtm"="81QC"</code>
 +  * Specify the Service Tag((typically found on Dell CBs and is typically set the same as the serial)): <code bash>"service_tag"="1GWZ083"</code>
 +  * Specify the manufacturer date: <code bash>"mfg_date"="2020-11-28"</code>
 +  * Specify the WNIC's MAC address: <code bash>"wifi_mac0"="04:6c:59:31:1b:ff"</code>
  
  
Line 211: Line 216:
     * You must be in the **/tmp** directory; it won't work in your home directory: <code bash>cd /tmp</code>     * You must be in the **/tmp** directory; it won't work in your home directory: <code bash>cd /tmp</code>
     * **Read** the **GBB** section of the flash chip and dump the data to a **BIN** file: <code bash>flashrom --read --image GBB:gbb.bin</code>     * **Read** the **GBB** section of the flash chip and dump the data to a **BIN** file: <code bash>flashrom --read --image GBB:gbb.bin</code>
 +      * If you'd like to see the HWID being reported, you can get it out of the file you just created: <code bash>gbb_utility --get gbb.bin --hwid</code>
     * **Write** the **HWID** to the **BIN** file: <code bash>gbb_utility --set --hwid "ROBO D5B-B4K-E5Q-45M-Y8C-A92" gbb.bin</code>     * **Write** the **HWID** to the **BIN** file: <code bash>gbb_utility --set --hwid "ROBO D5B-B4K-E5Q-45M-Y8C-A92" gbb.bin</code>
       * The aforementioned HWID is a valid one for Lenovo 100e Chromebooks, type **81ER**.       * The aforementioned HWID is a valid one for Lenovo 100e Chromebooks, type **81ER**.
Line 246: Line 252:
     * Find the **MAC address** under the ''ifconfig'' and ''network-devices'' sections.     * Find the **MAC address** under the ''ifconfig'' and ''network-devices'' sections.
     * Find the **IP address** under the ''network-devices'' section.     * Find the **IP address** under the ''network-devices'' section.
 +
 +===== Battery Disconnect =====
 +No, this is not about taking apart the device and unplugging your battery...  This is how CBs are shipped.  There's a sequence that allows the device to be powered down and a //software switch// disconnects the battery for long-term storage.  To get out of this mode, you have to plug the CB into a power source - just like you have to do when you unbox a new CB.  
 +
 +  * Charge the device.  
 +    * Ideally, a full charge is nice but Google says 80% is fine.
 +  * With the device plugged into a power source, make sure the device is powered on.
 +  * While holding the **refresh button**((F3)) and the **power button**, pull out the charging cable.
 +    * With touchscreens like Lenovo's 300e CBs, the power button is on the side.  It may be difficult to reach both the buttons with one hand so I tend to use two hands for the buttons while the device is in my lap.  I then use my foot to step on the power cord and then lift the CB away - popping out the power cord.  
 +
 +To get the device to power on after being put into a battery-disconnect state, simply plug the device in and power it on.
 +
  • computers/chromebooks/chromebooks.1601570531.txt.gz
  • Last modified: 2020/10/01 16:42
  • by jon