AVM HWID SPOOFER TEST OTG

AVM spoofer software does not work for OTG (OffTheGrid). i am sure of this because i tested AVM Spoofer like this;

1- Windows Format (yes i did a deep clean, i wiped all disk partitions to delete all track files and did a fresh install again).

2- i reinstalled fully all my windows using ExpressVPN (I use static ip with my internet provider so that my ip changes every time i reset my modem)

3- I installed AVM spoofer and used the VIRTUSULATION setting and restarted my computer. Then i used the ghosta option (as they wrote in their EAC guide) then i checked that my HWID was hidden by entering the “WMIC DISKDRIVE GET SERIALNUMBER” command in cmd.

4- I created a new steam account by setting up a new email from the new ip and downloaded the game.

5- i entered the game using a reliable cheat software and waited in the main menu for 40 minutes and got banned, so i made sure that my HWID ban was not resolved.

+ When i asked their dc support, he said me “trust my words, not what is written on the site” thats important cuz on theır discord they dont say anythıng about we can spoof OTG, but at the end of the day i was still banned. (proof p1.1/1.2/1.3)

+ the administrator on discord said that he would offer me a solution because he was in bed right now, but it has been 2 days and he has not offered any support, in short, EAC is not that easy for you, new games use special tracking systems. (proof 1/2/3/4/5/6)

+ I am sure that the program does not work for the following reason i play the game on my second computer with the same cheat and I have more than +110 hours of game time and i have not been banned, so they cannot tell me that the program you are using has been detected. (proof7)

+ ı checked their SPOOFER on EFT/FORTNITE/RUST too, on this three games spoofer works well, ı afk tested on lobby for 20 hours on eft / 5 hours playın of rust and / played 3 matchs ın fortnite with reliable cheats and not get banned so on on these 3 games SPOOFER solves the TRACKING FILES for EAC for these games but OTG ıs a really new game and theır devs and EAC uses specific new tracking methods and this AVM cant solve the issue on OTG

+ i didnt tested but too many people on elitepvpers forums says AVM doesnt work for valo too.

so for 50bucks ıts not that good enough. but ıts stıll buyable

p1.1 [Only registered and activated users can see links. Click Here To Register...]
p1.2 [Only registered and activated users can see links. Click Here To Register...]
p1.3 [Only registered and activated users can see links. Click Here To Register...]
p1 [Only registered and activated users can see links. Click Here To Register...]
p2 [Only registered and activated users can see links. Click Here To Register...]
p3 [Only registered and activated users can see links. Click Here To Register...]
p4 [Only registered and activated users can see links. Click Here To Register...]
p5 [Only registered and activated users can see links. Click Here To Register...]
p6 [Only registered and activated users can see links. Click Here To Register...]
p7 [Only registered and activated users can see links. Click Here To Register...]

I can also confirm AVM causes serious issues on the system side, not just detection issues.

I tested AVM recently and while it does change identifiers like disk ID, motherboard ID, BIOS ID and MAC address, it ended up corrupting my system’s hardware query system after multiple spoof attempts.

After using the spoofer several times, my hardware identifiers started returning NULL values. My MAC address, disk serial, and system UUID were no longer readable through normal Windows queries.

Even basic commands like:

wmic nic get MACAddress,Name

started returning “Invalid namespace”.

For anyone technical, that error means the WMI repository (Windows Management Instrumentation) was corrupted. That repository is what Windows uses to query hardware identifiers.

I had to manually repair my system by resetting the WMI repository and recompiling MOF classes just to restore normal hardware detection. This is not something users should have to do after using a spoofer.

What makes it worse is that this issue appeared immediately after using AVM and it interfered with other spoofers as well. I normally use reported.lol and have never had this problem before, but after running AVM it broke my ability to spoof properly until I repaired WMI.

So while AVM technically changes some identifiers, the implementation seems unstable and can damage the system’s hardware query environment.

For a $50 lifetime spoofer it might seem attractive, but people should be aware of the potential system corruption issues that can happen after repeated use.

Personally I would rather pay more for a stable solution than deal with repairing Windows internals every time I spoof.