Device fingerprinting: why anti-fraud still recognizes my phone
Device fingerprinting: why anti-fraud still recognizes my phone
24-08-2025, 09:16 AM
Warning: If you are not a specialist in this field, please do not reply. Do not clutter the thread with unnecessary information.
For the past two weeks, I’ve been independently researching ways to bypass Supercell’s anti-fraud system. My goal is to contact Clash of Clans support to recover my account, but they refuse and block me. Since I am not a programmer and had no prior experience with phones, this has been a steep challenge. All I have is persistence and motivation .
Here’s what I’ve done so far:
Device: Xiaomi Redmi 7
Tools used: Magisk (with various modules and settings)
Achievements:
- Successfully spoofed phone information for multiple apps: KernelSU, Fingerprint OSS Demo, DevCheck, etc.
- Passed checks like AppList Detection, Momo, Play Integrity, Root Beer Check Sample.
Next steps I attempted:
- Considered reflashing the phone with modified identifiers: Device ID, Android ID, GSF ID, Media DRM ID, Device Fingerprint.
- Created custom firmware using avbtool, ChatGPT, and DeepSeek.
- Modified system.img and vendor.img, specifically in build.prop:
ReplacedCode:ro.vendor.build.fingerprint ro.vendor.build.id ro.build.version.bsp
withCode:"QKQ1.191008.001"
to generate a new device fingerprint.Code:"QKQ1.191003.001"
- All unique identifiers changed successfully.
- However, Clash of Clans support still recognized the device.
- IMEI and MAC address were not changed (as apps cannot access them or can?).
I have been exhausted over these two weeks, working from morning till night, but I lack the necessary knowledge. I am not asking for help bypassing the system. I only seek guidance on which identifiers or mechanisms allow them to recognize my device despite all changes.
I really hope for your tips and advice. Looking forward to your response.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)
