Same here… should it be rotate ? maybe rotate x users with N proxies ?
Hi, I’m using a 4G russian proxy and 3 accounts connected:
For 1 month everything ok, and now:
- one is working fine
- one got follow and like blocked (i don’t know how long)
- one got follow and like blocked for 5 hours
Follow actions: 58-60 / Day
Like actions: 40-45 / Day
Can you help me?
What I noticed with my clients is that the generally say that they got a log in attempt message and then got the notification to change their password. I was wondering why they kept getting log in attempt messages and then I remembered that setting I added when I was having issues with EB blocks. See image below
Do you think that this issue is from constantly logging in and out of EB?
I was also thinking that the workarounds from the api blocks might be causing these issues as well. After the api got blocked we started to use the EB when blocked. Then the EB started to get blocks so we started clearing the cookies and logging out of EB to get passed these blocks. Maybe we are just doing too many quick fixes which is just causing more issues?
I do have accounts that only use api and accounts that I do not clear the cookies for and they are experiencing the same problems. The one thing that is common for all accounts is the logout from EB setting. Is anyone experiencing this issue on accounts that don’t have the logout from EB setting enabled?
Also I noticed a new action block error or maybe it is not new but I am only noticing it now. Do you think all accounts get this message before the account compromised message. Will keep an eye on the account to see if it gets the compromised message.
Configuration
- Using own mobile proxies
- 5 accounts per proxy maximum
- Issue affecting about 15% of clients
- Accounts make less than 200 follows/unfollows, 300 likes and 1000 story views per day
- Don’t use night mode
- Compromised message does not appear to be location specific, happens to clients in same country as mobile proxies.
3 Likes
Sometimes I receive log in attempt emails when clearing cookies or logging in/out from the EB
Does clearing cookies log you out of EB?
For anyone who is still having issues with API Blocks when they have cleared cookies, changed proxies or tried to rotate ISP. Here was my account fix.
Here are the steps:
1. Download “Device Info HW” application from Google Playstore.
2. Go to your automation software settings and change device id with your custom device id.
You may ask why?
Heres a screenshot:
This was my device id on profile. Problem is Device SM-G313U doesnt support nor 27 Android API nor Android Oreo. The DPI count is completely wrong, same as resolution. qcom is also bad info since there is no other info (there are tons of qcom processors).
3. You know why we are doing this. Now we can proceed. Go to Device Info HW and copy your stats from your real android device.
_
(Android API Number)/(Android Version Number); (DPI); (Resolution); (Device Manufacturer);(ROM Name);(Device Model); (system platform); (device language)
_
Example of my Xiaomi Redmi Note 7 Pro:
Explanation
28 as Android API Level of Android Pie
9.0.0 as Android Pie
409dpi/409ppi Density of my device
1080x2340 Resolution of device
Xiaomi as manufacturer
Redmi as Brand name
Note 7 as model name/number
msm8953 as board/platform holder of device
en_US as my language on Android Device
It should work now. You can also change main infos like device id, phone id, unique id, advertising id.
If you shook up all the things. I’ve mentioned and things before this post. It’s a guarantee your profile should be API-Block-FREE.
36 Likes
Thanks for the heads up. Will give this a try but I have a few question if you wouldn’t mind answering them.
- How do you know the exact format to enter the information? For example you have down for device language en_US, would English US also work?
- I don’t see ROM name in that app, where do you get that from?
- Does this information have to be input in a specific order? If so how do you know what order?
Is this information displayed in the app you mentioned as well?
Thank you so much for the tutorial. I have one question, if I have 100 clients does that mean I need to get my hands on 100 android devices inorder to extract their device id?
1 Like
hi @itsmeyourtime may i know the setting for this 
For like please use it mixed with like after follow and you will get better follow back ratio and again,
Anyone tried and verified this works? If it’s just because of the device that’s too old, can the devs do any changes to it?
3 Likes
You could probably do one device for all the profiles. The point I wanted to show was that Device infos were outdated and not just oudated a bit but outdated by a mile and also not rightly configured.
1 Like
I believe devs thought about about this. But you can just randomize this stuff like its a piece of cake.
My bad -
- You can google all short terms for language packs, they are all universal with their naming
- ROM name - Brand Name
- I dont know about the order, I used order based of current api agents.
Device ids, phone ids are shown differently on other phones. Youtube helps here.
Ok very interesting. I had the same theory a week ago that JArvees API user agent is wrong.
So how would i input it exactly for my Galaxy S9?
“28/9.0.0; 480dpi; 1080x2220; Samsung;Galaxy;SM-G960F; samsungexynos9810; en_US” Like this ?
The information in the software you said to download is all over the place. And what about the Jarvees Embeded Browser User Agent window?
I modified mine to this “Mozilla/5.0 (Linux; Android 9.0.0; SM-G960F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.101 Mobile Safari/537.36”
Any modifications there? Thanks a million!
2 Likes
ApiAgent for smartphone should be ok. You should try modify device ids, phone ids too if you can!
EB uses their own ApiAgents, I didn’t test EB since, I never did EB. But in theory it should be the same thing and with modification you should be fine.
HAHA, just tried the method, with a proxy and BOOM, 7 DAY block. Damn. I think automation has come to an end. Oh well. Bye Jarvee
You shouldnt do that now since there are API changes ongoing on Instagram 
Ah okay cool. Will try some tests with this and see
Shouldn’t try what exactly? Shouldn’t try changing the api user agent or shouldn’t try changing device IDs etc?
When I wrote this, everything was fine. When you replied they started to report problems. But idk what caused your block, my acc was fine, now getting 17days without single API block.
2 Likes