When I boot on system, there is a message say that:
Security policy restricts use of external sdcard
Click to expand...
Click to collapse
When I tried to mount sdcard in Recovery mode, it can't mount sdcard. They show this error
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
I: failed to mount ext4/vfat/exfat /dev/block/mmcblk1p1 /sdcard (null)
W: failed to mount /dev/block/mmcblk1p1 /sdcard ext4 (No such file or directory)
E: Can't mount /sdcard/
Click to expand...
Click to collapse
Is my card reader chip on my s2 broken?
Go to Settings/Security/
Device Admins and see if there are any possible restrictions else try wiping cache and dalvik cache (just in case) !
oh i just read it again and i saw you posted EXTERNAL sdcard, haha i thought it was internal sdcard
well do what niku~ said. first go in security and see if there's smth and wipe cache/dalvik.
it happened to some people that flashed a theme to the Rom, and after flashing another theme, the bug disappeared...so if u flashed a theme, try it...
if it doesnt work, try reflashing Rom.
if it doesnt work too, i suggest you do a full wipe and flash another Rom.
this is probably a software issue
it happened to some people that flashed a theme to the Rom, and after flashing another theme, the bug disappeared...
Related
hey, I installed the CM7 today by using the clockworkmod 0.8 (I used the VEgan 5.11 before )
I wipe cache partition, wipe data, wipe, wipe Dalvik Cache
but when I wipe Dalvik Cache, there is a error: can't mount dev/block/mmcblk0p2
anyway, I install the CM7 successfully... but I am a little worried about that erro...
so why this error appear? what is that mean?
do I need to fix this error and then reinstall the CM7?
sorry for so much naive question! thanks!
savage0,
I've read two or three explanations for why that
error comes up -- but I really don't know why.
I do know that a pile of folks have been getting
that message almost since the G-Tablet came
out and I have never heard of it meaning anything
significant -- or anyone having problems as a
result.
Forget it is my advice.
Rev
Exactly. Had that issue since my first flash and nothing fixes it. On the good side, like the Rev says, it has no known meaning or consequence.
savage0 said:
h
but when I wipe Dalvik Cache, there is a error: can't mount dev/block/mmcblk0p2
Click to expand...
Click to collapse
im gettting the same error, but when i try to mount /data, and now im stuck in a constant boot loop
savage0 said:
but when I wipe Dalvik Cache, there is a error: can't mount dev/block/mmcblk0p2
Click to expand...
Click to collapse
The correct error message actually is:
Code:
E:Can't mount /dev/block/mmcblk2p2
(File exists)
As butchconner said, it's a harmless error message. It just means that
a) You don't have an external SD card in the SD card slot, or
b) If you do have one, it does not have a second partition on it. Most likely, you have a SD card with a single VFAT partition.
When you select the "Wipe Dalvik Cache" option, CWM does, basically, this:
1. Mounts the /data partition. This, on the gTablet, is the second partition (Linux ext3 type) on the internal SD card, /dev/block/mmcblk3.
2. Mounts the /sd-ext partition. This is the second partition (generally of Linux ext3 type) on the external SD card, /dev/block/mmcblk2.
3. Mounts the /cache partition. This is a yaffs2 filesystem (on /dev/block/mtdblock4) on the in-built NAND flash chip.
4. Prints a "Confirm wipe?" message and a "Yes - Wipe Dalvik Cache" menu.
5. Removes the entire /data/dalvik-cache directory tree.
6. Removes the entire /cache/dalvik-cache directory tree.
7. Removes the entire /sd-ext/dalvik-cache directory tree.
The error message you noticed comes at step 2 because there is no external SD card, or, the external SD card does not have 2 partitions on it.
The second line, "(File exists)", is the left-over result of a mkdir() system call used to create the mount-point directory which already exists.
If you can read C code and wish to look at this further, look at the show_advanced_menu() function here:
https://github.com/CyanogenMod/android_bootable_recovery/blob/gingerbread/extendedcommands.c
The link is for a newer version of CWM, so the error message is different.
Cheers!
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
Hey guys, wondering if you could help me. I'm running Jelly Blast V-3.5, with Rafaels Kernel 2.6.35-7 on my S5380i. I've been trying to increase the internal storage on my device by partitioning my 32gb card in CWM with a 1gb ext. I've tried every solution I've found on this forum but I simply cannot get it to mount. Link2sd yields 'invalid argument' no matter where I point it, and when trying to format/mount the ext. in CWM it just says 'apps 2 sd partition not found'.
Here's a list of the things I've tried which have failed to solve this:
Partitioning in minitool, with various sizes and exts, and setting the partition as active.
Flashing conrod script, doesnt seem to be effective.
Script to mount sd-ext at boot, followed iamareebjamal's guide found here http://forum.xda-developers.com/showthread.php?t=1971689
S2E
Mount2SD
I'm completely at a loss, and with the internal storage of the S5380i being what it is, it would be great if anyone could offer me any advice.
Thanks!
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
soham jambhekar said:
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Thanks for responding.
Attempted to mount in CWM but just receive an error. It's as if the partition isn't there at all. Re-partioned the card but still, no luck.
My rom doesn't have the auto mount at boot option, so it looks I'll have to mount with terminal emulator. Could you run me through the process, or point me towards a guide? Cheers
what error did you get in cwm while mounting ?
yry this line in terminal
mount -o rw /dev/block/
mmcblk0p2 /sd-ext
also is mount2sd file present in your /etc /init.d folder ?
Sent from my GT-S5670 using xda premium
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
galaimo said:
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
Click to expand...
Click to collapse
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
Click to expand...
Click to collapse
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
galaimo said:
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
Click to expand...
Click to collapse
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
ChelebiTech said:
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
Click to expand...
Click to collapse
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
galaimo said:
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
Click to expand...
Click to collapse
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
ChelebiTech said:
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
Click to expand...
Click to collapse
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
galaimo said:
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
Click to expand...
Click to collapse
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
Click to expand...
Click to collapse
Thanks for taking the time to talk me through this.
Turns out my SD card is defective, swapped for another card and I've now increased my internal storage!
I'll be sending the other one back.
Thank you again for your time :good:
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
Click to expand...
Click to collapse
Thanks for the link! seems like my CWM wasn't detecting sd-ext.. this fixed!! feared my sd card was ruined.. really thanks a lot!
I recently followed a guide to increase my ram by using swapper2 on my galaxy s3 mobile , i must did something wrong ,then the phone stuck at the boot loop
my usb port is damaged so i tried to flash a custom rom but it didn't work
I'm using cwm v6.0.4 when i choose wipe data/factory reset it says
E: unknown volume for path [/sd-ext]
Click to expand...
Click to collapse
and when i choose mount /efs it says
error mounting /efs
Click to expand...
Click to collapse
when i choose format preload it says
E: format_volume: make extf4fs failed on /dev/block/mmcb1k0p10
Click to expand...
Click to collapse
i used aroma installer to know what the problem really is , i chose Exec Demo and it showed that
Mounting /sdcard
Mount:can't find /sdcard in /ect/fstab
Mounting /system
Mount:mounting /dev/block/mmcblk0p9 on /system
failed: Device or resource busy
Mounting /data
Mount:mounting /dev/block/mmcblk0p12 on /data
failed: Device or resource busy
Mounting /sd-ext
mount:can't find /sd-ext in /ect/fstab
Click to expand...
Click to collapse
so please help
so should i give up ?!!
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) ...