[Google Pixel 6 Pro] brunoaduarte:
Hi! Has anyone been able to bypass the "You need the offcial WhatsApp to log in" error on Waydroid or any other emulator?

- This number was always used in emulators (LDPlayer, MuMuPlayer, etc)

- I never used WhatsApp mods like WhatsAppGB, etc...

- The number was never used to spam or anything like that.

- It was logged in on a official WhatsApp app from the Play Store and all of the sudden it logged out, and when I tried to register again it was banned, so I waited for ~12 hours till WhatsApp unbanned it.

Then I tried registering again and this message appeared.

- I can register the same number with not problems on a real device with factory settings (locker bootloader + official rom)

I followed all the instructions from here and other I've found on another threads

- Copied properties from a real certified device to /var/lib/waydroid/waydroid.cfg

These will make the device look similar to a real device avoiding the "Custom rom error" popup on WhatsApp as it uses some of these properties to detect the custom rom in the app/custom-rom routine (mostly from display.id).

[waydroid]
arch = x86_64
vendor_type = MAINLINE
system_datetime = 1722043792
vendor_datetime = 1722079261
suspend_action = freeze
mount_overlays = True
auto_adb = True
images_path = /var/lib/waydroid/images
system_ota = https://ota.waydro.id/system/lineage/waydroid_x86_64/GAPPS.json
vendor_ota = https://ota.waydro.id/vendor/waydroid_x86_64/MAINLINE.json
binder = binder
vndbinder = vndbinder
hwbinder = hwbinder
binder_protocol = aidl3
service_manager_protocol = aidl3

[properties]
ro.hardware.gralloc = default
ro.hardware.egl = swiftshader
ro.product.brand = google
ro.product.manufacturer = Google
ro.system.build.product = redfin
ro.product.name = redfin
ro.product.device = redfin
ro.product.model = Pixel 5
ro.system.build.flavor = redfin-user
ro.build.fingerprint = google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys
ro.system.build.description = redfin-user 11 RQ3A.211001.001 eng.electr.20230318.111310 release-keys
ro.bootimage.build.fingerprint = google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys
ro.build.display.id = google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys
ro.build.tags = release-keys
ro.build.description = redfin-user 11 RQ3A.211001.001 eng.electr.20230318.111310 release-keys
ro.vendor.build.fingerprint = google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys
ro.vendor.build.id = RQ3A.211001.001
ro.vendor.build.tags = release-keys
ro.vendor.build.type = user
ro.odm.build.tags = release-keys

- Turned off Play Protect on Play Store

Installed:

- Magisk

- enabled Zygisk + MagiskHide + Hide Magisk app (bhrx.r.qm)

- PlayIntegrityFix v1.6.9

- Zygisk LSposed v1.9.3

- Added Play Services, Play Store and WhatsApp to MagiskHide list

- LSposed v1.9.3

- Bootloader Spoofer v3.8 module

- Enabled Bootloader Spoofer to all apps.

And just to be on the safe side, I also registered the device at Google Android Uncertified (even though it's not required as I'm mimicking a "Google Redfin" device)

Apps (all from official Play Store):

- WhatsApp

- Key Attestation Demo

- Play Integrity API Checker

- Cleaned Play Services, Play Store and WhatsApp

pm clear com.android.vending; pm clear com.google.android.gms; pm clear com.whatsapp;

With the "Key Attestation Demo" I can see that the Bootloader Spoofer is working properly ✅.

✅

But on the Play Store app / Settings I have the "Device not certified" message and Play Integriry API Checker fails with an "UNEVALUATED" error, meaning the check is not even occuring (it seems).

And on WhatsApp the "You need the offcial WhatsApp to log in" error.

Any ideas whatelse could I try here?

Thanks!