Closed Evanlol123 closed 1 week ago
You may have just messed up actually installing murkmod. Recover with version 105 or later, then unenroll and try using murkmod again, record the terminal output just before the chromebook reboots just in case the issue happens again.
So i should do badrecovery then recover again then try murkmod?
Doesn't Murkmod recover you already?
Try using badrecovery again, if that doesn't fix the issue then you'll need to recover the Chromebook with a valid recovery image. I am not super familiar with badrecovery anyway, so I would consider using SH1mmer if this error persists.
I tried again after doing badrecovery, but it did the same thing
I am going to disable hardware write protection and then set gbb flags, and it should fix the issue, but it's annoying that it doesn't work beforehand
Badrecovery is iffy, just try recovering again and everything should work.
Describe the bug So I installed murkmod after using bad recovery and it says devmode is blocked and then I have to recover
To Reproduce Steps to reproduce the behavior:
Expected behavior Devmode would be unblocked allowing me to use murkmod on my Chromebook
System (please complete the following information):