Just wanted to post this in case anyone runs into this problem with the EVO 4G LTE. I believe I caused it by trying to "Factory Reset" via bootloader.
I was unable to format /sdcard via busybox per instructions in other threads. I was, however, able to format fine with Windows 7. The proper options are:
File System: fat32
Allocation Unit Size: 4096
Perform a quick format: Unchecked
The other settings can be left on default. Similar settings should work from other operating systems. After this, you can mount the /sdcard via your recovery and transfer/flash your downloaded rom.
Edit: must mount via recovery so it will show up in Windows.
Thank your for this post. I was trying to load a ROM and something errored out. Then, I tried to load it again but noticed that I had to following:
E:failed to mount /sdcard (invalid argument)
I was able to format in Windows 7 and then sucessfully load the ROM.
I was actually stuck in a boot loop prior to me trying to reformat the card. To fix that, I pressed down the power button for about 45 seconds and then it eventually stopped rebooting. I was then able to get into recovery.
Anyway, hope this helps someone.
failed to mount /sdcard (Invalid argument)
Hi there, just got the same error message up. I've tried formatting in bootloader (cwm), also twrp and neither allow the sd card to be seen on pc. I've used minitool partition wizard to partition on the pc following instructions from the xda site and that doesn't show up on the android system either way i format from pc it comes up on mounting from android as the "failed to mount /sdcard (Invalid argument)" error
Any other solutions anyone??
Thanks
Dan
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Gizzy00360 said:
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Click to expand...
Click to collapse
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
petitgregory said:
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
Click to expand...
Click to collapse
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Gizzy00360 said:
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Click to expand...
Click to collapse
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
petitgregory said:
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
Click to expand...
Click to collapse
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Gizzy00360 said:
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Click to expand...
Click to collapse
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
petitgregory said:
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
Click to expand...
Click to collapse
I had a few reboots when it was working, then it just suddenly bricked my phone
Sounds like the eMMC brickbug. You need to get the eMMC replaced. All of you that face the problems.
Well, after four years my S3 was getting very slow. It was bearable with CM, but I decided to say farewell now.
Also, my microphone was busted when I dropped it at some point, so I could only call with a headset anyway.
It's not worth replacing I think, time to move on
The same happened to my Beelink GT1 S912 9377 TV-box (after failed OTA update). Will check eMMC brickbug (from TWRP) ...
My device is SD
i'm on china dev MIUI 8
boot loader is officially unlocked
installed alka recovery via fastboot
from fastboot i'm not able to mount 'Data' and because of that recovery is giving me a error 'Failed to mount '/data' (invalid argument)
internal storage is also showing its size 0mb
whenever i click on 'data' it does not get ticked in Mount option of recovery
i tried with coffice recovery too but same error is there everytime
i'm not able to backup my efs
i'm i missing anything
sunny277 said:
My device is SD
i'm on china dev MIUI 8
boot loader is officially unlocked
installed alka recovery via fastboot
from fastboot i'm not able to mount 'Data' and because of that recovery is giving me a error 'Failed to mount '/data' (invalid argument)
internal storage is also showing its size 0mb
whenever i click on 'data' it does not get ticked in Mount option of recovery
i tried with coffice recovery too but same error is there everytime
i'm not able to backup my efs
i'm i missing anything
Click to expand...
Click to collapse
i had same problem and that was because i had formatted data and internal storage to f2fs format and after formatting them back to ext4 everything working fine.maybe you had same prob like me so try formatting data into ext4 format using twrp
I have an old Oneplus one that I would like to get working to recover some data. The phone is stuck in a bootloop. This happened out of nowhere one day while charging. I was running CM 11. I can still access twrp(version 3.0.2-0) and i can enter fastboot. The various partitions are as follows Boot(16MB), System(733MB), Data(OMB). The 0 MB in data in odd. Also the storage doesnt mount. Whenever i try to format data it says, "Failed to mount '/data'(invalid argument), unable to recreate /data/media folder, unable to mount storage". If i try to repair or change the file system, it says the same thing. Any help would be appreciated. Thanks.
I have a ZTE Axon 7 (A2017U) and I'm trying to install a stock rom (A2017UV1.1.0B35). I currently have TWRP installed and an unlocked bootloader. I can access the device via fastboot and TWRP recovery mode, but otherwise it will not boot.
I'm stuck in a loop:
If I install my rom via TWRP, when I reboot the phone the /system partition is never mounted. I can see "Failed to mount '/system' (Invalid argument)" written in the log
If I view the /system partition details on TWRP's "Wipe->Advanced wipe->Repair or change file system" screen, the partition is listed as "Present: Yes, Removable: No, Size: 0MB, Used: 0MB, Free: 0MB, Backup size: 0MB
If I format the /system partition using "Wipe" function, the "Formatting system using make_ext4fs" operation succeeds and partition seems to be correctly formatted using ext4, and is listed as "Present: Yes, Removable: No, Size: 5455MB, Used: 10MB, Free: 5444MB, Backup size: 10MB
I'm able to access the partition via the terminal, and if I write a text file to it and reboot the device, I'm able to read it back... It seems the partition is working correctly.
I attempt to install the rom again using TWRP's "Install->Install zip" option, and after ~10 minutes it states that installation was completed successfully.
I reboot the device and the OS does not load. If I access TWRP, I see the /system partition is not mounted and the cycle continues
I've also tried installing other roms (e.g. Lineage OS), but they all fail assert checks, even thought I'm 100% positive they're for the correct device.
I'm tearing my hair out here. I'm a programmer by day and I'm fairly experienced with Unix, but admittedly I don't have much experience working with Android. There's a good chance I'm missing something.
Any idea what's going on, or what to try next? Is there any other information I can provide that might help me troubleshoot the problem?