Ket i use HackBGRT-1.5.0 on my taichi, it changes the windows bootloader image instead of the bios which is much safer, this will work on any ryzen board with a uefi install
Theres zero risk in changing the boot image in the firmware itself. You can do it with UEFI Tool, MMTool, or AMI Change Logo. Just look for "Logo.bmp", and replace it with whatever image you want. I tend to use AMI Change Logo so I can insert jpg images which saves space in the rom image for other things.
You can do it with UEFI Tool, MMTool, or AMI Change Logo. Just look for "Logo.bmp" or if using AMI Change Logo itās "Splash Logo - Default". Using AMI Change Logo is the best way to do it as you can insert other image formats for the splash screen not just .bmp files.
In a seperate news post folks after extended testing of both F22b and F22 firmwares for X370 and B350 boards I have concluded they are both utter crap. I am currently testing F21 which thus far seems about as good as F5a/F7a/F9f for their respective boards. Iām going to cook up a modded F21 for the K5 next which hopefully @JSebastian can test.
As a point of interest what kind of firmware are people primarily looking for? At the moment Iām exposing any option I think some people might find useful as well as applying tweaks / fixes / workarounds. Tell me what settings you often dig around in or find useful to have there and Iāll trim away the stuff people donāt use.
Canāt find where to change p-states in Gaming 5 F9fM-D bios. That would be a nice addition as good bug, odd multiplier clockdown, does not seem to happen. Or well, maybe the read out is off in hwinfo64: at idle all cores are reported full speed, load some cores and some others seem to downclock.
Canāt find where to change p-states in Gaming 5 F9fM-D bios. That would be a nice addition as good bug, odd multiplier clockdown, does not seem to happen. Or well, maybe the read out is off in hwinfo64: at idle all cores are reported full speed, load some cores and some others seem to downclock.
Thats part of the AMD CBS menu, its locked by default in F9f but unlocked from F10 onward afaik. Iām working on an F21 modded firmware atm as F22b and F22 are total gabage GB really (for lack of a better way to adequately describe it) fucked those up in numerous ways. F22b isnāt as bad as F22, but both of them are overall crap. F21 so far seemsā¦ adequate. Are you able to test the GOP issue reported on your Gaming 5 and let me know if its broken or not? Be good to have feedback on both the K5 and G5 itāll be pretty solid then that all F21 firmwares are good in that regard at least.
Alright guys, the warning is coming in early. If improvements / bug fixes the Aorus X470 line get do not trickly down to the X370 boards at least a month or so after launch Iām not wasting my time any further on Gigabytes garbage it would take me too long to rip things apart fully to really start to correct problems. My advice; Just avoid anything Gigabyte branded, particularly when it comes to motherboards.
Alright everyone Iāve finished testing F21 (donāt worry B350 owners waiting on older modded firmware Iāve not forgotten about you) and here is what I can tell you for those who only want a short read; Iāll be making modded firmware around it. Itās not perfect, and there is certainly plenty to be desired about it, but itās not totally crap either cough Iām looking at you F22 cough. For those wanting a longer read;
The Good:
Polling rate for voltage readings is good
Mouse sensitivity isā¦ passable. Still a pain in the arse when trying to use the colour wheel in the UEFI but in general itās not as bad.
Memory overclocking is decent, reaching 3466MHz.
What options there are by default seem to all be working without issue for a change
Vcore voltage readings at long bloody last have been recalibrated it seems. Tested with āNormalā Vcore settings on a CPU with 1.225v VID, set offset to +0.1v, readings come back as 1.296v - 1.32v. Average 1.308v. Thats about right.
HPET isnāt broken
Saved profiles appear to be storing data correctly (tested via saving to usb drive and loading)
The Bad:
No CLDO_VDDP option, MIA since F9f.
No BankGroupSwap option, MIA since F9f
No BankGroupSwapAlt option
Still a massive amount of options not exposed to the user such as Spread Spectrum, Timer Tick, or options to disable SATA slumber state
Some LED colour presets are of course still not fixed
Still the same bugs Iāve been using workarounds to overcome for over a year
SPD readout in the UEFI is still hilariously badly broken.
UEFI UI design is still bastard fugly. Considering I think most would agree this would beā¦ say 70% resolved just by placing a large version of the falcon logo in the bottom left instead of that nasty blank black background its almost beggars belife this hasnāt been done yet.
I forgot to test the memory dividers. SIX of those negatives at least would be quick and easy to fix for GB. I would offer some praise to GB if it were not for the fact it is plain as day to tell F21 is an accident / fluke rather than an obvious concerted effort from GB to fix their mess. 4-5 of those negatives Iāll look in to fixing myself, it wonāt be as neat and tidy where I donāt have the same tools GB have to do it easily, but I can likely resolve them all the same.
Hello,
While I was searching for new drivers I found out this recent version of Realtek drivers that are compatible: Realtek High Definition Audio (HDA) R2.8x (8403) WHQL + Dolby : http://www.station-drivers.com/index.phpā¦derby=4&lang=en
I tested and works with Sound Blaster X-Fi MB5 1.00.19.
Oh, I wasnāt worried. 
Iād already read all the news and watched multiple videos on the subject, including AdoredTVās. It was pretty obvious from the start that the CTS-Labs and Viceroy Research reports were Intel funded hit pieces. Of course, thereās no concrete proof of that; but the fact that a lot of Intel motherboards also use the same ASMedia chips Ryzen mobos do, and this was never mentioned anywhere in those reports, is very telling.
Hey, thatās great! Glad to see youāve settled on a BIOS that supports Pinnacle Ridge aka Ryzen 2000 series.
While I personally wonāt be upgrading my 1700 CPU (not enough of a performance increase in any of the new models to justify the cost), at least thereās the opportunity to continue using your modded BIOSes in the future if I change my mind. I look forward to a new modded release based on F21.
I do have one request, though!
It seems that the boot logo bitmap is where the text is, that shows what keys you can press during boot. When you replace the logo with your own custom one, that text goes missing. It would be nice if you could copy the text from the bottom of the original logo and add it your yours?
Oh, I wasnāt worried. Iād already read all the news and watched multiple videos on the subject, including AdoredTVās. It was pretty obvious from the start that the CTS-Labs and Viceroy Research reports were Intel funded hit pieces. Of course, thereās no concrete proof of that; but the fact that a lot of Intel motherboards also use the same ASMedia chips Ryzen mobos do, and this was never mentioned anywhere in those reports, is very telling.
Hey, thatās great! Glad to see youāve settled on a BIOS that supports Pinnacle Ridge aka Ryzen 2000 series.
While I personally wonāt be upgrading my 1700 CPU (not enough of a performance increase in any of the new models to justify the cost), at least thereās the opportunity to continue using your modded BIOSes in the future if I change my mind. I look forward to a new modded release based on F21.
I do have one request, though!
It seems that the boot logo bitmap is where the text is, that shows what keys you can press during boot. When you replace the logo with your own custom one, that text goes missing. It would be nice if you could copy the text from the bottom of the original logo and add it your yours?
That is very odd I donāt have that problem with the modded firmware I use on the test Gaming 5. Iāll be sure to pay close attention to it though with the next round of modded firmware to ensure the boot logo isnāt disgusing the text but afaik the text is actually an overlay of the boot logo itself so it shouldnāt just disappear. Now Iāve navigated the minefield that is the F2x firmware versions Iām pretty confident I can make some modded firmware around F22b instead of F21 I worked out where all the bugs are and can circumvent them.
Grabbed the driver from softpedia, Iāll mod it when I get a chance.
+1
Ive successfully managed to put 5 of my friends off from buying the last stocks of these pieces of crap, and the rest that do own them have had nothing but problems (captain obvious) these boards are certifiable nightmares. In a nutshell, they are fucking garbage.
New Realtek driver is up. Old modded firmware for the B350 boards is also up. First new firmware based on F22b is up for the Gaming 5.
If ever there was a reason to not buy a GB motherboard gents I think we have a winner here. GB may have replaced the board but VRMs blowing out should not be happening. Period. Whos to say other untold damage wasnāt done to the other hardware as well.
CLDO_VDDP is āhidden in plain sightā under the VDDP offset in the voltage menu. For reasons unknown the increments are 0.020V where Iād prefer 0.010V - Iāve just bumped mine +0.060V and it added just that. And now Iām going to re-try all of my RAM timings from the top. I managed to increase read speed 48300-48500MB/s at 3400Mhz CL16 to 53600-53800Mb/s at 3466Mhz CL14 booting into Windows without problems but not entirely stable.
Iām still on F21 cuz I wants my RGB, lol.
@ket
I understand your point. Itās not fair to have anyone not associated with the manufacturer fixing their software ā¦ unless they end up sending you a big, fat check. Youāre still doing a great job, dude. Really appreciate it.
I can only be (kind of) grateful I got my MB at a sale, almost ā¬45 under MSRP. If I want RGB to work properly Iāll get a Morpheus and RGB fans for my GFX, add LED-strips and blah-blah-blah.
Thats a common misconception, CPU VDDP is not the same as CLDO_VDDP. The former only changes the external voltage on the CPU pins where the latter is the DDR4 PHY on the SoC which is primarily used to move or resolve memory holes allowing for previously unstable memory overclocks to become stable 
Thatās what I get for trying to sound smart rather than ask the right question. 
What is the useful function of CPU VDDP, then? I (seem to) get fewer errors in memtest after Iāve raised it. (3466Mhz would pop error upon error upon etc. within 30sec at 0,900V but at 0,980V itās one every 15-30min)
I wonder if the guys at GB have confused the two?
CPU VDDP is for all intents and purposes AMDs version of VCCSA. In other words it raises the voltage for the IMC. CLDO_VDDP alters what is known as a sine wave that has equal values at the crest (+) and trough (-). Eg; +0.35v to -0.35v. A simpler way to look at it is CPU VDDP is the overclockers hammer, while CLDO_VDDP is an overclockers scalpel GB might well be confusing the two but if they are you should really be very worried as both are similar in regards to their ultimate goal but both function entirely differently so if GB are confusing the two it only demonstrates their severe lack of technical understanding and as such they should not be in the business of manufacturing motherboards and attempting to (badly) write firmware to go with them. Iād be more inclined to simply think itās lazy firmware coding though as the CLDO_VDDP option is still present in AMDs code as of F22b, didnāt check the "final" F22 version as its such a buggy mess.
I agree once againā¦ Thx to this GB K5 it seems to have also messed up the SPD for one of the FlareX sticks!!! Itās being detected as an "Unknown NVM" instead of SDRAM UDIMM Module like it used to & like the second stick is correctly detectedā¦ GB says its G.Skillās fault and to RMA my RAMā¦ LOL!!! Iām sending them screenshots of my previous TridentZ 3000 set along with screenshots of these FlareX with both stickās SPD intactā¦ Of coarse this was just prior to their F10 Beta firmware that messed everything upā¦ Kinda leaning towards an ASUS Crosshair Hero VI if GB doesnāt get on the F*****g ballā¦
That is a weird issueā¦ you might want to flash to a very old firmware then flash up to F21, doing so will force a complete erase and reprogramming rather than just an "upgrade". Migh iron out a few things for you.
Gaming K7 F22b modded firmware is up.