MP51.0084.B00 Rom Dump Request

[MisterAndrew]

Has anyone besides zozomester tried injecting the new firmware with the NVMe driver? Is it working for you?
[doublepost=1527953960][/doublepost]Is the NVMe driver injected into the older firmware not working with 10.13.5 as well?

 

[zozomester]

Did you back up your firmware before you upgraded?

Does anyone know where the serial number is stored in the firmware?

I updated yesterday ... I do not know where the serial number is
[doublepost=1527954890][/doublepost]

Has anyone besides zozomester tried injecting the new firmware with the NVMe driver? Is it working for you?
[doublepost=1527953960][/doublepost]Is the NVMe driver injected into the older firmware not working with 10.13.5 as well?

Unfortunately I updated the Bootrom firmware before 10.13.5, so Hack does not work.

 

[h9826790]

Yes, unfortunately, the new firmware does not work with the Gillies hack....

Perhaps you could PM Gilles and offer your cMP for testing solutions ?

Do I miss anything?

How you guys confirm the hack doesn't work with the 0087.B00 firmware?

From what I've read. zozomester never do the firmware hack by himself. His 0085.B00 firmware was modded by another member.

He flashed that modded 0085.B00 firmware onto the Mac. Then the cMP can boot from NVMe natively.

But then he upgrade to the Apple stock 0087.B00 firmware, which of course will completely replace the modded 0085.B00 firmware.

Until he mod the 0087.B00 and flash the cMP again, the cMP of course cannot boot form NVMe natively.

So far, I can't see anything to confirm the hack doesn't work on the 0087.B00 firmware.

 

[zozomester]

Do I miss anything?

How you guys confirm the hack doesn't work with the 0087.B00 firmware?

From what I've read. zozomester never do the firmware hack by himself. His 0085.B00 firmware was modded by another member.

He flashed that modded 0085.B00 firmware onto the Mac. Then the cMP can boot from NVMe natively.

But then he upgrade to the Apple stock 0087.B00 firmware, which of course will covered the modded 0085.B00 firmware.

Until he mod the 0087.B00 and flash the cMP again, the cMP of course cannot boot form NVMe natively.

So far, I can't see anything to confirm the hack doesn't work on the 0087.B00 firmware.

I and mikeboss have modified this new Firmware. Does not work.

 

[h9826790]

I and mikeboss have modified this new Firmware. Does not work.

I see, I miss this part. Thanks for the confirmation.

 

[zozomester]

I see, I miss this part. Thanks for the confirmation.

Has anyone ever succeeded in modifying it?

 

[h9826790]

I and mikeboss have modified this new Firmware. Does not work.

Did you try to use the ROMTool to flash the modded 0085.B00 back in?

 

[zozomester]

Did you try to use the ROMTool to flash the modded 0085.B00 back in?

Yeah, that does not work.

 

[h9826790]

Yeah, that does not work.

So, the ROMTool can't force flash a firmware, but can only perform "upgrade" or "re-flash the same version".

Or the ROMtool can't flash anything now after this firmware update?

 

[thomasthegps]

It's getting kind of ridiculous. Apple could easily bake in NVME and GOP drivers in their EFI in a heartbeat if they wanted to. I hope someone finds how to do all of that on every firmware as a way to give apple the middle finger and make us cMP users happy in the process.

 

[zozomester]

So, the ROMTool can't force flash a firmware, but can only perform "upgrade" or "re-flash the same version".

Or the ROMtool can't flash anything now after this firmware update?

I tried earlier and I modified the original ROM.
[doublepost=1527957640][/doublepost]

It's getting kind of ridiculous. Apple could easily bake in NVME and GOP drivers in their EFI in a heartbeat if they wanted to. I hope someone finds how to do all of that on every firmware as a way to give apple the middle finger and make us cMP users happy in the process.

The apple deliberately abolished the opportunity.

 

[crjackson2134]

I wonder if the latest firmware update was intended to ensure that HS is the last macOS version for the cMP. I hope that’s not the case, but with the next OS around the corner the timing seems suspect.

 

[h9826790]

I tried earlier and I modified the original ROM.

Understand that you modded the ROM, and tried to flash it.

But I want to know more to make it more clearer for everyone.

1) It doesn't work with 0087.B00 means?

A) can't mod the ROM
B) can mod, but can't flash the ROM
C) can mod, can flash, but can't boot from NVMe

2) If case B, did you tried just flash the dumped ummodded ROM back in? So that we can know if the ROMTool can work with a proper ROM, or the tool is disabled by 0087.B00.

 

[zozomester]

Understand that you modded the ROM, and tried to flash it.

But I want to know more to make it more clearer for everyone.

1) It doesn't work with 0087.B00 means?

A) can't mod the ROM
B) can mod, but can't flash the ROM
C) can mod, can flash, but can't boot from NVMe

2) If case B, did you tried just flash the dumped ummodded ROM back in? So that we can know if the ROMTool can work with a proper ROM, or the tool is disabled by 0087.B00.

The Hack runs normally, makes the terminal command a modified rom.
This modified rom does not work.
On efi bootscren not see nVME SSDs.

 

[MIKX]

Everything was looking so positive up until this bootROM upgrade.

Now it's a "Catch22" situation. If anyone HAS flashed their bootROM to MP51.0087.B00 . . they can no longer go back at least using the software we have available.

If the upgrades is done from a Combo or from the App Store, the bootROM is not upgraded from MP51.0085.B00. We need confirmation from Gilles regarding this.

( incorrect ) AFAIK zozomester did the 10.13.5 upgrade through the App Store = no bootROM upgrade . .
. . if so . . then the problem lies elsewhere.

EDIT : I just found zozomester's post where his 'Hardware Overview' indeed does show his current bootROM IS . .. MP51.0087.B00

I think that dosdude1 has it now . . . let's hope he gets an inspiration.

 

[zozomester]

Everything was looking so positive up until this bootROM upgrade.

Now it's a "Catch22" situation. If anyone HAS flashed their bootROM to MP51.0087.B00 . . they can no longer go back at least using the software we have available.

AFAIK zozomester did the 10.13.5 upgrade through the App Store = no bootROM upgrade . .
. . if so . . then the problem lies elsewhere.

zozomester
Can you confirm that your current bootROM actually is MP51.0087.B00 bootROM ?

Yes:
[doublepost=1527961130][/doublepost]How to make DXEinject file for new firmware?
I have the old one. Maybe that's the problem ...

 

[bookemdano]

I have to admit being sort of confused about the order of operations that you went through zozomester. So can you correct anything I got wrong here:

1. Running 10.13.4 and on bootrom 0085.B00 you flashed (using dosdude1 tool) a version of 0085.B00 with the NVMe driver injected. This allowed you to boot 10.13.4 from your NVMe drive

2. When 10.13.5 was released you installed it from the Mac App Store (meaning that your bootrom was unchanged and remained at 0085.B00) but after the install your cMP would not boot 10.13.5 from your NVMe drive

3. You flashed the stock bootrom 0087.B00 (by downloading and running the 10.13.5 combo updater). This resulted in still no ability to boot from NVMe

4. You dumped your 0087.B00 bootrom, injected the NVMe driver, and flashed it to you cMP, and you still cannot boot from NVMe.

Since you're the only one who presently has this problem (assume everyone else is too scared at this point to try it) it would be helpful to know the exact steps you took and in what order.

 

[MisterAndrew]

I can’t believe the old firmware couldn’t be flashed after the update. How would they implement that?

 

[zozomester]

I have to admit being sort of confused about the order of operations that you went through zozomester. So can you correct anything I got wrong here:

1. Running 10.13.4 and on bootrom 0085.B00 you flashed (using dosdude1 tool) a version of 0085.B00 with the NVMe driver injected. This allowed you to boot 10.13.4 from your NVMe drive

2. When 10.13.5 was released you installed it from the Mac App Store (meaning that your bootrom was unchanged and remained at 0085.B00) but after the install your cMP would not boot 10.13.5 from your NVMe drive

3. You flashed the stock bootrom 0087.B00 (by downloading and running the 10.13.5 combo updater). This resulted in still no ability to boot from NVMe

4. You dumped your 0087.B00 bootrom, injected the NVMe driver, and flashed it to you cMP, and you still cannot boot from NVMe.

Since you're the only one who presently has this problem (assume everyone else is too scared at this point to try it) it would be helpful to know the exact steps you took and in what order.

4. I dumped my 0087.B00 bootrom, injected the NVMe driver, and flashed it to my cMP, and still cannot boot from NVMe.

previously worked well with 0085.B00 previous version.

 

[h9826790]

The Hack runs normally, makes the terminal command a modified rom.
This modified rom does not work.
On efi bootscren not see nVME SSDs.

Thanks for the details. So, now we know even with the 0087.B00 firmware. we can

1) Dump the ROM with the cMP's serial number on it
2) mod the ROM
3) Flash the ROM

And the CMP can still boot. Therefore, not extra security features to stop us using a modded firmware.

The main issue now is

A) the "old" NVMe EFI driver doesn't work, or
B) the "old" way to patch the firmware doesn't work

Of course not at the best situation. But at least not entirely hopeless, and no one brick the cMP yet.

 

[MisterAndrew]

4. I dumped my 0087.B00 bootrom, injected the NVMe driver, and flashed it to my cMP, and still cannot boot from NVMe.

Can you boot 10.13.4?

 

[bookemdano]

4. I dumped my 0087.B00 bootrom, injected the NVMe driver, and flashed it to my cMP, and still cannot boot from NVMe.

Isn't that the same thing I said?

At what stage did you try to re-flash the previously modified 0085.B00 bootrom? After you flashed it, did System Information show 0085.B00 or 0087.B00?

 

[MisterAndrew]

I wonder if the latest firmware update was intended to ensure that HS is the last macOS version for the cMP. I hope that’s not the case, but with the next OS around the corner the timing seems suspect.

I don’t think that’s the case since the 2012 model is still supported. Has Apple ever denied an OS release to a still supported model?

 

[zozomester]

Can you boot 10.13.4?

 

[h9826790]

I don’t think that’s the case since the 2012 model is still supported. Has Apple ever denied an OS release to a still supported model?

In fact, even the 2010 model is also officially supported now.