crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Nick

crwdns2934249:0crwdne2934249:0:

-The newer "CR-49" Chromebooks use an NVRAM "write protect" flag, not a physical flag. ***You have to be able to boot it into dev mode (blocked by any competent sysadmin on managed ones), and then you need to go into the terminal.*** [link|https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html|MrChromeboox] has instructions for most of them. Others are the same but you boot it into developer mode and run the shell command, then:
+The newer "CR-49" Chromebooks use an NVRAM "write protect" flag, not a physical flag. ***You have to be able to boot it into dev mode (blocked by any competent sysadmin on managed ones), and then you need to go into the terminal.*** [link|https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html|MrChromeboox|new_window=true] has instructions for most of them. Others are the same, but you boot it into developer mode and run the shell command, then:
[code]
-flashrom --wp-disable.
+flashrom --wp-disable
[/code]
***''This is the only way on Chromebooks newer than the CR-48. Google learned a lot of lessons from the ARM CR-48 series being easily hacked by script kiddies to remove MDM from them illegitimately.''***

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Nick

crwdns2934249:0crwdne2934249:0:

-The newer "CR-49" Chromebooks use an NVRAM "write protect" flag, not a physical flag. ***You have to be able to boot it into dev mode (blocked by any competent sysadmin on managed ones), and then you need to go into the terminal.*** [https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html|MrChromeboox|new_window=true] has instructions for most of them. Others are the same but you boot it into developer mode and run the shell command, then ***flashrom --wp-''disable.''***
+The newer "CR-49" Chromebooks use an NVRAM "write protect" flag, not a physical flag. ***You have to be able to boot it into dev mode (blocked by any competent sysadmin on managed ones), and then you need to go into the terminal.*** [link|https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html|MrChromeboox] has instructions for most of them. Others are the same but you boot it into developer mode and run the shell command, then:
+[code]
+flashrom --wp-disable.
+[/code]
***''This is the only way on Chromebooks newer than the CR-48. Google learned a lot of lessons from the ARM CR-48 series being easily hacked by script kiddies to remove MDM from them illegitimately.''***

crwdns2915684:0crwdne2915684:0:

open

crwdns2934241:0crwdne2934241:0 Nick

crwdns2934249:0crwdne2934249:0:

The newer "CR-49" Chromebooks use an NVRAM "write protect" flag, not a physical flag. ***You have to be able to boot it into dev mode (blocked by any competent sysadmin on managed ones), and then you need to go into the terminal.*** [https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html|MrChromeboox|new_window=true] has instructions for most of them. Others are the same but you boot it into developer mode and run the shell command, then ***flashrom --wp-''disable.''***

***''This is the only way on Chromebooks newer than the CR-48. Google learned a lot of lessons from the ARM CR-48 series being easily hacked by script kiddies to remove MDM from them illegitimately.''***

crwdns2915684:0crwdne2915684:0:

open