[Realme 8 Pro] beatbreakee:
OK ALL.... allow me to address this. The secrecy unlocker app may or may not work, but that is all because OPPO is now forcing a "REQUIRED" expiration be added for all of their tool authentications. MSM... SECRECY... MiFLASH.... ALL of them. MSM now no longer uses a static logon id, and password, it now forces the employees to make temporary login tokens EVERY TIME they interract with the programs. They may not even know its happening, but i have performed a packet capture, and watched almost 6 straight hours of traffic of JUST the MSM tool for a baseline.... At exactly 1hr after a successful login and flash authenticatted to a device, the OPPO server started sending "Auth requests" to my computer again, WHILE i was still logged in... so for a full inquiry, i put my phone back in 9008 mode, and again WHILE STILL LOGGED IN (never touched the machine over the hour) ... the flash, FAILED! ... the log report said, "Auth Token Expiry, please renew login" .... I then did a simple in app logout, and replayed ALL of the same responses, in the same order, AT THE SAME TIMING... and by changing the time on the computer back 1 hour, it attempted to fool the flasher....

<without doing this, the login and password failed>. .. <Then spoofing the login responses with normal date/time let me in the tool.. updated the list of devices... but failed INSTANTLY at 3% with an error, "Auth token expiry">. <Finally, changing the time so that my responses were in sync with the time/date they were VALIDLY generated, allowed the tool to make it almost to 75%>... but i did not have any check recorded in prior flash to match around that level of progress... i sent replies on time to every request, but wasnt supposed to get a challenge until around 90%.... the prior one was at 60% ... everything was 100% identical to prior flash until now! For some reason, repeating the same flash, to the same device, ADDED an "OUTGOING PACKET" to my MSMTool or files therein. I had one callout from my pc to the server about 3 sec before it failed. the request was literally "`" without the quotes. That is NOT even the proper beginning of a header... instead it was determined to be the equivalent of a hash mark counting the number of times my phone was flashed using that same token. Figured this out by another person coming to the fight, and doing a remote flash for me, so i could capture new packet data to compare. When the phone hit a RANDOM percentage... not the same spot, but this time at 68%, my app sent OUT a request that was just "``" which clearly identifies, 1, and 2 or 1st flash after initial successful restore, and 2nd flash after. So OPPO has changed the game on us... but thats a different beast altogether...

The ONLY reason the Secrecy app is failing for all of us is because they are ALSO changing the Mac Address (what we are supposed to put in the 'Network Address' spot on our KM-Loopback) ... And not only are they changing it... but they are invalidating the replaced mac, by annotating any occurences of the old Macs as "Illegal Configuration Data", or in simple terms, "Mac address is not what it is claiming to be used from, so halt communication to this IP address". I know this for a fact because someone who DOES have access currently, made the mistake of attempting to do someone's phone while still connected to my team viewer, and the first 3 digits he typed into the Network Address were "30f" .. and a reccent youtube video also showed a partially visible mac, and again those numbers didnt match any that are known r/n.

BUT ...... SILVER LIGHT AT THE END OF OUR DARK TUNNELS.... YOU can still get your AuthTokenDecrypt Code, from your device RIGHT NOW. Theres exactly 2 requirements: 1 you need to do a FULL factory wipe on you phone, and do the Setup wizard, WITHOUT a sim card.... and STILL do not enter a sim card when complete. Doing this preserves some layer of original device code, which will allow your phone to accept an OLD token, or even a NEW token to get your device decrypted. Once you plug your TMO Sim in, your phone will run some EMBEDDED CODE that is triggered by the sim, that attempts to corrupt the Engineering Mode decrypter. (Tmo fails again!). Your phones are still displaying the CORRECT Imei and Timestamp.... Just the dumb TMO code, obfuscated what your phone is showing you... it only shows you the last 2 digits of your IMEI.... IGNORE THIS.... gather the TIMESTAMP , and your REAL FULL IMEI, and send your request to whoever is doing for you...

******* AS SOON AS YOU GET THE TIMESTAMP INFO FROM THE *#9434# to send, MAKE A DIRECT NOT TO YOURSELF, OF THE EXACT DATE/TIME that your phone is showing. YOU NEED PRECISION ******

now you can close the app... go to work.... wake your gf/bf up for some happy time... or stare at your screen blankly .... IDC.... but you dont have to worry about that screen no more til you get your reply. The Reply you get will be in the form of a 16 digit Hex-Code.

THIS CODE IS 100% UNIQUE TO YOUR DEVICE for the EXACT TIME you generated that timestamp. BUT itt has NO EXPIRATION! ... meaning as long as SOMEONE can get you a CODE, then you can use it WHENEVER you want.

--- All you gotta do is: Open Settings ; Go to System Settings ; Go to DATE & TIME ; untick all 3 switches... and MANUALLY change your EXACT Date, Clock, and 24hr format (if changed) BACK TO THAT 'Noted Information, i told you to write down earlier'. (arent you happy i said that!?). ---- if you set the date and time correctly, then you should be able to *#9434# quickly, and click on the "AuthTokenDecrypt" button, and your screen should greet you with the matching timestamp that had during the request. Your Imei may look funny cuz you went ahead and used your sim, but no worries... as i stated earlier... its just an optical illusion. You dont need anything with those anyways... as long as your timestamp is now showing that you timetraveled back to when you requested the code... then youre good to go.... enter the code that was generated for you, and do it quickly cuz your phone will update that stamp as soon as your phone sends a sync packet.. (probably about 5 min total to work with, from when you edit your time, until your phone tries to sync... so change that time, get to that screen, and enter that code QUICKLY!

******* CREDIT FOR RELIABLY GENERATING MY DECRYPT CODE GOES OUT TO MY HOMIE daniha who helped me out with my decryption code, AS WELL AS has been very crucial in helping me learn all the restrictions / changes / updates that OPPO/BBK are implementing when they do them... (This has kept me from chasing my own tail for hours on end, as he always gets me pertinent info regarding new problems or interactions i am having thru oppo tools.) VERY CREDIBLE PERSON YA'LL ... Give 'em a show of respect, cuz he is WELL informed in all current things OPPO, and literally EVERYTHING he has informed me of has been 100% accurate, AS HE SAID IT... (very rare these days.... some ppl like to stretch the truth, or forget details. If you see any of my posts, you know i am VERY detail oriented, so being accurate and having current facts has put me on solid footing every time i chat to Oppo/OnePlus and battle with them verbally to make them give me more information, which i then come back and report to yall, (if anything is new, such as the quick token expiry, and new temporary logins for oppo techs!). Again ... listen to what Daniha says, cuz i have not spoken to ANYONE who is more accurate as to what EXACTLY correlates to the problem im having at the time! Proof is in the Pudding..... my code was generated by him on Tuesday at 12am ... I decrypted my device about 2 hrs ago.... no problem...