I have searched all over and I cannot seem to find a working solution to what I am looking for. I want to use full disk encryption with my Oneplus 5. All posts say you can disable encryption totally. I can do that, no problem. I cannot get it to turn on full disk encryption. I do not want file based. Is there any way of doing this with Android Oreo? Did google remove all possibilities?
Does anyone know how to enable full disk encryption on Oreo and the Oneplus 5? This is all stock except root.
Something like this?
So far as I'm aware the phone when in nougat was encrypted, it's only through choice and the obvious data format that decryption had been possible and it's been more of a requirement for newer ROM's.
If it's a ROM you're flashing then just choose encrypted.
maikvitesse said:
Something like this?
Click to expand...
Click to collapse
That worked great for Android 7. That zip no longer works on Android 8. I have found updated zips for 8. I have verified that it changes the fstab file like it should, but upon format and reboot it is either back in FBE or no encryption and fails/does nothing to FDE.
Sent from my OnePlus 5 using XDA Labs
dladz said:
So far as I'm aware the phone when in nougat was encrypted, it's only through choice and the obvious data format that decryption had been possible and it's been more of a requirement for newer ROM's.
If it's a ROM you're flashing then just choose encrypted.
Click to expand...
Click to collapse
Yes, in 7 it was FBE stock. I was able to disable forced encryption (and format data). I than went and turned on FDE. Everything was grand!
Now in 8, I can disable it but it either still has FBE on or all encryption off (does show in settings and allows to attempt to turn on) and not allowing me to turn on FDE.
I am only flashing stock OxygenOS 5.0.1 and Magisk. I just want to turn off encryption and format data and be able to turn on FDE. I do not want any of FBE.
Sent from my OnePlus 5 using XDA Labs
dl200010 said:
Yes, in 7 it was FBE stock. I was able to disable forced encryption (and format data). I than went and turned on FDE. Everything was grand!
Now in 8, I can disable it but it either still has FBE on or all encryption off (does show in settings and allows to attempt to turn on) and not allowing me to turn on FDE.
I am only flashing stock OxygenOS 5.0.1 and Magisk. I just want to turn off encryption and format data and be able to turn on FDE. I do not want any of FBE.
Click to expand...
Click to collapse
I think things have changed since nougat mate. Didn't the beta require decryption ? Might be a knock on effect of that, personally I don't care for encryption, unless every dev is using it as it causes issues between ROM changes.
Is there a reason why you have to have encryption Vs decrypted ??
dladz said:
I think things have changed since nougat mate. Didn't the beta require decryption ? Might be a knock on effect of that, personally I don't care for encryption, unless every dev is using it as it causes issues between ROM changes.
Click to expand...
Click to collapse
I did not install the beta. This is my only phone and I do need it to run right. I know when the Nexus 6P got 8 it could still use FDE. I actually updated from 7 to 8 on the 6P with FDE on. Just had to flash Magisk and let it turn of forced encryption.
I just want to have FDE over FBE.
Sent from my OnePlus 5 using XDA Labs
Related
Hi,
I installed a recent nightly and everything is fine, however, when restoring my TWRP backup (CM10.2), my encryption password is no longer recognised and system won't boot.
The password is accepted by TWRP and also by restoring the OMNI password, but when I restore the CM10.2 image, the password is not accepted.
Has anything major changed in dm-crypt?
Thanks.
Yes, 4.4 changed the encryption algorithm to use scrypt. It was converted when you upgraded, so you won't be able to switch between without removing the encryption
Sent from my Nexus 5
Mevordel said:
Yes, 4.4 changed the encryption algorithm to use scrypt. It was converted when you upgraded, so you won't be able to switch between without removing the encryption
Click to expand...
Click to collapse
Thanks, I had to remove encryption, restore and encrypt it again.
Looks like I have to wait a while until all features are added into omnirom (quiet hours, battery percentage (!) etc).
One Plus Two (chinese version), oxygen os 2.0.2, twrp recovery & supersu.
If I try to encrypt the phone storage (settings -> security), accepting all the warning, the android robot appears a few seconds, then the phone reboots itself, but the device is not encrypted.
Any ideas?
Thanks!
I've tried also to do it in safe mode, but the same result, reboots and the device is not encrypted
I wiped the device and started from scratch and now it works
I think that it was my mistake because I was trying to encrypt it using PIN protection instead password... so maybe I didn't need to wipe it but...
Same problem on OneA2001
e-Minguez said:
I wiped the device and started from scratch and now it works
I think that it was my mistake because I was trying to encrypt it using PIN protection instead password... so maybe I didn't need to wipe it but...
Click to expand...
Click to collapse
Can anybody provide more details on this issue? Im having the exact same problem; Phone is 100% charged, Click encrypt and the phone briefly reboots but doesnt encrypt. Ive tried both PIN and Password as options but neither seems to work....
If you are using twrp I don't think it works. They don't support encryption on the OPT yet.
Sent from my ONE A2003 using Tapatalk
da_anton said:
If you are using twrp I don't think it works. They don't support encryption on the OPT yet.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Twrp cannot read your internal storage, but you can sideload otas, zips,...
Try a full wipe and encrypt it before starting to install apps... (it worked for me...)
if you encrypt while in OxyOS 2 you can keep the encryption and move forward with OxyOS 3 and onto other custom ROMs.
OS 3.1.0 | TWRP 3.0.2 - 2: encryption ?
Hello Team,
I have similar problem with encryption.
device configuration:
- Latest stock os 3.1.0
- TWRP 3.0.2-2
- root
- fully wiped
when I choise encrypt, phone reboots to bootanimation (spinig wheels) and do not go futher. Device left c.a 12h at this state and afer reboot no encryption.
As 3.1.0 is quite fresh compilation, there is not much at net about. Do you have any possibile solutions?
thnx
Encrypt for corporate e-mail and calendar access
Hi Guys, I have the same issue (Cannot encrypt my One Plus 2) , my settings:
Model - ONE A2011
OxygenOS - 3.5.8
Tried with pin and password, it justs reboots the device and doesn't encrypt.
I need the to encrypt in order to have access to corporate e-mail and calendar.
Thanks for the help.
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Thanks for the tip, seems to work :good:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
amirfk12 said:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
Click to expand...
Click to collapse
You need to change it to another security type. For example if you have a PIN change it to pattern and back or vice versa
tried that. didn't work. any other ideas?
I never set secure startup and mine reset every reboot. Since I reboot every day.
Sent from my Nexus 6P using XDA Free mobile app
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Can not remove the secure startup
uknowme4me said:
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you factory reset through recovery mode or through backup and reset setting?
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
uknowme4me said:
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
yeah, was chatting with Google CS....wiped cache, didn't work and so they suggested factory reset. if it didn't work for you, i don't think i'm going to do it
My 6P requires patern before boot up and sRGB does not reset by itself.
Sent from my Nexus 6P using Tapatalk
That did the trick! Thank you!
For those of you still having issues, here are the steps: Settings > Security > Screen Lock (top option on this page) > confirm your password/pattern/etc. > choose a new one (can be the same as before) > THEN you choose the "Secure Start-up" yes or no. CHOOSE " No Thanks" ...Problem solved. Well, for me at least.
Absolutely 100% stock
Non rooted
Build number MDB08K
enhancedcollagen said:
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Click to expand...
Click to collapse
if you disable Secure startup doesn't that make device encryption useless?
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
chaddesch said:
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
Click to expand...
Click to collapse
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
chaddesch said:
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
Click to expand...
Click to collapse
It won't but there's nothing wrong with ADB Sideload the OTA zip or manually flashing boot, system and vendor. Just make sure to go directly into TWRP (do not boot into the rom) and flash superuser/custom kernel before booting up to stay decrypted. I've manually installed each OTA and kept decrypted doing those steps.
Sent from my Nexus 5X using Tapatalk
I recently bought a Nexus 6P and I just rooted it a few days ago. I have been reading about how it is less safe now that the bootloader is unlocked, so I figured I could encrypt my phone for more securities! I don't want ro re-lock since unlocking will wipe my data all over again.
So I went into Settings->Encrypt phone and started the encryption process. It first showed a green outline of an Android, then it started the boot animation. It stayed there for about half an hour and it was clearly not encrypting (not getting hot or anything) so I just rebooted (I have a backup, that's why I'm so bold ) and it just normally rebooted to a working phone with nothing encrypted. Tried it again, same result.
I'm running Marshmallow 6.0.1 MMB29M with TWRP, SuperSU (I'm pretty sure it's systemless) and Xposed. I'm not sure what kernel I flashed when I rooted (that is the boot.img, right?).
Is this a bug? Is it a feature? I would like to be able to encrypt my phone; does anyone have any ideas on how to achieve this, now that TWRP can decrypt stuff?
Thanks!
I have the same issue with a HTC One M8 running Marshmallow 6.0 and systemless root. I've had this phone encrypted in the past but that was with standard root. Seems like systemless root and something to do with the modification of the boot image has something to do with encryption breaking.
Glad I made a nandroid before starting also, just incase.
I got it to work
So I just flashed the latest 6.0.1 (MMB29P) system, boot, etc. partitions because of the January security update. I folllowed Heisenberg's guide, point 10. I then had to reflash TWRP and then install SuperSU and Xposed again, because they were gone.
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
What you need to do is to remove any security you set up (just set the lockscreen unlock to "None") and then re-add it. When the phone asks if you want it to require the password at startup, say yes. It will then change the encryption password to your custom one and voila, your phone is now encrypted and uses your password/pin/pattern/whatev.
tudy77 said:
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
Click to expand...
Click to collapse
Question, is the default password: "default_password" lowercase and all? Im on the same boat you were, about to do this just to get encryption back but i want to be 100% sure of the steps lol
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
tudy77 said:
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so i dont type anything just hit enter?
I was not prompted to type anything
Sent from my Nexus 6P using Tapatalk
Hello,
I have a question about force encryption and how to disable it.
I want to use encryption, but I want to setup with a specific Password and not with pattern lock. Do I need to remove the forced encryption to do so?
I already tried flashing Disable-Force-Encryption-Treble.zip, but under phone settings on Havoc it still says "Encrypted and therefore there is no option to enable encryption since it already is. I already tried different TWRPs and many times reinstalling Havoc, wiping partitions and formatting the Data Partition, but somehow nothing seems to remove this encryption.
Maybe I just missed something...
Many thanks in advance