Gfrktyl

After trying to install Linux (CentOs) and it crashed I can no longer boot W10.
I can only choose OS X and its recovery after the alt option key....
The EFI partition is renamed to blank / NO NAME, as you can see in the diskutil list before installing Linux:

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

And after the Linux install crashed:

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI NO NAME 208.7 MB disk0s1

Somehow the Linux install renamed the EFI partition to NO Name or blank and what more......

Does anyone know how I can resolve this?

By the way I did follow the steps of

http://www.makeuseof.com/tag/install-linux-macbook-pro/
to install CentOs instead of Ubuntu.

Without success ......

This helped me a lot!
It looks like the install of CentOs made a new boot partition.
I started Try Ubuntu and gnome-disk give the following info:

sda3
Size ---------------524 MB — 491 MB free (6.3% full)
Device ----------- /dev/sda3
Partition Type ---Basic Data
Contents --------XFS — Mounted at /media/ubuntu/564b41fb-86e3-4350-b906-65d36dae16c6

Also the old EFI boot is still there:

sda1
Size --------------209 MB (208,666,624 bytes)
Device -----------/dev/sda1
Partition Type ---EFI System
Contents --------FAT (16-bit version) — Not MountedEFI System

EFIbootmgr gave the following result in Ubuntu:
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0080,0000
Boot0000 Windows Boot Manager*
Boot0080 Mac OS X*
Boot0081 Mac OS X*
Boot0082 *
BootFFFF *

The question is how to get lost of the new boot partition and get back to the old boot partition sda1, and that it will boot from there.... Or not?

For better understanding I have attached screenshots of the disk:
CentOs Disk Partition screenshot
Ubuntu disk part sda1 screenshot

Sorry for my lack of understanding ;-(

I did install W10 Technical preview directly to my opinion.

But it was made with or without a MBR, I really don't know...

Can you recognize a MBR?

I did run Try Ubuntu to run gdisk:

ubuntu@ubuntu:~$ sudo gdisk /dev/sda

GPT fdisk (gdisk) version 0.8.8

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p

Disk /dev/sda: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): C38E8DF0-D5D2-460C-BD6A-EAD7406FB049

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 977105026

Partitions will be aligned on 8-sector boundaries

Total free space is 4697 sectors (2.3 MiB)

Number --- Start (sector) --- End (sector) --- Size --- Code --- Name

1 ----------- 2048 ------------409599------199.0 MiB -EF00 ---EFI System Partition

2 ---------409640---------391034639-----186.3 GiB - AF00 ---MacIntosh HD 1

3----- 391034880 --------392058879------500.0 MiB - 0700

4-----486737768 ---------488007303 -----619.9 MiB - AF00 --Recovery HD

5-----488007680 ---------976080895------232.7 GiB - 0700 --BOOTCAMP

6-----976080896 ---------976183295 ------50.0 MiB - 0C01 --Microsoft reserved part

7-----976183296----------977104895 -----450.0 MiB -2700

8-----392058880----------486735871 ------45.1 GiB - 8E00

It says that there is an MBR (protective)

Can you advise how to continue?

Chances are it's not the renaming of the EFI System Partition (ESP) that's the problem. (I note also that its size has changed slightly -- but again, I don't think that's the issue.) Chances are the installation attempt has wiped out a hybrid MBR upon which Windows was reliant for booting. If so, restoring the hybrid MBR should fix the problem. You can do that with my gdisk program or with gptsync (which comes with the old rEFIt, my rEFInd fork of it, and as a standalone program in some Linux distributions). Apple's Disk Utility can also create hybrid MBRs, but I don't know of a way to force it to create one without making other changes to the disk. (Normally it'll do the job when you create a FAT partition, for instance.)

Another possibility is the exact opposite, depending on the nature of the boot problem: It could be that the failed installation, or your attempt to recover from it, has created a hybrid MBR where one had not previously existed. This is a more likely explanation if you installed Windows 10 directly, rather than if you upgraded to Windows 10 from an earlier version.

Unfortunately, Apple's early reliance on hybrid MBRs and subsequent shift away from them has created an environment in which you need to be an expert to recover from problems like yours.

EDIT:

Please don't create multiple answers, or use answers to ask more questions. Instead, edit your question or post follow-up questions as comments to answers. This site sorts answers by votes, so using multiple answers to carry out a conversation quickly becomes very confusing because it becomes impossible to follow the sequence of questions and answers.

Based on your gdisk output, you've currently got a standard protective MBR, which means a pure-GPT disk (not a hybrid MBR). Thus, you've got conflicting indications -- the efibootmgr output indicates a probable EFI-mode Windows install (at some point); but if it's not booting with the current partition table, that might hint at a BIOS-mode Windows install (at some point). It's also possible it's always been EFI-mode, but something's trashed the Windows boot loader.

Given that your ESP is now a different size than it had been, my best guess at this point is that you (or the CentOS installer) inappropriately deleted and re-created the ESP, thus destroying the Windows boot loader. If so, then this question and answers may be your best bet for recovery.

EDIT 2:

You can always edit your question if you need to add extensive information.

Also, in all the back-and-forth, I forgot you were dealing with a Mac. It's possible that your ESP retains Windows boot files, but the Mac just isn't displaying them. If so, installing my rEFInd boot manager may restore your ability to boot both OSes. Before you do that, though, you should determine whether there are Windows boot files on your ESP. (I believe that's what you mean by "MBR partition." You have no MBR partitions, since your disk is GPT-only.) Mount it and look for a file called EFI/Microsoft/Boot/bootmgfw.efi. If it's present, that's your Windows boot loader, and rEFInd should enable you to launch it. If it's absent, then you'll need to follow a Windows recovery procedure to restore it. In fact, you might want to search the ESP for any files with names that end in .efi; those are EFI boot loaders (and possibly related files, like drivers).

Deleting your ESP will not help, and could make matters worse! At this point, it appears that either files are missing from the ESP or you're lacking the ability to launch files from the ESP. In either case, deleting the ESP will, at best, do no good. If there are relevant files on the ESP, deleting the ESP will just make matters worse.