Database Info

Data Partition Encryption

Hey all,
I unlocked bootloader, installed TWRP and installed Magisk just fine.
As far as I was aware, I had disabled encryption on the sdcard, and this makes sense as I flashed Magisk from its installation zip in my sdcard.
However, I just rebooted to recovery in order to make a backup
It prompts me to input password in order to decrypt data.
I don't need to input password, I can click cancel and get to TWRP, but then, using its file manager, I see that all file names are in gibberish. Obviously the personal data Partition is also read only
I don't know how it got encrypted, and it was after I installed Magisk from sdcard, showing it was not encrypted at some point.
Well I can't make a TWRP back in this state.
Anyone know how it got encrypted again and how to undo that so I can make backups?

for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.

Ajaykumar21066 said:
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Click to expand...
Click to collapse
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone. ?
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs

drakenabarion said:
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone.
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
only change was you didnt have any lockscreen pin setup on your phone, And now you have one i think. its the same pin twrp is asking for.

Ajaykumar21066 said:
only change was you didnt have any lockscreen pin setup on your phone, And you have one i think. its the same pin twrp is asking for.
Click to expand...
Click to collapse
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison! ??
Sent from my OnePlus 6 using XDA Labs

drakenabarion said:
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.

Ajaykumar21066 said:
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Click to expand...
Click to collapse
The important thing for me now is that I have a stable backup. It can take me days to setup a new phone to my comfortable default setting, so now I feel secure that I have a saved image of my idea of a good install. So thank you for helping with that!
But it will be interesting to see how custom roms not based on OOS will be.
Up until my last phone (Honor 6x - proprietary soc, therefore limited rom support), I would flash a custom rom ASAP (typically LineageOS or before that, CyanogenMod). But I already get that kind of experience (with good historical reasons I guess) from OOS. It would take a bit to tempt to flash something else. ?
Sent from my OnePlus 6 using XDA Labs
And might I just say that woohoo for large storage! My previous 32gb phone took 10 gb for firmware and left me struggling after installing a normal set of apps, typically leaving me about 10gb to put music etc into. My backup that I just made took 18gb, because I installed alot of games I couldn't before, is bigger in general than base free space before!

Pixel is stuck at "Pixel is starting"

My bootloader-unlocked Google Pixel runs Android Pie and it uses file-based encryption. Both system partitions are unmodified.
In an effort to get TWRP to successfully decrypt my Pixel's encrypted data, I performed a combination of:
Renaming these files (i.e., appending .bak to their names):
Code:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.pattern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
Copying the files back to their original names.
Setting and removing a lock pattern/password/PIN.
Now, my Pixel does not move past the "Pixel is starting" page. I can access Settings, but I have no access to my applications and files. How do I fix this so that I can get it to move past "Pixel is starting"?

I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Hang on. Did you skim my post? I'm trying to get it to decrypt or, if the decryption is not the problem, just get past "Pixel is starting" and get to my things on it. Wiping it won't fix that!
Fingerprints are not used to decrypt the device.

Bump.

Anyone else? What could be the cause of this? Would it give an error message if it couldn't find the right files?

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Are you there?

TENN3R said:
I once ran into this issue, it has something to do with fingerprint and encryption, somehow it unlocks but it won't decrypt.
The only solution I've found is to wipe the device. Since you can power on the device, I suggest you to backup what you can with adb or from twrp, and do an advanced wipe, with even "format data" enabled (warning: you lose also /sdcard files), then reflash the stock factory image from fastboot.
This should remove the corrupted lock files and set it up like new.
Click to expand...
Click to collapse
Were you able to recover your data?

Bump.

Unfortunately not. I just wiped the device, maybe there is some way but I really don't know. Wiped and setup again

Bump.

Bump.

Someone please help.

Master Melab said:
Someone please help.
Click to expand...
Click to collapse
Wipe your phone maybe.

what is wrong with you all you needed to do to decrypt in twrp is disable your lock screen security, none of this other bull**** lmao.

Please help.

SnowFuhrer said:
Wipe your phone maybe.
Click to expand...
Click to collapse
That won't achieve the desired result as I'm trying to recover my data.

sudoxd said:
what is wrong with you all you needed to do to decrypt in twrp is disable your lock screen security, none of this other bull**** lmao.
Click to expand...
Click to collapse
First, I got into this mess by trying to get that to work. Second, how is this a solution?

Master Melab said:
First, I got into this mess by trying to get that to work. Second, how is this a solution?
Click to expand...
Click to collapse
it is a solution, unless there is something wrong with your phone which is caused by an entirely different issue, to access your data in twrp all you needed to do was disable your lock screen security

Unfortunately I don't think there's a way you can do it. The issue the OP is facing is that the system is unable to decrypt your user data at all, regardless of whether or not you are in TWRP or Stock Android, Stock Recovery, etc.
Trying to read between the lines on the AOSP File-based encryption https://source.android.com/security/encryption, your data is always encrypted - regardless of whether or not you have some security set (pin, password, etc). It's just a matter of whether or not the pin etc is part of the metadata used in the decryption. When you altered the security files that stored the information, you lost the ability to decrypt (probably the files have additional information that is passed with your pin to unlock the encryption keys). Removal of the files needed to be done within the system by removing the security, not by removing the files whilst it is encrypted. (Sorry if this isn't exactly what happened, it's hard to tell the exact sequence of events from the OP, i.e. whether or not it was all done in system, and when reboots were done.)
I did something like this before, and got the same result. Sorry but you'll have to rely upon the latest Google backups you had...

NZedPred said:
Trying to read between the lines on the AOSP File-based encryption https://source.android.com/security/encryption
Click to expand...
Click to collapse
I've tried, but I am unable to follow all of it.
NZedPred said:
your data is always encrypted - regardless of whether or not you have some security set (pin, password, etc). It's just a matter of whether or not the pin etc is part of the metadata used in the decryption.
Click to expand...
Click to collapse
I'm aware of that.
NZedPred said:
When you altered the security files that stored the information, you lost the ability to decrypt (probably the files have additional information that is passed with your pin to unlock the encryption keys). Removal of the files needed to be done within the system by removing the security, not by removing the files whilst it is encrypted. (Sorry if this isn't exactly what happened, it's hard to tell the exact sequence of events from the OP, i.e. whether or not it was all done in system, and when reboots were done.)
Click to expand...
Click to collapse
The files I touched have nothing to do with decryption, only unlocking.
NZedPred said:
I did something like this before, and got the same result.
Click to expand...
Click to collapse
Could you please explain what you did?

hide data partition in twrp

I have a unbranded android phone stuck on kitkat and will encrypt fine but have installed a custom rom marshmallow. This doesnt encrypt at all (green robot, reboot and nothing).
What i would like to do is to hide the data partition from twrp so if it gets lost no one can access data. Should be able to lock unlock from os that way i can atleast ensure data is safe. Ideally i would like to encrypt but it cannot find a custom rom with encryption. I cannot lock BL again as it hangs most likely i think cos it rooted. any info ?

I think you can't really hide a partition - really hide data in a partition, even if a dot is 1st character of name of a directory and/or file or the empty .nomedia file is present in a directory. But, if Android is rooted, there a quick and easy, non-desctructable method to make sure the data can’t be accessed without doing some effort. Useful to hide data from a layperson.
The method is simple: flip the 5th least significant bit of the partition ID. The 0x83 for Linux partitions becomes 0x93. Let’s say we want to hide the partition /dev/sdd1 we run in Terminal window
Code:
su
sfdisk --change-id /dev/sdd 1 93
Note: sfdisk is part of BusyBox

thats what im looking or, any chance theres an app for this ? using commands phone side is a bit tricky, an app could make like work of that. Still its good enough maybe.

Deleted member 1890170 said:
I think you can't really hide a partition - really hide data in a partition, even if a dot is 1st character of name of a directory and/or file or the empty .nomedia file is present in a directory. But, if Android is rooted, there a quick and easy, non-desctructable method to make sure the data can’t be accessed without doing some effort. Useful to hide data from a layperson.
The method is simple: flip the 5th least significant bit of the partition ID. The 0x83 for Linux partitions becomes 0x93. Let’s say we want to hide the partition /dev/sdd1 we run in Terminal window
Code:
su
sfdisk --change-id /dev/sdd 1 93
Note: sfdisk is part of BusyBox
Click to expand...
Click to collapse
can i ask if re installin twrp make the data partition reappear ? if not then this is what i could do rather than encrypt. And do you have a more detailed guide on how to do the sfdisk thanks

androzer said:
I have a unbranded android phone stuck on kitkat and will encrypt fine but have installed a custom rom marshmallow. This doesnt encrypt at all (green robot, reboot and nothing).
What i would like to do is to hide the data partition from twrp so if it gets lost no one can access data. Should be able to lock unlock from os that way i can atleast ensure data is safe. Ideally i would like to encrypt but it cannot find a custom rom with encryption. I cannot lock BL again as it hangs most likely i think cos it rooted. any info ?
Click to expand...
Click to collapse
TWRP has the option to password lock TWRP.

Droidriven said:
TWRP has the option to password lock
Droidriven said:
TWRP has the option to password lock TWRP.
Click to expand...
Click to collapse
i dont think it has but even if it does whats the point ? you could reflash twrp writing over the password. But which twrp has this version or where is this option ?
Click to expand...
Click to collapse

@nidowak653
No, flashing TWRP will not remove the password because the password is stored in data partition, not in recovery.
As far as I know, it is and has always been an option in TWRP.
Also, relocking bootloader would wipe all data on the device, defeating the purpose of trying to encrypt/protect your data.
You are aware that if your device is lost or stolen, you can go to your Google account online and use the "Find My Device" option to remotely wipe your device of all data.

Droidriven said:
@nidowak653
No, flashing TWRP will not remove the password because the password is stored in data partition, not in recovery.
As far as I know, it is and has always been an option in TWRP.
Also, relocking bootloader would wipe all data on the device, defeating the purpose of trying to encrypt/protect your data.
You are aware that if your device is lost or stolen, you can go to your Google account online and use the "Find My Device" option to remotely wipe your device of all data.
Click to expand...
Click to collapse
i cannot find any option in twrp to lock the recovery with password, also read this
Why doesn't TWRP have password protection?
I’ve had people ask enough for a protected TWRP that I’m creating this page as a response so I don’t have to retype. If you’re seeing this page, you’re proba...
twrp.me
i only want encrypt to be able to use the fone for work purposes i dont really care about the data or the phone itself they can be replaced but havin encrypt means i can work on it.

[Xiaomi] How to unlock phone after forgetting the password.

Hello,
today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs.
I have Poco F2 Pro on MIUI 13
Is there known a bug which could in any way make me unable to log into my phone?
Please help me. I am really desperate. I beg you. If you need any information about this case and it's sensible to share it there, please ask.

people report similar on updates, but I don't think it's official known bug. however, there is gatekeeper in background which will deny correct password after too many attempts, timeout increases up to 1 trial per day. if something corrupted it might happen this deny is silent without notifying you.
so best what you can do for now is nothing, just wait for 24 hours and keep on charging.

perwell said:
Hello,
today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs.
I have Poco F2 Pro on MIUI 13
Is there known a bug which could in any way make me unable to log into my phone?
Please help me. I am really desperate. I beg you. If you need any information about this case and it's sensible to share it there, please ask.
Click to expand...
Click to collapse
if you're decrypted you can delete your lockscreen in twrp if you're encrypted you'll need to remember your password otherwise it's wipe data

@jons99 if OP would have the availability to access lockdettings it would be also possible to backup data, right?

aIecxs said:
people report similar on updates, but I don't think it's official known bug. however, there is gatekeeper in background which will deny correct password after too many attempts, timeout increases up to 1 trial per day. if something corrupted it might happen this deny is silent without notifying you.
so best what you can do for now is nothing, just wait for 24 hours and keep on charging.
Click to expand...
Click to collapse
It would be strange to ask again for password every 2 minutes and silently block out for the whole day. Actually it would rather bad for the actual users rather than unauthorized break in.
I've tried many times and I'm quite sure that I've typed the correct password at least once. Are there any options like blocking it through Xiaomi cloud and maybe it would ask to log into the account. I've tried changing the password but it still does not work (maybe it was made after too many attempts).
Does the password to phone change when it is changed to the Xiaomi account?

as stated above, it doesn't matter you typed the correct password

aIecxs said:
@jons99 if OP would have the availability to access lockdettings it would be also possible to backup data, right?
Click to expand...
Click to collapse
any one with working twrp can access the lockscreen file but if your device is encrypted you'll be locked out if you delete it

Poco F2 Pro on MIUI 13 /data/system/lockdettings.db is unencrypted despites /data partition is encrypted?

aIecxs said:
Poco F2 Pro on MIUI 13 /data/system/lockdettings.db is unencrypted despites /data partition is encrypted?
Click to expand...
Click to collapse
if his data partition is encrypted then it doesn't matter deleting locksettings won't help

except for most Xiaomi devices encrypted with default_password where lockdettings.db can be deleted safely (if you would have access to decrypted /data partition, which would also allow you to backup /data)

aIecxs said:
except for most Xiaomi devices encrypted with default_password where lockdettings.db can be deleted safely (if you would have access to decrypted /data partition, which would also allow you to backup /data)
Click to expand...
Click to collapse
To access files I need to enable file transfers. Besides I also wouldn't want to risk bricking the phone.

as your bootloader is locked there is nothing you can do anyway... this was just side note question to @jons99
it's true that file-based encryption is tied to lock screen credentials, but MIUI 13 is insecure and implemented metadata encryption in a wrong way so that TWRP is able to decrypt without password, like it was common on full-disk encryption.
full-disk encryption requires decrypted partition first in order to access files on it, so the suggestion to delete locksettings.db is pointless as goal (access /data) would already achieved before. but I am curious about file-based encryption and metadata encryption leaves /data/system unencrypted. while it for sure would break file-based encryption, I am not quite sure this applies to MIUI weak metadata encryption too, if we delete locksettings.db

aIecxs said:
as your bootloader is locked there is nothing you can do anyway... this was just side note question to @jons99
it's true that file-based encryption is tied to lock screen credentials, but MIUI 13 is insecure and implemented metadata encryption in a wrong way so that TWRP is able to decrypt without password, like it was common on full-disk encryption.
full-disk encryption requires decrypted partition first in order to access files on it, so the suggestion to delete locksettings.db is pointless as goal (access /data) would already achieved before. but I am curious about file-based encryption and metadata encryption leaves /data/system unencrypted. while it for sure would break file-based encryption, I am not quite sure this applies to MIUI weak metadata encryption too, if we delete locksettings.db
Click to expand...
Click to collapse
I'm pretty sure xiaomi is using file based encryption and without the locksettings you won't be able to decrypt your data I mean the system will load but you won't be able to use it as it will show phone is starting message forever cause it won't be able to decrypt your data on the other hand I don't know much about xiaomi so I guess anything is possible

nope, actually it's metadata encryption (but I have never seen personally as I don't got such device in hands)
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,checkpoint_merge latemount,wait,formattable,fileencryption=ice,wrappedkey,keydirectory=/metadata/vold/metadata_encryption,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs

perwell said:
Hello,
today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs.
I have Poco F2 Pro on MIUI 13
Is there known a bug which could in any way make me unable to log into my phone?
Please help me. I am really desperate. I beg you. If you need any information about this case and it's sensible to share it there, please ask.
Click to expand...
Click to collapse
Hi my friend
Were you able to unlock your cell phone?
It just happened to me with a xiaomi redmi note 8 and every time I try, the device makes me wait 64 minutes.

SBUnlock said:
Hi my friend
Were you able to unlock your cell phone?
It just happened to me with a xiaomi redmi note 8 and every time I try, the device makes me wait 64 minutes.
Click to expand...
Click to collapse
Did you previously unlocked bootloader with Miflash Unlock Tool?

aIecxs said:
Did you previously unlocked bootloader with Miflash Unlock Tool?
Click to expand...
Click to collapse
Not yet
The truth is that I am new to this, when I investigated about Miflash Unlock Tool, I see that it is used to unlock bootloader, not to unlock cell phone security pattern.
I am right?
I need to unlock the security pattern of my cell phone

you can't unlock bootloader, it's too late. you are screwed. either give it back to the child for playing (hopefully one day it get unlocked) or factory reset phone. you can't break screen lock on locked bootloader no matter what encryption type used.

aIecxs said:
you can't unlock bootloader, it's too late. you are screwed. either give it back to the child for playing (hopefully one day it get unlocked) or factory reset phone. you can't break screen lock on locked bootloader no matter what encryption type used.
Click to expand...
Click to collapse
THANK YOU SO MUCH FRIEND,
Is there an android security option that after many failed attempts, blocks the correct pattern?

until now, theres still no solution to this bug

Factory reset didn't decrypt my Android. It's Android 11 [SOLVED]

Hello, My phone is new & fresh. Sometimes during playing games or heavy tasks, I see some lags. It's KG5K or Spark 8c model & Android 11. I noticed that my phone is already showing encrypted in 'Encryption & credentials'. I tapped on the Encrypted word but nothing comes to make it decrypt. I am a boy and a student. (Not a celebrity ) I don't want privacy or encrypted Android. I want to get highest performance from my phone. So factory reset it from 'Settings' app. But still showing encrypted. So I tried to get to the recovery mode to hard reset. I saw so many tutorials for the same model. Everywhere Volume + & Power button for this phone. I tried but can't get there. Anyway, after connecting another android via wireless adb. I commanded to go to recovery. Finally, I got there. And hard reset it.But I saw it's still encrypted . Any solution? I already lost so many app data because didn't create backup. PLEASE HELP ME DECRYPT IT. SO MY PHONE CAN BE MORE FAST!! AND LET ME USE IT ASAP. I DON'T WANT TO USE IT UNTIL I DECRYPT IT !!!!!!!!

Look inside here:
How to Decrypt an Encrypted Phone
If you have an encrypted phone, you may be wondering how to decrypt it. Answer for common questions about how to decrypt an encrypted phone.
innobytech.com

Thx. But it didn't work. They are talking about keys. Please note that I can't go through the 'encryption' button. Showing no option to disable it or to input keys. Android Device Manager also not showing Encrypt) Decrypt option. I bought it from official Tecno show room. Still if the phone is fake, how can I discover it? Or want to know if there is any way to check if my phone is really encrypted. I have doubt about that the 'setting's 'encryption' word is like a demo word just showing itself. HELP ME!!

To check Android's encryption state you may use ADB
Code:
adb devices
adb shell "getprop ro.crypto.state"

jwoegerbauer said:
To check Android's encryption state you may use ADB
Code:
adb devices
adb shell "getprop ro.crypto.state"
Click to expand...
Click to collapse
Sir, I entered the command via wireless adb. It says "encrypted" . Please see the attached photo. I am afraid now. Help me decrypt it (specially via adb) Any command to do it? !. Please HELP ME!!

You can't remove encryption, AFAIK. Use the device with encryption.
FYI:
That happens when Android boots up

Sorry sir, but that's not a solution. I want to decrypt it. To make it faster. It's Android 11 and it's 2023. It's a modern age and nothing is impossible. (HAPPY NEW YEAR ) You can't leave it like that, sir. Thx.

You simply didn't understand it: encryption takes place when Android boots up, this is forced by Android kernel.
Flash a Custom ROM what doesn't encrypt Android.

It has 12+1 months warranty. So I don't want to install TWRP, root, Custom ROM, Customized Kerbal etc. Because, I'm a student and my exam will held within 4 month from now. Please sir assure me, as you said encryption or decryption happens when Android boots up. So it may take a while to boot up completely. I've no problem in it. Please sir tell me after it boots up is there any decryption process happens further. I meant is encryption/decryption happens only when it boots up and only for that moment. Or it continuously or Constantly run this encrypt/decrypt all the time (when the Android is powered on ) Hope ya understand . And Help to free me from this problem. Thx

lightinfo10 said:
It has 12+1 months warranty. So I don't want to install TWRP, root, Custom ROM, Customized Kerbal etc. Because, I'm a student and my exam will held within 4 month from now. Please sir assure me, as you said encryption or decryption happens when Android boots up. So it may take a while to boot up completely. I've no problem in it. Please sir tell me after it boots up is there any decryption process happens further. I meant is encryption/decryption happens only when it boots up and only for that moment. Or it continuously or Constantly run this encrypt/decrypt all the time (when the Android is powered on ) Hope ya understand . And Help to free me from this problem. Thx
Click to expand...
Click to collapse
then you can't decrypt. you need to format in twrp, reboot into twrp, and flash the decrypt file for your device.

Encryption is mandatory in Android 10 and up.
Factory Data Reset won't decrypt your device and will only regenerate new encryption keys.
The only way to decrypt your device is to unlock the bootloader, and flash no-encrypt in a custom recovery to prevent re-encrypting the flash memory.
Phones nowadays can't experience performance impact from encryption since they have a Dedicated AES engine implemented in hardware so that they can decrypt blocks in memory on-the-fly. You shouldn't really be decrypting your device as it is NOT RECOMMENDED.
Though if you really want to decrypt your device, some phones are decrypted by not using a lock screen as some phones require a lock screen so that they can get data from there to derive a secure encryption key.

Look, your phone doesn't slow down for encryption, the problem you have is that your phone is a low end device. Even if you manage to decrypt it, you won't see any difference except that if someone steals your phone, they will have every data you have. You need to optimize it, you may root it and delete system apps and things like that, when I want a boost in games, i temporary disable Google Play Services and Google Play, then the phone goes faster.
lightinfo10 said:
Hello, My phone is new & fresh. Sometimes during playing games or heavy tasks, I see some lags. It's KG5K or Spark 8c model & Android 11. I noticed that my phone is already showing encrypted in 'Encryption & credentials'. I tapped on the Encrypted word but nothing comes to make it decrypt. I am a boy and a student. (Not a celebrity ) I don't want privacy or encrypted Android. I want to get highest performance from my phone. So factory reset it from 'Settings' app. But still showing encrypted. So I tried to get to the recovery mode to hard reset. I saw so many tutorials for the same model. Everywhere Volume + & Power button for this phone. I tried but can't get there. Anyway, after connecting another android via wireless adb. I commanded to go to recovery. Finally, I got there. And hard reset it.But I saw it's still encrypted . Any solution? I already lost so many app data because didn't create backup. PLEASE HELP ME DECRYPT IT. SO MY PHONE CAN BE MORE FAST!! AND LET ME USE IT ASAP. I DON'T WANT TO USE IT UNTIL I DECRYPT IT !!!!!!!!
Click to expand...
Click to collapse

Thanks to you all ! I fully understood the situation. [SOLVED]