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

Murkmod fails to re enroll, but still installs when using Cryptosmite #87

Open Eboi47 opened 2 months ago

Eboi47 commented 2 months ago

Describe the bug When Murkmod finishes installing, it gives you an error about write protection being on, and then says it installed and reboots. When you boot the Chromebook and press CTRL + D the Chromebook will not enroll. The Chromebook will act as if it was a personal device. It still installs because if you log in or browse as guest, pressing CTRL + ALT + T still boots the mush terminal instead of crosh.

To Reproduce Steps to reproduce the behavior:

  1. Install Murkmod with the Devmode installer
  2. Press CTRL + D if the Devmode screen shows
  3. Connect to wifi
  4. The Chromebook will not be enrolled and act as a personal device.

Expected behavior Chromebook should enroll successfully

Screenshots PXL_20240919_224432168

System (please complete the following information):

Additional context -This just started happening recently. -Attempting to enter secure mode results in something went wrong screen, but doesn't brick the device. -This error doesn't happen 100% of the time, and the cause is unknown.

rainestorme commented 2 months ago

This could have something to do with cryptosmite. I'm not very familiar with it, and I'm not sure of the internals as much as I am with other methods of unenrollment.

rainestorme commented 2 months ago

Try enabling secure mode, reinstall everything from scratch with a stock recovery image, and try unenrolling and running everything again. Other than that, I have no clue how to troubleshoot.

Eboi47 commented 2 months ago

I worked this time, but it seems to work with v119 best, it might only work with v119. However, v119 is unstable and buggy, but it still works. I don't think cryptosmite has an official way to re-enroll, but it is the only thing I can use because using a recovery image that works with SH1mmer results in an out-of-date error.