Database Info

failed to mount /data

SOLVED
I rooted my s7 and installed twrp. I tried to do a nandroid backup in twrp and got the message that it couldn't mount /data. It turns out that by not performing the data format step in http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 TWRP couldn't access /data. I did the steps over again and all was well.

kettir said:
I've rooted my s7 and installed twrp. I tried to do a nandroid backup in twrp and got the message that it couldn't mount /data.
I do have root, twrp does run when I boot into recovery. However, whether I select to allow modifications to system or not, twrp does not see the internal sd card.
I followed these instructions to root: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
However, I did not do step 10:
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
Is this the reason that I can't access internal storage? If it is, I can go ahead and do the format data thing. I just would like to know if that is probably the reason I'm having this problem. NOTE: The phone is not encrypted so far as I know.
Click to expand...
Click to collapse
Internal data is encrypted nevertheless. Only a format will remove this encryption and it is the only way that you can make a TWRP backup of this data.

Bright.Light said:
Internal data is encrypted nevertheless. Only a format will remove this encryption and it is the only way that you can make a TWRP backup of this data.
Click to expand...
Click to collapse
Frag. Well, in that case, I've already installed TWRP, so presumably I can just boot to TWRP, swipe right to enable changes, format data, flash supersu, and then flash dm-verity and force encryption disabler. Then go through the setup again.
If I could have my way, someone would disable the security deal with writing to the SD card, the phone could be purchased pre-rooted, and I wouldn't have to worry about bricking my phone every time I flash something.
Rant over.

@kettir: You're exactly right!
btw: The security deal is not over when you root your phone. 'I still haven't found what I'm looking for' is a very precise song for this problem.

I had the same issues and succesfully used the sequence proposed by Kettir:
- Enable OEM unlock
- ODIN: Install TWRP
- TWRP: Wipe -> Format data
- TWRP: flash supersu
- TWRP: flash dm-verity and force encryption disabler

Disable encryption protection?

Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris

scientificharmony said:
Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris
Click to expand...
Click to collapse
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom

MAX 404 said:
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom
Click to expand...
Click to collapse
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.

scientificharmony said:
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.
Click to expand...
Click to collapse
Hi
TWRP can not handle Samsung encryption . if you wish to use TWRP and have access to the Data partition ( internal SD card) you need to format it so the encryption is disabled ( you lose all your apps , data and user configuration AKA factory reset) , you can have TWRP and data encryption but mods and roms have to be flashed from external memories also you will not have available MTP in recovery or factory reset from it.
There is no way to disable data encryption without format data.....

Ok, I got a friends SD card and placed the Rom on there. I can now see the Rom but the trouble is, TWRP wont let me wipe Dalvik / data / system / cache as it wont mount the storage....
can I still apply the ROM?

Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.

scientificharmony said:
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.
Click to expand...
Click to collapse
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........

MAX 404 said:
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........
Click to expand...
Click to collapse
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.

scientificharmony said:
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.
Click to expand...
Click to collapse
How did you flash the stock rom...which files did you use?
Wipe data is not enough you have to Wipe / FORMAT DATA and type yes....

1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app

Josh Smith10 said:
1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app
Click to expand...
Click to collapse
What version of TWRP are you guys using and what version Super SU?

Delete

How do you backup with TWRP given the issues caused by dm-verity?

I have a J710DM/DS. I flashed the latest version of TWRP (TWRP for j7xelte - 3.0.2.1) with no problems.
But when I try to do a backup (to the external SD card), I get the expected "failed to mount /data" errors that result from dm-verity.
TWRP's website talks about this and mentions that some versions have a "System Image" option, but I don't see it on my phone.
So how do I properly do a backup?

This is nothing to do with dm-verity, it's encryption.
Format DATA to remove encryption and then install the boot patch.
My builds of TWRP have image backup, but not sure if I've compiled a j710 version.

ashyx said:
This is nothing to do with dm-verity, it's encryption.
Format DATA to remove encryption and then install the boot patch.
My builds of TWRP have image backup, but not sure if I've compiled a j710 version.
Click to expand...
Click to collapse
Thanks for the information.
What boot patch?
Edit:
Also, what's the recommended way to format DATA? If TWRP can't even mount it, can it even format it?

Haphim said:
Thanks for the information.
What boot patch?
Edit:
Also, what's the recommended way to format DATA? If TWRP can't even mount it, can it even format it?
Click to expand...
Click to collapse
FORMAT *not* WIPE. You don't need to mount to FORMAT.
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx

ashyx said:
FORMAT *not* WIPE. You don't need to mount to FORMAT.
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Click to expand...
Click to collapse
Thank you so much for elaborating!
Quick follow-up: I have already flashed SuperSU previously. Will I need to flash it again after formatting DATA?

Haphim said:
Thank you so much for elaborating!
Quick follow-up: I have already flashed SuperSU previously. Will I need to flash it again after formatting DATA?
Click to expand...
Click to collapse
You will need to reflash supersu.

Quick, but vital question:
Does flashing "no-verity-no-encrypt_ashyx" mean that I can now safely restore a full system backup?

Haphim said:
Quick, but vital question:
Does flashing "no-verity-no-encrypt_ashyx" mean that I can now safely restore a full system backup?
Click to expand...
Click to collapse
If you made a backup of an unencrypted data partition then you can restore if /data is mountable.
If you are not restoring /data then it doesn't matter.

Thank you so much for helping me understand all of this. You're the best!

twrp

Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption

Newrooter22 said:
Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption
Click to expand...
Click to collapse
It only wipes /data.
Though, if you use TWRP by Pretoriano80 there's no point as that has decryption.
If you still want to continue you need to Format Data, 'reboot recovery', then remove fileencryption flag in /vendor/etc/fstab.hi3660. (you can pull this file using adb, edit on computer then push it back using adb.).
If you don't edit fstab your phone will re-encrypt on next boot to system.
You will also have to flash Public and HW zip for your firmware as these will be gone (system update ability and themes are stuff that will be gone if you don't flash these.)

How to decrypt /sdcard from ADB?

Long story short, I screwed up, and now I have an encrypted storage (with my files that I want back) but TWRP and the OS thinks it is not.
It goes like this:
The Magisk v22.0 update screwed up my phone, which stuck in a bootloop.
After countless tries with Magisk (updating, uninstalling. installing, removing mods, adding mods) in TWRP, I read somewhere to dirty flash the ROM.
Due to an HDD failure in my PC, I did not have any storage to back up my internal storage from the phone.
Because I wanted to update the ROM anyways (from MIUI 11 to 12) I decided to flash the newer one. That was the first mistake.
This made the bootloop worse, and now it stuck in fastboot mode, no recovery. After many sleepless nights I found out that not every USB-C cable is equal, and I couldn't reach my phone via fastboot because of the cable itself. Tried it with the original cable, it sure showed up as a fastboot device.
So now I was able to flash an original fastboot ROM which still gave me bootloop, so I went wiping (not formatting, so the /sdcard fs doesn't gets erased) Data and Cache in TWRP.
Then reflashed the fastboot ROM, and somehow it worked. When It booted up, I had to type in my screen lock pin again, and after setup all my files were available.
Now that the phone worked again, I wanted to finish what I started, to update to latest EU (recovery) ROM. This was the second mistake. It did not work (because it required formatting data, which I did not wanted to, and just wiped it), and came bootloop again.
So I went back to the fastboot ROM again, which fixed the phone again.
But this time, it thought the internal storage was not encrypted, so it encrypted it again.
Now I can't access the internal storage. Even the camera app says that first I need an SD Card to take photos.
Its clearly still encrypted because when I browse it in TWRP, the structure and files are there, but the names are like "74t7Z1,dnvgIIexr1QAfhD".
The problem being neither the OS, nor TWRP knows the storage is encrypted double, so it doesn't even tries to decrypt it, and there are no options to do it.
Tried to set encryption in the running OS, but it gave me the same results: even tho TWRP asks for decryption key, and says it successfully decrypted, the storage is still a mess like its in encrypted state.
Is there any way to manually force some flag, so I can access my files again? I have the encryption key, I just need some way to decrypt the storage. I think of something like an ADB command to flag the partition as encrypted, so TWRP and OS would try to decrypt it.
Thanks in advance!

insetta said:
Long story short, I screwed up, and now I have an encrypted storage (with my files that I want back) but TWRP and the OS thinks it is not.
It goes like this:
The Magisk v22.0 update screwed up my phone, which stuck in a bootloop.
After countless tries with Magisk (updating, uninstalling. installing, removing mods, adding mods) in TWRP, I read somewhere to dirty flash the ROM.
Due to an HDD failure in my PC, I did not have any storage to back up my internal storage from the phone.
Because I wanted to update the ROM anyways (from MIUI 11 to 12) I decided to flash the newer one. That was the first mistake. This made the bootloop worse, and now it stuck in fastboot mode, no recovery. After many sleepless nights I found out that not every USB-C cable is equal, and I couldn't reach my phone via fastboot because of the cable itself.
Due to an HDD failure in my PC, I did not have any storage to back up my internal storage from the phone.
So now I was able to flash an original fastboot ROM which still gave me bootloop, but after wiping (not formatting, so the /sdcard fs doesn't gets erased) Data and Cache in TWRP.
Then reflashed the fastboot ROM, and somehow it worked. When It booted up, I had to type in my screenlock pin again, and after setup all my files were available.
Now that the phone worked again, I wanted to finish what I started, to update to latest EU (recovery) ROM. This was the second mistake. It did not work (because it required formatting data, which I did not wanted to, and just wiped it), and came bootloop again.
So I went back to the fastboot ROM again, which fixed the phone again.
But this time, it thinks the internal storage is not encrypted.
Now I can't access the internal storage. Even the camera app says that first I need an SD Card to take photos.
Its clearly still encrypted because when I browse it in TWRP, the structure and files are there, but the names are like "74t7Z1,dnvgIIexr1QAfhD".
The problem being neither the OS, nor TWRP knows the storage is encrypted, so it doesn't even tries to decrypt it, and there are no options to do it.
Tried to set encryption in the running OS, but it gave me the same results: even tho TWRP asks for decryption key, and says it successfully decrypted, the storage is still a mess like its in encrypted state.
Is there any way to manually force some flag, so I can access my files again? I have the encryption key, I just need some way to decrypt the storage. I think of something like an ADB command to flag the partition as encrypted, so TWRP and OS would try to decrypt it.
Thanks in advance!
Click to expand...
Click to collapse
Is twrp permanently installed

Austinredstoner said:
Is twrp permanently installed
Click to expand...
Click to collapse
No, its not.
Also, seems like the option to decrypt is not there because its being encrypted double. One with my original pin, and now with "default_password" since the encryption is forced in this ROM.
Trying to create any backup in TWRP now gives the "required key not available" error.

insetta said:
No, its not.
Also, seems like the option to decrypt is not there because its being encrypted double. One with my original pin, and now with "default_password" since the encryption is forced in this ROM.
Trying to create any backup in TWRP now gives the "required key not available" error.
Click to expand...
Click to collapse
Decryption only works when twrp permanently installed

Austinredstoner said:
Decryption only works when twrp permanently installed
Click to expand...
Click to collapse
Okay, I flashed TWRP.
Now I found that from shell, TWRP has a "decrypt" function, which I called, but no success
tucana:/ # twrp
TWRP openrecoveryscript command line tool, TWRP version 3.5.2_9-0
Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
install /path/to/update.zip
backup <SDCRBAEM> [backupname]
restore <SDCRBAEM> [backupname]
wipe <partition name>
format data
sideload
set <variable> [value]
decrypt <password> [USER ID]
remountrw
fixperms
mount <path>
unmount <path>
print <value>
mkdir <directory>
reboot [recovery|poweroff|bootloader|download|edl]
tucana:/ # twrp decrypt **********
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.

insetta said:
Okay, I flashed TWRP.
Now I found that from shell, TWRP has a "decrypt" function, which I called, but no success
tucana:/ # twrp
TWRP openrecoveryscript command line tool, TWRP version 3.5.2_9-0
Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
install /path/to/update.zip
backup <SDCRBAEM> [backupname]
restore <SDCRBAEM> [backupname]
wipe <partition name>
format data
sideload
set <variable> [value]
decrypt <password> [USER ID]
remountrw
fixperms
mount <path>
unmount <path>
print <value>
mkdir <directory>
reboot [recovery|poweroff|bootloader|download|edl]
tucana:/ # twrp decrypt **********
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Click to expand...
Click to collapse
Can u partition sd card if not can u install recovery ramdisk

Austinredstoner said:
Can u partition sd card if not can u install recovery ramdisk
Click to expand...
Click to collapse
What would be the purpose of partitioning the fs? Not to mention it would like cause data loss

insetta said:
What would be the purpose of partitioning the fs? Not to mention it would like cause data loss
Click to expand...
Click to collapse
That maybe true I can't think of anything else the only thing I can still think of is dm verify or vbmeta

Austinredstoner said:
That maybe true I can't think of anything else the only thing I can still think of is dm verify or vbmeta
Click to expand...
Click to collapse
"dm verify or vbmeta"
Sound familiar, please elaborate

insetta said:
"dm verify or vbmeta"
Sound familiar, please elaborate
Click to expand...
Click to collapse
How to enable and disable dm verity on android user build
How to enable and disable dm verity on android user build. adb root, adb disable-verity, adb enable-verity. remount failed: permission denied
5gnotes.com

Austinredstoner said:
How to enable and disable dm verity on android user build
How to enable and disable dm verity on android user build. adb root, adb disable-verity, adb enable-verity. remount failed: permission denied
5gnotes.com
Click to expand...
Click to collapse
Encryption / decryption of /sdcard partition relies on PIN/password set and stored in file /data/system/locksetting.db.
Neither AVB 1.0 ( AKA DM-Verity ) nor AVB 2.0 (read: Android Verified Boot - available only on project Treble devices) have anything to do with encryption / decryption of Android partitions: their purpose is the verification of the Android OS through the bootloader when phone gets started.

insetta said:
tucana:/ # twrp decrypt **********
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Click to expand...
Click to collapse
Look into Android's file /cache/recovery/log to get the reason why TWRP's decrypt fails.
Why not pull content of /sdcard to PC ( e.g. TAR-archived ) and then do a factory reset to get rid of the encryption?

jwoegerbauer said:
Look into Android's file /cache/recovery/log to get the reason why TWRP's decrypt fails.
Why not pull content of /sdcard to PC ( e.g. TAR-archived ) and then do a factory reset to get rid of the encryption?
Click to expand...
Click to collapse
Because pulling encrypted /storage is pointless. First I need to be able to decrypt them.

Because pulling encrypted /storage is pointless. First I need to be able to decrypt them.
Looked into the TWRP log, and seems like it uses the native android Keymaster HAL 4 to decrypt the storage, but it ran into some issues:
This is on TWRP boot:
Bash:
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = true
Wrapped key supported on /data
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = true
Wrapped key supported on /data
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
And this is after I wanted to decrypt it:
Bash:
I:Command 'decrypt *************' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition or user data via command line.
E:Unexpected value for crypto key location
E:Error getting crypt footer and key
E:Could not get footer
Failed to decrypt data.
I:Done reading ORS command from command line
I:operation_end - status=0

I also would like to decrypt my phone. I have access to adb shell, fastboot and twrp. Is there any news on how to do it?