Database Users

Encryption doesn't work?

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.

Found out why sRGB mode keeps resetting after reboot

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

OS pin incorrect, but same pin works for TWRP and Android cold boot login

*Fixed by suggestoins below.*
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks

strifej said:
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks
Click to expand...
Click to collapse
Yeah, that's a normal problem. I think there's a guide, but you simply have to go to TWRP's file manager and delete a couple of files (I don't remember the exact files, search on XDA for that). One of them is lockscreen-settings.db I think, so you can use that as a keyword

strifej said:
Hey,
So all of a sudden, I can't login to my phone after it boots (where you usually use fingerprint). I enter my pin but it says it's wrong, but I know it's right because it works for TWRP and during Android boot.
Anyway to fix without having to factory reset/format data?
Thanks
Click to expand...
Click to collapse
Yep, CaUname got it:
- Boot toTWRP Recovery
- Use the File Manager & navigate to:
- data > system > locksettings.db -- Delete that file
- reboot then re-setup your pin
Good luck

Oneplus 5 with OxygenOS 5.0.1 Use Full Disk Encryption

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

8.1 - lost data after update

I am 100% stock, did the update earlier and I now can't get any data (2g, 3g or 4g) wifi is fine but I just can't get any data.
I had data turned off during upgrade and after upgrade I noted it was turned on again, not sure what to do now.

Update, not only was my SMS history deleted by the update, my APN settings were also deleted, inputting them again sorted my data.

I also lost all my SMS messages ...

dlhak said:
I also lost all my SMS messages ...
Click to expand...
Click to collapse
Thank goodness for SMS backup and restore.

Did you use any 3rd party app for sms backup and restore? I lost my messages too. The only backup I have is 6 months old.

After update to 8.1, Jio Sim is not working on both the slots. Messages wiped out. In Android version it is showing a"prerelease".
Tell me something such that my Jio Sim starts functioning.

I lost my SMS messages and Developer options got disabled for some reason. Gcam is working fine and Bluetooth connection is working fine again.

subiranjan said:
After update to 8.1, Jio Sim is not working on both the slots. Messages wiped out. In Android version it is showing a"prerelease".
Tell me something such that my Jio Sim starts functioning.
Click to expand...
Click to collapse
Settings>network & internet>Sim cards>Cellular data> change to jio

I just updated to 8.1.0 and I lost nothing.
Also you might wanna change your title from "lost data" to "lost mobile connectivity".

I also lost all my msgs after 8.1 update. Is there any option or way to restore my recent msgs. I had also taken backup long time ago.

Lost all my SMS too!
Sent from my Mi A1 using Tapatalk

Lost all text messages
How can I get lost sms back, I updated to 8.1 June update and after restarting all my messages are gone , need help
mediately.

varishtg said:
Did you use any 3rd party app for sms backup and restore? I lost my messages too. The only backup I have is 6 months old.
Click to expand...
Click to collapse
Yes lucky for me I was using SMS backup and restore and my last auto backup was a week ago.

Did Xiaomi pull the Trigger? No update for me.

I can't not help you. Just can say I updated yesterday and I'm not experimenting any issue. However you may change the post tittle. My updated was as follows:
Previous:
Set magisk core mode -> Uninstall xposed SDK26 module -> Restore boot.img
Update:
Update -> Patch boot.img with magisk -> Reboot -> Everything fine
After update:
Enable magisk -> Reboot -> Bootloop -> Boot into TWRP and flash magisk uninstaller -> Reboot -> Everything fine -> Boot into TWRP and flash magisk -> Reboot -> Everything fine -> Install xposed SDK27 module and unified hosts adblock -> Reboot -> Everything fine till now
Goods founds after update to 8.1:
Camera lag using magisk solved -> Fixing module not needed anymore
GCam working without enabler module -> Module not needed anymore
Swipe FPS for notifications come back -> Find under settings, gestures
Native dark theme -> Substratum not needed anymore
Also found update is not available for everyone. My mothers one full stock system is not receiving. I attached images with my setup.
Hope my info is useful for someone.

pastarasta said:
Did Xiaomi pull the Trigger? No update for me.
Click to expand...
Click to collapse
Yep,the pulled the update looks like,maybe bcs that sms bug.
Tried to update mine but i got a wifi problem so i restarted my phone,after i restarted it, it's gone

also lost SMS messages using the standard magisk OTA update way. luckily had a daily automatic backup setup using https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore

Lost all my SMSes after updating to 8.1.0.
kudos1uk said:
I am 100% stock, did the update earlier and I now can't get any data (2g, 3g or 4g) wifi is fine but I just can't get any data.
I had data turned off during upgrade and after upgrade I noted it was turned on again, not sure what to do now.
Click to expand...
Click to collapse
kudos1uk said:
Update, not only was my SMS history deleted by the update, my APN settings were also deleted, inputting them again sorted my data.
Click to expand...
Click to collapse
My last SMS backup is of Oct 2017 when I changed over to Mi A1. What are my options to recover these messages, if at all?! Thanks

KayteeShanx said:
My last SMS backup is of Oct 2017 when I changed over to Mi A1. What are my options to recover these messages, if at all?! Thanks
Click to expand...
Click to collapse
Don't think you have much of an option.
The only thing you could check is to see if google is backing up your sms's
See here: https://forum.xda-developers.com/mi-a1/help/google-photos-backup-off-t3810065
Some A1's are backing up as part of Google's backup..... but....... you can't manually restore the backup, the only way would be to reset the phone and let it pull the SMS's down as part of the setup. Or maybe if you have a spare phone you could restore it with the A1's google backup, then use SMS Backup & Restore app to make a backup, then push the backup to the A1 (long winded but would work).
If your phone is backing up SMS's you would also need to check when the last backup was, if it has backed up since the update your backup might be replaced with what is on your phone..... ie nothing.

surajsun22 said:
Also you might wanna change your title from "lost data" to "lost mobile connectivity".
Click to expand...
Click to collapse
Titles cannot be edited, I tried.