Related
Hi Guys,
I'm pretty sure most of you have ran into the problem when you have flashed a rom with TWRP and you have set it up etc.. and you boot into
recovery it will ask you to decry your data with a password and if you look on the internet on how to fix this, they will tell you that you have
FORMAT DATA.
Well if you have set up a screen lock pattern when you set your phone up, you're in luck!
The trick is to convert your lock pattern into numbers.
For example if you have 3x3 then it should be something like this:
1 2 3
4 5 6
7 8 9
If you see the image attached, starting with green dot is the start of my screen lock pattern and end on red. If you see the numbers it converts to 7598 which is the same code you use to decrypt TWRP and you can access your data!
I hope I was clear enough, this is my first time making a guide but i have seen many people suffer from the issue and having to wipe data including myself!
Please leave a thanks if this worked for you!
Sometimes this happens while downgrading Android to a lower version, because the lower version doesn't recognize the pattern and TWRP can't decrypt it
The solutions can be to reflash the latest version so that it can decrypt data successfully
what if my password has x2 a digit, for ex. 3387?
about twrp password
I try same pattern like on my phone and working so just do it
Pin password user here
Format data then problem solved.
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?
Alright, so i have an OP5T and it is encrypted. I decided to disable one magisk module, op5t gcam dot issue patch, i think thats is what it was called, and then then i couldnt unlock the phone. It was running LOS for microg android 9, and the encryption from oxygenos to los passed no problem (just enter the same lock screen pattern) (also why i think this doesnt belong in some op5t forums because it shouldnt be op5t specific, judging by how i was able to use los with an encrypted phone no problem). Now i deleted something like /data/system/gatekeeper.{password,pattern}.key, and /data/system/lockssettings.db (moved it to a different folder). That kind of worked, but then my phone was stuck on 'starting phone'. Even when getting the files back, it was still stuck. Trying to decerypt it via twrp gave like a 2 second try when using the wrong pattern, and a 5-7 second try when using the correct pattern, although still failed.
When looking at the twrp logs trying to backup /data:
failed to lookup tar policy for '/data/misc_ce/0' - 'cba6a56b3cad5706'
I:Error adding file '/data/misc_ce/0' to '/usbstorage/TWRP/BACKUPS/ab5cbcf1/2020-09-06--05-12-48_lineage_dumpling-userdebug_9_PQ3A190801002/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbstorage/TWRP/BACKUPS/ab5cbcf1/2020-09-06--05-12-48_lineage_dumpling-userdebug_9_PQ3A190801002/data.info'
createTarFork() process ended with ERROR: 255
I also removed magisk via a zip, and reinstalled LOS for microg to no avail.
So, im now copying the internal storage stuff over mtp to my pc, and hoping there would be a way to decrypt them. I have the gatekeeper and lockscreensettings files and i know my pattern, so is there any way i could decrypt them on my pc?
Also, could it be done by wiping /data, booting up android and then setting up a lock screen pattern, enabling encryption, or just copying the files to /data/system/...?
Im typing this really rushed, sorry for any misunderstanding you may encounter.
Alright so another update, gatekeeper.password.key is empty, while gatekeeper.pattern contains some characters. I did use a pattern based lockscreen only, this normal for gatekeeper.password.key to be empty, right?
Ive reflashed the whole thing, now the only thing that could help me would be if i could somehow decrypt the files i have downloaded. I know my pattern and have the gatekeeper.pattern.key file, if that can help?
constatinus said:
Ive reflashed the whole thing, now the only thing that could help me would be if i could somehow decrypt the files i have downloaded. I know my pattern and have the gatekeeper.pattern.key file, if that can help?
Click to expand...
Click to collapse
if you didn't unencrypt the files before resetting the device. the files are now useless. no recovery options unless you know someone who works for the NSA (sarcasm) but true.
I know the feeling. i lost recovery keys for online storage for porn....all lost, but not forgotten.
Nope, you cant.
Sent from my BASIC using Tapatalk
Default setup set a password for lock screen, phone says it is encrypted under settings but i doubt that.
It did not reboot for the encryption progress which might be fine given that it comes with pre generated keys.
However the phone boots immediately to sim pin enter and after unlock everyting is directly accessible. It boots way to fast to be encrypted IMHO.
I also had a simmilar bug with paranoid os (also android 10) where it said its encrypted but it was not, twrp did not ask for a password everything was accessible and it was the same boot process.
Usually with android encryption i first have to enter the password for decryption, phone continues with boot animation and then have to enter sim pin.
So i wonder is this a bug with android 10 or is it really encrypted.
Yes, Android will force encrypt by default. Your phone is actually encrypted using "default_password", and in MIUI, decryption keys are not changeable by setting another lock PIN/Password, like it normally would in any other Android versions. If you manage to tamper with the keys using third party tools, you will be locked out of your system. Typing password during boot will return an "incorrect password" message, even if you typed it corrrectly.
Xiaomi considers bootloader LOCKED devices to be safe enough, hence why they don't really care much about encrypting. If your phone's bootloader is unlocked, you might be worrying about your data/internal storage being easily decryptable by thieves or unwanted people (for example), and I understand that. There is not much you can do about changing the default decryption password, you might just wait for a custom ROM that supports encryption properly, like Pixel Experience.
It use FBE, not FDE, search about it
Okay thats interesting to know, so basically the encryption is worthless as anyone with physical access can just desolder the flash chip and read the whole content.
I quite like miui but thats a major reason for me to switch to a custom rom.
Worthless encryption then. This is plain obfuscation and no security concept.
Which custom ROM can I use for my Poco x3 with FDE?
POCO X3 NFC stuck at boot logo (has locked bootloader)
Question: if I do a recovery - "Wipe Data" - which will do a factory reset
After that, will I be able to use an undelete program to recover the files?
If default encryption is being used - but encryption password is always the same - won't the old data be recoverable using an undelete type program?
The intent here is for me to get the phone working again - but to salvage the data from the phone internal storage as much as I can (even if is just the files that were at top level and not app-specific folders etc.).
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