MacBook Pro Late 2016 Serial Numbers

Here are the first four/thirteen eighteen serial numbers of the new MacBook Pro (updated):

GTDX – MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 ports)

GTDY – MacBook Pro (15-inch, Late 2016)
GTF1 – MacBook Pro (15-inch, Late 2016)

GTFJ – MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
GTFL – MacBook Pro (15-inch, Late 2016)
GTFM – MacBook Pro (15-inch, Late 2016)
GTFN – MacBook Pro (15-inch, Late 2016)

GVC1 – MacBook Pro (13-inch, Late 2016, Two Thunderbolt 3 ports)
GVC8 – MacBook Pro (13-inch, Late 2016, Two Thunderbolt 3 ports)
GY25 – MacBook Pro (13-inch, Late 2016, Two Thunderbolt 3 ports)
GY6N – MacBook Pro (13-inch, Late 2016, Two Thunderbolt 3 ports)

GYFH – MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
GYGR – MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)

H03Q – MacBook Pro (15-inch, Late 2016)
H03T – MacBook Pro (15-inch, Late 2016)
H03M – MacBook Pro (15-inch, Late 2016)
H03Y – MacBook Pro (15-inch, Late 2016)
H040 – MacBook Pro (15-inch, Late 2016)

Initially I only had four of the entry level MacBook Pro. The one without the new Touch Bar/Touch ID. Now I also have some of the MacBookPro13,2 and MacBookPro13,3 And more will be added once they become available.

p.s. Not all links will be forwarded to the support document – Apple has to update them first.


9 thoughts on “MacBook Pro Late 2016 Serial Numbers

  1. If you have access to MBP13,3 – can you make DarwinDumper dump? And maybe dump of kexts. It has HD530 inside, and we are still facing strange glitches with same video as on MBP13,3. Can be very useful to check how things are made on real mac…

    • LOL You can order a brand new MBP13,1 on-line and make that dump yourself. After that you can either keep the new MBP or return it.

      But seriously. Look at this -disablegfxfirmware boot argument. Why do you think that it is implemented? Because Apple is using custom firmware? If you boot with -disablegfxfirmware and check the log then you see that it won’t search for firmware anymore. But nope. This boot argument itself is not the fix. Extracting the GFX firmware from the EFI image is.

      I also found some new EFI property in the firmware: board-rev, device-colors, MachinePersonality and personality.

      SMBIOS is now 3.0

      Edit: The MBP13,1 comes with Build 16A2323a and also runs Build 16B2657 after the first update. This helps you track the kexts that are updated by the AutoPatch.pkg (check the link in the developer CatalogURL).

      • Unfortunately I can’t 😦 In my country there is no even official Apple store. Yes, i’m living in such country – it is called Ukraine 🙂
        And also 13,1 is not so interesting bcz of Iris graphics. I just thought you have some access to 13,3 machine with HD530 onboard – this video is used on a lot of hackintoshes with i7 skylake. And it is working fine on 10.11.6. But has weird glitches on Sierra. So we are trying to find out what is wrong – driver itself is not ready for HD530 and will be updated later, or we are doing something wrong to make it working on 10.12
        And excuse me if i’m boring you. Just trying to find out any workaround for people with Skylakes that are stuck currently on El Capitan

      • Bored? No way. Things only get more interesting. I also gave you a pointer about the changed kexts. I mean. Just compare the binary of AppleIntelSKLGraphics.kext from El Capitan with the one for Sierra. Use Hopper to search for -disablegfxfirmware. Follow the path to the code and note the (frame buffer) checks for 0x19020001, 0x19120001 and 0x19320001 (set to use the ‘Default EL Scheduler’) since GraphicsFirmwareSelect in the Info.plist is set to 2. The binary skips this if it is set to 1.

        Now scroll down to the checks for 0x09038086, 0x09048086, 0x19268086, 0x193b8086. 0x19328086. This whole section cannot be found in the binary for El Capitan. Also note the or eax, 0x4000 there. That also isn’t there in the binary for El Capitan. But more importantly. Where is our device-id? It’s not there! Please note that El Capitan does not check for device-id’s so…

        What happens when we change, say, cmp ecx, 0x9038086 into cmp ecx, 0x19128086?

  2. goodwinalexs You are right I’m digging in and out and reading all posts I came across with related or not, to have some understanding on “Whats the reason of these glitches with HD530 behind the scene” and I feel that I’m close to find out. Everything existed for a reason especially in programming there is always a workaround we just have keep pushing wall.

    • Just found one interesting thing. In 10.12.2 (not sure about earlier builds, have no one to check) in AppleIntelSKLFramebuffer there is new ID – 191b0006. Tried booting with it – boots fine with acceleration, but still same glitches… Also, grabbed SkylakeGraphics efi driver from MBP13,3 bios – it has also 0006 1B19 id inside (new one). Thing are going to be more interesting… Trying to dig deeper…

  3. Also, i think, having dump from new MBP will be also useful to help with making correct ACPI patches for USB-C gen2 and TB3. But currently, not so much people with IT experience has it…

  4. goodwinalexs AND pikeralpha i know its old post i just need to know from where to start to understand how u know the value you check
    i have different thing the hd530 on p50 laptop and it works fine but no luck with hdmi

    p50 run laptop display through p50 and hdmi port through nvidia quadro m1000m

    i need to know what to read to understand patching i know C++ java but i cant understand what is this

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s