Database Info

[Q] Tiamat 1.4.0, 3g/wifi, sdcard doesnt mount on boot.

i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion

ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night

mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?

still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?

In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom

Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.

@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion

That's odd, mine mounts to external with no issue with 1.4.0

[Q] Phone won't recognize internal storage from SD partition

Hello everyone -- like everyone always says, I did quite a bit of research before posting this, but I can't seem to find the right answer for me.
(I use Cyanogenmod 7 on my HTC Hero (Sprint).)
After using ROM Manager to partition my SD card (it says it successfully partitioned, and the phone boots fine), my phone won't recognize its new internal storage. Like when I go to "manage applications" it only shows my 156 MB, not the 512 MB like I expected from my ROM Manager partition.
The only other person I've found who said the same thing, after quite a bit of searching, said ROM Manager wouldn't work for him for some reason, but Amon_RA did.
So I flashed Amon_RA, partitioned the SD card that way too, and my phone still will not recognize its internal storage. I set the partition w/ Amon_RA to 700+ MB and rebooted but the phone again only says I have 156 MB of internal storage.
I would use ClockworkMod, but the highest level supported for the HTC Hero doesn't have the partition mode. And considering how the other two programs were unable to partition it, I feel like it's more a mistake on my end.
Am I making some dumb mistake on the last step? I don't know of many other options I can be messing up -- in the case of ROM Manager, I simply enter in my specifications (I've tried with no swap and small swap) and it does that fine and boots fine. My phone just doesn't recognize the internal memory.

I forgot to add -- when I go under Cyanogenmod's settings --> application settings --> the "Use internal storage" option is grayed out, saying "This device doesn't have extended internal storage."

Format the sdcard,Delete all of the partitions you have made and try again using clockworkmod (An older version would be nice thats what i use).Then make a partition through the recovery's menu set the swap size to 0 and select ext2/3
You can also try an ext-4 partition

[email protected] said:
Format the sdcard,Delete all of the partitions you have made and try again using clockworkmod (An older version would be nice thats what i use).Then make a partition through the recovery's menu set the swap size to 0 and select ext2/3
You can also try an ext-4 partition
Click to expand...
Click to collapse
Thanks for the reply! Clockworkmod's website says the latest supported version for the HTC Hero (CDMA) is 2.5.0.7 -- do you know of a version that would be safe for me to use that will also support partitioning? Also, I've read that ROM Manager simply uses Clockworkmod to partition SD cards, so would using Clockworkmod itself offer a better solution than my failed ROM Manager efforts?
After reading your post, I used the 2.5.0.7 CWM to format my SD card and Ext, then I flashed and booted Amon_RA again to wipe the partitions. I then used Amon_RA to partition my card (with no swap as you specified). And I used Amon_RA to upgrade my Ext2 to Ext3. After rebooting, my "Use internal storage -- This device doesn't have expanded internal storage" was still grayed out and the internal memory still showed me at 156 MB.
I returned to Clockworkmod to mount /sdcard and /sd-ext (which I had never tried before). Still no new internal memory, same checkbox grayed out.
Am I being a total idiot here? Thanks for any help in advance!

I don't mean to spam this thread, but upon returning to Clockworkmod 2.5.0.7 to reformat the SD card and try again -- I find that it still offers me the option to mount /sdcard and mount /sd-ext.
Does this mean that my previous mounting didn't take? Maybe this is the source of my problem, that my phone won't let me permanently mount the /sdcard or /sd-ext. Any ideas along these lines?
Edit: I went back, formatted and re-installed partitions w/ Amon_RA (no upgrade from Ext2-->Ext3 this time though). After the box was still grayed out and my internal storage still 156 MB, I went back to CWM to mount /sdcard and /sd-ext -- then I simply rebooted CWM, and it STILL said I had the option to mount /sdcard and /sd-ext.

gjs16 said:
Thanks for the reply! Clockworkmod's website says the latest supported version for the HTC Hero (CDMA) is 2.5.0.7 -- do you know of a version that would be safe for me to use that will also support partitioning? Also, I've read that ROM Manager simply uses Clockworkmod to partition SD cards, so would using Clockworkmod itself offer a better solution than my failed ROM Manager efforts?
After reading your post, I used the 2.5.0.7 CWM to format my SD card and Ext, then I flashed and booted Amon_RA again to wipe the partitions. I then used Amon_RA to partition my card (with no swap as you specified). And I used Amon_RA to upgrade my Ext2 to Ext3. After rebooting, my "Use internal storage -- This device doesn't have expanded internal storage" was still grayed out and the internal memory still showed me at 156 MB.
I returned to Clockworkmod to mount /sdcard and /sd-ext (which I had never tried before). Still no new internal memory, same checkbox grayed out.
Am I being a total idiot here? Thanks for any help in advance!
Click to expand...
Click to collapse
the version is ok
i think you should better use windows to remove partitions (with disk management)I dont know if the problem persists then try a different sdcard(maybe a friend's)

Hi,
I'm running Cyan 7 on Legend and having the same problem.
The option for 'expanded internal memory' is still grayed out, no matter what!
I tried using CMW to partition, it only gave me maximum 512 MB while I wanted 1 GB but whatever. That doesn't work.
I tried Ubuntu live CD to format and partition the card into 2 parts, first FAT and second ext3/ext4 -> doesn't work.
The last option is to use an app called S2E from the market. It does the job, but still isn't the official supporting of expanded internal memory from Cyan.
There's a tutorial how to manually partition the card. It mentioned using rm 1 command to remove the partition. However I found that it was impossible because the recovery was running on that partition and thus cannot remove itself.
Any other solution?!
Thanks guys!

For gjs16: mounting partitions in recovery are only in effect when you are in that recovery session; once you boot the phone the mounts are gone.
I was looking into this CM7/Use internal storage thing myself (I'm playing with my old Nexus One) which is how I came upong this thread. I think this option works "out-of-box" only on devices that have some internal flash in addition to an sd-card slot, like the Samsung Galaxy S (2 GB ROM for apps + 8/16 GB internal storage + sd-card slot).
So, this is just a guess but I think you'd have to play with the mount points, perhaps with symlinks, to make it work with a partitioned sd-card, so that CM7 recognizes the fs structure the way it is handled in e.g. SGS.
Edit. This solution worked for my NX1+CM7: http://forum.xda-developers.com/showpost.php?p=18911182&postcount=1784
Just flash this right after flashing CM7 (and gapps if you want them). It mounts the sd-ext to /data so you can have all the space you need for your apps...

[SOLVED] Forced Close of core (or all) apps, Internal SD removed unexpectedly...

Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.

Though i didn't understand a word(being an internee dentist) it will be useful to others.appreciate your efforts!!
Sent from my GT-I9003 using xda app-developers app

This is what i call a complete and useful guide.
This should become a sticky.. now... NOW!

+1 for sticky, superb info.

that would be a really nice sticky
i had the motherboard changed..

Thanks Dipu K for your efforts.
I've tried this solution in my I9003, and I have only a problem: When reboot the phone, /data is copied into de Ext4 partition on SD card, but all aplications have errors because isn´t possible to unmount /data,
Here is the messaje in remnt-log (only a few lines):
Code:
...
3. Make Directory --->
4. Mount new data partition from external SD --->
5. Copy the current files in /data
6. Remove current files in /data
7. Unmount /data
umount: can't umount /data: Device or resource busy
8. Remove dir /data as a safety measure
9. Linking external sd data partition as /data
10. Final Mount status --->
...
What can I do to correct this?
Thanks

bfsa said:
...
What can I do to correct this?
Thanks
Click to expand...
Click to collapse
Finally, I've changed a line on 00remnt, and seems to work properly: busybox umount -l /data 2>> /system/remnt-log

Where can I get make_ext4fs? Sadly the same case has happened to me...

Hi Guys.
I am using alpha 4 from last one month and experience was awesome but from last 1 week I am getting lot of FC for lot of services like exchange service gapps what's up camera and lot more. I am not sure why FC issue started happening from last one week.
History :
I was using CM 10 alpha 1 then alpha 2 then alpha 3 and now on alpha 4.
I really fed up with Force close issue from last one week . I tried reboot but still 80% of apps and services getting FC. Please guide me on this .
Sent from my GT-I9003 using xda app-developers app
Sent from my GT-I9003 using xda app-developers app

hi all, i have a galaxy i9003 with a corrupted or completely dead (not sure) internal memory chip. I have come to this conclusion after 3 days of trying to install custom and stock roms. I can access recovery and download mode but i cant install any ROM, the phone keeps rebooting after the SAMSUNG (whole screen black except SAMSUNG in the middle). All i have is atm this http://forum.xda-developers.com/showthread.php?t=1351056 installed on my phone via ODIN. I dont have knowledge about ADB, can somebody help me out with instructions more?

Pre-requisites:
- Rooted Phone
Click to expand...
Click to collapse
Is there a solution without a rooted phone or can I root it somehow, even if the there is a hardware defect? I got an error with /dev/block/mmcblk1p that rfs can't be written.

I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...

allxx said:
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
Click to expand...
Click to collapse
Please do send us a report, I'd appreciate it very much. Have to deal with a similar situation as well for an old i9003. I've tried to employ the steps mentioned here but could not get it to work as well.

Hi everybody!
Had to remove the internal SD to install everything on the external one by following the mentioned post. Nothing else worked.
http://forum.xda-developers.com/showthread.php?t=1651619

can anyone here recomended me custom rom that already with swap sdcard?

Dipu K said:
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Click to expand...
Click to collapse
Somebody's Samsung Galaxy SL i9003 had wiped the internal SD card by itself! Is this even possible that it just wipes/formats on it's own? Is there any advice? The contacts appear to still be there.

CWM 6.0.1.0 cant backup to local SD?

Hi,
I tried to run a nandroid backup & I am getting this error message:
Unable to find mounted volume: /sdcard
error finding an appropriate backup handler
I then tried to mount the SD card using CWM, that didnt not work but I can mount my external card & perform a backup - but it takes much much longer.
Any ideas why this would be?
I am running the stock ICS rom that is rooted. I did try to upgrade to a JB rom & updated the modem and rpm to a JB one. I dont know if that is the issue.
Any advice would be great.
Thanks,
Rich

Are you using an SDXC card? If so, try formatting it to FAT32 using this guide (I used the GUIFORMAT.EXE program to do it): http://forum.xda-developers.com/showthread.php?t=1773735. I have a 64GB SDXC card in mine and couldn't see it in recovery (or in AOSP ROMs) until I did that.

I am not using a SD card at all anymore. I am sort of stuck. I want to try another rom but I want a nandroid backup before I start messing around so I have somewhere to get back to.
I tried deleting .android secure but that did not help.
Any ideas on what I could try?
When I backup it says:
no /sdcard/.android_secure found skipping backup of applications on external storage.
no /sd-ext found,skipping.
Complete
My backup (which by the way says its in 1970) is only about 30 megs which seems way to small to be a real backup.
Thanks,
Rich

That's the backup. They use blobs that store common info so backups seem small. My stock backup is only 20.82 mb
Sent from my SCH-I535

[Q] Can't mount system partition. Anyone, please help.

I am at my wits end here. I've searched for hours now, without getting any results. My problem is as the title says.
Right now I can't mount the System Partition (it's 0 MB) in the latest TWRP recovery. So I can't install any ROM, and my old one is already wiped.
I used to be on CM 11, with my sd-card partitioned in a way (forgot what way) that support mount2sd method of increasing /data size.
Now I want to upgrade to CM 12 (http://forum.xda-developers.com/htc...dev-cyanogenmod-12-11-19-2012-alpha1-t2945587). Problem is, I lost my sd adapter to connect my micro-sd card to my computer. I was trying other methods of partitioning it. Ended up wiping everything clean, and erasing (all?) partitions on the sd card. I guess I now I've gone and done it. System doesn't wanna mount. All data is backed up, thankfully.
So can anyone please suggest what I should do now?
And on a side note, how to multi-partition the sdcard without PC?