11-12-2017 11:59 PM
11-13-2017 06:13 AM
I have a eprom programmer (Minipro TL866CS)..
I did'nt flash the original chip on the motherboard, but i bought a brand new chip (i had found an GD25Q64BISIG on ebay)
so i read the original eprom (the 3.03 that didn't save any change) and i saved the file (eprom303.bin).
Obviously, before I put out the bios chip with hot air...
After that, I programmed the new chip with the old data. I soldered the new chip on the motherboard ... and now it works! now save all change, now i can boot in legacy mode!!!
I didn't try to remove and solder the same chip..maybe this work too.
Sorry for my bad english... but i hope to help somebody to fix this problem
11-13-2017 08:01 AM
11-13-2017 12:20 PM
11-30-2017 01:24 AM
I have the same issue but with some differences.
My device is in dual boot. Windows 10 and ubuntu latest.
Now I am able to open only ubuntu.
While ttrying to open Windows it shows :
alloc magic is broken at 0x74cc3de0: 0
Aborted. Press any key to exit._
So what to do now.
Thanks in advance for any kind of help related to this.
12-01-2017 02:47 PM
I think it is really absurd that some basic feature like dual-boot bricks a BIOS chip. Actually absurd part is it is a known issue and Lenovo doesn`t do anything about it. I had to send my PC to Hardware service to solve the issue. But I had to dual boot for my project and i think it accured again. Luckly this time I realized before losing both OS but still if I want to change OS it is not possible anymore, It makes me feel left alone by the company. I don`t know what we can do about it
12-01-2017 10:17 PM
12-02-2017 02:18 AM - edited 12-02-2017 02:20 AM
A simple fix can be provided by Lenovo Engineers is a bios recovery update using USB flash drive, but unfortunately this solution isn't even available for our laptop...
12-02-2017 02:37 AM
Please don not spread false information. It is no Ubuntu 17.10 issue. I never had Ubuntu but Antergos and the same happen to me. This is hardware failure of the NVRAM - too many writes, caused by how Linux/systemd (my guess) is handling any Kernel related change.
The real fix has been mentioned here - replacing the NVRAM and copying the old ones content to it.
Wayaround - my solution with rEFInd.