Jump to content

CodeRush

Retired Developers
  • Content count

    437
  • Joined

  • Last visited

  • Days Won

    10

CodeRush last won the day on August 5 2016

CodeRush had the most liked content!

About CodeRush

  • Rank
    InsanelyMac Sage

Contact Methods

  • Website URL
    https://github.com/NikolajSchlej/
  • ICQ
    136033666

Profile Information

  • Gender
    Male
  • Location
    Deggendorf, Germany

Recent Profile Visitors

13,024 profile views
  1. CodeRush

    [UEFIPatch] UEFI patching utility

    Hi all, today I've joined Apple to work on low-level security and other firmware-related stuff, and this means I can't support OSS tools nor answer any questions. Please move myself to "retired developers" group. I want to thank all members if IM community for your help and testing during UEFIPatch development and hope the tool served you well. So long, and thanks for all the fish. Best regards, CodeRush
  2. CodeRush

    [UEFIPatch] UEFI patching utility

    Broadwell-E users, please try out new (yet untested) patch for BDW-E from here and post your results. Thanks in advance.
  3. CodeRush

    [UEFIPatch] UEFI patching utility

    It's patched correctly.
  4. CodeRush

    [UEFIPatch] UEFI patching utility

    giacomoleopardo, is that Skylake patchset working on your board? If so, I will add it to the next UEFIPatch release. You can try BIOS flashback or this method (use google translate).
  5. CodeRush

    [UEFIPatch] UEFI patching utility

    Kynyo, it's a bug in both Gigabyte descriptor and UEFITool, will try to get rid of it, thanks for pointing me out. You can use hex editor to replace the ME region manually, but I don't recommend doing it at all, use FwUpdLcl to update the existing one, if nothing blocks ypu from it.
  6. CodeRush

    [UEFIPatch] UEFI patching utility

    For all early adopters of OSX on Skylake platfroms, please try this patch out if your board has locked 0xE2: # SiInit | Skylake 299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9 10 P:75080D00800000:EB080D00800000 299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9 12 P:75080D00800000:EB080D00800000 Add it at the end of patches.txt file before running UEFIPatch on your BIOS image. Don't forget to add a space after the last 0. Thanks to PikeRAlpha for pointing me out.
  7. CodeRush

    [UEFIPatch] UEFI patching utility

    @pongal, all UEFI versions for this motherboard are having BIOS Lock enabled, so if you don't want a risky way, buy yourself a cheap CH341A-based SPI programmer (around $5 on Ebay) and forget about all that BIOS Lock stuff.
  8. CodeRush

    [UEFIPatch] UEFI patching utility

    @thegmanosx, if you see "CFG Lock" somewhere in BIOS Setup, change it to Disabled, if not - use AMIBCP to find and set it's default to Disabled, then follow this guide to flash modified Asrock BIOS.
  9. CodeRush

    [UEFIPatch] UEFI patching utility

    Don't see any locking code in that BIOS dump. Factory unlocked maybe?
  10. CodeRush

    [UEFIPatch] UEFI patching utility

    https://github.com/LongSoft/UEFITool/releases/tag/0.20.4
  11. CodeRush

    [UEFIPatch] UEFI patching utility

    You need pattern matching, the value is too big for offset.
  12. CodeRush

    [UEFIPatch] UEFI patching utility

    Is it a .BIO file or a SPI flash dump. If first, you can patch it but it can't be flashed back because of RSA signature that breaks with the patch. The only reliable way to patch Intel BIOS is to dump it using hardware SPI programmer, patch the dump and flash it back.
  13. CodeRush

    [UEFIPatch] UEFI patching utility

    href="/monthly_12_2014/post-1111314-0-85713400-1419879135.png"> Second parameter is not needed for UEFIPatch, this enables drag-n-drop patching under Windows:
  14. CodeRush

    [UEFIPatch] UEFI patching utility

    @ammoune78, the best way to get around this is using SPI flasher with SOIC clip, but it can also be flashed using (non-latest) version of AFU wuth /GAN switch using dump/patch/flash approach. I can't say that it will work for sure, but you can try it.
  15. CodeRush

    [UEFIPatch] UEFI patching utility

    That .1A0 file is not an executable, but a normal BIOS image. The source of "PE32 image with invalid DOS signature" messages are a bunch of files with graphichs packed into files with a wrong section type (10h instead of 01h), this is an MSI bug but I doesn't affect image's integrity. Suggestion: use UEFIPatch as usual, don't look at this messages.
×