this is the reading without a chip
Mac EFI Toolkit
Collapse
X
-
PITERPENY I'm not sure, I've no experience with the EZP. You'll have to find a "compatible" 1.8V chip model by chance in the list. I had to do this when I had a TL866II+.Comment
-
PITERPENY I'm not sure, I've no experience with the EZP. You'll have to find a "compatible" 1.8V chip model by chance in the list. I had to do this when I had a TL866II+.! You should not press test in the program, this will not give anything and there will be an error, you just need to read it right away and then we will get the ROM file
! By the way, if you do not use the 1.8v adapter, nothing happens to the chip, but the file will not be complete (no serial number, etc.)
! But nothing burns, this is good! Of course there is much more information on EFI ROM
but the fact that you can quickly rewrite the serial number is priceless! And once again I want to thank muerto for the work done! thank you
Comment
-
PITERPENY Thanks for sharing, I see the hardware config MD6M was missing from the internal database so it has been added for the next update. HWC: MD6M = CC: MacBook Pro (16-inch, 2019).
Comment
-
Comment
-
PITERPENY One is a 25 series SPIROM, one is a 24 series EEPROM (SEPROM). Never touch the SEPROMComment
-
-
Working on a dump of a 2017 iMAC (820-00579 board) with a locked BIOS. It's the current version from Ventura (529.140.2.0) and showing that APFS driver not present. Just a cosmetic thing so not a biggie.
Also noted there is no Save As option. If you make a change (e.g. clear NVRAM) and don't save it, there is no option to Save, other than to go back in again and do the same action then hit save.
​
Comment
-
Is there any chance you can zero the serial number in that firmware and send it to me? I might have broken something in the update, as there were changes made to the GetIsApfsCapable function.
As for the 'save as', I've purposefully designed it that way. When you apply a patch it will load in a clone of the binary buffer, patch and promt the user to save it. If one cancels, it will discard all patches in memory.
Working on a dump of a 2017 iMAC (820-00579 board) with a locked BIOS. It's the current version from Ventura (529.140.2.0) and showing that APFS driver not present. Just a cosmetic thing so not a biggie.
Also noted there is no Save As option. If you make a change (e.g. clear NVRAM) and don't save it, there is no option to Save, other than to go back in again and do the same action then hit save.
Comment
-
-
Version 2.0.3 released:
https://github.com/MuertoGB/MacEfiTo...leases/tag/203
Comment
-
Version 2.0.3 released:
https://github.com/MuertoGB/MacEfiTo...leases/tag/203but version 203 did not
Comment
-
-
Hi, nothing changed for the T2 SocROM code from v202 > v203 (https://github.com/MuertoGB/MacEfiTo...6603d44f38a65d). M1 devices are not supported, only Intel based T2 SoCROM.
If you like, you could pass me the firmware so I can test, however it would still not load after. There's nothing of interest in Apple Silicon ROM apart from iBoot version.
Comment
-
Hi, nothing changed for the T2 SocROM code from v202 > v203 (https://github.com/MuertoGB/MacEfiTo...6603d44f38a65d). M1 devices are not supported, only Intel based T2 SoCROM.
If you like, you could pass me the firmware so I can test, however it would still not load after. There's nothing of interest in Apple Silicon ROM apart from iBoot version.
socrom2337Comment
-
Hi, nothing changed for the T2 SocROM code from v202 > v203 (https://github.com/MuertoGB/MacEfiTo...6603d44f38a65d). M1 devices are not supported, only Intel based T2 SoCROM.
If you like, you could pass me the firmware so I can test, however it would still not load after. There's nothing of interest in Apple Silicon ROM apart from iBoot version.Comment
-
Version 2.0.3 released:
https://github.com/MuertoGB/MacEfiTo...leases/tag/203Comment
-
Version 2.0.3 released:
https://github.com/MuertoGB/MacEfiTo...leases/tag/203Comment
-
This is a thread about Mac EFI Toolkit, The Tiva E SMC is not supported. Turn your bloody caps off, the whole forum can hear you.Comment
Related Topics
Collapse
-
Is there a way to change the CPU multiplier through editing the laptop's BIOS. I have a Latitude 7300 using Intel core I7-8665U CPU which has default multiplier settings between x4.0-x48.0. The problem with the device is that as soon as Windows boots up, the processor temperature is always high (usually in the range of 97-100 degrees Celsius), the multiplier is in the range of x46.0 - x48.0 even though no applications enabled. On a desktop we can change many things related to core voltage, multiplier or base frequency. but on laptop models using U suffix processors this is not available. I would...
-
Channel: BIOS Requests ONLY!
07-22-2024, 07:57 PM -
-
by SMDFleaCopying DMI information from an old bios to a new one is difficult for some members, often they have no experience with a hex editor,or some that have tried find it too hard.There is an option to make things easier for those members so that they don`t need to post their own bios backup for the DMI copying.
Experienced bios modding members can help by posting in other threads the DMI offsets,macro script generated by the software and a download link to the software at softpedia mentioned in this guide,or post your macros in the comments here with a link to the bios request thread ....-
Channel: BIOS Requests ONLY!
-
-
by Aditya11tttPost Hp | Dell | Asus | Lenovo
on board Ram Bios we try to disable via bios edit.-
Channel: BIOS Requests ONLY!
-
-
by Rustam14Zenbook 13 UX325 Intel Core i5-1135G7 UX325/425EA REV 2.1
Hello! I can’t edit the bios on the asus, I tried to manually glue it from ASUS support and through Fit.
turns on without iso tries to initialize and turns off...-
Channel: BIOS Requests ONLY!
-
-
by grimacelordHello,
I have a Lenovo Flex-14IWL here that I believe might be suffering from a corrupt BIOS. The device tries to power on, but black screen and no fan spin. The power LED then quickly turns off. I admit I am not 100% certain it's corrupt BIOS, but this is something relatively easy that I can rule out before I begin diagnosing board-level hardware problems. So far, I have:
1. I have saved the original (possibly corrupt) BIOS from the chip using a programmer. This file is 16,384KB in size and is in .BIN format.
2. I have extracted the BIOS image from the Lenovo...-
Channel: BIOS Requests ONLY!
-
- Loading...
- No more items.
Comment