Photos does not seem to crash for me with regular photos at least. I don't have iPhone XS unfortunately.
Edit: I just realised that I am running 10.14.6 Beta 1, so my testing might not be very helpful in this particular case.
Last edited:
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
Photos does not seem to crash for me with regular photos at least. I don't have iPhone XS unfortunately.
Edit: I just realised that I am running 10.14.6 Beta 1, so my testing might not be very helpful in this particular case.
In this way
You can directly open the Mojave "Software Update" then parallel opening a Terminal window and type that, immediately the T2 message should disappear and if you're enrolled in public beta you should get immediately a prompt to download 10.14.6 beta 1
edit:
I am not really sure if that string "MacBook Pro Supplemental Update" should work for any language locale. Maybe they could need the string in their main language.
Photos crashes in my case when trying to edit any photo taken in "live" mode with an iPhone, and imported to Photos.
This always happens, and I didn't see Photos crash on any other occasion.
As I don't use "live" photos intentionally, I don't remember since which macOS version it happens, and also I don't really care.
Crash report attached.
(MBP5,2 17" 2.8GHz mid 2009, 8GB, APFS ROM patch applied, Samsung SSD 860 EVO with APFS. macOS 10.14.5 installed with dosdude's patcher 1.3.2. iPhone SE IOS 12(.3.1))
Last edited:
Join me on the quest for macOS 10.15 on unsupported Macs on this thread. Enjoy WWDC 2019 everyone.
Edit: It's happening.
Edit: It's happening.
Last edited:
I ran both the primary and extended tests but I can't find what the codes mean as they do not correspond to what Apple published.
Simple test code: 4SNS/1/40000000: TB3T-128.000
Extended test code: 4MEM/9/40000000: 0xaa316b18
From here : https://www.cnet.com/news/how-to-invoke-and-interpret-the-apple-hardware-tests/
The error codes
If the tests determine there is an error with your system, they will display an error code similar to the following:
4SNS/1/1/4000000 TL0P-130
The codes may be a bit cryptic, but you can contact Apple Support to see what they mean. As a general reference, here are some of the breakdowns for what the error codes mean, so if you see an error that begins with one of these codes, then it means the specified component listed at the end of the code is not working properly:
4ETH: Ethernet controller
4IRP: Main Logic board
4MLB: Logic board controller
4PRC: Processor
4HDD: Hard disk
4MHD: External disk
4YDC: Video card
4SNS: System sensor
4MOT: Fan motor
4MEM: Memory module
4AIR: AirPort wireless card
In the case of a sensor error (4SNS), to determine what type of sensor is being referenced, check its first letter, which should either be "I" for current, "T" for temperature, or "V" for voltage. Then check the second letter against the following list to see what component it refers to:
A: Ambient air sensor
B: Battery
C: Central processors (CPU)
D: DC (direct current)
e: PCI-express slot
F: FireWire port
G: Graphics processor (GPU)
H: Hard disk
h: Heat pipe (heat sink)
L: LCD display
M: Memory or memory riser boards
m: Misc. (i.e., battery chargers)
N: North bridge (motherboard controller)
O: Optical drives
P: Power bus
p: Power supply
s: Palm rests for laptops
W: Airport Wi-Fi card
In the example mentioned above, a sensor called "TL0P-130" is not working properly, which is an LCD temperature sensor in a portable system.
What to do
When it comes to addressing the error code situation, unfortunately many times there's not much that you can do. In most cases if a hardware component is not working then you will need to get it replaced; however, there are some instances where you can try another step or two before having your system serviced.
If you get an error that deals with an Ethernet controller, the main logic board, a logic board controller, processors, or sensors, then try rebooting the system and resetting the system PRAM to see if the problem clears. If you are getting a problem with the fan speeds or any sensors then you can also try resetting the system management controller, but in addition to these resets do check the fans for physical obstructions (dust and dirt) or for mechanical issues.
If you see a memory or AirPort card error code, then your best bet would be to first try resetting them in their connections on the motherboard, but ultimately replace them if you cannot get the errors to go away on subsequent tests. If you are unable to perform these tasks yourself, then you should be able to have it done at an Apple Store.
Hey dosdude, consider including this http://netkas.org/?p=1484 into your patcher, for 10.14.5 only and mp3,1 only
Definitely will. Thanks so much for your work!
I had the first error a while ago, #14910 on pg597. Temperature sensor of a non-original battery. Didn‘t do any harm.
Your 2nd error could though.
This is excellent work @natkas! Maybe someone could now patch the AMD Radeon HD 6xxx and AMD Radeon HD 5xxx so MBPs 2011 15-inch and 17-inch and iMacs 2010 and 2011 could work under macOS Mojave with Full Graphics Acceleration? I think there is some hope for these Macs. I really hope so.
That would make sense as I replaced the battery a year or so ago. Thanks!
[doublepost=1559634738][/doublepost]
Very helpful, thanks!
I did replace the battery about a year ago, so one of the errors makes sense. My fans are definitely working alright as the systems checks during the preliminary install triggers them.
Does anyone know what the steps for installation of the OS or if there is a manual process?
Bom dia Alex, I've read about this and I'm really amazed.
As a 3,1 owner, I've bought a GTX680 as the only card available to having a 3,1 with Mojave. It works, yes, but unfortunately the performance in Final Cut (what I do) is really worse than with my old 5770 in El Capitan. This is unbelievable due the ATI it had only 1gb and this GTX 2gb...
I'm still trying to get all the power from this card. Do you think this patch it would work on my GTX? Any way to get that my 3,1 runs faster video editing? Would this open a new way for cases like mine?
Thank you
I hope that is possible. At the end, I have circunvent the Radeon and leave only the intel, so I can run Mojave (and maybe Catalina) without problem in my Macbook Pro 17
Hi upipes, I am also following this development and I am considering getting an AMD580 to test it out. The patch is presently only for 14.5 and will only help if you have a metal AMD card. It will make no difference to the GTX680 as the fix is to the AMD metal driver so it can use SSE4.1 as far as I understand. These AMD cards may suit FCP better but there may be other restrictions in our old machines. Also with 10.15 now on the horizon It may be worth waiting to see what happens. The other downside is that there are no Mac efi AMD560/580 cards so no boot screen. However this may change with the new mp now due.
So I just installed Mojave on a MBP 6,2 (mid 2010 with Nvidia Geforce 320M maxed out RAM and SSD) and I am getting pretty bad Quicktime performance when playing back 1080p files that played butter smooth under HighSierra. I see that others have had Quicktime Issues but not with my exact model. Anyone have any solutions to improve quicktime performance?