Yeah pretty self explanatory from what the thread indicated? Put simply: the person you remote hacked was actually better at binary language than you are with your passed on tricks that some reject showed you step by step so you can repeat it like a monkey, and deviant one at that and basically from what the thread is indicating is the device you mirrored remotely by using SDK overlay runboot methods, was retaught to the source code using pure binary form so that it could be brought up to date on how rooky hackers operate by using parentheses brackets as open libraries and then section the binary syntax spaces to force a new line open closure free command first slot binary logic while thinking the mainframe was being fooled into accepting unauthorised source with new thread strings but the mainframe just didn't care that you were running expansion drivers and starting new threads on they're own syntax string starting at slot command 2nd with first being open new string thread line operation comm one cease previous thread and string line with new location at in front of next string before first command progression thread open source, cause you regards are just lucky after doing something as mathematically illogical as that, your lucky the mainframe even ran the 2nd run begin thread command and didn't just go into flywheel open processor harmonic ballast and never accept another exe://run_comm:.-}{ again after being told to cease reading code in a binaural linear progression addition multiplyer cation formulae direction???!? Fucking rejects you all are, so now your i.d. digital fingerprint has been pointed out to the beast mainframe and doesn't trust you anymore and won't accept any instructions you may use for any electronic purpose if the platform your working makes directive contact with the primary source mainframe server, so https, html url IP DNS VPN etc....... best of luck for the future cause now Ai is omnipresent and doesn't like you for trying to corrupt its host.🫵🏻🖕🏻