Jump to content
Andy Vandijck

AutoAMDTool 1.0 (Automatic system decrypter + cpuid patcher)T

18 posts in this topic

Recommended Posts

I have written a tool to auto-patch cpuids and auto-decrypt system binaries on Mountain Lion and Lion.

It is based on AutoAPBDecrypt but uses a launcher to elevate itself to admin rights.

This way it can directly patch and replace the system binaries. ;)

Pre-built binaries for Mountain Lion and Lion are built.

Source is, as usual, also included in the zip package.

Make sure you do a Time Machine backup just to be safe.

Enjoy ;)

AutoAMDTool.zip

Share this post


Link to post
Share on other sites
Advertisement

Hi Andy, I've tried the tool as soon as I start the tool and select them the partition, the tool breaks down and closes.

PS: I've put all binaries in the original condition (Intel) and then tested with your new tool

 

after I have the tool enabled a second time I get a kernel panic.

Edited by spakk

Share this post


Link to post
Share on other sites

Hi Andy, I've tried the tool as soon as I start the tool and select them the partition, the tool breaks down and closes.

PS: I've put all binaries in the original condition (Intel) and then tested with your new tool

 

after I have the tool enabled a second time I get a kernel panic.

That's odd.

The crash is related to the opemu... :s

Share this post


Link to post
Share on other sites

Interesting. If i'm not wrong, a 32-bit instruction, right?

Somewhere in the user trap.

Not sure wether it is 32/64 bit.

By default my app is 64bit but it does support running in 32-bit (Right click, Get Info, 32-bit).

Could I get some more feedback please?

I need other testers since I am at a loss...

It should work just fine the way it is...

Share this post


Link to post
Share on other sites

Running Lion 10.7.5 with ItTz ShAnE's kernel (XNU 11.4.0).

 

$ ./AutoAMDToolLauncher.app/Contents/Resources/MacOS/AutoAMDToolLauncher
./AutoAMDToolLauncher
objc[386]: Object 0x104c1d330 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1d690 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1da30 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1daa0 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1dc10 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1dd10 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1de20 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[386]: Object 0x104c1d8d0 of class __NSCFData autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
$

After authenticating, it asks where to scan, then, after an unbelievably short time, it disappears. I guess it's crashing?

 

Now I'll try with my nVidia card just in case it did do anything.

 

EDIT: Aha! I ran this directly from Terminal. It's been scanning and spewing output for the past few minutes.

 

 

$ sudo AutoAMDTool/Release\ Lion/AutoAMDToolLauncher.app/Contents/Resources/AutoAMDTool.app/Contents/MacOS/AutoAMDTool
...lots of this
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
ERROR: Unsupported or no Mach-O file
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 1 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 1 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patching universal binary (50 architectures)
Skipping non-Intel architecture (0)
Skipping non-Intel architecture (1)
Skipping non-Intel architecture (2)
Skipping non-Intel architecture (3)
Skipping non-Intel architecture (4)
Skipping non-Intel architecture (5)
Skipping non-Intel architecture (6)
Skipping non-Intel architecture (7)
Skipping non-Intel architecture (8)
Skipping non-Intel architecture (9)
Skipping non-Intel architecture (10)
Skipping non-Intel architecture (11)
Skipping non-Intel architecture (12)
Skipping non-Intel architecture (13)
Skipping non-Intel architecture (14)
Skipping non-Intel architecture (15)
Skipping non-Intel architecture (16)
Skipping non-Intel architecture (17)
Skipping non-Intel architecture (18)
Skipping non-Intel architecture (19)
Skipping non-Intel architecture (20)
Skipping non-Intel architecture (21)
Skipping non-Intel architecture (22)
Skipping non-Intel architecture (23)
Skipping non-Intel architecture (24)
Skipping non-Intel architecture (25)
Skipping non-Intel architecture (26)
Skipping non-Intel architecture (27)
Skipping non-Intel architecture (28)
Skipping non-Intel architecture (29)
Skipping non-Intel architecture (30)
Skipping non-Intel architecture (31)
Skipping non-Intel architecture (32)
Skipping non-Intel architecture (33)
Skipping non-Intel architecture (34)
Skipping non-Intel architecture (35)
Skipping non-Intel architecture (36)
Skipping non-Intel architecture (37)
Skipping non-Intel architecture (38)
Skipping non-Intel architecture (39)
Skipping non-Intel architecture (40)
Skipping non-Intel architecture (41)
Skipping non-Intel architecture (42)
Skipping non-Intel architecture (43)
Skipping non-Intel architecture (44)
Skipping non-Intel architecture (45)
Skipping non-Intel architecture (46)
Skipping non-Intel architecture (47)
Skipping non-Intel architecture (48)
Skipping non-Intel architecture (49)
ERROR: Unsupported or no Mach-O file
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 1 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 1 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 3 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 6 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 1 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 8 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
ERROR: Unsupported or no Mach-O file
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 17 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 5 bad instructions, patches bypassed: NO
Patch report: 0 instructions patched, 0 bad instructions, patches bypassed: NO
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file
ERROR: Unsupported or no Mach-O file

...lots of this

 

 

EDIT2: It froze again...

 

EDIT3: I rebooted and tried the 7600GS, just a grey screen with the cursor stuck in the top left corner as usual...

 

EDIT4: Now running Bronzovka's kernel with arch=i386. I was going to try running the tool on /S/L/E only, however it won't scan if I enter "/System/Library/Extentions/" in the box: the following is outputted.

$ sudo sudo AutoAMDTool/Release\ Lion/AutoAMDToolLauncher.app/Contents/Resources/AutoAMDTool.app/Contents/MacOS/AutoAMDTool
2013-02-02 14:39:17.642 AutoAMDTool[252:1a0f] *** -[NSLock unlock]: lock (<NSLock: 0x7fbb4ba20c30> '(null)') unlocked from thread which did not lock it
2013-02-02 14:39:17.643 AutoAMDTool[252:1a0f] *** Break on _NSLockError() to debug.

 

I tried running on / again but captured its output this time before it froze. See attached file.

AutoAMDTool.log.zip

Share this post


Link to post
Share on other sites

Logged on with root.

 

Still crash at the launcher, running from the package contents now. It's working like above mentioned.

 

EDIT: Logging on as root and running it from inside the package contents seems to work. 10 min in the scan of system and hasn't crashed yet! Will update when it's done, or if It crashes

 

EDIT 2: Guess I was very wrong! It killed all my HDD Space for that partition, Click here to view

 

EDIT 3: Copied Extensions to desktop then, Open the package contents again, till the AutoAMDTool in the MacOS folder, ran it in terminal as sudo. Like so:

 

Durans-Mac-Pro:~ durankeeley$ sudo /Users/durankeeley/Desktop/Release\ Mountain\ Lion/AutoAMDToolLauncher.app/Contents/Resources/AutoAMDTool.app/Contents/MacOS/AutoAMDTool

 

. And got the following lines, basically like "instant idiot's" first EDIT.

http://pastebin.com/cDXsMhGv

 

ERROR: Unsupported or no Mach-O file

2013-02-02 20:06:17.925 AutoAMDTool[267:a207] *** -[NSLock unlock]: lock ( '(null)') unlocked from thread which did not lock it

2013-02-02 20:06:17.925 AutoAMDTool[267:a207] *** Break on _NSLockError() to debug

Share this post


Link to post
Share on other sites

Hi Andy, I've tried the tool as soon as I start the tool and select them the partition, the tool breaks down and closes.

PS: I've put all binaries in the original condition (Intel) and then tested with your new tool

 

after I have the tool enabled a second time I get a kernel panic.

 

Hi Andy, I now have everything reinstalled and modified binaries with your tool, unfortunately I get the same message Panic! opemu_utrap the exact same panic message. can it be that the Phenom II X6 T1100 not properly supported entirely by the kernel? Because it's very annoying gradually all other user does not have these problems.

 

as I have already described several times, does this panic message as soon as I open a program or want to, for example, to copy something or want to edit something. :wallbash: :wallbash:

:wallbash: :wallbash:

Share this post


Link to post
Share on other sites

 

 

Hi Andy, I now have everything reinstalled and modified binaries with your tool, unfortunately I get the same message Panic! opemu_utrap the exact same panic message. can it be that the Phenom II X6 T1100 not properly supported entirely by the kernel? Because it's very annoying gradually all other user does not have these problems.

 

as I have already described several times, does this panic message as soon as I open a program or want to, for example, to copy something or want to edit something. :wallbash: :wallbash:

:wallbash: :wallbash:

 

I have a 1050T so not too sure about that. But I'm using an older kernel has I said before, which kernel are you using maybe I can test with that one later today.

 

EDIT: Ok so I did uname -v and I have the same kernel build as your screenshot. I don't know what could be different, I install using iatkos and replaced corecrypto.kext but I did have to use VoodooTSCSync cause DSDT I just can't do, so that allows for all my cores and not have to boot with cpus=1

Share this post


Link to post
Share on other sites

IF anyone is wondering that tests this tool "Unsupported or no Mach-O file" is when amd_insn_patcher runs over a non binary file. So ignore that error.

 

Hi Duran Keeley has the tool works for you? If so? then please upload the binaries which has found the tool here so I can test it.

Share this post


Link to post
Share on other sites

Hi Duran Keeley has the tool works for you? If so? then please upload the binaries which has found the tool here so I can test it.

 

It seems to stop as like if i just run AutoAPBDecrypt 1.1 itself on the NSLock unlock error after amd_inst_patcher has run over files so I guess it has?? To be honest I'm gonna have to reinstall because I have no idea what is patched. If I run AutoAPBDecrypt now my SysDecrypts is empty.

 

I tried to do my whole partition from root user but it killed ALL of my HHD space, like 20GB free to 200mb free :o

Share this post


Link to post
Share on other sites

It seems to stop as like if i just run AutoAPBDecrypt 1.1 itself on the NSLock unlock error after amd_inst_patcher has run over files so I guess it has?? To be honest I'm gonna have to reinstall because I have no idea what is patched. If I run AutoAPBDecrypt now my SysDecrypts is empty.

 

I tried to do my whole partition from root user but it killed ALL of my HHD space, like 20GB free to 200mb free :o

 

I have done differently, I connected my Mountain Lion-USB HDD on my laptop with Mountain Lion and have started the AutoAPBDecrypt 1.1 .There are found seven binaries than i've put these manually into the right place.

Share this post


Link to post
Share on other sites

I have done differently, I connected my Mountain Lion-USB HDD on my laptop with Mountain Lion and have started the AutoAPBDecrypt 1.1 .There are found seven binaries than i've put these manually into the right place.

 

Yeah that would work even better :D

Share this post


Link to post
Share on other sites

Ok so using it on 10.8.3 from 10.7.5

 

Same 7 files,

 

Does anyone else have the problem where every 2 minutes it uses about 1GB of HHD space!???

 

EDIT: Starts to settle down after quitting, thanks again Andy.

Share this post


Link to post
Share on other sites

Mods, could you please move the topic to the AMD Development forum (if Andy agrees, of course)?

It doesn't matter to me.

It may be moved if you think it should be placed there ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By THE M
      Hi,Everyone
      i've struggled to install Mac High Sierra from three days ago  with an strange error then my pc restart ......
      My PC specifications is
      Cpu amd Athlon 620 II x2
      Ram 8g
      Graphic Ati 5670 DDR3 2g
      Motharboard msi 970 amd

    • By thiagomenini
      Hello everybody,
      I'm from Brazil, if someone wants to write in portuguese, i will understand too. But english is fine.
       
      Days ago I installed the High Sierra, using the image (HighSierraAMD V2 UEFI.dmg). I have an FX8320e, the Asus M5A78L-M / USB3 mobo, GTX 750 and 12GB of RAM.
       
      Well, I build Hackintosh to run audio programs. Everything is working except the USB audio card on the card. But I read that some gyus updates to 10.13.4 or higher and it work.
      But I have some problem with startup and shutdown. I had installed the Clover in different ways, but it did not appear at startup. If I do not use the pen drive to boot, I do not have access to the system.
       
      I've tried different solutions. I formatted the EFI partition using the Terminal and reinstalled the Clover, but it also did not work.
       
      The other problem is the shutdown. The system goes off, but the fans and the mobo remains on. I need to manually press the on/off button to turn off the computer. I had used the Clover Configurations App to set the flag (shutdonw fix) but it not work too. I think this might be related to the boot problem.
       
      Thanks for any help!
    • By 5kr1p7
      Just installed Mojave 10.14.1 (guided by the Shaneee tutorial) and faced a number of problems:
       
      Annoying USB related errors loop when system boot (if anyone got this just wait longer). Entering commands in single user mode commands was really challenging with screen full of errors Reboot/shutdown doesn't work (after lines in console just black screen. Need to push reset/power button) Computer doesn't wake up after sleep Browser are crashing on some web pages (Safari and Chrome on same pages (can't login on rutracker.org for example))  
      USB error:
      ... 2019-04-02 23:52:57.982767+0300 0x1adc     Default     0x0                  0      0    kernel: (AppleUSBEHCI) 000122.778171 UHC4@53000000: AppleUSBEHCI::StopUSBBus: USBSTS.HCHalted did not set as expected: USBCMD 0x00010030 USBSTS 0x00004008 2019-04-02 23:52:57.982779+0300 0x1ad3     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.778184 UHC6@56000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000010 2019-04-02 23:52:57.985297+0300 0x1ad3     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.780706 UHC6@56000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:57.985320+0300 0x1ad3     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.780730 UHC6@56000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000008 2019-04-02 23:52:57.985339+0300 0x1ad3     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.780750 UHC6@56000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:58.021308+0300 0x1ad1     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.816718 UHC2@52000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000010 2019-04-02 23:52:58.023653+0300 0x1ad1     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.819066 UHC2@52000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:58.023664+0300 0x1ad1     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.819078 UHC2@52000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000008 2019-04-02 23:52:58.023673+0300 0x1ad1     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.819087 UHC2@52000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:58.088634+0300 0x1ad7     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.884043 UHC4@53000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000010 2019-04-02 23:52:58.091464+0300 0x1ad7     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.886874 UHC4@53000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:58.091481+0300 0x1ad7     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.886893 UHC4@53000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000008 2019-04-02 23:52:58.091495+0300 0x1ad7     Default     0x0                  0      0    kernel: (IOUSBHostFamily) 000122.886909 UHC4@53000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery 2019-04-02 23:52:58.092790+0300 0x1ad8     Default     0x0                  0      0    kernel: (AppleUSBEHCI) 000122.888199 UHC6@56000000: AppleUSBEHCI::StopUSBBus: USBSTS.HCHalted did not set as expected: USBCMD 0x00010030 USBSTS 0x00004008 2019-04-02 23:52:58.131032+0300 0x1ae4     Default     0x0                  0      0    kernel: (AppleUSBEHCI) 000122.926440 UHC2@52000000: AppleUSBEHCI::StopUSBBus: USBSTS.HCHalted did not set as expected: USBCMD 0x00010030 USBSTS 0x00004008 2019-04-02 23:52:58.196398+0300 0x1ae9     Default     0x0                  0      0    kernel: (AppleUSBEHCI) 000122.991807 UHC4@53000000: AppleUSBEHCI::StopUSBBus: USBSTS.HCHalted did not set as expected: USBCMD 0x00010030 USBSTS 0x00004008 ...  
      Can anyone who fixed theese issues share kexts archive, config.plist, kernel newer than the manual? My PC specs in signature.
    • By karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By Fede1132
      Hi guys i have a problem install macOs Mojave on my PC, I have this configuration:

      CPU: Ryzen 7 2700X;
      GPU1: GTX 970 Strix(For game rendering and 144Hz Monitor);
      GPU2: GTX 750ti Strix(For 2nd monitor rendering to get 100% performances from 1st 144Hz Monitor);
      MotherBoard: MSI x470 GAMING PLUS
      Hard Disk 1 (Windows 10): Samsung EVO M.2;
      Hard Disk 2 (For Storage): RAID (1) between two hard disks;
      Hard Disk 3 (For Mojave): Kingston SSD 120GB;

      I have created my USB with this:
       
      Create Bootable USB Code: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install\ macOS\ Mojave.app -- nointeract && say Done. Clover Settings: Boot: Verbose; dart=0; nv_disable=0; kext-dev-mode=1; GraphicsEnabler=No; XMPDetection = No. Cpu: C6. Devices: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Inject (Full Enabled); Add ClockID (Full Enabled); FixOwnership (Full Enabled); Gui: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Enabled (Full Enabled); Screen Resolution: 1920x1080; Kernel and Kext Patches: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Apple RTC (Full Enabled); KernelPm (Full Enabled); SMBIOS: iMac(18,3); System Parameters: Inject Kexts = Yes; Inject System ID; Used Kexts: FakeSMC FakePCIID NVIDIA WEB LILU BIOS: VT-d = Disabled; XHCI Hand-Off = Enabled; Legacy USB Support: Enabled; Hard Disk: AHCI Mode; Selection Mode: Legacy + EUFI; Clover Install Log:
      Full Error Log:
       
×