I have installed TWRP and SuperSU following instructions here and it all works but If I try to install any zips or do any sort of wiping i get a list of error messages :
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid arguement)
Unable to recreate /data/media folder.
Unable to mount storage.
etc
I have tried reinstalling TWRP and SuperSU, even tried reinstalling firmware and still get the errors. My phone seems to be working fine as long as nothing goes wrong or I imagine I can't install a ROM
Any advice would be greatfully appreciated.
Related
hi i am a noob and i downgraded from the crc1 to the rc29
and i get in the recovery menu E:Can't mount CACHE:recovery/log
i fallowed the http://forum.xda-developers.com/showthread.php?t=538456&highlight=crc1
and got to this part "If you are coming from another Apps2SD ROM. In order to guarantee you won't have any issues with the install you should remove all directories starting with "app" and the dalvik-cache directory on your /system/sd (ext2/ext3) partition. If you backed up your whole SDcard, this shouldn't be a huge issue. - Yes you'll have to reinstall your apps. You can try to skip this step, but if the install fails, rinse, wash, repeat and don't skip this step." and did not understand what i needed to do
i tried to complete the guide and now all that i have is the E:Can't mount CACHE:recovery/log and i cant load any update.zip.
i really dont know what to do pls help
To resolve this error, you must wipe in the recovery mode (Alt+w) and then try installing
thanks i did it and it worked, but now i have a different problem
when i try to mount the g1 the pc doesn't recognizes the phone, what should i do?
My galaxy S3 Crash and TWRP says it can't mount anything internal. So I thought I would install CWM Rcovery and see what happens. I used Odin and it says it went find, but I noticed that the progress bar on the phone never displayed. When I reboot, TWRP is still there. What's wrong?
Reflash with Odin but don't check auto reboot. After flashing cwm, remove cable, remove battery, replace battery, he button combo to get into recovery.
Same thing. Odin sees the phone, then acts like it is flashing, but I never see anything happen on the phone itself. I thought normally there is a progress bar to show something is uploading, but nothing happens. When I go into recovery mode, I am back in the teamwin screen which takes about 3 minutes to boot. When I go to the TWRP log, I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder/
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/data'
E: Unable to mount '/cache'
E: Unable to mount internal storage
E: Unable to mount /data/meda during GUI startup
E: Unable to mount '/cache'
E: Full SELinux support is present.
Running boot script...
Finished runing boot script
E: Unable to mount '/cache'
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount '/data'
Is the phone an i747 or i747m?
Have you tried mounting the data partition in twrp and formatting it using a Windows machine?
Hello everyone,
I have a little problem with TWRP on my LG G3 (D855, 32 GB).
I installed TWRP two months ago and flashed CyanogenMod 12.1.
Now I've noticed that TWRP (2.8.6.0) shows the Internal Storage with 0MB.
When I tap the middle Icon on the bottom of the TWRP Main screen, I get an (maybe helpful?) output:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
...done
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
I'm a bit confused. Could this be, because I used CyanogenMod's Device Encryption?
I'm planning on reverting to Stock Rom (...i quite liked it. And considering the camera quality, CM isn't really any better), but i fear this (or flashing anything different) could brick my phone, since there seems to be something strange.
Is there any way to debug or even fix this?
Is it safe to revert to Stock, when TWRP doesn't even detect the Internal Storage? (following this Guide: http://forum.xda-developers.com/showthread.php?t=2785089)
I'd be glad about any help oder hint, about how to proceed. Thanks in advance!
First, update your TWRP version to 2.8.7.0 (available here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129 )
Then, boot into TWRP, go to Wipe and choose "Format Data".
After done that, reboot your device into recovery again.
Thank you very much. I will try this.
i had that , but dont remember what i did ,, but i do know you need to format , by fastboot or twrp and repair partitions
It happens often to me when I upgrade.
I use 3 phones: Xperia Z2, LG G3, Samsung Galaxy S2 and when I've updated to Lollipop it happened all three times.
Recently I noticed that also on the S2 happened this and I suppose it's because partitions are not initialized.
I was unable to write to internal partition (0 MB) and I've solve this way:
I've flashed CyanogenMod, mounted the internal memory as flashdrive under windows and simply formated it.
When I've disconnected the phone from the pc, Android was able to write normally to the internal storage and everything worked like a charm.
I know it's not possible (AFAIK) to mount internal memory on stock roms as Mass Storage, but perhaps someone will point you on how to correctly fix partitions without using my method.
Looks like Kill Switch Wiped
Did you find any solution, even i am struggling with same problem. I think LG G3 has kill switch that wiped out everything, but not sure just guess.
Have same problem any help?
I have a Samsung Galaxy S3 (SGH-I747). It was running fine on CM13 nightlies. One night I needed the phone for calculator (odd enough lol) and noticed it was turned off. I turned it back on. It seemed like it was just gonna boot like it usually does but I got a bootup message claiming that the /data partition is corrupted and needs to be reset to continue using the phone.
I followed the phones instructions and did the reset (I've had to factory reset before I really didn't care). It booted to TWRP (3.0.2-0) and started the factory reset. The log for the recovery showed many errors. Heres the log if I just boot into TWRP without doing anything:
Code:
[COLOR="Red"]Failed to mount /data and unable to find crypto footer.
Failed to mount '/data' (No such file or directory)[/COLOR]
[COLOR="red"]Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]Unable to mount '/data' (No such file or directory)[/COLOR]
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (No such file or directory)[/COLOR]
Full SELinux support is present.
Running boot script...
Done.
[COLOR="red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
[COLOR="red"]Failed to mount '/data' (No such file or directory)[/COLOR]
The same errors pop up when wiping the device too.
Here's what i've tried:
The corrupt data reset (didn't work)
Reinstalling a new copy of CM13 (didn't help)
I also have tried flashing stock images (AT&T) firmware. Did not work, the AT&T system says the /data partition is corrupted too and cannot do anything about it.
NOTE: The /data partition info in TWRP shows the size as 0MB!
I've posted for help on the cyanogenmod forums but no avail so far. I do not what to do next and need some suggestions.
Thanks.
Have you tried Odin to flash the stock firmware?
StoneyJSG said:
Have you tried Odin to flash the stock firmware?
Click to expand...
Click to collapse
That's what I used to get the stock firmware on it in the first place...
I'm still learning how to mod and customise android so I completely missed this.
The fix was as simple as changing the filesystem into a different format on TWRP..
Sent from my SAMSUNG-SGH-I747 using Tapatalk
TechGuyAnthony said:
I'm still learning how to mod and customise android so I completely missed this.
The fix was as simple as changing the filesystem into a different format on TWRP..
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
thanks for posting fix as i'm sure it will help others.
"err on the side of kindness"
Hi,
I tried to flash viperOS using squid twrp for moto G5S, but something in the process i think i did wrong.
My phone model is montana xt1790.
I unlocked the bootloader.
I tried to install the recovery, but had same problem than @dau999
dau999 said:
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
Click to expand...
Click to collapse
I tried to flash "no-verity-opt-encrypt-5.1.zip" file posted as solution here https://forum.xda-developers.com/showpost.php?p=74813124&postcount=23.
After this i have working the recovery, but i believe this is what did wrong:
With debug mode enabled, after a wipe clean (Cache, Data, Dalvik/ART and system) and format data (wipe all your apps, backups, pictures, videos, media and removes encryption on internal storage) got this errors:
Code:
Could not mount /data and unable to find crypto folder.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage.
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
After this errors i flashed ViperOS, but after first boot it, first thing viper OS ask me was the phone password, after i enter it, the phone show up a message saying that password is ok but data is corrupt, restarting and trying to fix my phone without success (same errors like failed to mount /data)
Also i tried to use the "repair or change file system" selecting Data partition, twrp show me this: http://oi65.tinypic.com/2prin8y.jpg, also i got this errors:
Code:
/sbin/fsck.f2fs /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to repair Data
What should i do?, i don't know is related with an encryption on data partition, or if this can be solve.
EDIT:
Found the solution in reddit: www.reddit.com/r/AndroidQuestions/comments/7w5c75/used_the_format_data_option_in_twrp_recovery_on/
Just fixed the issue after making a second format in TWRP ( WIPE > FORMAT DATA)