Andy Vandijck Posted January 31, 2013 Share Posted January 31, 2013 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 8 Link to comment Share on other sites More sharing options...
spakk Posted February 1, 2013 Share Posted February 1, 2013 (edited) 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 February 1, 2013 by spakk Link to comment Share on other sites More sharing options...
Andy Vandijck Posted February 1, 2013 Author Share Posted February 1, 2013 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 Link to comment Share on other sites More sharing options...
theconnactic Posted February 2, 2013 Share Posted February 2, 2013 Interesting. If i'm not wrong, a 32-bit instruction, right? Link to comment Share on other sites More sharing options...
Andy Vandijck Posted February 2, 2013 Author Share Posted February 2, 2013 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... Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 2, 2013 Share Posted February 2, 2013 Using the Mountain Lion release it crashes but it does not crash so suddenly if you view package contents, resources. Run it from there, it runs for a while then crashes with an error report. Error Here http://pastebin.com/Q5vx0YpJ EDIT: Does it matter that I'm using an old kernel with AnVsCoreCrypto? Link to comment Share on other sites More sharing options...
instant idiot Posted February 2, 2013 Share Posted February 2, 2013 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 Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 2, 2013 Share Posted February 2, 2013 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 Link to comment Share on other sites More sharing options...
spakk Posted February 3, 2013 Share Posted February 3, 2013 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: Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 3, 2013 Share Posted February 3, 2013 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: 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 Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 4, 2013 Share Posted February 4, 2013 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. Link to comment Share on other sites More sharing options...
spakk Posted February 4, 2013 Share Posted February 4, 2013 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. Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 4, 2013 Share Posted February 4, 2013 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 Link to comment Share on other sites More sharing options...
spakk Posted February 4, 2013 Share Posted February 4, 2013 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 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. Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 5, 2013 Share Posted February 5, 2013 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 Link to comment Share on other sites More sharing options...
Duran Keeley Posted February 14, 2013 Share Posted February 14, 2013 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. Link to comment Share on other sites More sharing options...
theconnactic Posted February 14, 2013 Share Posted February 14, 2013 Mods, could you please move the topic to the AMD Development forum (if Andy agrees, of course)? Link to comment Share on other sites More sharing options...
Andy Vandijck Posted February 14, 2013 Author Share Posted February 14, 2013 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 Link to comment Share on other sites More sharing options...
Recommended Posts