Hi everybody,
I installed CM13 ported for my Alcatel Pixi 4 (5) 5010.
Everything works fine, excepting the camera and the external SD Card. But the camera doesn't count so much. I want to make my phone detect and use the SD Card. There is a file mmcblk1, wich I think is kinda connected with the card. If I use apps like Aparted, Parted4Android and Mount2SD the SD card is founded. But wathever option I select(mount, delete, format, create) still no SD Card directory created. Is there something I can do?
The SD Card is detected by other devices. I also formated it in NTSF, FAT32, FAT16, ext4, ext3 and still no resolved. But it is founded in TWRP Recovery.
Thanks.
PS: I also installed other ROMS and all detected the card. But this is the only one having root. (Can't root this phone, not even by flashing zip files.)
Related
Hi
I am an xperia miro user(ICS). I updated framewire recenty to 5.8 and rooted my device. Now i am having issues with my external sd card. Es file explorer although it had been granted SU permissions isnt able to create a folder ( operation failed) or transfer any file from sd card to External Sd card. Tried another app called "Rootbrowser" with which i was able to create new folder in external sd card, but still cant write to the External sd card. I have already tried formating my External sd and also changing permissions which i saw on one of the forums here.
Nothing is working for me
I have tons of space left in my External sd card and i cant use it :crying:
Kindly help and solve this issue
I've tried searching for info about this and can't seem to find anything specific. My question is can the S5 be altered so that the internal memory is just memory and not recognized as an SD card? Can it be forced to use the external SD card instead? Will this affect the pre-installed programs? I've had another phone that used the internal memory like this and had custom ROMs that "removed" the internal SD card. I'm not willing to install a custom ROM or recovery right now, but I do have root access.
I've used the edits from this thread: http://forum.xda-developers.com/galaxy-s5/general/mod-how-to-add-init-d-write-to-external-t2814733
Even with these edits, certain apps(TubeMate for example) still recognize that you're running KitKat and won't allow writing to the external SD card.
I've tried using the app Mounts2SD to move app data to the external SD, but it doesn't recognize the second partition of the SD card(I've tried Ext4 and Fat32), so either there's a problem with the SD card partitioning or the init.d section of the program isn't working correctly. I've used this app with my previous phone and it seemed to work fine. I appreciate any help or suggestions on this.
I've been rooted for a while without any issues, until recently I'm not sure what happened but suddenly TWRP won't show the /mnt folder or be able to access anything on my SD Card, I've tried mounting and selecting the SD Card in TWRP settings but it displays 0MB and won't select it. All I see is my Internal Storage files, which means I can't flash anything easily. I don't know when it happened but it was working about a week ago. I formatted my SD Card as ext4 in TWRP itself and also tried NTFS on Windows.
NOTE: I can view the SD Card in Solid Explorer and on my computer, TWRP is the only one that can't mount/read any SD Card files or even recognize it.
Is there any way I can work around this without formatting the SD Card?
Hi there. I'm using a Xiaomi Redmi 1S with 16GB SD card. Previously I had partitioned my SD card with 2nd partition set to FAT type, which I used to link apps to SD card using Link2SD. My SD card could be read fine by my laptop when I plugged it in to my laptop with a USB connector (i.e. I could open both my internal storage as well as external SD card storage). Recently I had to reformat the SD card due to some issues with my phone, and I hence deleted the old partition and created a new 2nd partition in EXT2 format instead. The 2nd partition is readable on my phone and works with Link2SD to link apps to SD card like before, however when I plug into my laptop, I cannot see the SD card storage. I can only see the internal memory storage. Please advise how to fix this, if possible without reformatting, as I am unable to move files to and from the SD card storage if I can't see it. Thank you!
Hello,
I have a problem with Link2SD which I hope someone knows an answer for. My setup looks like this:
Hardware
Galaxy A3 (2017) - SM-A320FL
SanDisk Ultra MicroSD (64 GB)
Software:
Android 8.0.0 (A320FLXXS3CRK1)
Newest TWRP for my phone
Newest Magisk
Universal Init.d Injector v2.2 (https://forum.xda-developers.com/android/software-hacking/mod-universal-init-d-injector-wip-t3692105)
How I setup the partitions of the microSD
First Partition as FAT32 (Primary) with a drive letter assigned. Second Partition ext4 (also Primary) without a drive letter. MiniTool Partition Wizard was used for this process.
Also tried a few variations of the above like making the second partition ext2 or setting the first partition to active but in the end it all made no difference
Now the strange part ....
The partitions are properly detected when I connect the microSD to the PC using a card reader.
The first partition is also detected as external memory by android and I can use it like every other SD with one partition
Link2SD is also able to detect the second partition, mount it at start and link apps to it
The problem is that my PC wont detect the sd card when I connect the phone to it. When I reformat the SD back to one partition the SD card is detected without a problem (explorer showing the internal memory aswell the external memory)
[*]Sometimes the card is also shown as not detected in the default samsung file explorer even tho the apps moved to the sdCard are stil working
Does anyone have a clue what is happening here or what I am doing wrong?
Dear user
I am having the same troubles with my a320fl when attempting to use 64gb sd card partitioned with fat32 and ext2/ex4.
Once I enter the card in the phone and restart it doesn't register on the phone.
I hope someone else can help us!
I have the same problem, also with a 64GB Samsung Evo, could this be an A3 issue?