Database Users

MIUI8.2 8.2.1.0 Global Stable For Mimax650&652

#Newupdate MIUI8.2 8.2.1.0 Global Stable for MimaxPro
http://bigota.d.miui.com/V8.2.1.0.MBDMIDL/miui_MIMAX652Global_V8.2.1.0.MBDMIDL_9060ae09fa_6.0.zip
ota 8.1.9.0-8.2.1.0
http://bigota.d.miui.com/V8.2.1.0.M...0.MBDMIDI-V8.2.1.0.MBDMIDL-b2511afedf-6.0.zip
formimax650
FullRom http://bigota.d.miui.com/V8.2.1.0.MBCMIDL/miui_MIMAXGlobal_V8.2.1.0.MBCMIDL_ad2db3ac36_6.0.zip

Does it work on mi max 32g global? Thanks in advance

Nano23 said:
Does it work on mi max 32g global? Thanks in advance
Click to expand...
Click to collapse
Yes, it should do.

Note:
Update for Mi Max / Redmi 1S suspended
http://en.miui.com/thread-501418-1-1.html
Waiting for fix the bugs

Plz. Which one is for mi max 32g global version?
---------- Post added at 12:11 AM ---------- Previous post was at 12:10 AM ----------
And how to update i am in miui 8 1.6.0

On my 32GB Global, i had OTA notification for v8.2.1.0 when i was on v8.1.6.0
Downloaded using upgrade tool, installation is ok.
Easily rooted using TWRP after.

I have no information about upgrade mi max plz can somone explain step by step how to do

Thank you very much! Full ROM work like a charm on Mi Max 3/32GB.

It's Android Nougat ?

bortoloj said:
It's Android Nougat ?
Click to expand...
Click to collapse
No, it's Marshmallow 6.0.1.

Why full rom is still unavailable for Fastboot mode ?

How can i install this with TWRP and keep TWRP and keep root and keep my unencrypted internal storage?

Is it rooted or my Mi Max root will be gone, thanks

Well, full ROM is not rooted, that's for sure. If you want to install it, do a backup before with TWRP on Micro SD. It is very recomended. If something goes wrong then you can restore your system.
For CLEAN INSTALL, on Mi Max 3/32 GB, I followed theese steps. By doing this, you will loose all your previously apps and data:
1. Download and Copy full ROM from first post on Micro SD (miui_MIMAXGlobal_V8.1.6.0.MBCMIDI_1e6706b520_6.0.zip).
2. Download and Copy SR3-SuperSU-v2.79-SR3-20170114223742.zip on Micro SD. Can be found here: download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
3. Download and Copy Install lazyflasher-no-verity-opt-encrypt.zip (a script to disable dm-verity and forced encryption) on Micro SD. Can be found here: en.miui.com/thread-310923-1-1.html
4. Boot into TWRP.
5. Mount System, Data, Cache, Internal Storage, Micro SD.
6. Advanced WIPE -> Select Dalvik/ART Cache, System, Data, Cache, Internal Storage. Swipe to WIPE.
7. Install miui_MIMAXGlobal_V8.1.6.0.MBCMIDI_1e6706b520_6.0.zip from Micro SD.
8. Install SR3-SuperSU-v2.79-SR3-20170114223742.zip from Micro SD.
9. Install lazyflasher-no-verity-opt-encrypt.zip from Micro SD.
10. WIPE DALVIK & CACHE.
11. Reboot to System.
If device automatically reboot after step 8, reboot again in TWRP (by continuously pressing Power + Volume Up until vibrate and then release and wait for TWRP) and continue with step 9, 10 and 11.
Wait 10-20 min for first boot and continue with system setup. You will have SuperSU installed.
This worked for me, but I'm NOT responsible for your actions.
More about MIUI Global Stable ROM 8.2 Fastboot and Recovery versions here: en.miui.com/thread-508000-1-1.html (Changelog and Download links).

Tried it, still on Android 6. Not much different.
Will try the beta 7.2.16.

Can NOT install MultiRom.ME
HawkXP said:
Well, full ROM is not rooted, that's for sure. If you want to install it, do a backup before with TWRP on Micro SD. It is very recomended. If something goes wrong then you can restore your system.
For CLEAN INSTALL, on Mi Max 3/32 GB, I followed theese steps. By doing this, you will loose all your previously apps and data:
1. Download and Copy full ROM from first post on Micro SD (miui_MIMAXGlobal_V8.1.6.0.MBCMIDI_1e6706b520_6.0.zip).
2. Download and Copy SR3-SuperSU-v2.79-SR3-20170114223742.zip on Micro SD. Can be found here: download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
3. Download and Copy Install lazyflasher-no-verity-opt-encrypt.zip (a script to disable dm-verity and forced encryption) on Micro SD. Can be found here: en.miui.com/thread-310923-1-1.html
4. Boot into TWRP.
5. Mount System, Data, Cache, Internal Storage, Micro SD.
6. Advanced WIPE -> Select Dalvik/ART Cache, System, Data, Cache, Internal Storage. Swipe to WIPE.
7. Install miui_MIMAXGlobal_V8.1.6.0.MBCMIDI_1e6706b520_6.0.zip from Micro SD.
8. Install SR3-SuperSU-v2.79-SR3-20170114223742.zip from Micro SD.
9. Install lazyflasher-no-verity-opt-encrypt.zip from Micro SD.
10. WIPE DALVIK & CACHE.
11. Reboot to System.
If device automatically reboot after step 8, reboot again in TWRP (by continuously pressing Power + Volume Up until vibrate and then release and wait for TWRP) and continue with step 9, 10 and 11.
Wait 10-20 min for first boot and continue with system setup. You will have SuperSU installed.
This worked for me, but I'm NOT responsible for your actions.
More about MIUI Global Stable ROM 8.2 Fastboot and Recovery versions here: en.miui.com/thread-508000-1-1.html (Changelog and Download links).
Click to expand...
Click to collapse
Hi there,
I can not install any version of MultiRom.me ROM, except this one v8.0.1.0 Global Stable. Here is the detail of my weird issue.
A. What do you have?
Mimax 3/32GB with working TWRP 3.0.3-0
https://dl.twrp.me/hydrogen/twrp-3.0.3-0-hydrogen.img
v8.0.1.0 Global Stable ROM flashable .zip file (1)
http://ua.multirom.me/MROTA/STABLE/V8/V8.0/multirom_MIMAX_V8.0.1.0.MBCCNDG_v6.0.1_b13_e685363f8e.zip
v8.2.2.0 Global Stable ROM flashable .zip file (2)
https://vroms2fe7lh.multirom.me/MRO...AX_V8.2.2.0.MBCCNDL_v6.0.1_b24_8c9ad51076.zip
SuperSU 2.79 flashable .zip file (3)
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
B. What process did you use?
Booted to TWRP
Wiped fully (system, data, cache, davik cache)
Installed ROM (saved in USB OTG)
Installed SuperSU (saved in USB OTG)
Wiped Cache & Davik Cache
Rebooted​
C. What is your issue?
If I used the combo (1), (3) and process (B), everything worked well w/o any problem. But,
If I used the combo (2), (3) and process (B), it could not boot up. The Mi logo lighted on in 1s and shutdown immediately later whenever I pressed power button.
In addition, I could not boot into TWRP too.
Now I've been in rom (1) with working TWRP, and still could not flash rom (2).
Kindly help me explain it and show me how to solve this issue.
Thanks and Best Regards,
[email protected]

Hello,
I tried to download v8.2.2.0 Global Stable ROM flashable .zip (2) but I could not access the file (forbidden). So I have no way to test the installation.
Try this:
1. Boot into TWRP.
2. Wipe (system, data, cache, davik cache and internal storage).
3. Install ROM.
4. Go to Mount -> Select , Deselect and Select againSystem. Let it selected.
5. Go to Advanced -> File Manager -> Go to System folder. In root of System it's a file: recovery-from-boot.p. Delete it. In this way, you will not loose TWRP.
6. Go back and install SuperSU.
7. Wipe Cache & Davik Cache.
8. Reboot.
It is possible for the device to auto reboot 2-3 times until the system will load.
See if this will help you.

[KERNEL][RECOVERY][LOS15.1] F2FS upstreamed Kernel + TWRP for Lineage 15.1

WARNING: I am not responsible if you brick your device or lose any data. I personally heavely tested these releases myself and have not encountered any problems.
These are built on official sources and nothing more should be broken but remember to always make backups before installing any mods, kernels etc.!
You should read everything I wrote in this thread before taking any steps unless you know exactly what are doing.
About:
Okay, so I was tired of almost not usable Magisk on official builds because of outdated Moto F2FS implementation, so I built new LOS15.1 kernel and Treble-compatible TWRP with newer version of it for myself and I want to share this with you.
You may ask why I did it and what does it change, so here's the list of features:
This combo may be solution for smooth transition from 15.1 --> 16 without losing data (Without this you will need to reformat your /data partition before flashing when the day of 16 comes - confirmed by Mike). I cannot say 100% that it give you this ability but I'm pretty sure it will!
This Kernel and TWRP applies to LineageOS 15.1, all LOS15.1-based ROMs (like RRemix) and all Treble GSI's.
F2FS loopback fix module is not needed anymore, you can directly install modules from Magisk Manager app.
Magisk modules are persistent now. They will never disappear, even when cache is cleared.
Magisk hide settings are persistent now. They will not reset after reboot.
You can now use systemless hosts properly (No ads and SafetyNet is still passing!).
Filesystem R/W speeds may and should be slightly better (I haven't tested this myself so feel free to do before-after benchmark comparisions).
Don't need to start from zero. You can restore your /data backup after formatting device and it will work just fine.
TWRP is updated to version 3.2.3-0 so it may fix OTA's on "enter pin to boot" encrypted devices.
In TWRP there's written "Lineage" next to it's version to avoid confusion, especially for newbs (Lineage because everyone's talking about LOS TWRP and it's also built on Lineage source)
"Format Data" button in "Wipe" screen is temporarily removed until I/we find fix to make it work. This feature is still broken and causing bootloops (Like on TWRP from LOS Wiki). You still need to use official one for decryption.
That's all I think. I will edit this thread If missed something.
Instructions:
* This instruction applies to new and existing LOS-based ROMs users *
* This tutorial I wrote for someone may be useful if you need help with bootloader mode(fastboot) *
Important: If you don't care about porting your /data to newer F2FS (not talking about Internal data) and willing to start from "zero" then you just should typical LOS installation steps + changing kernel (Steps 1 - 8 and 14 eventually if you're going to restore some pictures or something)
1. Do /data partition and/or Internal Storage backups if you didn't already. Pull them to your computer or SD card.
2. Flash TWRP 3.2.3-0 Lineage build (lineagetwrp.img) from the download section using method you want (fastboot one is recommended).
3. Flash latest official build of LOS15.1 (If you have it already then you can skip this step).
4. Flash bootimage (f2fs_boot.img): Install > Install Image > f2fs_boot.img and check "Boot"
5. Download latest official TWRP from HERE
6. Boot to bootloader mode (fastboot) and use this command "fastboot boot [OFFICIAL_TWRP_IMAGE.img]" to boot into official TWRP without flashing it.
7. When in official TWRP: Wipe > Format Data > type "yes". If it fails then reboot to bootloader mode (Main menu > Reboot > Bootloader) and boot it once again as in point 3 (It happens very often).
8. If formatting went fine then go to: Reboot > Recovery to boot to recovery flashed before. After it boots just make sure that it says "3.2.3-0 Lineage" on top bar like in attachment screnshot
9. Wipe > Advanced Wipe > check "Data" > Repair or Change File System > Change File System > F2FS (This step is not really necessary but it confirms that everything is set up if no errors was throwed here).
10. Reboot to recovery and put your TWRP /data backup on your Internal Storage via PC - Skip if on SD card.
11. Restore your TWRP backup.
12. Don't exit yet if you haven't restored from SD card. There's a little bug(?) where your data from Internal Storage will stay in /data/media directory but MTP will switch to /data/media/0/ after first boot so you will be not able to see that data via PC. Make sure you've deleted these files before rebooting to system. You can do this after first start too but these files will extend encypting time at least twice.
13. Finally you can reboot. In case you were using any lockscreen when doing a backup you should check THIS
14. You can put back your internal storage data right when ROM successfully booted.
Download:
DOWNLOAD - 12.01.2019
Troubleshooting:
If you encounter any problems in any of these steps you will probably need to start from step 6.
Still not able to do this or messed something up very badly so u can't enter TWRP? Try entering bootloader mode and type "fastboot erase userdata", then proceed to step 6.
Remember: After doing an OTA you will need to flash "f2fs_boot.img" once again before booting into system. Else you will end in constant reboots until you do this. Kernel will be updated when some changes will be pushed into it (not often)
Any support for this will be probably instantly dropped after first stable enough release of LineageOS 16.
Have Fun!​
All thanks goes to @mikeioannina for commiting to kuntao sources which I used here.
Kernel source
Recovery source​

Thx, I was looking for this.
---------- Post added at 10:11 AM ---------- Previous post was at 09:20 AM ----------
I reread the whole article again and better to wait for lineage os 16 and fixes. I am fine with ext4 now. No need to mess with twrp and bootloops

Well, the most complicated flashing orgy so far...

Why making another kernel for putting just 1 commit that fixes f2fs? Recovery was needed because for treble we are still using 3.2.2-0, but kernel is useless, @mikeioannina could merge that commit in official lineage kernel.

mahmutpekkara said:
Thx, I was looking for this.
---------- Post added at 10:11 AM ---------- Previous post was at 09:20 AM ----------
I reread the whole article again and better to wait for lineage os 16 and fixes. I am fine with ext4 now. No need to mess with twrp and bootloops
Click to expand...
Click to collapse
There's almost no changes in that kernel compared to stock. The same for TWRP. The real difference between this procedure and re-installing LOS15.1 is installing the kernel file. Resetting lockscreen settings (because your pins will not work) was always the case when restorong nandroid backup.
If you're on ext4 then just stay on it. Not worth doing it in your case

RayDeemer said:
Well, the most complicated flashing orgy so far...
Click to expand...
Click to collapse
It's not that complicated even if it looks like that. It's very detailed, step by step comparing to typical flashing instructions. I did this because I know that a lot of users from this forum have problems even with simple things. Like I said before: the only difference between this and reinstalling ROM with restoring /data partition is flashing boot.img. Not my fault that this treble TWRP formatting feature is broken and nandroid backups are breaking login when PIN is set.

matteo0026 said:
Why making another kernel for putting just 1 commit that fixes f2fs? Recovery was needed because for treble we are still using 3.2.2-0, but kernel is useless, @mikeioannina could merge that commit in official lineage kernel.
Click to expand...
Click to collapse
This will not gonna happen and that's why I compiled it myself. He reverted this change before it came live and I just readded it (https://github.com/LineageOS/androi...it/48c639c3581eb04693ae0771d8e85ce1151550b4).
You will probably find his post around page 50 of LOS thread about that.
He said that he will be not push this change to build since it will break LOS14 -> LOS15.1 transition when doing an OTA (user data will be corrupted if I remember correctly).
If you wondered why this tutorial is long and "complicated" like people said before then as you can see it turns out that data transition could be done with simply doing nandroid backup and then restoring it. These step are 90% of this tutorial due to bugs which are in lineage TWRP and "bugs" because that TWRP is backing up ROM with lockscreen settings which are breaking every time when restoring from backup. Also removing backup data step is necessary because these files will slow down encryption and will be not placed in /sdcard so people will forget about it probably and wonder what is eating so much space.
EDIT: I forgot to add that Mike refused my opinion about this but at the end you will still need to format your data anyway when going from 15.1 to 16. This kernel with TWRP may be solution for smooth transition to 16.

Kielbek said:
This will not gonna happen and that's why I compiled it myself. He reverted this change before it came live and I just readded it (https://github.com/LineageOS/androi...it/48c639c3581eb04693ae0771d8e85ce1151550b4).
You will probably find his post around page 50 of LOS thread about that.
He said that he will be not push this change to build since it will break LOS14 -> LOS15.1 transition when doing an OTA (user data will be corrupted if I remember correctly).
If you wondered why this tutorial is long and "complicated" like people said before then as you can see it turns out that data transition could be done with simply doing nandroid backup and then restoring it. These step are 90% of this tutorial due to bugs which are in lineage TWRP and "bugs" because that TWRP is backing up ROM with lockscreen settings which are breaking every time when restoring from backup. Also removing backup data step is necessary because these files will slow down encryption and will be not placed in /sdcard so people will forget about it probably and wonder what is eating so much space.
Click to expand...
Click to collapse
Ok, I understand. I think that some things in lineage wiki for p2 must be more clear. Starting from the guide for going from stock ROM to lineage 15.1...

matteo0026 said:
Ok, I understand. I think that some things in lineage wiki for p2 must be more clear. Starting from the guide for going from stock ROM to lineage 15.1...
Click to expand...
Click to collapse
Yeah, wiki instructions are a big mess. You actually need to perform most of steps I've written and described here if coming from another ROM (Steps 1 - 8) and you can do this few different ways
Maybe I will shorten this tutorial by fixing some aspects of TWRP and then request it to be included in the wiki so it will be easier for everyone.

Kielbek said:
Yeah, wiki instructions are a big mess. You actually need to perform most of steps I've written and described here if coming from another ROM (Steps 1 - 8) and you can do this few different ways
Maybe I will shorten this tutorial by fixing some aspects of TWRP and then request it to be included in the wiki so it will be easier for everyone.
Click to expand...
Click to collapse
Yes, for example for going from stock to los15.1 the right steps are:
- unlock bootloader and install official twrp 3.2.3-0
- (in case, do a backup)
- wipe system, data, cache and dalvik
- format data in ext4 (with official kernel, with yours I think it's not needed)
- install treble twrp
- wipe system, data, cache and dalvik another time
- install los15.1 (+ in case your kernel) + gapps and eventually addonsu or magisk
- reboot system

matteo0026 said:
Yes, for example for going from stock to los15.1 the right steps are:
- unlock bootloader and install official twrp 3.2.3-0
- (in case, do a backup)
- wipe system, data, cache and dalvik
- format data in ext4 (with official kernel, with yours I think it's not needed)
- install treble twrp
- wipe system, data, cache and dalvik another time
- install los15.1 (+ in case your kernel) + gapps and eventually addonsu or magisk
- reboot system
Click to expand...
Click to collapse
Yep, the only difference is that I suggest to use "fastboot boot recovery.img" with official twrp instead of flashing it directly to /recovery partition to prevent meaningless excessive data writing here. NAND will last for longer.

Kielbek said:
Yep, the only difference is that I suggest to use "fastboot boot recovery.img" with official twrp instead of flashing it directly to /recovery partition to prevent meaningless excessive data writing here. NAND will last for longer.
Click to expand...
Click to collapse
You are right, but I think NAND is not a problem, we are going to flash recovery maybe 10-20 times in all the device's life, no more

I am now on los15.1 with ext4 data partition which is encrypted. So can I direclty update recovery to this one or I need to do something else ?

Mrinmay Medhi said:
I am now on los15.1 with ext4 data partition which is encrypted. So can I direclty update recovery to this one or I need to do something else ?
Click to expand...
Click to collapse
Yes, of course you can directly update it. If you're on EXT4 it will work for you just fine like version from LOS wiki and maybe even better. Assuming to changelog this version fixes OTAs on encrypted devices. Only F2FS users need to reformat their data.

Hopefully when lineage os 16 released, treble twrp can format data properly, and decrypt/format/use right f2fs system...

mahmutpekkara said:
Hopefully when lineage os 16 released, treble twrp can format data properly, and decrypt/format/use right f2fs system...
Click to expand...
Click to collapse
There's no doubt that it will use newer F2FS version. Not sure about TWRP tho. Maybe I will look into it.

Kielbek said:
There's no doubt that it will use newer F2FS version. Not sure about TWRP tho. Maybe I will look into it.
Click to expand...
Click to collapse
Please do, we need one dedicated TWRP. Also thx again.:angel:

@Kielbek hi does it fix 1689mhz stuck speed bug?

Cuvillier said:
@Kielbek hi does it fix 1689mhz stuck speed bug?
Click to expand...
Click to collapse
What do you mean by this? I don't have such problems.

@Kielbek
How can we disable force encrypt from the kernel?

Any Pie Roms Without Loosing Internal Data

Hello Guys,
After flashing few pie roms and few GSI I faced really big trouble. When we flash rom we must install erecovery and factory format data. After doing this we loose everything on our internal memory. And this is very headaches. :silly:
So I search many times " How to flash pie roms without wiping internal storage" Finally I figure out a method. Some times you know about this, Some times you don't know about this. Pls let me guide.
• I do not responsible for bricked devices, dead SD cards
We call this "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers"
Link here - https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
Introduction....
• If you're currently encrypted: BACKUP YOUR INTERNAL STORAGE TO YOUR PC.
1- Download zip file
2- Reboot to recovery, Then format data.
3- Reboot back into recovery
4- After doing that or if you're not encrypt anymore
5- Make a backup using TWRP ( Ramdisk,Vendor)
6- Wipe required partitions(If you want)
7- Flash your rom, custom kernel (if applicable), then this zip, the magisk/supersu/other root, then Gapps
8- Most important part after flashing rom, You must factory reset using twrp. (TWRP -> Wipe -> slide Left to Right)
• This zip should be flashed after anything that modifies your boot img (like a custom kernel) but before magisk/supersu since this zip creates the files that tells magisk/supersu to not encrypt.
Congratulations now you don't need bootloader for flash roms... :laugh: Feel Free
Credits - @Zackptg5

Cannot root OP5 via Magisk

I cannot root my OP5. I have followed all of the directions unless I'm missing something. A week ago I previously switched to LineageOS but didn't like it so far. So I'm comfortable flashing ROMS.
1. I then downloaded the OOS official ROM, then loaded.
2. Update to most recent OOS (9.0.3) via OTA
3. Followed by factory reset to completely clear TWRP (which was downloaded via official website).
4. Downloaded TWRP
5. *Flash* No verity-opt-encrypt
6. Rebooted to TWRP
7. Downloaded Magisk zip, then flashed
8. Downloaded Magisk apk
9. Open Magisk app *shows* "Magisk is not installed*
I'm thinking maybe I've messed my phone FUBAR up or just completely doing wrong.
*sorry if this has already been answered as well or is posted in the wrong category*

sjonesd3 said:
I cannot root my OP5. I have followed all of the directions unless I'm missing something. A week ago I previously switched to LineageOS but didn't like it so far. So I'm comfortable flashing ROMS.
1. I then downloaded the OOS official ROM, then loaded.
2. Update to most recent OOS (9.0.3) via OTA
3. Followed by factory reset to completely clear TWRP (which was downloaded via official website).
4. Downloaded TWRP
5. *Flash* No verity-opt-encrypt
6. Rebooted to TWRP
7. Downloaded Magisk zip, then flashed
8. Downloaded Magisk apk
9. Open Magisk app *shows* "Magisk is not installed*
I'm thinking maybe I've messed my phone FUBAR up or just completely doing wrong.
*sorry if this has already been answered as well or is posted in the wrong category*
Click to expand...
Click to collapse
The instructions you need to follow are here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
You did not mention any file versions from rom, twrp, magisk.
What does the twrp log says? Are there any errors why magisk isn't installing sucessfully?

strongst said:
The instructions you need to follow are here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
You did not mention any file versions from rom, twrp, magisk.
What does the twrp log says? Are there any errors why magisk isn't installing sucessfully?
Click to expand...
Click to collapse
Sorry for not including the rom type. I was gonna try & run the official stock rom, while rooted. I know it was the TWRP from the official TWRP site "twrp-3.2.3-0-cheeseburger.img". Magisk was the most recent version a "Magisk-v18.1.zip". I don't think there were errors, but I can definitely try again.
I am going to try following those instructions. With me already being on "OxygenOS 9.0.4" via OTA update would I just need to cancel some parts? And to make sure that I flashed blu-spark correctly. I just drag then flash that while under TWRP correct?
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot

sjonesd3 said:
Sorry for not including the rom type. I was gonna try & run the official stock rom, while rooted. I know it was the TWRP from the official TWRP site "twrp-3.2.3-0-cheeseburger.img". Magisk was the most recent version a "Magisk-v18.1.zip". I don't think there were errors, but I can definitely try again.
I am going to try following those instructions. With me already being on "OxygenOS 9.0.4" via OTA update would I just need to cancel some parts? And to make sure that I flashed blu-spark correctly. I just drag then flash that while under TWRP correct?
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
Click to expand...
Click to collapse
Use latest Codeworkx twrp(link in the instructions) and flash it with your current twrp
Then flash magisk 18.1 and watch the log for errors!
Then flash no verity patch(if you were decrypted before and want to stay, otherwise please inform me!)
Your quoted instructions are the ones for clean flash the whole rom. DON'T DO THIS! there are also instructions for updating

strongst said:
Use latest Codeworkx twrp(link in the instructions) and flash it with your current twrp
Then flash magisk 18.1 and watch the log for errors!
Then flash no verity patch(if you were decrypted before and want to stay, otherwise please inform me!)
Your quoted instructions are the ones for clean flash the whole rom. DON'T DO THIS! there are also instructions for updating
Click to expand...
Click to collapse
I followed this right in order. And right when it was time to reboot, it was a black screen with a blue LED light. Looked it up, said that it's bricked/stuck in boot loop

sjonesd3 said:
I followed this right in order. And right when it was time to reboot, it was a black screen with a blue LED light. Looked it up, said that it's bricked/stuck in boot loop
Click to expand...
Click to collapse
Firmware issue. Your device is most likely on a firmware other then the one that twrp supports.
So what was the last oxygenOS firmware / rom you use and which twrp(file name) did you flash?
Within the flashing instructions it's written that you need to be on 5.1.7 before flashing 9.0.x

Disable [DM-Verity]/[Force Encryption] [OnePlus 3T/3] for [PIE] Oxygen OS

Oneplus has released the PIE Oxygen OS for Oneplus 3T and 3.
This thread is only for OOS PIE. For disabling Dm-Verity and force Encryption in NOUGAT OOS ROMs refer to my thread here:https://forum.xda-developers.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232 and for OREO OOS refer to my thread here:https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Disclaimer: I am not responsible for any damage or data loss that happens to your device on embarking this procedure. This is a just released version of OOS and so expect the unexpected. Back up all your data and valuables before you go on and don't blame me if you or your device commits suicide..
THE DETAILS....
After a thororugh initial analysis of the PIE installation zip file for Oneplus 3/3T, I found that there has not been much hell of a difference in the protection schema related to Dm-verity and force encryption. Hence most of the procedure remains the same...As mentioned this is relatively new build and probably existing Twrp may need upstream fixes or other changes to accommodate PIE related commits before encrypting, decrypting and flashing...I have no intention of flashing the PIE build unless it gets stable and have a lot of time to spare so that if things get rough i can dive into it..So its untested from my side but its ought to work same as before. ..
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 detail 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://forum.xda-developers.com/showpost.php?p=74326761&postcount=3
THIS METHOD WILL WORK FOR BOTH ONEPLUS 3 T AND ONEPLUS 3...
FOR THOSE WHO HAVE ALREADY TRIGGERED DM-VERITY ON OOS PIE 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 9.0.6
https://www.mediafire.com/file/mgdc7fga7ypemon/boot-patched-9.0.6-OP3T.img/file
Patched Boot Image Stable OOS 9.0.5
http://www.mediafire.com/file/xuea2pjk7iebo7y/boot-patched-9.0.5-OP3T.img/file
Patched Boot Image Stable OOS 9.0.4
http://www.mediafire.com/file/dzbe1djwlc24h0q/boot-patched-9.0.4-OP3T.img/file
Patched Boot Image Stable OOS 9.0.3
http://www.mediafire.com/file/432r3vew6786pga/boot-patched-9.0.3-OP3T.img/file
Patched Boot Image Stable OOS 9.0.2
https://www.mediafire.com/file/fj2offc35sa0zo7/boot-patched-9.0.2-OP3T.img/file
BETA OOS Boot Images
Patched Boot Image Beta OOS 9.0.1
http://www.mediafire.com/file/bf32s2mf2c7y66o/boot-patched-9.0.1-OP3T.img/file
Patched Boot Image Beta OOS 9.0
http://www.mediafire.com/file/kesaqq2q8dgi43p/boot-patched-9.0.0-OP3T.img/file
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 9.0.6
http://www.mediafire.com/file/huxj64syp8l1o58/boot-patched-9.0.6-OP3.img/file
Patched Boot Image Stable OOS 9.0.5
http://www.mediafire.com/file/mkv6swi72pruafy/boot-patched-9.0.5-OP3.img/file
Patched Boot Image Stable OOS 9.0.4
http://www.mediafire.com/file/7d9k4nytqa7nqjv/boot-patched-9.0.4-OP3.img/file
Patched Boot Image Stable OOS 9.0.3
http://www.mediafire.com/file/z7dckvcztskes53/boot-patched-9.0.3-OP3.img/file
Patched Boot Image Stable OOS 9.0.2
http://www.mediafire.com/file/3rzae15wf25l72w/boot-patched-9.0.2-OP3.img/file
BETA OOS Boot Images
Patched Boot Image Beta OOS 9.0.1
http://www.mediafire.com/file/v36cxtcnao23bc3/boot-patched-9.0.1-OP3.img/file
Patched Boot Image Beta OOS 9.0
http://www.mediafire.com/file/a9gq8koevpra9bh/boot-patched-9.0.0-OP3.img/file
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 Pie 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 Pie v1.zip" in TWRP.
9. Flash SuperSuSR5 / Magisk 18+
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 Pie v1.zip" in TWRP.
10. Flash SuperSuSR5 / Magisk 18+
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 18 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: @Siddk007 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....
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...

THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS PIE ROMs. ...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
READ ALL THE STEPS AND DOWNLOAD ALL REQUIRED FILES BEFORE PROCEEDING. FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for PIE OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for PIE OOS corresponding to your current OOS (current OOS is the version of OREO OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
12) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
13) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT:
1. If you need to keep your phone un-encrypted flash Force Encryption Disabler For OOS PIE.zip immediately after step 12 and then only reboot.
2.If you are attempting this method on a a CUSTOM ROM then after Step 12 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...

Reserved..

Reserved...

Thanks for your work!
I have a question. Is there anyway to prevent OOS Pie Community Build from corrupting the /data partition on Unlocked Bootloaders with Encrypted /data partition? They specifically designed the builds to do so. It doesn't cause it if the device is locked. Can the boot image be patched for that too?
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
Thanks for your work!
I have a question. Is there anyway to prevent OOS Pie Community Build from corrupting the /data partition on Unlocked Bootloaders with Encrypted /data partition? They specifically designed the builds to do so. It doesn't cause it if the device is locked. Can the boot image be patched for that too?
Click to expand...
Click to collapse
That is the duty of twrp (recovery) I suppose because with stock recovery it doesn't seem to happen and it probably doesn't have anything to do with boot image as such...but u can very well try with the patched boot image..either u can flash the patched boot image immediately after flashing the zip file and try rebooting back to twrp and see
Or replace the boot image in the OOS zip file with mine and try flashing...but no guarantees buddy...
ALWAYS BACKUP BEFORE DOING ANYTHING...THIS IS A NEW OS ANS WE ARE STILL LEARNING...

Xennet said:
That is the duty of twrp (recovery) I suppose because with stock recovery it doesn't seem to happen and it probably doesn't have anything to do with boot image as such...but u can very well try with the patched boot image..either u can flash the patched boot image immediately after flashing the zip file and try rebooting back to twrp and see
Or replace the boot image in the OOS zip file with mine and try flashing...but no guarantees buddy...
ALWAYS BACKUP BEFORE DOING ANYTHING...THIS IS A NEW OS ANS WE ARE STILL LEARNING...
Click to expand...
Click to collapse
Alright thanks!
Let's see if anyone tries it out [emoji14]
I'm not in the urge of risking getting my /data wiped as of now
Sent from my #FlagshipKiller3T using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks @Xennet ...:good:
I followed all the steps from procedure 1 ( PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED ) and for everyone out there who are confused or fear of loosing data , I successfully booted OOS Pie beta/community build without loosing any of my data/internal storage (everything regarding data is intact).

DarkSJ1998 said:
Alright thanks!
Let's see if anyone tries it out [emoji14]
I'm not in the urge of risking getting my /data wiped as of now
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't try because if your data is encrypted and you follow the old steps with pie files for just not triggering dm-verity
Twrp cannot decrypt the data if you reboot after flashing oos community beta and then immediately patched boot image for pie
Luckily i saved myself (from loosing data) by not booting into system and again dirty flashing stable oreo rom using the guide for oreo and patched oreo boot image.
I had to dirty flash OREO Rom patched boot image and magisk all using OTG since i couldn't access data partition.

a0879 said:
thanks @Xennet ...:good:
I followed all the steps from procedure 1 ( PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED ) and for everyone out there who are confused or fear of loosing data , I successfully booted OOS Pie beta/community build without loosing any of my data/internal storage (everything regarding data is intact).
Click to expand...
Click to collapse
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...

Yudh said:
Don't try because if your data is encrypted and you follow the old steps with pie files for just not triggering dm-verity
Twrp cannot decrypt the data if you reboot after flashing oos community beta and then immediately patched boot image for pie
Luckily i saved myself (from loosing data) by not booting into system and again dirty flashing stable oreo rom using the guide for oreo and patched oreo boot image.
I had to dirty flash OREO Rom patched boot image and magisk all using OTG since i couldn't access data partition.
Click to expand...
Click to collapse
That's in line....
Hmmmmmm it's a Twrp problem...the problem is with decryption of pie data by twrp...as stated earlier by @a0879, the patched boot image works perfectly with already decrypted data partitions without losing data...
But @Yudh, the patched boot image did it's work by not letting twrp being overwritten by the stock recovery or else you would have been in trouble...

Xennet said:
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...
Click to expand...
Click to collapse
Yes, my bootloader is unlocked from time immemorial and i was on havoc 2.4, twrp 3.2.3-10, magisk v18.1 just before flashing oos pie beta today.
Earlier i tried the leaked version and the one3tos also a few days back which ultimately wiped whole of my data/internal (though i backed it on pc) and replaced it with the stock recovery, i was unable to do anything other than just using it as it was but then also my bootloader was unlocked.
So i was searching for how to use pie by remaining non encrypted and not formatting internal storage and saving then Finally after going through your post i decided to follow each and every step as told, and "B A N G" !! , it worked as told by you !
thanks again..:good:

Xennet said:
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...
Click to expand...
Click to collapse
I had my bootloader unlocked.
I was on oos 5.0.8 latest stable build.
Also i discovered a workaround.
Steps below to keep your app data, unlocked bootloader and update to pie.
1)First upgrade the twrp to latest 3.3.0-1
2)remove any kind of lock in the system.
{otherwise it creates issues at the last point by not allowing us to enter the phone past lock screen.
[ If forgot to do so like me Workaround(perform after step 14 only) is to reboot to twrp and deleting the file located at /data/system/locksettings.db using twrp file manager (trick picked from OnePlus official rooting guide).
Then reboot into system and create the same locking method to retain fingerprints and facelock]
But for some people it would be better to remove locks in the first place from system before taking a full backup using twrp because you can always forget which file needs to be deleted or bymistakely if wrong file is deleted then it will cause issues}
3) reboot to twrp and take a COMPLETE BACKUP IN AN EXTERNAL DEVICE . Internal backup won't help.
It would be better if you don't compress it.(in rare cases it led me to corrupted backup in the past with previous twrp versions)
4)after taking backup don't go out of twrp and using MTP
Copy the whole internal storage to pc .
Bellow part isn't necessary but it would be better if you do it.
Also check the twrp backups digest for each created partition just to be on safer side.( It's better to be safe than sorry.)
So that you can make sure that your backup isn't corrupted.
5) download the community pie beta build and patched boot image for pie on the external storage like an otg (which i used).
Sha256 for OnePlus 3T beta build is
837d0f972ce7a10e422ddbf4d96d37cf3d84422ee5717c37a0ee5c3e1419d3c0
Also sha256 for OnePlus 3T patched boot image is
e2619b029e2f14f8cbe3c3b9306181e6688f038f39e8fcd4d5dea823360dcce0
6)wipe everything in twrp using format data option.
7) reboot to recovery again immediately using twrp otherwise twrp won't be able to access data partition afterwards.
8)flash the community beta build and immediately after that the patched pie boot image.
9) reboot to twrp again
10)flash magisk if you want.
11) reboot to system. After the system is started don't enter anything.
Instead again reboot to twrp.
12)while in twrp connect the mobile to pc and delete all the new folders and files in new internal storage.
After that copy the old internal storage contents to your mobile.
Just wait even i was exhausted. But it worked out well.
13)after that restore only the data partition from the nandroid backup which you made using twrp in the start of this guide
14) reboot to system and your data is still there in your mobile with pie community beta build and also unlocked bootloader

Proof that i succeeded
Now its time for me to enjoy my pie and go to sleep.
For you it's time to prepare your own pie

Xennet said:
That's in line....
Hmmmmmm it's a Twrp problem...the problem is with decryption of pie data by twrp...as stated earlier by @a0879, the patched boot image works perfectly with already decrypted data partitions without losing data...
But @Yudh, the patched boot image did it's work by not letting twrp being overwritten by the stock recovery or else you would have been in trouble...
Click to expand...
Click to collapse
The problem isn't with twrp i think because
After rebooting to recovery after flashing the pie beta and patched boot image
Even the system couldn't access the data partition it asked me to reset my phone by saying the data partition is corrupted (which in reality wasn't because i was able to recover the data)
So after i formatted it via twrp and rebooted again into twrp
Both the system and twrp were able to decrypt it.
I think something about encryption is changed in pie in oos

I successfully flash the open beta pie following the op's instruction.! Decrypted with no dm-verity message! Thank you Xennet!
I was on Aosip before and I didn't loose my data!

Sent from my OnePlus 3T using XDA Labs

As @a0879 and @xarrismoto have provided proof it's 100% clear that the patched boot image and force encryption disabler zip is able to update Oreo to pie without losing data if the phone is in DECRYPTED STATE ...
Now the problem is for encrypted phones...
Now as @Yudh mentioned it is definitely due to a change in the encryption in pie the data wipe is happening..that's sure..
But the question is if you have a locked bootloader and stock recovery, you are able to update from Oreo to pie without lose of data??...but with twrp you can't....
So the question is, whether the problem of encryption is not handled by twrp or by the system in pie itself....

xarrismoto said:
I successfully flash the open beta pie following the op's instruction.! Decrypted with no dm-verity message! Thank you Xennet!
I was on Aosip before and I didn't loose my data!
Click to expand...
Click to collapse
Can you please elaborate a bit more and it will be most helpful post of the day. As i was on closed beta and lost my data on flashing closed beta however afterwards i flashed custom roms and now my device is encrypted and locked bootloader having TWRP running Colt PIE OS. If i flashed decryption zip and modified boot then my data will be wiped or not? If not then please share your steps. Thanks
Sent from my ONEPLUS A3003 using Tapatalk

MirzaAwais said:
Can you please elaborate a bit more as its most helpful post of the day. As i was on closed beta and lost my data on flashing closed beta however afterwards i flashed custom roms and now my device is encrypted and locked bootloader having TWRP running Colt PIE OS. If i flashed decryption zip and modified boot then my data will be wiped or not? If not then please share your steps. Thanks
Click to expand...
Click to collapse
I don't think it will work for you as you are encrypted!
I was decrypted before and I stay decrypted after I flash Pie rom. I use latest TWRP 3.3.0.1 and magisk v19.0,also my bootloader is unlock
I followed the instruction from Op which is PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED
Sent from my OnePlus 3T using XDA Labs