-- Per a suggestion, I have moved this question from Galaxy Tab to Galaxy Tab 10.1. Apologies for any confusion. --
I've been attempting to root my SGT 10.1. Thus far I have gotten CWM 5.0.2.7 on the device, but when attempting to select the rooting ROM from the "sdcard", CWM responds that "E:Can't mount /sdcard/" It responds similarly when attempting a backup. I also get the same response when attempting to manually "Mount /data."
The tablet still works fine. The internal memory is fine - I am able to boot normally, and access my files on the device or via USB in Windows. I just can't seem to access the internal memory from CWM, and am therefore unable to flash.
Looking at the log in CWM:
W:using /data/media, no /sdcard found.
W:failed to mount /dev/block/mmcblk0p8 (Invalid argument)
E:Can't mount /sdcard
Any suggestions? I've found similar issues - but they usually indicate that the tablet is unusable, which mine is not. All of the rooting guides I have found seem to assume that the /sdcard or /data will be available in CWM right after flashing.
Thank you for your help.
E:Can't mount /sdcard
atroposrandom said:
-- Per a suggestion, I have moved this question from Galaxy Tab to Galaxy Tab 10.1. Apologies for any confusion. --
I've been attempting to root my SGT 10.1. Thus far I have gotten CWM 5.0.2.7 on the device, but when attempting to select the rooting ROM from the "sdcard", CWM responds that "E:Can't mount /sdcard/" It responds similarly when attempting a backup. I also get the same response when attempting to manually "Mount /data."
The tablet still works fine. The internal memory is fine - I am able to boot normally, and access my files on the device or via USB in Windows. I just can't seem to access the internal memory from CWM, and am therefore unable to flash.
Looking at the log in CWM:
W:using /data/media, no /sdcard found.
W:failed to mount /dev/block/mmcblk0p8 (Invalid argument)
E:Can't mount /sdcard
Any suggestions? I've found similar issues - but they usually indicate that the tablet is unusable, which mine is not. All of the rooting guides I have found seem to assume that the /sdcard or /data will be available in CWM right after flashing.
Thank you for your help.
Click to expand...
Click to collapse
Almost the same problem.
E:Can't mount /sdcard
I suggest the guide here to get back to stock... and try again. http://www.teamovercome.net/p7500/?page_id=5 on down the page it has a section "restocking yer system" Its helped many people stuck in strange situations get back to normal and start anew.
Just make sure every step is double checked and followed. Hope this helps.
If you can read this it was sent using my GT-P7510.
Related
Hello,
I ran into some issues after installing the Classic Jewel V0.0.4 Rom that ultimately led to my internal SD card not being recognized or not mounted properly. For the record, I am not blaming the ROM nor am I suggesting that there is anything wrong with the ROM.
Below is the sequence of events:
1. Full wipe of everything except SD card.
2. Flashed the ROM.
3. The Phone booted all the way to the setup wizard but then rebooted.
4. Phone went into a bootloop.
5. Re-flashed the ROM without wiping.
6. The Phone won't get pass the HTC logo screen.
7. I went in recovery and wiped everything and Flashed Fresh's rom / this did not work.
8. I flashed maybe two other ROMS and still not working.
9. I went into bootloader and did a factory reset (I think this may have been my downfall)
10. The internal SD card is not mounted (or not mounted properly) in Recovery. (I can see the SD card, and see the TWRP folder but nothing else.)
11. Flashing any ROM fails. I see several lines of this error: "E:failed to mount /sdcard (invalid argument)"
12. I tried to do a restore but the file is not there (I guess it's because the internal SD card is acting up?)
Any ideas on how I can fix this?
----------------
Edit:
Here are some more errors that I see while in Recovery
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard during GUI startup.
*Verifying filesystems...
*Verifying partition sizes...
E:unable to mount /sdcard
E:unable to mount /sdcard
Running boot script...
Finished running boot script.
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard
E:failed to mount /sdcard (invalid argument)
-----------------
Thanks,
Aloupha
I think my problem could be fixed by doing something similar to what's discussed in this thread... but I have no clue on what to do.
http://forum.xda-developers.com/showthread.php?t=1526912
Stab in the dark but can you get Windows to recognize the sd while in recovery? If so open cmd prompt and type chkdsk /X /F <SD card drive letter> and see if it repairs it......just a thought
Sent from my Transformer Prime TF201 using Tapatalk 2
The problem is gone!
The strangest thing happened. I kept flashing roms and they kept failing. Eventually, I tried flashing the MeanRom and it flashed successfully.
I am not sure how that was possible but I am happy! I lost some most of files I had in the Internal SD card though but that's okay!
I am going to install the Classic Jewel rom again and see if the same thing happen again.
I know this thread is a little old but i didn't find much else on this issue. I followed these steps to get a ROM loaded back on my phone
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I am still trying to figure out whats going on with my internal SD I will post if i find a solution.
Do not use clockwork recovery.
Sent from my EVO using xda premium
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
I have a rooted CHT firmware ASUS Padfone (4.0.3) and I want to restore the original ROM file. However, when I boot into Recovery and try to install from "external" storage, I get the message 'E:failed to mount /sdcard (Invalid argument)'. I have no other installation location such as my MicroSD card. I can't install from cache because the ROMs are too big.
There is absolutely no problem with the SDcard when in the OS (the sdcard is internal).
I have seen this error relating to other phones, but no-one else in the never-ending Padfone thread has mentioned it.
I should mention that there is no CWM available for the Padfone, so only the default Recovery is available.
Anyone have any suggestions?
PS: I posted here because I wanted a wider, more knowledgeable audience. There is no Padfone section and the things tend to get lost very quickly in the current 247 pages of the 'Padfone Thread'...
An update to this.
If I remove the external MicroSD card and try to update from Recovery, I get:
E:failed to mount /sdcard (No such file or directory)
Meh. Sussed it. Recovery doesn't recognise NTFS (the FS on my MicroSD card). Formatted FAT32 and all magically works...
Okay so last night I attempted to root my nook tablet 1.4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2037368. I downloaded all the files that were pointed to in that thread, and followed the instructions. Everything went perfect and soon I was setting up my google account, then following the final steps which involved downloading rom manager, and goo manager. All was well, until I decided to reboot the tablet.
After I rebooted the initial loading seemed fine (got the "n" screen"), then cyanobootloader popped up, then the Team B presents XDA logo popped up and then nothing. The tablet stayed frozen on the Team B logo, and rebooting did nothing.
So being the idiot that I am, I tried going into recovery from the cyanobootloder. This took me to TWRP where my dumbass ended up going to advanced and Wiping the system. After that I tried installing Cm-7-Team-B-Beata1-signed.zip and gapps-gb-20110828-signed.zip from TWRP. The log gives several messages that read:
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /emmc
E: Unable to mount /emmc
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
At this point I was freaking out, stopped using my head, and began trying desperately to go back to stock. I tried using this method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/, but it didn't change anything.
I decided then to try redoing the rooting guide again to see if that could solve the problem. It did not.
So now the tablet boots into TWRP when I turn it on. I can also enter CWM-based Recovery using the SD card I made from the guide. However, when I enter CWM-based-recovery I get these messages at the bottom:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
That's pretty much where I'm stuck on at the moment. I figured I should probably stop messing with this tablet before I made a bigger mess.
Any help would be greatly appreciated.
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard based CWM recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Nook needs a /recovery folder in /cache partition like /cache/recovery.
Somehow that folder is missing
Is so easy to fix that you will laugh
dd zero the cache partition after you make sure cwm/twrp is not have it mounted check by reading mount /cache if it says unmount cache select it first.
Then format cache in cwm/twrp and that's it. Folder will be created by it self and that error print out will stop.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
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) ...