zorz Posted October 21, 2015 Share Posted October 21, 2015 I'll try after my job That's after 18:00 CET Link to comment Share on other sites More sharing options...
uglyJoe Posted October 21, 2015 Share Posted October 21, 2015 He must first disable SIP. Use this Defaults.plist.To boot the OS X Installer, it dosen't matter if SIP is disabled or not. The kext's are cached in the prelinkedkernel. Only after the first reboot, SIP must be disabled to install the kext's to the HD. Link to comment Share on other sites More sharing options...
crusher Posted October 21, 2015 Share Posted October 21, 2015 To boot the OS X Installer, it dosen't matter if SIP is disabled or not. The kext's are cached in the prelinkedkernel. Only after the first reboot, SIP must be disabled to install the kext's to the HD. He try install El Cap via Clover!!!!! Link to comment Share on other sites More sharing options...
MattsCreative Posted October 21, 2015 Share Posted October 21, 2015 I'll try after my job That's after 18:00 CET best not to over complicate things just install with clover and do it the fast and smart way Link to comment Share on other sites More sharing options...
uglyJoe Posted October 21, 2015 Share Posted October 21, 2015 He try install El Cap via Clover!!!!! But we are not talking about Clover Link to comment Share on other sites More sharing options...
zorz Posted October 21, 2015 Share Posted October 21, 2015 i don't want Clover because i have bad experience. Never, but never, success install with Clover. Only Chameleon with Extra folder... I want to try uglyJoe method because have an Ozmosis in BIOS working perfectly with Yosemite... Link to comment Share on other sites More sharing options...
MattsCreative Posted October 21, 2015 Share Posted October 21, 2015 i don't want Clover because i have bad experience. Never, but never, success install with Clover. Only Chameleon with Extra folder... I want to try uglyJoe method because have an Ozmosis in BIOS working perfectly with Yosemite... yes but it wont work with 10.11 right now thats why most oz users use clover for install and oz for boot after they did what i did Link to comment Share on other sites More sharing options...
zorz Posted October 21, 2015 Share Posted October 21, 2015 Ok If no success with uglyJoe method i'll try with clover. Promise Link to comment Share on other sites More sharing options...
Aigors Posted October 21, 2015 Share Posted October 21, 2015 Hi, it's' mandatory build usb key on Yosemite? i have built my el-capitan usb key on Mavricks and doesn't work, but i suspect some my issue. Link to comment Share on other sites More sharing options...
MattsCreative Posted October 21, 2015 Share Posted October 21, 2015 Ok If no success with uglyJoe method i'll try with clover. Promise wait try my method with oz but place fakesmc inside system/library/extensions if you can boot with -s with the installer Link to comment Share on other sites More sharing options...
uglyJoe Posted October 21, 2015 Share Posted October 21, 2015 Hi, it's' mandatory build usb key on Yosemite? i have built my el-capitan usb key on Mavricks and doesn't work, but i suspect some my issue. It is not mandatory but different, see fusion71au's guide at #4 http://www.insanelymac.com/forum/topic/308034-how-to-create-an-el-capitan-installer-which-doesnt-need-bootloader-kext-injection-fakesmc-in-pre-linked-kernel/?do=findComment&comment=2168466 Link to comment Share on other sites More sharing options...
zorz Posted October 22, 2015 Share Posted October 22, 2015 Here are my report: 0. All works fine till point 8. commands executing. 1. My system don´t boot with boot args kext-dev-mode=1 in nvram... I reset nvram with success and load kext-dev-mode=1. Reading nvram kextedvmode was there but after rebooting no kextdevmode in nvram 2. All marks well done till point 8. when command "kextcache -u /Volumes/OS\ X\ Base\ System" don´t load FakeSMC and Realtek kexts in newly formed "prelinked kernel" but also "kextcache" komand working well on my base system Yosemite. Give You an output: I think my mistake is strange nvram problem which does not load values into and no kexts load in "prelinked kernel"... Any HELP?! Link to comment Share on other sites More sharing options...
uglyJoe Posted October 22, 2015 Share Posted October 22, 2015 Your terminal output looks good! bash-3.2# chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions bash-3.2# chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions bash-3.2# touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions bash-3.2# kextcache -u /Volumes/OS\ X\ Base\ System /Volumes/OS X Base System locked; waiting for lock. Lock acquired; proceeding. If all steps till 8 are fine, you should be able to boot the pen drive. For install FakeSMC and Lan after the first reboot you need to set csr-active-config via nvram nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config=%67%00%00%00 Reboot to Yosemite and check with 'nvram -p' if the setting is present.If not, put it in your oz defaults.plist <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>kext-dev-mode=1</string> <key>csr-active-config</key> <data>ZwAAAA==</data> </dict> kext-dev-mode is for Yosemite only. csr-active-config is for El Capitan only. Link to comment Share on other sites More sharing options...
zorz Posted October 22, 2015 Share Posted October 22, 2015 Just now tried to boot wit inserted "nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config=%67%00%00%00" without no success In my EFI/Quo folder i haven´t any .plist and i make it from Your suggestion, and then i have get an output from the picture but still no success. Where i am wrong (stopped at same point as all times before)?!?!? Link to comment Share on other sites More sharing options...
Mrengles Posted October 22, 2015 Share Posted October 22, 2015 @zorz I know others have said removing injected kext extensions from your UEFI/Bios is not required, but my experience contradicts those statements. Link to comment Share on other sites More sharing options...
zorz Posted October 22, 2015 Share Posted October 22, 2015 Ok. For couple of minutes i´ll replace my BIOS with original and give it a try then report... Link to comment Share on other sites More sharing options...
uglyJoe Posted October 22, 2015 Share Posted October 22, 2015 FakeSMC and RealtekRTL are loaded. For starting the Installer SIP dosen't matter. Maybe it's USB related. The pen drive is plugged to a USB2 port? Try disabling external USB3 and XHCI in bios. If you flash your original bios, the pen drive can't start because of the missing boot-loader. Link to comment Share on other sites More sharing options...
zorz Posted October 22, 2015 Share Posted October 22, 2015 I´ll try with different USB and yes, it´s in USB2.0 port sticked. Report comeing later, and, yes, of course, if i replace BIOS then no more any loader P.S. Disabling USB3.0, XHCI or EHCI din´t get any result. Next move is t change USB drive... Link to comment Share on other sites More sharing options...
uglyJoe Posted October 22, 2015 Share Posted October 22, 2015 @zorz I know others have said removing injected kext extensions from your UEFI/Bios is not required, but my experience contradicts those statements. For booting the Installer it shouldn't matter but in generally you are right. At the moment I'm running Yosemite on a second disc and El Capitan boots fine, so for me it's ok. But I never got these 'Failed to load ...' messages, like zorz showing at the top of his log. 1 Link to comment Share on other sites More sharing options...
Mrengles Posted October 22, 2015 Share Posted October 22, 2015 For booting the Installer it shouldn't matter but in generally you are right. At the moment I'm running Yosemite on a second disc and El Capitan boots fine, so for me it's ok. But I never got these 'Failed to load ...' messages, like zorz showing at the top of his log. It can't hurt to try and load El Capitan with Oz and without the injected kexts.ffs files. Either it helps and solves his problem, like it did me, or he's in the same boat again... nothing really changes... @Zorz If you would like me to build an Oz 1479 UEFI/Bios for your mother board the same way I did for my machine, just post your current OzmosisDefaults.plist, /EFI/Oz folder and Stock unmodified Bios from motherboard vendor. Or if you feel like doing yourself... check out my OZMTool output log below. Last login: Thu Oct 8 09:03:29 on console robert$ ./OZMTool --ozmcreate --aggressivity 0 --input GigabyteZ77NWiFi-F3.rom --ffs Gigabyte_Ozmosis_1479/ --out Ozmosis-1479-GigabyteZ77NWiFi-F3.rom OZMTool - v0.3 Warning: No KEXT-dir given! Injecting only Ozmosis files! Warning: No DSDT file given! Will leave DSDT as-is! Info: Aggressivity level set to 'Do nothing - Inject as-is'... Injecting FFS into BIOS... * Current file: 'EnhancedFAT.ffs'... * File not existent, inserting at the end of volume * Current file: 'HFSPlus.ffs'... * File not existent, inserting at the end of volume * Current file: 'Ozmosis.ffs'... * File not existent, inserting at the end of volume * Current file: 'OzmosisTheme.ffs'... * File not existent, inserting at the end of volume * Current file: 'PartitionDXE.ffs'... * File not existent, inserting at the end of volume Deleting non required Filesystem FFS... * Removed 'FileSystem' [93022F8C-1F09-47EF-BBB2-5814FF609DF5] succesfully! Reconstructing final image... * Image built successfully! Bios successfully saved to 'Ozmosis-1479-GigabyteZ77NWiFi-F3.rom' Starting verification... if you see any unusual warnings/errors -> DONT USE THE IMAGE! NOTE: You are using this application on your own risk anyway... NOTE: 'parseInputFile: descriptor parsing failed, descriptor region has intersection with BIOS region' can be ignored... ERROR: Failed to dump 'OzmosisDefaults' [99F2839C-57C3-411E-ABC3-ADE5267D960D] ! ERROR: Failed to dump 'SmcEmulatorKext' [DADE1001-1B31-4FE4-8557-26FCEFC78275] ! Link to comment Share on other sites More sharing options...
zorz Posted October 23, 2015 Share Posted October 23, 2015 I have no Defaults.plist in Oz/Quo folder and in my BIOS only Oz v.894 can size (small BIOS chip). Now i tried to install OSX10.11 with Clover instaled on EFI partition of USB and all works perfectly... Canceled installation to prepare something steps if stuck Report come latter. Link to comment Share on other sites More sharing options...
CrazyCreator Posted October 23, 2015 Share Posted October 23, 2015 @zorz look at the website in my signature ... we have a big ozmosis database 1 Link to comment Share on other sites More sharing options...
pmcnano Posted October 23, 2015 Share Posted October 23, 2015 Its so awesome how nobody reads {censored}. 2 Link to comment Share on other sites More sharing options...
zorz Posted October 23, 2015 Share Posted October 23, 2015 Hmmh. Have a problem. When boot into -s mode and check my /dev/ folder, there no my usb listed!!! just recent hdd with all partitions and a bunch of a tty... What is happening with my usb stick and no listed in /dev/? Link to comment Share on other sites More sharing options...
uglyJoe Posted October 23, 2015 Share Posted October 23, 2015 Hmmh. Have a problem. When boot into -s mode and check my /dev/ folder, there no my usb listed!!! just recent hdd with all partitions and a bunch of a tty... What is happening with my usb stick and no listed in /dev/? I am a little confused now. Clover or not? First stage of the installation was successful? If so, you can boot into Yosemite and install the kext from there (see the guide linked above) Link to comment Share on other sites More sharing options...
Recommended Posts