Unable to mount \data (internal storage) - Samsung Galaxy J7 (2017) Questions & Answers

Hi,
I recently encountered a bug in TWRP where \data wouldn't mount. When I finally fixed the \data mount and installed a custom rom (Oreo 8.0), the next time I booted into TWRP recovery my internal storage would show up as 0mb not being able to install any .zip files.
how can i fix it?

faturazis said:
Hi,
I recently encountered a bug in TWRP where \data wouldn't mount. When I finally fixed the \data mount and installed a custom rom (Oreo 8.0), the next time I booted into TWRP recovery my internal storage would show up as 0mb not being able to install any .zip files.
how can i fix it?
Click to expand...
Click to collapse
It's not a bug.
It's a product of Samsung encryption.
This needs to be disabled to retain an unencrypted device.
Plenty of info out there how to accomplish this.

Related

S8 TWRP Error

Hi all,
Yesterday I managed to root my phone all fine with TWRP and SuperSU. Then after incorrectly uninstalling the security log agent and getting a million errors I foolishly deleted the stock OS.
I have download the correct version for my phone and location but now TWRP fails to launch.
I get the follows errors when booting to the recovery.
Failed to mount /data (invalid argument)
Unable to recreate /data/media folder
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I have googled a millions things and am still stuck.
Interestingly tho, If i install the Indian version of the OS, it loads and roots no problems (I'm from New Zealand).
Any help greatly appreciated.
VacantLot said:
Hi all,
Yesterday I managed to root my phone all fine with TWRP and SuperSU. Then after incorrectly uninstalling the security log agent and getting a million errors I foolishly deleted the stock OS.
I have download the correct version for my phone and location but now TWRP fails to launch.
I get the follows errors when booting to the recovery.
Failed to mount /data (invalid argument)
Unable to recreate /data/media folder
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I have googled a millions things and am still stuck.
Interestingly tho, If i install the Indian version of the OS, it loads and roots no problems (I'm from New Zealand).
Any help greatly appreciated.
Click to expand...
Click to collapse
Hi
Your internal memory now corrupt you have to format it.
Use twrp wipe option select internal memory then format to fat32 after that again do same thing. This time choose its original format type.
drparvez said:
Hi
Your internal memory now corrupt you have to format it.
Use twrp wipe option select internal memory then format to fat32 after that again do same thing. This time choose its original format type.
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
Iv'e tried this option, I installed the Indian OS which works with TWRP, formatted the Data drive to FAT (Fat32 isn't an option) and then back to EXT4. I then used Odin to Install the carrier firmware I want to run and the same errors occurred. Could it be a problem with the actual OS?
Edit** When I install the Carrier firmware I can't get TWRP to open, these errors occur as soon as it opens, and then it crashes and reboots
VacantLot said:
Hi, thanks for the fast reply.
Iv'e tried this option, I installed the Indian OS which works with TWRP, formatted the Data drive to FAT (Fat32 isn't an option) and then back to EXT4. I then used Odin to Install the carrier firmware I want to run and the same errors occurred. Could it be a problem with the actual OS?
Edit** When I install the Carrier firmware I can't get TWRP to open, these errors occur as soon as it opens, and then it crashes and reboots
Click to expand...
Click to collapse
Try reflashing twrp
Acoustichayes said:
Try reflashing twrp
Click to expand...
Click to collapse
Hi hi, tried that several times. Would still like to find out what is causing the issue but have now installed Nemisis and all is working perfrctly which makes me think it's the OS as opposed to my file system, considering I have installed multiple other versions and ran TWRP no problems.
Got same problem here. Installed TWRP to flash a custom rom, TWRP can't mount /data.
Google doesn't give me any solutions
This fixed it for me:
- download stock firmware from sammobile & flash with Odin
- go into stock recovery
- wipe data and cache partitions
- flash twrp using odin
After that, TWRP was able to mount /data and function normally again

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.

Help in rooting G935W8 Oreo 8.0.0

Hello;
I wanted to root my G935W8 Oreo 8.0.0, i already flashed TWRP 3.2.3 with ODIN v3.13.1.
The problem is when i'm on recovery mode and i use TWRP in order to install zip it shows me that internal storage is 0 MB
And when i choose Micro SD card to install Magisk-v19.zip and i confirm flash, it shows me in red:
could not mount /data and unable to find cryptofooter.
failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
unable to mount /data/media/twrp/.twrp.
Can anyone help me to root it.
Thanks.
gueabd said:
Hello;
I wanted to root my G935W8 Oreo 8.0.0, i already flashed TWRP 3.2.3 with ODIN v3.13.1.
The problem is when i'm on recovery mode and i use TWRP in order to install zip it shows me that internal storage is 0 MB
And when i choose Micro SD card to install Magisk-v19.zip and i confirm flash, it shows me in red:
could not mount /data and unable to find cryptofooter.
failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
unable to mount /data/media/twrp/.twrp.
Can anyone help me to root it.
Thanks.
Click to expand...
Click to collapse
This is known problem, did you used latest twrp ?
Pls search the forums before posting a new thread..
Follow this post here :
https://forum.xda-developers.com/s7...l-twrp-hero2lte-3-0-0-0-t3334084/post79871347
Sent from my S7 Edge using XDA Labs
gueabd said:
Hello;
I wanted to root my G935W8 Oreo 8.0.0, i already flashed TWRP 3.2.3 with ODIN v3.13.1.
The problem is when i'm on recovery mode and i use TWRP in order to install zip it shows me that internal storage is 0 MB
And when i choose Micro SD card to install Magisk-v19.zip and i confirm flash, it shows me in red:
could not mount /data and unable to find cryptofooter.
failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
unable to mount /data/media/twrp/.twrp.
Can anyone help me to root it.
Thanks.
Click to expand...
Click to collapse
I know it's a bit late to write to you, but now I got the same phone. The same thing happened to me and I discovered a solution and it is the following: download the latest twrp then the patched version of Odin, it can be version 3.13 or 3.14 which is the final one. Once you have all that in Odin disable the automatic reboot option in (ap) put the twrp.md5.tar, then put the phone in download mode and install it. Once installed, press the power button and volume down for a few seconds until the phone turns off. Now enter the recovery, then go to the format option and write (yes) so that all the information is erased and ready, you can see the internal memory. The only bad thing that I found is that the original system is not Root since the system is damaged, so you have to install the Floyd s7 version 5 rom. It is the most stable version and has Android 10, and you have to root it install later. If you install this rom there are some patches that are to record in 4k at 60 frames and have ar-sticker.

Twrp unable to mount data/decrypt data even after flashing decrypt.zip

Hi!! I have unlocked my bootloader, flashed twrp successfully. But when i boot into twrp it asks a password and then a message pops up and shows
"Unable to mount storage".
"Failed to decrypt data".
After that the internal memory and every data partiton shows 0mb. I have to factory reset my phone so thattwrp can read the memory in my phone.
After that i flash decrypt.zip and magisk and then boot into my system. But when i boot into twrp again the same message pops up and it cannot read my memory.
Can anyone help me i have been trying to fix my twrp for over a week now:crying:.
what version of TWRP are you using?
If you are from locked bootloader and flashing TWRP via fastboot for flashing custom roms, TWRP will recommend you to wipe internal storage.
I used Advanced Wipe and select all except USB-OTG and Micro SD Card to remove the encryption set by the stock rom to the internal storage and to clean the phone for the preparation of flashing custom rom
After that, that will fix the "Unable to mount storage" error and internal storage is now available. You don't need to flash decrypt.zip when you are flashing a custom rom unless you are flashing a modified Stock rom or the dev recommends it for their custom rom :good:
jude thomas said:
Hi!! I have unlocked my bootloader, flashed twrp successfully. But when i boot into twrp it asks a password and then a message pops up and shows
"Unable to mount storage".
"Failed to decrypt data".
After that the internal memory and every data partiton shows 0mb. I have to factory reset my phone so thattwrp can read the memory in my phone.
After that i flash decrypt.zip and magisk and then boot into my system. But when i boot into twrp again the same message pops up and it cannot read my memory.
Can anyone help me i have been trying to fix my twrp for over a week now:crying:.
Click to expand...
Click to collapse
See my new Q&A thread.
Sent from my ZenFone Max Pro M1 using XDA Labs

Internal Storage isn't present in twrp and falild to mount with invalid argument while wiping

Hello,
the problem occurs when i flashed this zip file VoLTE-patch-yuphoria-by-huboinc i was trying to fix dropped mobile signal issues but after that flashed file i cant boot to my rom and the internal storage in twrp is 0mb and all partition (vendor, data system,..) are not present and they are 0 mb except for microsd i tried booting to erecovery to install stock rom via sd card it keeps booting any soluation would be apperaciated
I FIXED THAT after board firmware flash

Categories

Resources