yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 General] anupritaisno1:
Just need to confirm that these files are actually official

Pm me the s3 support link

---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------

And my friend

You need to install the test certificate first !

Edit:- file confirmed legit ! Totally official, way to go, [MENTION=4844194]fareed_xtreme[/MENTION] !
[OnePlus 2 General] fareed_xtreme:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
[OnePlus 2 General] anupritaisno1:
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use

That is how I found out about this certificate
[OnePlus 2 General] xbit:
Is there any similar process por ONEPLUS ONE?

I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
[OnePlus 2 General] beaverhead:
http://xdaforums.com/showthread.php?t=2970390

[MENTION=329511]xbit[/MENTION]
[OnePlus 2 General] Spannaa:
Quick search and: http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
[OnePlus 2 General] xbit:
This didn't work for me:

fastboot oem unlock didn't work because I had a corrupt bootloader.

But this was great! My OPO is alive now. Thanks
[OnePlus 2 General] chicken99:
Thank you!!!! this worked.

I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
[OnePlus 2 General] Wagi99:
Download from your Link

https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing

the File:

OnePlus2_14_A.11_151211.rar

Extract it.

But where is the "QC Folder"

found only "OnePlus2_14_A.11_151211"

Your Link to:

http://xdaforums.com/show...1&postcount=46

is wrong. (Not complete) Error 404
[OnePlus 2 General] Spannaa:
Yep, the qc folder is missing from the zip.

The link should be: http://xdaforums.com/showpost.php?p=64674951&postcount=46

I suspect these are both down to copying & pasting the instructions from [MENTION=3062786]paultje162[/MENTION]'s thread and I'm sure [MENTION=4844194]fareed_xtreme[/MENTION] will sort it out when he gets the chance.
[OnePlus 2 General] fareed_xtreme:
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.

Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
[OnePlus 2 General] fareed_xtreme:
Updated Information with UnTamper Guide
[OnePlus 2 General] albertocastillo2001:
Hello

Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?

I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
[OnePlus 2 General] fareed_xtreme:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.

The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.

You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty :P)

Hope this helps.
[OnePlus 2 General] albertocastillo2001:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.

I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.

Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.

The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.

This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.

I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.

I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?

I assume they look at this when they get defective devices returned.

Thanks
[OnePlus 2 General] fareed_xtreme:
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.

OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.

You are right to assume I had a session with them earlier and that's how i have the files.
[OnePlus 2 General] albertocastillo2001:
Thanks for your reply.

I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.

Thanks!
[OnePlus 2 General] fareed_xtreme:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
[OnePlus 2 General] albertocastillo2001:
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?

Thanks
[OnePlus 2 General] fareed_xtreme:
Well, I guess we need to take this conversation off the thread as it might go off-topic.

But FYI, I had (and still have with my new phone) a Bluetooth Audio Quality issue and hence I had the Remote Session. However, during the session the support didn't look into the device info and just went about flashing the whole ROM again. Turned out this issue exists on the OS level on all devices and nothing to do with hardware fault.

Hence they asked me to return the device for replacement (in my case, return to the online reseller). Before sending, I had followed the method (mentioned in First Post) to untamper my device and then returned it back which was swapped for a new one.

Hope this answers your questions. Should you have any further questions, do PM me as it kinda getting off-topic.
[OnePlus 2 General] albertocastillo2001:
Thanks

If I have a question I will message you.
[OnePlus 2 General] Flatric:
Hello,

I'm stuck at step A7, my device gets not recognized by windows, but it's shown in the device manager and after a while there's a message that it was not recognized(your workaround isn't working too:/) but if I pull the USB cable out of my computer I get the typical "unplug" noise. Some additional info: I came to this thread because I unlocked my bootloader some time ago, flashed TWRP and SuperSU and everything worked fine... today I tried to boot into TWRP, but it just showed the 1+ logo 2 times and booted normal. So I decided to flash TWRP again with fastboot, as I tried this fastboot said that my bootloader is locked(WTF I unlocked it some days ago??) I checked with fastboot oem device-info and my bootloader was locked, so I tried to unlock the bootloader again but as it finished I was stuck in a bootloop... and here I am now. It would be great if I could get some help by more experienced users than I am.

Tl;dr:

No recovery, no system, locked bootloader, stuck at step A7

EDIT: Googled and found out that I should try fastboot continue, no it booted succesfully
[OnePlus 2 General] fareed_xtreme:
I am sure it sucks to be in such a situation. However, from the sound of it, Seems more like an issue of either the USB Port, cable or an Antivirus.

I have had issues installing the Qualcomm driver on a McAfee system which detects it as a PUP and blocks installation of the driver in the background. Setup will be successful but the actual driver wouldn't be installed.

If you have the time, might I suggest creating a new profile in Windows, blocking the Realtime scanner of your Antivirus and proceeding forward from there? Let us know if you managed to resolve or not as this could be informative for others.
[OnePlus 2 General] Flatric:
After about trying 100 times it got recognized and I was able to restore my device...
[OnePlus 2 General] fareed_xtreme:
Congrats on your new OnePlus 2 experience :P. Glad that your persistence paid off :P.
[OnePlus 2 General] asmz1902:
Some plz plz plz help me. My fingerprint sensor, Proximity sensor, and accelerometer and probably other ones were not working since the day I reverted from Phoenix Marshmallow ROM which was based on H2OS. I had to flash a revert package which restored the partition supported by lollipop. After that all these sensors stopped working. I tried flashing this hoping that they will work... No good... I am pretty scared right now... help please...
[OnePlus 2 General] yanowman:
Queakooom

Question....

What is the point of the tamper part if there is a really good chance of it bricking the phone? The whole point of the instructions is to reset to stick (presumably to unbrixk a softbrixk or bootloop)....

What's the pros and cons?

---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------

Its not as simple as flashing a file... Did you even read the OP little homie
[OnePlus 2 General] asmz1902:
yes I guess and I know its not that simple that's why I am looking for help! do I just have to wait for marshmallow release now?
[OnePlus 2 General] fareed_xtreme:
From the looks of the information provided, it seems like your drivers kinda have been corrupted. This tool will reflash most of the partitions except for a few like devinfo, fsc etc.

I would suggest you to reflash the marshmallow and hope this time around all partition patches will be installed successfully. I will check if there are other threads around with any other users facing such issues.

Edit: Try posting in this thread http://xdaforums.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967

The whole point behind all this is to ensure you meticulously follow instructions bit by bit and not mess up the instructions. It's for those who really need it desperately and know what they are doing or dealing with along with the risks involved.

For Example:

You buy an expensive vacuum cleaner from another country and the instruction says you need to use between 100 - 120V and without reading instructions you plug it into a 230V Plug, then the damage done would never be covered by anyone as its failure to read the instructions. Now you have a heavy unnecessary paperweight.

Hope you understand.
[OnePlus 2 General] asmz1902:
Someone over the Phoenix ROM Thread suggested me to flash persist.img again separately from this thread's recovery package. And guess what, it worked like a charm!! :):)
[OnePlus 2 General] fareed_xtreme:
Thanks for the information. So now we have one more troubleshooting step for damaged sensors. However, it is strange why the persist.img did not flash successfully for you. Anyways the persistence paid off
[OnePlus 2 General] Jakkomo77:
After flashing phoenix ROM my device is bricked! No recovery, no flashing via fastboot recovery ,no booting no,no,no.

After that procedure my opt is alive !!!

Thanxxx :)

Gesendet von meinem ONE A2003 mit Tapatalk
[OnePlus 2 General] asmz1902:
Exactly, I knew persist.img is for sensors but I didn't expect that it is not properly flashed and was thinking of some other reasons :p

Now I know, Manually flashing stuff is the best way :D
[OnePlus 2 General] fareed_xtreme:
This is the best option for your phone using fastboot:

http://xdaforums.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
[OnePlus 2 General] Chris-woods:
Reset Tamper Flag

Hello my device isn't brick but i'm looking this forum in case if i brick my device

So i don't understand the"reset tamper flag" and what is it for?

If I install a ROM(Skydragon 3.3 Oxygen OS based, CyanogenMod 13) is there a risk of soft/hard brick ?

Thanks have a nice day :)
[OnePlus 2 General] yanowman:
UNIX/Windows

Has anyone does this procedure in Linux or only windows?

I think i need to do this because newest skydragon wiped out my recovery..... but im scurrred!:rolleyes:
[OnePlus 2 General] fareed_xtreme:
This is for Windows only as it has an exe file in it that handles the flashing process. For Linux, I would suggest using Fastboot Flashing package by [MENTION=2948558]Spannaa[/MENTION],. Head over to his thread http://xdaforums.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 and you will find the 2.2.0 Fastboot package in the 2nd Post.
[OnePlus 2 General] mqweer56:
Thank you soooo much man! I had literally searched every nook and corner of XDA for saving my friend's OPT from not bricking. And that persistent RELINK driver where I couldn't find anything about it after searching soo much!

Long story short it fixed his phone!

Thanks a LOT!!!
[OnePlus 2 General] fareed_xtreme:
Nice to know that it worked out. Keep it handy (or tell your friend to keep it handy) as it is very useful should you want to revert to stock at any time.
[OnePlus 2 General] Nanostray:
hi man, I've tried your unbrick guide, but I'm stuck at the point of the program recognizin my phone. The device manager tells me RELINK QDLoader 9008 is connected, but I can't find a different line of chinese text in the program, run both normal and administrator. Can you help me with this?

Only thing that visibly works in fastboot ,a 0.5 second logo when booting and it being recognised by my computer.

EDIT: so sorry, didn't read the page linked to in the driver install part
[OnePlus 2 General] Nanostray:
alright, did as was described, but when I try to install the driver, it says windows hit an error. Something with the driver might be tampered and it won't install. When I actually get to the qualcom in the device manager, the recovery program still doesn't show the phone. What else could I be missing?
[OnePlus 2 General] fareed_xtreme:
Just to confirm. You are logged in with the driver signing disabled? Also, you have fixed the relink issue and can see the qualcomm driver in your device manager on connecting the phone?
[OnePlus 2 General] Nanostray:
Yes, when I install the drivers normally (.exe) it gives no problem, no signature problem. The phone is recognised as Qualcomm HS-USB QDLoader 9008 (COM3) right now in device manager.
[OnePlus 2 General] fareed_xtreme:
The qualcomm setup will install normally but when the actual driver installation takes place (when you plug your device), your driver will show in device manager with a yellow triangle or similar. Right click the Qualcomm HS-USB QDLoader 9008 and select properties to confirm if there are no error codes.

Should there be any error then, like I have mentioned in the first post, restart your computer with "Driver Signature Enforcement Disabled". It is different for different versions of windows. In some cases, you have to do this everytime you want to flash your phone with this tool, regardless of whether the driver is installed properly in the beginning or not.
[OnePlus 2 General] Nanostray:
After I installed the qc program, I connected the phone, and it was immediately recognised as qualcomm. What exactly is the difference between connecting with holding volume up vs normal? Because I don't really see a difference other than the phone being recognised as 900E for normal and 9008 for volume up.

Anyway, even though the program wouldn't show me it detected my phone, I just had it do its stuff overnight. When I woke up this morning, the phone was vibrating every 5 minutes and plugging in to the charger got the a proper charging screen after which the screen went black again
[OnePlus 2 General] Nanostray:
Hey,

It seemed my phone died out halfway through the flashing and it thus not completing. I left it an hour on the charger and tried again a few minutes ago and my phone is already checking the connection. Thank you so much for this guide ^^
[OnePlus 2 General] fareed_xtreme:
Awesome that you managed to sort out the issues. Congrats on your new OnePlus 2 (Oxygen OS Only) :P.
[OnePlus 2 General] Nanostray:
Maybe an idea to add to the guide that there won't be a changed line in the chinese program necessarily. I flashed my phone without having any changed line in chinese.
[OnePlus 2 General] Yo_MaMa:
Can someone confirm is this is working correctly on North American version? (A2005)
[OnePlus 2 General] SpaceBo:
Amazing!

Damn, this is so nice :D :D Finaly my OPT is booting!

Awesome Guide! Thx!
[OnePlus 2 General] fareed_xtreme:
This should work on all versions of the OOS. The thing is that the Modem Partitions etc are not re flashed by this and hence, it should be generic.
[OnePlus 2 General] LifeFsky:
Hey! I used 3 hex editor but they are ****,what hex editor you used? thanks!!! i want to untamper :)
[OnePlus 2 General] KingJames1996:
Hi, i'm doing this guide, and after install test certificate and Qualcomm drivers, the phone is connected to computer with the name Qualcomm HS-USB QDLoader 9008. But, when i start MSM download tool give me this. Please, help me, what do i do now? :(
[OnePlus 2 General] thedeamon:
You are ready to go, from the image attached, I can see you phone ( in DOWNLOAD Mode ) got detected against a COM port number.

You have a "Com" entry on one of the ROW in the tool, that is the soft COM port via which the flashing will take palace over the USB connection.

Just select that row & click start.

It should flash (It might take a long time to flash System.img and or Userdata.img sometimes)

It ( that row text ) will show green once its done, at this point you can disconnect device and hold power to reboot.

You should be fully restored to stock ROM, Enjoy !!
[OnePlus 2 General] thedeamon:
Filename: OnePlus2_14_A.11_151211.rar ( This is for Oxygen OS 2.2.0 )

Pre-Flash Step:

Within the above RAR bundle , you will see a DRIVER.ISO file.

Extract this ISO file to install the Serial to USB driver for OP2 phones in Windows

Flashing Technique:

0. Ensure the Phone is OFF.

1. Extract the rar bundle and open "MSM8994DownloadTool.exe" with Admin right

2. Connect the Phone ( Powered OFF ) to PC & wait till all the animations are over & you see only the black scree with charging LED as RED.

3. Now take the phone in "DOWNLOAD Mode" which is the special flashing mode by holding down POWER + Vol-UP together & wait till you hear a device detection beep in Windows. The RED charging LED will also be OFF at this time. This state of the phone will initiate Windows to start loading the Serial-USB driver. At this time release the buttons.

4. Once the driver is loaded without any error, look if your phone is detected in the tool's list. Everything is Chinese but you will see one different entry in column # 2 in the list saying "Com". If not, check connection with PC.

5. First click the right square Chinese button. This will verify if all downloaded files are successfully downloaded and that the MD5 is correct.

6. When everything is ok. Select the row which has "Com" entry on it & click "Start" and let the progress finish when the text color in that row changes to green.

7. When it's done wait for the Phone to reboot. Disconnect the USB cable and Click stop on the tool & exit the Tool.

Happy un-bricking of your OP2!!

Note: This procedure will also enable boot loader unlocking if it was re-locked earlier.
[OnePlus 2 General] LOL9988:
My device doesnt detect in download tool. tried the RELINK solution too. It has RELINK issue in device manager all time
[OnePlus 2 General] 12parsa:
Not working download link

I can't download Qualcomm driver :(
[OnePlus 2 General] fareed_xtreme:
Added Google Drive Mirror for the Qualcomm driver in first post. Use it in case of issues with Mediafire.

https://drive.google.com/open?id=0BxFd4Zc3_d1CQ0diTmE5SF9ZVnc
[OnePlus 2 General] white43:
Thought I'd add to this as I'd just reset my phone with some pain.

Followed the instructions - but I constantly got my OP2 connected as an unknown device(error 43) and despite trying to update the drivers using the QC directory, I was constantly told it had the latest drivers.

So.

I uninstalled all Qualcomm drivers, using the setup.exe to remove the drivers.

Reboot

Reinstalled the certificates

Reinstalled the Qualcomm drivers

Installed the Serial to USB drivers as detailed in a post above. (#56)

Reboot

Connected phone and although it connected OK, there was an exclamation mark - insisted on a reboot.

Reboot

Phone is then detected again as USB unknown. So hold down power and the volume up button, so the power light comes on.

Hold down the up volume and power again, power light goes out.

Phone then seems to connect as Qualcomm device as Com3.

The important thing is that the phone is detected and it sees it on a COM port in devices manager. Even though it may detect the phone as Qualcomm, if it doesn't assign it a COM port, it won't show in the software when you run it.

I found, after doing the above, at times I was seeing it assigned the driver, but not the COM port, so the software didn't see it. So after putting it to 'power' mode, (volume up and power) - this would see the light - and then again, to see the light go out, I was eventually assigned COM3. When I ran the software, THEN I would see a difference.

Ran a check and the first time, it failed (right hand panel in the app). Ran again and passed.

YOU MUST SELECT THE DIFFERENT LINE and then click start.

So, also, when you phone boots up, all that's changed is the OS and the bootloader. YOU STILL NEED TO FACTORY RESET to get rid of all your old data. I hope this helps someone, as I had a bit of a ballache with this one.