STOP BOTTING 0.39 API IS BEING FORCED NOW.

[Silph-Road]

STOP BOTTING 0.39 API IS BEING FORCED NOW.

Bot might work, but you will get flagged and banned.

**1. The Official Apps forced to use 0.39.0 API.

2. All bots are .35 API
3. Niantic will let you connect with not authorized .35 API
4. Now they know 100% you are bot account....... BAN.**

WE DO NOT HAVE SOLUTION TO NEW 0.39.0 API & DON'T HAVE ETA.

[TriNtoro]

OK boss... wait untill clear

[vfuyong]

@Silph-Road How did you know?

[vfuyong]

Oh it is..I was just forced to update

[MaximusP]

Any update necrobot for API 0.39?

[Raverbunny]

I also got force updated today. (Aus, on Android)

[zc3721]

now it shows where u got the Pokemon, I think all my accounts will be banned lol.

Raverbunny notifications@github.com于2016年9月26日周一 00:33写道：

I also got force updated today. (Aus, on Android)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Necrobot-Private/NecroBot/issues/285#issuecomment-249499062, or mute the thread https://github.com/notifications/unsubscribe-auth/AVESRC1MO7rZZMxWJDPr7VkfNeh47FDVks5qt3VMgaJpZM4KGKMm .

[BoydTM]

zc3721 - the fact that new apk shows pokemon source location only means that they start to use data which was ALWAYS in niantic database. I am no developer but i guess that sniper aps are giving to API original coordinates or something like original spawn point id (some data which clearly identifies creature as sniped) Conclusion - long distance sniping (involving teleport) is completely pointless if you wish to hope that your account will survive

[mo0ojava]

This is no news. The location of caught Pokemon were in the official client a few versions back afaik but the visualization was removed. Now it's reappearing.

[Silph-Road]

^

[langit7]

necrosocket and msniper still gathering data.. so the 0.35 API still get work?

[Silph-Road]

1. The Official Apps forced to use 0.39.0 API.
2. All bots are .35 API
3. Server will let you connect with not authorized .35 API
4. Now they know 100% you are bot account....... BAN.

[iwean]

.... a few versions back (with the map/location) :thought_balloon:

[ckchiang]

Agreed with this hypothesis. Stop boting until 0.39 API released or some state changes.

[ajns73]

@dragolong No warranty stated or implied can be given on the bot. Understand, we are all cheating the system. There is never any guarantees even during times of "safe" botting.

[ValorRed]

Boting stopped. It feels like part of the life is lost. Hoho

Anyone knows the discord about the progress to crack 0.39 API?

[PenzRules]

Praise the Gods of NecroBot! They may ban our accounts but they may not ban the love we received. The love of the Gods. Thank you!

What I want to say is: I'm fine doing a little rest realizing how luckily we are.

[ckchiang]

Seems like Necrobot v0.9.7 use 0.39 API

[ajns73]

@ckchiang What leads you to this conclusion? Because you can login? I find it hard to believe that a bot from a month ago could be using an API that hasn't been cracked and didn't exist in the wild until a week ago (if 0.39 is indeed incremental and not a completely different API than 0.37)

[langit7]

the most sad thing not so many RE dev. is active not just when they change from 33 to 35.. Ibelive Nianctic did not change so much on their proto but by adding SafetyNet API ... its much harder to crack

[ckchiang]

@ajns73 http://gopokemongo-download.com/category/update/

[ajns73]

@ckchiang Necrobot is mentioned 3 place on that page in "Popular links pages." It has nothing to do with main story about .39 being live. Necrobot 9.9.7 used .35 APIs (barely. The first bot that used all .35 APIs was .9.9.5). We're now up to .39. The devs have been clear. DO NOT BOT until .39 is cracked and the bot is updated. They have Killswitched the bot and taken down all releases. Why do you think they would do all that?

[CreativiTimothy]

Hopefully when we update to the latest API for this bot, we use the most updated API available. Seem like Grover's API is the most updated, therefore the most safe. I don't mind if it's a long wait -- as long it's safer

[langit7]

I run test bot , just to know how far niantic take action again bot.

[ajns73]

I give up.

[PenzRules]

May I ask some questions about root and 0.39? Is it true that the game will say something like "incompatible" if the phone is rooted? I have a rooted Galaxy S5 G900F and with different accounts I always get "Authentication failed. Please try again." I even created a new one. It didn't even try to gain root access so how will it know? And what is SafetyNet? Is this an app I have to install, too to login? And last questions: Is KNOX warranty void or actually using custom ROM a problem or what is a "rooted phone" in the app's eyes? Either I have to completely turn to stock or they somehow may have banned my whole phone? To spoof androidId and so on I would need Xposed, but I'm afraid that this would also be detected.

If someone is willing to test if the new account is banned use this: account: keineahnung1951@gmail.com password: pleasecheck birthdate: 1.1.1951 And no, thats not my birthdate. I hope someone can help me playing the game. I may move my question to a new thread. I wouldn't have asked at all if the game would just say something like "Your phone is rooted, dude."

[iwean]

[PenzRules]

Thank you very much. So it seems it's still rooted somehow. I'll give "Full Unroot" the 5 minutes instead of two and check system/bin and system/xbin for any su file after that. EDIT: I did this yesterday and waited 2 minutes and didn't work. But now it did in 5 seconds. Well, updating the binary su after first try might have fixed it. And surprisingly i can login now. EDIT 2: Finally Magisk works for me. Sadly, restoring data backup of PoGO didn't beware it from reloading monster graphics for my main account. I'm sure I just backed up to late. Maybe will work next time.

Would it work to make the monster graphic cache files read-only or some kinda hosts-hack to reload these files from the phone itself? Could save valuable traffic for many users. Or some PoGO dev should stabilize the cache. Would reduce Niantic's traffic, too, haha.

[langit7]

good article regarding SafetyNet https://koz.io/inside-safetynet/

[PenzRules]

Well, that was a hundred percent detail, thx. P.S. It seems backing up monster graphic cache works.

[ghet2rockuu]

you need to flash magisk and phhsuuser and iinstall magisk maganager if you are rooted

[zsatanxz]

No have next vestion necrobot...??

[nguyenkhanh87]

Well, I wish you guy crack new API tmr so that we all happy to farm again. Thank for your hard working.

[PenzRules]

Thank you, ghet2rockuu. Of cource i did flash these. But first time it didn't work, because I did something wrong that prevented "Full Unroot" to work. Either I installed SuperSU once from TWRP or I flashed both phh's superuser (one for Magisk and one for without) or I might have swiped to reboot but that caused SuperSU install over it. Don't know, but flashing unSU and SuperSU again fixed it. I even reinstalled Phoenix ROM without deleting any cache to solve boot fail. So, now you know the whole story. The only thing I have to test yet if setting Titanium Backup and maybe more apps as system apps would remove the need to toggle root at all. P.S. I deleted the mentioned test account for safety reasons to us all. P.P.S.: I'm sure the devs will tell us right here when API is done, but I would prefer closing other bugs first to make it easier for them to keep track of branches. I don't know how the devs analize the new API. Limitations caused by SafetyNet may make it more difficult or maybe not at all.

[iliadc88]

Many boting people's account has been BAN today.

[ckchiang]

@erickerich Really? How do you know

[iliadc88]

many people here in my country talking about their account has been banned on FB. all of them were using necrobot or other bot.

[langit7]

Ban wave is coming to prepare trade feature

[Silph-Road]

@langit7 your source? (Trade feature)

[CreativiTimothy]

Looks like I survived the ban wave -- stopped botting before the force update. Even my spoofing sniping crazy account didn't get banned. It looks like Niantic is taking it the easy way out: they ban people based on if they're using the old 0.35 API. Other than that, they don't have any form of cheat detection it seems. My teleporting account didn't get banned -- just as long I didn't use the bot after the force update.

[langit7]

@CreativiTimothy scripts is still running on niantic dB server it's take sometimes to scan and update 100M, users. Just hold on till the script hits your account id

[Kongolan]

Was there actually any bans for using the 0.35 API all the time? Anyone?

[yandraker]

Yes @Kongolan , i got banned many accounts using the 0.35 API. BTW, somebody knows how its going the 0.39 API crack?

[Raverbunny]

@Flyingboots3 hey Niantic lapdog https://twitter.com/FastPokeMapCom/status/785528752126255104 So much trolling for nothing, i feel for ya mate....

[langit7]

@Raverbunny , Niantic here , 0.41 is out.. LoL

[Raverbunny]

@langit7 Man, how many trolls need feeding? I'm going broke for all the bait

[Raverbunny]

Maybe so, but once the Api is reversed I can't see the guys from FPM re-obfuscating it, so the hard work will be done whether it's shared or not

[yandraker]

Seems like the interest of bot creators in pokemon go is decreasing, right? I mean, in this last couple months even if the Api wasnt cracked, bot creators and people in general were like informing and working on it, but nowadays, forums are very quiet about everything related to bots. I know that the hipe about pokemon go is decreasing a lot too, but I dont know...

[BaiqingL]

The API should be cracked during sometime next week.

[Raverbunny]

We're making new progress, as we go further, we see that Niantic really went all in with their security + obufscation but nothing impossible to manage. Api will be public once reversed.

This is straight from the FPM team doing the RE work on discord

[ValorRed]

Is there any progress. I got confused information, some place said the API is out already, some place said it is Sunday.