Contribute
Register

HackinDROM App for OpenCore EFI Creation and Update

Sonoma 14.2.1:
1708090099219.png

1708090129268.png

Vendor and motherboard fields are not selectable.
 
Sonoma 14.2.1:
View attachment 578607
View attachment 578608
Vendor and motherboard fields are not selectable.
As I can see in your first screenshot, you are in "offline mode" (no connection was established between your OS and HackinDROM server) and this is probably the cause.

To check if you can connect to HackinDROM server please visit https://hackindrom.zapto.org/ and see if it works on your browser. If so, relaunch HackinDROM App and try again. If it still fails then something on your OS/Network blocks the connection (VPN? some network controller ?) if so please try disable them and try again

NOTE:
This Vendor / Motherboard configuration doesn't affects the "Right click" update process.
 
As I can see in your first screenshot, you are in "offline mode" (no connection was established between your OS and HackinDROM server) and this is probably the cause.

To check if you can connect to HackinDROM server please visit https://hackindrom.zapto.org/ and see if it works on your browser. If so, relaunch HackinDROM App and try again. If it still fails then something on your OS/Network blocks the connection (VPN? some network controller ?) if so please try disable them and try again

NOTE:
This Vendor / Motherboard configuration doesn't affects the "Right click" update process.
Thanks. Had to add custom rule to adguard home:
@@||hackindrom.zapto.org^
OC is now at 0.9.9, but I have 0.9.7 and it says up to date.
 
Last edited:
Thanks. Had to add custom rule to adguard home:

OC is now at 0.9.9, but I have 0.9.7 and it says up to date.
Hello,
Right now OC 0.9.8 is the latest stable release :

Version 0.9.9 is still in development stage :

You may go from OC 0.9.7 to 0.9.8 ( I do use 0.9.8 ) or ... wait for the final (stable ) version of OC 0.9.9.

Hope we all will see version 1.0.0......0 after Apple's 2024 Event Plan(s) in June :)

Cheers.
 
Thanks. Had to add custom rule to adguard home:

OC is now at 0.9.9, but I have 0.9.7 and it says up to date.

ignore the "Up to date" which is not relevant when you don't update your EFI with admin's provided config.

Simply right click then Update, it will update your EFI to latest OC version (0.9.8)
Screenshot 2024-02-17 at 23.44.40.png
Screenshot 2024-02-17 at 23.51.52.png
 
Anyone encounter this problem? After updated, it shows "OC Beta?"

Snipaste_2024-04-30_22-51-23.png
 
Anyone encounter this problem? After updated, it shows "OC Beta?"

View attachment 582013
Hello @ianccc
Some details about "OC Beta?" label

As Acidanthera do not includes any version in OpenCore.efi file's metadata its difficult to know OC version without executing the .efi file, or without some difficult (hacky) binary research.

I had the idea to get the version by release date from this OC releases page, then compare them to your local OpenCore.efi file's creation date to predict the version it includes.
But it wasn't a great idea as Release date published on GitHub isn't always the same as when OpenCore.efi file was created.

Therefore I made a choice to create a map table where Official OC Release versions is linked to the year + month when the official OpenCore.efi file is created, and the mapping table was updated before a new version is released (sometimes months before) so the updates for you all went flawlessly and with correct OC version label.
It was easy to predict the release date and the version as Acidanthera published a new version on every first Monday of a month.
This worked well until Ukrainian war begin, and then OpenCore updates were released on random dates. (Acidanthera team was/is mainly composed by Russian and Ukrainian developers).

Todays strategy to keep the mapping table up to date is to wait until OpenCore is actually released, then update HackinDROM.app to include the new version and the date. It has its downsides like having "OC Beta?" label, but its still better then showing a wrong version.

Could you please tell me more about your EFI? How it was created, what's the creation date of OpenCore.efi file ?
 
Last edited:
Hello @ianccc
Some details about "OC Beta?" label

As Acidanthera do not includes any version in OpenCore.efi file's metadata its difficult to know OC version without executing the .efi file, or without some difficult (hacky) binary research.

I had the idea to get the version by release date from this OC releases page, then compare them to your local OpenCore.efi file's creation date to predict the version it includes.
But it wasn't a great idea as Release date published on GitHub isn't always the same as when OpenCore.efi file was created.

Therefore I made a choice to create a map table where Official OC Release versions is linked to the year + month when the official OpenCore.efi file is created, and the mapping table was updated before a new version is released (sometimes months before) so the updates for you all went flawlessly and with correct OC version label.
It was easy to predict the release date and the version as Acidanthera published a new version on every first Monday of a month.
This worked well until Ukrainian war begin, and then OpenCore updates were released on random dates. (Acidanthera team was/is mainly composed by Russian and Ukrainian developers).

Todays strategy to keep the mapping table up to date is to wait until OpenCore is actually released, then update HackinDROM.app to include the new version and the date. It has its downsides like having "OC Beta?" label, but its still better then showing a wrong version.

Could you please tell me more about your EFI? How it was created, what's the creation date of OpenCore.efi file ?

Hi,Inqnuam;
Based on the Hackintool, it was on version 0.99. The creation date of Opencore(March 12th) also confirmed it. My original ETF came from the golden build of CaseySJ(https://www.tonymacx86.com/threads/...-i7-12700k-amd-rx-6800-xt.318311/post-2331210). I just updated it several times by HackinDROM. I guess everything still works fine currently.
 
I'm late to this thread, but HackinDROM looks amazing. I'm running .60 OpenCore and Monterery, so in much need of an update. I have the Designare z390 Golden Build and I was having a problem getting HackinDROM to run- kept saying it needed and update.

You can force it to run by Ctrl-Clicking on it. You'll get a 3rd option that allows you to bypass the security check and launch the app - shows up in the menu bar. Thanks for your cool tool.
 
@Inqnuam,

Have you tried using HackinDROM 2.2.1 to update from OpenCore 0.9.9 to the new 1.0.0?

In my case (Asus X670E Gene -- AMD Ryzen), the update process begins but ends with Illegal Hardware Instruction:

Bash:
% pwd
/Applications/HackinDROM.app/Contents/MacOS

% ./HackinDROM
zsh: illegal hardware instruction  ./HackinDROM

I captured a video (attached) and crash log (spoiler below).

Code:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               HackinDROM [1672]
Path:                  /Applications/HackinDROM.app/Contents/MacOS/HackinDROM
Identifier:            Inqnuam.HackinDROM
Version:               2.2 (1)
Code Type:             X86-64 (Native)
Parent Process:        zsh [1161]
Responsible:           Terminal [1157]
User ID:               501

Date/Time:             2024-05-12 05:01:15.6835 -0700
OS Version:            macOS 14.5 (23F79)
Report Version:        12
Anonymous UUID:        713D3043-F874-E002-2155-1F5D1CE5A301


Time Awake Since Boot: 500 seconds

System Integrity Protection: enabled

Crashed Thread:        7

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process:   exc handler [1672]

Thread 0::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                0x7ff802dc93ce mach_msg2_trap + 10
1   libsystem_kernel.dylib                0x7ff802dd7c88 mach_msg2_internal + 84
2   libsystem_kernel.dylib                0x7ff802dd0510 mach_msg_overwrite + 653
3   libsystem_kernel.dylib                0x7ff802dc96bd mach_msg + 19
4   CoreFoundation                        0x7ff802ee61c5 __CFRunLoopServiceMachPort + 143
5   CoreFoundation                        0x7ff802ee4c35 __CFRunLoopRun + 1371
6   CoreFoundation                        0x7ff802ee4112 CFRunLoopRunSpecific + 557
7   HIToolbox                             0x7ff80d8fda09 RunCurrentEventLoopInMode + 292
8   HIToolbox                             0x7ff80d8fd816 ReceiveNextEventCommon + 665
9   HIToolbox                             0x7ff80d8fd561 _BlockUntilNextEventMatchingListInModeWithFilter + 66
10  AppKit                                0x7ff806554c61 _DPSNextEvent + 880
11  AppKit                                0x7ff806e68dc0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1273
12  AppKit                                0x7ff806546075 -[NSApplication run] + 603
13  AppKit                                0x7ff806519ff3 NSApplicationMain + 816
14  HackinDROM                               0x10fdd9dc6 0x10fdd5000 + 19910
15  dyld                                  0x7ff802a7d366 start + 1942

Thread 1:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 3:: com.apple.NSEventThread
0   libsystem_kernel.dylib                0x7ff802dc93ce mach_msg2_trap + 10
1   libsystem_kernel.dylib                0x7ff802dd7c88 mach_msg2_internal + 84
2   libsystem_kernel.dylib                0x7ff802dd0510 mach_msg_overwrite + 653
3   libsystem_kernel.dylib                0x7ff802dc96bd mach_msg + 19
4   CoreFoundation                        0x7ff802ee61c5 __CFRunLoopServiceMachPort + 143
5   CoreFoundation                        0x7ff802ee4c35 __CFRunLoopRun + 1371
6   CoreFoundation                        0x7ff802ee4112 CFRunLoopRunSpecific + 557
7   AppKit                                0x7ff8066b2bbc _NSEventThread + 122
8   libsystem_pthread.dylib               0x7ff802e0918b _pthread_start + 99
9   libsystem_pthread.dylib               0x7ff802e04ae3 thread_start + 15

Thread 4:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 5:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 6:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 7 Crashed:
0   HackinDROM                               0x10ff51313 0x10fdd5000 + 1557267
1   HackinDROM                               0x10ff4c882 0x10fdd5000 + 1538178
2   HackinDROM                               0x10fe8d1d1 0x10fdd5000 + 754129
3   HackinDROM                               0x10fe8b641 0x10fdd5000 + 747073
4   HackinDROM                               0x10fe94691 0x10fdd5000 + 784017
5   HackinDROM                               0x10ff00171 0x10fdd5000 + 1225073
6   HackinDROM                               0x10fe94791 0x10fdd5000 + 784273

Thread 8:
0   libsystem_pthread.dylib               0x7ff802e04ac0 start_wqthread + 0

Thread 9:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib                0x7ff802dc93ce mach_msg2_trap + 10
1   libsystem_kernel.dylib                0x7ff802dd7c88 mach_msg2_internal + 84
2   libsystem_kernel.dylib                0x7ff802dd0510 mach_msg_overwrite + 653
3   libsystem_kernel.dylib                0x7ff802dc96bd mach_msg + 19
4   CoreFoundation                        0x7ff802ee61c5 __CFRunLoopServiceMachPort + 143
5   CoreFoundation                        0x7ff802ee4c35 __CFRunLoopRun + 1371
6   CoreFoundation                        0x7ff802ee4112 CFRunLoopRunSpecific + 557
7   CFNetwork                             0x7ff8082b6b2d 0x7ff80806f000 + 2390829
8   Foundation                            0x7ff803e8ed9c __NSThread__start__ + 1013
9   libsystem_pthread.dylib               0x7ff802e0918b _pthread_start + 99
10  libsystem_pthread.dylib               0x7ff802e04ae3 thread_start + 15


Thread 7 crashed with X86 Thread State (64-bit):
  rax: 0x000070000aed1cb0  rbx: 0x000070000aed1c88  rcx: 0x0000000000000000  rdx: 0x0000000000000000
  rdi: 0x000070000aed1cd8  rsi: 0x000070000aed1cb0  rbp: 0x000070000aed1d80  rsp: 0x000070000aed1c80
   r8: 0x00000000000000cb   r9: 0x000000009145d813  r10: 0x00000000000000bb  r11: 0x000070000aed1cb0
  r12: 0x7250444d41434d53  r13: 0x00007ff8463e6c48  r14: 0x00007fdf49071040  r15: 0xef726f737365636f
  rip: 0x000000010ff51313  rfl: 0x0000000000010246  cr2: 0x0000000000000000
 
Logical CPU:     8
Error Code:      0x00000000
Trap Number:     6

Thread 7 instruction stream:
  45 d0 48 8d 7d d0 e8 92-25 ec ff 48 8b 45 80 48  E.H.}...%..H.E.H
  89 45 c8 48 8d 7d c8 45-31 f6 45 31 ff 48 8b 5d  .E.H.}.E1.E1.H.]
  b0 e8 77 25 ec ff 48 89-df e8 09 7e 0a 00 4c 89  ..w%..H....~..L.
  f0 4c 89 fa 48 81 c4 d8-00 00 00 5b 41 5c 41 5d  .L..H......[A\A]
  41 5e 41 5f 5d c3 0f 0b-48 8d 3d fe 49 11 00 48  A^A_]...H.=.I..H
  8d 35 97 b6 fd ff e8 0e-7f 0a 00 e9 24 fe ff ff  .5..........$...
 [0f]0b 66 66 2e 0f 1f 84-00 00 00 00 00 55 48 89  ..ff.........UH.    <==
  e5 41 57 41 56 41 55 41-54 53 48 81 ec a8 00 00  .AWAVAUATSH.....
  00 48 89 95 40 ff ff ff-48 89 b5 48 ff ff ff 48  [email protected]
  89 fb 48 8b 05 ec d6 0f-00 48 8b 00 48 89 45 d0  ..H......H..H.E.
  31 ff e8 d0 6d 0a 00 48-89 85 30 ff ff ff 48 8b  1...m..H..0...H.
  40 f8 48 89 85 38 ff ff-ff 48 8b 40 40 e8 7b ad  @.H..8...H.@@.{.
 

Attachments

  • Screen Recording 2024-05-12 at 5.01.06 AM.zip
    2.1 MB · Views: 3
Back
Top