Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate instructions for disabling RO FW WP on Ti50 Chromebooks from chrultrabook docs #10

Closed
wants to merge 2 commits into from

Conversation

sadlerm4
Copy link

Instructions on disabling RO FW WP on Ti50 Chromebooks was recently added to the docs, I'm opening this PR as part of migrating this to your site instead (chrultrabook/docs#200).

I've taken the liberty of adding it as a new page under firmware/wp where I think it makes sense, but please let me know how you would like best to integrate it with the rest of your site.

@MrChromebox
Copy link
Owner

there is already a small section on the RO firmware verification on disabling.md page, I don't think we need a separate page here just for this section, do you?

@sadlerm4
Copy link
Author

I must be blind, I didn't see what you'd written for step 7 under disabling write protection. Yep totally get it now, you don't need this as well.

@sadlerm4 sadlerm4 closed this Jul 17, 2024
@MrChromebox MrChromebox reopened this Jul 17, 2024
@MrChromebox
Copy link
Owner

I'm not saying we shouldn't expand on what I have, especially the bit on how to boot if RO verification is on, just that we should keep it all on the same page

@sadlerm4
Copy link
Author

sadlerm4 commented Jul 18, 2024

I'll work on doing that then.

To use the CCD you need to run gsctool -a -o from ChromeOS on stock firmware the first time right? So if someone did end up bricking because they used a different method to disable hardware WP and didn't disable RO verification before flashing, even with the temporary fix, they would then need to reflash stock firmware, open the CCD and factory reset CCD flags with a SuzyQ?

Am I understanding that correctly?

@MrChromebox
Copy link
Owner

I'll work on doing that then.

To use the CCD you need to run gsctool -a -o from ChromeOS on stock firmware the first time right? So if someone did end up bricking because they used a different method to disable hardware WP and didn't disable RO verification before flashing, even with the temporary fix, they would then need to reflash stock firmware, open the CCD and factory reset CCD flags with a SuzyQ?

Am I understanding that correctly?

no. All you would need to do is:

  • disconnect battery
  • connect the SuzyQ to another device running Linux
  • open the ttyUSB terminal
  • ccd open
  • ccd reset factory

gsctool can also be run from Linux on the device but have not tested if the commands listed in https://www.chromium.org/chromium-os/developer-library/guides/device/ro-firmware-unlock/ can be run that way

@sadlerm4
Copy link
Author

Sorry for the late reply. So the temporary RO verification fix isn't really related to the permanent fix that you've explained here. In that case, I think that your information is more useful than the current stated temporary workaround for booting when RO verification is still on, but I can find a way to include both methods in the docs.

@MrChromebox
Copy link
Owner

I went ahead and integrated these changes into the wp/disabling page, so don't think we need this PR anymore unless you think some changes are needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants