[Journey] PhoneFarms

justmeseo

justmeseo

Power Member
Joined
Nov 16, 2017
Messages
670
Reaction score
472
Alright, I know this has been out for a while, but AI is getting smarter by the day. Detection of browser CTRs is becoming the day-to-day norm, browsers are getting banned, low-quality accounts are getting banned, and more than ever marketers need more and more resources to be able to rank things. I have also partaken of my other personal journey https://www.blackhatworld.com/seo/gmb-google-youtube-ctr-bot-buidling.1630669/page-9#post-21198708 , where I show from the start to end the full creation of a fully function CTR platform.

Therefore I decided to solve the new problem, and please I should remind users that I'm not selling anything, and I'm looking to make this opensource in the near future, if you feel like you could bring something to the project please leave a comment, and this could become a potential joint venture.


Background points:

  • Mobile apps are becoming more important than browser-based environments
  • Many platforms require phone/device verification
  • Apps have their own device-specific data and state
  • Managing physical phones at scale is difficult
  • Traditional Android emulators are heavy on CPU and RAM
  • Android environments need to be easy to backup, move, and restore
  • I want multiple Android environments running from one PC
Solutions I want to solve:

  • Portable Android environments that can be backed up and restored
  • Lightweight Android with Play Store and Google services
  • Multiple independent Android instances on one PC
  • Less dependency on physical phones and hardware
  • Simple management of multiple instances from one machine
Current features:

  • Mass Creation of devices
  • Mass Control of devices (one action replicates in all)
  • Proxied sessions, phones take different proxies
  • Multiple versions of phone devices with different resolutions
  • ABD automation setup (run automations like warmup etc)
  • Full backup of profiles and accounts used throughout socials, with the ability to export to another device.

Current setup: (currently can run around 50-100 devices)

  • 16GB RAM
  • 6-core CPU
  • Astro js + Java + RUST
  • My own custom version of android (with injected GSM + google play)
  • No dedicated GPU
  • Custom lightweight Android environment
  • Play Store + Google services integrated
  • ADB access for device management
  • API for managing and communicating with Android instances
  • Multiple Android instances running from a single PC
  • Android/app data can be backed up and restored


ps. you might see some pixalated views of the phones, thats due to the low resolution I set and Im using in order to be able to manage multiple ones without slowing down the devices.
 
Last edited:
Advertise on BHW
New feature added: Bulk apk installation (this will be useful when I create an android app, and need installs to promote it, on playstore.)


1790886728882.png
 
justmeseo said:
New feature added: Bulk apk installation (this will be useful when I create an android app, and need installs to promote it, on playstore.)


View attachment 549801
Click to expand...
wonderful journey man!

I would like to know if your end goal is to farm accounts with the devices and what type of accounts you thin kyou could work better with this type of setting
 
looks like a great project. How do you plan on getting around blocks/bans/captchas ect ?
 
Narakhu07 said:
wonderful journey man!

I would like to know if your end goal is to farm accounts with the devices and what type of accounts you thin kyou could work better with this type of setting
Click to expand...
thanks @Narakhu07 , that’s exactly the right mentality. The goal is to be able to warm up accounts and set up scheduled flows that perform different actions, like listening to Spotify playlists, watching YouTube channels, or interacting within a Reddit community.

From there, you could scale things up to thousands of devices for things like mass interactions, Play Store downloads/reviews, Google Maps activity, Etsy purchases/reviews with digital cc recharged, etc. I’m sure there are plenty of other use cases you could come up with too.
bonzo90 said:
looks like a great project. How do you plan on getting around blocks/bans/captchas ect ?
Click to expand...
To be honest, I’ve probably only run into 2 Google Search CAPTCHAs, and they were easy to bypass with a clean IP. The nice thing about the current process is that we can store accounts with cheap, low-quality proxies, so the accounts stay in good shape regardless of the proxy and remain fully functional across other apps as well. TikTok has a few limitations here and there, but Twitter works great.

Clean mobile proxies, are a must for google ctr.
 
BooSpaceMan said:
Amazing project, but what android version are you using? Using an old one is a MASSIVE fingerprint
Click to expand...
That’s a great question. From my experience, I haven’t had any issues with the Android versions I’ve used. The Android image is personally customized, and the fingerprints are overwritten to make it look as natural as possible.

The only downside is that each Android version needs to be custom-injected if you specifically want to use a certain version. For me, though, the main goal is being able to run 100+ devices on a simple VPS. That requires heavy debloating and removing unnecessary UI components.

With a standard Android image, you’d struggle to run more than a couple of instances on a VPS of this size. With my version, I can theoretically run up to 1,000 on the current host and still manage them smoothly. Even on a normal PC, try running 10+ Android emulators at once and you’ll see how quickly it starts getting heavy. With this setup, we can do that without breaking a sweat.

We want to move away from traditional hardware phone farms, where each box costs around $800 and can only hold about 20 devices, plus the networking infrastructure and proxies. The network side also needs to be modified, since some apps can detect nearby Wi-Fi networks. Imagine having 100 devices all seeing the same nearby networks, that’s a pretty obvious fingerprint.

❌ you’re looking at roughly $1,000+ per hardware box setup (that can only have 20 devices), plus proxies, maintenance, electricity, and everything else that comes with running physical hardware.
✅ While our goal is to move all of that into a virtual environment where we’re paying around $20/month for the VPS, plus proxies, while being able to scale much further without having to watch over anything else.

thank you for your question.
 
justmeseo said:
That’s a great question. From my experience, I haven’t had any issues with the Android versions I’ve used. The Android image is personally customized, and the fingerprints are overwritten to make it look as natural as possible.

The only downside is that each Android version needs to be custom-injected if you specifically want to use a certain version. For me, though, the main goal is being able to run 100+ devices on a simple VPS. That requires heavy debloating and removing unnecessary UI components.

With a standard Android image, you’d struggle to run more than a couple of instances on a VPS of this size. With my version, I can theoretically run up to 1,000 on the current host and still manage them smoothly. Even on a normal PC, try running 10+ Android emulators at once and you’ll see how quickly it starts getting heavy. With this setup, we can do that without breaking a sweat.

We want to move away from traditional hardware phone farms, where each box costs around $800 and can only hold about 20 devices, plus the networking infrastructure and proxies. The network side also needs to be modified, since some apps can detect nearby Wi-Fi networks. Imagine having 100 devices all seeing the same nearby networks, that’s a pretty obvious fingerprint.

❌ you’re looking at roughly $1,000+ per hardware box setup (that can only have 20 devices), plus proxies, maintenance, electricity, and everything else that comes with running physical hardware.
✅ While our goal is to move all of that into a virtual environment where we’re paying around $20/month for the VPS, plus proxies, while being able to scale much further without having to watch over anything else.

thank you for your question.
Click to expand...
and for things like viewbotting in a setup like this, how would you manage things like fingerprinting in the long run? Of course, i think you would use a rotating mobile proxy to keep it more safe
 
Narakhu07 said:
and for things like viewbotting in a setup like this, how would you manage things like fingerprinting in the long run? Of course, i think you would use a rotating mobile proxy to keep it more safe
Click to expand...
For viewbotting, the setup works really well. You wouldn’t have many issues with storing the accounts either, since any account you add to a social media app can be exported to another virtual device. So even if you lose one device, you can move the tokens over to another and stay logged in across the apps.

Rotating proxies also work well with this. I’ve already tested it with 5 devices running rotating proxies for YouTube watch hours, and it worked really well and stayed consistent.

I think the main idea here is not to burn through accounts, but to build up high-quality accounts over time, basically a real army of users that you can maintain and reuse at an affordable cost.
 
PrimeCove said:
Which versions?
Click to expand...
From 12 to 16, not 17 yet. Since 17 just came out, I haven’t had much time to get into it yet.

I’ll be working on the architecture first, then I’ll move on to the individual images. The important part is that the platform should be flexible enough to support any Android version and adapt it to our environment without any major issues.

what are your thoughts on the version though? any in particular that you think might be better for any specific reason?
 
justmeseo said:
For viewbotting, the setup works really well. You wouldn’t have many issues with storing the accounts either, since any account you add to a social media app can be exported to another virtual device. So even if you lose one device, you can move the tokens over to another and stay logged in across the apps.

Rotating proxies also work well with this. I’ve already tested it with 5 devices running rotating proxies for YouTube watch hours, and it worked really well and stayed consistent.

I think the main idea here is not to burn through accounts, but to build up high-quality accounts over time, basically a real army of users that you can maintain and reuse at an affordable cost.
Click to expand...
Exactly. When you have all the parameters controlled, grow accounts and maintain them should be as easy as working with organic traffic, but way much more reliable since you control the traffic from the strart.
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top