Anonymous
What we got here is a very unhealthy situation, where somebody without basic knowledge about eMMC, UEFI, partitioning … takes a ‘broken by design OS’, starts it somehow, let it do something, without understanding the consequences and then produces itself a problem that should have never happened in the first place, if one would have been informing itself when it was time to do it. The result is a situation that can’t be solved in this thread except in two cases: 1. a blind shot in the dark (== pure luck); 2. start from the beginning.
There are simply too many things to consider in this case: UEFI/CSM, Secure-Boot modes, ‘Other OS’ options, eMMC, OS that uses hacks instead of a ‘standard way’ of installing …
Easy explained, eMMC is simply a SD-Card inclusive Card-Reader which is soldered on the mainboard.
The main difference between normal SD-Card and eMMC is that one can boot from eMMC (–> mmcblkXbootX)but, not from the SD.
If you are wondering about mmcblk0boot0 and mmcblk0boot1, you can start reading here:
http://www.kernel.org/doc/Documentation/mmc/mmc-dev-parts.txt
http://trac.gateworks.com/wiki/MMC
They are not partitions as in the usual sense but the place (or part of?) where UEFI (the firmware, not the ESP) puts the “boot partition”(s).
Read about eMMC specs (search for ‘white papers’ that explain technology behind) if you want to know more about them.
The user part is mmcblk0.
Now, the possibility to use the different boot modes like UEFI and CSM combined with different ways of how the ISO files were made (MBR, UEFI, Hybrid) and different ways of how different ‘bakers’ are writing the ISO’s on a USB drives, results in a chaos, if one doesn’t exactly know what one’s doing — which is obviously your case.
Proper ‘baking’ software, ‘baking’ proper OS would (in your specific case) result in a USB pen drive which would offer you 2 (two) different boot options: MBR (CSM) and EFI/UEFI.
Obviously, if you have a UEFI based HW (like yours) but, your USB DOES NOT show the both options, then something went wrong — either ‘baker’ or the ISO-maker screwed it.
In a perfect case, if your HW was installed in UEFI mode, you would have a GPT partitioning (that’s always the case with every YOGA + Windows).
If you are reinstalling or dual-booting, you would choose the UEFI option from your USB drive and NOT MBR option since that one would result in ‘mixed mode’.
That’s a Linux problem — it allows something that it shouldn’t be allowed in the first place.
If you want to find out more about it, you can start with these links and then continue ‘binging’, ‘googleing’, ‘searxing’ or whatever.
http://help.ubuntu.com/community/UEFI
http://askubuntu.com/questions/221835/how-do-i-install-ubuntu-alongside-a-pre-installed-windows-with-uefi
http://opensource.com/article/19/5/dual-booting-windows-linux-uefi
http://forums.linuxmint.com/viewtopic.php?t=219231
http://forums.lenovo.com/t5/Other-Linux-Discussions/confusion-about-UEFI-BIOS-and-GPT-MBR-compatibility-issues/td-p/1556526
http://www.rodsbooks.com/gdisk/hybrid.html
Two things to keep in mind — certified UEFI distributions will show the needed options in their installers:
http://heise.cloudimg.io/width/778/q75.png-lossy-75.webp-lossy-75.foil1/_www-heise-de_/select/ct/2018/23/1541481050338744/contentimages/image-1540195440458058.jpg
Lenovo had some broken BIOS versions which, when used together with some broken OS (almost all Linux distributions except Ubuntu/Ubuntu based and evtl. Fedora), resulted in:
http://heise.cloudimg.io/width/712/q50.png-lossy-50.webp-lossy-50.foil1/_www-heise-de_/ct/imgs/04/1/1/6/7/7/2/0/22_-eed7e1ec66ae867f.png
For German speaking people here, willing to make use of their credit-cards, there’s a very good explanation of Linux/UEFI/CSM problem and a proper way of installing, tipps and …
http://shop.heise.de/katalog/c-t-23-2018
As of a solution for you, there a few possibilities:
1. If you have some Windows 10 bootable media laying around, you might try starting Windows installation.
The point is not installing Windows itself but the fact that, Windows installer might help restoring eMMC.
At some point, Windows installer will show you the existing partitions and that’s where you should delete all partitions that show up.
http://ibb.co/LkHmZTM
Afterwards, you create one single NTFS partition and shutdown the computer without installing.
With a little luck, Windows reinitialized and repaired/restored the eMMC ‘automagicaly’ and you know exactly where you are — you’ve got GPT initialized eMMC.
2. If you have properly created USB (as discussed above), you simply boot from USB and choose the EFI/UEFI (NOT MBR!) option on start and Ubuntu/Mint will automatically start in the proper mode and will be able to install correctly.
When the Live DVD/USB starts you can tell immediately where it’ll end up by its Start Screen (as you could see on the screenshots in one of the links above).
If the BIOS is set up to boot the CD in UEFI mode: http://pix.toile-libre.org/upload/original/1347445084.png
If the BIOS is NOT set up to boot the CD in UEFI mode, or if the disk is not 64-bit: http://pix.toile-libre.org/upload/original/1347445119.png
—
If that failed or you did something wrong again, you might try:
Get STANDALONE version of GParted (Ubuntu-based version, NOT Debian-based!), ‘bake’ it with Rufus under Windows and try to ‘destroy’ ALL partitions so you can reinitialize in the desired mode — either MBR or GPT (preferably GPT).
http://gparted.org/download.php
http://rufus.ie/
If that failed too, you might consider getting help of some IT-Specialist which understands the whole problematic.
However, that could easily cost more than your device itself.