Using real mobile device ID in Jarvee

ChrisMonkey

ChrisMonkey

Registered Member
Joined
Dec 7, 2017
Messages
64
Reaction score
16
I am creating Instagram accounts on mobile and use them in Jarvee.

My thought was to copy the real device ID from the mobile phone and use that as the device ID into Jarvee.

I asked Jarvee but I can't get a straight answer (like usual). So I am gonna ask here.

Is it a good idea to use the real device ID in Jarvee from the phone the account was created on?
 
Advertise on BHW
Why should't it be a good idea? You have to check useragent etc. as well, but apart from that I see no problem with it
 
barmer said:
Why should't it be a good idea? You have to check useragent etc. as well, but apart from that I see no problem with it
Click to expand...
That’s exactly what I thought. But jarvee tech support said no, that using the device ID would raise red flags with Instagram. That doesn’t make sense so i asked again and got same answer!
 
ChrisMonkey said:
That’s exactly what I thought. But jarvee tech support said no, that using the device ID would raise red flags with Instagram. That doesn’t make sense so i asked again and got same answer!
Click to expand...
well maybe because using the same id over and over again isnt a good idea
 
In fact its not a good ideia, i believe there is an app that gives you this kind of information, tho there is some information that is generated by the Instagram app itself based on the device, that info you cannot grab it easly, so for this reason its not a good idea.

Plus if you think a bit it wouldnt make any sense to have 2 sessions on the same "device" for the same account, so once again for this reason, its not a good idea.
 
Can javee do that? as far as i know, javee is web-based, how can they mimic the phone behaviors? the web-based and app-based has a lot not in common
 
toninin said:
Can javee do that? as far as i know, javee is web-based, how can they mimic the phone behaviors? the web-based and app-based has a lot not in common
Click to expand...
- Jarvee is not web based
- Both Web Based and Traditional Softwares can emulate exactly anything in same way.
- Delete the Internet pls.
 
Obviously I am not talking about using the same device ID over and over... we are talking about using 1 device ID per account

Obviously I am not talking about having 2 sessions with the same device ID at the same time. We are talking about creating an account on a unique device, removing the account from the device, wiping the device ID and other information from that device, and then using that unique device ID for Jarvee where the account will live from then on.

Come on guys, I am not retarded.

But the question about Instagram adding some unique bit of information to the device ID / Api User Agent? Well that is interesting. Does anyone have more information about this? I thought the device ID and user agent were pretty standard templates... didn't think an app was able to add information here. But that would be a reason not to use a real device ID if it's true.
 
tubatesmal said:
- Jarvee is not web based
- Both Web Based and Traditional Softwares can emulate exactly anything in same way.
- Delete the Internet pls.
Click to expand...
I am a mobile developer and frontend developer for years, some simple javascript can detect a lot of information. like for mobile app click and web-based click are triggered in different way. not saying information like webgl and canvas, I don;t know much about javee though, but i don't think they are mobile-based. I managed 3k accounts with my own system, i do know what to care and which are not important
 
ChrisMonkey said:
Obviously I am not talking about using the same device ID over and over... we are talking about using 1 device ID per account

Obviously I am not talking about having 2 sessions with the same device ID at the same time. We are talking about creating an account on a unique device, removing the account from the device, wiping the device ID and other information from that device, and then using that unique device ID for Jarvee where the account will live from then on.

Come on guys, I am not retarded.

But the question about Instagram adding some unique bit of information to the device ID / Api User Agent? Well that is interesting. Does anyone have more information about this? I thought the device ID and user agent were pretty standard templates... didn't think an app was able to add information here. But that would be a reason not to use a real device ID if it's true.
Click to expand...

If you are using Android to do it, there is a lot of "underground" information being passed and hard to emulate, also know as Device Fingerprint, Saftynet collects all the enviorment variables when the register request is made and sends this to Instagram servers ( for attestation ) and probably for analysis. When moving this to Jarvee you will probably get some new uuids generated that will not match your fingerprint, resulting in a red flag. ( Resumed lol )
 
tubatesmal said:
If you are using Android to do it, there is a lot of "underground" information being passed and hard to emulate, also know as Device Fingerprint, Saftynet collects all the enviorment variables when the register request is made and sends this to Instagram servers ( for attestation ) and probably for analysis. When moving this to Jarvee you will probably get some new uuids generated that will not match your fingerprint, resulting in a red flag. ( Resumed lol )
Click to expand...

Ok, that is a good reason not to do it then.

Maybe for fun I will just try with a test account and see what happens, and how quickly.
 
toninin said:
I am a mobile developer and frontend developer for years, some simple javascript can detect a lot of information. like for mobile app click and web-based click are triggered in different way. not saying information like webgl and canvas, I don;t know much about javee though, but i don't think they are mobile-based. I managed 3k accounts with my own system, i do know what to care and which are not important
Click to expand...

In your opinion, what types of fingerprints are detected using Jarvee with API? Is it safer with Embed browser? my goal is to hide among the mass of average users, and therefore be as normal as possible.
 
The way the Jarvee API is made is by taking the current version of the Instagram app and reverse-engineering how the private API on the app works and translating it over to Jarvee's software. This is the reason the API actions appear as if they happen from a phone and this is also the reason Jarvee updates as frequently as Instagram does. An embedded browser however is just that, a browser lol. Way easier to track.
 
Jibri Wright said:
The way the Jarvee API is made is by taking the current version of the Instagram app and reverse-engineering how the private API on the app works and translating it over to Jarvee's software. This is the reason the API actions appear as if they happen from a phone and this is also the reason Jarvee updates as frequently as Instagram does. An embedded browser however is just that, a browser lol. Way easier to track.
Click to expand...

@Jibri Wright So according to your reasoning, using Jarvee with API should be safer right?
What types of fingerprints are left using Jarvee with API in your opinion?
Second is it better to use API Jarvee with proxy 4g or with hotspots from the phone?
Which of the 2 is the safer method with API?
Let's say the method that allows it to be exchanged for an average normal user.
 
manureverse said:
@Jibri Wright So according to your reasoning, using Jarvee with API should be safer right?
What types of fingerprints are left using Jarvee with API in your opinion?
Second is it better to use API Jarvee with proxy 4g or with hotspots from the phone?
Which of the 2 is the safer method with API?
Let's say the method that allows it to be exchanged for an average normal user.
Click to expand...
Again the reason you're getting issues with a 4G proxy is because you're only tunneling the IPv4 information through the proxy. The IPv6 however is coming from a different geolocation than the IPv4. The reason hotspots are better is because either the IPv4 as well as the IPv6 is run through the hotspot or only the IPv4 is. Because this is the only connection the computer has to the internet (as opposed to running it through a proxy where YOUR modem is the initial connection) the IPv4 and IPv6 have the same geolocation and so it doesn't raise any flags.
 
Jibri Wright said:
Again the reason you're getting issues with a 4G proxy is because you're only tunneling the IPv4 information through the proxy. The IPv6 however is coming from a different geolocation than the IPv4. The reason hotspots are better is because either the IPv4 as well as the IPv6 is run through the hotspot or only the IPv4 is. Because this is the only connection the computer has to the internet (as opposed to running it through a proxy where YOUR modem is the initial connection) the IPv4 and IPv6 have the same geolocation and so it doesn't raise any flags.
Click to expand...

@Jibri Wright In all the tests I've done, the geolocation has always been consistent, as the 4g proxies are from the city where I live.
However, in the tests I did (inside Jarvee, then in an "android" system) I found that with hotspots instead there is an inconsistency on the passive os fingerprint that results windows instead of linux.
Still within Jarvee, using the proxy 4g instead is the same passive os fingerprint.

Having said that, do you think it's better to use the hotspot?
In your opinion, which fingerprints can find instagram using the API mode?
API and Hotspot can be the solution to have more consistent results?

thanks for the answers you're giving me.
 
With everything most of you guys are saying, then it would make sense to only use api in Jarvee, and not the EB.

Correct?
 
manureverse said:
@Jibri Wright In all the tests I've done, the geolocation has always been consistent, as the 4g proxies are from the city where I live.
However, in the tests I did (inside Jarvee, then in an "android" system) I found that with hotspots instead there is an inconsistency on the passive os fingerprint that results windows instead of linux.
Still within Jarvee, using the proxy 4g instead is the same passive os fingerprint.

Having said that, do you think it's better to use the hotspot?
In your opinion, which fingerprints can find instagram using the API mode?
API and Hotspot can be the solution to have more consistent results?

thanks for the answers you're giving me.
Click to expand...
The geolocation has to match EXACTLY lol. iplocation.net has it where you can look up the geolocation of an IP address in real-time. I suggest you use that to see what I mean. If your IPv4 and IPv6 don't exactly match up in real-time, that's a red flag. Even if it's the same city, geolocation is very precise.
 
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