I'm trying to install iOS 13 on an iPad Air 2 with a broken screen (nothing showing) and possible motherboard damage (based on testing with a third party replacement screen) but Catalina refuses to restore it with the IPSW because of "an unknown error (14)" so I'm trying to use Xcode 11 for it. Is there maybe an easier way to do this?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
If a possible board damage I guess that's reason why you get that error, however you need Xcode 11 beta and Catalina (or latest Mojave), then from Catalina you can use directly the Finder if your iPad is detected and click on it on the left finder sidebar (where are all the volumes), instead from Mojave you have to use iTunes and from both places you should hold "alt" key on "Update" button then you can sideload your IPSW .
I doubt that's the issue. Since restoring iOS 12.3.1 works fine from Mojave and Catalina. The possible board damage is relating to the display. It still sorta functions and I wanted to get iOS 13 for mouse support and try to connect it to an external monitor. I have a new Air 2 on the way already but I don't want this one to go to "waste".
Then or from iTunes (Mojave 10.14.5) or Catalina Finder (left sidebar where you iPad should show as a Volume), hold "alt-option" key on "Update" button, and you should select your IPSW path.
edit:
You have to take Xcode11 beta opened during this process!
I have tried that on Catalina. I don't particularly want to have to upgrade my Mac to 10.14.5 :/
Are you sure you have took the right IPSW for your IpadOS model ?
I mean iPad Air 2 doesn't have officially iOS 13 but IpadOS (that is in some way a different version of iOS 13).
Congratulations! Would you mind sharing what "appropriate nvram args for AMD hardware acceleration" you used? I have DisableLibraryValidation.kext loaded, as well as Lilu and WhateverGreen, but still no joy...AMD RX 580 works in the 3,1 now thanks to netkas's work, just took a bit more effort to get working than we had realized.
I had to use the kext you mentioned to disable library validation.
(...)
Added Lilu and WhateverGreen along with appropriate nvram args for AMD hardware acceleration, VideoProc apparently can't determine the GPU hardware when it is in the 3,1...
They're IPSW bundles for betas. I have one just named "iPad 64-bit Touch ID", so... that should be the right one.
Check your crash logs for windowserver
probably all you need to emulate with a kext is pcmptq xmm0, xmm1 and pcmptq xmm0, xmm2
all these popcnt inAMDSharedIL could be not used on mp3,1, at least when GUI is rendered
then you cna use your kext and all original binaries
but if you want just to get to desktop, without mtl, remove AMDRadeonX4000.kext
Thanks, that made some progress. Without AMDRadeonX4000.kext, 10.14.5 will boot, it recognizes the card as an RX570, but there's no acceleration (as you said). This is the same with or without Lilu/WhateverGreen. I noticed that the X4000 GL driver contains pcmpgtq instructions, so I'm guessing that's why removing the base X4000 driver allows it to work at all.
re: crash logs - with DisableLibraryValidation, Lilu, and WhateverGreen loaded, I don't get any crash logs - it just hangs forever at the first progress bar (white background). Nothing to analyze, just a quiet failure to boot.
Since I can now reliably boot with the RX570 without acceleration, I'll move on to just testing my stuff. Thanks for everyone's help (although if @Ludacrisvp was to pass along his Lilu/WhateverGreen settings, I'd surely try them out).
It worked fine without Lilu / whatevergreen / nvram settings. Those were an added benefit of enabling hardware assisted h264 encode / decode and hardware hevc decode. They didn’t impact getting the card to work.
So, no Lilu/WhateverGreen; you used Netkas' patched driver and the DisableLibraryValidation kext, and that was it? That setup doesn't work on my system, for some reason...
Part of me wonders if all of this MP3,1 with modern AMD cards could / should be in its own thread even if the provided patcher has this function. Based on what my results are the patcher may need to include this DLV kext if we can't figure out why codesign is not accepting this.
Your md5 will likely not match if you have also done a code sign via 'codesign' like I did.
Then check your Library validation kext, after you 'installed it' did you load the kext manually?
I used this to load it
The nvram settings used in conjunction with Lilu / WEG are (you don't have to have the debug and verbose option as they are unrelated to this):
You should also see something like this from kextstat:
I'd check if the patch was installed properly (permissions)So, no Lilu/WhateverGreen; you used Netkas' patched driver and the DisableLibraryValidation kext, and that was it? That setup doesn't work on my system, for some reason...
Your md5 will likely not match if you have also done a code sign via 'codesign' like I did.
Then check your Library validation kext, after you 'installed it' did you load the kext manually?
I used this to load it
Code:
sudo kextutil -v 4 /Library/Extensions/DisableLibraryValidation.kext
Code:
Mac-Pro:~ ludacrisvp$ ls -lh /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
-rwxr-xr-x 1 root wheel 1.7M Jun 16 00:08 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
Mac-Pro:~ ludacrisvp$ md5 /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
MD5 (/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver) = e33bf93570636e97bb37b6f374ab9e2b
Mac-Pro:~ ludacrisvp$ ls -lhR /Library/Extensions/DisableLibraryValidation.kext
total 0
drwxr-xr-x 4 root wheel 128B Jun 2 12:21 Contents
/Library/Extensions/DisableLibraryValidation.kext/Contents:
total 8
-rwxr-xr-x 1 root wheel 2.1K Jun 2 12:21 Info.plist
drwxr-xr-x 3 root wheel 96B Jun 2 12:21 MacOS
/Library/Extensions/DisableLibraryValidation.kext/Contents/MacOS:
total 72
-rwxr-xr-x 1 root wheel 34K Jun 2 12:21 DisableLibraryValidation
Mac-Pro:~ ludacrisvp$ codesign -vv /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver: valid on disk
/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver: satisfies its Designated Requirement
Mac-Pro:~ ludacrisvp$ codesign -dv /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
Executable=/System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver
Identifier=com.apple.AMDMTLBronzeDriver
Format=bundle with Mach-O thin (x86_64)
CodeDirectory v=20100 size=13837 flags=0x2(adhoc) hashes=427+3 location=embedded
Signature=adhoc
Info.plist entries=11
TeamIdentifier=not set
Sealed Resources version=2 rules=13 files=5
Internal requirements count=0 size=12The nvram settings used in conjunction with Lilu / WEG are (you don't have to have the debug and verbose option as they are unrelated to this):
Code:
Mac-Pro:~ ludacrisvp$ nvram -p |grep boot-args
boot-args shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94 debug=0x144 -vYou should also see something like this from kextstat:
Code:
Mac-Pro:~ ludacrisvp$ kextstat|egrep 'AMD|mol'
115 2 0xffffff7f85f26000 0x201000 0x201000 com.apple.kext.AMDSupport (2.0.9) A212D4A1-95AA-3284-B9BF-DECE3D72EC8D <114 113 13 12 8 6 5 3 1>
125 0 0xffffff7f862a8000 0xfa000 0xfa000 com.apple.kext.AMD9500Controller (2.0.9) 0B192707-0B2A-327A-BE03-3B4AD0A64C74 <115 114 113 13 12 6 5 3 1>
155 0 0xffffff7f80d18000 0x2000 0x2000 com.apple.kext.mologie.DisableLibraryValidation (1) 1515FCCE-A78D-3677-B74E-C7F0E340A4D7 <7 5 3>
161 0 0xffffff7f86905000 0x11000 0x11000 com.apple.kext.AMDRadeonX4000HWServices (2.0.9) 15ED0BAB-A035-37E0-A350-A6F22E42259C <113 13 12 8 6 5 3 1>
163 0 0xffffff7f869ba000 0x537000 0x537000 com.apple.kext.AMDRadeonX4000 (2.0.9) 6AD64509-77E3-32EB-8800-FCB397DC7DA0 <162 145 113 13 8 6 5 3 1>
164 0 0xffffff7f86ef1000 0x11c3000 0x11c3000 com.apple.kext.AMDRadeonX4000HWLibs (1.0) C30FFC7A-BCAA-3691-8811-4A56BE45B09D <13 6 5 3 1>
165 0 0xffffff7f880b4000 0x3c000 0x3c000 com.apple.kext.AMDFramebuffer (2.0.9) AFECA5EC-3965-39FA-9FA6-2D51C7D22F6E <115 113 13 12 8 6 5 3 1>Are you on 10.14.5?So, no Lilu/WhateverGreen; you used Netkas' patched driver and the DisableLibraryValidation kext, and that was it? That setup doesn't work on my system, for some reason...
Sounds like not if you say you have sse4.2 in opengl driver.
Removing x4000.kext helped because it tells system what metal driver to use and if its not found/loaded windowserver crashes with assert.
Strange enough for me it works without disablelibval.kext after ldid (one can install ot via brew)
That library validation is a btch
Last edited:
Oh. thanks a lot for tip. I thought it is my problem so did not bothered with updating to 10.14.5. I guess I skipped v 3. I saw now I can update directly and just repatch system. I will try. I tried HS on external drive. Have not much time to play with but have not seem issue there yet.
I have A1260 model. 2.4 GHz Core2duo, 4 GB RAM, SSD HDD I guess in APFS and Geforce 8600M GT graphic 256 MB RAM.
[doublepost=1560763895][/doublepost]Hello,
Is there anyone running Mojave on Macbook Air late 2010, 1.86 GHz Core2duo/2 GB RAM. I have not updated it beyond El Capitan or so because hear that Sierra slowed it down very much. Can anyone say it is workable? Thanks.
My old Macbook Air 2011 is slow at startup but still holds up. Sad to see support dropped. Perhaps I should sideload macOS Mojave on it. Catalina didn’t bring that much to the table for me.
I have experiencing some interesting issues. I am currently running OSX14.3 on my MBP5,5 (mid 2009)
2 things:
1)So the APFS drive selector crashes every time I try to open it in system settings.
2) I am trying to do a system update to OSX14.5 but I get a boot loop every time.
I have tried to create a install drive with DOSDUDE1 1.3.3 patcher with OSX14.5 The drive isn't recognized in drive management. It shows up as a drive but does even show up as boot option in the startup drive in system settings.
Any suggestions?
2 things:
1)So the APFS drive selector crashes every time I try to open it in system settings.
2) I am trying to do a system update to OSX14.5 but I get a boot loop every time.
I have tried to create a install drive with DOSDUDE1 1.3.3 patcher with OSX14.5 The drive isn't recognized in drive management. It shows up as a drive but does even show up as boot option in the startup drive in system settings.
Any suggestions?
I'm now running Mojave 10.14.5 (APFS) on my Dell Latitude E6410 (I7-620m, NVidia 3100m, 8GB RAM, 512GB SSD) (defined as MacBookPro 6,2 in CLOVER config.plist). Laptop performance is OUTSTANDING! The only issue I still need to resolve is sleep (which seems to be a common problem for the Latitude E6410 Hackintosh). Once again, I am amazed at the incredible work done by the DosDude team to extend the life of older hardware. Great job!!!
Last edited:
I suggest upgrading to 6GB RAM for more speed since it's cheap and easy. My almost identical spec 17" MacBookPro4,1 A1261 model 2.6 GHz Core2Duo, 6 GB RAM, SSD HDD in APFS and Geforce 8600M GT graphic 512 MB RAM has been running Mojave 10.14.3 and 10.14.5 GREAT using the then current DosDude1's macOS Mojave Patcher.
Thanks for info. Not sure I can upgrade A1260 to 6 GB of RAM. But I am mostly OK with performance. No speed demon but ok whether stalls will disapear as it seems happened. I already updated to latest version. so be happy.
Just be willing to hear experience of someone with MBA 2010.
Apple specs state my A1261 and your A1260 max RAM is 4GB... but EveryMac.com and Other World Computing both show 6GB for my A1261 and your A1260. Increasing RAM will reduce your RAM <-> SSD swaps a LOT. It did on my almost identical A1261.
https://everymac.com/search/search.html?cx=partner-pub-8015755554271706%3A2hojc0-6s67&cof=FORID%3A11&ie=ISO-8859-1&q=A1260&sa=Search&siteurl=www.everymac.com%2F&ref=&ss=1j1j2
Maximum RAM: 6 GB*
*Apple officially supports a maximum of 4 GB of RAM but third-parties have been able to upgrade the system to 6 GB of RAM using one 2 GB and one 4 GB memory module.
My 17" Early 2008 MacBookPro4,1 has had 6GB RAM for years. Works great!
Last edited:
Im in the same problem, have you been able to resolve the issue ? or any help ? thanks in advanced
hheh
After pram reset and disabling csr again, I have hit the issue of white screen and no crash logs.
OK. Thanks for tip. But I may not do that as 50-100 USD is not reasonable cost for me. And it is 800 MHz. And I can not find cheaper/used ones here as well.
[doublepost=1560859295][/doublepost]
Thanks a lot. It seems it is right solution. You made ma day!