What's new

Tutorial HWID Ban: Change UUID and Serial of AMI BIOS Motherboard

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
I posted this here, due to HWID bans happening on Modern Warfare.
Staff feel free to move it to a different section if you desire.

Let me start off by saying follow this tutorial at your own risk. There are programs that can become unusable if they are somehow linked to your SMBIOS data.
Most importantly, your windows activation could deactivate. If you don't have a problem with that, then feel free to continue with the tutorial.

What you need:
  1. USB Drive formatted to Fat32
  2. AMIDEEFIx64 compatible with your motherboard
Step 1: Getting the AMI Utility (AMIDEEFI)
For this you need to know exactly what processor or motherboard you have.
I have a AsRock X470 motherboard flashed with a bios that is compatible with Ryzen 3000.
So from there, I will look up a lenovo computer that has an AsRock motherboard or a Ryzen 3000 CPU.
I searched for "Lenovo Ryzen 3600" and found: ThinkCentre M75s. Next look for the drivers for the computer.
I searched for "ThinkCentre M75s Drivers", it was the first result. Choose Manual Update and Select BIOS/UEFI under Components.
You should get one result found, click on it and you'll see a list of downloads. Like this:



Look for the package that says, "USB drive UEFI BIOS flash package" and download it.
If the computer you are looking at doesn't have that package, you can try the M75s.



Step 2: Format your USB Drive to FAT32
Open the File Explorer and go to "This PC" Right-Click your USB Drive and hit Format.
Choose FAT32 and Hit quick format. It will erase everything that is on the USB Drive.
After the format is complete, place all the files inside the zip you downloaded in Step 1, onto the USB.



Step 3: Booting into EFI Shell
Restart your computer, and press whatever key it is for the Boot Menu, mine is F11.
In the Boot Menu select the USB Drive, if there is two, choose the one that says UEFI.
Press ESC immediately when the message Press ESC in 5 seconds to skip... appears inscreen.
If you are having problems getting to the EFI shell, try searching google for your motherboard and error.

Step 4: Changing UUID and Serial Number.
If you booted into the EFI Shell without any problems you should see: "Shell>" in the console.
Run the command: AMIDEEFIx64.efi /SU /BS (That will display your current values.)
Change the Serial Number with the command: AMIDEEFIx64.efi /BS XXX (Replace XXX with the modified serial)
Change the UUID to all F's with the command: AMIDEEFIx64.efi /SU FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Change the UUID with the command: AMIDEEFIx64.efi /SU XXX (Replace XXX with 32-Hex digit id)
You can also run: AMIDEEFIx64.efi /SU AUTO and it will automatically generate you a new UUID.

Side Note: Did your UUID reset to original?
I'd suggest just using the AUTO command above, as it seems to be the easiest way.
If you restarted your computer and the UUID reset to the original, try following this.
You can check your UUID in CMD with the following command: wmic csproduct get "UUID"
I was able to change my UUID without it reverting using the link above and this version.

Step 5: DOS Version
If the zip file you download doesn't contain "AMIDEEFIx64.efi" and has "AMIDEDOS", follow this.
The process is similar, but instead of formatting the USB Drive to FAT32, you need to download the program called Rufus.
Use Rufus to format the USB Drive, and select FreeDos for the Boot Selection. Leave everything else default.
Extract the files within the zip onto the root of your USB Drive, after you used Rufus.



After that restart windows and press what ever key it is for the Boot Menu.
Choose the USB Drive, if you see both USB: and UEFI: make sure to choose USB.
You should load into the DOS environment and be able to use the console.
Follow Step 4, but replace "AMIDEEFIx64.efi" with "AMIDEDOS.exe"

What you'll need:

Side note:
The version of amide provided is from AptioV. This version worked with my motherboard.
If it doesn't work for you, you'll have to find it from one of the other Aptio versions.

Step 1: Getting the files
Download both files provided. Again the password is my username.
Extract the zip file somewhere on your computer. I recommend putting it on your desktop.
Place the dsefix.exe into the same folder as everything else.

Step 2: Creating a batch file
At this point we need to create a windows batch file to get the driver loaded.
Open notepad and paste the following code inside of it.
Replace <dsefix.exe location> with the real location.
Replace <AMIFLDRV64.sys location> with the real location.
Press File->Save in notepad, choose All Files, save it as "Load.bat", and save it in the same location as everything else.

Code:
start <dsefix.exe location>
timeout /t 3
sc create AMIFLDRV64 binpath=<AMIFLDRV64.sys location> type=kernel
sc start AMIFLDRV64
timeout /t 6
start <dsefix.exe location> -e
timeout /t 3
For example on my computer it would look like this:

Code:
start C:\Users\Grin\Desktop\GRINX64\dsefix.exe
timeout /t 3
sc create AMIFLDRV64 binpath=C:\Users\Grin\Desktop\GRINX64\AMIFLDRV64.sys type=kernel
sc start AMIFLDRV64
timeout /t 6
start C:\Users\Grin\Desktop\GRINX64\dsefix.exe -e
timeout /t 3
Step 3: Disable driver signature enforcement
Restart windows with Driver Signature Enforcement disabled.
  1. Press and hold the Shift key on your keyboard and click the Restart button.
  2. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
  3. When your computer restarts you’ll see a list of options. Press F7 on your keyboard to select Disable driver signature enforcement.

Step 4: Loading the driver
At this point all you need to do is right-click the load file you created, and hit run as administrator.
A command window should open up showing dsefix loading the driver.
Keep an eye out for STATE. If it says Running then you now have the driver running in windows.
If you get any type of error, either your locations in the bat file are incorrect, or windows driver signature enforcement isn't disabled.
Google is your friend when it comes to errors, but feel free to comment and I'll try and help.



Step 5: Changing the uuid and serial
Now that you have the driver running, you can use the program AMIDEWINx64.exe to change your uuid and serial.
Keep in mind that there is no UI included, it is all command line based. That being said, open cmd as administrator.
If you don't know how to do that, simply type cmd in the windows search bar, right-click cmd and hit run as administrator.
Change the location to the folder you have everything in. In my case it would be "C:\Users\Grin\Desktop\GRINX64"
Just type in cd <location> and hit enter, mine would be cd C:\Users\Grin\Desktop\GRINX64

Code:
* /SU  [16 Bytes]    Read/Write system UUID.
* /BS  ["String"]    Read/Write baseboard serial number.

* 16 Bytes            This parameter MUST be 32-digits hexadecimal value.
* String              NULL-Terminated ASCII string.
To get your current uuid, type: AMIDEWINx64.exe /SU
To get your current serial, type: AMIDEWINx64.exe /BS



I recommend saving both of them to a text file, just in case you want to ever change them back.
You can also preform a full dump of everything, with /DUMPALL dump.txt
Once you have your current ids, simply change them to whatever you want.

To change your current uuid, type: AMIDEWINx64.exe /SU XXX (Replace XXX with the id)
To change your current serial, type: AMIDEWINx64.exe /BS XXX (Replace XXX with serial)



Side Note:
The program will display your uuid and serial along with a lower case "h" at the end.
The lower case "h" stands for Hex Values, it is not included in the value, nor do you need to put it when changing the ids.
Your UUID will show something like this: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXh

Step 6: Disabling the driver
After you are finished changing your uuid and serial, it is a good idea to remove the driver from your computer.
Open CMD As Administrator once again, no need to change locations this time.
Type: sc stop AMIFLDRV64 (to stop the driver.)
Type: sc delete AMIFLDRV64 (to delete the driver.)


Things you need:
I found a few more versions you can try. Hopefully one of them works for you.
Run all the batch files as Admin. You still need to disable Driver Signature Enforcement.

What you'll need:
Step 1: Getting the files
Download the file provided and use 7zip to extract the folder to your desktop.
The password is my username.

Step 2: Changing the uuid and serial
Run the application named "DMIEDIT.EXE" as Admin. If you get any errors, your bios isn't compatible with version 5.20.
If the application starts without issue, your uuid is inside "System Information" and your serial is inside "Base Board"





All you have to do is double click each one and change it to whatever you want.
Just make sure you keep the same length as the original id.
After you change them, just press Update/All and it should save.


There you go, now you know how to change the uuid and serial of an AMI BIOS motherboard.

NOTE:
For some reason the UUID change isn't permanent and resets after you restart the computer.
I have been playing on the same account, not knowing about the reset, and I haven't been flagged.
For me, my serial number changed permanently, so that is a good thing.
The safest thing you can do is, change the uuid right before you make a new account and load the game for a first time.
You can also change it back to the same value every time you restart the computer.


Extra Info: Bypassing HWID ban
In this section I will explain what I did to bypass the HWID ban I received on my main account.
While doing research I saw a bunch of different methods and suggestions by people, but this is what worked for me.
I never found, nor took the time, to figure out what the anti-cheat actually logs in regards to your account.
People have said it logs: registry data in windows, unique ids connected to your motherboard, network interface controller, disk drives...etc.
Someone also said that that the game saves tracker files within the installations directory.
It might be a good idea to change the manufacturing serial number of all the disk drives you have installed. I was unable to find a way to do that.
That being said, I in no way shape or form, am claiming to be an expert on this subject,

Here is what I did in the exact order.
  1. Changed the MAC Address of my NIC.
  2. Called my ISP and requested them to change my IP Address. (This might not be required.)
  3. Changed the UUID and Serial of my motherboard. Follow the guide above. (If your ids keep resetting, I would do 3 after 5.)
  4. Completely erased 3 of the 4 disk drives installed in my pc. Yes, I deleted windows off the drive.
  5. Reinstalled windows onto a different drive than previously before. I did not buy a new ssd, I kept the 4 I already had.
  6. When creating a windows account, I used a different name than what I had before the wipe.
  7. Installed Battle.net and Modern Warfare to a different driver than previously before.
  8. Created a new account on both Blizzard and Activision.
I might have went a little over-kill, but you will need to wipe your windows drive and the drive where the game is installed.
It's that simple. Do not, for any reason, log into your banned account after following those steps.
If you do, the anti-cheat will log all of the new information, and your new account will be banned.
 
Last edited:

IwiLLHuRtU

Newbie
Messages
15
Reaction score
0
Just finished and now am fully un-HWID banned! Playing the game and it's great as ever!
 

kikisif346

Newbie
Messages
3
Reaction score
0
Initializing the SMBIOS interface. Please wait a moment......
Error:The size of UUID is too long.
d6 - Error: No OEM Data blocks found in ROM file.

Please Help (Change UUID)
 

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
Initializing the SMBIOS interface. Please wait a moment......
Error:The size of UUID is too long.
d6 - Error: No OEM Data blocks found in ROM file.

Please Help (Change UUID)
This is within the readme.txt file provided:
* /SU [16 Bytes] Read/Write system UUID.
16 Bytes This parameter MUST be 32-digits hexadecimal value.

You are most likely not using 16 bytes. There is a lowercase "h" at the end of your UUID. That stands for "hex values" it is not part of the UUID.
You original UUID could be 78889bc3802b77a251443f02764b2d0a but cmd will show 78889bc3802b77a251443f02764b2d0ah don't include the h.
If you are including the "h" at the end, then the id you are passing to the program is 33-digits long, which is where the issue will be.
 
Last edited:

CallMeAqua

Newbie
Messages
7
Reaction score
0
This is within the readme.txt file provided:
* /SU [16 Bytes] Read/Write system UUID.
16 Bytes This parameter MUST be 32-digits hexadecimal value.

You are most likely not using 16 bytes. There is a lowercase "h" at the end of your UUID. That stands for "hex values" it is not part of the UUID.
You original UUID could be 78889bc3802b77a251443f02764b2d0a but cmd will show 78889bc3802b77a251443f02764b2d0ah don't include the h.
If you are including the "h" at the end, then the id you are passing to the program is 33-digits long, which is where the issue will be.
I'm having the same problem but i did it without the h and it still says Error:The size of UUID is too long, and i checked and it is only 32 digits
 

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
I'm having the same problem but i did it without the h and it still says Error:The size of UUID is too long, and i checked and it is only 32 digits
Can you send me a screenshot of cmd when you get the error in a private message?

Edit: tutorial updated removing “ID=“ from the commands.
 
Last edited:

whiteforlife

Enthusiast
Messages
464
Reaction score
50
When I attempt to to use /SU or /BS I get the error below. Am I doing something wrong or will this method not work on my mobo?
"
Platform checking......
da - Error: System doesn't support.
"
 

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
When I attempt to to use /SU or /BS I get the error below. Am I doing something wrong or will this method not work on my mobo?
"
Platform checking......
da - Error: System doesn't support.
"
Not exactly sure what that error means but most likely it means you aren't on 64 bit windows, or your bios isn't made by AMI, or if it is AMI then it isn't compatible with AptioV.
 

whiteforlife

Enthusiast
Messages
464
Reaction score
50
Not exactly sure what that error means but most likely it means you aren't on 64 bit windows, or your bios isn't made by AMI, or if it is AMI then it isn't compatible with AptioV.
In my sytem info it says Windows 10 64 bit and BIOS is American Megatrends Inc. I will keep trying
 

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
In my sytem info it says Windows 10 64 bit and BIOS is American Megatrends Inc. I will keep trying
If you are on Windows 10 x64 then your motherboard isn't compatible with AptioV. There are other versions like Aptio4 and AMIbios 8.
I was only able to find the version for AptioV. You'll have to look for another version, but the process is still the same.


Also, let me know what motherboard you have, I may be able to help.
 
Last edited:

corey brown

Newbie
Messages
26
Reaction score
1
You know if my motherboard is compatible how do i find out if its AMI?

Gigabyte Z370P D3 LGA 1151 ATX Motherboard
 

GRINSPANKER13

Getting There
Messages
1,011
Reaction score
504
You know if my motherboard is compatible how do i find out if its AMI?

Gigabyte Z370P D3 LGA 1151 ATX Motherboard
Just look up the specs of your motherboard and you’ll see: “Use of licensed AMI UEFI BIOS.” That doesn’t mean its compatible with this version of the program. You’ll have to try and find out that way. I found another version all post after work, maybe that will do the trick.
 

whiteforlife

Enthusiast
Messages
464
Reaction score
50
Just look up the specs of your motherboard and you’ll see: “Use of licensed AMI UEFI BIOS.” That doesn’t mean its compatible with this version of the program. You’ll have to try and find out that way. I found another version all post after work, maybe that will do the trick.
I see, ill try the other method when you get a chance to post. Thanks for the help
 

whiteforlife

Enthusiast
Messages
464
Reaction score
50
Does that mean you tried the current version and it didn’t work?
Originally I got this error

"
Platform checking......
da - Error: System d"

But now I am getting a windows pop up saying that the program is not compatible with my computer.
 
Top Bottom