Unenrollment not working - It enrolls again
Opened this issue · 4 comments
Describe the bug
When booting chrome os and connecting to the wifi, it enrolls again
Steps to reproduce the behavior:
- Enter shimboot normally, the same way you would with sh1mmer
- Boot chrome os through Root A (I haven't tested Root B yet) (Prompts: "n" on the frist one and "y" in the second)
- Connect to the wifi and go through the setup normally
- Enrollment shows up and the device ends up still enrolled
Expected behavior
After booting into chrome os and connecting to the wifi network, the device enrolls again, even if I press "y" in the "unenrollment" prompt
Target Chrome OS Device:
- Board Name: octopus
- Device Name: bluebird
- Shimboot version: 1.1.1
Additional context
No additional context needed
You need to select "y" on both prompts.
You need to select "y" on both prompts.
I tried that, but chrome os didn't even boot, so I need to do that to get into chrome os. When I press "y" on both of them, the chrome os logo just pops up and hangs there, and if I press "n" and then "y", then it actually boots, with the VT-2 terminal and everything
Maybe you need to force a powerwash. Inside the Debian install, use dd to corrupt the first partition of the internal eMMC drive.
sudo dd if=/dev/urandom of=/dev/mmcblk1p1 bs=1M count=1 oflag=sync
You may need to use /dev/mmcblk0p1 instead of /dev/mmcblk1p1. Use sudo fdisk -l to check which device name is correct.
I can't even access chrome os now. I think that's probably because I updated to chrome os 126 and got kernver 4. Before, I had chrome os 120 and kernver 3