ChromeOS will fail to boot if device is rebooted on v120 or later

[Eboi47]

Describe the bug
If you use murkmod for the latest version and reboot, the Chromebook will show a screen saying "Confirm returning to secure mode". Pressing confirm will cause a "something went wrong" screen to show up. You have to recover the Chromebook to fix this. The Chromebook then re-enrolls itself and you have to start the whole thing over.

To Reproduce
Steps to reproduce the behavior:

1. Boot chrome OS
2. Reboot however you want (I used Power + Refresh)
3. Click enter when the "Confirm returning to secure mode" screen shows.
4. The "something went wrong" screen should show up.

Expected behavior
The Chromebook should return to the login screen as normal.

Screenshots
There are not any screenshots that would be of any use, sorry!

System Info:

• Board [MAGALOR-DUKI (DEDEDE)]
• Version [v127]
• Installation method used [devmode installer]
  -Unenrollment method used [cryptosmite (SH1MMER)]
  Additional context
  -This issue also causes the Emergency Revert, Re-enroll option in mush, powerwashing, and likely more to brick the chromebook as well.
  -This issue also happened with classic fakemurk on the same version. Perhaps it is because of the additional checks before booting on newer versions.
  -This issue is similar to others, but is slightly different, which is why I included this as a separate issue.
  -I don't know if the unenrollment method matters, but I included it just in case.
  -Using the sign out button works perfectly fine!

[rainestorme]

v127 (and, for that matter, v119 and above) is vastly untested, and this is not an unexpected issue to arise - I'll take a look.

[rainestorme]

Seems tied to #68

[miceoroni]

Same, it appears to be prevalent when fetching a version that is not compatible with the kernver of the chromebook

[Sweepe]

Still a problem, had to use a recovery image to get my Chromebook back to normal

[miceoroni]

same here, appears to be affecting the majority of kv3 peeps.

Still a problem, had to use a recovery image to get my Chromebook back to normal

[Eboi47]

The reason for this issue is because chromeOS versions 120 or higher have more checks for suspicious files on the system. This causes the Chromebook to detect an issue on boot, and brick itself in the process.