[Q] Ext4 external SD... no write! - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.

artu72 said:
I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.
Click to expand...
Click to collapse
Same here. Just wanted to post the issue too. It used to work so it must be something new. Problems copying my music to the SD card, can'T delete files and so on.

oneofthekaramosowbrothers said:
Same here. Just wanted to post the issue too. It used to work so it must be something new. Problems copying my music to the SD card, can'T delete files and so on.
Click to expand...
Click to collapse
artu72 said:
I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.

sasank360 said:
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.
Click to expand...
Click to collapse
Thanks for the hint.
Meanwhile I formatted my SD card as FAT32 again. I ran into problems accessing the card from my Linux machine as well. Somehow everything went wrong suddenly on both my phone and PC.

sasank360 said:
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.
Click to expand...
Click to collapse
That app modifies the file /system/etc/permissions/platform.xml
I have already tried editing directly this file and it didn't work. Now I am using FAT32 without problems, but it is stupid that an linux-based operating system does not use natilvely a linux filesystem.

Related

Un-partitioning SD card?

Hi guys,
I couldn't find anything about this (I did try searching before posting this thread, so I hope I am not repeating a common question!).... I wish to unpartition my sd card and just go back to a normal fat32 partition....
So far I have tired windows disk management and Rom Manager, which just allows you to ADD a ext partition with no luck!
Can anyone else guide me how to achieve this?
Regards!
Open Recovery Menu (green) per adb.
Partition SD Card
SWAP=0 MB
EXT=0 MB
Remainder - FAT32
good night
cargobr151 said:
Open Recovery Menu (green) per adb.
Partition SD Card
SWAP=0 MB
EXT=0 MB
Remainder - FAT32
good night
Click to expand...
Click to collapse
:O Thanks, which recovery should I be using? :s
System recover? clockworkmod using the fake flash method? because I don't see the Partition SD Card menu anywhere else and i've tried both!
I know its right in front of me somewhere, I just can't see it, D'oh!
use the one from rooting folder
Bah,
I ended up using GPart live cd to undo it!!
Thanks for the responses guys, hopefully this will help someone else who needs it!
cargobr151 said:
Open Recovery Menu (green) per adb.
Partition SD Card
SWAP=0 MB
EXT=0 MB
Remainder - FAT32
good night
Click to expand...
Click to collapse
Sorry for using your thread, however I don't have that Partition SD Card option on my Desire, when I go into recovery?
jacobtc said:
Sorry for using your thread, however I don't have that Partition SD Card option on my Desire, when I go into recovery?
Click to expand...
Click to collapse
That's fine, it's why I created the thread!
If you just want to partition you can use ROM Manager (but this requires root)
you need the recovery file (entitled 'pushfiles' or something) from the risk-free root package to partition/un-partition the card.
Else, you can use a GPart live CD, which makes it really easy!
Hope that helps buddy...
r5ingh said:
That's fine, it's why I created the thread!
If you just want to partition you can use ROM Manager (but this requires root)
you need the recovery file (entitled 'pushfiles' or something) from the risk-free root package to partition/un-partition the card.
Else, you can use a GPart live CD, which makes it really easy!
Hope that helps buddy...
Click to expand...
Click to collapse
I already partitioned my SD card via GParted, got a 16 gb card partitioned as follows:
14 gb fat32
1 gb ext2
250 gb swap
However in recovery, when I try to mount sd-ext it fails to do so Don't know why...
jacobtc said:
I already partitioned my SD card via GParted, got a 16 gb card partitioned as follows:
14 gb fat32
1 gb ext2
250 gb swap
However in recovery, when I try to mount sd-ext it fails to do so Don't know why...
Click to expand...
Click to collapse
If you're using a2sd+ then you need to change your ext2 partition to ext3, Also, I don't believe that you need a swap partition anymore...
Try that!
r5ingh said:
If you're using a2sd+ then you need to change your ext2 partition to ext3, Also, I don't believe that you need a swap partition anymore...
Try that!
Click to expand...
Click to collapse
Cool, now I can mount the ext partition in recovery! Thanks!
jacobtc said:
I already partitioned my SD card via GParted, got a 16 gb card partitioned as follows:
14 gb fat32
1 gb ext2
250 gb swap
Click to expand...
Click to collapse
Was that a 16gb card or a 265gb?
Sent from my HTC Desire using XDA App
GANJDROID said:
Was that a 16gb card or a 265gb?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
lol, lets give the guy a break.... we all know it was a 256GB Flash card!
Anywhooo, I have another question, so I think i'll hijack my own thread!
Guys, whats the most efficient way to backup/restore and move apps between roms? I've ended up manually re-installing installed apps 2/3 times now, I was going between roms that did/didn't support a2sd. Also, should there be any consideration to any specific backup options available in the various tools?
Thanks in advance!
Hi, my phone got bricked using GPart live to turn my ext 2 into a 3 partition. Everything went fine using the program, turned off Usb storage, went into market and tried to download a program, when it started to install the screen when black.
Now I cant boot with sdcard in, I don't come past the white HTC screen
Without SDcard it starts loading the system but the loading is a never ending loop.
Tried to format SD with fakeflash, dosent help
Tried reflashing my rom with wipe and everything, dosent help
Any ideas?
prove said:
Hi, my phone got bricked using GPart live to turn my ext 2 into a 3 partition. Everything went fine using the program, turned off Usb storage, went into market and tried to download a program, when it started to install the screen when black.
Now I cant boot with sdcard in, I don't come past the white HTC screen
Without SDcard it starts loading the system but the loading is a never ending loop.
Tried to format SD with fakeflash, dosent help
Tried reflashing my rom with wipe and everything, dosent help
Any ideas?
Click to expand...
Click to collapse
I would say, firstly try to get your phone working by wiping it clean and re flashing the rom. Use a different memory card just to get up and running. Then you can concentrate on fixing you card..
Although that seems like a very strange issue, are you sure you formatted your card correctly with GPart? (eg, exactly 512 MB/1024MB?) I'm a n00b myself so I would also wait for some of the more experienced users to offer their input. lol
r5ingh said:
I would say, firstly try to get your phone working by wiping it clean and re flashing the rom. Use a different memory card just to get up and running. Then you can concentrate on fixing you card..
Although that seems like a very strange issue, are you sure you formatted your card correctly with GPart? (eg, exactly 512 MB/1024MB?) I'm a n00b myself so I would also wait for some of the more experienced users to offer their input. lol
Click to expand...
Click to collapse
Solved it by using AM recovery, repair + new partition solved the problem! Gonna reflash 2.0 again since i messed up the wiping somehow and then keep this until the rooted 2.2 is out!

[Q] CWM recovery dooesnt see Restore files after formatting to Fat32 with GParted.

Before installing a Custom ROM on my rooted Desire I am trying to sort out the SDCard as required but am running into problems.
The guides I've read say to change the size of the Fat32 partition on my card to allow an Ext partition. The trouble is in GParted my card just comes up as 'unallocated'.
If I do format it to Fat32 and add an Ext partition (both Primary) once I put my recovery files (and or update.zip for custom ROM) on the card and enter CWM Recovery it doesnt see the files. It just says 'no files found'.
At one point my phone said it couldn't mount SD Card. This even occured when booting phone as usual as no memory card was showing up.
Has anyone else had this problem?
Well I've spent about three hours on this again today still to no avail.
I tried formatting the card in recovery then brought it up in gparted. The card was still showing up as 'unallocated' and when I created the Fat32/Ext partitions the card once again failed to be read by recovery. Although Windows has no problem seeing it.
Eventually my phone and gparted couldnt see or mount the card at all. After running my phone and formatting the card it eventually saw it.
I thought the problem may be because I connected my card to gparted through the phone so tried a card reader but the card reader didn't appear to work. I don't know if the difference I explained is important.
Is it feasible to install a decent custom rom with A2SD with the partition created through recovery? (which gparted also didnt see) as I am having an absolute headache with gparted. Every work around I try just creates a new problem.
Try this: Use Gparted to partition whole card to 1 FAT32 primary partition and then partition it via 4ext recovery into two partitions as required.
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Steveh8204 said:
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Click to expand...
Click to collapse
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Droidzone said:
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Click to expand...
Click to collapse
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Steveh8204 said:
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Click to expand...
Click to collapse
You were the one who mentioned a full wipe! I thought that was what you meant.
Droidzone said:
You were the one who mentioned a full wipe! I thought that was what you meant.
Click to expand...
Click to collapse
The installation instructions mention a full wipe but reading further it does mention a factory reset so its ok. Will let you know how I get on once the kids are in bed.
Right after some messing about I've had some success. I booted back into Android once I'd used GParted and after a while it saw my SD Card ok.
My Windows PC only saw 12.9GB (of a 16GB card), my phone saw the full 14.9gb in Android and GParted saw both partitions.
As I'd just done a factory reset and my PC saw my Phone I transferred the ROM File to my memory card and installed.
As I had downloaded the Extreme edition I followed the Classic install instructions as instructed and rebooted (after booting to android after install).
The LEd flashed green a couple of times as mentioned but then stopped and is now stuck on the htc screen.
Am I right the file I installed (Supernova_2.4.0.0_signed) is the classic version? Should I have downloaded a sepaerate file for the A2SD installer? The instructions don't seem to suggest this.
And most importantly how do I get my phone to work? lol, please help!
Update: Before I installed the ROM it was showing up correctly in GParted and in Windows it was only showing the Fat32 section which I assumed to be correct. After removing the battery I am back to starting up as normal (with the new Custom ROM) but the SD Card will not show up in GParted and will only allow me to use in Windows if I format first which I havent done. Therefore I can only conclude the file system has got lost somewhere which is why the A2SD installer crashed.
I've very happy with the improved ROM but I still don't have extra stoarge space which was the whole point in upgrading.
Any idea where I can go from here?
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Droidzone said:
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Click to expand...
Click to collapse
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Steveh8204 said:
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Click to expand...
Click to collapse
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Steveh8204 said:
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Click to expand...
Click to collapse
Take my advice and move over to 4ext recovery.. It's the best atm.. you'll love it.
Edit:
I saw your post at droid-force.com and have responded to it there/

[Q] Link2SD Read-only filesystem (Solution found)

Hi all
(This problem is fixed, plz go to #4 for more)
I am now using link2sd with CM7.2. Link2SD worked well with rooted stock ROM.
After I unlocked the bootloader and flashed 3rd-party ROMs, link2sd went crazy and this happens on both Arconium and CM7.2.
When I was trying to restore my apps from Titanium backup, link2sd should automatically link the apps to 2nd partition of the sd card (it is an ext3 partition), this works fine at the first few apps. However, when the restore progressed, link2sd would encounter errors with error message telling me "/data/sdext2 ..... " has a read-only file system. This would be "solved" temporarily but re-appears when I tried to restore apps in batch again.
Also, the internal storage sometimes fills up ridiculously. With no new apps in the internal storage, it would be filled up with only <4MB left. No space is freed even if I wiped cache and dalvik-cache in CWM.
Now I formatted the 2nd partition as FAT32 to see whether the problem would appear again.
These just sound very strange to me, it would be grateful if someone can help. Thanks.
With cm7 use "s2e"
Sent from my MT15i using Tapatalk
taaviu said:
With cm7 use "s2e"
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Thanks for your information, does that mean I have to switch from link2sd to s2e? Is it okay to use link2sd with FAT32 partition? thanks
hi all, i just found a possible solution to this problem.
Just insert the SD card to computer and boot into GParted, because Windows only recognize the first partition, but Linux recognizes all (how crappy Windows is LOL)
And then check the 2nd partition, GParted will check and fix all the errors on the partition. After that insert the SD card back to the phone and this problem would not appear again.
Probably it is caused by a corrupted filesystem, maybe due to frequent IO on the partition, or unclean booting and shutdown.
Tried and tested
heihei_ivan said:
hi all, i just found a possible solution to this problem.
Just insert the SD card to computer and boot into GParted, because Windows only recognize the first partition, but Linux recognizes all (how crappy Windows is LOL)
And then check the 2nd partition, GParted will check and fix all the errors on the partition. After that insert the SD card back to the phone and this problem would not appear again.
Probably it is caused by a corrupted filesystem, maybe due to frequent IO on the partition, or unclean booting and shutdown.
Click to expand...
Click to collapse
Hi, I tried your method as I'm having the same problem
but after about a minute of linking the internal applications that I normally have on my sd-ext partition, the same problem reappears.
I used the "Check" option on GParted to check and fix errors on my sd-card and it did it without a problem, however it did mess up on the first running of the program...
any ideas? I hate how Link2SD just dies now and then, it's absolutely vital for my phone!
Link2sd Read Only Error
I had this error from last 2 days, i searched a lot, but it solves only by updating super user.... now its working.
heihei_ivan said:
hi all, i just found a possible solution to this problem.
Just insert the SD card to computer and boot into GParted, because Windows only recognize the first partition, but Linux recognizes all (how crappy Windows is LOL)
And then check the 2nd partition, GParted will check and fix all the errors on the partition. After that insert the SD card back to the phone and this problem would not appear again.
Probably it is caused by a corrupted filesystem, maybe due to frequent IO on the partition, or unclean booting and shutdown.
Click to expand...
Click to collapse
Bro, I've same problem with "read only" 2nd partition for my Galaxy Mini, and I want to fix it.
But can you tell me how to use Gparted? FYI I use windows 7 for my cpu. Should I have to use Gparted via CD?
Hi,
Every time the phone boots have a message "mount warning" and i must quick reboot the phone in order to see my linked apps, which could be the cause?
Thanks
Is there a solution for this in the meantime? Since Lineage OS 17.1 I have exactly the same problem, even though it is a new SD card.
Saiwaa said:
Is there a solution for this in the meantime? Since Lineage OS 17.1 I have exactly the same problem, even though it is a new SD card.
Click to expand...
Click to collapse
Solved "read-only" problem.
Lineage 17.1 on galaxy mega 6.3 with superuser update. In Magisk manager do install and restart. After a link2SD message come, and now choose quick reboot.

Dead Internal SD Solution Galaxy S

Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
I wont waste your time listing the hundreds of methods I tried or posts I read, but in the end all things pointed to a dead internal SD.
I should be able to run the OS off an external SD... shouldn't I? The answer is Yes!
Many hours were spent on this stage and for about a week I had a working pone with OS running on External SD, but no access to the camera or anything which required an external SD.
I now have a perfectly working phone, using a 16gb External SD to run the OS and remaining space on it recognised as the external SD.
I can't promise this will work for everyone but here is the last of WAY TO MANY methods I used which completely solved this problem for me.
Let me know if this works for you & GOOD LUCK!
Step 1:
Your phone must be rooted!
The best, easiest and only way I was able to do it is with the following guide, big thank you to the person who put it up. As my Internal SD was dead! my external SD was to be my new internal SD...so the standard add to zip method for rooting on external SD... would obviously not work for me! yes I worded that perfectly!
BIG IMPORTANT NOTE IN CAPITAL LETTERS! - Make sure you have your external SD inserted during the below process!
http://forum.xda-developers.com/showthread.php?t=1852546
NOW! You should have your phone booting as it used to back in the good old days! However.....some of you wont...if this is the case please follow Step 1B.
Step 1B:
If the above did not work for you then you need a way to connect your Micro SD to your PC (I did this using a USB adaptor).
1. Download and install EaseUS partition master
2. Insert Micro SD in PC
3. EaseUS partition master
4. Wipe all partitions/data.
5. Create EXT4 partition approx 2gb
6. Create FAT32 partition with remaining space.
7. Remove battery from phone
8. Insert SD, Battery back in.
9. Turn on, you should have your phone booting as it used to back in the good old days!
IF NOT THEN.....Start with Step 1B then do Step1 then if all looking as it should move to step 2. If not...sorry...I have failed you!
Step 2:
You phone should now have booted like the good old days....but if you go into SD/Storage on android OS, you will notice it does not recognise the remaining space on the External SD as an external SD...it must be very confusing for the green robot!
So next steps as follows!
1. Install script manager app and mount r/w app from Google Play (market)
2. Use mount r/w to Mount the system partition in r/w mode.
3. Browse using script manager app as root (change setting in config).
4. Go to /system/etc folder and change file permission for vold.fstab to rwxrwxrwx (This means tick all the 9 boxes on the left not the 3 on the right.....such a technical explanation)
5. Then edit the vold.fstab file as text and change the following
Change:
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0
to
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Change:
s3c-sdhci.0
to
s3c-sdhci.2
Change:
mmc0
to
mmc2
Save the file and reboot the phone!
If all has gone well then your sdcard partition will be mounted and old faithful is ready to ride once again!
I hope this worked for you, if it didn't...gutted and I guess you have moved onto the next post...good hunting!
Please note this solution was created from a pile of posts I trawled through to get a solution. The above vold.fstab solution was taken from the following post. Unfortunately this posts overall solution didn't work for me, but I would not have been able to mount remaining External SD Space as well...you know THE EXTERNAL SD! without his post, which is the best part!
http://forum.xda-developers.com/show....php?t=1193010
Thanks for this, I'm going to try this again. Finally a good explanation of what to do.
I posted a thread yesterday with, I think, the same problem. Could you take a look and see if I have the same problem as you did?
Thread: http://forum.xda-developers.com/showthread.php?t=1905284
EDIT
Does the EXT4 partition has to be the first and the FAT32 the second?
If so, isn't it a problem that windows can't read the FAT32 partition. In case I need to drop files on it? (because it only reads the first)
EDIT
Thanks in advance!
Good Luck!
Pindagus said:
Thanks for this, I'm going to try this again. Finally a good explanation of what to do.
I posted a thread yesterday with, I think, the same problem. Could you take a look and see if I have the same problem as you did?
Thread: http://forum.xda-developers.com/showthread.php?t=1905284
EDIT
Does the EXT4 partition has to be the first and the FAT32 the second?
If so, isn't it a problem that windows can't read the FAT32 partition. In case I need to drop files on it? (because it only reads the first)
EDIT
Thanks in advance!
Click to expand...
Click to collapse
Does the EXT4 partition has to be the first and the FAT32 the second?
do EXT4 first, make both as primary partitions (NOT logical..probably obvious but just spelling it out )
If so, isn't it a problem that windows can't read the FAT32 partition. In case I need to drop files on it? (because it only reads the first)
with the method I used above you shouldnt need to drop any files on, let me know.
Quite similar except I couldnt acces my internal SD at all, let me know how you go!
Same issue ?
Hi,
My friend has Galaxy S, And he has similar issue. For him phone boots till splash screen and then reboots on its own.
He was able to go to recovery mode/wipe data/cache partitions etc. He was also able to go to download mode.
But he didn't try flashing custom ROM or anything instead he gave it to Samsung service center where they told him that his Motherboard has gone for toss and need to replace complete MOBO which would cost $110 (6K INR).
Though i didnt get time to check his cell myself i guess it is because of internal SD card has gone. Because he was telling in recovery page it was showing some mount error (not sure if it was internal or external SD card). If that is the case i can try this method to run OS from external SD card .
I have two questions here.
1] If MOBO was gone (like samsung service guy told) would it still boot at first place ? or even if it boots would it go to recovery or download mode ?
2] Where exactly Recovery image is stored ? internal SD or in some other memory ?
Thanks
Exactly the same issue! MOBO i doubt it!
happy20b said:
Hi,
My friend has Galaxy S, And he has similar issue. For him phone boots till splash screen and then reboots on its own.
He was able to go to recovery mode/wipe data/cache partitions etc. He was also able to go to download mode.
But he didn't try flashing custom ROM or anything instead he gave it to Samsung service center where they told him that his Motherboard has gone for toss and need to replace complete MOBO which would cost $110 (6K INR).
Though i didnt get time to check his cell myself i guess it is because of internal SD card has gone. Because he was telling in recovery page it was showing some mount error (not sure if it was internal or external SD card). If that is the case i can try this method to run OS from external SD card .
I have two questions here.
1] If MOBO was gone (like samsung service guy told) would it still boot at first place ? or even if it boots would it go to recovery or download mode ?
2] Where exactly Recovery image is stored ? internal SD or in some other memory ?
Thanks
Click to expand...
Click to collapse
That is exactly the same situation my phone was in, exactly.
I highly doubt there was any issue with the motherboard, as I understand it the internal SD is hard wired on the MOBO which is probably why they said to replace it as one piece.
1] If MOBO was gone (like samsung service guy told) would it still boot at first place ? or even if it boots would it go to recovery or download mode ?
As above! As i understand it it would not go into either mode if MOBO was fried, doubt you would get any response at all.
2] Where exactly Recovery image is stored ? internal SD or in some other memory ?
Il get back to you on this one
Same issue ?
--- deleted double post ------
Dead Internal SD Solution Galaxy S - HELP
reganstott,
First of all thank you for the hope.
1 - Your step 1, the link provided doesn't work (http://forum.xda-developers.com/show....php?t=1852546)
is there another link available?
In what step I ACTUALLY install the OS on the EXTERNAL SD, just asking to get the whole pic.
Is it possible, in order to just test it, use a 2GB SD card?
thanks
It seems to work, I only have to do a mount switch now.
The only thing is; I had the EXT4 (2GB) as first partition and FAT32 (5GB) as second, but now if I connect to my PC it sees only 2GB storage of FAT32. So I guess I have to switch them?
I'm going to try again and then do the mount switch.
EDIT
Confirmed this is working, running on CyanogenMod 9.1.0 right now.
I thank you really reaally much! I almost gave up, but luckily I saw your post in time.
Thanks!
help please
Hello,
I guess I have the same problem and wanted to know if you have to CORRECT links to the files
needed to do this.
thanks
p.s.
maybe a short EXTRA explanation on how you did it may help.
DannyBrazil said:
Hello,
I guess I have the same problem and wanted to know if you have to CORRECT links to the files
needed to do this.
thanks
p.s.
maybe a short EXTRA explanation on how you did it may help.
Click to expand...
Click to collapse
Just follow the steps, in case it is still unclear here exactly what I did;
Needed
microSDcard
Step 1
1. Wipe your external SD card and create 2 partitions; first one FAT32, second one EXT4 (about 2GB). Both has to be primary (not local)
I did this with Minitool Partition Wizard
2. Insert the SD card into your phone and install firmware from point 2: http://forum.xda-developers.com/showthread.php?t=1852546
3. Install CF-Root link is also here: http://forum.xda-developers.com/showthread.php?t=1852546
4. Check if phone boots right (this goes slower than normal, so just wait)
5. If phone works right do Step 2 from first post
Step 2
My phone happened to have no Play Store after the root. If so, follow this step 2
1. Install this zip: will upload this file in a minute -> I can't post outside links yet -.-
This will to the mount swap (for firmware above)
OR
2. Install a root explorer APK through ADB and edit vold.fstab like Step 2 in first post
Now your phone has to be working. If not, check the steps and try again.
Otherwise your problem is others than ours.
p.s.
If you do flash another ROM don't forget to swap mounts! (edit /system/etc/vold.fstab in zip file from ROM)
Currently on Slimbean 2.5
Thank you
Hello,
First I want to thank you for the effort and time. I believe that my SGS has a very similar problem.
I try to flash it with many ROMS, uninstall the apps, but after reboot they always come back and I get TONS os FORCE CLOSES.
Can't Install new apps, so I guess the internal SD is the problem.
The thing is that my SGS is a Brazilian model I9000b (with TV) just wanted to make sure if it changes anything from the
instructions you gave me.
(I don't need a working TV, so I don't care for another firmware)
thanks
---------- Post added at 09:49 AM ---------- Previous post was at 09:31 AM ----------
Just a question:
1 - I created 2 partitions on the EXTERNAL SD
2 - inserted the EXTERNAL SD into phone.
3 - on ODIN, how he knows to install the new firmware ON THE EXTERNAL SD rather that on the INTERNAL SD??
---------- Post added at 10:15 AM ---------- Previous post was at 09:49 AM ----------
when I try to apply the new ZIP from sd it doesn't recofnize the SD
actually it never did.
it is showing me the INTERNAL SD with all the folder of the apps I had, which I can't delete anymore.
3 - on ODIN, how he knows to install the new firmware ON THE EXTERNAL SD rather that on the INTERNAL SD??
I don't know how it works, but it does work.
when I try to apply the new ZIP from sd it doesn't recofnize the SD
Which ZIP do you mean? You only have to flash firmware and root through ODIN.
Great
Pindagus said:
It seems to work, I only have to do a mount switch now.
The only thing is; I had the EXT4 (2GB) as first partition and FAT32 (5GB) as second, but now if I connect to my PC it sees only 2GB storage of FAT32. So I guess I have to switch them?
I'm going to try again and then do the mount switch.
EDIT
Confirmed this is working, running on CyanogenMod 9.1.0 right now.
I thank you really reaally much! I almost gave up, but luckily I saw your post in time.
Thanks!
Click to expand...
Click to collapse
Not a problem, glad it worked for you too. Not sure why the step 1 link isn't working anymore. Anyone else reading this.... I will post soon with the method for step one rooting exercise. (to put a up a brief its just using the odin way of rooting to avoid the issue of not being able to use external sd add zip method)
Info
Hey there,
2 important questions:
1 - My SGS is the Brazilian model I9000B, does it make any difference?
2 - Can I use a 2GB EXTERNAL SD, or it MUST be more than this?
3 - Do I need to have any knowledge in LINUX?
thanks again.,
I have managed to get it all done, modded .fstab file before applying new rom but after applying the new rom and booting in, I get encryption unsuccessful. (CM9.1.0)
Is this unfortunately the end of what can be done?
Nope..
KiDCady said:
I have managed to get it all done, modded .fstab file before applying new rom but after applying the new rom and booting in, I get encryption unsuccessful. (CM9.1.0)
Is this unfortunately the end of what can be done?
Click to expand...
Click to collapse
If you use this method and then do a new rom...u have to do the whole process again...each time you put a new rom on you will need to change .fstab etc..
reganstott said:
If you use this method and then do a new rom...u have to do the whole process again...each time you put a new rom on you will need to change .fstab etc..
Click to expand...
Click to collapse
Thanks for getting back to me. I modded the rom to have the fstab use the correct settings but I still get the issue. I've tried with Darky and with CM.
Seems I will need to stay with jw4 and the app crashes until I get a new phone at the end of the year.
Pindagus said:
3 - on ODIN, how he knows to install the new firmware ON THE EXTERNAL SD rather that on the INTERNAL SD??
I don't know how it works, but it does work.
when I try to apply the new ZIP from sd it doesn't recofnize the SD
Which ZIP do you mean? You only have to flash firmware and root through ODIN.
Click to expand...
Click to collapse
Hello,
Does my phone have a dead Internal Storage ?
after i install any (stock) rom by odin , it shows up in recovery 3e:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
E:format_volume: rfs format failed on /dev/block/mmcblk0pk2
and i try to flash new rom in External SDcard following http://forum.xda-developers.com/showthread.php?t=1852546,
odin don't know what i want , it puts new rom in internal sd which was broken so above error display.
I have formated my external sd by MiniTool Partition Wizard Home Edition with 2gb ext4 and 5.592 gb fat32.
but same errors.
What should i do to flash rom in external sd.
sorry about my English , i'm not native speaker.
reganstott said:
If you use this method and then do a new rom...u have to do the whole process again...each time you put a new rom on you will need to change .fstab etc..
Click to expand...
Click to collapse
Do you mean that after the new rom is applied and I get encryption unsuccessful, i need to access the root of the phone somehow (presumably android commander or something similar) and change the fstab that way while it is powered on and stuck on the error message?
Or do I need to modify the zip file I want to apply before I apply it and then deploy it? If so, then I have already done this with no success.
Also, is there a way to ensure that messages and contacts don't get lost everytime the phone loses power?
vietanhnc said:
Hello,
Does my phone have a dead Internal Storage ?
after i install any (stock) rom by odin , it shows up in recovery 3e:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
E:format_volume: rfs format failed on /dev/block/mmcblk0pk2
and i try to flash new rom in External SDcard following http://forum.xda-developers.com/showthread.php?t=1852546,
odin don't know what i want , it puts new rom in internal sd which was broken so above error display.
I have formated my external sd by MiniTool Partition Wizard Home Edition with 2gb ext4 and 5.592 gb fat32.
but same errors.
What should i do to flash rom in external sd.
sorry about my English , i'm not native speaker.
Click to expand...
Click to collapse
Yes, means your internal storage is dead. My advice - if you can get it replaced thru warranty do that, otherwise buy one on Ebay with broken screen (or/and any other parts) but with working motherboard and swap it. Last option - sell your phone for parts and get a new one...

TWRP won't recognize external SD card

Right now there is no ROM installed on my phone because I just wiped my phone, but when I went to install a new ROM, it doesn't seem to recognize my external SD card. I tried 2 SD cards and neither of them work, but they work on my other phone. How can I fix this issue? I went to mount and it says "E: Unable to mount '/external_sd'.
Update twrp if available, if not try to reflash it and if it still doesn't work then try cwm
Sent from my SGH-M919 using Tapatalk
Thanks for the reply. Which method of installation would be the best? Odin? I only have access to recovery as far as I know.
Yes Odin
Sent from my SGH-M919 using Tapatalk
The latest TWRP doesn't seem to recognize my SD card either. Also both of them are saying that my device is not rooted and it asks if I want to fix root. I'm trying CWM now but it isn't finding anything either.
Edit: CWM says my device isn't rooted as well.
Edit 2: Flashed http://www.androidfilehost.com/?fid=23212708291679687 with Odin and when the phone boots up, it's stuck on the Samsung logo. Any thoughts?
Factory reset. Incompatible data probably causing boot hang.
This will wipe apps and data.
Thanks for the help everyone. I flashed back to stock and re-rooted. However it still won't read anything from the external SD. Does this mean the SD reader is broken?
Can you plug it into the computer? Does it see it there? If so what is the file system type? Can you format it?
DocHoliday77 said:
Can you plug it into the computer? Does it see it there? If so what is the file system type? Can you format it?
Click to expand...
Click to collapse
Yep, the computer only sees the phone's harddrive, not the SD card. On my other phone, the SD card is working fine.
No, I mean plug the card into the computer. Not the phone. But if another device uses it ok, then you msy just need to reformat using the computer.
DocHoliday77 said:
No, I mean plug the card into the computer. Not the phone. But if another device uses it ok, then you msy just need to reformat using the computer.
Click to expand...
Click to collapse
Reformat the card? I will try that. But I have two SD cards and neither work on my S3, and both work on my S4.
That tells me the cards are ok and something is probably wrong with the device then. If you format one card to fat32 and it still can't read it, its probably hardware.
@bjornturoque Here was my problem. Exactly like yours. I am BL unlocked, Rooted, TWRP 2.8.7. I am having a problem with the ext sd card not being read in TWRP. I have had ver 2.8.5 / 2.8.7 / 3.0.2 of TWRP and none of them will read the card. I have tried formatting the card with my Note4, GS 5, Tab S, and my PC using SD Card Formatter. Still getting the same result.
Here is what I did to fix it.
Install Xposed, Download Wanam Xposed, activate the module, open and go to security hacks and check the box for SDcard RW permission, then reboot.
I just did this to mine and it fixed my problem. Hope it works for ya.
Format SD-card via Windows (FAT32/Default Allocation).
stajam said:
...Here is what I did to fix it.
Install Xposed, Download Wanam Xposed, activate the module, open and go to security hacks and check the box for SDcard RW permission, then reboot.
I just did this to mine and it fixed my problem. Hope it works for ya.
Click to expand...
Click to collapse
No, doesn't work
I have a 128 GB SD with exFAT, it worked without problems in TWRP 3.0.2 recovery under CM12.1
Now I am on CM13 and beside the bluddy permission google-bug it works in the system but not anymore in TWRP 3.0.2 recovery.
I tried to fix the permissions to write to external sd (this 128 GB sd) by adding stuff to the /data/system/packages.xml file, see this post.
But I didn't change the wrong thing I am pretty sure and doubt that this is related, as TWRP comes without using this file, I guess.
I flashed 3.0.2 again with Odin, no change.
Fact is, that I installed CM13 with another SD-card, a 64 GB FAT32, not this one. Maybe it never worked under CM13. But anyway, what has TWRP to do with CM13 and its permissions? TWRP is previous to any CM system, which is not running at TWRP times.
What could that be?
I flashed now CWRM v6.0.4.7 (ClockworkMod Recovery) but the problem persists:
E: Can't mount /storage/sdcard1
Error mounting /storage/sdcard1
Click to expand...
Click to collapse
What is it? The sdcard is working flawlessly in the running system and another FAT32 sdcard works in TWRP. What do I miss here?
Is it that TWRP and CWM doesn't know exFAT?
I think to be quite sure that this was working, I have exFAT since a while now.
Deleted.

Categories

Resources