09-24-2017 03:05 PM
Me too!
This is totally weird. I cannot change anything but the time and date. None of the method found on internet worked.
I've Linux installed so even flashing BIOS is not an option.
I've tried to install complete new system on a second harddrive, swap it after but BIOS is failing to boot.
Lenovo support, you are really needed here!
09-25-2017 10:51 AM
I've found an advice to remove cmos battery, main battery and memory and do several restarts combined with adding the cmos, memory etc. every few reboot sequentially.
It didn't work.
I'm still stucked with same configuration. Lenovo phone support said without Windows I/they cannot do nothing. Only sending the laptop for (after warranty) service. We will see, how much that will put me back...
10-21-2017 12:11 AM
10-23-2017 03:02 PM
same here
10-24-2017 12:05 PM
OK, although the problem is marked as "Solved" it is not.
DISCLAIMER!
I've created a "prosthetic" bypass allowing me to avoid Lenovo service and (most probably) very expensive option of replacing MB.
To the point.
Premises.
I had working Antergos installation while discovered the BIOS issue. Wanted to install new system but was not allowed to change boot settings (nor in BIOS or via boot menu).
Using command:
efibootmgr -v
I've got my EFI boot configuration that looks like this:
BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0001,0002,2001,2002,2003 Boot0001* antergos_grub HD(1,GPT,f128f12b-fa3e-45b1-b5c9-f03c328498cb,0x800,0x64000)/File(\EFI\antergos_grub\grubx64.efi) Boot0002* Windows Boot Manager HD(1,GPT,f128f12b-fa3e-45b1-b5c9-f03c328498cb,0x800,0x64000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC
It means the file grubx64.efi in antergos_grub directory will be loaded as first. Nothing else. And from no other drive but the 1st having the ID: f128f12b-fa3e-45b1-b5c9-f03c328498cb
So. Am I forever bound the Antergos? Well, no.
Long story short.
I've downloaded rEFInd package and REPLACED the antergos_grub directory with the content of rEFInd package, renaming the refind_x64.efi to grubx64.efi
Now, after restart I've rEFInd boot menu (you can compare it to the BIOS boot menu) with the option for selecting boot source (including USB drives and optical drive (my case also via USB)).
This way I was able to install openSUSE and few other systems in between.
BUT!!!!
You must never erase the first partition with the rEFInd bootloader.
It will bind automatically systems installed on the next boot partition.
What if my hard drive got damaged or anything... Well, I thought of that too.
Using command:
sfdisk -d /dev/sda > HD_partitions.txt
you get a file named HD_partitions.txt containing IDs of all your partitions.
You only need the first value. In my case:
/dev/sda1 : start= 2048, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=F128F12B-FA3E-45B1-B5C9-F03C328498CB, name="EFI System Partition"
I took second disc, made same first partition on it, exported the partition table with the same command and REPLACED the uuid value from the main disc.
Then what you need to do is flipping the "pipe" direction, from ">" to "<" and write the partition table to another disc:
sfdisk -d /dev/sdb < modified_partition_table.txt
(Assuming the second drive is sdb!!!).
That is all.
TL;DR
rEFInd is your friend.
Thank you for your attention.
11-04-2017 05:54 AM
11-05-2017 01:29 AM
To install further Linux(es) you need to create second EFI partition where the GRUB is installed. rEFInd will detect all of them and show in the menu to select from. This is how I have it right now.
11-12-2017 10:28 AM - edited 11-12-2017 10:29 AM
@Marcin78 (post 15) You are the best!! I've been stuck having to press f12 and choose the windows bootloader because an old ubuntu bootloader was default for a year now...
Worked like a charm (on my y70-70 Touch) =] I just had to get all the files from the old ubuntu bootloader that I had deleted (duh!) and then put refind on top and now I can usb boot again!
Thank you for giving me back my linux!
11-12-2017 11:25 AM
11-12-2017 12:07 PM - edited 11-12-2017 12:09 PM
I have the same problem... after upgraded Ubuntu to 17.10 version, the bios won't save any change...
So, i bought a new chip and a will try to flash with an older version of my bios...
Stay tuned!