MDS 1.2 imagr Error


MDS 1.2 seems to have an imgr issue. The creation process completes without any errors but when I boot to the bootable volume and run MDS. The imagr fails to open.


Sometimes recovery partitions do not get updated. When you are in recovery, open Terminal and run:


and see what it returns. If it is <10.10, you’ll have issues even if Imagr worked.

The solution is to make the external drive bootable and run imagr from the externally booted drive. This will update the recovery partition so it should resolve the issue for next time.



Just received my Bundle (Arduino), and it runs and then this happens:

Starting up. Please be patient…
DNS lookup to good, so inferring we have internet.
Traceback (most recent call last):
File “”, line 19, in
import MainController
File “/Volumes/mds/Deploy/Applications/”, line 17, in
from Quartz.CoreGraphics import *
File “/Volumes/MDS/Deploy/Applications/”, line 112, in
File “/Volumes/MDS/Deploy/Applications/”, line 57, in _load
import Quartz.CoreGraphics._coregraphics as m
ImportError: dlopen(/Volumes/MDS/Deploy/Applications/, 2): Library not loaded: /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
Referenced from: /Volumes/MDS/Deploy/Applications/
Reason: image not found
2019-03-07 16:34:46.752 Imagr[321:707] *** Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘/Users/tperfitt/Documents/Projects/imagr-python/imagr/Imagr/main.m:40 main() PyRun_SimpleFile failed with file ‘/Volumes/mds/Deploy/Applications/’. See console for errors.’
*** First throw call stack:
0 CoreFoundation 0x000000010e395b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x000000010ceab3f0 objc_exception_throw + 43
2 CoreFoundation 0x000000010e3958dc +[NSException raise:format:] + 204
3 Imagr 0x000000010c6ed0d2 main + 1682
4 libdyld.dylib 0x000000011099f7e1 start + 0
5 ??? 0x0000000000000001 0x0 + 1
libc++abi.dylib: terminate called throwing an exception
/Volumes/mds/run: line 41: 321 Abort trap: 6 “${dir}/Deploy/Applications/”


Can you run sw_vers and check the version number of the recovery partition? It is probably very old (like 10.7). Just boot in to internet recovery (command-shift-R) and it should boot into a newer version of recovery that will work.



Just did and it was 10.8.5 - So then the solution is to run a full internet restore to update the recovery partition, or is there a simpler way?


OK, I booted into recovery with Command + Option + R and I see it is a different version, plugged in the stick and the Arduino, will let you know…