The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Ask Question. Asked 5 years, 1 month ago. Active 12 months ago. Viewed 2k times. My questions are: At this point it looks like a lost cause to get ChromeOS back on here, and I'd rather something like LinuxMint anyway. So that's what I'd like to attempt. Do I have to overwrite the bootloader to do this?
I'm okay with that. Is this a lost cause since the TPM module is apparently dead? Josh M. That will be a last resort. Mar 1 '15 at TPM module received. No clue what to do now!
I assume it has to be initialized with some key from the old module Apr 1 '15 at I believe if the netbook is also to be sold in China then there has to be a way to disable the chip even if it's TPM 2.
You might have a hard time finding out the correct CMOS position though. Not an answer about installing Linux, but this will probably fix the tpm error: just turn the chromebook on, wait until the error screen comes up, leave it on like this for 30 seconds, then turn it off. Wait a few seconds then repeat. Within cycles of this, the Chromebook should start booting properly again.
I used to work at a helpdesk in a school district that used Chromebooks, and this worked for me all three times I encountered that tpm error, though I always lost count of how many cycles it took. A link from Google product forums about this as well: support.
Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
The Overflow Blog.
ChromeOS is missing or damaged - TPM read error in rewritable firmware
The Overflow How many jobs can be done at home? Socializing with co-workers while Social distancing. Featured on Meta. Community and Moderator guidelines for escalating issues via new response….Currently known exploits are computationally expensive; specifically, for RSA keys of bit sizethe researchers give an estimate of Note that this figure might drop as more researchers look at the attack.
At the current point in time, it means TPM-generated RSA keys can't be broken at large scale, but targeted attacks are possible. Slowing down brute-force attacks against encrypted user data. The page Protecting Cached User Data describes this in more detail. The vulnerability allows the attacker to brute-force the encryption key bit size off-device. However, note that off-device brute-force attacks are only advantageous against strong passwords - weak passwords are still less expensive to brute-force against the TPM regardless of whether it runs vulnerable firmware or not.
The vulnerability allows attackers to determine the private key. The bit size of generated and imported keys depends on parameters. Chrome OS Verified Access allows network services to verify client device integrity and identity. Attackers can exploit the vulnerability to break an "Attestation Identity Key", which allows them to impersonate a legit device from an endpoint of their choice. In Chrome OS M60, we strengthened Chrome OS user data protection using the scrypt password hashing scheme to act as a second line of defense even in case the brute-force protection afforded by the TPM is lost.
Users were automatically upgraded to the new scheme behind the scenes without user-observable effects. This measure guarantees adequate protection of encrypted user data for users that use strong passwords. If your password isn't strong, now is a good time to fix this - the risk involved with using a weak password generally transcends Chrome OS and affects other places that store sensitive data.
For hardware-backed encryption keys and Verified Access, mitigations are technically infeasible without losing the hardware binding, and thus breaking the feature. The only supported path to restore the designed security strength for these features is to update TPM firmware. Upgrade to a newer version and check again. Here is the complete list of affected devices with code names and marketing names:. After installing the update, RSA keys generated by the TPM are no longer vulnerable against the attack described above.
There is a problem with firmware update installation on that device, we intend to ship an update with a fix to enable the TPM firmware update as soon as possible. This means that all data held by the TPM will be discarded. This includes disk encryption keys, implying all user data stored locally on the device will be lost. Thus, you need to carefully backup any important data before you install the update. We are actively working on ways to allow updated TPM firmware to be installed without losing all data on the device.
Launch dates for these non-destructive update flows are not confirmed at this point though. There is also a risk that the update will fail e. See below for more information on how to recover from this situation. You'll need Chrome OS recovery media in order to invoke the recovery flow. You will want to make sure that you either prepare it before starting the TPM firmware update just in case or have another computer available to create recovery media in case you need it.
There is no one-size-fits-all advice on whether to install the update or not. As described above, there are inherent inconveniences and risks associated with the update process and a limited set of features is impacted by the vulnerability.
In order to help make an informed decision, here is some guidance. If any of the following applies, consider installing the update:. You rely on the highest level of protection that Chrome OS can offer for your encrypted user data TPM-backed protection against password brute-forcing attacks.
You are using hardware-backed encryption keys and corresponding certificates to access network services such as corporate web sites, VPNs. You are using Verified Access for device authentication on your enterprise-managed Chrome OS devices. When in doubt, ask your administrator. If none of the bullets above apply to you, you don't benefit from the update and can safely skip it, thus avoiding potential complications due to failing updates as described above.Can someone please help me out here?
What made this happen for me was pressing escape refresh and power during the Enterprise enrollment loading screen. This is the one that you get after rebooting the whole device, for me which was back into verified mode after a failed attempt at activating dev mode, which is blocked.
Now, I just finished logging in to my school account so that it knows you are part of the Enterprise. Right during the loading screen was when I hit the keybind for recovery mode, and it never booted normal again, it just went back to the missing or damaged screen whenever I tried to restart it.
What's weird though is that although dev mode is blocked, like I said, when I tried and failed to recover the devices os with a recovery drive it says that I should turn os verification back on, and that I was in dev mode. Didn't find what you were looking for? Ask the community or Ask the Virtual Agent. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.HP Chromebook TPM Read Error
Showing results for. Search instead for. Did you mean:. It has been a while since anyone has replied. Simply ask a new question if you would like to start the discussion again.
All forum topics Previous Topic Next Topic. New member. Message 1 of 2. HP Recommended. Product: HP Chromebook 13 G1. Tags 6. Tags: boot. Message 2 of 2. Be alert for scammers posting fake support phone numbers on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
Member levels indicate a user's level of participation in a forum.
ChromeOS is missing or damaged - TPM read error in rewritable firmware
The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level These activities can increase your level in a forum:. This comment originated in the Google Product Forum. To report abuse, you need to leave the current Help page.
Copy and paste the first three lines you see here. Ethans Chromebook. Community content may not be verified or up-to-date. Learn more. Recommended Answer. Leave on for at least 30 seconds. Power off the chromebook. The chromebook will eventually reset itself properly.
Yes No. Are these managed Chromebooks?Google Help. Help Center Community Chromebook.
Subscribe to RSS
Considering a Chromebook? New to Chromebooks. Tour of your Chromebook. Connect to your phone. Use mobile networks.
Connect to other devices. Fix connection problems. Add apps and extensions. Phone and video calls. Files and downloads. Use Progressive Web Apps. Users and sync. Operating system and browser. Advanced settings. Turn on Chromebook accessibility features. Zoom in or magnify your Chromebook screen. Use the built-in screen reader. Use a braille device with your Chromebook.
Use the on-screen keyboard. Use your Chromebook keyboard. Hear text read aloud. Automatically click objects on your Chromebook. Get image descriptions on Chrome. Reset your Chromebook to factory settings. Recover your Chromebook.
Report a problem or send feedback. About managed devices. Get help from your Chromebook manufacturer. Other devices and accessories.Chrome Blog. Chromebook security: browsing more securely Friday, July 29, Chromebooks take Chrome and its core values simplicity, speed and security and apply them to our own operating system infrastructure.
The result is a multi-layered set of defenses which boosts the security of Chromebooks against malicious software that could compromise and linger on the system. Baked in, seriously Our security model is rooted in two pieces of hardware that ship with every Chromebook: a custom firmware chip and a Trusted Platform Module TPM.
The custom firmware chip consists of two parts: a read-only firmware and a read-write firmware that can be updated.
When you press the power button, our read-only firmware starts a process we call Verified Boot. It uses an embedded bit RSA public key to verify the cryptographic signature on the read-write firmware. After the read-only firmware verifies and runs the read-write firmware, the latter performs a similar verification operation on the operating system kernel before running it. The operating system kernel will then continue the verification process as it loads all of the system software, like Chrome.
To put this into perspective, the system does all this in about 8 seconds. If you don't want to boot Google-verified software — let's say you built your own version of Chromium OS — no problem. You can flip the developer switch on your device and use the Chromebook however you'd like. The updater checks with the server securely and downloads updates when they become available. It keeps the system updated against emerging threats and allows for new features to be rolled out seamlessly.
Since every Chromebook keeps two copies of the operating system, it's easy to update and then switch to the new version without interrupting your normal flow.
In addition, it allows for the Chromebook to revert to the known working version if there are any problems during the update. Signing in, with confidence Signing in to the Chromebook is as simple as using your Google Account. The first user of a Chromebook can determine who else is allowed to sign in or choose to keep her machine open for anyone to sign in. The encrypted store is implemented using the Linux kernel's eCryptfs with keys that are protected by the TPM.
Or don't sign in at all Chromebooks also offer the ability to browse without signing in. We call this function Guest Mode.
When Guest Mode is used, Chrome runs with the usual privacy measures of incognito modebut none of the browsing data, including downloads, will stick around.This document describes the usage of a Trusted Platform Module TPM in Chrome devices Chromebook or other form factorsincluding firmware, operating system, and applications.
The rest of this document first discusses the four different modes of operation of Chrome devices; then it describes how Chrome OS controls TPM ownership; and finally it presents each area of TPM usage in detail.
A Chrome device can be booted in four different modes, corresponding to the settings of two switches physical or virtual at power on. They are the developer switch and the recovery switch. They may be physically present on the device, or they may be virtual, in which case they are triggered by certain key presses at power on.
When both switches are off, the boot is called normal mode boot. When the developer switch is on, it is called developer mode boot. When the recovery switch is on, it is called recovery mode boot and normal-recovery or developer-recovery when there is a need to distinguish them. These modes give users a choice between a high degree of security or complete control over the device.
In normal mode, the device is running a Google-provided copy of Chrome OS, which cannot be altered assuming the hardware has not been tampered with. In developer mode, users can run a modified copy of Chromium OS or any other supported operating systemthough without some of the Chrome OS security defenses.
In normal mode, Chrome OS attempts to establish a TPM owner with a random password, which is generated only after the owner of the Chrome device starts using it.
When the owner password is created, there is a period of time in which the user can find out what it is and write it down. After this period, the password is destroyed.
However, knowledge of the owner password is not necessary at any point in Chrome OS. Under certain conditions, the TPM owner will be cleared, rendering keys currently protected by the TPM useless and therefore the data protected by those keys unrecoverable. These conditions are as follows:. When a non-Chrome OS image is booted in developer mode, it is up to that user-installed OS to decide whether or not to take ownership, or do anything at all with the TPM. In the event that the NVRAM kernel space is removed, the device will only boot a Google-provided recovery image, which will try to reconstruct that space.
Chrome OS recovery will aggressively destroy other spaces as needed to make room. Each link in the chain is responsible for verifying that the next link has not been tampered with before yielding control to it.
For security, the automatic update process does not allow updating to versions of the software that are older than the current one. The kernel space can be removed in developer mode, but the firmware space cannot. Also note that a Chrome OS recovery image will try to recreate the kernel space, possibly removing other spaces to make room.
The firmware space contains the read-write firmware version number among other things.