Prebuilt [SFFn] ASRock's DeskMini A300 - Finally!

ToraSapphire

Case Bender
New User
Nov 27, 2024
2
1
has anyone been able to flash an A300M-STX back to the A300 BIOS after crossflashing an X300M-STX BIOS? I'm not able to do so using the MSI utility I used before because I get a secure boot violation error, and changing any BIOS settings causes a soft brick where I have to unplug the CMOS battery to reset it. I have a 4700G in mine and went from A300 BIOS 3.60S to X300 BIOS 2.00.
I figured it out: I had to downgrade from X300M-STX P2.00 to P1.70 to disable Secure Boot, and then use the MSI utility to re-flash A300M-STX P3.60S. Took several hours of brainstorming to come up with that idea. It's super un-intuitive, but it worked for me.
 
  • Like
Reactions: Phuncz

HyphenK

Efficiency Noob
Dec 17, 2024
6
1
Hello everyone.
My 5600g+A300 with 3.70E BIOS does not fully work - it could enter BIOS setting but was unable to enter Ubuntu.
I had to downgrade to 3400g and now it works fine with 3.70E.
I need some advice from anyone installed 3.70E.
 

HyphenK

Efficiency Noob
Dec 17, 2024
6
1
So it doesnt save the settings anymore? CMOS battery gone kaputt?

cu, w0lf.
yeah I can't.
If I boot without CMOS clearing, the A300 cannot find any boot disc, so it keeps looping in the BIOS. The only way to resolve is CMOS clearing, and it boots normally just one time. Another reboot then stuck again. I can't understand why this thing is happening...
 

HyphenK

Efficiency Noob
Dec 17, 2024
6
1
yeah I can't.
If I boot without CMOS clearing, the A300 cannot find any boot disc, so it keeps looping in the BIOS. The only way to resolve is CMOS clearing, and it boots normally just one time. Another reboot then stuck again. I can't understand why this thing is happening...
and it seems it is not a cmos battery problem, since i didnt have any problem before updating to p1.70 and 5600g, and i heard nothing about relationships between broken cmos battery and non-detected boot disc
 

hrh_ginsterbusch

King of Cable Management
Silver Supporter
Nov 18, 2021
783
306
wp-devil.com
and it seems it is not a cmos battery problem, since i didnt have any problem before updating to p1.70 and 5600g, and i heard nothing about relationships between broken cmos battery and non-detected boot disc
if it doesn't save the settings / starw, then the boot disk disappears after reboot. and not being able to save the state, aside of some bios bug, could also point to a hw problem. hence CMOS battery as the easiest option.
 

HyphenK

Efficiency Noob
Dec 17, 2024
6
1
if it doesn't save the settings / starw, then the boot disk disappears after reboot. and not being able to save the state, aside of some bios bug, could also point to a hw problem. hence CMOS battery as the easiest option.
maybe i need to re-flash p1.70 or flash p1.90 again... i'll try it later
 

HyphenK

Efficiency Noob
Dec 17, 2024
6
1
so the second try... this time i used p1.90 and it didn't resolve the error, but i found that this is caused by not properly flashed bios. it kept fail to pass the validity check. maybe i need to try instant flash, or buy another ch341a or bios chip?
 

Dr. Nick

Trash Compacter
Sep 2, 2024
48
42
so the second try... this time i used p1.90 and it didn't resolve the error, but i found that this is caused by not properly flashed bios. it kept fail to pass the validity check. maybe i need to try instant flash, or buy another ch341a or bios chip?
Did you try to re-flash P1.90 via "Instant Flash" in BIOS?
 

Figl

Case Bender
New User
Jan 3, 2023
2
0
I can confirm that the firmware from x300 is the source of the problem with starting after saving the cmos settings. I tried flashing it back in 2023 with ch341 and xgecu t48. These are not just problems with starting. If you measure the voltage on the capacitors in the power circuits at this point, they will be very different from normal. This problem will persist even if you update the bios later via instant flash. I also found that if you do not enter the bios, there will be no problems. I think that the bios from x300 is configured to save data in cmos differently. Or there is an incompatibility of the knoll activator chip firmware