yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Josh Brent:
Hey, I have tried it on two different smartphones OnePlus 9 Pro Stock and OnePlus 8Pro. Once with Magisk and once with KernelSU. With KernelSU, my smartphone bypassed both Momo and YASNAC. Nevertheless, the warning appears in WhatsApp and I can't use it. As soon as the bootloader is closed, no problems. It's a real shame. Hope to find any solution soon
[Google Pixel 6 Pro] CanerKaraca:
Did you tried Bootloader Spoofer?
[Google Pixel 6 Pro] Hasan9540:
I downloaded the new integrity and flashed it and rebooted, then installed and activated Bootloader Spoofer (all Google services and WhatsApp selected). Google Play security deactivated, Google Play storage contents deleted, Whatsapp storage contents deleted, I restarted the device, opened WhatsApp and entered my number. Unfortunately the error message came back. No matter which Rom and which device I use, as long as the bootloader is open, there are no instructions for me
[Google Pixel 6 Pro] CanerKaraca:
Post in thread 'Problem with WhatsApp and Bootloader Unlock' https://xdaforums.com/t/problem-with-whatsapp-and-bootloader-unlock.4642218/post-89399428
[Google Pixel 6 Pro] daicaxomlieu:
won't work on my pixel 8 pro too
[Google Pixel 6 Pro] Hasan9540:
I tried that too and it doesn't work either
[Google Pixel 6 Pro] chopwell20:
worked for me .. Device Redmi Note 10 5G, both imei restored, pixel experiance rom.
[Google Pixel 6 Pro] farish_xda:
Geat ===

Great ... works perfectly on android 12 ... was stuck ... thanks mate
[Google Pixel 6 Pro] Hasan9540:
@yassine2217 Brother it worked, I love your ass

But how safe is Magisk Kitsune?
[Google Pixel 6 Pro] fillwithjoy1:
Why would you add YASNAC to Denylist? YASNAC doesn't do the detections, Google Play does 🤦‍♂️
[Google Pixel 6 Pro] Izuru87:
My samsung device doesn't support this spoofer, is there any alternative? when wpp detects the custom rom it already sends the warning that it's not the official version
[Google Pixel 6 Pro] Izuru87:
I'VE FINALLY SOLVED IT

what I did

I was using BiTGapps core and when I switched to Open Gapps Pico (still without root), when I started wpp after force stopping, deleting the cache and data, wpp didn't recognize the system as a custom rom.

But when I installed Magisk Kitsune, wpp recognized it again when I logged in as a custom system. To solve this, I did what is shown in the images.

(there are some apps that don't make much sense, but I've been at it for a while and since there were only a few, I added them to magisk hide)

And after that the system was not recognized as custom at first, but still gave an error, then I found a tutorial on this site teaching how to use LSPosed (Remembering that my device is not compatible with lsposed) and followed the tutorial:

Install Xposed Framework/LSPosed on Android [Upd: Android 14]

In this comprehensive tutorial, we will show you the detailed steps to install Xposed Framework LSPosed on your device running Android 13.

droidwin.com

And after following the tutorial it looked like this:

(I don't think it was necessary to install Riru)

After doing the tutorial, to get it to work I deleted the cache, the data and forced the PlayStore and Whatsapp to stop and I managed to get past the screen that asked me to install the official Whatsapp.

I think that any method that makes the system not be recognized as custom and that hides the enabled OEM and deletes the PlayStore data in some cases, is enough to make wpp work again ;-;

Device: Samsung j8

System: LineageOS

Version: 17.1 arm64

Android: 10

Gapps: OpenGApps arm64-pico
[Google Pixel 6 Pro] lucasmz:
I had this issue on CalyxOS. I did have SafetyNet off on microG, so maybe that was the issue? Interestingly, I got banned for "spam" and then unbanned because I definitely did not do that; but after that this issue started appearing.

CalyxOS usually manages to pass basic and bootloader check, with HARDWARE_BACKED too, though it can't pass CTS. I believe SafetyNet is also used to check if apps were modified, so maybe because I had it off it just gave me that error.

Thankfully I've managed to get everyone to talk to me over Signal and so it helped me in that at least.
[Google Pixel 6 Pro] S@lwos:
I tried with my Samsung Note 20 5G, it doesn't work.
[Google Pixel 6 Pro] Remymans:
Great, this solution works on my Samsung S21+ with Stock Rom, rooted by magisk and thus the Bootloader unlocked.

But now tow questions...

1. Does it work only on stock Whatsapp or now with this solution it will also works on modified versions like GBWatsapp or FMwhatsapp?

2. Please, despite of the fact I succeed to get whatsapp working again, I do not know what 'gms' means. Is it a app which you an find somewhere? I found info on the internet ... gms = google mobile services which includes all the google apps like google maps, gmail, contacts .... and many more. So do I under sector 1 and 6 of Yassine's solution do that for every app of google?

Thanks.
[Google Pixel 6 Pro] yassine2217:
First question:

I haven't personally tested this on a custom ROM, but according to some users, it worked. I recommend reading the comments after my post for more information.

Second question:

GMS, which stands for Google Mobile Services, doesn't include Google apps. However, it provides essential services that many Android apps rely on.
[Google Pixel 6 Pro] SalaheddineMejd:
I found a solution.

For me I use rooted device (Motorola one vision) with custom rom (LineageOS21) and bootloader unlock.

1. Disable all root apps and not protected apps for just some time until you end this, for me as soon kali Linux Nethunter runs SafetyNet got disabled.

2. Download Magisk go to settings hide magisk, enable zygisk and enforce denylist.

3. Add Google play store, WhatsApp, Google Play Services and Google Services Framework to the denylist.

4. Disbale all modules from magisk.

5. Download Shamiko and Play Integrity Fix (search the mod version if you have android 14).

6. Delete storage from Google play store, Google Play Services and Google Services Framework, WhatsApp (make sure that you don't need data from WhatsApp).

7. REBOOT.

8. Add your number to WhatsApp (you may still get costume rom message but it's still fine WhatsApp doesn't block people because its costume rom what its matter the SafetyNet verification).

9.It should work.

(if it didn't work and you still get that message you need official WhatsApp IN THE OFFICIAL ONE maybe because your number is in some kind of some blocked list, I have 2 numbers they are wasn't working until I did this solution, but the other number still didn't work until I deleted it, and it works fine than after this).

​
[Google Pixel 6 Pro] SalaheddineMejd:
Tell me if it helps you and sorry for my English :).
[Google Pixel 6 Pro] turhvjbufv:
anyone managed to pass it with micro g installed(lineage 21)?
[Google Pixel 6 Pro] turhvjbufv:
the link to make lsposed compatible is broken? yo uahve another one?
[Google Pixel 6 Pro] turhvjbufv:
fixed, for me it was needed for whatsapp and play store and gms and play store framework to be on deny list and in bootloder spoofer only whatsapp to be on, play integrity fix module and play integrity next module
[Google Pixel 6 Pro] CAnmolG:
Hey when I enable bootloader spoofer then Play integrity test fails..if I disable it Play integrity test pass
[Google Pixel 6 Pro] CAnmolG:
D

Did u select system framework in spoofer ?
[Google Pixel 6 Pro] turhvjbufv:
No, only whatsapp otherwise play integrity fails
[Google Pixel 6 Pro] CAnmolG:
thanks, i did same and worked !
[Google Pixel 6 Pro] s--c:
Wow worked finally 👍 Although play integrity fails both basic & device?

Edit.. only enabling WhatsApp in spoofer worked and passes play integrity basic & device
[Google Pixel 6 Pro] frandypro:
Worked thanks You , My friend
[Google Pixel 6 Pro] smithopher:
You were not able to achieve that, right? For me it was exactly as @lucasmz described here - I think they marked my number as "only allow from trusted devices" - I can login with other numbers just fine (no "you need the official WhatsApp").

I tried BootloaderSpoofer, it didn't help. YASNAC passes, and says "Evaluation type: Basic". "Play Integrity API Checker" however says "Error getting token from Google". Not sure why..
[Google Pixel 6 Pro] turhvjbufv:
Not possible, I installed play services, that's because micro g currently doesn't support play integrity so when WhatsApp check for passing play integrity they get an error 9 back and it just defaults you to an untrusted device meaning you can't log in
[Google Pixel 6 Pro] smithopher:
Yes.. Maybe it would be possible with "microG Services + real Play Store" somehow:

Implement Play Integrity by js6pak · Pull Request #2077 · microg/GmsCore

It doesn't work yet, I'm suspecting microg's droidguard implementation, but it also doesn't make sense as there are recent reports of play integrity working through patched play store (I wasn't abl...

github.com

After I installed the real Play Store (via microg_installer_revived), not even YASNAC passes anymore, though: "The version of the Google Play services installed on this device is not authentic".
[Google Pixel 6 Pro] turhvjbufv:
Weird hmm I would have checked it but Installing the real play store with MIR is really annoying as it can easily get ****ed from playing with it for a bit
[Google Pixel 6 Pro] smithopher:
For the record, the problem with YASNAC got fixed by installing it from Play Store (its a known problem).

But even after installing WhatsApp from Playstore and using

Magisk-Kitsune's Hide List + BootloaderSpoofer + play integrity fix + real Play Store, WhatsApp still complained about "not being official".

Maybe its due to microG, or I have missed some steps.
[Google Pixel 6 Pro] turhvjbufv:
What did you enable bootloader spoofer on?

And are you passing device integrity in play integrity?
[Google Pixel 6 Pro] turhvjbufv:
You also need play curl (play integrity next), used to pass play integrity which is needed
[Google Pixel 6 Pro] smithopher:
Only on WhatsApp and "Play Integrity API Checker" (here that seems to have been enough).

Yes, in "Play Integrity API Checker" MEETS_DEVICE_INTEGRITY passes. Only "MEETS_STRONG_INTEGRITY" fails.

Have tried that now, ran "fp" in termux, and cleared data from Play Store + WhatsApp. The Issue still persists, sadly
[Google Pixel 6 Pro] turhvjbufv:
Only on WhatsApp and "Play Integrity API Checker" (here that seems to have been enough).

Try using hidemyapplist and hide every root app from Whatsapp and play store

And also what ROM are you using?
[Google Pixel 6 Pro] smithopher:
Tried hidemyapplist, created a profile as you described, no change. Also tried to hide LineageOS Apps, no effect

LineageOS 20 MicroG Edition
[Google Pixel 6 Pro] turhvjbufv:
Hmm so me your root denied apps on magisk kitsune
[Google Pixel 6 Pro] SalaheddineMejd:
bootloader spoofer kind a disable safetynet so don't use it btw I am using lineageos
[Google Pixel 6 Pro] turhvjbufv:
For me enabling this on WhatsApp works fine for me, maybe for @smithopher it should be disabled
[Google Pixel 6 Pro] smithopher:
As described here? Did you wait before creating it again, or can one recreate it right away? In case this helps, I guess it resets the "only allow from trusted devices" flag WhatsApp seems to have stored for that account
[Google Pixel 6 Pro] SalaheddineMejd:
For me I delete it than I recreate it in another device right away and move it to my device, and it works with me.

before you do that make sure if you search ChatGPT on Google Play it shows the original one from OpenAI this may look weird, but it shows that SafetyNet it is working fin for you.
[Google Pixel 6 Pro] smithopher:
What do you mean with move? Is the other device (which you use to recreate the account) rooted/unlocked too?
[Google Pixel 6 Pro] SalaheddineMejd:
My other device is not root or unlock and WhatsApp works perfectly in it.

Or you can just get a new number if you don't have device works perfectly with WhatsApp.
[Google Pixel 6 Pro] smithopher:
Ok, sorry for the ignorance, but you said (or I understood you as saying) originally that you then "moved" it to the rooted device. Or do you just use that one as "linked device" then?

What I wonder about, is if there is a chance, that completely deleting the account (not just from phone, but as described here), will reset the "needs official app" mark
[Google Pixel 6 Pro] TheTrueJayTwenty:
When in doubt wipe, and re-flash.
[Google Pixel 6 Pro] SalaheddineMejd:
For me when I deleted my account from "WhatsApp" not from the phone "needs official app" mark got removed and I move my number to the rooted device without using linked device method and my number works perfectly fine on the rooted device.

I am not sure that would be the same case as you as described here.

before doing anything make sure if you search ChatGPT on google play it going to show the original one from OpenAI to make sure SafetyNet is working fine.
[Google Pixel 6 Pro] turhvjbufv:
Seems like it's only checking for device integrity and locked bootloader on log in, since play curl fingerprint was banned for a while and it didn't log out or gave me any problem, anyone can confirm?
[Google Pixel 6 Pro] lucasmz:
For a while, what I did was set up my whatsapp account in another device from a trusted party, but with a strong password in ANOTHER profile, and then added my device as an extra one.

Now I switched numbers and things are working again. I'd try to get people to contact you before contacting them, at least for the first interaction so that WhatsApp doesn't flag you as a bot and get you in this situation.

If you have this issue, and are getting a new number, I wouldn't migrate my account, instead would do a new account and delete the last one.

WhatsApp really just seems to discriminate accounts to determine what kind of verification level they should have, as with a number it was very strict but not with another.
[Google Pixel 6 Pro] turhvjbufv:
Im guessing that once you got banned on a device that didn't pass integrity that they flagged you for being a bot automatically, and they just flag the number, if anyone here has root I recommend backing up Whatsapp using swift backup(and backup everything from Whatsapp)and then when you restore from that you don't need to login again
[Google Pixel 6 Pro] Nergal di Cuthah:
I think it more using unofficial or modded whatsapp as opposed to play integrity, as i fail device integrity when ever fringerprints are burned and my WhatsApp doesn't care.
[Google Pixel 6 Pro] turhvjbufv:
They don't care since they only checks for it on login, and if the problem was modded or something then why when you install the official one from play store and try to log in it says that you are trying to login from unofficial whatsapp
[Google Pixel 6 Pro] Nergal di Cuthah:
Because once you're flagged for using unofficial, even regular won't work on a bootloader unlocked device.

Tbis has all been discussed in this thread.

Again, as I've said before, my WhatsApp doesn't care that I'm rooted. I've never used unofficial so I'm not flagged
[Google Pixel 6 Pro] Ćwirek:
It worked on Pixel 8 running Evolution X ROM (root+unlocked bootloader), but only with official WhatsApp from Google Play Store. It does not work with modded version, like GBWhatsApp Pro
[Google Pixel 6 Pro] turhvjbufv:
Obviously dude you cannot log in to these
[Google Pixel 6 Pro] Ćwirek:
You could. Untill yesterday I was using GBWhatsApp Pro, but as a secondary device, on primary phone regular WhatsApp from PlayStore was running. Yesterday I wanted to check something and could not make it work like before and found solution here.

Now my completelly stock Pixel 5 runs regular WhatsApp, and my Pixel 8 is running regular WhatsApp but as secondary device linked to WhatsApp on Pixel 5
[Google Pixel 6 Pro] turhvjbufv:
First of all Gb Whatsapp pro is a scam and you should use fmmods as they are copying from them, second of all whatsapp yesterday released a check that makes it so you cannot use modded whatsapp as secondary devices
[Google Pixel 6 Pro] Ćwirek:
I did not know that, good to know. Thank you:)
[Google Pixel 6 Pro] dvhamham:
The problem not with root

This problem happen with bootloader unlock

If you lock bootloader it will work

And if you unlock bootloader without root

You will see the same problem.

And for who tell that her Whatsapp working with root it's normal me to my Whatsapp with root

But a day Whatsapp a added my number to list who can't register without bootloader locked.

So if you want use another number on the same phone it will work.

Solution for using Whatsapp:

Changing number or lock bootloader.

Me too I have the same problem and I tried a lot of things and I have arrived to this results.

I tried to hide bootloader by lsposed module (bootloader spoofer)

But not working.

Who have any solution to hide bootloader status please tell us.

My phone Google pixel 7.
[Google Pixel 6 Pro] turhvjbufv:
You need to pass device Integrity, which you can so by having root with play integrity fix module and play integrity next
[Google Pixel 6 Pro] sieger007:
still gotta go thru all rungs of the thread but I'm since 10+ days greeted by WhatsApp 🐜🧠 👎 d/l official app, when I've been on this since long long ago. everything was hunky D until i had to reflash my phone P1 . In my case it verifies fine on P2 ph with lock b/l stock & p3 too stock + unlocked b/l

i followed guide to get my Google play certificate by entering gsf apk id . Google ack this registration but I'm still showing device is not certified. i dunno what this online registration does is this supposed to reverse a certificate status as showing 'nothing ' , or certified from hitherto , not certified ?

anyways all persons in this thread who encounter this ugly WhatsApp bouncer & and are rooted with custom rom should take a look at the log directory here and share the output of respective logs

/data/data/com.whatsapp/files/Logs

it is quite possible that the same symptom is experienced but the underlying cause may be different

so here is my log snippet that talks about custom ROM

m20. Download/walogs# cat * | grep -i custom
2024-07-03 03:18:12.717 LL_I M [2:main] app/custom-rom
2024-07-03 03:18:33.847 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onCreate
2024-07-03 03:18:33.880 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onStart
2024-07-03 03:18:33.883 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onResume
2024-07-03 03:18:33.885 LL_I M [2:main] app/dt/set com.whatsapp.registration.parole.CustomRegistrationBlockActivity@987da26
2024-07-03 03:18:35.697 LL_I M [2:main] app/dt/clear dt=com.whatsapp.registration.parole.CustomRegistrationBlockActivity@987da26 dialog_toast=com.whatsapp.registration.parole.CustomRegistrationBlockActivity@987da26
2024-07-03 03:18:35.698 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onPause
2024-07-03 03:18:36.823 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onStop
2024-07-03 03:18:37.730 LL_I M [2:main] com.whatsapp.registration.parole.CustomRegistrationBlockActivity.onDestroy
2024-07-03 08:23:57.898 LL_I D [2:main] app/custom-rom
m20. Download/walogs#

BTW

I am already magisk rooted with delta i.e su allow list enforced & have installed Play integrity fix.. yet Google Play status shows as device not registered

so I think my issue is a custom ROM rather than a bootloader but I may be wrong maybe someone can take a harder look at the logs and tell me what is going on

the entire log is over here
[Google Pixel 6 Pro] turhvjbufv:
Yep, ask your custom ROM maintainer to sign the ROM to google or ask them how to do it, alternatively you can sign into whatsapp on another device and do a linked device to your current one
[Google Pixel 6 Pro] sieger007:
Its in fact not a custom ROM . Its a stock ROM that has had TWRP installed with Magisk.

I used MagiskHideProps apps to change the ROM for Samsung M20 which is what the phone is after hittings all these walls

Is there anyway to completely hide your custom ROM Status. See what I did so far PFA
[Google Pixel 6 Pro] sieger007:
I have seens the linked device stuff many places . Problem;s I have the unencrypted backup oof /data/data/com.whatsapp from previous instance that I will directly restore to my next phone using root. So where whatsapp verifies me I am unrooted and I can't push that folder
[Google Pixel 6 Pro] Max-Jaan:
Almost 3 month the issue has fixed for me.

im using unofficial WhatsApp and got banned on custom rom and when ever i login in my iPhone with that number no issue it all used another locked bootloader phone working fine but in unlocked bootloader official i can't login the WA shows mx login official app

The fix With kernelSU

I'm attacking screenshot

4 modules in KSU

And in LSPosed Bootloadersper

Checked whatsapp with this play services and WhatsApp worked

I know many people in trouble like me thats why i just now logged in and i came to share with you guys

And Sorry for my English 😁
[Google Pixel 6 Pro] sieger007:
Thx will give it a shot. My logs from /data/data/com.whatsapp/files/Logs give a message "custom/ROM" . I could verify myself in phone stock + b/l lock , stock + b/l unlock but not in Custom ROM + b/l ulock + root
[Google Pixel 6 Pro] turhvjbufv:
You need to pass Integrity and hide root, a lot of us here on custom ROM and still managed to sign it
[Google Pixel 8 Pro] Utini:
...is this on purpose or is it just me? First time I see a pixem without it being installed.

Funnily I also have issues with t-mobile where I will loose signal on both my sims if someone calls me on my t-mobile sim. So i thought I might need carrier services app.
[Google Pixel 8 Pro] yanggame:
If you are taking about Google's Carrier Services, you are not along.

But I think it's mainly for RCS, not for phone calls.
[Xiaomi Pad 6] Yuri1rina:
I bought the MI PAD 6 in Italy, so the MIUI version is set to global, but I bought the Stylus pen 2 from AliExpress and just now I realized that the pen doesn't work with global version. Do I have to change the MIUI version specific to China?

And if so, how can I do that?
[Xiaomi Pad 6] kevinsunny:
What? I'm using Pad 6, MIUI global, and the pen works perfectly fine. I'm thinking the pen you bought is wrong.
[Xiaomi Pad 6] matadorka:
Did you turned off MIUI Optimisation? I don't have stylus, but after turning it off, xiaomi keyboard stopped working.
[Xiaomi Pad 6] RiTCHiE007:
The stylus works fine in the global rom and you can even see the stylus settings in the general settings tab.