Database Users

Can't read extSdCard after enable encryption

All,
I am using safestrap+gravition on i337 MF3. So far it was good for a week, but today my SD card stopped showing up. When I replug the SD card i got a message telling Preparing SD card checking for errors. This message stays forever. If I kill it the SD card just doesn't mount
I tried to mount it manually with:
mount -t vfat -o rw /dev/block/vold/179\:33 /storage/extSdCard/
and I am able to mount the card and see it through terminal. But none of the apps is able to see the /storage/extSdCard content. I checked permissions and they look good
Let me tell that I am using email.apk, the modified app to circumvent exchange security. As I said, this worked well until this morning that it stopped working.
http://forum.xda-developers.com/showthread.php?t=1749921
I removed the account and the issue stayed. I wiped all the data out and it fixed the issue. However, when I create the exchange account it happens agan.
Any has undergone this kind of situation
Also, a possible workaround would be mounting the SdCard manually. But I am not able to make it visible to the APS, am I missing something besides that mount command?
Thanks!!

[Q] system partition corrupted (can't umount)

Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:

Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...

Can't install app - insufficient storage available

Notification: I have been asked by Droidriven to move my question from XDA Assist Forum to this Forum !!!
================================================================
I cannot install anymore applications. I got an error "Can't install app - insufficient storage available".
I lack place on my device, so I move app as much as I can to the External card using AParted and Link2SD.
I found out that every time I want to link to SD card with Link2SD I got a warning: "NOT MOUNTED - /data/sdext2 mount not found"
When Link2SD starts, it opens a window asking to select my SD card's second partition from the following list: ext2, ext3, ext4 (the others are irrelevant). Whatever I choose I get an Mount script error "Mount script cannot be created. Mount invalid argument".
I checked the Storage Info (using the Link2SD app), and found that all the "partitions" - like Internal, SDcard, External SD, System and Cache - have some data and the percentage of free place - except "SD Card 2nd Partition" that remains empty. There is even a label that says "NOT MOUNTED".
I searched my phone trying to find the "sdext2" to mount it (how do I do it?) - but I couldn't find it. This is an CATCH 22 situation :laugh: I cannot download and install app but I can continue to use my phone with a lot of app removed!
Is there a way to delete the /data/sdext2?
is there a way to mount the ext2?
How can I repair it?
Somebody with some help?! Please, don't recommend me to use the frightened FACTORY RESET - I had enough of this solution!
thanks, Roby
------------------------------------------------------------------------------------
Answer to Droidriven:
Do you have root explorer set and mount R/W set correctly?
Click to expand...
Click to collapse
I use Root Explorer. I found "sdext2" ! It is under "root" as follows: "/data/sdext2". Its permissions are "rwxrwx--x". I unchecked the last "x" (it shows on the column of Other Execute) but it didn't saved! Why?
Are you sure you followed instructions to setup Link2SD correctly?
Click to expand...
Click to collapse
I don't remember I believe so. I bought the Link2SD Plus more than one year ago.
Roby

So is this a stock rom we're talking about?

GDReaper said:
So is this a stock rom we're talking about?
Click to expand...
Click to collapse
YES!... and rooted!~!!

I cannot install anymore applications in my GT-i9505
My GT-i9505 fell down and seems something went wrong! I cannot install anymore applications. I got an error "Can't install app - insufficient storage available".
When Link2SD starts, it opens a window asking to select my SD card's second partition from the following list: ext2, ext3, ext4 (the others are irrelevant). Whatever I choose I get an Mount script error "Mount script cannot be created. Mount invalid argument".
I cannot link or remove system app. System app that have the option to "Link to SD Card" or to "Remove Link", they encountered with a warning: "NOT MOUNTED - /data/sdext2 mount not found" Moving user applications from SD Card to Phone is no problem at all.
I checked the Storage Info (using the Link2SD app), and found that all the "partitions" - like Internal, SDcard, External SD, System and Cache - have some data - except "SD Card 2nd Partition" that remains empty. There is even a label that says "NOT MOUNTED".
I use Root Explorer to find "sdext2". I founded it! It is under "root" as follows: "/data/sdext2". Its permissions are "rwxrwx--x". Believing that this is the problem, I unchecked the last "x" but it didn't save! Why?
I cannot download and install app but I can continue to use my phone with a lot of app removed!
Is there a way to delete the /data/sdext2?
is there a way to mount the ext2?
What could happen if I delete Link2SD and Link2SD Plus, I restart the phone and install Link2SD again?
Is there a way to repair it? XDA Senior members, you are the geeks here, aren't you? Please, I ran out of ideas!
I don't want to FACTORY RESET my phone - I had enough of this solution!
I am afraid that all my data will be wiped off!
thanks, Roby[/QUOTE]

Flash a custom recovery, backup your data, do a factory reset.
Or use Titanium Backup to backup your apps and do a factory reset or flash another rom.

Link2sd Mount error- "2nd Partition not mounting during boot" (SM-A710F)

Im getting Link2sd mount error :- "Since the 2nd partition is not mounted during boot time it has been mounted after the system finishes booting. Therefore linked apps are not visible to the system at the moment".
After I follow its advice and do a quick reboot (soft reboot) everything is ok
After researching a lot, I can tell that both init.d & install-recovery.sh is required, which cannot find in /system/etc (using root explorer).
Please suggest if it can be created or not.
Mobile is rooted with Twrp 3.0.2 installed (running 5.1.1).
Busybox is also installed

SM-T580: Issue with Card Card setup (Link2SD and Titanium access)

Edit: Title should read "SD Card" (how to edit that?)
I have root and I am trying to get Link2SD to work. I have created the FAT32 (primary) and EXT4 (primary) partitions but I keep getting a mount script error ("unable to mount") (Also tried EXT2)
I am doing the same thing as I have done on several other devices and it is not working on the samsung.
Also, I am having issues with getting Titanium Backup to wrtie to the SD card too. I tried the Kitkit SD card patch but it failed.
I know the SD card works so I am thinking it is a wonky Samsung thing?
Thoughts or advice
Edit: Pulling SD card, re-inserting and rebooting and then Link2SD reports that the 2nd partition is not accessible during boot (and suggests quick boot to fix which it does not). Samsung says the FAT32 is fine but the EXT is "corrupt" but I have confirmed on two other devices it is fine.
So this seems to be some sort of access thing. Maybe related to the removal of encryption patch as part of the TWRP install?
Edit2: cat /sys/block/mmcblk2/device/type gives back "no such file or directory"; (whereas mmcblk1 gives SD)
Total commander shows sd-card (which is internal /storage/emulated/0), sd-card(2) "/data/sdext2"), and USB (SD FAT32 as /storage/BDB2-8960)

Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.

chemie99 said:
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
Click to expand...
Click to collapse
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.

moxalis said:
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
Click to expand...
Click to collapse
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?

chemie99 said:
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
Click to expand...
Click to collapse
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.

moxalis said:
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
Click to expand...
Click to collapse
How do I manually delete the mount scripts?

chemie99 said:
How do I manually delete the mount scripts?
Click to expand...
Click to collapse
There is the option "Delete mount scripts" in the Apps2SD app. Check their FAQ page for any questions, it's pretty helpful.

Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?

otamaglimmer said:
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
Click to expand...
Click to collapse
Seems Link2SD does not like Marshmallow so I switched to Apps2SD (which also suggests what you did). It would not create the partition itself but took windows EXT4 and after a bunch of config, worked. The issue I now have is that Samsung still thinks the card is corrupt (which it isnt); any EXT partition and it says that. So on any reboot it greets me with a system notification of a corrupt card (which I want to get rid of but so far can't)..
I did try adoptable using a scripts from this site (didn't work) and the Apps2SD option. Seem to work on device but windows only saw the device memory so would not copy anything when it reported full.

took another kick at the cat today; installed Apps2SD, created mount scripts, but now, for reasons unknown, it no longer reports the SD as corrupt on boot (although it does say that partition is corrupt from the storage setting menu. Weird. No idea why it is no longer doing this. I will say the reinstall was funny. I had to delete and recreate the mount scripts several times (all said it worked) to actually get apps to move without disappearing. perhpas I ended up with a different mount script method in all the trying