Dead Gigabyte Aorus B450 M Mobo. Apparently.

[bythecantloads]

Heyo!

Board in question: B450 AORUS M (rev. 1.x) Gallery | Motherboard - GIGABYTE Global

So just wandering what to do in this instance... I sold a B450 mobo to a forum member on the 16th of July 2021 and stated in my ad that I would give 7 days to test. So this kid was going to use it with a 2700x, which turned out to be DOA and he swapped it out for a 3600. Now he needed a BIOS update for the new CPU, which I told him that I could not help with. Offered to post a help thread on the forum, but I didn't get any feedback. He then decided to take the update in his own hands.

Yesterday (24/08/2021), the kid sends a messages stating the board is dead and he wants a refund. He took the board to two seperate shops and they could not get it to post or even boot to BIOS. They apparently tried different CPUs and different sets of RAM as well. Now look. I am not a doos and my standing on Carb is worth much more than this mobo, so I do the refund no questions asked. I also have a funny feeling that the kid isn't being completely truthful. The board was working in my dad's rig and was replaced because the LAN port no longer worked.

Here is the question, would I be able to tell if a botched flash bricked the board? Would I be able to bring a bricked board back to life?

I have reached out to a member for assistance when I get the board back. Just wondering what to do if the board is fried due as a result of this kid's doing...

 

[orange_jo0se]

Heyo!

So just wandering what to do in this instance... I sold a B450 mobo to a forum member on the 16th of July 2021 and stated in my ad that I would give 7 days to test. So this kid was going to use it with a 2700x, which turned out to be DOA and he swapped it out for a 3600. Now he needed a BIOS update for the new CPU, which I told him that I could not help with. Offered to post a help thread on the forum, but I didn't get any feedback. He then decided to take the update in his own hands.

Yesterday (24/08/2021), the kid sends a messages stating the board is dead and he wants a refund. He took the board to two seperate shops and they could not get it to post or even boot to BIOS. They apparently tried different CPUs and different sets of RAM as well. Now look. I am not a doos and my standing on Carb is worth much more than this mobo, so I do the refund no questions asked. I also have a funny feeling that the kid isn't being completely truthful. The board was working in my dad's rig and was replaced because the LAN port no longer worked.

Here is the question, would I be able to tell if a botched flash bricked the board? Would I be able to bring a bricked board back to life?

I have reached out to a member for assistance when I get the board back. Just wondering what to do if the board is fried due as a result of this kid's doing...

exact board model would help, some boards have built in protection for scenarios like these

 

[bythecantloads]

exact board model would help, some boards have built in protection for scenarios like these

Thanks. Updated title with link to mobo as well.

 

[TheJudge]

Looks like it has dual bios.

 

[TheJudge]

Also, I see the BIOS updates have one of those special updates (F40) that specify you have to follow the instructions properly to go past that. Remember a YouTube video where someone bricked their mobo because of that but can't remember what model it was.

 

[orange_jo0se]

@bythecantloads Check the below video, i couldn't watch it as im at work 👀

But scrolling through the comments it seems this dude managed to fix his. Don't know if it'll apply to your case though, like i said, i couldn't watch it.

 

[bythecantloads]

Also, I see the BIOS updates have one of those special updates (F40) that specify you have to follow the instructions properly to go past that. Remember a YouTube video where someone bricked their mobo because of that but can't remember what model it was.

Mmmm... If this is the case it would be annoying AF.

@bythecantloads Check the below video, i couldn't watch it as im at work 👀

But scrolling through the comments it seems this dude managed to fix his. Don't know if it'll apply to your case though, like i said, i couldn't watch it.

Thanks. Will check it out tonight. Picking up the board likely tomorrow.

 

[Techfox]

Mm, no experience with said F40 related brickage, but usually the DualBIOS will kick in automatically should it detect the main BIOS being botched/corrupt

Had a few botched ones, and even (don't even ask how) a B550 that somehow had a B450 BIOS update to it. It usually kicks in, and you'll be able to use Q-Flash to overwrite the borked one

Tried checking for some sort of paper trail though, but doesn't seem to log anything. You'll be able to see what the current version is though

* Edit for typos

 

[𝐹𝓇𝒾𝓀𝓀𝒾𝑒𝒮𝓌𝒶𝑔]

Mm, no experience with said F40 related brickage, but usually the DualBIOS will kick in automatically should it detect the main BIOS being botched/corrupt

Had a few botched ones, and even (don't even ask how) a B550 that somehow had a B450 BIOS update to it. It usually kicks in, and you'll be able to use Q-Flash to overwrite the borked one

Tried checking for some sort of paper trail though, but doesn't seem to log anything. You'll be able to see what the current version is though

* Edit for typos

On an unrelated topic - Your website looks sick

 

[mujeeb1]

On an unrelated topic - Your website looks sick

Agreed, how I became a customer

 

[Switch]

Heyo!

Board in question: B450 AORUS M (rev. 1.x) Gallery | Motherboard - GIGABYTE Global

So just wandering what to do in this instance... I sold a B450 mobo to a forum member on the 16th of July 2021 and stated in my ad that I would give 7 days to test. So this kid was going to use it with a 2700x, which turned out to be DOA and he swapped it out for a 3600. Now he needed a BIOS update for the new CPU, which I told him that I could not help with. Offered to post a help thread on the forum, but I didn't get any feedback. He then decided to take the update in his own hands.

Yesterday (24/08/2021), the kid sends a messages stating the board is dead and he wants a refund. He took the board to two seperate shops and they could not get it to post or even boot to BIOS. They apparently tried different CPUs and different sets of RAM as well. Now look. I am not a doos and my standing on Carb is worth much more than this mobo, so I do the refund no questions asked. I also have a funny feeling that the kid isn't being completely truthful. The board was working in my dad's rig and was replaced because the LAN port no longer worked.

Here is the question, would I be able to tell if a botched flash bricked the board? Would I be able to bring a bricked board back to life?

I have reached out to a member for assistance when I get the board back. Just wondering what to do if the board is fried due as a result of this kid's doing...

Follow the following if gigabyte hasn't made any changes to their dual bios system:

How to force Gigabyte motherboard to boot in the backup bios by shorting pins on the bios chip?

I have a bios update for my motherboard on the Gigabyte website and flashed it using qflash (because I had problems with my old bios). After the update reached 100% my pc turned off automatically,...

superuser.com

Some consumer boards have a bios events log system, but such logging functionality is very uncommon if not rare (usually only found on enterprise hardware, specifically mid tier to high performance). You probably won't be able to find out if the user borked the bios update process.

 

[Techfox]

On an unrelated topic - Your website looks sick

gracias ❤️

 

[bythecantloads]

And just an update for all.

Picked up the board on Friday. The mother expressed her gratitude that I did a refund.

Took the board to @PC Rescue. Spent a lovely time testing the board and an even better time having a chat. Unfortunately he didn't have the right CPU on hand to get in to the bios.

Now at home popped in the CPU that used to be in the board 2600X and booted straight to the BIOS.

Had to update to F32, then to F40 and then F60 for the support of 5000 series CPUs.

Thanks to everyone's input.

 

[LunaFox]

Wish I could've done more

 

[Toy Machine]

And just an update for all.

Picked up the board on Friday. The mother expressed her gratitude that I did a refund.

Took the board to @PC Rescue. Spent a lovely time testing the board and an even better time having a chat. Unfortunately he didn't have the right CPU on hand to get in to the bios.

Now at home popped in the CPU that used to be in the board 2600X and booted straight to the BIOS.

Had to update to F32, then to F40 and then F60 for the support of 5000 series CPUs.

Thanks to everyone's input.

Question in regards to why you did each BIOS update individually, do the latest releases not contain the previous version features?

i.e. F10 introduces AGESA, F15 introduces 5000 support

If I just go straight to F15 would that not introduce the AGESA update?

Asking because I did exactly this as my mobo [Gigabyte B550i] was on F1 & I went straight to F15 and I've had my wireless keyboard disconnect after the update which I can only really derive being the AGESA disconnecting problem AM4 had on release

 

[bythecantloads]

Wish I could've done more

You already did the most and once again thank you for it.

Question in regards to why you did each BIOS update individually, do the latest releases not contain the previous version features?

i.e. F10 introduces AGESA, F15 introduces 5000 support

If I just go straight to F15 would that not introduce the AGESA update?

Asking because I did exactly this as my mobo [Gigabyte B550i] was on F1 & I went straight to F15 and I've had my wireless keyboard disconnect after the update which I can only really derive being the AGESA disconnecting problem AM4 had on release

So Gigabyte themselves are saying that before you do F60, you need to F40 and F40 requires the F32 update. So I guess it wasn't all cumulative updates, which is fine.

I think that if there are no notes from the manufacturer it's fine to update to the latest without having support problems.

Just found out that the guy that bought the board from me, took it to Titan Ice. Not reflecting well on them to be honest.

 

[Toy Machine]

So Gigabyte themselves are saying that before you do F60, you need to F40 and F40 requires the F32 update. So I guess it wasn't all cumulative updates, which is fine.

I think that if there are no notes from the manufacturer it's fine to update to the latest without having support problems.

Just found out that the guy that bought the board from me, took it to Titan Ice. Not reflecting well on them to be honest.

I see, they don't particularly say they are cumulative for my mobo & the latest revisions are noted for 5000series support rather than 3000, with a 3000 series update being an earlier revision. So might be worth it for me to do that rev update just to be safe.