Hi everyone. I'm going to attempt an efi lock removal on the model above but have one concern. In the rare case that the original bios is somehow corrupted upon trying to read, would it be a complete loss or could it possibly be recovered? Thank you for your time and the resources you have shared.
darknezz19 wrote: Hi everyone. I'm going to attempt an efi lock removal on the model above but have one concern. In the rare case that the original bios is somehow corrupted upon trying to read, would it be a complete loss or could it possibly be recovered? Thank you for your time and the resources you have shared.
I have started fallowing the guide but am having an issue building flashrom.
pi@raspberrypi:~/flashrom $ sudo make
Replacing all version templates with 0.9.9-unknown.
Checking for a C compiler... found.
Target arch is arm
Target OS is Linux
Checking for libpci headers... found.
Checking version of pci_get_dev... new version (including PCI domain parameter).
Checking if libpci is present and sufficient... yes.
Checking for libusb-0.1/libusb-compat headers... found.
Checking if libusb-0.1 is usable... yes.
Checking for libusb-1.0 headers... not found.
The following features require libusb-1.0: CONFIG_DEDIPROG CONFIG_CH341A_SPI.
Please install libusb-1.0 headers or disable all features
mentioned above by specifying make CONFIG_ENABLE_LIBUSB1_PROGRAMMERS=no
See README for more information.
Makefile:1150: recipe for target 'hwlibs' failed
make: *** [hwlibs] Error 1
Here is the log from the libusb-dev install.
pi@raspberrypi:~ $ sudo apt-get install libusb-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libusb-dev is already the newest version.
libusb-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It says 'libusb-dev set to manually installed.' I'm actively trying to google a solution because linux is new to me. Any ideas?
Edit:
SpuriousSpectre already posted the solution to this problem in his comment on the original blog. Need to also install 'libusb-1.0-1-dev'
Looks like it's compiling now.
Last edit: 7 years 9 months ago by darknezz19. Reason: found solution to issue.
My new issue is when I try the -r argument with flashrom and try to tell it where to save I get this error.
Error: Extra parameter found.
This is my command
sudo flashrom –r "~/Desktop/efi/read.bin" -V -p linux_spi:dev=/dev/spidev0.0 -c "MX25L3206E/MX25L3208E"
If I remove the -r "~/Desktop/efi/read.bin" it detects my chip just fine.
Edit:
went into /efi directory first and then added the -r operator to the end of the command with just the file name.
flashrom -V -p linux_spi:dev=/dev/spidev0.0 -c "MX25L3206E/MX25L3208E" –r read1.bin
Last edit: 7 years 9 months ago by darknezz19. Reason: solution found, for now?
I tried to import my serial number into the clean efi from the repository but the index of where the numbers were didn't line up the same. This coupled with reading about needing to clean the ME region made me think the pearl script was the way to go.
Ran the script, it outputted the modified file and gave the argument to add to flashrom. Interfaced with the spi chip and flashed it and it verified. Removed pi and booted into single user mode without issue, then cleared PRAM, success.
One thing that worried me was when PAVEL KLUKIN said in the script blog post this.
"Make sure that 'RFT' variable has been defined. 'RFT' is a Record Format Type, it may have value 1 or 2 in other cases patching will be incorrect."
Luckily it wasn't an issue but what did he mean by this?
A Big thank you to everyone who made this possible.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
You have declined cookies. This decision can be reversed.
You have allowed cookies to be placed on your computer. This decision can be reversed.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.