8787 build

[Dksy]

Still not working right evweryone?

[flashburn]

such continuous ?

[15:42:36] (INFO) Amount of Pokemon Seen: 115/151, Amount of Pokemon Caught: 112/151
[15:42:36] (EGG) Incubator status update: 1.13km left
[15:42:36] (EGG) Incubator status update: 2.05km left
[15:42:36] (EGG) Incubator status update: 3.35km left
[15:42:36] (ATTENTION) No usable PokeStops found in your area. Is your maximum distance too small?
[15:42:37] (UPDATE) [Evolves] Potential Evolves: 0

Are you not even ashamed to be yet another one of "those guys"?

[Gangsy]

Good Job!

[Relican]

Remember to keep things civil and on topic here, folks.

No reason to start flame wars and insult each other here, and it does nothing to further the conversation of the post.

I'm going to continue keeping an eye on this thread, and if the people flaming, insulting, and harassing each other continue, infractions/bans will be given out. Stay on topic, be helpful, and remember that OwnedCore has a very global user-base and English is not the native language of many users; insulting someone for their typos is not necessary.

Also keep in mind that not everyone is spending all day refreshing OwnedCore for updates. Calling someone an idiot for not realising their bot was broken should instead either be solved by ignoring them, or by explained to them that, no, the bot is not currently working.

[cuocsongxanh]

someone please show me how to config this tool, sorry, first time use this tool

[Luckiesonfire]

someone please show me how to config this tool, sorry, first time use this tool

All bots are already down, so nothing's working at the moment. Keep reading for any info

[cancelled]

unknown 6 chunk is basically the 1k egg, was previously never known to be this chunk

[Mad4poko]

From Necronomicon:
@everyone Just to make sure. The /r/pokemongodev team just found the Unkown 6 Chunk nothing else. Its still takes more work. The api guys just know where to look now. Sorry for false Information!

[hayychat]

nice that it still works for evolves.



just did 240 evolves, was getting 10 mill/exp an hour for the 2 minutes that took

[slowmo1991]

go go team rocked a.k.a. pokemongodevs

[Greninjax]

nice that it still works for evolves.



just did 240 evolves, was getting 10 mill/exp an hour for the 2 minutes that took

i call BS on that

[hjyg]

i call BS on that

500xp per evo
1000xp per evo with lucky egg
1000*240 = 240,000

It'd be about one evolution every 0.5 seconds. All evos in total would therefore take about 120 seconds, or two minutes (as the guy suggested).
So that's 240k xp over two minutes, which is one 30th of an hour.

240,000*30 = 7,200,000xp/hr
or 7.2 million xp/h
Not far off I guess.

[Mad4poko]

SUMMARY/UPDATES
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!
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! I am locked out on the discord too, so no more updates from me I guess. They let me in (16:20).
Unknown6 is indeed related to API changes, meaning our worst fear is not true. That would be when we would be able to recreate the unknown6, but that was not what broke the API. In that case everything we did would be worthless. We are on the right track.
GMT +1, 16:30 - The stuff being done is very technical. From my understanding we know where unknown6's core is created. From there we are able to see what inputs it takes and which functions it calls for further encryption. We are in a steady process of uncovering more steps of unknown6 it's creation. We've still got some steps to do..
GMT +1, 18:00 - Some important part of the encryption method has been decompiled, meaning we can now read it, and run the code through the decompilation when the other parts of the encryption have been found.
GMT +1, 19:30 - One step closer to fully determining the input.
GMT +1, 20:30 - Breaktrough #2: Two pieces of the unknown6 creation-code got linked together. We figured out where the encryption is called. As mentioned earlier we have the decompiled encryption.
GMT +1, 21:15 - We now need to do 2 things:
Get the decompiled encryption into a usable state. The encryption is a custom encryption and the decompiled file was over 200 pages long. People are working on it and it is not the hardest part but it has to be done. (slow but steady)
Figure out the last pieces of input, this could prove to be the difficult part. There is 3-4 fields remaining and every field that we figure out is a minor breakthrough.
GMT +1, 22:30 - No news, other than "they are working on it", but I thought I'd write something anyways, a reflection on the last 24 hours.
It has been facinating to see the devs from this sub work together to crack the unknown6. This is the same thing Ingress-hackers never defeated. But the POGO-dev community is bigger. I have seen people work on it 20 hours out of the 24 that the API-change is live. /u/keyphact hasnt slept for 40 (seriously go to sleep). These people are tirelessly, determined. I feel like we can do this.
We found the core creation place of unknown6 in mere hours. The encryptionfunctions were decompiled and the place where its called has been found. 10% of the input and the usability of the encryptionfunctions is whats left. Were so close, yet so far away. Will we solve this?

From reddit pokemongodev dev

[kvothe0153]

@Mad4poko Thank you for the updates

[wannabehaxor]

damn the programming community is so beast! thx for the updates