What would happen if I removed the emmc from the device and then installed Linux on that, reinstalled the chip into the device? Would I be able to dual boot w/o dev mode?
Pardon the edit, I accidentally left the browser mid way through typing so it posted unfinished
1: Why?
2: You would be thrown into recovery mode.
Why would I be thrown into recovery mode? It’s not like any changes have been made to the drive itself, plus if it finds an issue with the total space I could just change how the partition reports the total space so that it seems like nothing changed
I missed the dualboot part. It doesn’t matter though because you still wouldn’t be able to boot anything other than ChromeOS. What exactly are you trying to do here?
I haven’t exactly figured out what I’m trying to do here, other than just see if I can give my teachers a stroke. (My school has the families buy the chromebooks from them for whatever reason before distribution so it’s not school property) Would it be possible to implement a bypass into the firmware without breaking the enterprise enrollment? (despite the chromebooks not being school property anymore they still don’t like people trying to break enrollment, which is exactly what I am not trying to do)
So just flash the firmware
I don’t really know how I would go about reprogramming the firmware to allow for this anyway, plus I am discussing this before actually undertaking the project
the short answer is no, you can’t do anything remotely close to what you’re proposing. If the device is managed, you are not the legal owner, and you’re taking a significant legal risk to try to bypass any of the restrictions on the device.