General MSM TOOLS
- Thread starter tap77
- Start date
Can you flash your 10 pro yourself? If so, can you try to capture logs using
USBCAP? We might be able to learn how it communicates with OPPO.
I have a problem with my computer and cannot cooperate with crawling
Though this is completely off topic, is your PFP from plastic memories?
Back on topic, I don't know how else to help. When you launch your leftover MSM tool, are you asked for a login? If not, can you dumped your copy on drive or somewhere else?
Then he will ask you your model and phone number, email, the phone is used to contact you, the email will send you a file, and then he will get in touch with you and ask you what you need, I will answer the tools account password, and then he will give you Send a file, let you reply to the email when the file is downloaded, and then he will send you a remote connection
God damn, looks like OnePlus doesn't care about US users at all. What a joke. This is incredibly useful to know.
I think after sales from China OnePlus is the most likely thing, as far as I understand their working hours are 9:00~20:00
Similar threads
Top Liked Posts
-
2
Actually it was partially disclosed in an earlier post ... One of the methods for removing the login requirement ....
I didn't use this one... I edited further into the Hex and made it so I can enter anything into the user id, and password and 00000 for authentication code... But there's a few posts about this in this exact thread ... Just they are so short most ppl miss them. Also the trick in the post above only works on that version... But it should be enough to get you moving if you wanna follow that route. I just know that once you click start to flash, ANOTHER request goes out to an OPPO auth server and the Mac address/server details are obfuscated so without that, you can never generate a valid AUTH packet, and it will fail at the 3% marker every time!.... If you get lucky enough to confuse the server, which I did thru some exhausting measures, you will be met with a 3rd and 4th authentication request at 19% and 97%....
They set up some pretty good backup security in this tool just for ppl like us!
(Give yourself a pat on the back Oppo, cuz that's the one and only compliment you will EVER get from me! ... The next time you see me mention your name and the tool security , will be when I announce that I've cracked it! Cheers!)2
I do not think that will happen, nor do I advise it... While we CAN disclose the offsets that need to be changed for access... To publicly or even privately host a reverse engineered, copyrighted application not only violates XDA rules, but I'm fairly sure that can also land the host or person sharing it, in some legal trouble....
Im not 100% sure of that but I do know that asking or publishing this will definitely get u in some hot water with the xda mods! Fair warning...
There are a TON of free hex editors for windows ... Mac... And Linux that are all simple to use....download one, plus the MsM version described and linked in earlier posts... Then make the alteration yourself and voila... No trouble and you learn 1 more crafty tool!1One bit of new update guys .. the OnePlus US team DID attempt to help me, without knowing .. unfortunately we hit the same roadblock.. another dead link, but the funny thing is... It's the SAME link, but on a European OnePlus Support website.... I'll share the link below, and a screenshot of the email... There are too many breadcrumbs sprinkled across the internet for this file to be "unobtainable". Mainly FRESH OnePlus Support sites disclosing the exact file! Maybe we need an Obox account... Idk ... But even when you take the deep testing link, and switch SBOX in for OBOX.... Then delete everything after .com... The website it takes you to is an OBOX login screen.... Which says OPPO at the bottom..... Please join the hunt... We're almost there... This is like a scavenger hunt for techs.... I think that Oppo simply either region blocked this file to mainland china, or simply stopped sharing it, cuz it's not "404 not found" ... It's "you request timed out" ... As in some part of the data submitted to access the file was not sufficient , so the server timed out due to a failed request for further info.
Norway Support -
7GOOD GOOD... Thats what i like to hear from my Android Brethren !! Hack, Crack, Disassemble, and Attack the weaknesses of these infernal devices !!! (I need sleep!) ... Sorry, im stuck in some medieval, warfare mindset .. my bad! lol...
BUT heres what i came for: Humor me.....
IN THEORY... considering that EVERY post on the internet regarding DIAG mode on phone, (including IOS!) has started with the same goal.... "Using Root access, to enable Diag for access to the EFS" .... So basically everyone is saying that at the time... ROOT was horse... and Diag was the finish line! ... Right? Cuz thees guys were trying to hack bootloaders that had no accessible interface. And DIAG was their answer every time... and it worked! (Mostly)....
What i am proposing is NOT trying to hack the bootloader, because i already know how to crack that... But if it used to be a REQUIREMENT that to even discuss DIAG, you must have Root.... Then can ANYONE HERE put together a way, in which I could REVERSE that process.... or at least leverage DIAG MODE, to get myself a Root Shell.... or alter the SUID or even outright set a new user, as "UID 0" ... temporarily even if i can only force 1 app to see my account as SYSTEM, so that i can get RW access to Build.prop, or Local.Prop ?? Then i can make 1 flag change in it that will snowball me right thru the security and into the bootloader!
I mean as Diag I can literally DELETE the phone's whole identity! No imei.. no baseband... no modem... no mac address.. by the access i have to the EFS... and you cant even directly access that partition with ROOT ... only DIag and EDL have that authority! So imho there HAS TO BE a way to leverage a lower permission level thru some kind of console, where i can indirectly make a change to the build.prop. And i dont care if it Bricks the device 5 minutes later, cuz i am gonna make my change be locked with a persistent property that is already in place! It just needs a 1 in place of a 0, or an alternate access point which is also persistent, and just needs one word added to the line! Either way, if the phone bricks right after for some security violation, i will still have enough access to break the secure chain of trust and make my flags permanent! So if i have to pay for a flash to restore my phone, so be it... i know that the two things i edit survived an edl flash several times already!
I really need EVERYONE ON DECK for this... cuz getting this done will cut at least 50% of the work i need to build us an MSM - Mafia FREE edition. Im talking to the guys who still think UP UP DOWN DOWN LEFT RIGHT LEFT RIGHT B A Start, is a goof cheat code! As well as the people who can walk past an ATM machine, wave their hand in front of it, and 100's start spitting out like a money shooter... Yall cannot tell me that the Apple guys are better than us r/n ... cuz literally every time a new IOS drops... in less than a few days 3+ randos release videos as POC of them successfully gaining TFP0 , which is the IOS equivalent of ROOT.... I refuse to believe that the 17 y/o kid wearing a fedora, and a neckerchief, as they are walking up to the Starbucks counter to order their Venti Chai Mocha Latte..... NO .... I DO NOT ACCEPT THAT VISUAL! To me that worse than walking in on your parents smashing on top of the dining room table! ... at least then i know that they were making each other happy! ... But "Smuggy McMasterson III" strutting up to buy a lawn garden coctail from a coffee shop, while feeling all "chipper" cuz his team found a Kernel Memory Leak in 'IOS whogivesacrap beta 4' ... yet we cant find one privilege escalation, is the stuff of my nightmares!
YALL DONT WANNA GIVE ME NIGHTMARES DO YOU!!! I THOUGHT WE WERE FRIENDS!!!
FRIENDS DONT LET FRIENDS GET HANDLED BY A CRAPTASTIC BOOTLOADER, ,GUARDED BY 1 FLAG! COME ON!7so heres what the OTP guys are doing...
Be prepared... this is a VERY long detailed post...
so what they are basically doing is....
they are running their own "last pass" kind of server from AWS... Where they are daily logging in to their amazon web server account, and updating the MSM TOOL login, so that it refreshes every time one of them needs to pull an OTP. But its up to whoever admins the account as to how long tokens last for.
then they created (or cloned) that GA_Login tool, which is just a general purpose login tool which can be made to work with any app. It comes with modified code so that you can attach it to any program written under a certain language. (different versions of the login tool for different program languages) Then the tool officially has access to manipulate the login values of whatever app.
I believe the tool has legit licenses with the companies otherwise they would be violating the reverse engineering laws, and everyone who is profiting from it would be subject to an arresting offense! That would depend on the companies to press charges. But its easy to gain permission from a company for this purpose because you arent altering the code, only adding further security to mask passwords!
So the OTP being generated, are just a valid login that is masked by a secure password masking system. Unfortunately it is unable to be decrypted due to mitigations involved with packet capture and the login relies on an internet connection. Now unfortunately thru further inspection, the OFP flashing app DOES maintain a secure check of the VIP Authentication signature, and that signature is verified on the phone itself through a command called by the Linux Library "Libqmi" ... this can be built and programmed by anyone, but the actual procedure for JUST doing a VIP Auth signature, is not detailed on how to perform this.
THIS is what the QFIL application is doing when the sahara programmer is called.... the sahara programmer has a heavily encrypted HASHING ALGORITHM which sends one value to your phone, and then your phone verifies and calculates a response to send back to the Sahara.... The sahara already knows the correct answer even though it sits waiting, and if a single character is off, then sahara shuts down the communication portal, and sends us back an error. At that time, the phone is stuck in perpetual FAILED mode, and needs to be reset in order to try again.
The problem with this is that during a FULL BRICK state, meaning no communication without shorting the Test Points, while the battery is disconnected, then there is no way to get a valid time stamp from your device. The timestamp is part of the sahara's calculation. Thus this is why manually flashing thru QFIL continues to fail. The PATCHED Firehose loaders, simply have the TIMESTAMP requirement removed from the calculation, so that the only thing verified is the devices SOC and board information.
The MSM ONLINE tool, does its own timestamp calculations and intercepts the communication of the Sahara, then injects the current valid timestamp in real time, which then gives the approved signature to the sahara, and authorizes your flash.
Conclusion: Someone who has .elf file coding skills needs to completely disassemble the loader, which can be pulled from ANY OP 10series.... or actually ANY Snapdragon 845 r 1, based phone, and compare that to several other loaders of recent related chipsets... ie Snapdragon 845 r 2, or possibly even Snapdragon 865... but if they are fluent enough working with elf files, they should be able to locate the instruction code that requests a timestamp, as part of the signature, and delete/disable that requirement. THEN recompile that loader and we will have the file needed from OFFLINE flashes via the patched MSM Tool, or Qfil.
The login is the ONLY requirement of the MSMTool!
It is the sahara firehose itself that is killing our ability to continue flashing once the login is bypassed. Whether the phone is in brickstate or not has no value to the value being submitted to the sahara. OPPO programmed our phones to interrupt communication thru the USB, on a BUTTON, or ADB request to enter EDL mode. This is why when connecting via the command line, or thru the recovery mode shortcut, there is a slight 3-5 second delay until your phone is detected in 9008 mode.
1. When entering by holding the VOL buttons and plugging the usb in, the phone loses communication to the TIMESTAMP function, which makes the sahara fail offline, due to no MSM Tool server intervention. (remember the MSM server is not maintained by OPPO, but is actually built by Qualcomm... they just provide access to OPPO for repair functions.)
^^This will cause QFIL to fail, because a valid VIP cant be generated without the timestamp! ... But the MSM server can interject the correct timestamp being that its online and always in sync^^
2. When entering EDL via cli, the phone is SUPPOSED to go straight into QCOMM DOWNLOAD MODE... with no interruption, but OPPO amended a "Reboot" command into the opperand forcing the usb to lose connection to the board and breaking the sync, and thus forcing the timestamp to be invalid once the connection is made again with the programmer.
^^This is why COLOROS is a game changer... Because they pushed their own, RECOVERY, and FASTBOOT protocols as overlays of the REAL Qcomm Recovery and Fastboot. Recovery and Fastboot are requirements of Qcomm/Android devices. But HOW they are laid out to us are completely up to the manufacturers. The ColorOS Recovery, and Fastboot (D) that is made by OPPO, alters the timestamp being generated, to force a standard 12hr format instead of 24hr ... Sahara doesnt know wtf AM, or PM is... so anything from ColorOS is gibberish in the timestamp.
THERE IS ONE CAVEAT...
All androids with altered Fastboot and Recovery protocols, ,MUST include a "Debug Boot Image". These actually communicate to the Qualcomm diagnostic function. Although atm i have no idea how to BOOT into these images, as they are not the same as the normal .img files we use for everything else. Calling on one of these images, is a process completely different than standard android boot.img ... so again i believe this to be one of the functions of LIBQMI .... this library makes a connection to the device over usb but more importantly the SERIAL communicator console on the board. Once this communication is connected, you have full control over all partitions/filesystems inside the entire device, without regulation. You could technically tell your smartphone it is now a smart TOASTER, (but this would certainly crash immediately without the proper functions being built into the chipset.)
So now i task ANYONE who might have decent Linux knowledge to research QMI and how it communicates, to find the proper commands/access to call upon the Debug.img , which you can pull our of any downloaded fw.
I will still be working on alternate methods, but as of now QMI seems to be our only answer.
And final statement. OTP cannot be spoofed in any method to gain authorized MSM access, anymore than you being able to spoof authentication into a "last pass" account to gain control over someones password collection. They both maintain about the same level of encryption.
I hope thats detailed enough to get to everyones thoughts, as i probably wont be able to answer anything much deeper for the time being. I have personally put myself into a financial situation, by the amount of time i have devoted to this, and now need to create a miracle or 2 in order to recover from the domino effect that i hadnt realized i triggered until today. Sorry i couldnt do a hell of a lot more... if i had the financial resources to not worry about bills for a month or two i could totally crack this thing wide open, and probably put a devastating hurt on OPPO in the process... but Electricity, Rent, Car, Insurance, Food, and general living, all factor in to the amount of time i can spend on this. (which sucks because bounties are upwards of 50K or more for the discovery of holes in the functions i was working on, and according to Qcomm i was very close to a pretty high critical cve being declared!)
6
i dont recover THAT phone.... i have 2... a 10 Pro, and a 10T.... building the FREE version of the msmtool requires a TON of full captures of all the usb data being passed from device to software, to weed out the BS, and isolate the signature itself, then decrypt or find a way to spoof it.... But testing the method over and over on the exact same device does not produce me enough variables to know if my findings are valid FOR ME... which will help no one... or if they are valid for ALL ... and for that I need the data which my 10T will provide.The thing I don't understand is HOW you recover the phone after bricking it?
))
Isn't this the point of all this efforts? To find a FREE way to flash the bricks?
the 10Pro uses the Snapdragon 8450... the 10T uses the Snapdragon 8475 ....
BOTH models use the same board config, TARO..... the only big difference is the cameras....
ive completely eliminated the sign on necessity for the tool... so far my mods have successfully patched out the entire login script. So on the newest MSMTool... mine opens right up to the choose your device screen, ... but there are 3 major verification checks that happen during the flag.... 3% a VIP or AUTH token is requested by the app... I think i have isolated the process on the phone that generates the validated response..... (1st good find... because that means if the next 2 are also generated BY the phone.... I can trash the hell out of the programming inside the MSM tool, that sends ANY KIND of network request!.... If all the tool needs the net for is the LOGIN, and everything else is validated by the phone, it proves the EDL flash can be completed offline! Tag in the LOOPBACK adapter again to fool MSM into thinking it is still online.... remove the login segment of the tool.... drop in a few shell commands to trigger the intents that i believe the AUTH signature are coming from.... and if that all goes well on 2 DIFFERENT devices, then i know it will work on ALL in the 10 series..... capice?
oh, and HOW i keep recovering my 10 Pro is thanks to a buddy who you have spoken with in the past few replies.... Canuck ... he is supplying me with OTP credits he purchased to help me do this research... each token lasts 24 hrs... which gives me around 2 - 300 flashes... IF i needed that many... but i usually pull about 10-12 ... i have captures of over 500 successful flashes and now have started finding REPEATED DATA overlapping thru several captures.... meaning none of that data is part of the encrypted AUTH signature... In my 27 years of programming... and 14 specifically with android... I have NEVER seen a truly encrypted Hash value EVER repeat the same sequence of an entire row of encrypted code... let alone even 64 characters..... well i have about 90 pages that have this in common! so that makes the amount of data i have to isolate even smaller..... more flashes.... more eliminations..... more repeating crypto segments overlapping on other flash captures, more characters i get to delete from my control group....
you see... THIS is old school hash calculating by reversing the code.... eventually you will have several lines of code which are 100% different on every full capture.... THAT CODE, is then used as a kind of reverse captain crrunch decoder ring..... you plug in some common fixed variables.... until you locate a set or maybe 10 sets that all produce the same exact "value tables" as i call them.... but more formally, the ALGORITHM that when applied , generates the exact number of characters required in a valid AUTH token, and then you plug that result into a blanked pre-formed response packet then replay or inject it via a script with the timing set for the correct intervals... and PRAY that you didnt miss some little variable way earlier which breaks your entire data set!.... (normally this doesnt happen.... but 9 out of 10 times i also dont have to work this hard to strip the tables from the encrypted packet. I usually have SEVERAL different attack platforms... or devices... game consoles.... files.... whatever it is that all are locked by the same apparatus, so i can generate much less collections of the info being sent between the Challenge and the Response packets.
think of it like this.... if you have to pick a barrel lock, but rather than force it open and damaging it, you instead opt to forge a master key...
to do this you would either need a model of the working key.... (like having the signature given to you... which isnt gonna happen...) OR you would need to get as many different keys that FIT the lock, as you can find...
Once you have a solid control set, ( copies of all of the keys that engaged at least 1 pin inside the tumbler without twisting or manipulation.... all of the tumblers pins MUST be engaged for the key to spin the lock to OPEN)
If you have 20 keys that all engage at least 1 pin... then you group them off by which pin they set... and now you have the ability to compare those in each group and find the matching cuts in the key. The more you have , the more you have to examine! The more you examine, the more you will find keys that overlap into other groups because some keys will engage more than 1 pin ..... now you get to eliminate ENTIRE GROUPS cuz u only need the one that matches 1 pin in multiple sets....
the goal is to get at least 10 grooves / cuts identified, so you can record the location and measurement of each working pin setting... depth... size and width of the groove... ( on lets say a Coke machine, it has a barrel (tumbler) lock that protects the money collector. Those usually have 10-set cuts in the barrel key ... you need all 10 cuts to be precise or the lock wont budge. BUT if you have 10 keys that each engage 1 different pin in the lock, you can map out the position, depth, and cut needed for each pin, and forge them onto a blank uncut barrel key using nothing more than a rotary tool and a diamond tip engraving bit.
once all your results are transferred onto the blank then you should be able to push it in the lock and turn the key with ease!
well the EXACT same idea structure works when cracking mathematical algorithms ...
in this case, having NOTHING but hundreds of copies of the same key will not help, as you need MORE different keys to isolate perfect segments, and eliminate garbage. well i actually have 2 keys... but 1 of them is being blocked from testing, by an immortal bouncer named T-Mobile Bootloader Lock!
( i dont know if humor helps other ppl relate to something, but it works wonderfully for me!)65
nope... not for this screen... there are 4 total password protected screens in engineering mode... 2 of em are 6776 ... the other 2 have 1 that uses a 10 digit code, and the other is between 1 and 16... frustrating because both of the screens have hidden text that is blocked by the password request and pressing cancel exits the screen.
and as far as the extreme method, that has no concern to me, because it would do no good cheating by changing the processor... cuz then how would that help anyone else?? unless someone is sitting on a hoarded supply of a couple thousand & they are just giving them away.... plus a technician somewhere doing processor swaps for free. lol
naa im good.
WHAT I AM THINKING ABOUT THOUGH is :
Does anyone here remember a WHILE back, there was some Sony and HTC and Motorola phones that all had some crazy locked bootloaders?? The technique that ended up working reequired shorting out something on the board , then connecting the usb, and opening a flash programmer...
Im not saying that my phone is anywhere near having to do all of that.... BUT ive already had the back off my phone before, so does anyone know where i might find schematics for the OP 10T? that might guide me towards a jtag diagram at least.?
I am fully confident that just about every device in current production has a fail safe built in... and i know for a fact that for that the Pixel 6 has an old failsafe built in.... its called "Android Rescue Party" ... and its triggered in 3 stages, but the conditions have to be exact.
1. after 3 consecutive failed attempts to boot into the OS after a System Update initiated by the normal System Update, (cant be a local update or any flash not pushed by the system) the phone will attempt to boot into recovery mode. Once in recovery you are supposed to attempt a Factory Wipe, and reboot.
2. on the 4fh attempt which is after the factory wipe, it fails to boot again, the phone will again boot to recovery and it will perform a wipe itself, and reboot when complete..
3. on the 5rh failed boot, the phone will reboot and crash into fastboot. Where you are supposed to then wipe and flash new images to the partitions.
Now from what ive read, this became a regular thing in android 10, but theres no document anywhere of it being removed. And the conditions that must happen cannot be from a Forced reboot... the phone has to not detect any outside interaction with the device while its basically looping.
Now i know many of us have experienced boot loops on our 10 Pro & some on 10T... but im fairly certain that all of us who did, got it by flashing a rom thru local update, which breaks the rule. So what im thinking is i find the connecting points for a jtag, and use different combos to short them out. Cuz a jtag intercepts the boot process, and i am confident that i can find SOME WAY of breaking communication between the on board Storage, and the SOC but i dont wanna go blindly shorting things out and blow up my phone lol..
I am getting desperate, and it seems like the upper level hackers just are not interested in helping me. And i say this because back in the Galaxy S7, S8, S9 and S10 days , in another thread of XDA, we were assembling POC escalation attacks from CVE reports to gain elevated permissions for temp root and such, like it was beer pong... every couple of days someone else found a better way to break the security. AND THAT WAS ON SAMSUNG DEVICES... No bootloader unlock even possible, yet we had bootleg versions of TWRP.... customized hack recoveries... and pieced togther linux or windows applications that had to be loaded at the exact right time , just to get us a root shell, that we could then edit system files, while not breaking knox. (i guess we were more hardcore then... it was before the entitled kids took over the tech scene....
"Whats a Jtag, and will it match my Supreme track suit??" ...
" DO WHAT?? OPEN MY PHONE UP? ... OMG I DONT THINK SO... Like Ill just call geek squad or something..."
"Forget all that, wheres the nearest Genius bar, im gonna buy the new Iphone!"
UGGHHH.....
but for real... these apple "hackers" are running circles around us now... its embarrassing yall... GET IT TOGETHER PEOPLE!!! .... We cant have no mamby pambty SPYPHONE LOVERS, droppin the word Jailbreak all over the place, and making US look weak! When jailbreaks are SOFT anyways.... They dont even mess with the actual FW on the phone anymore... Most jailbreaks are not persistent, and alot of em are deactivated simply by rebooting the phone!... wheres the risk factor and stress induced in that??? Aint no real "brick scares" cuz they can just reboot! That is the danger equivalent of playing FULL CONTACT, FLAG FOOTBALL! WE ARE ANDROID PPL.... WE DONT GOT NO FLAGS ON US, EXCEPT THE OCCASIONAL FLAG THROWN BY OUR DEVICES, DURING A BOOTLOOP! ... We dont have TRAINING WHEELS LIKE IPHONES!!! ... ANDROID Phones are taking your kid outside and making them learn to ride a bike by throwing them the keys to a Harley with no helmet, and just telling them to "Hang On!", then duct taping their hands to the bars, & firing it up... yank back the throttle right before YOU dive off! WE ARE ANDROID ENTHUSIASTS!! ... we dont "jailbreak" and fix failures by no REBOOT!!??? When we fail, we take the whole dang OS with us! Recovery and ALL!! Why??? cuz Android users are hard like that!!!
NOW WHERES MY ARMCHAIR ENGINEERS AT??? I NEED THEORIES PPL.... SPECULATION..... ANSWERS THAT SOUND CONVINCING ENOUGH THAT I FEEL CONFIDENT IN YOUR IDEAS TELLING ME WHERE TO PLACE BARE WIRES CONNECTING TINY TERMINALS, AND THEN PLUGGING THE DEVICE INTO AN ELECTRICAL OUTLET!
My fire extinguisher, and soldering rig are getting bored over here!!!
-
18I found out how to bypass the login prompt. Whether or not the tool will actually work is yet to be determined.
I don't have a oneplus 10 pro, but would be really curious if this works for anyone.
In order to avoid potential legal issues, and so you don't have to trust any files I upload, here are the instructions to crack the msm login...
Using a download from the previously-linked rar, you should have a copy of 'MsmDownloadTool.exe'
Use 7-zip to open the exe as an archive, and extract all the files into a new folder.
Open 'FTGUIDev.exe' with a hex editor (HxD is good)
Find the hex value '0f84e7000000b8'
Replace the 84 with an 85
Save the modified exe and launch it.
Choose a server other than 'in company'
Put whatever for userID/Password/Verify, click login.
I hope this is useful.
9BTW... I am STILL in need of someone to share me access to a MSM Tool account that is active... Again... i dont care if its a guest account... or regular. You can change your password 12 hours after you give me the login info.... I am VERY close to being able to spoof an authentication, and signature response back to the phone in order to allow generic flashing of the 2213, 2215, and 2217. I just need to do about 2, maybe 3 more flashes, an hour between each, so i can decipher the algorithm that generates the token for the response. I have 9... i need 12, as they are partially calculated by a timestamp. So ANYONE who can help me with an account that is active, and maybe it is close to expiring anyways, please DM me, with the info to gain access.
I am working under an authenticated letterhead, permissions document sent to me by Qualcomm, which completely supercedes ANY legal action brought forth by Oneplus/Oppo/BBK. The letter expressly provides me permission to use any of the tools/functions which are originated/derived from a Qualcomm Tool in any fashion. MSM is written and designed by qualcomm. I am permitted to use whatever, in the "Research, and Penetration Testing, of any and all protocols called upon by a function of any process that begins in a device with a qualcomm chipset.!"
They make the MSM Tool... but access to the servers which are used to flash each qualcomm device is controlled by their respective manufacturers.9Hello all, i am here to leak OPPO tech tool that allows one plus 10 pro to be flashed. Sadly i cannot share login but if you are able to bypass login screen the tool does not need to authenticate with server to flash device in EDL mode. Attached is screen shot of login screen and file. The tool picks up device in EDL mode and allows user to select the OPF file associated for device (please note you must have this downloaded externally ideally from msm tool for your device)
I wish you luck bypassing this login and fixing your phones.
7GOOD GOOD... Thats what i like to hear from my Android Brethren !! Hack, Crack, Disassemble, and Attack the weaknesses of these infernal devices !!! (I need sleep!) ... Sorry, im stuck in some medieval, warfare mindset .. my bad! lol...
BUT heres what i came for: Humor me.....
IN THEORY... considering that EVERY post on the internet regarding DIAG mode on phone, (including IOS!) has started with the same goal.... "Using Root access, to enable Diag for access to the EFS" .... So basically everyone is saying that at the time... ROOT was horse... and Diag was the finish line! ... Right? Cuz thees guys were trying to hack bootloaders that had no accessible interface. And DIAG was their answer every time... and it worked! (Mostly)....
What i am proposing is NOT trying to hack the bootloader, because i already know how to crack that... But if it used to be a REQUIREMENT that to even discuss DIAG, you must have Root.... Then can ANYONE HERE put together a way, in which I could REVERSE that process.... or at least leverage DIAG MODE, to get myself a Root Shell.... or alter the SUID or even outright set a new user, as "UID 0" ... temporarily even if i can only force 1 app to see my account as SYSTEM, so that i can get RW access to Build.prop, or Local.Prop ?? Then i can make 1 flag change in it that will snowball me right thru the security and into the bootloader!
I mean as Diag I can literally DELETE the phone's whole identity! No imei.. no baseband... no modem... no mac address.. by the access i have to the EFS... and you cant even directly access that partition with ROOT ... only DIag and EDL have that authority! So imho there HAS TO BE a way to leverage a lower permission level thru some kind of console, where i can indirectly make a change to the build.prop. And i dont care if it Bricks the device 5 minutes later, cuz i am gonna make my change be locked with a persistent property that is already in place! It just needs a 1 in place of a 0, or an alternate access point which is also persistent, and just needs one word added to the line! Either way, if the phone bricks right after for some security violation, i will still have enough access to break the secure chain of trust and make my flags permanent! So if i have to pay for a flash to restore my phone, so be it... i know that the two things i edit survived an edl flash several times already!
I really need EVERYONE ON DECK for this... cuz getting this done will cut at least 50% of the work i need to build us an MSM - Mafia FREE edition. Im talking to the guys who still think UP UP DOWN DOWN LEFT RIGHT LEFT RIGHT B A Start, is a goof cheat code! As well as the people who can walk past an ATM machine, wave their hand in front of it, and 100's start spitting out like a money shooter... Yall cannot tell me that the Apple guys are better than us r/n ... cuz literally every time a new IOS drops... in less than a few days 3+ randos release videos as POC of them successfully gaining TFP0 , which is the IOS equivalent of ROOT.... I refuse to believe that the 17 y/o kid wearing a fedora, and a neckerchief, as they are walking up to the Starbucks counter to order their Venti Chai Mocha Latte..... NO .... I DO NOT ACCEPT THAT VISUAL! To me that worse than walking in on your parents smashing on top of the dining room table! ... at least then i know that they were making each other happy! ... But "Smuggy McMasterson III" strutting up to buy a lawn garden coctail from a coffee shop, while feeling all "chipper" cuz his team found a Kernel Memory Leak in 'IOS whogivesacrap beta 4' ... yet we cant find one privilege escalation, is the stuff of my nightmares!
YALL DONT WANNA GIVE ME NIGHTMARES DO YOU!!! I THOUGHT WE WERE FRIENDS!!!
FRIENDS DONT LET FRIENDS GET HANDLED BY A CRAPTASTIC BOOTLOADER, ,GUARDED BY 1 FLAG! COME ON!
