95% of the webui update has been completed, and now it is time to update the tweaks.

Features such as DPI per app and many others are awaiting implementation. Additionally, features like show fps, optimization menu, and game turbo will soon be added to COPG in the future.

Newer spoofing methods and app bypass techniques are also in the pipeline, and of course, Play Integrity fix and many other features will be added, turning COPG into a super module.

Chinese, Arabic, Persian, and Spanish languages will also be added in the next update.

Trying to reverse engineer a module to see what device it uses, then I will add it to the COPG. I don't know why they hide their code so hard and don't like to let people know about it! Anyways, he also uses the COPG method to unlock 120 fps on Asphalt.

The module was successfully hacked.

It took me so long to hack. You can't make your module immune to hacking; you're just making it harder/longer for me to hack.

The new update of COPG will also include proper Asphalt 120 FPS support.

Anyways, let's move on. I love the new web UI.

Claude Code 4.8 has been added as a second developer to the COPG development team officially.

Creating a module and tool for you with an insignificant amount is accepted.

Are you using unlimited google photos by COPG?
I'm planning to drop it

Ok, now COPG is the first-ever Zygisk module which can spoof AndroidID/SSAID per app.
I guess? Now no one can ban your device in games no reboot needed at all


Will be added very soon

I hope other modules give credit when they use my code

I'm not playing freefire btw

Btw don't forget to support this project I would keep it free I need support to buy a laptop for coding

I found a better method than GOT hooking that works better and is much safer.

How useful is IMEI spoofing on modern Android?
Many people think that changing the IMEI through Zygisk / LSPosed can fully change a device’s identity, but the reality is a bit different.
On newer Android versions, access to the IMEI is heavily restricted. Most normal (non-privileged) apps can no longer read hardware identifiers like they used to, and Android has added more limitations around sensitive device information.
Even if you spoof the IMEI at the framework/API level, it usually only changes what applications see — not what the modem and mobile network actually use.
The real network path is:
App → Android Framework → Radio HAL → Modem → Carrier
Spoofing at the app/framework layer usually does not reach the modem or baseband.
So IMEI spoofing alone usually:
does not restore mobile signal
does not change the real modem IMEI
is not a complete device identity change
Nowadays, for many scenarios, other factors matter more:
Device fingerprint
Build properties
Play Integrity
Hardware-backed attestation
Service-specific identifiers
But the important question is:
What is your actual goal with IMEI spoofing?
Because the problem you are trying to solve may not be related to IMEI at all, and there might be a different solution.

Still beta

Backup and moving to the new ROM. Wish me luck The update will continue on Friday.