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
In dubio pro reo.
As long as 0403979 does not respond, I´d like to try to open the Zip if you can send it or append it to your post. It might be the addition that enables the MB4,1 with the prelinked kernel that he added just recently.
Strange coding nonetheless...
Last edited by a moderator:
That's not true. That's merely the file downloaded to open the password protected zip, which contains another script that is then executed.
[doublepost=1553096662][/doublepost]
Thanks, gonna try that and report back. In the meantime - any idea why my SSD doesn't show up in boot selection menu after successfully installing and patching Mojave on my MacBook 6,1 (late 2009)?
Last edited by a moderator:
Sounds like you converted it to APFS, which is not out-of-the-box bootable. To accomplish this, you´d have to patch the boot ROM with the APFS ROM patcher tool from dosdude1.
Other reasons might include broken/damaged SSD flex cable, or negotiation problems between a SATA-3 SSD and a possibly slower SATA controller in your MacBook.
That seems to be it - fairly new to this. However APFS Patch greyed out in the Post Install Patcher; I'll try installing Mojave with Extended since I can probably patch it from a full OS, to then go back to installing Mojave with APFS. Thanks!
edit: I wish there was a ReadTheDocs somewhere and not just some cluttered forum posts (sorry but the search functionality ain't exactly good), as most of these problems seem to come up since High Sierra.
Last edited:
Apparently this script "as is" does nothing, unless there is another "121521.sh" previously copied somewhere, the "C121521.zip" does contain again the same file and the zip itself, just checked from Terminal without extraction:
zipinfo C121521.zip
And any "bit.ly" URL shortener inserted into a shell script does nothing too.
That said it's weird it was there, probably 0403979 copied it for mistake.
Last edited by a moderator:
True but it's conveniently at the end of the script. So another sub-script could easily read the main script as text, extract the very last line and download it. An open-source project handling a password protected zip file, which's content is then executed, is imo just sketchy. Aside from that I doubt it's a copying mistake as /link removed/.
Last edited by a moderator:
I have a MacBook6,1, with SSD and 8Gb RAM, and I successfully updated it from High Sierra to 10.14.3 thanks to the dosdude patcher. Thank you very much. Everything works as well as on High Sierra. The problem of artifacts of the light theme was safely solved by the transutil script.
Macbook 6.1 uses hardware video decoding through 9400m. This reduces the heating of the processor and unloads it by 2 times when watching FullHD movies. Some videos recorded with the iPhone began to occur jerks and friezes, which were not on the High Sierra. I was able to fix this problem by taking AppleGVA.framework from High Sierra (17G5019) and replacing it with a system one. And then updated the script cache. After the reboot, the jerks stopped. Everything now plays smoothly, as well as in High Sierra.
I wrote to share this decision, it may be useful to someone. For myself, I wrote a script to make the substitution of AppleGVA.framework quick and easy. The script is trusted on my macbook. It contains AppleGVA.framework from High Sierra. No need to search. There are even two scripts. The second script restores the state of the system before the patch. This is in case you don’t like the result. Sorry for my English. Thanks.
Macbook 6.1 uses hardware video decoding through 9400m. This reduces the heating of the processor and unloads it by 2 times when watching FullHD movies. Some videos recorded with the iPhone began to occur jerks and friezes, which were not on the High Sierra. I was able to fix this problem by taking AppleGVA.framework from High Sierra (17G5019) and replacing it with a system one. And then updated the script cache. After the reboot, the jerks stopped. Everything now plays smoothly, as well as in High Sierra.
I wrote to share this decision, it may be useful to someone. For myself, I wrote a script to make the substitution of AppleGVA.framework quick and easy. The script is trusted on my macbook. It contains AppleGVA.framework from High Sierra. No need to search. There are even two scripts. The second script restores the state of the system before the patch. This is in case you don’t like the result. Sorry for my English. Thanks.
The link and associated zip you have found is a password protected note. I thought it would be fun to include and see if anyone would find it and maybe even find the password and read the message. It's not malware. I have never and will never intentionally damage someone's device. Now that it's been found, I have removed it.
If want to learn something then read ahead. Bash scripts never accept an unaccompanied link. Any link like this or a message, especially if there are special characters in front of it, marking it as a comment, will not be ran as a command.
On another note, I never actually researched the strength of Apple zip encryption. I saw that someone was able to decrypt it. This is worrying to me and I won't use this encryption again.
There are two patcher because choice is important. My patcher is geared more to developers than to average users. I also offer experimental support for the MacBook4,1.
I hope this answers your questions. If you have questions or concerns about my work please contact me via this thread or via direct message.
[doublepost=1553101879][/doublepost]
To whom it concerns. @jackluke @Larsvonhier @Loyd-01a @icevolt
If want to learn something then read ahead. Bash scripts never accept an unaccompanied link. Any link like this or a message, especially if there are special characters in front of it, marking it as a comment, will not be ran as a command.
On another note, I never actually researched the strength of Apple zip encryption. I saw that someone was able to decrypt it. This is worrying to me and I won't use this encryption again.
There are two patcher because choice is important. My patcher is geared more to developers than to average users. I also offer experimental support for the MacBook4,1.
I hope this answers your questions. If you have questions or concerns about my work please contact me via this thread or via direct message.
[doublepost=1553101879][/doublepost]
To whom it concerns. @jackluke @Larsvonhier @Loyd-01a @icevolt
There is no "Apple ZIP encryption". They follow the ZIP "standard" and it is known that its a rather weak encryption. There are a lot of brute-force decryption tools for ZIP archives...
Last edited by a moderator:
I bruteforced it. Quite a managable task if it's only 3 digits.
Anyways, I can't seem to get APFS support to work on my MacBook 6,1 Late 2009. I tried both the dedicated APFS ROM Patcher (for which I also had to guess the password), which said System not compatible, and the Post Install Patcher that comes with the Mojave installer, on which the APFS patch field is greyed out.
However I just dm'd @gosvamih who confirmed that his MacBook 6,1 Late 2009 is indeed running with APFS support. Any ideas?
Last edited by a moderator:
I guess I won't be using zip encryption anymore. I don't have experience so I can't help with the apfs issue. Congratulations on finding the message.
APFS support is native on my MacBook 6,1 (unibody). I converted my SSD to APFS while on High Sierra, so a firmware upgrade may have been applied by Apple at that time.
Cheers
Hugh
Greyed out means:
a) already patched ROM or
b) still on HFS+ (so no patch can be applied by software)
This means you´ll have to convert your volume to APFS first, then use either patch (ROM or software)
btw: password APFS is given on page #1 (always a good hub for basic questions), so you don´t need to guess that one ;-)
Just pick a longer password and you should be fine.
APFS support is native on my MacBook 6,1 (unibody). I converted my SSD to APFS while on High Sierra, so a firmware upgrade may have been applied by Apple at that time.
Cheers
Hugh
I tried installing macOS Mojave on an APFS drive earlier today and it wouldn't appear in my boot menu. I simply got the blinking question mark folder if I left it to boot unattended.
Last edited by a moderator:
I forgot that the 6,1 is natively supported for APFS. You should try installing High Sierra on an APFS formatted drive. This should run a firmware update to add the APFS support.
What do you mean? While the installation stick indeed is HFS+, I tried installing macOS Mojave on an APFS drive, as described previously. Even when the installation drive was APFS formatted, the checkbox for APFS Patch was greyed out, while the BIOS was still unable to find the drive during boot.
PS: Well, was an easy one. I used the search function for APFS ROM Patcher Password, but couldn't get any results - I guess I'm too intimidated by the front page heheh
[doublepost=1553104898][/doublepost]
I see, so that additional upgrade step is not included in the patches Mojave versions. Thanks for the insight!
PS: This whole process could really use a proper Wiki imo, so people here can actually focus on discussing current topics.
Last edited by a moderator:
The MacBook6,1 supports APFS natively. In order to get it to boot from an APFS volume, you first need to install High Sierra so your BootROM is updated for APFS booting support. Then, you can install Mojave.
The wiki is community managed. Anyone with more than 100 messages can make changes. The password is listed at the end of the APFS ROM Patcher section.
A wiki for me is what you refer to as a Q&A. Something that could work quite well is either a GitHub Wiki or https://readthedocs.org/
imo the search functionality is insufficient to help an inexperienced user to get started as the process turns out to be quite complex after all. It's obviously easy once you know the specifics a little better, but the beginner questions just bloat this thread. Which is mainly due to insufficient resources to read things up properly.
The wiki is good but I do think we need a Q&A. In that situation, do we want a closed access Q&A with modification access to only certain people or a community managed Q&A?
Last edited:
You should have done on April Fools day, would have been more credible.
Anyway I know you don't want hack no one, and they are shell scripts so open-sourced, most dangerous instead unknown closed-source binary files.
Last edited by a moderator:
It was meant as a secret message for those who find it to try and access. I never planned on anyone actually finding it let alone reading it. The message isn't a joke though.