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

Unable to Mount Data in TWRP

I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!

You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs

Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2

Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.

the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs

Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.

Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.

Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor

help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me

I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.

[RECOVERY][TWRP][OFFICIAL] TWRP 3.2.1.0 encrypted /data - cant mount

I searched and didn't found... searched longer than an hour....
nexus 5x, lineageos (not rooted), twrp installed, bootloader open
PROBLEM: when I reboot to recovery twrp asks for lock pattern, so I can't mount /data
Yes I can format data and so on...
But hoe can I flash ROMs (LOS-updates) without loosing the data every time?
Why can't I read the data partition?

First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted. (read)
Flashing rom updates without losing your data is called dirty flashing - all you need to wipe is /cache and /dalvik(or /art), after that you simply flash the new rom build.
Keep in mind - dirty flashing could: cause new problems; not fix existing ones.
When experiencing issues, go for clean flash.

Thanks.
When Q&A is the right section, then this could be moved, I can't.
But: I did a clean flash, with "advanced data" and factory reset. And I got this encryption problem.
I already made a clean flash again and the pattern comes back.
I don't understand, where is the step I made the mistake.
Also got a g4 h815 here it works....

Again:
shhnedo said:
Your /data partition should be decrypted. (read)
Click to expand...
Click to collapse

Thanks I read it tomorrow, it's 2 aclock in the night in Germany....
By the way , I'm on 14.1 7.2.1 not on 8.1

shhnedo said:
First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted.
Click to expand...
Click to collapse
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.

Noob_Master said:
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.
Click to expand...
Click to collapse
crDroid and many other LOS base ROMs have the "forcefdeorfbe" flag set in the boot.img. (It is the LOS standard to set this). While most don't feel there is a "speed hit" when running encrypted, I don't like the hassle between ROM flashes.

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.

Encrypted Internal Storage after flashing with TWRP CFW

Good Afternoon.
A question for you guys, every time i try to wipe my current rom and flash another custom rom, or an update to the current rom on my begonia (with cfw installed), my damn internal storage gets encrypted, so ive got no choice but to format it, or else i can't access it, which is a major pain...
Do you guys know of a way to prevent this??
I'm running twrp recovery with cfw support.
And am pretty sure i'm not f-ing up with the rom installation instructions...

Jollld said:
Good Afternoon.
A question for you guys, every time i try to wipe my current rom and flash another custom rom, or an update to the current rom on my begonia (with cfw installed), my damn internal storage gets encrypted, so ive got no choice but to format it, or else i can't access it, which is a major pain...
Do you guys know of a way to prevent this??
I'm running twrp recovery with cfw support.
And am pretty sure i'm not f-ing up with the rom installation instructions...
Click to expand...
Click to collapse
Hi, If you setup the lockscreen on your ROM you will encrypt the internal storage and TWRP will ask you the password to decrypt it.
If u remove the lockscreen before entering recovery you won't have to decrypt the internal storage.

Thanks but some kind souls on discord helped me out, using a disable encryption zip fixed it.

Jollld said:
Thanks but some kind souls on discord helped me out, using a disable encryption zip fixed it.
Click to expand...
Click to collapse
Any chance for sharing it here? Thank you

porotikos said:
Any chance for sharing it here? Thank you
Click to expand...
Click to collapse
Install this then format data.
Also if you flash a new ROM you'll have to install this again.

Canny1913 said:
Install this then format data.
Also if you flash a new ROM you'll have to install this again.
Click to expand...
Click to collapse
oh my god i fecked up.
i installed this via twrp and didnt format. (i dont want to lose data).
Now the phone doesnt boot. it gets stuck in miui logo.
is there a way to go to twrp and revert the changes?

porotikos said:
oh my god i fecked up.
i installed this via twrp and didnt format. (i dont want to lose data).
Now the phone doesnt boot. it gets stuck in miui logo.
is there a way to go to twrp and revert the changes?
Click to expand...
Click to collapse
Can you tell me the ROM version? So i can try to give you some files and instructions for fixing it.

Canny1913 said:
Can you tell me the ROM version? So i can try to give you some files and instructions for fixing it.
Click to expand...
Click to collapse
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.

Canny1913 said:
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.
Click to expand...
Click to collapse
worked. thanks

Canny1913 said:
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.
Click to expand...
Click to collapse
i have managed to turn on the phone. my internal storage isnt wiped. just the data. so i am setting up my accounts etc.
i can see tha tmy inernal storage that is used, is 215 gb. so my data is there. but they are not accessible. because they seem to be decryptewd from the module i guess.
is there any way i can get back my data so that i can back up, and then i can hard format the phone?
when i open the files appliucation, it doesnt even show my internal folders. nothing.
this is really strange

porotikos said:
i have managed to turn on the phone. my internal storage isnt wiped. just the data. so i am setting up my accounts etc.
i can see tha tmy inernal storage that is used, is 215 gb. so my data is there. but they are not accessible. because they seem to be decryptewd from the module i guess.
is there any way i can get back my data so that i can back up, and then i can hard format the phone?
when i open the files appliucation, it doesnt even show my internal folders. nothing.
this is really strange
Click to expand...
Click to collapse
In TWRP, mount Data and using the in-built File Manager, check inside /data/media/0 (this is where your Internal Storage is located)
Is your password intact btw?

Canny1913 said:
In TWRP, mount Data and using the in-built File Manager, check inside /data/media/0 (this is where your Internal Storage is located)
Is your password intact btw?
Click to expand...
Click to collapse
data kept showing encrypted. just did a hard format. thanks for your help anyway

porotikos said:
data kept showing encrypted. just did a hard format. thanks for your help anyway
Click to expand...
Click to collapse
This is why i hate android's "security"