hi,
i have recently encrypted my moto g5 and i use TWRP recovery, which now asks me for a password. it doesnt seem to be my pin code and also when i cancel, i cant get to the data directory within TWRP.
is there a default password?
ehmdjii said:
hi,
i have recently encrypted my moto g5 and i use TWRP recovery, which now asks me for a password. it doesnt seem to be my pin code and also when i cancel, i cant get to the data directory within TWRP.
is there a default password?
Click to expand...
Click to collapse
1.Boot into recovery
2.advanced
3.file manager
4.data
5.system
6. Delete the following files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
7.reboot to system.
TheArtistSpud said:
1.Boot into recovery
2.advanced
3.file manager
4.data
5.system
6. Delete the following files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
7.reboot to system.
Click to expand...
Click to collapse
thanks, but the problem is that i dont even see the contents of data in recovery since TWRP asks me for a password when it starts. this password doesnt seem to be something i picked nor the pin or pattern code.
ehmdjii said:
thanks, but the problem is that i dont even see the contents of data in recovery since TWRP asks me for a password when it starts. this password doesnt seem to be something i picked nor the pin or pattern code.
Click to expand...
Click to collapse
https://www.reddit.com/r/Nexus5/comments/2mskzu/twrp_is_asking_for_a_password
This could help you.
TheArtistSpud said:
https://www.reddit.com/r/Nexus5/comments/2mskzu/twrp_is_asking_for_a_password
This could help you.
Click to expand...
Click to collapse
thanks again, tried all those tips with various combinations of my pin, but none worked.
it really seems, that the official motog5 rom uses some modified version as the password for disk encryption.
ehmdjii said:
hi,
i have recently encrypted my moto g5 and i use TWRP recovery, which now asks me for a password. it doesnt seem to be my pin code and also when i cancel, i cant get to the data directory within TWRP.
is there a default password?
Click to expand...
Click to collapse
TWRP decryption for G5 is broken, and it's a pretty known issue. If you are rooted you can use a workaround:
1) Completely disable the lockscreen from settings.
2) Use flashfire (it's in the play store) to create a data backup on an memory stick connected through OTG. Don't use internal memory, because you will not see the backup in TWRP. The new backup in the memory stick will be decrypted.
3) Boot into TWRP, format data partition and restore the backup flashing the auto generated zip located in the Flashfire folder from the memory stick.
After that your restored data will be temporally
decrypted.
4) Do whatever you want to do in TWRP before reboot.
5) Disconnect your OTG and your external memory stick before to reboot onto system. Your device will not boot correctly if you don't do that.
After rebooting the data will be encrypted again automatically.
WARNING: Remember If you boot onto system it will encrypt data again automatically it can't be avoided. The first boot-up after this procedure will take some time because of the re-encryption process. Be patient and don't freak out, the device will stay 5-10 mins on the boot logo without a progress bar. Don't interrupt it, or your data will get corrupted and you will need to restore the backup and start over again.
WARNING 2: Your password will not work after restoring the backup. If you skipped the step 1) delete the .key And locksettings.db files in data/system before restarting onto system.
I strongly recommend disabling the password/pin/pattern before booting onto TWRP. It will prevent that your password gets corrupted (it happens easily).
By example if you format data from recovery without doing that, your password will not work anymore. If it happens, the only way back is format your data and restore your Flashfire backup if you have one.
Enviado desde mi Moto G (5) mediante Tapatalk
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
fex42 said:
Hi,
I try to install LineageOS 14.1 + Magisk 15.0 without encryption on Data, but it always is encrypted after installation again.
Here are the steps I take:
1. Install TWRP 3.2.1-0
2. Boot into TWRP recovery (getting prompted to enter pattern so it can decrypt data)
3. Format Data (forced to type "yes" , so did not only wipe it)
4. Reboot into recovery to proove that I am unencrypted now (not prompted again for the pattern again)
5. Install LineageOS 14.1
6. Install Magisk 15.0
7. Install Google Apps
8. Reboot into system, installing LineageOS, some apps, etc.
The next time I boot into recovery, I get prompted for the pattern so I guess my Data partition is encrypted again.
I tried several variants of install packages, also the "no-enforce-encrypt-no-verify" package (after installing LineageOS), but got no luck so far.
Please could someone tell me what I am doing wrong and what to do to avoid encryption of data again?
Thank you!
fex42
Click to expand...
Click to collapse
Use this recovery:
Pendragon2000 said:
Use this recovery:
Click to expand...
Click to collapse
Thank you, but it seems not to be caused by my TWRP version (3.2.1-0). In the meantime I installed LineageOS 15.1 but did format data again just before rebooting and now data stays unencrypted (does not ask me for unlock pattern in TWRP). Even after installing Magisk v15.0 later, is stays unencrypted . But in MagiskManager there's the checkbox set "keep force encryption" - dont know if that does matter? On my Redmi Note 4 this checkbox is not set.
Same problem here with my Redmi K20 Pro. The problem occurred after I reboot my phone to uninstall FDE.AI magisk module. My phone then encrypts itself. Factory reset, format data, repair partition, re-flashing stock ROM doesn't solve the problem. Have you solved it yet?
Hi,
I'm using a Poco F3 with latest stable Xiaomi.eu 12.5.3.0. With older phones, I could avoid having a pattern/password while still using the finger print sensor by deleting the file at "data/system/locksettings.db". Since it is something I have done many times with other Android phones, I didn't expect it could be a problem, but after deleting the file, the data folder is encrypted and I have no way to decrypt it.
After deleting the file and booting into MIUI as usual, all my apps says "wait until your device is fully rebooted before opening apps". I can open system apps like the clock or the weather, but that's it.
Things I've tried:
Factory reset from the device settings. After pressing the button, the screen gets black and after 2 seconds it gets back on the settings menu.
Change the security settings. Both changing the pattern, the password or leaving it without security. It only affects how the device is locked, but nothing else.
Using adb, I have no permission to see the data folder and the sdcard folder says it does not exists.
From TWRP, if I had set any kind of lock while in Android, it will ask for it (such a pattern or password). But whatever I input, it always says "Failed to decrypt user 0". I can cancel the input and enter normal TWRP but with the data folder encrypted.
I've tried to Wipe>Format Data, with the following error message:
Code:
/system/bin/make_f2fs -d1 -f -0 encrypt -0 quota -0 verity -w 4096 /dev/block/sda35 27865079 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Filed to mount '/data' (Device or resource busy)
In Wipe>Advanced Wipe>Repair or Change File System (to the Data partition). If I try to repair it gives me error 255 again. If I try to Change File System to F2FS, again "Error chaning file system".
I cannot flash Xiaomi.eu again from TWRP because I cannot move the file to the phone through adb "permission denied".
What other options do I have?
Thanks in advance for the help.
flashing stock miui theres a fastboot flash userdata that might do the trick.
guillermo1996 said:
Hi,
I'm using a Poco F3 with latest stable Xiaomi.eu 12.5.3.0. With older phones, I could avoid having a pattern/password while still using the finger print sensor by deleting the file at "data/system/locksettings.db". Since it is something I have done many times with other Android phones, I didn't expect it could be a problem, but after deleting the file, the data folder is encrypted and I have no way to decrypt it.
After deleting the file and booting into MIUI as usual, all my apps says "wait until your device is fully rebooted before opening apps". I can open system apps like the clock or the weather, but that's it.
Things I've tried:
Factory reset from the device settings. After pressing the button, the screen gets black and after 2 seconds it gets back on the settings menu.
Change the security settings. Both changing the pattern, the password or leaving it without security. It only affects how the device is locked, but nothing else.
Using adb, I have no permission to see the data folder and the sdcard folder says it does not exists.
From TWRP, if I had set any kind of lock while in Android, it will ask for it (such a pattern or password). But whatever I input, it always says "Failed to decrypt user 0". I can cancel the input and enter normal TWRP but with the data folder encrypted.
I've tried to Wipe>Format Data, with the following error message:
Code:
/system/bin/make_f2fs -d1 -f -0 encrypt -0 quota -0 verity -w 4096 /dev/block/sda35 27865079 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Filed to mount '/data' (Device or resource busy)
In Wipe>Advanced Wipe>Repair or Change File System (to the Data partition). If I try to repair it gives me error 255 again. If I try to Change File System to F2FS, again "Error chaning file system".
I cannot flash Xiaomi.eu again from TWRP because I cannot move the file to the phone through adb "permission denied".
What other options do I have?
Thanks in advance for the help.
Click to expand...
Click to collapse
U can try to flash a stock ROM using MiFlash tool and flash xiaomi.eu ROM again.
Also you can use a USB OTG to flash from twrp
Alin45 said:
U can try to flash a stock ROM using MiFlash tool and flash xiaomi.eu ROM again.
Click to expand...
Click to collapse
I thought I couldn't downgrade to stock rom because of Anti Rollback restrictions, but it did work and solved the problem. Thanks for the help!
arifqur said:
Also you can use a USB OTG to flash from twrp
Click to expand...
Click to collapse
Didn't think of that, unfortunately flashing from TWRP does not format the data partition, so it didn't solve the problem.
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.