How to Fix Somehow broke my USB on one machine and one machine only
This mini-guide provides a structural approach to troubleshoot and fix the issue.
Prerequisites
- Confirm your hardware specifications (CPU, GPU, Motherboard).
- Ensure you have a bootable recovery USB and backup your EFI.
Fix Steps
- Boot with
-v keepsyms=1 debug=0x100to identify the exact kernel panic. - Validate your config.plist using ocvalidate.
- Ensure your EFI matches the Dortania guide specifications for your CPU generation.
Verification
- Reboot and verify if the functionality is restored and stable under typical usage.
Original Question:
So I was trying to add MacOS in as a triple boot alongside two other OSes on my machine. It's a Google Pixelbook running custom firmware. Was having some issues with the recovery server, so I ran a command in Terminal in MacOS Base System (that install USB I made off gib-MacOS) to change the date. The one where you enter "date 00000000," with the month, hour, minute, year, in a specific order. I thought it worked, but afterwards, every time I try to boot the USB, it kernel panics after a few seconds. Every time. I've already synced the RTC back up to my Windows install, but there's something that's been saved and changed that causes problems even with a fresh USB. The MacOS USB still works flawlessly on another custom-firmware'd Pixelbook that I didn't touch, which is the confusing part. How can I undo what that "date" command did to my machine that causes kernel panics?
Firmware: OpenCore
CPU: i7 7Y75
RAM: 16 GB LPDDR3
The Google Pixelbook's motherboard codename is EVE
[link] [comments]
Post a Comment