Database Users

H2-MM TWRP - Failed to decrypt /data partition

I was previously on OOS 2.2.1 and TWRP 3.0.0-2 (phone encrypted) and it was able to decrypt the /data partition just fine.
I decided to update to OOS 3.0 Beta with the modified H2-MM TWRP 3.0.0-1. I did this by dirty flashing. My phone boots up fine and I'm able to unlock the phone and everything seems to be running fine. The problem is now H2-MM TWRP 3.0.0-1 is unable to decrypt my /data partition. It keeps asking for my password, saying it's the wrong password. I know the password is correct because I'm able to get into my phone just fine. Would like to be able to access TWRP to flash su among other things.
Is anyone else having this issue? Anyone have OOS 3.0 Beta with H2-MM TWRP that CAN decrypt?
TWRP 3.0.0-2's decryption was working fine on OOS 2.2.1. I tried using TWRP 3.0.0-2 with OOS 3.0 Beta, but it won't work. Seems H2-MM TWRP 3.0.0-1 is required.
Thanks in advance!

Same problem here, I hope a solution comes soon..

TWRP backup issue - can't backup /data

TWRP backup doesn't give me the option to backup /data and gives an error saying unable to mount /data, mounted without encryption
Running stock b160, on vns-l21, rooted systemlessly with magiskSU, running systemless xposed.

deleted ....... wrong, i saw that you have meticulus twrp, that was my suggestion

i also have this problem and not only can i not do a backup of the /data (it doesn't show up in the first place) but i also cannot flash a different ROM.

Flashed new OnePlus 5 firmware, phone stuck on LineageOS loading screen

So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?

walker_flocker said:
So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?
Click to expand...
Click to collapse
Have you used latest blu spark or codeworkx recovery with vendor partition support? Also mounting the created vendor partition within twrp might be necessary after flashing stock oos and proceed further.

Can't accsess /data in TWRP and Have no root

Something recently broke Twrp so now I cant touch my /data partition, ive read that I need to format my phone to fix this issue, the problem is that a recent update from Lineage OS is what broke it I believe, and I updated from within LOS (check for new updates download and install) which auto restarted, so when I went to go back into TWRP to reflash Magisk I started getting the issue
So now I have no root, and no twrp abilities that I know off, which means I cant use a decent backup program
can anyone help?
EDIT: I don't know if they has any relevance but ADB does have root permissions,
EDIT 2: I found out that I can reinstall magisk VIA ADB Sideload from within TWRP, as such I now have root again

@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.

AnonVendetta said:
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
Click to expand...
Click to collapse
Getting into twrp is no issue, the issue is that TWRP cannot read the internal storage, it can read external fine, but fails to read internal storage, which means i cant flash anything, an reflashing twrp does nothing
im fine with reformatting the phone, but i need to backup my stuff first, which i can not do since no root

@foxtrotdragon: Unfortunately for you, backing up the contents of your internal storage is no longer possible, unless you can think of some ingenius method to decrypt without formatting. Formatting /data is your only option. In the future, you should make backups *BEFORE* disaster strikes.

Encryption on DotOS Pie bootloops, TWRP won't decrypt even with correct password

So, after a few months on Oreo I clean flashed DotOS Pie last night, got the whole thing set up and tried to encrypt phone. It now bootloops, but I can get to TWRP, which shows me a pattern to decrypt data, even though my phone had PIN lock. I did the trick to "translate" between PIN and pattern grid. TWRP shows me "data successfully decrypted, new block device: '/dev/block/dm-0'", but I can't mount /data (consequently can't mount /sdcard), though I can mount /system. TWRP's console shows "Failed to mount /data (Invalid argument)".
I know I can just format /data on the wipe menu to get rid of encryption, but since I don't have a backup of /sdcard, I would like to know if there is any way to get /data mounted again so I can backup my internal storage before formatting /data.
If it makes any difference, my TWRP version is 3.2.1-0, latest one available at twrp.me. I heard that 3.2.1-1 handles encryption better (even better than more recent versions on some devices), but it's not available on the official site.
--Other details that might be relevant, but I'm not sure:
1. I do have TiBu's backup on my computer, so if I must restore my apps I'm fine with it (though I don't have a backup of the whole internal storage);
2. I also have a Nandroid backup of /system, /data and /boot, but it's on the phone storage only;
3. Last, but not least, I have flashed latest Magisk just before encrypting the device.
I saw some stuff related to a no-verity encryption zip file to be flashed via TWRP in some discussions regarding other devices, would it be of any help in my case?

@anupritaisno1 sorry to bother you, but you're the one person to ask for help with TWRP on OP2. Could you lend me a hand here? Would your enhanced TWRP help in my case? I know one shouldn't restore backups made with one version of TWRP within another version, and also that the tempcache stuff needs to be set up to flash ROMs. My plan here, if this could help, was to see if your enhanced TWRP can successfully decrypt my /data and internal storage, then I would back up my internal storage to my computer and either set up tempcache or reflash official 3.2.1-0 to format data and flash the ROM again.
Thanks in advance.