Related
Hi all--
I'm sorry in advance for the confusion I might have. I'm an extreme noob when it comes to this platform, and I'm not that great when it comes to Windows either...
Basically I was surprised to see that the external SD Card is used so much by CGM7 and is required for so much. For instance, all downloads HAVE to go to the external card. In addition: I don't know if this has anything to do with operating system, but all saved documents from basically any productivity program seems to save here by default as well.
So here are my questions:
Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used... Does the default location for app installation handle this?
What exactly uses the external card by default?
Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Thanks for your help and suggestions. I am using a gTablet, and I couldn't find a more appropriate forum for this question...
scyld said:
So here are my questions:
1. Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used.
Click to expand...
Click to collapse
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
2. What exactly uses the external card by default?
Click to expand...
Click to collapse
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
3. Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
Click to expand...
Click to collapse
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
4. I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Click to expand...
Click to collapse
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
rajeevvp said:
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
Click to expand...
Click to collapse
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
Click to expand...
Click to collapse
Thanks.
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
Click to expand...
Click to collapse
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this. However, I'm a little worried that it has Super User status, making me worried that I might accidentally do something bad with my clumsy fingers. But I suppose that's why I have CWM backing up my tablet.
Speaking of CWM...
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
Click to expand...
Click to collapse
Interesting, thanks. I unfortunately do not remember which version of CWM I use, but I think it is not this one. I should check it out.
scyld said:
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Click to expand...
Click to collapse
Here's my /system/etc/vold.fstab in its entirely. With this, my tablet uses the internal SD card as the default for storage.
Code:
## Vold 2.0 NVIDIA Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
#dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc0 /devices/platform/tegra-sdhci.3/mmc_host/mmc1
# dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
# dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this.
Click to expand...
Click to collapse
Ah, OK. The reason for the difference is due to the way the move is actually implemented in File Manager and Root Explorer.
I had an idea about why File Manager couldn't move files across filesystems, and to confirm my suspicion I attached strace to a running File Manager:
Code:
$ su
# strace -e rename -p `pidof org.openintents.filemanager`
Process 28466 attached - interrupt to quit
[I]lots of irrelevant output omitted[/I]
rename("/mnt/sdcard/Kernel/Pershoot/lib-2632.40_gb.tar.gz", "/data/local/tmp/lib-2632.40_gb.tar.gz") = -1 EXDEV (Cross-device link)
[I]more irrelevant output omitted[/I]
File Manager calls the rename() system call to move the lib-2632.40_gb.tar.gz file, which, as the spec says, will fail in this case. The program is then supposed to do the move the old-fashioned way if rename() returns an EXDEV error: copy file1 to file2 by reading bytes from file1 and writing bytes into file2; then delete file1 if the copy is successful.
But, File Manager doesn't perform this very basic fallback step. It throws up its hands at the first error and spits out the error message you got. And, it's not just File Manager. The system mv command (if you have it) in /system/bin also exhibits the same dumb behaviour. The busybox mv is more robust. (You should actually report this as a bug to the File Manager people.)
Which brings us to Root Explorer. I got curious about it after the experiment with File Manager. RE handles cross-device moves just fine. What's more, it also moves entire directory trees across devices. Having written directory tree-moving programs before, I know that this is a non-trivial bit of programming. So, I ran strace on Root Explorer to see how it handled things, and the result made me laugh.
Code:
$ su
# strace -f -e execve `pidof com.speedsoftware.rootexplorer`
Process 3602 attached with 12 threads - interrupt to quit
[I]lots of irrelevant output omitted[/I]
10893 execve("/system/xbin/busybox", ["busybox"..., "cp"..., "-pr"..., "/sdcard/Kernel/Pershoot/lib-2632"..., "/data/local/tmp/lib-2632.40_gb.t"...], [/* 19 vars */] <unfinished ...>
10893 <... execve resumed> ) = 0
10914 execve("/system/xbin/rm", ["rm"..., "-r"..., "/sdcard/Kernel/Pershoot/lib-2632"...], [/* 19 vars */] <unfinished ...>
10914 <... execve resumed> ) = 0
[I]more irrelevant output omitted[/I]
Root Explorer is also taking the easy way out: It's actually using busybox to do (almost) all of its work.
I suspected this when I compiled a new version of busybox a few days ago to test out a new compiler toolchain. I moved the newly compiled busybox into /system/xbin without properly testing it first, and discovered that most of the commands died with segfault errors.
I re-uploaded the working version of busybox back onto the tablet in /mnt/sdcard/download, and then went into Root Explorer to move this busybox into /system/xbin, and RE started force closing on every action. Once I had managed to replace busybox through other means, RE started working fine again. At that time, I didn't look at the issue too closely--I thought it was just another example of the random lossage that Android exhibits from time to time. Now I know why.
I have been running HyDrOG3N-ICS for a couple of days now and almost everything is working very well.
I really like this rom.
I have just 1 problem.
As per the quote below, the changelog mentions in 1.7 that emmc is now mounted as /sdcard/external_sd...
I cannot get this to work. I have tried everything.
I have even reverted to the stock 2.3.6 Sumsung ROM, doing a hard reset, formatting my SDCard and External SD Card, then rooting and installing this rom with all the settings as default.
I have done further research and created a script to mount it manually:
Code:
mount -o bind /mnt/emmc /mnt/sdcard/external_sd
This is working well, but is a manual process.
I also tried putting a script in /system/etc/init.d/ folder, but still no luck getting it done at boot.
I have tried various other work arounds...
Does this work for anybody else on this rom?
If so, any ideas what I am actually missing?
Thanks
Jakez
Changelog :
25:
_CodeWorkx 3.0.25 Kernel for now.
_Open Source libs
_Merged AOKP Changes
23:
_Recovery Backup Fixed.
_Lulzactive as default
_Vr I/O
_Merged AOKP Changes.
_Voltage Interface on kernel. Use voltage control.
22:
_New Kernel By Netchip. More Governors, I/O Schedulers, TouchScreen FIX.
_AOKP Merged stuff. As always.
20:
_MTP MTP MTP MTP MMMTTTTPPPP !!!
_AOKP Full Update. So many htings I can't write a proper changelog.
1.7
_Emmc Mounted as /sdcard/external_sd (Yep )
_New Lockscreen. AOSP (Gingerbread one !! Stock still there too.)
_Weather text color is modable now.
_Some fixes.
Click to expand...
Click to collapse
By default, Windows will only mount the first listed partition on any Removable Disk. This is unfortunate for CM7 SD version users since the 4th partition of the SD card is the one used to store user data, which frequently need to be viewed and edited.
Purpose:
This tutorial will show you how to modify a Local Disk driver in order for Windows to recognize all the partitions of your SD card.
So, just a couple of things before we start:
- This process is NOT limited to work for just SD cards, you can do this for USB flash drives as well.
- The drivers that we will be modifying are compatible with Windows XP and Windows 7 32-bit. They are NOT compatible with Windows 7 64-bit. If you run 64-bit, you're out of luck. However, if you needed to, you could run Windows in XP mode or use a different OS in a virtual machine.
Procedure:
1.) Download the USB_LocalDisk.zip file attached to this post. Or download it from here: http://www.etcwiki.org/wiki/Cfadisk_usb_driver . Or if that link stops working, try doing a google search of xpfiledvr1224_320.zip. They are the same drivers.
2.) Extract the USB_LocalDisk folder to your desktop.
3.) Insert the SD card (via MMC reader or USB adapter) that you want to be able to view, and open your computer's Device Manager. Click the dropdown arrow of the Disk drives category and find the entry for your SD card. Please note that this name will probably be different for each person based on the SD card and card reader/adapter you're using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.) Right click and select Properties. Choose the Details tab, and select Device Instance Path from the dropdown box. Copy that Value that appears in the box. Again, this value will most likely differ from the one in the screenshot.
5.) Go back to your desktop and open the USB_LocalDisk folder. Open the .inf file called "cfadisk" with Notepad or your favorite Text Editor.
6.) Navigate to the 26th line in the file. Highlight "device_instance_id_goes_here"
Paste your Value from before. Save the text file.
7.) Go back to the Device Manager, right click your SD card, and choose Update Driver Software -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Have Disk -> Browse. From here, go to your desktop or wherever you saved the driver files and open the cfadisk file. Click Okay.
8.) Click next. It might give you a message about driver compatibility, but it's fine, just hit yes. At this point, it will begin installing the drivers. Once again, you might be informed that the driver isn't signed. Don't worry about it, just choose Install this driver anyway. Now it should finish the installation.
9.) If all goes well, your SD card partitions should now be mounted separately in the Local Disk section of My Computer.
10.) You might want to consider renaming the different partitions to help you remember which is which. Again, this isn't necessary, but if you have a bunch of disks and get down to about drive letter P: and Q:, things start to get a little confusing.
If anyone has any suggestions on how to make this tutorial more helpful, let me know.
Lastly, I did not create these drivers or discover this process. I took my information from several sources and created this tutorial.
Sources:
http://www.getusb.info/usb-hack-turn-a-usb-stick-into-a-hard-drive-or-local-disk/
http://chdk.setepontos.com/index.php?topic=2332.0
http://www.ehow.com/how_5941768_make-flash-drive-local-disk.html
Disclaimer:
I am not responsible for any lost data or damages that occur to your computer or SD card. The steps in this tutorial are not harmful, but failure to follow the directions listed has the potential to harm your machine.
Looks nice, thanks. Can't test but i would like to read some feedback about this.
Ah maybe you could change Mount Multiple SDcard to Mount Multiple SDcard Partitions.
~ Veronica
lavero.burgos said:
Looks nice, thanks. Can't test but i would like to read some feedback about this.
Ah maybe you could change Mount Multiple SDcard to Mount Multiple SDcard Partitions.
~ Veronica
Click to expand...
Click to collapse
Where do you mean?
Nice guide you have written here, the main problem windows users have (unlike *nix users) is that an easier way needs to be found to flip the RMB (Removable Media Bit) on the thumb drive so it is recognized as HHD. I am currently researching this, if a solution exists then this would be applicable to all windows versions 32/64 bit and make our lives considerably easier.
EDIT///
Found a 64bit Hitachi cfdisk driver here h t tp : / / hardforum.com /showthread.php?t=1655684, haven't had a chance to test it yet since I am in class on my 32 bit laptop. (sorry I can't post url yet, I have to up my post count still.)
Attached file.
Redman247 said:
Nice guide you have written here, the main problem windows users have (unlike *nix users) is that an easier way needs to be found to flip the RMB (Removable Media Bit) on the thumb drive so it is recognized as HHD. I am currently researching this, if a solution exists then this would be applicable to all windows versions 32/64 bit and make our lives considerably easier.
EDIT///
Found a 64bit Hitachi cfdisk driver here h t tp : / / hardforum.com /showthread.php?t=1655684, haven't had a chance to test it yet since I am in class on my 32 bit laptop. (sorry I can't post url yet, I have to up my post count still.)
Attached file.
Click to expand...
Click to collapse
Nice work! I'm not able to test this right now as I'm out of town and away from my desktop, but I definitely will try this next week.
On a similar note, I am learning that to flip the RMB will require a mass production tool. The good news is that doing so will allow it to be read as a HDD no matter what windows machine you plug it in to (no need for cfdisk!) the bad news is that there is no mass production tool that covers all drives, it varies from manufacture to manufacture.
Redman247 said:
On a similar note, I am learning that to flip the RMB will require a mass production tool. The good news is that doing so will allow it to be read as a HDD no matter what windows machine you plug it in to (no need for cfdisk!) the bad news is that there is no mass production tool that covers all drives, it varies from manufacture to manufacture.
Click to expand...
Click to collapse
Your .zip was corrupt, so I attached a new one in this post and here is the originial source, too:
http://hardforum.com/showthread.php?t=1655684&highlight=cfadisk
@Everyone, be aware that in order to make this work on Windows 7 x64, you must either:
a.) Find a piece of software to sign the driver.
OR
b.) Disable the driver signing manually.
There's more information in the source thread.
Again, DO THIS AT YOUR OWN RISK. I may or may not add a section to this tutorial for the 64-bit OS.
Once the device driver is modified to recognize multiple partitions on an SD card, can one still write an ISO image to the SD card?
Followed your procedure for my 64GB Transcend Jetflash 500 and now I have this in windows explorer:
How do I get my old driver back???
UPDATE:
I reformatted my SDCard, but the first partition is still only recognized.
creeve4 said:
Followed your procedure for my 64GB Transcend Jetflash 500 and now I have this in windows explorer:
View attachment 1546701
How do I get my old driver back???
UPDATE:
I reformatted my SDCard, but the first partition is still only recognized.
Click to expand...
Click to collapse
Hi creeve,
Judging by your screenshot, your SD card is still being read as a removable disk. Looks like something didn't go correctly during the renaming and driver install.
View Last SD Card Partition on Native Nook Tablet Boot Option
Thank you for this. Would anyone know if similarly it is possible to view the last partition with all the storage data from a CM10 SD card when you boot into the native Nook Tablet system? Currently, only the first partition is visible when you boot into the native software.
Thanks!
I don't think it would be possible unless the NT is rooted.
moxda00 said:
Thank you for this. Would anyone know if similarly it is possible to view the last partition with all the storage data from a CM10 SD card when you boot into the native Nook Tablet system? Currently, only the first partition is visible when you boot into the native software.
Thanks!
Click to expand...
Click to collapse
Possibly by editing the vold.fstab file located in /etc to change which SD partitions your tablet mounts.
how to modify vold fstab file entry to show last partition
Solar.Plexus said:
Possibly by editing the vold.fstab file located in /etc to change which SD partitions your tablet mounts.
Click to expand...
Click to collapse
Thank you! I will try it, but is there any potential for damage? Below is the entry in my vold.fstab. What do I have to modify to make the fourth partition of my sdcard show up? By the way this is a CM10 SD Card created based on the intructions here: iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet
If there is some place where I can learn about the setup please point me to it. I am willing to learn!
Thanks again!
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
##
Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <lun_syspath> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## perm_mask - Mount permission mask: octal integer or 'auto' for default permission.
## <lun_syspath> - LUN for the device
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
dev_mount media /mnt/media 10 002 /devices/platform/usb_mass_storage/lun0 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
# TODO: it is preferrable to use 'by-name'
#dev_mount media /mnt/media auto auto /devices/platform/usb_mass_storage/lun0 /dev/block/platform/mmci-omap-hs.1/by-name/media
moxda00 said:
Thank you! I will try it, but is there any potential for damage? Below is the entry in my vold.fstab. What do I have to modify to make the fourth partition of my sdcard show up? By the way this is a CM10 SD Card created based on the intructions here: iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet
If there is some place where I can learn about the setup please point me to it. I am willing to learn!
Thanks again!
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
##
Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <lun_syspath> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## perm_mask - Mount permission mask: octal integer or 'auto' for default permission.
## <lun_syspath> - LUN for the device
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
dev_mount media /mnt/media 10 002 /devices/platform/usb_mass_storage/lun0 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
# TODO: it is preferrable to use 'by-name'
#dev_mount media /mnt/media auto auto /devices/platform/usb_mass_storage/lun0 /dev/block/platform/mmci-omap-hs.1/by-name/media
Click to expand...
Click to collapse
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Solar.Plexus said:
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Click to expand...
Click to collapse
Thanks, I did some research and bumped across this site which explains a bit (i have to remove the http cause I can't post links yet):
android.googlesource.com/platform/docs/source.android.com/+/master/src/tech/storage/index.md#
I'm curious why auto is repeated twice? I will try to just change the first auto for now and see what happens...
How to edit a root file?! Granting SU not working...
Solar.Plexus said:
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Click to expand...
Click to collapse
I've read around a little and I'm comfortable about trying it. However, I can't seem to modify the vold.fstab file and save the changes. I've tried several file editors including Root Browser. When I tried to save my changes the SU permission request box came up and I granted SU permission. However, I get a message saying: The file cannot be saved.
Please help! It's very frustrating. I've tried 5 different editors (ES, Root Browser, File Expert, etc)
moxda00 said:
I However, I get a message saying: The file cannot be saved.
Please help! It's very frustrating. I've tried 5 different editors (ES, Root Browser, File Expert, etc)
Click to expand...
Click to collapse
Have you mounted system folder as writeable? Root settings in ES.
Successfully modified volt.fstab and accessed 4th partition!!
asawi said:
Have you mounted system folder as writeable? Root settings in ES.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Thanks! That did it! I just had some trouble finding the flag/option to make root writeable. Once I did I was able to change the mount line as follows: dev_mount sdcard /mnt/sdcard 4 auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
I rebooted and it worked! Exactly what I wanted.
Thanks Solar.Plexus!
moxda00 said:
Thanks! That did it! I just had some trouble finding the flag/option to make root writeable. Once I did I was able to change the mount line as follows: dev_mount sdcard /mnt/sdcard 4 auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
I rebooted and it worked! Exactly what I wanted.
Thanks Solar.Plexus!
Click to expand...
Click to collapse
No problem, my friend. Glad to see you got it figured out!
Hi
I had the lastest stock ROM for my T-Mobile Samsung Vibrant with "DoW14 v1.4 344MB, Voodoo Lagfix, Sound, Color, BLN 2/21/2011". I had lag-fix applied as well as Voodoo sound. The phone had been working fine for months until a week ago when it didn't want to wake up. When I rebooted it started looping the first screen.
I have spend the last week trying to go back to stock with no luck. For some reason, my phone storage shows as "unavailable".
At this time I have in my phone Eugene's No Brick ROM with "3e" recovery applied as well as Overstock CWM recovery from CyagenMod Wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
My guess is that there is a problem with my internal SD card. I'm trying to follow the instructions in this post to try and format the internal memory but there is no "mmcblk0" in my "/dev/block/".
Here is the content of my "/dev/block":
Code:
# ls
stl5
stl2
stl1
bml11
bml10
bml9
bml8
bml7
bml6
bml5
bml4
bml3
bml2
bml1
bml0!c
tfsr12
tfsr11
tfsr10
tfsr9
tfsr8
tfsr7
tfsr6
tfsr5
tfsr4
tfsr3
tfsr2
tfsr1
tfsr0!c
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
bml12
stl12
stl11
stl10
stl9
stl8
stl7
stl6
stl4
stl3
ram0
Does it mean my internal SD memory is fried?
Sorry for the long email, but I am trying to give a good idea of my situation.
Still chasin
hmmm still no dice...
I was hoping someone would have chimed in by now. I still don't think my internal memory is fried, but I can't find where the internal memory is mapped. Even my "vold.fstab" file looks funny to me:
Code:
# cat vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# sdcard mount for the P1
# internal sdcard
{
mount_deep = 0
## [NAGSM_Android_HDLNC_SDcard_SeoJaeWoong_20101015 : do not use CD_ROM
# ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
asec = disable
mbr_policy = skip
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# externel sdcard
{
mount_deep = 1
## [NAGSM_Android_HDLNC_SDcard_SeoJaeWoong_20101015 : do not use CD_ROM
# ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun2/file
ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
asec = enable
mbr_policy = overwrite
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
See the following line:
Code:
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
There is no such locaton /devices/..." in my directory so why is this fstab points there????
At this point I'm still searching where the Eugene No Brick Rom got installed. Hopefully, once I find that out, I can reformat the drive and be able to install stock ROM.
chasin
Not one answer so far? I wonder if the developers and people in the know even read the Q & A forum.
Spend more time today and tried to follow this post: !SOLVED! Vibrant Internal Memory application storage 0b, please help! but it didn't help. After every ROM install I keep getting the same error message:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
No such file or directory
What confuses me is that any of these ROMs install at all if I'm having problem with my internal memory? Where are they being installed?
Help please!!! I have no more hair to pull
chasin away
Have you tried Odining?
I have had Dan_Brutal's original Vibrant at my house for the last few months, with this exact same problem. The only firmware, I have tried them all, that it will boot with is Eugene's JK2 package. I have it linked over in my RootzWiki ICZen thread, its worth a shot to flash it and see if it boots, however, when Dans boots up with that firmware, it reports a corrupt sd and is basically unusable.
I have done everything to this phone, flashed every firmware out there, tried repartitioning in recovery, even built custom Heimdall and Odin packages that work fine on mine, nothing will boot. I also tried the reparted technique, which is worth looking into, you might have better success with it. You can follow the reparted steps, but using the Vibrant specific partition structure, and it might work. It didn't on Dan's, I ran it and matched my partitions, and nothing.
If you need the stock partition mapping, let me know and I'll dig it up for you. Its probably faster to contact me on RW, I'm not over here very much anymore. And you are right, we rarely read Q&A, lol.
Sent from my ICZen Experience
Br1cK'd said:
I have had Dan_Brutal's original Vibrant at my house for the last few months, with this exact same problem. The only firmware, I have tried them all, that it will boot with is Eugene's JK2 package. I have it linked over in my RootzWiki ICZen thread, its worth a shot to flash it and see if it boots, however, when Dans boots up with that firmware, it reports a corrupt sd and is basically unusable.
I have done everything to this phone, flashed every firmware out there, tried repartitioning in recovery, even built custom Heimdall and Odin packages that work fine on mine, nothing will boot. I also tried the reparted technique, which is worth looking into, you might have better success with it. You can follow the reparted steps, but using the Vibrant specific partition structure, and it might work. It didn't on Dan's, I ran it and matched my partitions, and nothing.
If you need the stock partition mapping, let me know and I'll dig it up for you. Its probably faster to contact me on RW, I'm not over here very much anymore. And you are right, we rarely read Q&A, lol.
Sent from my ICZen Experience
Click to expand...
Click to collapse
Thanks for taking time to reply. My only two options are to try and use an external SD card or return ti to Samsung for repair. It pains me to say it, but I'm going to try and return it to Samsung and see how much they will charge me to fix it. I have already spend over 30 hours trying to fix this thing.
If Samsung wants and arm and a leg to fix it, I will probably got back to your idea of partitioning an external SD card and use that as phone's internal memory.
Thanks chasin
P.S. I'll keep the thread going for a few more weeks until I come to a solution.
Im wondering what's the difference of this error with the "Encryption Error" bug...
My phones internal sd is inacessible bacause of Encryption Bug that's said to be coming from early ICS Roms. Right now im running on a fix, using the external sd. The fix is posted here in Q & A.
Nice seeing you here Br1cK'd!
I know u can't resist to help.
Luv your IC Zen 1.7
gshmod known
silvercrown266 said:
Im wondering what's the difference of this error with the "Encryption Error" bug...
My phones internal sd is inacessible bacause of Encryption Bug that's said to be coming from early ICS Roms. Right now im running on a fix, using the external sd. The fix is posted here in Q & A.
Nice seeing you here Br1cK'd!
I know u can't resist to help.
Luv your IC Zen 1.7
Click to expand...
Click to collapse
The symptoms may be the same (unusable internal memory) but the cause is different. I was running Froyo not ICS when the problem started and I never got the encryption error.
I guess at the end of the day, the basic question I was rying to find was:
Is there a way to test the internal memory and determine if it is faulty?
If Eugene No Brick Rom is installed, where is being installed if the internal memory is bad?
If Samsung is asking too much money to fix my phone, by backup plan is to use the external card.
Thanks chasin
Here is an update to the thread. I just checked Samsung repair status and it saus the following:
Code:
*05/16/2012//11:38:50//0001773863//Telephone//ASC*
2012-05-16 ?? 10:38-JaeSung Ko: The unit has left the technician. SOLUTION: Replaced PBA
Looks like they had to replace the main board on the phone. I hope that means I was right and it was a hardware problem. Although I wished there was a way to test that. Hopefully I'll get my phone next week and close this thread.
chasin
P.S. I need to figure out how to update the a thread as solved when I'm done.
Solved
I finally got my phone from Samsung and they did replace the mainboard on the phone. I would like to think that it confirmed my suspicions that it was a hardware problem, not just a software corruption.
Total cost it was about $70 which included shipping both ways and part replacement. This was a pleasant surprise, considering the phone was out of warranty. It makes me feel good about my decision to skip those phone protection plans (which have a $50 deductible and ~$5 a month), but I'm usually careful with my phones.
Instead of moving all applications to SD card with app2sd, I want to move only selected applications.
Because I don't want to move my launcher, soft keyboard and dialer application to SD and make them unavaliable on boot if my SD card has problem or not inserted.
The idea behind is same, linking to SD card's second partition but differs in two ways.
One, instead of linking /data/app folder (that means moving all applications), you can select the applications that you want to move.
Two, it's an application which means has a user interface. You can manage your applications, create or remove links with just few clicks.
It also provides native apps2sd features on Android 2.2 and higher. Plus, it can move any non-protected user apps to SD card (force move), with batch moving capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).
Features:
- Create and remove link for apk, dex and lib files of the applications you select
- Automatically link newly installed apps
- Move any user apps to SD even though the app does not support moving to SD (for Android 2.2 and higher)
- Shows the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- Set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- Batch link, unlink, reinstall, uninstall, "move to SD", "move to phone" functions (multi-select mode)
- Uninstall system applications
- Freeze and un-freeze system and users applications
- Convert system apps into user apps
- Convert user apps into system apps
- Integrate "Updated" system apps into system (ROM)
- Clear data and cache of the application
- Clear all apps cache at once (1-tap cache cleaner without being root)
- List applications, show detailed size information and link status
- Sort and filter applications
- Search applications by name
- Display available space information of internal storage, SD card and SD card 2nd partition
What you need for linking applications:
- root permission
- a second partition on your SD card. You should have two partitions on SD card and both should be primary
The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4 or FAT32.
ext4 is the latest ext format but several ROMs have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
I use free "MiniTool Partition Wizard Home Edition" (windows application) for this.
You can create the second partition without repartitioning, formatting or deleting your existing partition with this tool. Connect your SD card to PC with a card reader or phone itself and make it visible as a drive. Open Minitool select this drive and resize down FAT partition, you will see an unallocated area at the end of the card. Create ext2, ext3 or FAT32 partition in that area (create as primary, not logical), click apply. Unplug from the PC and reboot the phone. (To be on the safe side backup your SD card data before starting)[/LIST]- That's all. Just install Link2SD, it will do all necessary. No need to copy files or run scripts.*
* Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need a matching ext2.ko or ext3.ko modules and even some additional modules to be able to mount.
Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones.
How it works:
Link2SD mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
When you select an application and press "Create Link" button you can select which files of the application will be linked and moved to SD card. Apk, dex and lib files can be moved and you can select all three or any two of three or even only one of them.
Depending on what you select, Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's second partition and creates symbolic links in original directories.
Note: On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if you move the apk file.
Can I remove the links and put application files back to phone?
Yes, just click on application that is linked and press "Remove Link" button. You can select which files of the application will be unlinked and moved back to internal storage.
Then, Link2SD removes the symbolic links and moves the files you selected to original directories.
What happens if I uninstall or update a linked application?
If you uninstall a linked application apk, dex and lib files will be automatically deleted from the SD card by Link2SD.
If you update a linked application new apk, dex and lib files will be placed in the internal memory at first and then they will be automatically relinked by Link2SD in the background.
You don't have to manually relink after updating applications.
Note: Since the app is linked again, On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if the apk file is linked
Some points
- System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
- When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted. Therefore linked applications are not affected and can be run without problems.
- Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files
UPDATE:
2.1.2
- fixed crash if too many apps (400+) are installed on some devices
- improved app search (use "contains" instead of "start with" and higlight the matching characters)
- updated translations
2.1.1
- some fixes and tweaks
- added Croatian language
- updated translations
2.1
- added "relink all application files" feature to scan 2nd partition and relink all the files (can be used when changing or updating the ROM)
- added "relink dex files at boot" option
- changed multi-select UI
- added batch freeze/unfreeze
- added size info of /system and /cache partitions to "Storage info"
- fixed bug in converting system apps into user apps and vice versa
- added Persian language
- updated translations
- some fixes and UI tweaks
2.0.4
- fixed relink lib bug introduced in 2.0.3
- added Catalan and Macedonian translations
- updated some translations
2.0.3
- fixed force close at startup on some devices
- updated translations
2.0.2
- fixed bug in obtaining root access on some devices
- updated translations
2.0.1
- added the ability to convert system apps into user apps
- added the ability to convert user apps into system apps
- added "Updated" mark to show if the app has been install as an update to a system (built-in) app
- added "Updated" filter option
- added the ability to integrate "Updated" system apps into system
- fixed freeze/unfreeze bug on some ICS devices
- improved ICS compatibility
- optimized link/unlink/move operations and speed improvements
- some fixes and UI tweaks
1.9.13
- added an option to change language in application settings
- fixed bug in "Storage info" that displays incorrect values if the partition is >1GB on some devices
1.9.12
- changed a2sd checking
1.9.11
- fixed "Mount warning" issue on some devices that do not have operational init scripts to mount 2nd partition at boot, e.g. new Samsung Gingerbread roms
** if you have this problem run "Recreate mount scripts" from the menu after installing the new version of Link2SD
- added Basque translation
- some fixes and tweaks
1.9.10
- fixed some issues on Android 4.0 (Ice Cream Sandwich)
- added Greek and Slovenian translations
- updated some translations
- some minor fixes and tweaks
1.9.9
- fixed bug in recognizing the second partition on some devices
- updated some translations
1.9.8
- fixed bug in setting install location option
- updated some translations
1.9.7
- moved filter and sort functions from menu to title bar
- added an indicator icon which shows the apps that can be moved to SD with native apps2sd (a small icon in upper right corner, for Android 2.2 and higher)
- added "Movable" filter option which lists the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- added "Clear data" to clear user data from the app
- added "Clear cache" to clear the app cache
- added "Cache size" sort option
- added ability to clear cache on all apps at once
- added "View in Market" for applications
- added an option to turn "auto link notification" off
- added Dutch, Serbian, Indonesian, Vietnamese translation
- fixed bug in recognizing the 2nd partition on some devices
- updated some translations
- some minor fixes and tweaks
1.9.6
- added Japanese, Chinese Simplified, French, Arabic, Bulgarian, Czech translation
- updated some translations
- added "Translation Credits" to the About page
1.9.5
- fixed freeze/unfreeze bug on some devices
- added Chinese Traditional, German, Hungarian, Italian, Polish, Portuguese, Portuguese Brazilian, Russian, Slovak, Spanish, Thai, Ukrainian translation
- added an option to use English language instead of system language
1.9.4
- added ability to freeze and unfreeze the user and system applications
- added "Frozen" filter option
- added ability to search applications by name, activated from the menu or search button
- some minor fixes and tweaks
1.9.3
- added "Recreate mount scripts" menu to recreate mount scripts manually when you change fs type or rom
- fixed bugs in "Quick reboot" and setting "Install location" on some devices
- some minor fixes and tweaks
1.9.2:
- added "Dex size" and "Total size" sort options
- some bugfixes
1.9.1:
- fixed FC on some devices
1.9.0:
- added native apps2sd function with batch capability (for Android 2.2 and higher)
** moves any user apps to SD even though the app does not support moving to SD
- added option to set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- added workaround for Roms that do not have install-recovery.sh and init.d scripts to mount 2nd partition at boot, e.g. new Samsung GB roms
** mounts after system finishes booting and you need to perform 'Quick reboot'
- new and safer 'Quick reboot' method
- added context menu to app list (activated on a long press)
- added option for automatic relinking of library files at boot
- added "on SD card" and "on internal" filter options
- added applications count to the title
- some UI changes
1.8.0
- changed the method for determining external storage to support devices that have more than one external storage (MMC and SD)
- added ability to uninstall system applications
- added batch (multi-select) reinstalling
- added batch (multi-select) uninstalling
- added "Relink library files" menu which relinks all the lib files that get unlinked after reboot
- removed "Market Fix" menu
- added "fast scroll thumb" option to quickly scroll through the app list
- added "Data size" to sort options
- some bugfixes
1.7.0
- added batch linking and unlinking (multi-select mode)
- some bugfixes
1.6.2
- fixed force close on application startup on some devices
1.6.1
- added horizontal screen orientation support
- added "Link dalvik-cache files" menu back
- improved loading and scrolling performance of the app list
- added cache size to app list
- fixed "Storage Info" bug on Android 2.3
- better CM7 support
Known issue:
* library files get unlinked after reboot on Android 2.3 and sometimes on 2.1 and 2.2. (PackageManager unpacks all native libraries from the apk files at boot)
1.6.0
- added option to link library (.so) files along with apk and dex files
- added automatic linking option for the new installed apps
- added ability to link/unlink apk, dex and lib files separately
- added '->' linked indicator to Apk, Dex and Lib labels
- added lib file size and link status information
- added lib size to sort options
- some bugfixes
1.5.5
- changed link creation, reboot is not required on Android 1.6 and 2.1 anymore
1.5.4
- added notification to status bar for automatic re-linking after app update
- added "reboot required" notification to status bar after linking app on Android 1.6 and 2.1
- some bugfixes
1.5.3
- changed menu name from "Quick Restart" to "Quick Reboot"
1.5.2
- added "Quick Restart" menu, cuts boot time
- added "Clean up the dalvik-cache" menu
- added "Clean up the 2nd partition" menu
- added ability to link updated system apps (that are located in /data/app)
- optimized refreshing of the app list after linking
- changed App2sd checking
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.5.1
- fixed background message
1.5.0
- added ext3, ext4 and FAT32 support for the second partition of SD card
- added refresh menu
- added "Not Linked" filter option
- changed App2sd checking
- added support in linking protected (/data/app-private) apps
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.4.2
- disabled automatic Market status fix after linking
1.4.1
- added option to link dalvik-cache (.dex) files along with apk files
- added automatic re-linking after app upgrade
- added automatic deleting from SD card after app uninstall
- added "Reinstall" button
- added "Link dalvik-cache files" menu which links dex files of all existing linked applications all at once
- added automatic Market status fix after linking
- better froyo support
- added dex file size and link status information
1.3.1
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.3.0
- added uninstall feature which deletes apk file also from ext2 for linked apps
- added launch and manage buttons
- added detailed size information of applications
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.2.1
- added info message to show which applications have been repaired after "Market Fix"
1.2.0
- added "Market Fix" feature to repair missing Market applications
- added support in detecting and mounting ext2 partition for some roms
- removed "ext2 found" info message at startup
- some minor bugfixes
1.0.5
- added support for some roms which install-recovery.sh is not operational
- added ext2.ko module installation on boot (if exists) for Motorola phones
1.0.4
- changed mount method at startup to be much safer
- some minor bugfixes
1.0.3
- initial release:good:
awesome app..very useful..!
what? are u the developer of link2sd? "BULENT AKPINAR" ??
this one https://play.google.com/store/apps/...?t=W251bGwsMSwxLDEsImNvbS5idWFrLkxpbmsyU0QiXQ.. ???
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
just another copycat . . what a shame! :/
eewwww i have been usin this app since ages with fat32 partition on my card..!!
Now who is this :|
Sent from my MT15i using xda app-developers app
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Abhilesh7 said:
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Click to expand...
Click to collapse
fat32 is usually supported by almost all roms .
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Later edit
A possible fix is to install a custom or an original rom. Actually this fixed my issue until I installed again Link2SD with partition mount script.
I installed: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ] after that I was able to attach my phone using MSC mode multiple times and I can access latest files / folders.
ciubexx said:
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Click to expand...
Click to collapse
open your link2sd, on 1st time it will ask you to choose mount script which kind of partition you use
after that reboot your phone.. open link2sd if it show same dialogue like 1st time open link2sd reboot go to cwm and mount your sd-ext
hmm... did you link your galery?? if yes unlink it
sorry my bad english
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
which file system(Fat 32,ext2 etc) should be proper to use with MT11i
Thank you for your answer.
Actually my problems is visible only when I attach my phone second time to PC, after a restart.
Opening the Link2SD I'm not asked to enable the mount script, because this script is already installed and running ok, I guess, because the second partition (/data/sdext2) appear on Link2SD -> Storage Info (see attached image).
Also I'm able to navigate through that linked folder (/data/sdext2/)
The behavior is like first time when I connect my phone to the PC, on the phone is created a 'cache' from where, on second / third / ... time are provided same informations (files and folders are same like on first connection).
I'm suspecting one of scripts: init.semc.rc or init.usbmode.sh (these files are recreated at start up / booting)
I'm not sure if I'm right.
Answering to aakash43
Try for first time to create two partitions with following formats:
- first partition: fat32
- second partition: ext2
More informations you can found here on the official page: Link2SD - Description - What you need for linking applications. ( link2sd.info/description)
If second partition is not mounted try to format to fat32. It is indicated to use a unix file format (ext4, ext3 or ext2) but depends by your phone kernel. In my case the phone (Neo - MT15i with latest firmware) was not able to recognize ext4 or ext3 format.
I want to know that Creating second partition in sd card will delete the data present in sdcard.
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
ciubexx said:
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
Click to expand...
Click to collapse
Great info! :good:
workaround for my MSC issue
I figured it out a workaround in my case, for the issue detailed on previous page at post #9.
It is important to have your phone rooted!
I flashed with a clean firmware (4.1.B.0.587) my phone (MT15i), I rooted my phone and I placed a customized rom: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ]
I opened the phone and I let it to install and configure all applications.
I rebooted twice to be sure all configurations are made properly.
I turned off my phone, I removed the SD card and I partitioned the card using my laptop card reader.
I partitioned using the MiniTool Partition Wizard Home Edition 7.6.1 on mine Windows 7 machine:
1. I deleted all partitions from my card (previously I had some partitions);
2. I created at the end of the card one primary partition with ext2 file system format; (previously I tested others formats ext3 and ext4, but seems to not be recognized these formats)
3. on the remaining space I created another primary partition with FAT32 file system format.
Like on below image:
I placed formated card into the phone and I turned on.
I modified the file: /system/etc/vold.fstab
I replaced:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
with:
Code:
dev_mount sdcard /mnt/sdcard 1 /devices/platform/msm_sdcc.4/mmc_host/mmc1
Format is:
Code:
Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
To found that solution I made some tests after each modification on /system/etc/vold.fstab I rebooted my phone. And I checked to see if the /mnt/sdcard is mounted properly.
I modified the file on PC and after each time I pushed modified file to the phone:
Code:
adb push vold.fstab /system/etc/vold.fstab
(you should have the terminal on the current folder where is your modified file)
Then, with my phone connected to PC I tried to mount the second partition to /data/sdext2/ folder.
Open a terminal and add below commands:
Code:
>adb shell
$su -
Your terminal should look like (this is in Windows):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\ciubex>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su -
su -
[email protected]:/ #
This folder was not on my phone, so I created: #mkdir /data/sdext2/
On PC terminal I tried to mount the partition using the command:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2
After each mount attempt you can check if the partition is mounted by using df command, the terminal should show like:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 169.9M 76.0K 169.9M 4096
/mnt/asec 169.9M 0.0K 169.9M 4096
/mnt/obb 169.9M 0.0K 169.9M 4096
/system 312.5M 310.7M 1.8M 4096
/data 380.0M 140.0M 240.0M 4096
/cache 101.5M 1.3M 100.2M 4096
/system/vendor 133.5M 92.1M 41.4M 4096
[b]/data/sdext2 1.4G 82.6M 1.3G 1024[/b]
[email protected]:/ $
If your second partition is mounted properly, you can proceed to install Link2SD.
I installed Link2SD, I let the software to generate mount script /system/etc/install-recovery.sh.
I don't rebooted, but I modified generated file by removing the line:
Code:
I let only the mounting:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2 1>>$LOG 2>>$LOG
Be careful to have an empty last line.
To exit from terminal, use commad: exit
After that I rebooted my phone.
Now I do not have any more problems with my latest created files or folders on the phone, when I connect the phone to PC using MSC protocol.
I attached an archive with modified files (vold.fstab and install-recovery.sh).
i used cwm recovery of lupus kernel and it partitioned my mc into fat32,ext3 n its running flawlessly
when I try to create partition using mini tool partition wizard the unlocated space does not increase above 304 MB plz help
Steps to make partitions
I really don't know what's wrong in your case, is your card empty? It is your card full and remaining empty space is 304MB?
But let suppose you have inserted a formatted card into a card reader with a single partition and want to have two partitions.
Method 1:
resize existing partition and create a second one:
- right click on partition
- select 'Move/Resize'
- click on right side of the partition image from 'Size And Location'
- move the border on left side to desired partition size
- click on 'Ok'
- now on the disks images should appear resized partition and an unallocated space at the end of the card
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
Method 2:
in that case the entire card is erased and partition(s) is (are) deleted firstly and created from beginning
- right click on partition or on each partition from card and select 'Delete'
- when entire card appear as Unallocated
- let create second partition at the end
- right click on Unallocated space and select 'Create'
- resize the partition image from 'Size And Location' by clicking on the left side and moving the left border to the right until the new partition have desired size
- select:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK'
- now will create first partition
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: FAT32
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
That's all.
This is the one I used ^^
I created a ext3 partition on the sd card, I selected what I want to moved or not.
And now, all new apps are installed on the sd card automatically.
Works great , thanks.