Develop Bugs

How To re-encrypt my OnePlus 3 ?

Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.

You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.

As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.

abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?

formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.

Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.

Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !

Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?

Nokia 6.1 stuck on unlock screen

Hello, I haveNokia 6.1 (2018) and I have just got it into a strange state. It happened during custom rom install, or to be more precise during the set-up (probably). I have finished setting up the Omni ROM from this thread (https://forum.xda-developers.com/nokia-6-2018/development/rom-omnirom-t3945850) and wanted to install magisk to have root.
After downloading the .zip file, I rebooted into TWRP (through the fastboot mode and using the "fastboot boot image.img" command) and TWRP asked for a password to decrypt the storage. I tried password that I am pretty sure is correct, but the TWRP insisted it is incorect. I tried several variations to it in case I made a misclick during a setup but no luck. I wiped everything (system, cache, data, sd) and through a fastboot mode I uploaded stock boot, vendor and system to both slots.
After the reboot, I am stuck on the password (system PIN, to be precise - not the SIM PIN, that is OK) screen. When I enter an incorrect PIN, it will say that the PIN is incorrect, but when I enter the correct one, screen just goes black for a while and I am back at the screen to enter the PIN.
Is there a way to get out of this mess? I am able to get into fastboot mode and boot recovery.
Any help would be much appreciated.

More details about the process as I forgot to include. TWRP used was 3.2.3 from this thread (https://forum.xda-developers.com/no...recovery-twrp-3-2-3-0-touch-recovery-t3825545). Stock FW (Nov 2019 version) used was from this thread (https://forum.xda-developers.com/no...de-how-to-make-backups-restore-stock-t3889815)
Before the OMNI ROM install I have tried stock system with custom vendor (version 2.2 from the thread linked in the OMNI ROM thread) which could also contribute to the failure, but the phone did not even boot (it got stuck on the "android one" logo). I hoped that I could at least get the ability to convert SD to internal storage, as that feature is disabled on stock, but with custom vendor it works (tested on the OMNI rom, which I managed to install correctly before)
I have also found here an OST tool, which could potentially help with the situation (I am not sure) but I am missing the original firmware files to use with this tool.
The problem must be with the internal storage encryption, which got messed up in the process (I am not still sure, what went wrong). Am I correct that now I would need to find the original loadout (is there something as RUU available fror this model?) and basically revert everything including the bootloader unlock and start from the begining? Could someone here point me in the right direction how to fix this issue?
If the only way is to pay someone to fix this issue, I will gladly provide any reasonable amount if it will resolve my problem.

So all I had to do was boot into TWRP and do a factory reset from there. How stupid of me that I did not try this.

Using TWRP recovery to repair LineageOS System

Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk

Z4_ said:
Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk
Click to expand...
Click to collapse
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.

kurtn said:
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.
Click to expand...
Click to collapse
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.

Z4_ said:
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.
Click to expand...
Click to collapse
There is twrp 3.4 out now. Fixed many android 10 bugs

kurtn said:
There is twrp 3.4 out now. Fixed many android 10 bugs
Click to expand...
Click to collapse
As you might have read in my original post: I was on android 8 and using twrp 3.4. It still did not work.
I have now switched to an unofficial CrDroid ROM with Android 9, as any attempts to restore my backups or install my used ROM lead to errors. This makes the restore of app data difficult, but my smartphone is back to action. I still do not know what caused the errors.

[HELP] XT1794 stuck at fastboot/twrp after infinite boot anim on the latest los16

Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.

First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot

JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.

You can try using adb sideload. adb sideload path/to/zip

worked like a charm. thanks a lot, Jarl.

And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled

Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.

Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that

OnePlus 7T Android 12 TWRP?

Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but nothing has worked for OOS 12. I am able to extract the OOS 12 stock recovery.img with Payload Dumper, and am able to create a basic TWRP device tree for android 12.1 using the official TWRP 12.1 Github manifest, but I'm not able to find a good guide to create a TWRP-ready device tree from my stock recovery.img I mentioned earlier. I've tried updating to OOS 11, and using the twrp-keep module on the magisk modules github to keep the official TWRP installed. (It support OOS 11, but not OOS 12). I've also tried flashing the unofficial build made by Mauronofrio, but none of the specified methods have worked. Can someone please either make a OOS12-compatible version of TWRP for the OnePlus 7T, or if they can't do that, guide me in a step-by-step process on how to do i myself? Any help would be greatly appreciated.

Oos12 does NOT support twrp nor does A13

I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge

rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
I just flashed it, and it booted successfully! I'll let you know if I can format /data.

Format /data works.

For confirmation, I flashed the .img of the OOS12 version to the recovery partition.

rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.

SiegeDaBoss said:
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
Click to expand...
Click to collapse
I just tested the non-OOS Android 13 TWRP file, and it has the same issue.

Can u back up all partitions except data? At least that would be helpful

HueyT said:
Can u back up all partitions except data? At least that would be helpful
Click to expand...
Click to collapse
Nope. Even when I de-select Data, and select everything else, it still fails with the "Failed to mount /data" error.

Yeah, I was afraid of that. No one has cracked twrp for oos12 yet

HueyT said:
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
Click to expand...
Click to collapse
I mean, at least both of them boot.

rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.

SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Thank you for testing the builds and for the feedback . I've been on oos11 for a long time, but today I'm going to flash oos12. Because i would need recovery log files to fix errors.
I don't have no time for some fixes, i will try to fix errors whenever possible.

did you not ttry to use the twrp and the twrp installer builds that are on official twrp site for one plus 7t

then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .

SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Hi again, i updated my repo and download links.
-OOS12 decryption working.
-Flash zip working . "I installed with zip by the Magisk and copy partititon, i flashed los20 & stock oos12 .)"
-Adb sideload working, i tried stock oos12 flashed successfully.
-Format data working.
-Mtp working.
-Otg working.
-Adb working.
-Vibration working.
* Backup data working, but restore data on oos bootloop
* i use swift backup instead of nandroid backup
When i have free time, i will work on twrp a13 fbev2.

mrk2815 said:
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
Click to expand...
Click to collapse
Every ROM comes built-in with its own recovery. So you'll have to flash the ROM via that recovery's ADB Sideload feature.

lets hope you can get a working twrp going for both andrid 12 and 13 .as my one plus 7t is just been put away in my drawer after seeing that one plus has given up on these older devices. when there is a working twrp i would probably want to flash something down the road. my primary driver unfortunately is a samsung S21 plus .

rabilgic said:
Hi again, i updated my repo and download links.
OOS12 decryption working.
Mtp working.
Adb working.
Vibration working.
I installed with zip by the Magisk and copy partititon.
Backup/restore boot.img working.
I haven't tested: flash rom, format data, needs some testing
When i have free time, i will work on twrp a13 fbev2.
Click to expand...
Click to collapse
All works until I tried to restore. Then it got stuck at red dot going around in circle. When I tried to go back in twrp again to format data, it won't mount data after that. Ended up having to restore all over using msmtool.
It mounted data fine before I tried to restore the data part, then it messed up decryption of data despite not having a lock code, no fingerprint, no pattern-lock, or lock screen enabled.