I have had problems using the OSMC installer on my Mac (OS Catalina 10.15.3) to install onto an SD card (32gb C10). The installer kept coming up with the error. I tried 3 x class 10 32gb sd cards.
Fri Jan 31 15:46:23 2020 Imaging failed!
Fri Jan 31 15:46:23 2020 Messages are:
Fri Jan 31 15:46:23 2020 stdout:
Fri Jan 31 15:46:23 2020 stderr: 0:133: execution error: dd: /dev/disk3s1: Operation not permitted (1)
I tried to install via Terminal instead:
sudo dd if=/Users/home/downloads/OSMC_TGT_rbp2_20200607.img of=/dev/disk3s1
and got this error:
dd: /dev/disk3s1: Operation not permitted
The card is not locked. It is brand new and I can read and write to it.
Does anyone have a clue what I do next?
Make sure that the SD is not mounted
Tried that and it still doesn’t work. Operation not permitted. The SD card is not locked, and I have not reformatted it since I bought it.
I cannot reproduce this on Catalina using Terminal.
The installer does not work on Catalina but this is a known issue. dd is however working well.
I’ve not asked if the SD is mounted but if it’s mounted. You probably need to run umount on the SD.
You could also try dd’ing to the ‘rdisk’
It worked! I had to unmount using Disk Utility. Cheers Sam.
I’m running macOS Catalina 10.15.6.
I downloaded the installer from the download page and I had a similar error on
Fri Oct 23 20:57:30 2020 going to start osa
Fri Oct 23 20:57:30 2020 pasting admin script to process do shell script "dd if=/Users/waa/OSMC_TGT_rbp2_20201019.img of=/dev/rdisk6 bs=1m conv=sync && sync" with administrator privileges
Fri Oct 23 20:57:30 2020 waiting for finish
Fri Oct 23 20:57:30 2020 osa claims to be done...collect output and verify
Fri Oct 23 20:57:30 2020 Imaging failed!
Fri Oct 23 20:57:30 2020 Messages are:
Fri Oct 23 20:57:30 2020 stdout:
Fri Oct 23 20:57:30 2020 stderr: 0:130: execution error: dd: /dev/rdisk6: Operation not permitted (1)
For me, it only worked after I did this:
- Disable SIP: How to turn off System Integrity Protection on your Mac | iMore
- Run the installer from the terminal with
Unfortunately I think we need to sign our macOS builds now to resolve this issue.
I’m looking in to what’s involved in doing this.