Hello.. I currently have PhireMod 6.3 installed on a SD card using these instructions:
http://forum.xda-developers.com/showthread.php?t=998861
I'm trying to add an IMEI to the system using these instructions:
http://forum.xda-developers.com/showthread.php?t=1004102
I can generate the new frameworks.jar fine, but I cannot figure out a way to mount the /System directory as read/write. I tried downloading the Mount System RW app from the marketplace, but that did not fix it. Is this a problem because I'm running it off the SD card instead of EMMC?
I'd just my Windows IMEI Generator/ROM patcher program here.
I have been using OmniROM KitKat on my Galaxy S2 for a while with no problems. I've recently had a GPS issue (still don't know the cause but that's another issue for another day) so decided to update my ROM to the latest nightly. The update went well, but then I found that I could not access any of my apps that had been copied using Link2SD.
I had created an EXT3 partition on my SD card and linked all files onto there using Link2SD. It had been working perfectly before but the update had obviously changed something in my system. When I run Link2SD, I get the following message:
mount: Device or resource busy
Googling this it looks like the partition is already mounted (a2sd?) or some scripts are missing. (Link2SD still has root permissions) I've had a look in init.d but can't see anything remiss, though I'm moving out of my comfort zone here.
Can anyone tell me what I should do next? Do I need to delete and recreate the EXT3 partition, copying the data back on to it? Would uninstalling and reinstalling Link2SD help, or would that cause even more trouble?
Finally, if I do another ROM update, what should I do to stop this happening again?
Thanks for your help.
I've had some success with this. I reformatted the partition to be FAT32 and Link2SD accepted this and created the necessary mount links. I then copied the files (apk etc) back onto the partition and everything is working again.
Now is FAT32 a good option for this partition or is it best to use EXT?
Ta
My phone is G900F.
TWRP(3.0.2) not detecting external storage, shown as 0MB
I use stock ROM. In android 5.0 Lollipop, it is normal to mount External SD card. However, in android 6.0 Marshmallow, it shows 0MB and I cannot mount it manual (select tick).
However, mounting external SD is normal after I booted to the system and can use normally. i can read my sdcard in root explorer and other apps.
Can anyone tell me whether it has solution? Or it is a bug in TWRP?
Thank you very much and best regards. Please help.
sonic997 said:
My phone is G900F.
TWRP(3.0.2) not detecting external storage, shown as 0MB
I use stock ROM. In android 5.0 Lollipop, it is normal to mount External SD card. However, in android 6.0 Marshmallow, it shows 0MB and I cannot mount it manual (select tick).
However, mounting external SD is normal after I booted to the system and can use normally. i can read my sdcard in root explorer and other apps.
Can anyone tell me whether it has solution? Or it is a bug in TWRP?
Thank you very much and best regards. Please help.
Click to expand...
Click to collapse
Bug in twrp. I have to use 3.0.0 for external sd access. Some twrp versions fail on aroma too.
ASHLEY117 said:
Bug in twrp. I have to use 3.0.0 for external sd access. Some twrp versions fail on aroma too.
Click to expand...
Click to collapse
Thanks~
I have changed to CWM! It has great compatibility ~
External SD works again! amazing!
Hi, I'm not an expert about mods on phone but I try it..
I have got my Note4 in signature with root access and E-motion kernel r26 installed into phone. The firmware is the stock one "DPH1".
1)
I installed Link2Sd and I followed the guidelines for partitions (ext2, etc.) to install apps to sd.
Today I've installed Foldermount app to move Whatsapp in extsd and this app has formatted my ext partition with deleting of my apps.
Therefore can't Link2sd and Foldermount operate together?
2)
How can I know my sd class? I tried through Sd tools but when you want test the sd card you get an error writing buffer.
Thanks for your helps..
Sent from Note 4 device - Rome - Italy
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