Develop Bugs

Why disable encryption?

I have seen several posts referring to disabling encryption but not a reason why I should. I am rooted, running 6.0.1, and I skipped the decryption step during the root. My phone says it is encrypted. I haven't noticed any lag but I have only had my phone for 1.5 weeks. One would "assume" that having it encrypted would be better. So why would I want to disable it? Is there a cumulative effect that I don't know about?
Thank you.

If you don't want to and you want to leave it encrypted go for it. An encrypted fs will have slower read/write speeds, and some people aren't worried about having their phone encrypted. You can always re encrypt in security settings just now you wont be forced to have it on.

For my personal device i never use encryption, without it devices are notably faster for me.

67p912 said:
I have seen several posts referring to disabling encryption but not a reason why I should. I am rooted, running 6.0.1, and I skipped the decryption step during the root. My phone says it is encrypted. I haven't noticed any lag but I have only had my phone for 1.5 weeks. One would "assume" that having it encrypted would be better. So why would I want to disable it? Is there a cumulative effect that I don't know about?
Thank you.
Click to expand...
Click to collapse
It's more convenient for flashing ROMs if it's decrypted. Because TWRP recovery can't see an encrypted partition, you can't download a ROM to your phone's storage and then flash it in recovery. It would be nice if we could have two data partitions, an encrypted one and an unencrypted one.

Jacquestrapp said:
It's more convenient for flashing ROMs if it's decrypted. Because TWRP recovery can't see an encrypted partition, you can't download a ROM to your phone's storage and then flash it in recovery. It would be nice if we could have two data partitions, an encrypted one and an unencrypted one.
Click to expand...
Click to collapse
TWRP has be able to 'see' encrypted storage for a while now.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
TWRP has be able to 'see' encrypted storage for a while now.
Click to expand...
Click to collapse
Is there some kind of trick to that, or some setting in TWRP that needs to be enabled? It didn't work for me the first time I tried it.

Jacquestrapp said:
Is there some kind of trick to that, or some setting in TWRP that needs to be enabled? It didn't work for me the first time I tried it.
Click to expand...
Click to collapse
It just works and has since November with TWRP version 2.8.7.2.
Sent from my Nexus 5X using Tapatalk

Regarding encryption, if I were to do a twrp backup with 'encryption on', can i restore that backup on a 'encryption off' phone after.
My plan is to:
Nandroid backup with encryption on
Decrypt (which erases all user data)
Restore backup
How will this affect the backup since 1 has encryption on previously?

how to disable encryption?

cavalloz said:
how to disable encryption?
Click to expand...
Click to collapse
Code:
fastboot format userdata
^^^This will wipe your internal storage^^^
Edit: Need a modified kernel that doesn't force encryption.

How about a few more details on turning off encryption please.
Sent from my Nexus 5X using Tapatalk

Kinda of a weird thing can't decrypt recovery

Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick

jamesblunt1 said:
Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick
Click to expand...
Click to collapse
It's the problem with nougat update and twrp currently. Look for other threads to see what options you have.

TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.

abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
.19 worked for me.

Wipe the /data partition and it won't ask for the pattern.

dbabaev21 said:
.19 worked for me.
Click to expand...
Click to collapse
To OP, Can you please try .19 version of twrp as suggested and see if it can decrypt your encrypted storage?

abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!

jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Please read what i typed, again. Why would i want to remove encryption and wipe my internal storage just because the TWRP is outdated? /data also includes your /data/media which is internal storage. I mentioned that TWRP is not supporting encrypted storage in it's present state. It's working fine for decrypted storage and it won't ask for a password if your storage is decrypted.

jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Even if you use this method, if you flash the official ROM later via TWRP, it won't work right. TWRP will prompt for a password even though you've never set one. So actually he's not really wrong.

I used this "method" just last night on my OP3. Loaded the OS via side load and SU also. I am writing to you on this device right now. I also got an AnTuTu score of over 157,484 running stock OOS 4.0. If you are having issues, they are more than likely user issues.

Please read this install method. It will help with data encryption.
https://forum.xda-developers.com/showthread.php?p=70429702#post70429702

disable the encryption on stock rom 7.1.1

hi, I unlocked and rooted my nexus with 5x stock rom 7.1.1
I try to disable the encryption of files by formatting the data partition, but if you check in the SECURITY settings, the phone is always encrypted.
What am I doing wrong? Thank you.

Decrypt Question
Are you flashing SuperSu to patch kernel to remove forced encryp or flashing a custom kernel to remove it? If not, the stock kernel will re-encrypt upon boot.

I think that is normal, mine also shows encrypted currently with a stock kernel. Only time I need to decrypt is in TWRP, and instead of a password, I'm using a pattern.

TypNguy said:
I think that is normal, mine also shows encrypted currently with a stock kernel. Only time I need to decrypt is in TWRP, and instead of a password, I'm using a pattern.
Click to expand...
Click to collapse
That's probably not the kind of decryption he was looking for.
The correct answer has been given

thanks for the answers, but I still have the same problem.
I rooted, I installed the latest TWRP recovery, as well installed nexus ...
Then I formatato the DATA partition.
Start the well nexus (latest version) and under the heading Safety, the phone is still encrypted!
The kernel of pure nexus is stock?

[OP5] Full-Disk-Encryption Enabler for OP5

You miss Full-Disk Encryption on your OnePlus 5?
Here's a fix.
Flash the zip below after flashing your kernel (which means after every ROM update as well!).
The very first time you flash this mod, you'll have to format userdata, or bad things will happen.
First-time Install instructions:
Flash your ROM
Flash the attached Zip
(Optional) Flash Magisk
Format userdata. In TWRP, go to Wipe -> Format Data
Reboot
You are now unencrypted.
To encrypt in Full-Disk Encryption mode, go to Settings -> Security -> Encrypt
You're now in FDE mode!
Profit!
And don't forget to reflash this module every time you flash a new boot image.
XDA:DevDB Information
Full-Disk-Encryption Enabler for OP5, Device Specific App for the OnePlus 5
Contributors
Fif_
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-12
Created 2017-09-13
Last Updated 2017-09-13

Here's the Zip.

@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk

dragoi90 said:
@Fif_ should i erase "internal storage" or just data partition!Thank You!
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
You need to format the data partition. That all also nuke the internal storage by the way, so your phone will be back to factory reset.

Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?

BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.

Fif_ said:
No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.
Click to expand...
Click to collapse
You can have Xposed working with FBE by just soft rebooting using Xposed installer.

alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
You are right, but I don't want to have to do that, I want Xposed on the first boot...

BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
If you want the go under settings and security and encrypt your phone

BlueEffect said:
Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?
Click to expand...
Click to collapse
ndarkside93 said:
If you want the go under settings and security and encrypt your phone
Click to expand...
Click to collapse
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.

Fif_ said:
This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.
Click to expand...
Click to collapse
I know.I was just answering his question.

alukarulz said:
You can have Xposed working with FBE by just soft rebooting using Xposed installer.
Click to expand...
Click to collapse
Fif_ said:
You are right, but I don't want to have to do that, I want Xposed on the first boot...
Click to expand...
Click to collapse
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?

sjamie said:
Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?
Click to expand...
Click to collapse
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.

alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
Would I have to also erase my data when switching to a different ROM?

alukarulz said:
I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.
Click to expand...
Click to collapse
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.

sjamie said:
Would I have to also erase my data when switching to a different ROM?
Click to expand...
Click to collapse
No. Only once.

Fif_ said:
I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.
Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.
Click to expand...
Click to collapse
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?

sjamie said:
Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?
Click to expand...
Click to collapse
Yes you can, run in a root shell:
Code:
setsid sh -c 'stop; start'
But I always run into strange things in Xposed if it's not running at boot, so YMMV.
Be careful not to just restart the system UI but the full zygote stack.

Fif_ said:
Yes you can, run in a root shell:
Click to expand...
Click to collapse
Thank you. What exactly is that command doing? Do I have to run it after each boot?

sjamie said:
Thank you. What exactly is that command doing? Do I have to run it after each boot?
Click to expand...
Click to collapse
"stop" stops all Android services.
"start" starts them again.
The "setsid sh" wrapper is there so that the commands will survive the Android shutdown and run to completion even if the parent process calling root is killed (which will happen as soon as "stop" runs).
Yes you'd have to run this after every boot.
But be careful that the second time Android starts after a boot is not detected as a second boot event or you'll end up in a restart loop.

Wrong password after restore nandroid backup / flashing new rom

I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?

ostvarivanje said:
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
Click to expand...
Click to collapse
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.

preference said:
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
Click to expand...
Click to collapse
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close

ostvarivanje said:
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
Click to expand...
Click to collapse
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup

preference said:
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
Click to expand...
Click to collapse
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.

ostvarivanje said:
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
Click to expand...
Click to collapse
Which twrp are you using? Are you on the latest from codeworkx

preference said:
Which twrp are you using? Are you on the latest from codeworkx
Click to expand...
Click to collapse
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem

ostvarivanje said:
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
Click to expand...
Click to collapse
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?

preference said:
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
Click to expand...
Click to collapse
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?

ostvarivanje said:
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
Click to expand...
Click to collapse
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.

preference said:
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
Click to expand...
Click to collapse
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.

ostvarivanje said:
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
Click to expand...
Click to collapse
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.

preference said:
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
Click to expand...
Click to collapse
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!

ostvarivanje said:
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
Click to expand...
Click to collapse
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.

preference said:
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
Click to expand...
Click to collapse
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?

ostvarivanje said:
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
Click to expand...
Click to collapse
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.

preference said:
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
Click to expand...
Click to collapse
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.

ostvarivanje said:
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
Click to expand...
Click to collapse
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)

preference said:
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
Click to expand...
Click to collapse
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!

ostvarivanje said:
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
Click to expand...
Click to collapse
You can't use normal wipe, go to wipe then choose the option on the right (I think it says wipe device) and then it will tell you to type "yes". If you type yes then hit enter it will format the phone. That's a true format and it will decrypt your device. You can't just wipe all partitions because it's not a complete format.
So if you typed "yes" in TWRP you have a formatted phone. It will stay decrypted until you flash an encrypted rom.
So if you flash DU, you don't need no verity because the rom is decrypted. If you flash RR 6.0 then your phone will encrypt UNLESS you flash no verity. So the file I gave you is a way to stop encryption on encrypted roms.
You flash RR 6.0, gapps, no verity = RR but no encryption.
You flash DU, gapps = decrypted rom so you don't need no verity zip
Most roms are encrypted, so you flash rom, gapps, no verity to stay decrypted. The zip I gave you should be flashed after flashing rom and gapps on every encrypted rom if you want to stay decrypted.