@MrCjxer the SKTOCC pin is connected to that Nuvoton Super IO chip, that's right. But you have to measure it with a connection check (multimeter). You can not expect the pin somewhere on the base of another mainboard, except it is the exact same model.

When you have verified the location then you can connect it to ground.

I observed when there are no components like small ceramic capacitors or resistors on that Nuvoton SKTOCC pin, then that signal is not used and no shorting to ground is needed. Because SKTOCC is a low active signal ( 0V represents socket occupied ) there is a pull up resistor pulling that signal to a voltage level. Another mod could be to remove that resistor. Soldering skills or someone who can do this for you recommended.

In general there is no need to modify the socket. A simple check where the pin is connected to, makes it way easier to modify. Nearly every mainboard does have a SIO chip, only there SKTOCC is connected.

@reactive - That is not his board, those are Asus motherboard images of Asus SKTOCC mod. If you noticed that, OK
That's what I kept tell him, he has to find on his board or images of his exact model someone posted this mod for (or possibly some other Biostar, maybe). I looked and could not find anything for any BioStar

@MrCjxer - test board without CPU, how does it function and act? Then test with Coffee CPU, if it acts same, then your pads are not connected enough.
CPU solder is no problem to remove once you are done and want to sell CPU, flux chip, wipe off solder connection with clean solder tip (Wedge) and then clean with ALC and you'll never be able to tell it was soldered.

@filippos96 - No CMOS? I doubt that, did you check, it may just need replaced?!?!
Bclk is ME FW controlled, unless your BIOS has option to adjust it, if so then maybe you can get close to 100, but it's generally fluctuating a bit in modern systems.
Your posting here is a confusing, ongoing mess, this is Coffee Mod BIOS thread, do you need Coffee Mod AND unlocked menus?
If you need Coffee mod, tell me your old CPU model and your new CPU SSPEC off top of CPU.

Sorry, that image you linked, I have no idea what you're showing me that for?
If you need some defaults changed also, please give me exact name of settings and what you want them set to, in a list not an image.

@reactive - thank you for your help

@Lost_N_BIOS - thank you too but its done now







and so so so thaaaaank you for help me ...I could not do this without you

@MrCjxer - Awesome to see it's working now!!
Which BIOS did you use, so I can mark it tested/confirmed OK, if it's one I made you.
You're welcome!!!

yeeaah thanks you .

yes i use your mod .
[TOOL] Easy automated Mod tool for Coffee Lake bios (82)

You're welcome! And thanks for confirmation, I'll put a note in that BIOS folder, and on thread for others

Using a modified BIOS image (for non-OEM Windows UEFI-boot) with an MSI Z270-a Pro, the main tool-chain and the resulting BIOS work fine, however x.SyncAllCoreRatio gives me:

SiInit:
Header checksum: 31h, valid
Data checksum: CAh, invalid, should be CEh
Patching successful
Press any key to continue . . .
 

I haven't tried to flash this BIOS (I've only used the one the rest of the chain created) due to the questionable state of the data (as it notes invalid checksum) and resultingly cannot OC the CPU; would this be of concern/would it be safe to flash the BIOS despite that? And/or is there any way to fix that?

@wqco510 - drop BIOS in UEFITool 51-57+ and see if you see same error in parser section at bottom, in the finished mod BIOS. Even if not there, this could still be invalid, I would redo the mod with different tool, or same tool and see if outcome = same error.
I would not use that BIOS as-is now without lots of checking stuff.

With UEFITool A57:
Original unmodified BIOS and the UEFI-modified one both had:

parseIntelMicrocodeHeader: invalid microcode checksum 0BC9B013h, should be 0BC9AEFDh
parsePadFileBody: non-UEFI data found in pad-file
findFitRecursive: FIT table candidate found, but not referenced from the last VTF
findFitRecursive: real FIT table found at physical address FFDF0100h
parseFptRegion: FPT partition is located inside another FPT partition, skipped
 

The UEFI-modified one through the tool-chain (one I've been using fine so far, except CPU OC fails to apply; perhaps noteworthy that I'm using the R0 stepping/generated it as such), as well as the one additionally passed through x.SyncAllCoreRatio (which gave the checksum mismatch report upon generating it), only give:

findFitRecursive: FIT table candidate found, but not referenced from the last VTF
findFitRecursive: real FIT table found at physical address FFDF0100h
parseFptRegion: FPT partition is located inside another FPT partition, skipped
 

Admittedly, I don't really know my way around the actual BIOS structure, etc .. so --
What exactly is x.SyncAllCoreRatio comparing/referring to when it claims the mismatch anyway? Or which part of the BIOS should I take a look at to verify the changes it makes (and what should it look like/could I reasonably change it manually)?

@wqco510 - Sorry, Please compare again side by side with version 51, I forgot 57 shows some odd things, and shows things different, that we don't need to look at here.
And, your post above is confusing anyway, you say top part applies to both, then bottom part only to mod, it looks confusing, show me side by side image of stock and mod with parser tab selected
Also, mention what tool you used to do the CoffeeMod, never heard of "tool-chain" If that is a real tool, give me a link to where you downloaded it and it's support/discussion thread, thanks.

Please tell me your old CPU model, and your new CPU SSPEC/Model and I will make you a BIOS myself using latest BIOS and see if I run into any issues
I do CoffeeTime manually/advanced mode, one by one, DO NOT do microcodes in there - I do that myself manually/outside of tool, then fix FIT as needed.

SyncAllCoreRatio is just as it sounds, make all cores same/same

@Lost_N_BIOS
Sorry for the confusion; in the top one, when I said "UEFI-modified", I meant it had been modified to support the UEFI-boot-OS install (unrelated to the CPU-support thing that I've been applying on top of it now). So for both the original BIOS from the manufacturer and the one with this OS-boot-related mod the output was the top one.

By "tool-chain" I was referring to the chain of tools this thread is about (since it looks like they go in order from 0mecheck.exe to 7Cpu-patch.exe, each passing the intermediary result to the next one, I assume .. so a literal chain of tools).

The bottom output was for the resulting BIOS from AllinOne.exe (no errors while it was doing that), as well as that one passed to x.SyncAllCoreRatio.exe (same UEFITool parsing output for both BIOSes with A57).

With A51:
Top to bottom: unmodified, OS-boot-modded, AllinOne.exe, x.SyncAllCoreRatio.exe

So, similar to A57, but less verbose

---
Hmm, I'm not sure if this sync would help with the type of OC I'm trying to do -- a mild base-clock boost (rather than the multiplier), as it's a non-K (9700F (R0)); anything other than exactly 100, fails to apply (boots at 100 instead, however, any DRAM settings and voltages (including CPU) are still applied though). The previous CPU (7700), also got this problem, once using this BIOS (it applied a slight boost (up to 102.69) fine prior to applying the AllinOne).

@wqco510 - Please do side-by-side, top/bottom is hard to compare (and there should only be two comparison/BIOS open side by side, not four). I went ahead and look, bottom BIOS is not good (BOTH), do not flash (see the missing Non-UEFI-Pad file, this often causes brick)
OK, for your first discussed mod, about UEFI Boot, is that tested and booting/working? If yes, leave that out of this discussion, it adds to the pile unnecessarily. If that is not tested, by itself already, do that now.

This thread is about one tool, Revlaay's AIO Tool, and for that only ONE SINGLE EXE is used to do the coffeemod. You are not supposed to use anything other than the ALLInOne.exe, drop BIOS on that to modify.
So, summary as I see it here, BIOS in image #3 is proper BIOS modified by Revelaays AIO Tool, but may (read probably) = brick. So you need new proper BIOS.

Please link me to the BIOS download page (not BIOS) you want modified, and tell me your old CPU model, and your new CPU SSPEC or CPUID if you already know it (If 9700F (R0), OK, tell me that + old + BIOS download page when you reply)

Modern CPU's can't Bclk overclock, maybe to 102 as you mentioned, but all may not be able to do that.. So you already have booted and working 9700F? If yes, then what are these posts about if you already have working BIOS?
To answer your last question, NO, coresync has nothing to do with Bclk.

Sounds like broken BIOS, as I mentioned, but at least it didn't brick on you. How are you flashing in the mod BIOS, via Programmer, or already unlocked FD and using FPT?
Is your FD Unlocked? If not, how did you flash in the mod ME and mod FD? Both need flashed in, at very least mod ME FW, even if your original ME FW was old enough version to be compatible still mod one needs flashed in.

Zitat von Lost_N_BIOS im Beitrag #1242

---

OK, for your first discussed mod, about UEFI Boot, is that tested and booting/working?

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

bottom BIOS is not good (BOTH), do not flash (see the missing Non-UEFI-Pad file, this often causes brick)

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

there should only be two comparison/BIOS open side by side, not four

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

This thread is about one tool, Revlaay\'s AIO Tool, and for that only ONE SINGLE EXE is used to do the coffeemod. You are not supposed to use anything other than the ALLInOne.exe, drop BIOS on that to modify.
So, summary as I see it here, BIOS in image #3 is proper BIOS modified by Revelaays AIO Tool, but may (read probably) = brick. So you need new proper BIOS.

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

Modern CPU\'s can\'t Bclk overclock, maybe to 102 as you mentioned, but all may not be able to do that..

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

How are you flashing in the mod BIOS

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

or already unlocked FD and using FPT?
Is your FD Unlocked? If not, how did you flash in the mod ME and mod FD? Both need flashed in, at very least mod ME FW, even if your original ME FW was old enough version to be compatible still mod one needs flashed in.

---

Zitat von Lost_N_BIOS im Beitrag #1242

---

Please link me to the BIOS download page (not BIOS) you want modified

---

@wqco510 - Still talking image from 1241 here >> Bottom two are the ones missing "Non-UEFI-Pad file", unless you're looking at some other image than the one you posted above for me to look at?
Original MSI (Top BIOS #1, top-most) is NOT missing the Non-UEFI-Pad file, #1-2 are the ONLY ones WITH the non-UEFI pad file. Only the bottom two are missing this, as I mentioned above. Sorry, not sure how that is confusing??

This >> x.SyncAllCoreRatio.exe Toss, for two reasons, one it's missing Non-UEFI Pad file, and two, you are not supposed to use those tools in this manner.

AIO (#3 in original image) is the only valid "Coffee Mod" BIOS here, but as mentioned, it may brick, due to missing non-UEFI Pad file (and may have other issues we've not discussed, I can't tell I do not have BIOS to check)
If you are using AIO BIOS right now (#3 in image from post #1241) then you're all good, well, bootable at least. But both those issues, and some I may find but can't see from just an UEFITool image, may be what's causing the current issues you describe
That and or other issues with your AIO BIOS (Such as padding added/removed that are not mentioned in "parser), not sure, I have not looked at the BIOS. But from what I can see in the images above I would still suggest NOT using that BIOS, and to make a properly edited Coffee BIOS.

Send me the BIOS in PM then if you don't want to link it, otherwise explain what "UEFI Boot" change you need, and I can do that on stock BIOS for you and create a proper coffee mod BIOS for you.

Checksum of modules will change sometimes if you edit them, SyncAllCoreRatio is already done to the BIOS you are using, since you used AIO.exe,
This tool calls ALL the other tools in that folder as it does it's thing, that's the only way those other tools are meant to be used.

Oh wow, I misunderstood/-read the UEFI pad-file part, sorry

I assumed AIO to not already do x.SyncAllCoreRatio.exe since the opening post said:

Zitat von revlaay im Beitrag #1

---

Double click "AllinOne.exe" and select your bios for mod, or drag your bios on AllinOne.exe to execute.
If you have K processor, drag bios on "x.SyncAllCoreRatio.exe" to enable OC function properly.

---