So I've been getting banned Everytime I upload contacts to Whatsapp. I've found that for what ever reason when I uploaded a specific amount it never actually uploads from my android device. If I lower the limit by say 5k then it uploads fine. Ideally I want to do this across millions of contacts, but if I do this a few times it will temp ban and then ban after one or two more cycles. Creating a new account and doing it again almost always works the exact same way. Is there a way around this without distributing this across 1000s of accounts? Any ideas?
Prevent WhatsApp ban on contact syncing?
- Thread starter jetski761
- Start date
Update:I've been experimenting with cleaning our data against WhatsApp using an Android emulator. Installing WhatsApp and importing 15,000 contacts at once, then refreshing your contacts list in WhatsApp shows which contacts have WhatsApp accounts. While 15,000 seems optimal, 20k works but you have to wait hours for the contacts to pop up. After refreshing, you can dump wa.db from /data/data/com.whatsapp/databases and use the SQL query: SELECT * FROM wa_contacts WHERE is_whatsapp_user = 1 to grab users with an account. Afterward, you can clear the contacts with another ADB command and import another 15k.
Trying this for a third time leads to a 6-hour temp ban once the contacts are cleared. However, if you wait a few hours before the third attempt, you can repeat this process indefinitely. I've mostly automated this process from creating a VM, account creation, to verification, dumping the database, and extracting WhatsApp numbers. It can work across hundreds of threads.
The issue I've noticed is that over time the signup process changes in ways I've never seen on any website or app, and it's not logical. I assume the issues are coming because I can't pass basic integrity with this ROM? Now that I have found these limits, I was just going to start mass making accounts with automation, but I noticed after several days of doing this I get an error: "Login not available right now. For security reasons, we can't log you in right now."
The numbers are for sure not the issue. I have tried using VPNs to bypass this, but it doesn’t work. Also, during the beginning of testing, I was getting accounts banned, and was able to unban them, but then when I would try to log in again, it would give an error about using the official WhatsApp app, which I am doing... I tried moving this to a non-rooted phone and got the same error. Tried another number and presto it works. I then went to Walmart and used the one giving errors on a tablet there. It worked, which leads me to believe the issue comes from the ROM?
Does anyone have any ideas?
Trying this for a third time leads to a 6-hour temp ban once the contacts are cleared. However, if you wait a few hours before the third attempt, you can repeat this process indefinitely. I've mostly automated this process from creating a VM, account creation, to verification, dumping the database, and extracting WhatsApp numbers. It can work across hundreds of threads.
The issue I've noticed is that over time the signup process changes in ways I've never seen on any website or app, and it's not logical. I assume the issues are coming because I can't pass basic integrity with this ROM? Now that I have found these limits, I was just going to start mass making accounts with automation, but I noticed after several days of doing this I get an error: "Login not available right now. For security reasons, we can't log you in right now."
The numbers are for sure not the issue. I have tried using VPNs to bypass this, but it doesn’t work. Also, during the beginning of testing, I was getting accounts banned, and was able to unban them, but then when I would try to log in again, it would give an error about using the official WhatsApp app, which I am doing... I tried moving this to a non-rooted phone and got the same error. Tried another number and presto it works. I then went to Walmart and used the one giving errors on a tablet there. It worked, which leads me to believe the issue comes from the ROM?
Does anyone have any ideas?
Last edited:
- Feb 28, 2010
- 5,497
- 4,419
I don't think anyone will have any ideas as this is super specific. You already seem to be on the right track, just keep going
Yea that's what I was afraid of. I'm thinking the only solution is to move to physical devices but want to avoid that until I can verify this is worth it. Some of our tests have lead to 10 ecpm then 0 so not sure it's worth investing more time yet.
TeraJana021
Newbie
- Feb 11, 2025
- 15
- 5
same exact problem right here, although im using whatsapp for broadcasting. Haven't crack the problem just yet of "Login Not Available Right Now"
I have. From the looks of it it's 2 things causing it.
TeraJana021
Newbie
- Feb 11, 2025
- 15
- 5
So any root causes you spot on this problem bro?
emulators. Its a lot more specific than that but thats enough for someone to research.
Any progress on your analysis, i believe they added few limitations for banning accounts recently, i was also wondering if you are interested in selling your automated VM creation account creation etc ... source code
I ended up stopping, but I was able to figure out the issue was mainly the emulators, you would need to build custom custom roms with new device info in each to get anywhere. It's much easier to just use phones for long term stability. Otherwise the accounts only last a week at most.
I understand, what about selling the automation code ?
It's just a simple java program that launches stuff on seperate threads and runs some shell commands that launch the vm and then scripts to control it via adb. If you are interested send me a msg and we can discuss the details I guess.
Last edited: