[OnePlus 3T Guides, News, & Discussion] Xennet:
Oneplus has released the Stable and Beta OREO Oxygen OS for Oneplus 3T and 3.

This thread is only for OOS Oreo. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://xdaforums.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For disabling Dm-Verity and force Encryption in NOUGAT OOS ROMs refer to my thread here: https://xdaforums.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232[/I]

Disclaimer: I am not responsible for any damage or data loss that happens to your device on embarking this procedure...

THE DETAILS....

There has been some modifications that i came across after unpacking and verifying the packages..

After extracting the ramdisk to my surprise there was no fstab file and hence no fstab entries that could be modified to disable Dm-Verity and Force encryption...

After tweaking a little i found that indeed the file fstab does exist but its not in the ramdisk but in an other location..

So i disabled the Dm-Verity and Force encryption entries in the fstab file in the new location and made a flashable zip file which will replace the original fstab file.

As [MENTION=2464043]rk2612[/MENTION] pointed out the fact that indeed the system entries are hashed out in the fstab file and the kernel takes care of the system loading procedure in OREO, I have been working on it. Indeed it is true. After unpacking the boot image into kernel, ramdisk and device tree blobs (dtbs), I came accross 12 entries in the dtb that reference directly to mount the system after triggering the DM-Verity flag. So I patched the dtb binary to clear off the DM-Verity flags and repacked the Boot images. Moreover, in OREO as long as DM-Verity is triggered, any changes made to the system are reverted back once you boot to system which has been clearly stated with the help of posts from [MENTION=2911853]BillGoss[/MENTION].

The other fact is that regarding force encryption, it indeed is taken care of only in the fstab.

So in a nut shell, to disable DM-Verity you will need to flash the patched Boot Images and to disable force encryption you will have to flash the force encryption disabler zip - The links of which are provided below. Do refer to the correct procedure explained in datail before attempting to do anything...

For all those who need an in-depth reading of the nature of patching the fstab in dtb file and my work you can refer here:

https://xdaforums.com/showpost.php?p=74326761&postcount=3

THIS METHOD WILL WORK FOR BOTH ONEPLUS 3 T AND ONEPLUS 3...

TESTED AND WORKING TILL ONEPLUS 3/3T STABLE OOS 5.0.8 / ONEPLUS 3T BETA 30 / ONEPLUS 3 BETA 39..

FOR THOSE WHO HAVE ALREADY TRIGGERED DM-VERITY ON OOS OREO FOLLOW THE STEPS IN POST 2 IN THIS THREAD TO GET RID OF DM-VERITY BEFORE PROCEEDING...

Nothing has been changed....

It is 100% stock boot image except that the DM-Verity Flag has been patched...

Links:

For ONEPLUS 3T

STABLE OOS Boot Images

Patched Boot Image Stable OOS 5.0.8

http://www.mediafire.com/file/xcsiuizziw6xckq/boot-patched-5.0.8-OP3T.img/file

Patched Boot Image Stable OOS 5.0.7

http://www.mediafire.com/file/ckn0012znn8kw8c/boot-patched-5.0.7-OP3T.img/file

Patched Boot Image Stable OOS 5.0.6

http://www.mediafire.com/file/ma4plv5vtom4ih1/boot-patched-5.0.6-OP3T.img/file

Patched Boot Image Stable OOS 5.0.5

http://www.mediafire.com/file/adxxd99bgswez8d/boot-patched-5.0.5-OP3T.img/file

Patched Boot Image Stable OOS 5.0.4

http://www.mediafire.com/file/c8ftkmwqebmrer3/boot-patched-5.0.4-OP3T.img

Patched Boot Image Stable OOS 5.0.3

http://www.mediafire.com/file/z1kut18fycm2k57/boot-patched-5.0.3-OP3T.img/file

Patched Boot Image Stable OOS 5.0.2

http://www.mediafire.com/file/hu6n544a8yhpmma/boot-patched-5.0.2-OP3T.img

Patched Boot Image Stable OOS 5.0.1

http://www.mediafire.com/file/cjxs6plcngqc5g6/boot-patched-5.0.1-OP3T.img

Patched Boot Image Stable OOS 5.0

http://www.mediafire.com/file/dxxgn7i49sxbca1/boot-patched-5.0-OP3T.img

BETA OOS Boot Images

Patched Boot Image OOS Beta 30

http://www.mediafire.com/file/b3fu93f15zd576c/boot-patched-Beta30-OP3T.img/file

Patched Boot Image OOS Beta 29

http://www.mediafire.com/file/w80wj3lql256td3/boot-patched-Beta29-OP3T.img/file

Patched Boot Image OOS Beta 28

http://www.mediafire.com/file/k3fj0u71t85jo8q/boot-patched-Beta28-OP3T.img/file

Patched Boot Image OOS Beta 27

http://www.mediafire.com/file/d1m6awl8oda5087/boot-patched-Beta27-OP3T.img

Patched Boot Image OOS Beta 26

http://www.mediafire.com/file/6c832j5y5hwk68t/boot-patched-Beta26-OP3T.img

Patched Boot Image OOS Beta 25

http://www.mediafire.com/file/6h1h1cammycdu9f/boot-patched-Beta25-OP3T.img

Patched Boot Image OOS Beta 24

http://www.mediafire.com/file/s8q750qedda5c2n/boot-patched-Beta24-OP3T.img

Patched Boot Image OOS Beta 23

http://www.mediafire.com/file/a9r6o20qc865bij/boot-patched-Beta23-OP3T.img

Patched Boot Image OOS Beta 22

http://www.mediafire.com/file/kk5llc6s43kr2bb/boot-patched-Beta22-OP3T.img

Patched Boot Image OOS Beta 21

http://www.mediafire.com/file/di3nm7ci7fn1u6i/boot-patched-Beta21-OP3T.img

Patched Boot Image OOS Beta 20

http://www.mediafire.com/file/woow4q1enart2tf/boot-patched-Beta20-OP3T.img

Patched Boot Image OOS Beta 19

http://www.mediafire.com/file/vqud6vy7k61stzt/boot-patched-Beta19-OP3T.img

For OnePlus 3

STABLE OOS Boot Images

Patched Boot Image Stable OOS 5.0.8

http://www.mediafire.com/file/6i5yblsbx7rdiba/boot-patched-5.0.8-OP3.img/file

Patched Boot Image Stable OOS 5.0.7

http://www.mediafire.com/file/1xo7e9qr521s9z9/boot-patched-5.0.7-OP3.img/file

Patched Boot Image Stable OOS 5.0.6

http://www.mediafire.com/file/98nyyirwfy2mo9e/boot-patched-5.0.6-OP3.img/file

Patched Boot Image Stable OOS 5.0.5

http://www.mediafire.com/file/12bhw4bo48lrp8o/boot-patched-5.0.5-OP3.img/file

Patched Boot Image Stable OOS 5.0.4

http://www.mediafire.com/file/io7hqnwoiy0i9v5/boot-patched-5.0.4-OP3.img/file

Patched Boot Image Stable OOS 5.0.3

http://www.mediafire.com/file/vdeq5iox0700rou/boot-patched-5.0.3-OP3.img/file

Patched Boot Image Stable OOS 5.0.1

http://www.mediafire.com/file/e1ae6d7ae45571r/boot-patched-5.0.1-OP3.img

Patched Boot Image Stable OOS 5.0

http://www.mediafire.com/file/a69c69gw6gkj860/boot-patched-5.0-OP3.img

BETA OOS Boot Images

Patched Boot Image OOS Beta 39

http://www.mediafire.com/file/3rc3t0zc543oqf7/boot-patched-Beta39-OP3.img/file

Patched Boot Image OOS Beta 38

http://www.mediafire.com/file/6ef5szt65605woh/boot-patched-Beta38-OP3.img/file

Patched Boot Image OOS Beta 37

http://www.mediafire.com/file/856w586ctt39rg8/boot-patched-Beta37-OP3.img/file

Patched Boot Image OOS Beta 36

http://www.mediafire.com/file/2l6mj266z15vbbq/boot-patched-Beta36-OP3.img

Patched Boot Image OOS Beta 35

http://www.mediafire.com/file/cguelk95o3klcki/boot-patched-Beta35-OP3.img

Patched Boot Image OOS Beta 34

http://www.mediafire.com/file/r1sd37135f3d90u/boot-patched-Beta34-OP3.img

Patched Boot Image OOS Beta 33

http://www.mediafire.com/file/vmey23ggvafw2ps/boot-patched-Beta33-OP3.img

Patched Boot Image OOS Beta 32

http://www.mediafire.com/file/7m6gxldmenen2qs/boot-patched-Beta32-OP3.img

Patched Boot Image OOS Beta 31

http://www.mediafire.com/file/2150f2hnaclc1zk/boot-patched-Beta31-OP3.img

Patched Boot Image OOS Beta 30

http://www.mediafire.com/file/5x1bcyxzihscdj3/boot-patched-Beta30-OP3.img

Patched Boot Image OOS Beta 29

http://www.mediafire.com/file/v1cm7ddtmr6tnam/boot-patched-Beta29-OP3.img

Patched Boot Image OOS Beta 28

http://www.mediafire.com/file/1afm13h8ax9d3r0/boot-patched-Beta28-OP3.img

STEPS: This is applicable only to people who have their data currently ENCRYPTED and needs the procedure only for NOT TRIGGERING DM-VERITY

USAGE FOR STOCK OOS:

1. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)

2. Restart back to TWRP Recovery.

3. Done.

4. Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual

5. You dont have to worry about triggering DM-Verity again and any changes made to system via TWRP will not be reverted back..

The 2 Prodeures given below: This is applicable only to those people who needs the procedure for getting rid of FORCE ENCRYPTION AND PREVENT TRIGGERING DM-VERITY

PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED

First of all Backup your data preferably to and usb otg or a PC for later restore. You may lose your data from your phone following this procedure...

1. Format SYSTEM, DALVIK, CACHE and then only Flash the Full Rom Oreo Beta OOS zip file in TWRP.

2. DON'T REBOOT

3. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.

4. DON'T REBOOT TO SYSTEM

5. REBOOT TO TWRP.

6. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.

7. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.

8. Flash "Force Encryption Disabler For OOS Oreo v2.zip" in TWRP. (No need to mount system. The v2 zip file does it automatically)

9. Flash SuperSuSR5 / Magisk 15.3+

10. Done.

11. Reboot to System.

NB:f you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 6 and 7 carefully you wont end up here.

PROCEDURE 2: This is applicable only to people who have their data currently ENCRYPTED AND NEEDS TO GET IT DECRYPTED and PREVENT TRIGGERING DM-VERITY

First of all Backup your data preferably to and usb otg or a PC for later restore. You will lose your data from your phone following this procedure...

1. Go to Bootloader...

2. Connect to your PC..Type "fastboot format userdata" without quotes and press enter. (You will lose your data, do back up if you need something.)

3. Don't reboot to system...Using volume buttons select boot to recovery and Reboot to TWRP.....(Very Important)

4. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.

5. DON'T REBOOT TO SYSTEM

6. REBOOT TO TWRP

7. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.

8. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.

9. Flash "Force Encryption Disabler For OOS Oreo v2.zip" in TWRP. (No need to mount system. The v2 zip file does it automatically)

10. Flash SuperSuSR5 / Magisk 15.3+

11. Done.

12. Reboot to System.

NB: If you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 7 and 8 carefully you won't end up here.

Rooting:

For Rooting use only SuperSu 2.82 SR5 or Magisk 14.3 or above seems to work for root...

FAQs:

Q: Is the boot.img file altered in anyway?

A: As mentioned above its 100% stock boot image except that the DM-Verity Flag has been patched in the device tree blobs (dtb)...

Q: My phone is already encrypted, will I lose encryption on flashing the zip?

A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..

Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose changes made to system via TWRP or lose data/apps accidentally while updating OOS...Can this be corrected by using this method?

A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..

Q: I am Rooting my phone using Magisk/Supersu then why do i need this?

A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..

Q: How to flash the patched boot.img in TWRP?

A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.

Q: What is "-Xn" seen after the OOS Version in the settings menu?

A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity...

Q: Where to find downloads and queries regarding the Stock OOS ROM and Beta OOS?

A: [MENTION=4954690]Siddk007[/MENTION] has been maintaining Stock and Beta OOS threads were you can find relevant information.

Hope you find it useful...

Will update this OP as newer OOS versions come....

Thanks,

[MENTION=2464043]rk2612[/MENTION] -- For pointing out the presence of DM-Verity checks in dtbs...

[MENTION=2911853]BillGoss[/MENTION] -- For testing out the patched boot images and providing useful posts mentioning that DM-Verity triggering reverts changes made to system...

[MENTION=5854483]akhilnarang[/MENTION] -- For helping tackle the weirdness of fstab decryption....as he pointed out the fact of clearing the system of free space to get it done...

HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...

AND IF YOU DO APPRECIATE MY WORK DONATIONS ARE ALWAYS WELCOME...