This documentation is more thorough than for previous versions of this patcher, but it may still be incomplete. In addition, thanks to Ben Sova, MachInit, johncaling40, and Travis Parker for their contributions to this patcher. Ausdauersportler for integrating patches for iMac Metal GPU support.This turned out to be a good way to make LegacyUSBInjector function under Big Sur, and more generally and more importantly, it was absolutely essential for improving overall patcher reliability. testheit for describing how to use a kmutil feature that I was previously unaware of.ParrotGeek for developing the LegacyUSBInjector kernel extension that allows USB to work on various pre-2011 Mac models, and for creating the "trampoline" that allows the installer to be patched at runtime without first running Terminal commands.highvoltage12v for developing the first 802.11n Wi-Fi patches for Big Sur (no longer used by default, but still available through the -wifi=hv12v-old and -wifi=hv12v-new options for patch-kexts.sh), as well as patches used for Metal GPU support on 2011 iMacs.jackluke for figuring out how to patch the Recovery USB to bypass compatibility checks and AMFI enforcement in the absence of NVRAM boot-args settings. ASentientBot for developing the Hax series of installer patches which are so incredibly helpful for installing Big Sur on unsupported Macs, as well as for his patch to NVDAResmanTesla.kext which allows the GeForce Tesla (9400M/320M) framebuffer to work in Big Sur. Thanks to the following people for their hard work to get Big Sur running on unsupported Macs: For 2008 Mac Pros (MacPro3,1) in particular, Big Mac is clearly a better option than this patcher (at least for now). Just because greed is greed and $109 is still $109.A primitive USB patcher for installing macOS Big Sur on unsupported Macsīy the way, if you have a Mac Pro, Big Mac by StarPlayrX is another patcher worth considering. There is no doubt that in response to mainstream usage of this interface, it will be disabled in upcoming firmware versions, making life significanty difficult for everyone. SPI bus access via vendor ATA is a firmware-controlled feature, not a hardware interface. There is no doubt that as with UHD support, in a few days the respectable commercial firmware downgrade utilities would stop requiring changing the setting of IDE controller and would start working with USB drives. If anyone wants to make a community service and post official firmware images with this byte patched, you are welcome to do so in this thread. No checksums, no digital signatures, nothing. With this byte changed, the firmware will be accepted by drives with latest firmware, allowing downgrade using official flasher. In fact on all (old) firmwares the bytes just before this byte have some distinct values, and all bytes after this byte are FFs.Ĭhange just this single byte (at location 0x1ec056) from 0xFF to 0xDE ("downgrade enable").Ĭongratulations! You are an elite hacker now. Open the firmware BIN file with a hex editor. Here are instructions for the super-duper-secret-mega hack that would allow flashing the old firmware into drives with latest firmware: Any old firmware can be patched this way. A custom step is required to make the old firmware flash-able on a latest-firmware drive. For example ASUS drive with 3.03 firmware would refuse to flash firmware 3.0 (present in archive from link above). Normally official flasher would refuse to downgrade firmware from latest versions - the so-called "Write DRAM NG 05/24/00" error. This is important step - the official update BIN is needed, not a dump of any sort or "cleaned" dump. The archive at link above contains some images already. s58-96313/ This flasher operates using drive self-update mode.Īn unpacked official update image (bin file). No dosflash, no direct flash write, no meddling with IDE controller settings.Ī patched official MTK flasher. Here is my "guide" how to downgrade any MTK firmware using only official flashing app. Normally I avoid doing so, but the current insanity has to be stopped. To stop the painful drive abuse I have to divulge some information. This method is highly dangerous ( please see viewtopic.php?f=16&t=18857 ) but is used widely because this is the only method that is publicly available. Guides on our forum written by fellow members are also based on this method. Live flash update in raw mode became a commodity. DVDFab tool method) became more and more popular. However recently the firmware downgrade method using SPI access via vendor ATA commands (a.k.a. NOTE: Information in this post is mostly obsolete, please see the main FAQ thread for an up-to-date information - viewtopic.php?f=16&t=19634Īs mentioned many times earlier, I personally do not recommend downgrading your drive firmware without understanding the possible consequences.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |