Necronomicon: Okay so these are pretty big changes that go to protos level. We gotta work some more
Necronomicon: These are pretty big changes, might take up to 24-48hrs
Should be the same, depends on just how big the changes are but as far as I know you wont need to redownload it. Assuming they don't update something that could potentially make it better.
Necronomicon: Final Status Update: Niantic has now began to obfuscate the API answers. This means that we will need to update the POGOProtos and implement the new hash b1f2bf509a025b7cd76e1c484e2a24411c50f0612. Reverse Engineering an App with SSL Pinning is hard to do, thanks to git user rastapasta & cstrachan88 we able to bypass these security measures. Niantic took a big step to block Bots. But we are sure this is bypassable. Sorry for the inconvienience.
SUMMARY
API stopped accepting requests from any sources which are not the actual client. The API needs a value "unknown 6", this value was already in the API in previous versions, but now the server is validating it. Only the actual client can create a valid "unknown6". We dont actually 100% know that it is indeed "unknown6" that is being validated, but it would make sense since its a big piece of data which isnt recreateable.
It is not as easy as locating where any updates made changes because the unknown6 was already being calculated and sent in previous versions but not validated by the server.
It doesnt really matter exactly what values go into the unknown6. CRACKING/bruteforcing the code is impossible because the key alone wouldnt do it. We need to get to the piece of code that makes "unknown6". The key and the way to calculate unknown6 is somewhere within the code and were trying to find it.
We are trying to locate where the app calculates unknown6 in order to be able to recreate out own valid unknown6's. If we do that we have a working API again.
This is hard because parts of the code are not easily accessible. We need people that can decompile and document parts of the code!
Please keep the talking only about the API, no personal lives, let the programmers do their job.
Again were not looking for theories on how unknown6 is created, what values go in it. We will 99% sure only get a working API if we locate and understand the code creating unknown6.
If you think you can help, this document will bring you up to speed on the technical side of the issue. The broken PokemonGo API - Unknown6 Information Summary
GMT +1, 14:00 - Breakthrough? The programmers think they have found where unknown6 is created. Now the it still needs to be recreated and hope it actually works, that unknown6 really is what broke the code.
GMT +1, 14:30 - The dev discord has gone private due to people claiming the breakthrough as their own. They are still working doubletime on it!
are they reverse engineering the APK?Just wanted to report the good news!
A ton of devs(100+) came together to try and find a solution to the problem and they believe just solved it, they found unknown6!
PokemonGO Current API Status • /r/pokemongodev
Reverse engineering to figure out the unknown6 hash. This might take a few days to get fixed tough.are they reverse engineering the APK?
feel like I should help but if they've already got 100 coders on it...Reverse engineering to figure out the unknown6 hash. This might take a few days to get fixed tough.
Ask for permission on the pokegodev discord channel if you think you can help out. My knowledge of coding doesn't go far enough to help them outfeel like I should help but if they've already got 100 coders on it...
Bots are still down, devs have been working hard on it. Hopefully it shouldn't take another 24 hours.Any updates? Have they made any progress towards finding "unknown 6"
From Reddit:
- 8 minutes ago
Tidying up for a release.
/u/keyphact
From Discord:
[12:47 AM] keyphact: Hi all, Due to the large influx of people joinng, spamming and mass IMing the devs, we're going to lock the server while we make the finishing touches to our implementations. We will be back shortly or later. Thanks
[1:39 AM] keyphact: For all those spreading rumours that we released to a private bot first. An excited core member of the RE team implemented what we have so far (not 100% clean and done) into his bot and released a screenshot other members are implementing Unknown6 support into their non-bot projects as well (for example, see pgoapi and RocketAPI). Regardless, no matter what, everyone will have access to the finished work at the same time.
NicccccePokemonGoDev API dev's are getting ready for the release of the fixed API.

