search

rainestorme / murkmod

A continuation of fakemurk and mush that includes a plugin manager and additional useful utilities.
MIT License
21 stars 17 forks source link

Write protection error when using devmode installer. #84

Closed Eboi47 closed 2 months ago

Eboi47 commented 2 months ago

Describe the bug When using the Devmode installer, there will be an error complaining about having write protect on somewhere along the installation. For whatever reason, rebooting the Chromebook will make it act as a successfully murkmodded Chromebook, but some things are missing. However, if you run the Installer command again, it will work correctly without error.

To Reproduce Steps to reproduce the behavior:

  1. Open the terminal with CTRL+ALT+ ->
  2. Log in as root and run the installer command
  3. Do everything it says and wait.
  4. See error

Expected behavior The Chromebook should install murkmod successfully the first time.

Screenshots PXL_20240915_224516462

System (please complete the following information):

Additional context -When rebooting after error, murkmod will be missing plugins, emergency reverting, and various other things will be missing or broken. -This does not actually mess up installation if you just run the installer again, but does mess it up if you only reboot.

rainestorme commented 2 months ago

During installation, the installer tries to set your GBB flags to 0x8091 - it should just continue regardless if write-protect is enabled on your flash chip, but clearly it is not. This is indeed not the intended behavior. You're right, though - most preliminary assets will be installed to your system, and the rest can be repaired by rerunning the installer (through the update shortcut in mush).