Android faker and tiktok

[SpeedTX77]

I have a question is it possible to use LSPosed and use the module android faker to spoof the device ids for the tiktok app. My android is rooted, if so which ones can I enable to spoof tiktok? Reason is I want to make more accounts for my business and I don't have enough money for a new phone.

This is what it does module can spoof These Ids:

-> Imei -> Hardware Id -> Mac Address -> Mac Bssid -> Mac Ssid -> Bluetooth Mac -> Android Id -> Sim Serial Id -> Sim Sub Ids -> Mobile No -> GSF ID -> MediaDrm ID -> Advertisement ID

 

[Anson2008]

You have to try and see for yourself just take it slowly. Rome was not built in a day

 

[hemil]

did it work for you ?

 

[RaeAly]

The majority of that stuff won't help as TikTok doesn't or can't pull those values. The only ones I'm aware you can change are Google Ads ID, App specific Android ID (different from normal android id), and MediaDRM ID.

 

[hemil]

The majority of that stuff won't help as TikTok doesn't or can't pull those values. The only ones I'm aware you can change are Google Ads ID, App specific Android ID (different from normal android id), and MediaDRM ID.

Can i spoof this id's? And changing this ids can remove maximum attempt reached error?

 

[RaeAly]

Can i spoof this id's? And changing this ids can remove maximum attempt reached error?

I think all of those can be changed with a factory reset maybe? Can't tell you if that's enough for a fully new device. Though you can typically fix max attempts for 1-2 accounts by just wiping data repeatedly til it lets you through.

 

[hemil]

I think all of those can be changed with a factory reset maybe? Can't tell you if that's enough for a fully new device. Though you can typically fix max attempts for 1-2 accounts by just wiping data repeatedly til it lets you through.

i can't reset phone because i am using vmos virtual machine and maximum attempt reached came only if i create new account. Acctualy i am using vmos because one android 9 custom rom works fine with tiktok. in other roms i can't even like videos and if i upload videos tiktok removes it instantly. maximum attempt reach error came after i created 4 to 5 accounts when i newly installed rom. so i want to change all id's. i have already changed android id of rom but it's not working.

 

[RaeAly]

i can't reset phone because i am using vmos virtual machine and maximum attempt reached came only if i create new account. Acctualy i am using vmos because one android 9 custom rom works fine with tiktok. in other roms i can't even like videos and if i upload videos tiktok removes it instantly. maximum attempt reach error came after i created 4 to 5 accounts when i newly installed rom. so i want to change all id's. i have already changed android id of rom but it's not working.

Android emulator is not great for TikTok, they fully (and I mean fully) detect it, so they limit your actions quite a bit. The videos instantly deleting is an account quality issue, which you can see if you try logging into the account on your phone, the same thing will happen.

I know some people use emulators to spam post but they have to age the accounts quite a bit, but I don't have any experience with that so idk.

Also, if by "id of rom" you mean actual device/software details like roBuildId, I'd recommend against that unless you change every buildprop to be consistent. Maybe try another emulator, one with device presets you can switch through?

 

[hemil]

Android emulator is not great for TikTok, they fully (and I mean fully) detect it, so they limit your actions quite a bit. The videos instantly deleting is an account quality issue, which you can see if you try logging into the account on your phone, the same thing will happen.

I know some people use emulators to spam post but they have to age the accounts quite a bit, but I don't have any experience with that so idk.

Also, if by "id of rom" you mean actual device/software details like roBuildId, I'd recommend against that unless you change every buildprop to be consistent. Maybe try another emulator, one with device presets you can switch through?

I tried dolphin anti detect browser with 4g mobile proxy but i can't even like the videos . That's why i am using emulator.

 

[hemil]

I tried dolphin anti detect browser with 4g mobile proxy but i can't even like the videos . That's why i am using emulator.

Not able to like videos

 

[RaeAly]

I tried dolphin anti detect browser with 4g mobile proxy but i can't even like the videos . That's why i am using emulator.

Try another emulator, but like I said, don't expect to get results like phone, not possible.

 

[hemil]

Try another emulator, but like I said, don't expect to get results like phone, not possible.

but i get the result like phone on vmos i just need to remove the maximum attemp reach error while creating new account. And i am now trying ldplayer. And can you tell me where mediadrm id located? can i change it with root explorer? Thanks

 

[RaeAly]

but i get the result like phone on vmos i just need to remove the maximum attemp reach error while creating new account. And i am now trying ldplayer. And can you tell me where mediadrm id located? can i change it with root explorer? Thanks

Hmm ok, is the vmos rooted, or do you have proxy set in android settings? Disabling root and proxying the whole thing so tiktok can't detect proxy settings could help.

 

[hemil]

Hmm ok, is the vmos rooted, or do you have proxy set in android settings? Disabling root and proxying the whole thing so tiktok can't detect proxy settings could help.

no i use proxy outside the vmos in my original device with socksdroid and i don't think it's a root detection i already tried root cloack to hide root.

 

[RaeAly]

no i use proxy outside the vmos in my original device with socksdroid and i don't think it's a root detection i already tried root cloack to hide root.

Is adb enabled? Other than that and some buildprops like roSecure, roDebuggable, and roOemUnlock, idk? Maybe bad proxy?

 

[hemil]

Is adb enabled? Other than that and some buildprops like roSecure, roDebuggable, and roOemUnlock, idk? Maybe bad proxy?

i have creacted my own dante server in google cloud for socks5 proxy. i think vmos take some of my original device data while installing rom becuase in my device maximum attempt reach error also coming.

 

[kelturon]

i have creacted my own dante server in google cloud for socks5 proxy. i think vmos take some of my original device data while installing rom becuase in my device maximum attempt reach error also coming.

Vmos on proxies from Google cloud. From my experience sounds like worst setup ever. Honestly imo you are just wasting time. TT has a team of developers who are working against you. The odds are not on your side. What are you after? Money? You will loose much more time (money) battling TT antibot team only to realize you can't.
A used android can be bought for under 100$

You are trying to perform a brain surgery using a hammer and a stone

 

[hemil]

This is my build prop

Vmos on proxies from Google cloud. From my experience sounds like worst setup ever. Honestly imo you are just wasting time. TT has a team of developers who are working against you. The odds are not on your side. What are you after? Money? You will loose much more time (money) battling TT antibot team only to realize you can't.
A used android can be bought for under 100$

You are trying to perform a brain surgery using a hammer and a stone

i am just trying to do it without money and i have created 2 account which is viral with googe cloud proxy.

This is vmos build prop

ro.product.brand=google
ro.product.model=Nexus 5
ro.product.manufacturer=LGE
ro.product.name=hammerhead
ro.product.device=Infinix-X692
ro.product.board=smdk4x12
ro.product.platform=
ro.board.platform=mt6768
ro.bluetooth.name=Android
ro.boot.bootloader=unknown
ro.bootloader=unknown
ro.build.expect.bootloader=unknown
ro.build.id=PQ3A.190801.002
ro.build.version.incremental=10250142
ro.build.host=android
ro.build.type=user
ro.build.user=android-build
ro.build.product=hammerhead
ro.build.display.id=CPH1823-user 9 PQ3A.190801.002 eng.root.20191015.144423 release-keys
ro.build.fingerprint=google/hammerhead/hammerhead:9/LMY48G/10250142:user/release-keys
ro.build.description=hammerhead-user 9 LMY48G 10250142 release-keys
ro.build.characteristics=default
ro.build.flavor=user
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.security_patch=2019-10-01
ro.build.date=Tue Oct 15 14:44:23 CST 2019
ro.build.date.utc=1571121863
ro.build.tags=release-keys
ro.build.version.release=9
ro.bootimage.build.fingerprint=google/hammerhead/hammerhead:9/LMY48G/10250142:user/release-keys
ro.vendor.build.fingerprint=google/hammerhead/hammerhead:9/LMY48G/10250142:user/release-keys
ro.serialno=0C9BBECE2D6FA6D850FE
ro.boot.serialno=0C9BBECE2D6FA6D850FE
ro.product.locale=en-United States of America
ro.product.locale.language=en
ro.product.locale.region=United States of America
ro.bluetooth.address=fc:95:e5:7a:08:4c
ro.kernel=0
gsm.version.baseband=953_GEN_PACK-1.179545.1.181534.1
vmos.camera.enable=0
persist.adb.tcp.port=0
qemu.hw.mainkeys=0
qemu.hw.navbar.rtl=1
rf.bnum=01
ro.input.noresample=1
rf.mac=9e:89:e6:ed:9a:ad
debug.sf.nobootanimation=0
vmprop.networkoperatorname=AT&T Mobility
vmprop.networkoperator=312670
vmprop.networktype=
vmprop.datanetworktype=15
vmprop.simoperator=312670
vmprop.simoperatorname=AT&T Mobility
vmprop.simcountryiso=pk
vmprop.simserialnumber=42604351940902420887
vmprop.subscriberid=312670016850333
vmprop.groupidlevel1=
vmprop.line1number=11901497645
vmprop.dataconnectionstate=2
vmprop.simstate=5
vmprop.androidid=5C35CFD4B082A8E3
vmprop.imei=563286052742036
vmprop.imeisv=78
vmprop.ip=
vmprop.wifissid=yor
vmprop.wifibssid=00:00:00:00:00:00
ro.vmprop.maxfps=60
persist.clip.enable=1
persist.noti.enable=0
persist.dealvm.enable=false
persist.crash.sil=null
persist.show.signal=1
persist.package.name=com.android.secex
persist.sys.auto_boot_ctr=true
persist.show.romex=1
persist.vmper.enable=0
persist.vmstatus.hide=0
persist.vmlaun.dis=0
persist.debug.romex=0
ro.logcat.enable=0
sdk.logcat.tag_prefix=
persist.boottime.enable=1
persist.vmbnote.en=true
persist.landscape.en=0
persist.vmapps.orientation=true
prop.gpu.vendor=Qualcomm
prop.gpu.renderer=Adreno (TM) 650
persist.root.enable=0
sys.root.enable=0
vmprop.dev_ashmem=0

 

[hemil]

Vmos on proxies from Google cloud. From my experience sounds like worst setup ever. Honestly imo you are just wasting time. TT has a team of developers who are working against you. The odds are not on your side. What are you after? Money? You will loose much more time (money) battling TT antibot team only to realize you can't.
A used android can be bought for under 100$

You are trying to perform a brain surgery using a hammer and a stone

Ok now i tried with surfshark vpn with dedicated ip same problem "maximum attempts reached". I changed everything with android faker and checked with vd infos everything is changed. still same problem.

 

[Bamboo Agency]

I don't think it's very feasible, for long term you should try another solution