For experimental, I've made TikTok working with emulators but it's unusable in practice

DropVS said:

@Lukmat
With this solution a part of slow, you are undetectable? you can get views from country that you want? or it just to create accounts?

Click to expand...

Lukmat said:

Emulator MEMU and LDPlayer
Someone in the past was asking about Memu on forum, I've got interested and made it working and undetectable for TikTok
https://www.blackhatworld.com/seo/tiktok-and-memu.1606412/
@finkain

I am giving instruction because I will not use it.
In practive it's extremaly too slow for normal work.
You can manualy browse videos, create accounts, etc. Also upload videos
But for automation I need much faster solution.
That's why TikTok farm must be made with real devices, not emulators.
My set up: I gave memu 8gb ram, acceleration, RTX card acceleration and still videos are laggy when scrolling FYP.
It's not PC fault, but x86 to arm translation made by emulator.
Genymobile set up on Mac M1 would do the job

Instruction how to make emulator undetectable:

1. Run Samsung device in memu
** make sure you other real phones are disconnected from PC!
2. Then in adb you need to pull file build.prop
adb pull /system/build.prop C:/yourfolder/build.prop
3. Then copy values to ... ChatGPT, ask chat: "This is build.prop from emulator, change it to be typical to Samsung S7"
4. I've received

Code:

# begin build properties
# autogenerated by buildinfo.sh

ro.product.model=SM-G991U
ro.product.brand=samsung
ro.product.name=d1q
ro.product.device=d1q
ro.product.board=lito
ro.build.id=RP1A.200720.012
ro.build.version.incremental=G991USQS6DWF4
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=S
ro.build.version.all_codenames=S

ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Wed May 25 14:15:32 CST 2022
ro.build.date.utc=1653459332
ro.build.type=user
ro.build.user=cjw
ro.build.host=se.infra
ro.build.tags=release-keys
ro.build.flavor=rel-user
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,arm64-v8a,x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.characteristics=tablet
# end build properties
#
# from device/androVM/vbox64tp/system.prop
#
#
# system.prop
#

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
dalvik.vm.dexopt-flags=m=y
persist.service.adb.enable=
ro.secure=1
ro.opengles.version=131072
ro.zygote=zygote64_32
testing.mediascanner.skiplist=/storage/emulated/0/Android/

#
# Capabilities
#

# Battery sensor
ro.device.caps.bat=on
# GPS sensor
ro.device.caps.gps=on
# Accelerometer sensor
ro.device.caps.acc=on
# Webcam / camera sensor
ro.device.caps.cam=on
# Screencast / screenshot capability
ro.device.caps.scr=on
# Remote controller capability
ro.device.caps.rmt=on
# DeviceID / IMEI and AndroidID
ro.device.caps.did=on


#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.dalvik.vm.native.bridge=libnb.so
ro.ril.hsxpa=1
ro.ril.gprsclass=10
wifi.interface=wlan0
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.treble.enabled=false
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.x86_64.variant=x86_64
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=x86
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr

5. Then use command:
adb remount
adb push C:/yourfolder/build.prop /system/
6. Restart your emulator
7. Done, TikTok is working
8. Please note, to write build.prop you need to have set up in memu > storage > independent storage

Click to expand...

langtoi said:

The edited file has been successfully added to the memu, but when checking the parameters, they still haven't changed. There are some pieces of code that will cause errors. Maybe I did something wrong somewhere. I also tried changing your code but the parameters did not change

Click to expand...

SigmaMale said:

Same here, I managed to push the build.prop into the emulator's system folder but when I check the phone model under Settings it still shows the old phone.

Click to expand...

brucesidewalk said:

Did you restart emulator?

Click to expand...

Manifest101 said:

do you have a video tut on how to install it?

Click to expand...

Lukmat said:

This is not tutorial, this is some tip
I was sitting on that for whole day, for me it worked fine
it's showing me new phone in


Just get fun and do not mention me to help you. It's just experiment, I don't know why it's not working for you

View attachment 357285



View attachment 357287

View attachment 357288

Click to expand...

Manifest101 said:

Thanks for clarifying! i will give it a try

Click to expand...

GemmaMores said:

literally ran the app you used to check if its an emu or real device once i installed the emu and it said its a real one XD
also on the system info picture the entries are x86_64 and x86, which are architectures commonly used in virtualized Android environments. so you basically did nothing at all

Click to expand...

valques said:

Emulated never will be like the app , you could try another way

Click to expand...