Yes, sorry for any confusion there, I was not sure either, and it looked like that only helped him initially, then he programmed in BIOS I made including updating to that BIOS included ME FW too.

How are you trying to install windows, and onto what kind of drive? Make disk RAW and then try again

@Lost_N_BIOS So I have updated the ME into the newest one from BIOS version 6102 and flashed your BIOS after that (without reflashed the ME).
It is able to boot to Ubuntu as usual.

For Windows, it is the same thing. I cannot even get the installer to boot.
Still finding out why :)

@bagus - Maybe due to your settings (secure boot, CSM etc) and how you have the disk currently configured?
If NVME, disk must be RAW or initialized as GPT. If regular SSD/HDD, and secure boot enabled then it must be initialized as GPT, if CSM enabled you must use MBR initialized disk
But really, either way, it's best to make the target disk RAW and then point the installer to the RAW disk, then win10 installer will setup the initialization and partitions properly for the current BIOS configuration.

If you are not sure how to make disk RAW, do it from the win10 installer, either at the first screen where you choose language hit shift+F10 to get CMD prompt, or from repair/troubleshoot options in the installer/setup
Remove all other drives, so you have only USB and target win10 drive. Then from CMD prompt do the following

1. Diskpart
2. List Disk << Here, identify what your target disk is by size/name etc, and make note of it's #, you will use it's # next
3. select disk # << Here, instead of #, put target disk #, example >> select disk 0
4. clean
5. Exit

Reboot and run the installer again, then point it at the raw/blank drive, do not load any drivers or create any partitions etc, just select drive and click next

If this is a NVME, and you are using NVME mod BIOS, not sure if this system has NVME native compatibility, or you have to use mod NVME BIOS
anyway, if mod NVME BIOS, follow all steps exactly as noted at step #4 in the "This is what you should do" section of this guide. This does not strictly apply if BIOS is native NVME compatible, but you can still use this method/info
[Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS

It also sounds like possibly your installer setup/source is messed up, confirm on another system with this USB that you can run the installer/setup and it starts OK.

Guys,

I am receiving a factory new ASUS C621E SAGE Motherboard tomorrow. I do have one Xeon 6130 ES (arrived last week) - QL1M


What is the best option for me to proceed?

Shall I go for the latest stock BIOS (6201) and then install CPU and try it ?
Or shall use the modded by Lost_N_BIOS BIOS from post 241 (5503 based) BIOS and FlashBack it ?

I have read the whole thread, but I was unable to find a recommendation on how to proceed with a new board :)

I am quite techie, but I also do not know what tools and software are needed for direct BIOS flashing - is it CH384 (I used to BIOS mod some Lenovos in the past) or is it something else ?

@fallen2109 - new board is same as old board, if using ES/unsupported CPU you'll have to use mod BIOS, flash it via USB Flashback.
You're CPU 50652 CPUID, is certainly not compatible with stock BIOS, so you'll have to use BIOS from #241

CH341A + Dupont or other cables are needed to connect to the SPI header and flash this BIOS with programmer, but none of that is required here due to USB Flashback is possible
You may also be able to SOIC clip with programmer too, I can't remember and I don't have one of these boards so I don't know what kind of BIOS chip is there, or if it's soldered/in-socket etc - Someone else would have to answer you about that
But USB Flashback is all you need so really nothing to worry about further here in regards to a flash programmer.

@Lost_N_BIOS So - I will simply use your modded BIOS (based on stock 5503) from post #241 - correct ?

And I can do the flashback WITHOUT any CPU or RAM installed on the Motherboard?

By reading throughout the whole thread - I was left with the impression that ASUS stock BIOS 5602 or later also supports ES processors. Apparently - I got it wrong .

I do have CH341 programmer and all the cables clips that come with it - I believe an SPI cable is also part of the set I bought on eBay for my Lenovo unlock project couple of months ago.


Keep up the good work.

@fallen2109 - That's the only one that will work with your CPU
Yes, flashback works without CPU or memory installed, well not 100% sure about no memory (I think so), but no CPU for sure it works that way.
No, later BIOS do not support ES CPU, I thought I made one that should work but once tested it was a fail, so everyone is back to the one from #241

I just did it. There was no CPU and RAM installed (I am still waiting for my 192 GB RAM to turn up from the post ). The BIOS update led flashed for about 5 minutes or so and the USB stick LED was going flashing / constant lit. Now the BIOS LED is off. Can I presume that the process was successfully completed? The USB stick is a 1GB formatted as FAT32 and has only the BIOS file on it (properly named). Thanks for your help and sorry for being PITA .

Ah - one more question. If re-programming via the SPI - do you need to power the mother board or not ? I do not have experience with SPI programming - I am asking out of curiosity.

@fallen2109 - Wow 192GB! How much $$ was that, and how many sticks in that?
Sounds like it went correctly, you should be good to go

No, if ever programming via programmer, DO NOT power on the board or force power on the PSU etc
Here is a good guide with lots of images since you're not familiar with using programmer, but you do not need and should not do any of this (You'll loose serial, UUID, MAC ID etc if not done correctly)
[GUIDE] Flash BIOS with CH341A programmer

Well the RAM came cheep - I convinced someone to sell it to me for 10 USD a stick (6 x 32 GB sticks) on eBay. The sticks are Samsung ones and are on the approved list for this mobo. Keep fingers crossed that it will work. Otherwise - I will try to do an RMA with Samsung . I really do not understand why RAM should be so expensive these days. And I have read somewhere that this year the prices are going to get higher (at least in the nVME / SSD market segment) as they say that the demand is greater than the production yield.

Thanks for the CH341 Programming guide link - I will go through it - as I am a curious guy (always want to try something new). Anyway - I am not trying to do SPI programming unless explicitly needed. With the Lenovo I unlocked (with the help of a technician who is providing this service on WhatsApp for a small fee) - I remember now that I have sent him my BIOS image and he have sent me back a properly changed BIOS image - and even after that I had to answer to a randomly generated string with a specific key sequence he provided in order to remove the BIOS Setup password.

Keep up the good work

@fallen2109 - Nice deal then, wow!! I bet the memory are fine, unless you got that deal because user said maybe they are bad?
I know what you mean, always good to learn, and these tools are so cheap everyone should have a set and learn how to use, they can be lifesaver and $$ maker too if you can buy boards you know only have bad BIOS flashed (fix, resell)
Ohh yes, Lenovo password removal can be a painful process sometimes, don't set a new one once you clear it

Hello

For those interested, the latest BIOS 6201 from 31/07/2020 works with cpu50652 and cpu50653 , add the CPU ID and you're good to go. :)

@Airo - Awesome news, thanks for posting Were you able to test the following and those fail, or just unable to test these due to no CPU's >> 50650/50651/50653?
@fallen2109 - This applies to your incoming CPU's ^^ Once Airo replies back about 50650/50651 I will make new BIOS again

@Lost_N_BIOS I only have the 50652 CPUs , but if the 50652 works it would make sense that the 50653 works as well. That's my logic !

@Airo - Well then your logic = my logic and 50650-50653 should all work then (hopefully!)
OK, I will make new BIOS and users can try once again, hopefully it wont be debug 79 FAIL like the update I did on 6102 BIOS here at post #354
---------------------------

@Gurney_ @levelud @maxdata @paranoid_android @mitdal369 @avd @Onyxx1606 @myio @Branen @malucul @Kaboooom2000uk @dahuoxia @TechStream @XeonScalable
@Scotchmist @sochotek @nhan72nn @gloobox @trespasser2 @adhss_phil @SH_LEE @coldwove @lnwlf2k @rulik006 @Funeral_YAR @Irgen @samthekiller @dgjoma @Airo @Babar
@fallen2109 @Bitfan @LordCaedus @bagus

Here is new attempted ES BIOS for you guys based on latest 6201 due to Airo said it's tested OK with 50652, so fingers crossed all others now work again too! - Thanks again for heads up Airo
For now, we only know that 50652 works, all other CPUID's may = debug 79 FAIL or other, you'll have to let us know as you test - thanks!
http://s000.tinyupload.com/index.php?fil...476832636993225

Mirrors - https://ufile.io/2x2hk816
https://www.sendspace.com/file/liretz


Change Log = Add 50650-50653 CPUID - ALL updated to latest versions


Flash via USB Flashback ONLY, this is stock 6201 BIOS modified