Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Tnx guys, I installed Mojave on my MBA 3,2. So fa it's looking great, still have to test things.
One question about Hardware Encoding. Is t possible to enable it somehow? I think because of that I have issues with
Screenshot app when taking videos. They don't play as they should.

View attachment 772390
Well since that is the same GPU as other supported machines, I'm not sure what the problem is. Hardware acceleration should depend on the GPU, not the CPU.
[doublepost=1532407030][/doublepost]
You need to cover up the serial number
That's interesting because I have found you don't. I mean it is good practice, but people can't take you machine just because they know the serial number. I had a brand new iMac stolen from work a few years ago, and I called Apple to see if they could flag it in case anyone tried to get it repaired. They could not.
 
You need to cover up the serial number

You quoted their serial number as well.
[doublepost=1532410276][/doublepost]
Well since that is the same GPU as other supported machines, I'm not sure what the problem is. Hardware acceleration should depend on the GPU, not the CPU.
[doublepost=1532407030][/doublepost]
That's interesting because I have found you don't. I mean it is good practice, but people can't take you machine just because they know the serial number. I had a brand new iMac stolen from work a few years ago, and I called Apple to see if they could flag it in case anyone tried to get it repaired. They could not.

Actually... I could assign that serial number to a Hackintosh system. Which might present you with some problems if I activate certain features with your serial number. It would be a little inconvenient.
 
  • Like
Reactions: TimothyR734
Well since that is the same GPU as other supported machines, I'm not sure what the problem is. Hardware acceleration should depend on the GPU, not the CPU.
[doublepost=1532407030][/doublepost]
That's interesting because I have found you don't. I mean it is good practice, but people can't take you machine just because they know the serial number. I had a brand new iMac stolen from work a few years ago, and I called Apple to see if they could flag it in case anyone tried to get it repaired. They could not.

If Apple during any MacOS online activities logs records also the OrderNumber/SKU and LogicBoardSerialNumber as well explained by tsialex on page 148, then I am agree with you.

In case of fraud/crime/illegal use of your machine serial number, you could always prove that original factory SKU and LBSN still belong to you. This is a bit complicated anyway.

edit:
Maybe Apple during online activities could record also some SMC ids, or any Hardware ids, in this way only with a serial number the risks are very mitigated.
Don't forget that record of some hardware ids are soon noticeable when using Internet Recovery Mode, so outside from a MacOS completely booted system.

In conclusion it is more risky a lost standard user password (or an email account password) than a serial machine number. To not speak about a lost/stolen root Administrator password, in that case there are serious trouble.
 
Last edited:
  • Like
Reactions: TimothyR734
You need to cover up the serial number
if you don't mind me asking, what's the importance of covering up the serial number?
[doublepost=1532421321][/doublepost]
if you don't mind me asking, what's the importance of covering up the serial number?
a bit late in posting as question already answered. please ignore former post
 
Sorry to be off-topic (again) but to anyone experts those have a raspberry PI, or EEPROM programmer, or a SOIC8 SOP8 Clip tool, or any USB EEPROM programmer, please take a look to the EFI CHIP type picture I have attached.

I will erroneous call the first line one the EFI CHIP "with metal paws", while the second line one "without metal paws"

My two questions are, since on my bricked MacbookAir2,1 I have the printed EFI CHIP "without metal paws":

1) Will a Clip tool work without desoldering the CHIP or it's too thin to Clip it?
2) If I buy an EFI CHIP "with metal paws" can I weld it on a logic board that instead has an embedded EFI CHIP "without metal paws"?

Thanks to those who will answer.

Hi,

I think the main problem is the soldering process. Picture one "with paws" is designed to get soldered with some kind of soldering process. The one without "paws" is designed to get soldered through a bath type of soldering, without direct contact to some kind of solder iron.

From a repair point of view, you need to check the overall height of version one. It might be possible, but even with a successful repair job, your cover will not fit, because the chip with paws is larger and has higher/thicker dimensions.
In theory you can clip those paws, but then you will have a problem of de-placed solder points. It might only work if the clipped paws are exactly positioned to the old print. Since a clipping of paws will leave a stressed and deformed contact, you will need to grind it down instead of clipping.
However, even if you manage to have a correct positioned grinded down paw in place, the soldering will be another challenge. You need to know exactly how much heat and power is enough or needed for not doing a smelting grill session to ruin the whole thing. Do you have the right high precision tools available?

You may want to give that job to a GPU/CPU resoldering contractor, that has the right tools and solder bath to do it.
My Nvidia m330 gpu chip was destroyed through years of hard sweatlodge gaming on my MBP 2010, so a contractor put a new one in for about 180 bucks two years ago. Works like a charm. I would most likely use a service like that in your shoes.
 
Hi,

I think the main problem is the soldering process. Picture one "with paws" is designed to get soldered with some kind of soldering process. The one without "paws" is designed to get soldered through a bath type of soldering, without direct contact to some kind of solder iron.

From a repair point of view, you need to check the overall height of version one. It might be possible, but even with a successful repair job, your cover will not fit, because the chip with paws is larger and has higher/thicker dimensions.
In theory you can clip those paws, but then you will have a problem of de-placed solder points. It might only work if the clipped paws are exactly positioned to the old print. Since a clipping of paws will leave a stressed and deformed contact, you will need to grind it down instead of clipping.
However, even if you manage to have a correct positioned grinded down paw in place, the soldering will be another challenge. You need to know exactly how much heat and power is enough or needed for not doing a smelting grill session to ruin the whole thing. Do you have the right high precision tools available?

You may want to give that job to a GPU/CPU resoldering contractor, that has the right tools and solder bath to do it.
My Nvidia m330 gpu chip was destroyed through years of hard sweatlodge gaming on my MBP 2010, so a contractor put a new one in for about 180 bucks two years ago. Works like a charm. I would most likely use a service like that in your shoes.

I've observed that starting from 2009 all the MBAirs and MBP Retina (the thinner and lighter design line) have that kind of "without paws" EFI EEPROM CHIP (technically QFN CHIP type as dosdude1 explained me).
Anyway as stated many times I don't really care about it, but fixing is just a challenge for me, after done I can put it again in a box for others years.

edit:

There is still a chance for a very easy reprogramming my bricked EFI EEPROM, since my MBA2,1 logic board has that spare "Molex HRS HiRose" I/O connector, but can't find a right cheap adapter to fit it externally so I could do it easily from a Windows 7/Linux PC, I think it's an Apple Service proprietary port. There are some in the web markets but they are too expensive, I don't want to throw more than 50 $ to fix it.
 
Last edited:
  • Like
Reactions: TimothyR734
I gave this a couple shots and it failed both times. Does the error log contain anything I shouldn’t share? Would it be ok to share here for advice? I’m using a late 2011 15” MBP
 
  • Like
Reactions: TimothyR734
I just installed 10.14 beta 4 on a 27" core i7 2009 iMac with an AMD HD4850 using an external SSD for the time being. The install went perfectly and the GPU seems fully accelerated. It does crash when accessing Apple Store. Here is the first part of the crash log;

Process: App Store [576]
Path: /Applications/App Store.app/Contents/MacOS/App Store
Identifier: com.apple.AppStore
Version: 3.0 (1)
Build Info: AppStoreJet-3000079000000~11
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: App Store [576]
User ID: 501

Date/Time: 2018-07-24 19:41:53.710 +0900
OS Version: Mac OS X 10.14 (18A336e)
Report Version: 12
Anonymous UUID: Removed from Apple prying eyes


Time Awake Since Boot: 1400 seconds

System Integrity Protection: disabled

Crashed Thread: 10 Dispatch queue: com.apple.CoreAUC.monitorQueue

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [576]

VM Regions Near 0:
-->
__TEXT 000000010954b000-000000010987f000 [ 3280K] r-x/rwx SM=COW /Applications/App Store.app/Contents/MacOS/App Store

Application Specific Information:
dyld3 mode

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6b06da86 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6b06cf8c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3de4da54 __CFRunLoopServiceMachPort + 336
3 com.apple.CoreFoundation 0x00007fff3de4cef1 __CFRunLoopRun + 1661
4 com.apple.CoreFoundation 0x00007fff3de4c65c CFRunLoopRunSpecific + 467
5 com.apple.HIToolbox 0x00007fff3d0d6829 RunCurrentEventLoopInMode + 293
6 com.apple.HIToolbox 0x00007fff3d0d6556 ReceiveNextEventCommon + 618
7 com.apple.HIToolbox 0x00007fff3d0d62d3 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff3b391643 _DPSNextEvent + 997
9 com.apple.AppKit 0x00007fff3badf0a2 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
10 com.apple.AppKit 0x00007fff3b386eca -[NSApplication run] + 699
11 com.apple.AppKit 0x00007fff3b356ec3 NSApplicationMain + 782
12 com.apple.AppStore 0x0000000109550969 0x10954b000 + 22889
13 libdyld.dylib 0x00007fff6af0ded4 0x7fff6af0d000 + 3796

Thread 1:
0 libsystem_pthread.dylib 0x00007fff6b11328c start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 2:
0 libsystem_pthread.dylib 0x00007fff6b11328c start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 3:
0 com.apple.framework.IOKit 0x00007fff40937857 IOCFUnserializeBinary + 1040
1 com.apple.framework.IOKit 0x00007fff4093ac28 IORegistryEntryCreateCFProperties + 85
2 com.apple.framework.IOKit 0x00007fff40950b74 IOAccelFindAccelerator + 80
3 com.apple.CoreAUC 0x00007fff5193e7a7 0x7fff5193c000 + 10151
4 com.apple.CoreAUC 0x00007fff5193d182 0x7fff5193c000 + 4482
5 com.apple.CoreAUC 0x00007fff5193d08a Gnf6vZyAVLNQta0BwK + 413
6 com.apple.MediaToolbox 0x00007fff428c07f0 0x7fff4243b000 + 4741104
7 libdispatch.dylib 0x00007fff6aed5961 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff6aee176e _dispatch_lane_barrier_sync_invoke_and_complete + 60
9 com.apple.MediaToolbox 0x00007fff428c0636 0x7fff4243b000 + 4740662
10 com.apple.MediaToolbox 0x00007fff42af8b34 0x7fff4243b000 + 7068468
11 com.apple.MediaToolbox 0x00007fff42543fac FigPlayerStreamCreate + 1864
12 com.apple.MediaToolbox 0x00007fff42a3ac4f 0x7fff4243b000 + 6290511
13 libdispatch.dylib 0x00007fff6aed5961 _dispatch_client_callout + 8
14 libdispatch.dylib 0x00007fff6aee176e _dispatch_lane_barrier_sync_invoke_and_complete + 60
15 com.apple.MediaToolbox 0x00007fff42a3cda0 0x7fff4243b000 + 6299040
16 com.apple.MediaToolbox 0x00007fff42a40347 0x7fff4243b000 + 6312775
17 com.apple.MediaToolbox 0x00007fff42a3fe7a 0x7fff4243b000 + 6311546
18 com.apple.MediaToolbox 0x00007fff427abeaf 0x7fff4243b000 + 3608239
19 com.apple.MediaToolbox 0x00007fff427217d8 0x7fff4243b000 + 3041240
20 com.apple.MediaToolbox 0x00007fff425dbdf6 0x7fff4243b000 + 1707510
21 com.apple.MediaToolbox 0x00007fff425db065 0x7fff4243b000 + 1704037
22 com.apple.MediaToolbox 0x00007fff425e00b3 0x7fff4243b000 + 1724595
23 com.apple.avfoundation 0x00007f
 
I just installed 10.14 beta 4 on a 27" core i7 2009 iMac with an AMD HD4850 using an external SSD for the time being. The install went perfectly and the GPU seems fully accelerated. It does crash when accessing Apple Store. Here is the first part of the crash log;

Process: App Store [576]
Path: /Applications/App Store.app/Contents/MacOS/App Store
Identifier: com.apple.AppStore
Version: 3.0 (1)
Build Info: AppStoreJet-3000079000000~11
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: App Store [576]
User ID: 501

Date/Time: 2018-07-24 19:41:53.710 +0900
OS Version: Mac OS X 10.14 (18A336e)
Report Version: 12
Anonymous UUID: Removed from Apple prying eyes


Time Awake Since Boot: 1400 seconds

System Integrity Protection: disabled

Crashed Thread: 10 Dispatch queue: com.apple.CoreAUC.monitorQueue

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [576]

VM Regions Near 0:
-->
__TEXT 000000010954b000-000000010987f000 [ 3280K] r-x/rwx SM=COW /Applications/App Store.app/Contents/MacOS/App Store

Application Specific Information:
dyld3 mode

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6b06da86 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6b06cf8c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3de4da54 __CFRunLoopServiceMachPort + 336
3 com.apple.CoreFoundation 0x00007fff3de4cef1 __CFRunLoopRun + 1661
4 com.apple.CoreFoundation 0x00007fff3de4c65c CFRunLoopRunSpecific + 467
5 com.apple.HIToolbox 0x00007fff3d0d6829 RunCurrentEventLoopInMode + 293
6 com.apple.HIToolbox 0x00007fff3d0d6556 ReceiveNextEventCommon + 618
7 com.apple.HIToolbox 0x00007fff3d0d62d3 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff3b391643 _DPSNextEvent + 997
9 com.apple.AppKit 0x00007fff3badf0a2 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
10 com.apple.AppKit 0x00007fff3b386eca -[NSApplication run] + 699
11 com.apple.AppKit 0x00007fff3b356ec3 NSApplicationMain + 782
12 com.apple.AppStore 0x0000000109550969 0x10954b000 + 22889
13 libdyld.dylib 0x00007fff6af0ded4 0x7fff6af0d000 + 3796

Thread 1:
0 libsystem_pthread.dylib 0x00007fff6b11328c start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 2:
0 libsystem_pthread.dylib 0x00007fff6b11328c start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 3:
0 com.apple.framework.IOKit 0x00007fff40937857 IOCFUnserializeBinary + 1040
1 com.apple.framework.IOKit 0x00007fff4093ac28 IORegistryEntryCreateCFProperties + 85
2 com.apple.framework.IOKit 0x00007fff40950b74 IOAccelFindAccelerator + 80
3 com.apple.CoreAUC 0x00007fff5193e7a7 0x7fff5193c000 + 10151
4 com.apple.CoreAUC 0x00007fff5193d182 0x7fff5193c000 + 4482
5 com.apple.CoreAUC 0x00007fff5193d08a Gnf6vZyAVLNQta0BwK + 413
6 com.apple.MediaToolbox 0x00007fff428c07f0 0x7fff4243b000 + 4741104
7 libdispatch.dylib 0x00007fff6aed5961 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff6aee176e _dispatch_lane_barrier_sync_invoke_and_complete + 60
9 com.apple.MediaToolbox 0x00007fff428c0636 0x7fff4243b000 + 4740662
10 com.apple.MediaToolbox 0x00007fff42af8b34 0x7fff4243b000 + 7068468
11 com.apple.MediaToolbox 0x00007fff42543fac FigPlayerStreamCreate + 1864
12 com.apple.MediaToolbox 0x00007fff42a3ac4f 0x7fff4243b000 + 6290511
13 libdispatch.dylib 0x00007fff6aed5961 _dispatch_client_callout + 8
14 libdispatch.dylib 0x00007fff6aee176e _dispatch_lane_barrier_sync_invoke_and_complete + 60
15 com.apple.MediaToolbox 0x00007fff42a3cda0 0x7fff4243b000 + 6299040
16 com.apple.MediaToolbox 0x00007fff42a40347 0x7fff4243b000 + 6312775
17 com.apple.MediaToolbox 0x00007fff42a3fe7a 0x7fff4243b000 + 6311546
18 com.apple.MediaToolbox 0x00007fff427abeaf 0x7fff4243b000 + 3608239
19 com.apple.MediaToolbox 0x00007fff427217d8 0x7fff4243b000 + 3041240
20 com.apple.MediaToolbox 0x00007fff425dbdf6 0x7fff4243b000 + 1707510
21 com.apple.MediaToolbox 0x00007fff425db065 0x7fff4243b000 + 1704037
22 com.apple.MediaToolbox 0x00007fff425e00b3 0x7fff4243b000 + 1724595
23 com.apple.avfoundation 0x00007f

Try replacing System/Library/PrivateFrameworks/CoreAUC.framework with the same file from High Sierra.
 
  • Like
Reactions: TimothyR734
Facetime is working :D

MBP 13' Mid 2010
 

Attachments

  • fullsizeoutput_2.jpeg
    fullsizeoutput_2.jpeg
    237.4 KB · Views: 226
  • Like
Reactions: TimothyR734
I've observed that starting from 2009 all the MBAirs and MBP Retina (the thinner and lighter design line) have that kind of "without paws" EFI EEPROM CHIP (technically QFN CHIP type as dosdude1 explained me).
Anyway as stated many times I don't really care about it, but fixing is just a challenge for me, after done I can put it again in a box for others years.

edit:

There is still a chance for a very easy reprogramming my bricked EFI EEPROM, since my MBA2,1 logic board has that spare "Molex HRS HiRose" I/O connector, but can't find a right cheap adapter to fit it externally so I could do it easily from a Windows 7/Linux PC, I think it's an Apple Service proprietary port. There are some in the web markets but they are too expensive, I don't want to throw more than 50 $ to fix it.
Did you check this: https://ghostlyhaks.com/blog/blog/hacking/18-apple-efi-bypass It says " If you have a MBA then you can contact me about purchasing a clip for the header." maybe the price is not to high
 
Did you check this: https://ghostlyhaks.com/blog/blog/hacking/18-apple-efi-bypass It says " If you have a MBA then you can contact me about purchasing a clip for the header." maybe the price is not to high

Of course, but I missed that message. Just noticing again, how much important is to have a Windows PC to interfacing with these tools, I see in his video he's using Raspberry from putty in Windows 10. Windows libraries are needful in several fields, for ex. also in console triple-A games development.
 
  • Like
Reactions: TimothyR734
Of course, but I missed that message. Just noticing again, how much important is to have a Windows PC to interfacing with these tools, I see in his video he's using Raspberry from putty in Windows 10. Windows libraries are needful in several fields, for ex. also in console triple-A games development.
Putty is just a Windows alternative for SSH, because it doesn't exist natively. You can SSH into a RasPi just using Terminal in OS X or Linux, without installing any extra software. Just use the "ssh" command.
[doublepost=1532442853][/doublepost]
Try replacing System/Library/PrivateFrameworks/CoreAUC.framework with the same file from High Sierra.
Please don't add untested solutions to the OP. If you've tested yourself and verified it works, feel free, but I do not want users replacing system files unnecessarily and potentially causing issues with their OS install.
 
Putty is just a Windows alternative for SSH, because it doesn't exist natively. You can SSH into a RasPi just using Terminal in OS X or Linux, without installing any extra software. Just use the "ssh" command.

I know, I was just praising Microsoft products.
[doublepost=1532443391][/doublepost]
Not necessary on these old MBAs, as they use a TSOP EEPROM which you can attach a clip to. As I've said before, though, I've never had much luck programming an EEPROM in circuit.

Please check.
 

Attachments

  • MBA21 logic board A1304.jpeg
    MBA21 logic board A1304.jpeg
    191.1 KB · Views: 208
  • A1304 EMC2334 EFI CHIP.jpeg
    A1304 EMC2334 EFI CHIP.jpeg
    418.8 KB · Views: 227
Last edited:
  • Like
Reactions: TimothyR734
Well, I have more important things to worry about.. I found out sometime last week medical results that I have been diagnosed with cancer of the stomach.. so, really by the time Mojave comes out I may not even be here.

Every now and then we get reminded that some things are more important than this little tinkering hobby. Best of luck to you sir and I hope that there is hope.
 
Please don't add untested solutions to the OP. If you've tested yourself and verified it works, feel free, but I do not want users replacing system files unnecessarily and potentially causing issues with their OS install.

I can’t test it. The App Store on my machine works.
 
  • Like
Reactions: TimothyR734
I know, I was just praising Microsoft products.
[doublepost=1532443391][/doublepost]

Please check.
Ok, yeah it looks like yours does have a QFN EEPROM. I still think the only real solution is to desolder it and program it externally, as I don't think it's worth it to buy any special equipment just for that board (it's the worse and most unreliable MacBook Air that I've ever dealt with). I'm not sure where you're located, but I could just send you another board if you wanted, as I have quite a few of them.
 
Ok, yeah it looks like yours does have a QFN EEPROM. I still think the only real solution is to desolder it and program it externally, as I don't think it's worth it to buy any special equipment just for that board (it's the worse and most unreliable MacBook Air that I've ever dealt with). I'm not sure where you're located, but I could just send you another board if you wanted, as I have quite a few of them.

I can assure it's so from factory, never replaced any logic board's component on it.
I am located in Europe, it's not necessary a replacement board, thank you anyway.

edit:
In retrospect, I could accept, but only if the one you ship has a TSOP EEPROM on it. (I am joking of course)
 
Last edited:
  • Like
Reactions: TimothyR734
OK, so I did something stupid and now I need some help out here. I have tried to run Continuity Activation Tool on my MBPro Mid 2009 but it didn't work (it got stuck rebooting). Then I did a new installation of macOS Mojave, and everything went just fine, but when I rebooted my laptop, it got stuck on loading screen. I don't know what's going on, and I had to install OS over to get here, and now I'm afraid to reboot again. Any suggestion? I could really use some help, and you guys can see attached the CAT uninstalling screen, if it helps. Thanks!
 

Attachments

  • Captura de Tela 2018-07-24 às 14.12.17.png
    Captura de Tela 2018-07-24 às 14.12.17.png
    89.4 KB · Views: 152
  • Like
Reactions: TimothyR734
OK, so I did something stupid and now I need some help out here. I have tried to run Continuity Activation Tool on my MBPro Mid 2009 but it didn't work (it got stuck rebooting). Then I did a new installation of macOS Mojave, and everything went just fine, but when I rebooted my laptop, it got stuck on loading screen. I don't know what's going on, and I had to install OS over to get here, and now I'm afraid to reboot again. Any suggestion? I could really use some help, and you guys can see attached the CAT uninstalling screen, if it helps. Thanks!

First of all why you have used it if it's incompatible with your Wifi/BT card?

It seems from the contitool.sh that the tool has failed on step 1, step 3 and step 8, maybe it has installed also in your main Sierra/HS partition, so you should need to replace them from their original BT/Wifi kext typically present in /System/Library/Extensions folder of a Recovery Partition.

But before attempting a manually replacing kext, try to boot from any Recovery HD, or from the USB Mojave Patcher Installer, go to Utilities/Terminal and type:
csrutil disable; reboot

then try again and see if the continuity patch will uninstall automatically this time.

For sure this tool created an invalid prelinkedkernel/kextcache, that's why you boot looping, so you should try also from Mojave USB Installer to "force rebuild cache" from Post Install.
 
Last edited:
  • Like
Reactions: TimothyR734
First of all why you have used it if it's incompatible with your Wifi/BT card?

It seems from the contitool.sh that the tool has failed on step 1, step 3 and step 8, maybe it has installed also in your main Sierra/HS partition, so you should need to replace them from their original BT/Wifi kext typically present in /System/Library/Extensions folder of a Recovery Partition.

But before attempting a manually replacing kext, try to boot from any Recovery HD, or from the USB Mojave Patcher Installer, go to Utilities/Terminal and type:
csrutil disable; reboot

then try again and see if the continuity patch will uninstall automatically this time.

I just checked, and csrutil is already disabled, so what do I do? Where do I get that kexts from?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.