In an effort to keep this chatter out of other threads, here is the info that you seek. I didn't discover this process @DespairFactor and Bryant (not sure of his XDA handle) get the credit.
First you need to go through the Google set up and Skip everything except, the unlock Theft Protection. It will then ask you if you want to add the Google account and you say no. If at any point you say yes to something or add a pin / fingerprint it will encrypt. Then you need to reboot to the bootloader and run, fastboot format userdata then, Boot and Skip through the set up again. As long as you do not add a pin / password or a google account you will stay un-encrypted. This will work on the stock boot.img.
Reserved
Any advantage of doing it? In theory it should work faster, but is it visible?
Hola
And further to @DforDesign's question, I take it that having a decrypted device helps with existing TRWP and available custom kernel installations? I haven't reviewed the Development sub-forums yet as I am still awaiting my device.
Thanks for the guide.
If you do stay unencrypted, isn't all we can do for now is just edit the build prop? Anything else? I thought magisk would still bootloop
DforDesign said:
Any advantage of doing it? In theory it should work faster, but is it visible?
Click to expand...
Click to collapse
Depends on if you talk to people that wear tin foil hats, that also gives you your answer.
so after the setup, can you add your google account, fingerprint/pin later?
xryousukex said:
so after the setup, can you add your google account, fingerprint/pin later?
Click to expand...
Click to collapse
Then you will lose twrp after doing that process. It will be encrypted.
Let me make sure I'm understanding this.
I already set up my 2 XL with pin and fingerprint, so now it's encrypted making seeing root file tree impossible (like sdcard, download folder).
If I reset my device, and say NO to everything requiring pin or fingerprint on the device, I can set it up normally and still have access to the root file tree?
So long as I don't password, pin, fingerprint protect the device, I'll continue to have access to these files, right?
But this also means no google account activity (Gmail, contacts , photos, etc) right?
Yes for now, that's exactly what that means, at least for now until TWRP , or AOSP recovery is update and worked on to work with our device.
Az Biker said:
Let me make sure I'm understanding this.
I already set up my 2 XL with pin and fingerprint, so now it's encrypted making seeing root file tree impossible (like sdcard, download folder).
If I reset my device, and say NO to everything requiring pin or fingerprint on the device, I can set it up normally and still have access to the root file tree?
So long as I don't password, pin, fingerprint protect the device, I'll continue to have access to these files, right?
But this also means no google account activity (Gmail, contacts , photos, etc) right?
Click to expand...
Click to collapse
You understand correctly. The only thing I'm not sure about is whether or not a factory reset will be enough. We used format userdata in fastboot to achieve it. It may be a good test to see if simply linking a Google account will trip encryption.
I can add my google account as long as i dont set a pin or fingerprinter my phone's internal storage is visible via TWRP with no issues.
Let me add something we discovered. It seems to be on the pin/pattern setup only. I think you can do everything else to stay decrypted in twrp. Now might thought was to setup everything they way you want without pin/pattern and you can then backup. Then save that backup on a PC. After that you lock your device via pin/pattern. If for some reason something screws up instead of setting everything up again. Just factory reset and skip everything and place backup on SD card then boot twrp and try to restore. Someone want to test this theory lol????
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Let me add something we discovered. It seems to be on the pin/pattern setup only. I think you can do everything else to stay decrypted in twrp. Now might thought was to setup everything they way you want without pin/pattern and you can then backup. Then save that backup on a PC. After that you lock your device via pin/pattern. If for some reason something screws up instead of setting everything up again. Just factory reset and skip everything and place backup on SD card then boot twrp and try to restore. Someone want to test this theory lol????
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks for confirming
Great! Thanks. I can't use TWRP on the Nov patch but I have a question... I'm now using a permissive kernel. Can I simply wipe userdata to unencrypt? Can you confirm? Is the command fastboot format userdata?
Thanks in advance!
Mike02z said:
Great! Thanks. I can't use TWRP on the Nov patch but I have a question... I'm now using a permissive kernel. Can I simply wipe userdata to unencrypt? Can you confirm? Is the command fastboot format userdata?
Thanks in advance!
Click to expand...
Click to collapse
Yes, but twrp is still not functional
bryantjopplin said:
Yes, but twrp is still not functional
Click to expand...
Click to collapse
Thanks. I didn't realize we needed twrp. I was thinking we could just use fastboot erase userdata in leu of twrp.
Can't you just factory reset and then flash Magisk before re-setting up your phone? I thought Magisk disabled force encrypt by default.
Mike02z said:
Thanks. I didn't realize we needed twrp. I was thinking we could just use fastboot erase userdata in leu of twrp.
Click to expand...
Click to collapse
No you can, I thought you were thinking format userdata would fix twrp. Sorry
TheSt33v said:
Can't you just factory reset and then flash Magisk before re-setting up your phone? I thought Magisk disabled force encrypt by default.
Click to expand...
Click to collapse
Tried it, no luck. Removed my Google account, reset phone, did not log into my Google account and did not set up any PIN or password and it's still encrypted. I'll try fastboot erase userdata and cache and see if that works.
Related
So I saw the articles and threads on 12/25 reporting do not Disturb until next alarm was gone. After noting mine was gone too I turned off my 6P and went back to using my Galaxy S6 for 2 days.
I turned my 6P back on to get a file off it last night and noticed do not disturb symbol was on the top status bar. I pulled the toggles down saw it was lit with 'alarms only' under it. I clicked the toggle and it does not turn off. I tried double clicking and tried holding down toggle. I Pressed the volume up button and I can change volume for alarms and media, but ring tone slider is faded out so I can't modify it.
Then I went into settings and confirmed in the notifications section that there is no do not disturb schedule turned on and no apps have access to do not disturb. I also could not turn it off from inside settings either. I did a quick Google search and found a thread on 12/23 and 12/14 of this being reported on Android Central. Before this until next alarm disappeared. Every thread has no resolution if there was one.
I tried clearing all user cache and rebooting but it's still turned on. I also booted into twrp and wiped cache in there. It still shows! So it seems to be something in the system. I am rooted (systemless) but completely stock 6.0.1. I's anyone else experiencing this or have any suggestions?
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
fury683 said:
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
Click to expand...
Click to collapse
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
AndroidPurity said:
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
Click to expand...
Click to collapse
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks, I was not aware. I thought it was just FUBAR if you didn't remove it before making the backup.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
AndroidPurity said:
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
Click to expand...
Click to collapse
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
fury683 said:
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
Click to expand...
Click to collapse
Yes exactly. If you already made a nandroid and forgot, restore it and then erase that file. I've done it and it works.
fury683 said:
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Click to expand...
Click to collapse
So I downloaded the MMB29M factory image, and ran the flash-all.bat. Unfortunately I forgot to remove the -w. No biggie though I had no important pictures or documents that needed backed up. Just will have to sign into all my apps all over again. Anyways it did resolve the DND being stuck on, I figured it would since it went completely back to stock including user data.
However I am still baffled at how that could have happened when it was fine after the systemless root and never played around with the root files afterwards. No exposed modules or anything. Anyways I am about to flash twrp and install the new 2.65 SuperSU to root again. So I guess only time will tell if it happens again. Thanks for the help gentlemen!
Same problem but im on a stock phone. Not even rooted
It just occured to me, that despite encrypting my device, I can boot into TWRP recovery and flash things to various partitions without entering a password.
Doesn't that essentially mean that the encryption key must be stored somewhere by TWRP in a clear (unencrypted) form?
If so, doesn't root basically render device encryption meaningless? Sure the average phone thief might not care to crack into it, but it would probably be trivial for anybody with a little technical knowledge and time on their hands. And police probably have a step-by-step process for cracking rooted devices.
Does root compromise encryption?
static416 said:
It just occured to me, that despite encrypting my device, I can boot into TWRP recovery and flash things to various partitions without entering a password.
Doesn't that essentially mean that the encryption key must be stored somewhere by TWRP in a clear (unencrypted) form?
If so, doesn't root basically render device encryption meaningless? Sure the average phone thief might not care to crack into it, but it would probably be trivial for anybody with a little technical knowledge and time on their hands. And police probably have a step-by-step process for cracking rooted devices.
Does root compromise encryption?
Click to expand...
Click to collapse
To answer your exact question, no, root doesn't compromise encryption. Root and TWRP are two separate things, you can have TWRP without root. However, TWRP does allow access to your data without requiring authorisation.
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah that's a good point, I don't use that feature as I find it annoying so I forgot about it.
SlimSnoopOS said:
Doesn't "enable Password on Boot" in Settings/Security, force a password onto TWRP as well?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The only way your data is truly encrypted (in my opinion) is doing just that.
Agent said:
The only way your data is truly encrypted (in my opinion) is doing just that.
Click to expand...
Click to collapse
Thanks so much! This is exactly what I was looking for.
I don't know why it didn't occur to me earlier. I'm glad I don't have to choose between security and usability (root, TWRP, etc).
i was thinking about this today actually, because my phone has no encryption (both system and userdata).
However, with purenexus rom and cerberus if your phone is ON when it's stolen, you can essentially prevent someone from booting into recovery since the normal power menu is not available, and pressing and holding the power button for 10 secs just reboots the phone into OS again which is locked. Also, the USB defaults to charging, so data is inaccessible.
is there a way boot into recovery in a situation such as this?
2x4 said:
i was thinking about this today actually, because my phone has no encryption (both system and userdata).
However, with purenexus rom and cerberus if your phone is ON when it's stolen, you can essentially prevent someone from booting into recovery since the normal power menu is not available, and pressing and holding the power button for 10 secs just reboots the phone into OS again which is locked. Also, the USB defaults to charging, so data is inaccessible.
is there a way boot into recovery in a situation such as this?
Click to expand...
Click to collapse
They can hold Power and volume down to boot right into bootloader (and subsequently recovery) from lockscreen. I did this last night since restoring my TWRP 3.0 backup locked me out of my 5X lol
Edit: just want to be clear, I do not have Cerberus. idk if it blocks the above combo as well
SlimSnoopOS said:
They can hold Power and volume down to boot right into bootloader (and subsequently recovery) from lockscreen. I did this last night since restoring my TWRP 3.0 backup locked me out of my 5X lol
Edit: just want to be clear, I do not have Cerberus. idk if it blocks the above combo as well
Click to expand...
Click to collapse
You're right, that way definitely works. And I'm not sure that it it can block that tbh
2x4 said:
You're right, that way definitely works. And I'm not sure that it it can block that tbh
Click to expand...
Click to collapse
Keep in mind that when your data is encrypted and a boot password is used, they may can get into the bootloader, but they can not get inside your system. They will have to wipe it to get anything on it that will work.
Agent said:
Keep in mind that when your data is encrypted and a boot password is used, they may can get into the bootloader, but they can not get inside your system. They will have to wipe it to get anything on it that will work.
Click to expand...
Click to collapse
Thanks for the clarification. Is there any way to get the boot password feature without encrypting my data?
I have read that the most secure way to wipe data permanently on android devices and preparing them for sale is to do two things:
1- encrypt the device
2- factory restore
Since Nexus 6p comes already with mandatory encryption, then the only thing I have to do is to just reset the device to factory setting, is that true?
one1111 said:
I have read that the most secure way to wipe data permanently on android devices and preparing them for sale is to do two things:
1- encrypt the device
2- factory restore
Since Nexus 6p comes already with mandatory encryption, then the only thing I have to do is to just reset the device to factory setting, is that true?
Click to expand...
Click to collapse
Yes, right. You will just need to flash the factory image, and your device will be encrypted, all by itself. This will completely wipe the storage, so make sure that you do a backup first.
DJBhardwaj said:
Yes, right. You will just need to flash the factory image, and your device will be encrypted, all by itself. This will completely wipe the storage, so make sure that you do a backup first.
Click to expand...
Click to collapse
Thanks DJBhardwaj, but why do I need to flash the factory image? the device is already encrypted?
one1111 said:
I have read that the most secure way to wipe data permanently on android devices and preparing them for sale is to do two things:
1- encrypt the device
2- factory restore
Since Nexus 6p comes already with mandatory encryption, then the only thing I have to do is to just reset the device to factory setting, is that true?
Click to expand...
Click to collapse
That's correct. Encrypt the device first via the settings menu (Settings/Security/Encrypt Phone), then flash the factory images to return to stock. See my guide for detailed instructions:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Look at section 10 specifically, this instructs you how to return the device to the state it was in when it left the factory, including removing all of your personal data.
one1111 said:
Thanks DJBhardwaj, but why do I need to flash the factory image? the device is already encrypted?
Click to expand...
Click to collapse
Sorry, my bad. Just do a factory reset via stock recovery, or from within the Settings itself.
one1111 said:
Thanks DJBhardwaj, but why do I need to flash the factory image? the device is already encrypted?
Click to expand...
Click to collapse
To ensure that it's in a completely stock state for the buyer. Or has it never been modified?
Heisenberg said:
To ensure that it's in a completely stock state for the buyer. Or has it never been modified?
Click to expand...
Click to collapse
it has never been modified, no.
one1111 said:
it has never been modified, no.
Click to expand...
Click to collapse
My mistake! I'm so used to people having modified devices that I automatically assume every device is. As DJ already said a factory reset should suffice.
DJBhardwaj said:
Sorry, my bad. Just do a factory reset via stock recovery, or from within the Settings itself.
Click to expand...
Click to collapse
Don't use recovery unless you have already deleted all accounts. The new user will end up needing your Google login to be able to get into the phone.
Solutions Etcetera said:
Don't use recovery unless you have already deleted all accounts. The new user will end up needing your Google login to be able to get into the phone.
Click to expand...
Click to collapse
This happened to me when I sold a Moto X on Swappa. I ended up giving the buyer my credentials over the phone then changing them 5 minutes later.
Sent from my Nexus 6P using Tapatalk
Solutions Etcetera said:
Don't use recovery unless you have already deleted all accounts. The new user will end up needing your Google login to be able to get into the phone.
Click to expand...
Click to collapse
Wow. Good to add something to the knowledge.
Hi so I just rooted my op6t yesterday after having it for a couple weeks and I did everything fine and installed a couple root apps. I later discovered custom kernels and wanted to flash one. I went into twrp and all the folders were weird names and the same thing shows on my computer when I plug the phone in. After looking it up my phone is encrypted. I never clicked anything that said to encrypted my phone and it wasn't encrypted before. In Android it says it's encrypted and now I have to reset it to unencrypt it? I'm ok with that but that's a little annoying. Some people said something about a bug in twrp that has to do with encryption but I'm confused why my phone just did that. I restored apps and settings with Google backup which I ran right before I rooted the phone and restored right after I rooted it. Does anyone know what caused it to encrypt itself and how I can prevent it from doing it again? Thanks.
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
OnkeIM said:
are you sure you had encryption disabled before? my 6t was encrypted from the beginning. I installed root with twrp by using ADB sideload and I never used the file explorer from twrp itself.
if encryption was off, this happened on my old Nexus 6 sometimes too after installing a custom kernel. it was every time really annoying that I got force encrypted even when the kernel builder stated that it does not...
Click to expand...
Click to collapse
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Skyline3499 said:
Maybe it was encrypted from the factory. I could access files through my computer though. Should I reset the phone and flash twrp again then turn off encryption in Android settings? I'm a bit new to this so I'm not entirely sure. I just followed the guide on xda for rooting and unlocking the 6t bootloader.
Click to expand...
Click to collapse
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
tech_head said:
You should still be able to access files from the computer.
The phone should work fine.
It's just that the version of TWRP you have does not support encryption.
Click to expand...
Click to collapse
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Skyline3499 said:
I think it does though I tried the decrypt command in twrp terminal but it failed. It wants a password and I tried my pin which didn't work.
Click to expand...
Click to collapse
That version of TWRP does not support decryption.
GO back and flash the stock boot image.
Temp boot TWRP.
install Magisk and move on.
yerger said:
Sounds like you need to do a lot more reading before you attempt to modify your phone. The phone comes encrypted from the factory. There are plenty of topics about this exact issue. Also, if you had read anything in this thread then you would see that decryption in TWRP was fixed a while ago. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Click to expand...
Click to collapse
Ok, thanks, that twrp version worked with the encryption and everything if fine now.
Well, decryption actually. I would love to disable encryption entirely like on the OP6, but apparently that's not possible due to the fingerprint or something. It's so frustrating. I load OOS then Havoc (or ASOIP, maybe others) and everything seems fine until i try to flash something in TWRP only to find it won't accept my pattern, pin, fingerprint etc. Anyone seen this?
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
king_david43 said:
The other day it did that to me but when I skipped the pattern my files still showed up as normal. I'm using TWRP 3.3.0-2
Click to expand...
Click to collapse
ZeroKool76 said:
You have to clean flash an April security patch build, add your password/pin etc., then dirty flash to May and it will work
Click to expand...
Click to collapse
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
jaysonic88 said:
Hmm, i swear i think i tried that a couple times. :latest release, no beta.
I'm very familiar with wiping the data partition to create a fresh decrypt one. I think i just need a no-forced encrypt zip like on OP6. Unfortunately i think that screws up login attempts because of the fingerprint being proprietary. If someone knows a way or is working on it, you'd be my hero.
Click to expand...
Click to collapse
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
reppi said:
Have you tried to format data instead of wiping? Some ROMs like treskmod require this for successful decryption.
Click to expand...
Click to collapse
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
jaysonic88 said:
Sorry, yes that's what i mean. I indeed do completely format the data partition where it prompts and requires "yes" to do so. The odd thing is it DOES decrypt it just sometimes encrypts again and then locks me out. I do tend to reinstall twrp and root more than is probably required (to get safetynet passed). Is there some rule i need to follow or something i need to do during each flash to prevent this?
Thanks by the way for everyone's input.
Click to expand...
Click to collapse
Ok, i think i found the issue. According to the guy who wrote the unofffical TWRP 3.3.02 it's a bug in the code. He sent the info including the lines of code that were causing the problem to teamwin.
https://forum.xda-developers.com/showpost.php?p=79515334&postcount=2559