Hey
I disabled encryption my Nexus 5X once I was on 6.0 using TWRP.
Now after upgrading to 6.0.1 the device is encrypted again.
How can I avoid that in the future? I want to device to stay decrypted when I upgrade.
Thanks
When upgrading, if you flash the stock boot/kernel and start up Android it will encrypt your data again. To avoid this make sure you flash a custom boot/kernel that does not force exception before booting into Android
So installing twrp and elementalx right after upgrading should be OK?
Upgrade
Flash TWRP
Format
Flash systemless SuperSU
Flash ex kernel
That's the order I did it in and my phone is not encrypted
If you are already decrypted, upgrade by flashing system.img (along with vendor, radio, bootloader). Don't flash data.img, so you don't lose your current data. You also won't need to format the data partition if you are already decrypted.
Just make sure you flash a modified boot.img each time you upgrade before booting back into the system (best to make sure the modified boot.img is for that specific build) - or go systemless and flash SuperSU that modifies the boot.img automatically to remove encryption.
Thanks I'll do that next time!
I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk
hamedunix said:
I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..
tacofromhell said:
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..
Click to expand...
Click to collapse
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk
hamedunix said:
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.
peltus said:
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.
Click to expand...
Click to collapse
Been into rooting and stuff like that; however, I don't mind encryption as long as it won't affect my experience on N5X.
Sent from my Nexus 5X using Tapatalk
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs
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.