Flashed an R9 270X with a potentially malicious BIOS and now it doesn't get picked up by amdvbflash

[YourAverageGamer]

Basically, I was testing some BIOS mods for the GPU as it had artifacting and crashed, so I made a BIOS mod that got it stable by disabling half of the VRAM, however I was trying everything to get 7 chips usable instead of just 4, as 1GB is quite constraining. That's when I came across an ASUS 3GB vBIOS which got me curious since it likely used some weird arrangement that could've been useful, so there I went flashing it and got no display, but that was no biggie as that had happened before and I had another GPU plugged in to make flashing again possible, but it just wasn't popping up on amdvbflash (tried DOS, Linux, UEFI and some Windows versions). The most amount of success I got was on Windows with version 5.0.567 where it appeared but said that BIOS operations weren't supported. After troubleshooting lots I found out that the GPU was showing up as a 1002 6F98, which is the wrong ID and doesn't match any AMD GPU model, and that's likely why it isn't appearing properly. Is there any way to perhaps spoof the ID to the correct 6810 to get it to at least flash the card? Also, it pops up under Linux too and it picks up the Audio driver, but the GPU is still with that weird 6F98 ID.
Here's what pops up in Windows version 5.0.567

Here's what appears in every other version

Lastly here's GPU-Z

Also just realized the RAM module config is wrong as mine has Hynix modules.