Is it possible combo? I have f2fs and it says "Encrypted" in setting, but for example, twrp doesnt asks pasword and lets me do whatever i want with my filesystem. I heard in OP1 threads that f2fs cant be encrypted after all.
It can, you need to set password in lock screen settings. If you don't do it, TWRP will decrypt your storage using the default password.
Related
Hello friends,
My G3-D855 phone is encrypted, and when i try to wipe data, TWRP asked me for my password, So, I tried to enter it but nothing happens.
it doesn't typing my password, i just can feel the vibrate when im clicking the keyboard.
is anyone know what to do?
A_L_O_N said:
Hello friends,
My G3-D855 phone is encrypted, and when i try to wipe data, TWRP asked me for my password, So, I tried to enter it but nothing happens.
it doesn't typing my password, i just can feel the vibrate when im clicking the keyboard.
is anyone know what to do?
Click to expand...
Click to collapse
Can you mount data storage in TWRP?
I'm asking, because I can't on my device. I wonder if TWRP for G3 even supports encrypted storage?
p.s.
I spotted few users in this forum asked the same question, so definitely decrypting is not supported.
mister_no said:
Can you mount data storage in TWRP?
I'm asking, because I can't on my device. I wonder if TWRP for G3 even supports encrypted storage?
p.s.
I spotted few users in this forum asked the same question, so definitely decrypting is not supported.
Click to expand...
Click to collapse
I dont know yet, I think that it asks for unlock encryption password to mount data...
There is no option to decrypting encrypted device, thats why i need to wipe my phone :\
A_L_O_N said:
I dont know yet, I think that it asks for unlock encryption password to mount data...
There is no option to decrypting encrypted device, thats why i need to wipe my phone :\
Click to expand...
Click to collapse
If you want to wipe the phone, you could also reflash the firmware (kdz file). Check this thread or this one.
Guys, every rooting guide for the Samsung A 2017 states we need to format /data to remove encryption. I understand this is mostly due to TWRP not being able to decrypt it. However, if we don't care about an inaccessible /data in TWRP, can we leave /data encrypted (or reencrypt it later, after rooting)?
My idea is to have full rooting with Magisk + Xposed, while keeping my /data secure with encryption. Appreciate answers, even if alternative approaches to this security matter.
Actually, this is the current situation. At least here with Oreo after having done the root the /data remained encrypted. But in fact, you can not install any .zip for twrp because the /data is encrypted.
Hmm that's interesting. Have you formatted /data prior to flashing a rooted ROM / Magisk? In that case, how did you reencrypt it? I'm asking because from what I could find about other Galaxy models, people couldn't reencrypt their devices after rooting (the corresponding option in Settings just force closes). But it seems to vary among phone models and firmware versions.
Regarding the inability to flash ZIPs from TWRP with /data encrypted, have you tried using FlashFire for that?
Hi,
it would be nice if LOS allowed you to set a "format password" that would erase data partition and could even replace it with a prefilled partition.
I would like to implement it, but I have 0 experience with android dev :/
Thanks
Hey guys,
i wanted to flash something, so i rebooted into recovery and i was asked for a password. I skipped this and made a normal reboot, but I have to enter a password. I've set a lockscreen password a few days ago only for a few hours, after that i disabled it and since then i have no pin, fingerprint or something else. Some people say that we can delete in twrp filemanager *.key files, but if I go to /data, it shows nothing (on /system I see all folders and files). My phone is also not recognized by PC (https://forum.xda-developers.com/redmi-note-3/help/solution-fix-unlock-phone-restore-twrp-t3508173).
Any suggestions? Just made a reboot and now i can't access my files. I know that format data will solve that, but I really want to avoid that.
Edit: Storage was corrupted, so i had to full wipe...
A question about decrypting your device, in this case Luisrom Android 10, but would most probably count for other roms too.
Did not try it already but would like to decrypt my device and would like a confirmation if the following is the right procedure without doing a new install:
Boot in recovery
Make a backup of /data to internal storage with TWRP
Make a backup of internal storage to my pc
Format data in TWRP
Copy internal storage back from pc to OP3(T)
Restore backup from /data with TWRP
Reboot with decrypted phone
I could do a dirty flash afterwards ofcourse, but because /system is not touched I think the steps above should be enough.
Could someone confirm if this is right?
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Johan2020 said:
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Click to expand...
Click to collapse
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
nvertigo67 said:
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
Click to expand...
Click to collapse
I am using CrDroid 6.4 Luisrom which is not enforcing encryption, just as most other custom roms.
I had enabled encryption though after installation to see if encryption was working already for installing CrD Luis on my work phone (where I want encryption).
After that I decided to go back to unencrypted, following the procedure above, which did not work.
Did not make the link between fbe and file based encryption, but ofcourse this is the same and not available on op3/t.
Must have been sleeping when I wrote that.
Based on what you wrote and my missing knowledge;
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Johan2020 said:
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Click to expand...
Click to collapse
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
nvertigo67 said:
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
Click to expand...
Click to collapse
Good point, did not try that unfortunately and just did a fresh install so.... not really eager to try it now
But I think indeed reencryption was triggered because of also restoring the encryption settings.
Will try it when I have some spare time and want to take the risc of a fresh install again