Jailbreak Acer Chromebook CB5-312T-K5X4 to run Linux from USB
0
votes
1
answer
465
views
The other day I tried to get rid other the cheomeOS ony Acer Chromebook CB5-312T-K5X4, but when I went into developer mode and inserted the USB, it said chromeOS not found on this USB. I don't know if I didn't do the steps correctly, or if it is the Chromebook itself.I tried to do the
ctrl +refresh+power button
then I pressed ctrl + d
. After that, I inserted the USB with Linuxmin and I already flashed it through Etcher. But when it rebooted, it said in developer mode, press space to switch to chromeOS or something like that. I am pretty sure that the drivers can run it, but if not please tell me. If I need to jailbreak this laptop or I didn't do it right, please tell me. I would like to install Linuxmint or Ubuntu. I would be willing if this worked with Kali Linux.
When I entered sudo crossystem --all
this popped up:
Valid parameters:
act_fwver [RO/int] Active firmware version
act_kernver [RO/int] Active kernel version
arch [RO/str] Platform architecture
backup_nvram_request [RW/int] Backup the nvram somewhere at the next boot. Cleared on success.
battery_cutoff_request [RW/int] Cut off battery and shutdown on next boot
block_devmode [RW/int] Block all use of developer mode
board_id [RO/int] Board hardware revision number
clear_tpm_owner_done [RW/int] Clear TPM owner done
clear_tpm_owner_request [RW/int] Clear TPM owner on next boot
cros_debug [RO/int] OS should allow debug features
dbg_reset [RW/int] Debug reset mode request
debug_build [RO/int] OS image built for debug features
dev_boot_altfw [RW/int] Enable developer mode alternate bootloader
dev_boot_signed_only [RW/int] Enable developer mode boot only from official kernels
dev_boot_usb [RW/int] Enable developer mode boot from external disk (USB/SD)
dev_default_boot [RW/str] Default boot from disk, altfw or usb
dev_enable_udc [RW/int] Enable USB Device Controller
devsw_boot [RO/int] Developer switch position at boot
devsw_cur [RO/int] Developer switch current position
diagnostic_request [RW/int] Request diagnostic rom run on next boot
disable_dev_request [RW/int] Disable virtual dev-mode on next boot
ecfw_act [RO/str] Active EC firmware
post_ec_sync_delay [RW/int] Short delay after EC software sync (persistent, writable, eve only)
fw_prev_result [RO/str] Firmware result of previous boot
fw_prev_tried [RO/str] Firmware tried on previous boot (A or B)
fw_result [RW/str] Firmware result this boot
fw_tried [RO/str] Firmware tried this boot (A or B)
fw_try_count [RW/int] Number of times to try fw_try_next
fw_try_next [RW/str] Firmware to try next (A or B)
fw_vboot2 [RO/int] 1 if firmware was selected by vboot2 or 0 otherwise
fwb_tries [RW/int] Try firmware B count
fwid [RO/str] Active firmware ID
fwupdate_tries [RW/int] Times to try OS firmware update (inside kern_nv)
hwid [RO/str] Hardware ID
inside_vm [RO/int] Running in a VM?
kern_nv [RO/int] Non-volatile field for kernel use
kernel_max_rollforward [RW/int] Max kernel version to store into TPM
kernkey_vfy [RO/str] Type of verification done on kernel keyblock
loc_idx [RW/int] Localization index for firmware screens
mainfw_act [RO/str] Active main firmware
mainfw_type [RO/str] Active main firmware type
minios_priority [RW/str] miniOS image to try first (A or B)
nvram_cleared [RW/int] Have NV settings been lost? Write 0 to clear
display_request [RW/int] Should we initialize the display at boot?
phase_enforcement [RO/int] Board should have full security settings applied
recovery_reason [RO/int] Recovery mode reason for current boot
recovery_request [RW/int] Recovery mode request
recovery_subcode [RW/int] Recovery reason subcode
recoverysw_boot [RO/int] Recovery switch position at boot
recoverysw_cur [RO/int] Recovery switch current position
recoverysw_ec_boot [RO/int] Recovery switch position at EC boot
ro_fwid [RO/str] Read-only firmware ID
tpm_attack [RW/int] TPM was interrupted since this flag was cleared
tpm_fwver [RO/int] Firmware version stored in TPM
tpm_kernver [RO/int] Kernel version stored in TPM
tpm_rebooted [RO/int] TPM requesting repeated reboot
tried_fwb [RO/int] Tried firmware B before A this boot
try_ro_sync [RO/int] try read only software sync
vdat_flags [RO/int] Flags from VbSharedData
vdat_lfdebug [RO/str] LoadFirmware() debug data (not in print-all)
wipeout_request [RW/int] Firmware requested factory reset (wipeout)
wpsw_cur [RO/int] Firmware write protect hardware switch current position
Asked by 1nonly
(1 rep)
Feb 19, 2025, 04:57 PM
Last activity: Feb 26, 2025, 07:50 PM
Last activity: Feb 26, 2025, 07:50 PM