Hi to all Devs,
Currently i have an issue with my evo5 rom installed and locked but "ROOTED" bootloader (Z1). The issue is that i cannot move any app to external sd card nor i am able to backup up with (GOBACKUP)!!! When i open gobackup it the pops up message window says
" READ/WRITE/SDCARD canot identify backups,
SD Card might damage!
1. Recommend to copy GOBackup folder to other SD Card to try again.
2: If it happened after flashing a new ROM, the ROM might deny to Read/Write SD Card, can try another ROM.
Please, i have uploaded already all my apps from my previous GB installed phone, and try to recover them so that i can get my contacts and all sms messages.
Appreciate for any help..
Apply the third party write to SD card fix from the general section.
gregbradley said:
Apply the third party write to SD card fix from the general section.
Click to expand...
Click to collapse
Firstly thanks for the answer mate. I've rooted my device by installing XZDualrecovery of "NUT". And afterwards flashed the JFXPERIAS's (EVO5) ROM for Z1 C6903.. I uploaded the screenpic of the popup window here. I've installed already third party apps like SDFIX and NextApp SDfix that supposed to to work, but they didn't, however it ought to be. Do you think the issue is because of that my device is bootloader locked or the ROM itself?
I don't think it's the ROM as no one else is reporting this issue. It could be your SD card?
If you still think it's the ROM, try a different one and see if the problem persists
Ahki767 said:
I don't think it's the ROM as no one else is reporting this issue. It could be your SD card?
If you still think it's the ROM, try a different one and see if the problem persists
Click to expand...
Click to collapse
I'am doing cloud backup and restore. So it doesnt suppose to be related to the sdcard though? What is the logic of it when i'am trying to restore from cloud to straight internal sdcard?
Tried different SDcard it failed again.
Hi , today i tried the 2 different External SDcards and it failed again, the issue is still there, and i dunno what to do!!! Is Aroma installer do the partitioning of the internal SDcard?
Jacker75 said:
Hi , today i tried the 2 different External SDcards and it failed again, the issue is still there, and i dunno what to do!!! Is Aroma installer do the partitioning of the internal SDcard?
Click to expand...
Click to collapse
I dont know if this helps, but if you really need your SD card, I suggest you make a nandroid backup, SD card backup, and flash back to Sony stock rom with root and the SD card fix. Format the SD card again through your phone Settings > Storage > Format SD card. Try again.
If that doesn't work, could be a faulty card or your SD card reader is bad (unlikely).
kentexcitebot said:
I dont know if this helps, but if you really need your SD card, I suggest you make a nandroid backup, SD card backup, and flash back to Sony stock rom with root and the SD card fix. Format the SD card again through your phone Settings > Storage > Format SD card. Try again.
If that doesn't work, could be a faulty card or your SD card reader is bad (unlikely).
Click to expand...
Click to collapse
I have tried a different SDcards too, but unfortunately it didn't do the trick too. But, i have installed the stock 534 firmware and dualrecovery then it worked fine. But, when i installed the EVO5 ROM the issue occured again and again... I think it's because of somehow the AROMA's partitioning or something related to it... I'am totally messed up...
Jacker75 said:
I have tried a different SDcards too, but unfortunately it didn't do the trick too. But, i have installed the stock 534 firmware and dualrecovery then it worked fine. But, when i installed the EVO5 ROM the issue occured again and again... I think it's because of somehow the AROMA's partitioning or something related to it... I'am totally messed up...
Click to expand...
Click to collapse
I will say it again, since android 4.3+ third party apps cannot write to SDcard.
gregbradley said:
Apply the third party write to SD card fix from the general section.
Click to expand...
Click to collapse
Try doing it manually as opposed to using apps.
gregbradley said:
I will say it again, since android 4.3+ third party apps cannot write to SDcard.
Try doing it manually as opposed to using apps.
Click to expand...
Click to collapse
Read the above posts please...
Jacker75 said:
Read the above posts please...
Click to expand...
Click to collapse
I have done, please read mine.
I say to try and do it manually by editing the file yourself instead of using apps.
If it works on a 534 FW (android 4.2) but not on later FW (Android 4.3+) then its not the phone, not the sdcard but the platform.xml file in system/etc/permissions
gregbradley said:
I have done, please read mine.
I say to try and do it manually by editing the file yourself instead of using apps.
If it works on a 534 FW (android 4.2) but not on later FW (Android 4.3+) then its not the phone, not the sdcard but the permissions file....
Click to expand...
Click to collapse
Now i got what you tried to mention. I've read about it, so i will have to edit the XML file? Well, that was the only way i didn't try. Would you paste the link of it to here please so i can easly go through it.
Thanks anyways mate.
http://bit.ly/1vvdkJG
It could also be that you have not disabled sony RIC so you are losing the ability to mount system after a reboot. The apps work by changing the file after each reboot, whereas if you do it manually it stocks because you are actually changing the file
gregbradley said:
http://bit.ly/1vvdkJG
It could also be that you have not disabled sony RIC so you are losing the ability to mount system after a reboot. The apps work by changing the file after each reboot, whereas if you do it manually it stocks because you are actually changing the file
Click to expand...
Click to collapse
Unfortunately mate, the permisson.xml settings didn't help either. You can check the permissions below. I edited in ROOT_explorer PRO.
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORA GE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
Jacker75 said:
Unfortunately mate, the permisson.xml settings didn't help either. You can check the permissions below. I edited in ROOT_explorer PRO.
Click to expand...
Click to collapse
Since I've been struggling with this for a bit, I thought I'd post on how I finally got around it. It turns out that nothing was disabling the RIC, which protects /system from being written. I don't exactly understand how/why, but this was also preventing my modified permissions.xml from taking effect. I have XZ Dual Recovery installed, so all I had to do was enable the init.d functionality, which by default will disable the RIC during boot.
After that, everything's humming along nicely.
EDIT: I was wrong about this (but that above is still totally valid) - in my case, I ended up getting things working with a different SD card. My normal SD card, somehow, stopped being writable. It *acted* like it was writable, but changes were never committed. I couldn't even format it. I RMA'd it to Sandisk.
Backup you files to your PC, format sdcard with any formatter with FAT32 option. Now in your phone with sdcard and with the ROM you want running, see if you need to format it through android on Status Bar then do it. This helped me out when I switched phones (WT19 to C6903).
Related
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
I'm having the same problem How did you delete the fsck_msdos from the bin?
theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.
i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.
SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .
My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!
thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help
yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..
still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors
Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:
It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)
Right, I couldn't find this in a search. I'm not sure if I'm posing this in the right place, so feel free to yell at me!
After installing CM10 I have noticed that The permissions for both internal storage and external storage are always set to 'Read only', this may have been occurring before I used this ROM, but I'm not sure. I am unable to delete, rename or move files. This is VERY frustrating! On my PC I can temporarily change the Permissions of my micro SD card, but only when inserted without using the phone. When plugged into my phone it goes back to bring read only.
Please help!
Thanks in advance!
Sent from my Xperia T using xda app-developers app
I have a similar issue.
I can not delete or move anything from the internal card. It seems the card can not be set as write.
However, i think the issue is kernel related. I am running on the advanced stock kernel and I was going to flash the stock kernel when i had some time to check. I bet of you do that then the issue will be solved.
Please let me know whick kernel you are on now (I presume the kernel that comes with the cm10 download) and if this solves your problem.
It may also be the solution to the screenshot issue that does not let you take screenshots as it says the memeory s in use....
gregbradley said:
I have a similar issue.
I can not delete or move anything from the internal card. It seems the card can not be set as write.
However, i think the issue is kernel related. I am running on the advanced stock kernel and I was going to flash the stock kernel when i had some time to check. I bet of you do that then the issue will be solved.
Please let me know whick kernel you are on now (I presume the kernel that comes with the cm10 download) and if this solves your problem.
It may also be the solution to the screenshot issue that does not let you take screenshots as it says the memeory s in use....
Click to expand...
Click to collapse
I guess that makes sense, if that is the case I'll just have to wait for a fix!
Sent from my Xperia T using xda app-developers app
I have just flashed stock kernel and still got the same problem.
Very weird. I can delte the foursquare folder and some files in varius folders on my internal sd card, but whenever I try to delete any photos pr the camera folder in DCIM it just comes straight back....
and now those files I thought i had deleted are back....
Backing it up and formatting it next...but for some reason its saying it will take 23 hours to copy the files
EDIT
OK, I have backed up and formatted. Went into settings and deleted all content from internal sd card.
Then tried to forat it in recovery, but it failed. When i rebooted it said the internal sd card was in the wrong format so it gave me the option to format it, I did and now it seems to work. It at least allowed me to take a screenshot and save it.
OK, I have backed up and formatted. Went into settings and deleted all content from internal sd card.
Then tried to forat it in recovery, but it failed. When i rebooted it said the internal sd card was in the wrong format so it gave me the option to format it, I did and now it seems to work. It at least allowed me to take a screenshot and save it.
Click to expand...
Click to collapse
Just flashed the stock ftf file from the other thread, problem solved (YAAAAY!!!). But I lost CM10. Oh well.
Sent from my LT30p using xda app-developers app
Hey guys,
I recently rooted my s3 mini to JB 4.1.2 by faria and i was wondering why i cant install any more apps as my ram is used up by all my apps. is there a way to clear/wipe all this data and start from scratch installations or any way i can move this huge game files in android/obb to another location in my sdcard to save space for app installations on my phone memory.
also, i have tried directory bind,app2sd, lind2sd and gl to sd(root) none of them seems to be installing or working for me as i still face the prob with installation of the same app.
kindly help.
SinisterGrey said:
Hey guys,
I recently rooted my s3 mini to JB 4.1.2 by faria and i was wondering why i cant install any more apps as my ram is used up by all my apps. is there a way to clear/wipe all this data and start from scratch installations or any way i can move this huge game files in android/obb to another location in my sdcard to save space for app installations on my phone memory.
also, i have tried directory bind,app2sd, lind2sd and gl to sd(root) none of them seems to be installing or working for me as i still face the prob with installation of the same app.
kindly help.
Click to expand...
Click to collapse
Had this issue before. Try to reflash and reboot the phone.
Sent from my GT-I8190 using xda app-developers app
bOkz said:
Had this issue before. Try to reflash and reboot the phone.
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Tried that, didnt work thanks for your quick reply tho. its been happening even before the 4.1.2 update. even when i had the 4.1.1 XXJL by avicohh rooted. any other suggestions?
Go into recovery maybe, and wipe cache from there, either that or factory reset your phone
Sent from my GT-I8190 using Xparent Blue Tapatalk 2
Drop this script into /data, chmod it to 777, and run it through SManager (thank everybody in this thread, not me).
Sent from Spaceball One.
blackknightavalon said:
Drop this script into /data, chmod it to 777, and run it through SManager (thank everybody in this thread, not me).
Sent from Spaceball One.
Click to expand...
Click to collapse
Everything from ur last post was tried except for the downloading of the busy box. it wont even allow me to download it. it says insufficient storage. i cant proceed from there. i got the rest of it. i ran a chmod to 777 and instlled smanager . any help ?
Had the same error.
Simply wipe dalvik-cache and everything will work fine.
Cheers.
I used titanium backup and wiped dalvik cache. Still no use. Same error. Is there any way I can install busy box in linux.
Sent from my GT-I8190 using xda app-developers app
Remove a LOT of your apps. That should fix the storage problem until you get the script into /data.
you could
SinisterGrey said:
I used titanium backup and wiped dalvik cache. Still no use. Same error. Is there any way I can install busy box in linux.
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
try changing default install location. possible with normal device options, dont remember where. or else use app2sd to change it.
although i have the same error, when trying to install anything on extsdcard (with enough room on it), with faria rom v5.1.
with leatherface v2 i didnt have the problem if i remember correct.
update:
i still have the problem too.
wiped dalvik, factory reset multiple times, cleaned odin files, although faria rom is also using odex?
phone works fine, but i only have 4,5gb max internal (fused internal and sdcard).
and i cant install anything to external. i selected the options *install to: autoselect by android, internal, or external.
i tried it with more then one app, like rom toolbox pro.
i also noticed that chaning it it one app, correctly alters it in another.
i asked this in q&a, and i read what i can searching the whole forum. still i wuold really like to know:
-is 4,5 gb max combined/fused is normal for s3 mini +faria rom)?
-is it normal to have .obb partition completely empty, even having installed multipple apps?
its 402mb, totally free.
And i have other partitions also 402 mb, totally free.
-/cache partitions remains at 14mb, whatever happends, even after changing usage of cache heavier and lighter.
-cant install anything on extsdcard.
-/mnt/sdcard shows in that directory, with root explorer, as linked to sdcard0.
same in root:/sdcard (not sdcard0!) linked to -> sdcard0
but it has no apps in it. and only some folders.
?i dont know if i am correct in assuming that "->" symbol in root explorer means: linked to.
pushquares said:
try changing default install location. possible with normal device options, dont remember where. or else use app2sd to change it.
although i have the same error, when trying to install anything on extsdcard (with enough room on it), with faria rom v5.1.
with leatherface v2 i didnt have the problem if i remember correct.
update:
i still have the problem too.
wiped dalvik, factory reset multiple times, cleaned odin files, although faria rom is also using odex?
phone works fine, but i only have 4,5gb max internal (fused internal and sdcard).
and i cant install anything to external. i selected the options *install to: autoselect by android, internal, or external.
i tried it with more then one app, like rom toolbox pro.
i also noticed that chaning it it one app, correctly alters it in another.
i asked this in q&a, and i read what i can searching the whole forum. still i wuold really like to know:
-is 4,5 gb max combined/fused is normal for s3 mini +faria rom)?
-is it normal to have .obb partition completely empty, even having installed multipple apps?
its 402mb, totally free.
And i have other partitions also 402 mb, totally free.
-/cache partitions remains at 14mb, whatever happends, even after changing usage of cache heavier and lighter.
-cant install anything on extsdcard.
-/mnt/sdcard shows in that directory, with root explorer, as linked to sdcard0.
same in root:/sdcard (not sdcard0!) linked to -> sdcard0
but it has no apps in it. and only some folders.
?i dont know if i am correct in assuming that "->" symbol in root explorer means: linked to.
Click to expand...
Click to collapse
did u used linked to sd?if yes you have to select default instal location to automatic...that solved my problem...the setting in link 2 sd....before this i select install to ext sd card and every time theres error insufficient memory...
thx for yuor reply
nazri5363 said:
did u used linked to sd?if yes you have to select default instal location to automatic...that solved my problem...the setting in link 2 sd....before this i select install to ext sd card and every time theres error insufficient memory...
Click to expand...
Click to collapse
thx for yuor reply.
no that is not what i mean exactly.
i do use link2sd now, to use my extsd 2nd partition. but it gives an error: installl_failed_insufficent storage.
even when i put it on auto.
when pressing create link, i get: i/o error.
what do you have selected to auto move to 2nd partition?
my primary question, has to do with the fused internal+sdcard phone memory (so not extsdcard), of faria firmware.
Phone sees the fused internal as,... internal memory.
and the phone sees my extsdcard as external sdcard.
i presumed the reason for this is to be able to install apps on ext sd too, by default. (so without link2sd or others).
because the problem as i see it is:
now i have less phone storage.
i still cannot install to external sd card.
i would really like to know
- what should be the benefits of this fused memory? why did faria do this?
- beacause now i have less or same memory, and no benefits.
-what i have to change in system mount, or fuse, to get back original non-fused.
- And/Or, how i can enable extsdcard to install to it too.
thanks
Have you tried with an ext4 partition on your external sd, for link2sd? I've read somewhere that it worked.
Otherwise Directorybind do work. I've binded the whole Android folder without any problems at all :good:
hey
SinisterGrey said:
Hey guys,
I recently rooted my s3 mini to JB 4.1.2 by faria and i was wondering why i cant install any more apps as my ram is used up by all my apps. is there a way to clear/wipe all this data and start from scratch installations or any way i can move this huge game files in android/obb to another location in my sdcard to save space for app installations on my phone memory.
also, i have tried directory bind,app2sd, lind2sd and gl to sd(root) none of them seems to be installing or working for me as i still face the prob with installation of the same app.
kindly help.
Click to expand...
Click to collapse
hi,
actually i do also had a the same problem with my cell phone as of yours... so i just wanna know if we had comeout with those problem.... please suggest me a solution too if you had solved those problem.
please do help...
found a solution (maybe?)
I personally had the same problem right after flashing a new rom on my i9100. I read through the script amd it was quite literally just unmounting and mounting the sd card again. I wasn't sure how it could possibly be a simple matter of mounting the sd card but it worked so I'm okay with that.
If you're on 4.1.2 then you can probably manually unmount and mount the sd card by going into system settings, storage and scroll down to sd card for unmount. It'll take a short while to unmount and another to mount again and check for errors. Not sure if you have to do this will ever boot but it beats not ever installing anything, right?
SinisterGrey said:
Hey guys,
I recently rooted my s3 mini to JB 4.1.2 by faria and i was wondering why i cant install any more apps as my ram is used up by all my apps. is there a way to clear/wipe all this data and start from scratch installations or any way i can move this huge game files in android/obb to another location in my sdcard to save space for app installations on my phone memory.
also, i have tried directory bind,app2sd, lind2sd and gl to sd(root) none of them seems to be installing or working for me as i still face the prob with installation of the same app.
kindly help.
Click to expand...
Click to collapse
if u used lucky patcher remove previous patches and stuff like that
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.
Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0
NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.
NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.
How complicated will it be to make this compatible with 4.2.2?
grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines
grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update
SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
pressagny27 said:
SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
Click to expand...
Click to collapse
Does Root Explorer have root access? Also make sure you are using the editor to make changes.
pressagny27 said:
SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
Click to expand...
Click to collapse
Make sure you are doing it in the external storage section.
Glad I found this. I just brought my brand new baby home from the store this afternoon. As soon as I tried to delete some photos from folders on the SD card using Quickpic (photo app), I got the error. I understand the problem, but quite frankly, I don't understand why this issue exists only with the ext card, and not the internal storage. The skeptic/conspiracy-theorist part of me sees it as Google's way of making ext cards so uncomfortable and impractical to use (without root), that more people will start using internal storage exclusively - primping them for the Nexus (no ext SD) devices.
In any case, I didn't want to root on day 1. I'm frustrated enough about this that I'm really just about ready to return it and stick with my faithful Note 2.
Can these permission workarounds be performed without rooting?
ETA - Never mind - I'm able to manipulate the permissions file, but cannot save w/o root.
owlensteed said:
Does Root Explorer have root access? Also make sure you are using the editor to make changes.
Click to expand...
Click to collapse
Thanks I found the editor to make the change. Now all the apps I am downloading are saved to the SD. Is that normal? .