Database Info

paragon problem

Ok, i searched and couldn't find much about my problem with trying to partition my sd card to get ext2. when i try to partition in paragon it tells me this when i click on the sd card:
A new partition cannot be created on this hard disk. Most probably, all primary slots are occupied and there is no extended partition.
I tried reformatting the memory card to see if that would help, but it didnt change anything. So why is my sd card only allowing one primary partition? Is there any way around this problem? I tried on a 1gb card i had laying around and it will let me do it just fine, just not to my 8gb.

It doesnt work with Windows 7 either. And i tried compatibility modes.

You have to go into the advance mode. which is on the bottom of the main blue screen when you open it up. Then you have to delete the partition on your card. After that hit Apply(the green checkmark at top). right click on your sd where its says unallocated space and create the fat32 partition to the size you want and then use the rest of the space to create the ext2 partition no bigger than 2gb. When you have the two partitions hit apply and follow the directions it gives you. It mostly runs on its own at that point but you will need to restart the computer when it asks you to. make sure you do this through an adapter and not usb because it will show an error message after restart.

OK i deleted the partition but it only gives me the option to test the surface or something like that, i've tried the apply button twice now, and it just takes a few seconds and says its done, it says its unallocated now but when i explroe it in paragon i can see all my files still but it doesnt show on the computer anymore. it still has the same name and everything in paragon, but i still can't format it or create a partition, so right now i can't do anything else with it in paragon. in disk management i can see its there though and format it so i tried creating a simple volume on it leaving 100mb open for ext2 but after i do that i can't do anything else with the unallocated space in disk management and paragon still only sees the fat32 part of it, so i deleted the whole partition again and just did fat32. is my sd card just pure **** or what?

DO this
I had the same problem till today until i first formatted sd to single partition ie. fat 32 and then used my phone to partition it using the following steps-
You will need to download the attached file
and dump mke2fs and sdsplit or http://www.mediafire.com/?d9ceg9sbi2g files on your sdcard
There should not be any data except the files you downloaded.
BEFORE WE BEGIN, THIS WILL ERASE YOUR SDCARD, BACKUP BEFORE YOU START!
Step 1 - We're going to Partition your sdcard
open terminal emulator
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# busybox cp -a /sdcard/mke2fs /system/
# busybox cp -a /sdcard/sdsplit /system/
# cd system
# chmod 777 mke2fs
# chmod 777 sdsplit
******************************************
This is important! What size is your sdcard? If it's a 1gb and you want to share 50-50 then move to the next step and use 500m otherwise you have some very simple maths to do. 1gb is 1000mb (not actually but for simplicity...) if your card is 4gb and you want 500mb app space you need to specify 3500m. if it's 8gb and you want 1gb you would specify 7000m take the size you want for apps away from the size of your sdcard, add an m to the end and that is your magic number.
*******************************************
# sh sdsplit -fs MAGICNUMBER --pmke2fs /system/mke2fs
DOnt forget to put m after magic number like write 7000m instead of 7000
If all goes well you now have 2 partitions to your sdcard: you should get a message like this
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 62 7277445+ b Win95 FAT32
/dev/block/mmcblk0p2 63 968 497983 83 Linux
If you have, congrats. my next post in this thread will explain how to move your application, but pat yourself on the back, the hardest bit has been done!!!!!!
If any error come on copying data back to sd like can't mount sd dont worry.
It should be good till creating ext2 partition.
If not please follow go back to the beginning and follow these steps exactly.
Step 2 Mounting you're new linux partition.
Ok dump init.rc and mountd.conf on your sdcard (the windows portion - which is the only part that will appear) I highly recommend at this point you copy a update.zip onto your card just incase everything goes horribly wrong
Open Terminal emulator
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# mkdir /system/sd
# busybox cp -a /sdcard/mountd.conf /system/etc/mountd.conf
# busybox cp -a /sdcard/init.rc /system/init.rc
# reboot
I recommend a nandroid a before partition and wipe after partition.
Now everythings done. Download APPS to sd apps and move your apps.
COngrats.
.There may be other methods but others didn't work for me but this one did.
I also had the same problem exact same. I f****ed my sd with paragon and this saved me.

ok so after windows still wouldnt see the sd card in my computer, i checked it again and even though i assigned it a drive letter it didnt show up so i assigned it one again. so then the computer seen it so i decided to play with paragon again. this time though it let me partition it, idk why it was so goofy before but i got it setup now. i wanted to give 100mb to ext2 but since i have to use the slider i could only give 77 or 155, 77 a little low and 155 to high since the cards about filled as it is, so ill see how 77mb works. thanks for the help

do as said
Make it atleast 500 mb Will work better with it or u have to repartition it.

How to swap SD cards w/ Apps2SD

All props go to Jonnythan who gave the steps in another post. Mods may want to sticky this....
1. As always: Nandroid backup
2. reboot phone
3. adb shell into the phone
4. mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
5. copy sd card to pc
6. Shut off phone and remove old sdcard and insert new sdcard
7. Start in recovery mode and partition new sdcard (fat32, ext2, swap)
8. Enable usb mode, copy data from old sdcard to newly partitioned sdcard
9. reboot and ignore force closings
10. Plug in USB and enable USB mode
From PC ADB shell into phone and type the following (enter after each line):
rm -r /data/app/*
rm -r /data/app-private/*
[chances are those directories are empty already, but you never know]
cp -r /sdcard/backup/app/* /data/app/
cp -r /sdcard/backup/app-private/* /data/app-private
reboot recovery
11. Restore most recent nandroid
12. reboot and enjoy
All thanks again to Jonnythan

Tweaks:
Between 5 and 6, shut off phone. Then start step 7 by specifying to start into recovery mode to partition the card. Then specify that you need to plug in the usb and adb shell for step 10. End step 10 by typing in "reboot recovery" which will reboot you right into the recovery partition.
Thanks for writing it up! Now I don't have to

Ok, I must be doing something wrong here... Does this require a custom ROM or anything? Im on the sprint Hero, stock ROM and I do have root. Everytime I get to step 4, at the cp -r /data/app/* /sdcard/backup/app/ command i get an error. It cant find the directory. Also, if i check the folder properties through Astro or linda file manager, it says 0 files, 0 folders, and also shows that it is not taking up any space. Just as a test to see if I was somehow blocked, I made a nandroid backup and deleted the /data folder, and upon reboot nothing had changed. Still have all of my apps on the phone...

I think the stock ROM doesn't include the cp command.

jonnythan said:
I think the stock ROM doesn't include the cp command.
Click to expand...
Click to collapse
Wait, when i get my sd card I have to do all this? I can't just reformat using the utility and drag and drop everything back into the sd card?

runsoverfrogs said:
Wait, when i get my sd card I have to do all this? I can't just reformat using the utility and drag and drop everything back into the sd card?
Click to expand...
Click to collapse
Not if you're using AppsToSD.
If you're not using A2SD then just make a backup of the old card, unmount it, put the new one in, and copy everything back. If you are using A2SD, the process is more complex.

Cp = Copy. Works on any rom. Like he said since you're on the stock rom, I doubt you're using Apps2SD so no you don't have to do all this.

If only people would actually read the thread title....
"How to swap SD cards w/ Apps2SD."
Don't have Apps2SD? Then this isn't the thread for you.

Exactly what I was thinking.

jonnythan said:
If only people would actually read the thread title....
"How to swap SD cards w/ Apps2SD."
Don't have Apps2SD? Then this isn't the thread for you.
Click to expand...
Click to collapse
I'm using the modaco 1.1, i should've mentioned that. Doesnt that come with Apps2SD built in?

Only if you partitioned your sd card before you flashed.

After step 6, how do you boot into recovery mode to partition the new card if you dont have the recovery image on the new card? Did I miss a step where I added the recovery image to the new card?

chalan30 said:
After step 6, how do you boot into recovery mode to partition the new card if you dont have the recovery image on the new card? Did I miss a step where I added the recovery image to the new card?
Click to expand...
Click to collapse
The recovery partition is installed on the phone itself, not the card.

thanks I dont know why the first time I tried i didn't get back into the recovery screen but the second time I booted into it just fine... oh well thanks for all your hard work!!!

Partitioning links
To partition the new card, you might want to include links to sdparted and this page for people who want to do it manually.

I have a question about how to make the swap. I have moved /data/dalvik-cache/ to my sd card and freed up about 25 meg of space on internal memory. Is there anything I need to do in addition to your instructions or would it be better to just do a wipe and start from scratch. I am using MoCaDo 1.2 Rom using apps2sd and ext3 partition. I have a 16 gig card coming. By moving the cache I now have 143 meg of internal memory with about 65 apps installed counting some of the stock apps. I have removed several of those as well. 34 apps from the market or handmark.

esoteric1311 said:
All props go to Jonnythan who gave the steps in another post. Mods may want to sticky this....
1. As always: Nandroid backup
2. reboot phone
3. adb shell into the phone
4. mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
5. copy sd card to pc
6. Shut off phone and remove old sdcard and insert new sdcard
7. Start in recovery mode and partition new sdcard (fat32, ext2, swap)
8. Enable usb mode, copy data from old sdcard to newly partitioned sdcard
9. reboot and ignore force closings
10. Plug in USB and enable USB mode
From PC ADB shell into phone and type the following (enter after each line):
rm -r /data/app/*
rm -r /data/app-private/*
[chances are those directories are empty already, but you never know]
cp -r /sdcard/backup/app/* /data/app/
cp -r /sdcard/backup/app-private/* /data/app-private
reboot recovery
11. Restore most recent nandroid
12. reboot and enjoy
All thanks again to Jonnythan
Click to expand...
Click to collapse
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.

jmanley69 said:
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.
Click to expand...
Click to collapse
Now I'm confused don't take much.
I tried reading the ext2 partition using ubuntu and loading it temp on my windows 7 PC. It would not let me open that partition so I could not copy anything to it.
I guess the easiest way is to just wipe the phone back to factory, booting to recovery with the new card in and create the fat32-ext2-swap partition, re-flash the MoDaCo or any Rom that uses Apps2Sd and install all my apps again. I am assuming this would work as well.

jmanley69 said:
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.
Click to expand...
Click to collapse
Well, for one thing your method requires a linux machine
But what would you even have symlinks on the SD card for? Symlinks, uids, and attributes on SD card files simply aren't an issue at all for most people.
And truthfully if you are already doing that kind of stuff, you don't need this guide.

jonnythan said:
Well, for one thing your method requires a linux machine
But what would you even have symlinks on the SD card for? Symlinks, uids, and attributes on SD card files simply aren't an issue at all for most people.
And truthfully if you are already doing that kind of stuff, you don't need this guide.
Click to expand...
Click to collapse
As far as Linux... get VMWare player for free and download ubuntu and you're set real fast. Also if you notice what I said about doing a tar instead id using Linux.
As far as symlinks. You're right there "shouldn't" be any... but if you're backing up something why not do it right just in case? We have no idea what future versions of apps2ad sill do. It may happen that a file MUST reside on internal memory and therefore you'd need a symlink.
As far as the rest...
Actualy... each app gets its own user id and mismatches in those can cause problems with some apps. And each file in Linux gets attributes to tell the OS who is allowed ti read/write/execute it. If those get messed up it can cause problems.
So... we have a responsibility aa educators to give the best instructions possible. And not give instructions that ultimately would result in a backup that is missing vital information and would lead to a complete reload to fix the problems.
There are many reasons why Google decided to restrict apps to internal memory and we will never know all of them... this may very well be one of the problems they saw happening.

[Q] SD Card will not mount in Nexus S

Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.

Jacks0n said:
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Click to expand...
Click to collapse
Are you able to go with ADB through the directories?
and yeah, false Section! Q&A would be better

I am having the same issue. I actually just got my phone back from Samsung support (which is real ****ty) because the SD card started having I/O issues.
According to the ticket information they replaced the PCB.
Anyway, I immediately installed Clockwork recovery and transferred the latest Blandroid rom to the root of the SD card. No matter what I do I cannot mount the SD card from the recovery menu or format it from the recovery menu. Mounting USB storage works fine, though.

Hiya I got the same problem
Any salutation yet ?

Yeah. Don't format the internal storage with clockworkmod etc.

I have that issue I cant even open phone now
albundy2010 said:
Yeah. Don't format the internal storage with clockworkmod etc.
Click to expand...
Click to collapse
Hi The phone just stuck in boot logo I can patch iso file from adb though but I cant mount or even wipe devlink cache I dont know what to do ?

Did you ever get this resolved? If so, can you tell me how you did it?

Jouten said:
Did you ever get this resolved? If so, can you tell me how you did it?
Click to expand...
Click to collapse
1.power off...on it back...test it
2.plug your usb cable, boot into recovery..will heard usb sound from your PC, if does not work, try several times plug the usb untill you get usb sound...unplug, then reboot...
3.fresh install ROM...

Yeah, don't mess with the internal memory. I semi-bricked a Droid Incredible one time doing that. It ended up making all the internal partitions FAT. Took me hours to fix it. Be careful. I am afraid to even do it on my crespo4g. When I mount it in gparted running Linux Mint, the internal sd card showed up as not partitioned. I didn't even think about trying to partition it thinking back on the Incredible.

A solution, at least, for flashing/updating roms
Just happened to me, using CM9 after enabling the encryption I can't access the /data /sdcard paths. It would be nice to be able to read them but for me the biggest problem was how to update to the latest CM9 nighty.
In the end I've tricked the clockwork recovery to think the cache partition is the sdcard. I'll post the method in case someone find it useful.
1. Tranfer the update to the cache partition.
- Normally big enough, wipe it from the cwm if there is not enough space
adb push update-cm-9-20120305-NIGHTLY-crespo-signed.zip /cache/update.zip
2. Log into the phone and mount cache to sdcard.
adb shell
mount /dev/block/mtdblock4 /sdcard
3. Go into the cwm option to flash the uploaded package, it wont give you the mount error as we already mounted /sdcard
4. After the update log again and clear the update package, and unmount /sdcard
adb shell
rm /cache/update.zip
umount /sdcard
As long as you don't have to wipe you can continue updating and using your encrypted storage without much trouble

Help, internal storage not showing
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?

Hi i flash locky another CWR AND IT'S FIX LUCKY ME B^)
Sent from my Nexus S using xda app-developers app

getting SD card back
rellivisit said:
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Click to expand...
Click to collapse
I have had no luck using multiple methods to partition sd card with Nexus S. Each time I can view the modified fat32 partition from windows, add files etc, but cannot be recognised from within CWM recovery.
Left me unable to reflash roms etc.
The only thing which has worked for me is to use mini tool for windows and mount usb storage from recovery. Do a refresh from mini tool and it should come up in the list of drives. delete the partition(s) you find there (not your notebook ones of course), and reformat it as fat 32.
CWM>Advanced>Reboot recovery, move over your rom to the sd card, then try to find it in CWM, should now show up :fingers-crossed:

[Q] SD Card will not mount after ext4 part.

Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S (US, T-Mobile, manufactured Dec. '10)
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've tried all the recommended procedures garnered from the first 10 or so pages in google, xda, cyanogem forum, etc:
Restore from nandroid: Not possible, can't mount the SD,
Wipe/Reset: can't wipe /media as sd card won't mount,
partition sd card from within Clockwork: indicates success but does nothing,
format from within clockwork: unable to mount,
repartition using adb: works, parted can see them, I can move files to from, but the phone will not mount,
clearing fstab: no effect,
Fastboot works, but I don't have the proper images. ADB works, as do the installed utilities. Have not tried ODIN as again, I don't have the proper images. Should I attempt to compile my own images from source?
Update: SOLVED, Microsoft Windows. To whom it may concern: I was able to mount the /dev/block/platform/s3c-sdhci.0/by-name/media from two different laptops running OSX and Fedora/Ubuntu then successfully been able to partition them with fat32 as the ClockworkMod (and maybe Cyanogen?) expect with 0 progress. Then I pulled out an old Windows machine, installed the JDK/ADK's +tools and performed the same procedure and that time it worked. I'm uncertain as to what particular quality a 'genuine' Windows formatting provides, but either this phone or the particular software combination I'm running require it. I was able to mount & re-partition the /sdcard in Clockwork, then manually remove rebuild them and upgrade to ext4 using tune2fs as usual. In the interim for work and such, I had to find a surrogate (for the SIM) and could only find and old k750i (which still had a full charge and worked flawlessly all day, btw). Wow phones used to be small.
I think I was missing something about the way ClockworkMod handles fstab, because everytime I would modify it specifically to the specs I passed to parted while creating the partitions with mkpartfs, it would either ignore or overwrite them. So be careful messing with the sd-card, the S's aren't like the One's in the sense that if you screw it (the sd-card) up or it goes bad you can't just take it out and format it in another machine/phone, you have to appeal to ClockworkMod. ODIN $ucks by the way, I found fastboot to be much more effective.

If you format the sd partition ext4, then you should change the fstab too.
from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
to from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard ext4 rw
or from
Code:
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard auto rw
The 2nd last entry there is the file system type.
Likely, this would have solved your problem.
Of course, I don't know, whether the recovery has the vfat type in fstab. You might have to change it there too. On my linux box auto works very well in fstab.
Of course, if you partition your sd partition ext4, you won't be able to use it as usb memory from windows. (At least I am pretty sure you can't, haven't tried)

Well of course I couldn't let it die, I went back and started tinkering again now that I have a way back. I can't change the fstab it seems, whatever I change it to gets over written everytime either Clockwork or the Rom starts. It's weird, I know I'm missing something and I don't know much about CWMod. (had Amon_Ra on the N1, which had the nifty fsupgrade script)
The 2nd last entry there is the file system type.
Likely, this would have solved your problem.
Click to expand...
Click to collapse
I'm quite familiar with unix style fs and fstab, it's the stubbornness I'm not used to. I'm also spoiled by vi and nano. CW has some nice scripts built in as well though.

Vold.fstab missing?

For some reason I don't have the vold.fstab file under system/etc/ . I want to swap sdcard0 and sdcard1 but without vold.fstab I'm not sure if there are other methods. Thanks in advance for swapping suggestions or answers to the missing vold.fstab file. I'm on Lollipop.

yang_k_vue said:
For some reason I don't have the vold.fstab file under system/etc/ . I want to swap sdcard0 and sdcard1 but without vold.fstab I'm not sure if there are other methods. Thanks in advance for swapping suggestions or answers to the missing vold.fstab file. I'm on Lollipop.
Click to expand...
Click to collapse
It's been deprecated since android 4.3 the sdcard is now mounted in fstab which means you would have to unpack the boot.img

I too hav the same prob plz help...
Unjustified Dev said:
It's been deprecated since android 4.3 the sdcard is now mounted in fstab which means you would have to unpack the boot.img
Click to expand...
Click to collapse
Plz help me guys void. Fstab is missing on my device.... What to do

I'm really stuck on this too. I switched to a Sony Z1C recently, but it had a locked bootloader. I can't install Cyanogen. My last phone had Cyanogen and my SDcard is mounted ext4. I really want to mount this card while keeping the ext4 filesystem (it's 128GB. It's also full. All my music...well A-W...ran out of space. It took forever. I'm not reformatting. Don't ask).
I can mount the sdcard manually via the adb shell:
mount -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
And if I look at the directory in the console, everything shows up. But it doesn't show up in any apps! What gives? How do I fix this?

download Link2 Sd on playstore.
djsumdog said:
I'm really stuck on this too. I switched to a Sony Z1C recently, but it had a locked bootloader. I can't install Cyanogen. My last phone had Cyanogen and my SDcard is mounted ext4. I really want to mount this card while keeping the ext4 filesystem (it's 128GB. It's also full. All my music...well A-W...ran out of space. It took forever. I'm not reformatting. Don't ask).
I can mount the sdcard manually via the adb shell:
mount -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
And if I look at the directory in the console, everything shows up. But it doesn't show up in any apps! What gives? How do I fix this?
Click to expand...
Click to collapse
Go into link2 sd on phone and the first time you open it IT WILL ASK YOU 1 time!! pick wisely.. which ext1 (2) (3) you want to run... Solved!!