My brother and I are curious as to what is up with the File System in these phones involving the internal Memory and SD Card. He has a different GS and his file system is soo much stranger. However I'm more interested in how this Fascinate works
It claims 2gb internal memory But where in the file system is this internal memory? Where is the A2SD Memory? Where is all this stuff, say in like Root Explorer?
Here's a screen shot of the Fascinate with a 8gb SD Card
{
"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"
}
It shows the SD Card, which I get that, in Root Explorer its /sdcard/. However where is the 191mb that is completely empty of A2SD? Where is the 1.53gb of Internal Storage?
I know on my Inc, Internal memory is /emmc/ and sd is /sdcard/
Not one person on this forum knows how this phones file system is setup?
Its RFS file system, voodoo converts it to ext4. Apparently ext4 is more efficient/effective, specifically write operations. I'm no programmer so that's the extent of my knowledge.
Sent from my SCH-I500
nFiniti said:
It shows the SD Card, which I get that, in Root Explorer its /sdcard/. However where is the 191mb that is completely empty of A2SD? Where is the 1.53gb of Internal Storage?
Click to expand...
Click to collapse
I think Internal storage is /data, System storage is /system, System cache is /cache, and A2SD storage is /mnt/asec.
skreeves said:
I think Internal storage is /data, System storage is /system, System cache is /cache, and A2SD storage is /mnt/asec.
Click to expand...
Click to collapse
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
mrodsunshine said:
Its RFS file system, voodoo converts it to ext4. Apparently ext4 is more efficient/effective, specifically write operations. I'm no programmer so that's the extent of my knowledge.
Sent from my SCH-I500
Click to expand...
Click to collapse
Its slower, but more efficient and safer. But not what I was asking. I was asking for some kinda Diagram of the Storage Locations and what not like
IE: /mnt/sdcard = External SD Card.
No, there is internal storage. Take your microSD out and see if it still works... It might be an internal permanent SD card for all I know but it's there. Some of the other Galaxy S phones have both internal 16GB SD and an empty slot though which would have been nice to have.
I'm pretty sure RFS is not safer and definitely not more efficient... but by the way, most mount points are on the internal storage. Only /mnt/sdcard is on the sd card (big surprise).
If you want exact mount points for everything, run mount in a terminal emulator.
nFiniti said:
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
Click to expand...
Click to collapse
Yeah. There totally is internal storage. It's 2GB NAND flash storage. Totally not removeable.
Sent from my SCH-I500 using XDA App
here is eb16 with voodoo:
Code:
# mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
nFiniti said:
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
Click to expand...
Click to collapse
If there wasn't any internal storage, where would everything be stored? Can't store apps on the SD card on 2.1...
Related
Taken from http://forums.hardwarezone.com.sg/showthread.php?t=2806456
For those that do not want to download Kies, here is the driver. I did not try others except I know it works on Win7 x64
http://db.tt/ErGVyE
deckcard said:
Galaxy S Meminfo
Code:
MemTotal: 333416 kB
MemFree: 28220 kB
Buffers: 5700 kB
Cached: 112080 kB
SwapCached: 0 kB
Active: 92292 kB
Inactive: 165804 kB
Active(anon): 48956 kB
Inactive(anon): 92160 kB
Active(file): 43336 kB
Inactive(file): 73644 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 140336 kB
Mapped: 55228 kB
Slab: 13220 kB
SReclaimable: 3240 kB
SUnreclaim: 9980 kB
PageTables: 11976 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 166708 kB
Committed_AS: 7187348 kB
VmallocTotal: 286720 kB
VmallocUsed: 78580 kB
VmallocChunk: 154628 kB
Click to expand...
Click to collapse
deckcard said:
Galaxy S mountpoints
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?
worldicez said:
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?
Click to expand...
Click to collapse
born to be RW !? wow!
That link just tells me they don't have a revision history for the file?
If I use the original link, I just don't see how where I get an actual download link!?!?
Please help
some mirrors:
http://www.multiupload.com/A3VUGCKIIJ
u can find the drivers here:
http://forums.hardwarezone.com.sg/showthread.php?t=2812085
hmmm.. or you can extract the contents of the latest Kies application from the Samsung website using 7zip and save it on your computer.
..check the folders and you will see there a folder which contains the "USB driver".. copy that folder and save it someone.. as for the rest you can safely delete them.
.. that is what I did before.. Kies is to laggy for me and takes a long time to respond/load.. "drag and drop" works wonders for me.
**note: you must enable "show hidden.." from folder options so that you will be able to see the Appdata.. haven't tried directly typing on the adrress bar the direct location.. "C:\Users\<user account name>\AppData\Local\Temp\Samsung\"..
**oh yeah.. this is for Windows 7.. should be the same for Vista i guess.
{
"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"
}
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1600.0.exe
http://www.multiupload.com/ZQIEJHSRSI
this is from the samsung kies_win.exe package released on 2010/11/11
works with Win7 x64
Thank you, fixed my [nearly] bricked Captivate!
FLASH STOCK ROM then overcome kernel 3.1.0
it works
Sent from my GT-I9100 using XDA App
serious , how you make it work ? ?
Edit : i was kidding with ya ... perhaps , i don't know what i say ..
compare eur jq1 initramfs with jp8 just little different
it just works
Sent from my GT-I9100 using XDA App
owh that is so new !!!!!!
screen capture
{
"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"
}
we need "Microscope" to look at it .. btw what you posted is not new !!!! perhaps for some other ppl ...
simple howto - no guarantee. try at your own risks
Get P1000ZTJP8 ## http://www.samfirmware.com/WEBPROTECT-p1000.htm
Unrar the file downloaded and get the gt-p1000_mr.pit and P1000ZTJP8_P1000ZTJP5_P1000BRIJP8_HOME.tar inside
flash stock rom with re-partition using Odin3 (repeat once more if you install http://forum.xda-developers.com/showthread.php?t=1074759 Overcome ROM v2.0.1 Hermes before to make it really clean)
download Overcome Kernel V3.1.0 http://overcome.mimzo.com/wp-content/plugins/download-monitor/download.php?id=4
Heimdall flash the zImage inside. Be patient but there are some voice telling you the progress and it can take few minutes
Cons:
Try at your own risks and no guarantee
As expected most Overcome features will not work
Pros:
Has Superuser
Quandrant rating is 1567
ext4 mount
Code:
$ mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /preload vfat ro,nodev,noatime,nodiratime,fmask=0133,dmask=0022,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gi
d=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime
,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=10
00,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixe
d,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
some hard work . really
Introduction
Here's the classic Midnight Commander for Android!
{
"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"
}
Features
a) Function keys work (F3 - view, F5 - copy, F8 - delete, F10 - exit, etc...)
b) Very stable, doesn't crash.
c) Much easier installation than the previous one version (which needed an additional apt-get clone, named ipkg, etc). More about this below.
d) comes bundled with xterm (terminfo) and syntax highlighting for major languages.
e) I kept the wrapper script 4.6.2 but updated it so that function keys work.
Reasons
There is an one year old version floating around (version 4.6.2) and even if does start, it crashed every time I pressed the arrow keys in the search panels:
Code:
/system/xbin/mc.real: libc/misc/ctype/ctype.c: 290: tolower: Assertion `((((unsigned int)((c) - 0)) <= ((127 * 2 + 1) - 0)) || ((c) == (-1)))' failed.
Not only this, but I had to restart Putty, since the whole screen became garbled.
Installation
You need a rooted phone with busybox.
Installation is easy:
click Install and allow root access.
If everything is ok, you will see an output like in the screenshot below:
To use mc, you could connect with a terminal emulator (but it looks ugly). A good alternative is if you use DroidSSHd as SSH server on the phone and Putty as client from your PC (or connect-bot as client on the phone).
For now, there is no uninstaller for the native MC that is extracted on the phone. Thus, feel free to uninstall the app as you don't need it anymore once MC native is copied to the phone.
Download
Use it at your own risk! (License is GPLv2)
NativnuxInstaller_1.1.apk
cp cannot create 'mc-4.0.7................
read only file system.
How to solve this ?
I tried to remount /system as rw but didn´t help.
How to get write access to / ?
I tried to extract the archive on a linux machine and copy the folders to device via QtADB but when I tried to run mc from terminal emulator I get error run xterm.
So I think there was some permission errors.
1. Become super user:
su
2. Check output of current mounts:
cat /proc/mounts
You will see something like:
Code:
...
/dev/block/mtdblock0 /system yaffs2 rw,relatime 0 0
Remember the number after mtdblock! Important. In case above is 0, but it might be 3 also etc...
3. Execute command:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock[PUT_HERE_THE_NUMBER] /
viulian said:
1. Become super user:
su
2. Check output of current mounts:
cat /proc/mounts
You will see something like:
Code:
...
/dev/block/mtdblock0 /system yaffs2 rw,relatime 0 0
Remember the number after mtdblock! Important. In case above is 0, but it might be 3 also etc...
3. Execute command:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock[PUT_HERE_THE_NUMBER] /
Click to expand...
Click to collapse
Seems that /system is in /dev/block/mmcblk0p12 . I tried your command with mmcblk0p12 but again I get the same error. So, something I'm doing wrong. Here is the output of cat /proc/mounts:
Code:
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p12 /system ext3 rw,relatime,errors=continue,data=writeback 0 0
/dev/block/mmcblk0p13 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p1 /cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.junglesoft.calc-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.aldiko.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.jiubang.android.euphorialite-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.gamestar.idiottest-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.svox.classic.langpack.ell_grc_fem-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Can this helps you to give me, a specific to my system, command?
Thanks in advance
As you can see, your device has ext3 type partition, unlike mine which has yaffs2.
Your custom command is:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /
In future, please search your device specific forum for device specific questions - I found the answer myself here: http://forum.xda-developers.com/archive/index.php/t-928727.html
No, this doesn't work eather, I've already tried.
I figure it out myself though, needed to remount rw my / partition which is rootfs.
After that the extarction worked without any error.
But still I get:
Error opening terminal: xterm
when I try to execute mc.
Make sure you have the following file copied over from the .tar.gz archive:
/etc/terminfo/x/xterm
I suggest to copy all files (/etc/mc and /system/share .. ) because they contain a lot of .ini files / syntax etc, without which mc will look black and white
Better if you untar in / directly ...
I did this already, and xterm is in correct place.
Please post screenshot of the following commands executed in same terminal:
Code:
cls
ls -l /etc/terminfo/x/xterm
cat /system/xbin/mc
ls -l /system/xbin/mc.real
I execute them via adb:
Code:
# ls -l /etc/terminfo/x/xterm
-rw-r--r-- 1 system system 3213 Jul 5 2010 /etc/terminfo/x/xterm
# cat /system/xbin/mc
#!/system/bin/sh
export TMPDIR=/data/local/tmp
if [ ! -e $TMPDIR ]; then
mkdir $TMPDIR
fi
# So that F1, ... works
export TERM=xterm
/system/xbin/mc.real $*
# ls -l /system/xbin/mc.real
-rwxr-xr-x 1 system system 3508114 Aug 31 19:51 /system/xbin/mc.real
Looks good.
What kind of terminal are you using adb in ? I suggest http://code.google.com/p/droidsshd/ and ssh to the phone - and bypass adb completly.
I'm on linux machine and use tilda as terminal, but I execute the command and on device with terminal emulator with the same results
Try copying over your Linux /etc/terminfo (or depending on the distro, it might be somewhere else - my Ubuntu says to check /lib/terminfo then /usr/share/terminfo).
Copy all the single letter folder onto /etc/terminfo on the phone, and then change /system/xbin/mc to export a different type of terminal, for example:
export TERM=linux
Of course, make sure that /etc/terminfo/l/linux is there before this.
With TERM=linux, the function keys do not seem to work in my case, they are rendered like ~13 etc .. However, it might work in your case ?
I get the same error, but now for "linux"
linux is there on letter l
I'm curious, why does your phone shows the /etc contents are owned by system / system, instead root / root ?
I don't know, but I think that is the reason for this error.
viulian said:
As you can see, your device has ext3 type partition, unlike mine which has yaffs2.
Your custom command is:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /
In future, please search your device specific forum for device specific questions - I found the answer myself here: http://forum.xda-developers.com/archive/index.php/t-928727.html
Click to expand...
Click to collapse
To be strict - you don't have to use anything but this:
mount mountpoint -o remount,rw
which means in this case:
mount / -o remount,rw
Writing the filesystem type or device name for such a command in a guide for everyone is quite an error.
And to be complete - only thing you have to write to see all mounted filesystems is: mount<enter>
Cat'ting /proc is NOT safe (one of the reasons: it can be switched off, whole proc filesystem, and there are many more reasons to be honest)
viulian said:
Make sure you have the following file copied over from the .tar.gz archive:
/etc/terminfo/x/xterm
Click to expand...
Click to collapse
it's not correct place ) /usr/share/terminfo is compiled inside mc.real binary(to ensure strings -a mc.real | grep terminfo or winhex it), so to run we need to create /usr/share/terminfo/x/xterm, but it's not possibly to create such path on any device. the easest way to fix - recompile mc with hacked terminfo path. if you could compile mc can't you please?
ps: my english is baaad, sorry )
ok, it's solution - add export TERMINFO_DIRS=/system/etc/terminfo to mc script
Nice find.
I remember specifying the prefix to be /system and I removed /system/etc/terminfo and it failed to start, then I put it back and it executed.
There might also be some hardcoded paths too that strings finds, some failover defaults.
On my phone, /etc is a link to /system/etc in fact.
I will double later a bit, no access to PC now
Hi at all, basicly it works for me on cm7-nightly - but i get problems with loading the default skin
has anybody a solution for it ?
Uploaded with ImageShack.us
THX !
I have a 2GB card in my NC, and it's only showing 1.00GB size on the NC.
When I plug it into the computer over USB, it shows only 1.00GB.
When I pull the card and put it in the computer using the builtin card reader, it shows 2GB as it should.
What gives?
I have a new card on the way, 32GB, don't want to wind up with the same issue. Help?
?s
1. did you use it to nooter/install CWM? Some of the SD card CWM installers reformat the sd card to 1gb
Use easus partition to format the entire SD card and fix this...
2. did you get it off ebay? some people have reported getting fake cards there (where the actual capacity of the card is less than reported) though typically they can get it to fake the higher capacity until you write to it above its actual capacity.
I formatted it to 2GB in my computer. I can put the card directly into my computer and write 2GB on it. The problem with the card only occurs when it is in the NC.
??
and with file explorer can you see the 2gb of files on the sd when it's in the NC?
what happens when you connect to the NC as a flash drive? can you see the 2gb of files then? Do you also see your media partition?
The nook color internal memory has two partitions. A system partition and a media partition that you can connect to over usb. Some versions of Nook color had the media partition formatted to be 1gb.
gallahad2000 said:
and with file explorer can you see the 2gb of files on the sd when it's in the NC?
what happens when you connect to the NC as a flash drive? can you see the 2gb of files then? Do you also see your media directory?
The nook color has two partitions. A system partition and a media partition that you can connect to over usb. Some versions of Nook color had the media partition formatted to be 1gb.
Click to expand...
Click to collapse
{
"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"
}
1.00 Gb according to the NC.
As I said, when I connect the NC to the computer over USB it also appears as 1 gb. When I remove the card and put it directly into the computer it is 2 gb.
There is no media directory.
It appears the NC doesn't correctly recognize the card.
mr72 said:
It appears the NC doesn't correctly recognize the card.
Click to expand...
Click to collapse
If you remove the SD card does the 1.0gb or 1.88gb partition disappear?
Some things don't look right in there, in your posted image.
You got Internal storage of 5.09GB (it is the first weird one), then you got Additional storage (/mnt/emmc) of 1.86GB (it is another weird one).
Normally, we have either
1. old scheme: 1GB /data, 5GB /media
2. new scheme: 5GB /data, 1GB /media
3. custom scheme: 1.96GB /data, 4+GB /media.
Yours doesn't look right.
votinh said:
Some things don't look right in there, in your posted image.
You got Internal storage of 5.09GB (it is the first weird one), then you got Additional storage (/mnt/emmc) of 1.86GB (it is another weird one).
Normally, we have either
1. old scheme: 1GB /data, 5GB /media
2. new scheme: 5GB /data, 1GB /media
3. custom scheme: 1.96GB /data, 4+GB /media.
Yours doesn't look right.
Click to expand...
Click to collapse
Well I just did the normal install of cm 7.10 stable and no partitioning. However my problem is the SD. I am not particularly worried about the internal flash partitioning.
Any ideas why I can't use more than 1gb of SD? I have a 32gb SD card arriving today. I really would like to get to the bottom of this.
There is no /media partition mounted on my nook color.
$ export PATH=/data/local/bin:$PATH
$ mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p2 on /rom type vfat (rw,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p5 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p6 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:8 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:8 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/pl.idreams.jellydefense-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.devolver.sska-2 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
$ mount |grep media
$cd /media
cd: can't cd to /media
$
mr72 said:
Well I just did the normal install of cm 7.10 stable and no partitioning. However my problem is the SD. I am not particularly worried about the internal flash partitioning.
Any ideas why I can't use more than 1gb of SD? I have a 32gb SD card arriving today. I really would like to get to the bottom of this.
Click to expand...
Click to collapse
Just a stab in the dark but I have found most of my issues with uSD (and quality brands such as SanDisc) cards have gone back to how the card was formatted. I now never format in the device, nor do I use Windows to format. I've mentioned this before but it bears mentioning again, this free utility has never failed giving me a good intact format on cards of sizes 1G to 32G. Try it out here.
HTH
My NC is partitioned like this:
Code:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
I think this is default for the "new" partition style (which I will soon change).
However this is not affecting my SD card.
I should get my 32GB SD in the mail today or tomorrow. I suppose I will know soon enough whether I can use more than 1G on THAT card.
While trying to poke around on this NC and figure out exactly how the partitions are working, I discovered another thing which may be normal but sure seems odd to me.
The /emmc and /sdcard contents (directory names) are nearly identical.
Code:
ls /emmc
Android Music clockworkmod
B&N Downloads My Files com.maildroid
Books Nook data
DCIM OverDrive dropbox
Digital Editions ReceivedFiles eBooks
Download TempAudio fix_permissions.log
Evernote TunnyBrowser opera
GOLauncherEX Videos tmp
GoStore adobe
LOST.DIR backups
# ls /sdcard
ls /sdcard
Android My Files com.maildroid
B&N Downloads Nook data
Books OverDrive dropbox
DCIM ReceivedFiles eBooks
Digital Editions TempAudio fix_permissions.log
Download TunnyBrowser notes
GOLauncherEX Videos opera
GoStore adobe tmp
LOST.DIR backups
Music clockworkmod
#
Creating a file on one does not create it on the other. But some of the directories have identical files. For example the Titaniumbackup files in the /data dir on both /emmc and /sdcard are identical. I didn't check any others.
This seems quite odd. Comments?
OK, I think maybe I am getting to the bottom of this!
on my NC, when I take the SD card completely OUT, I can still view files mounted on /sdcard
So I am not convinced that my /sdcard mountpoint is actually reflecting the SD card directly.
When I unmount the SD card in the "Storage" settings, and I get the "Safe to remove..." notification, I presume the actual SD card is not mounted.
I removed the SD card from the NC and reformatted it using Panasonic SDFormatter. It's 1.86GB and has no files on it.
Without the SD card in my NC, it operates normally and still thinks it's writing to the /mnt/sdcard for things like downloading files.
My suspicion is that the partition normally mounted to /media is mounted to /mnt/sdcard
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 245892 32 245860 0% /dev
tmpfs 245892 0 245892 0% /mnt/asec
tmpfs 245892 0 245892 0% /mnt/obb
/dev/block/mmcblk0p2 71164 108 71056 0% /rom
/dev/block/mmcblk0p5 458532 169376 289156 37% /system
/dev/block/mmcblk0p6 5336664 688980 4376592 14% /data
/dev/block/mmcblk0p7 350018 42216 289731 13% /cache
/dev/block/vold/179:8 1050156 1029924 20232 98% /mnt/sdcard
/dev/block/vold/179:8 1050156 1029924 20232 98% /mnt/secure/asec
THERE IS NO SD CARD IN THE NC.
Looks like the NC still THINKS the sd card is mounted.
Notice there also is no mount point for /media
The partition I'd expect to be mounted at /media (/dev/block/mmcblk0p8) is not mounted.
Please, someone explain this to me! Seriously, what's the Nook Color's partition scheme?
mr72 said:
OK, I think maybe I am getting to the bottom of this!
on my NC, when I take the SD card completely OUT, I can still view files mounted on /sdcard
So I am not convinced that my /sdcard mountpoint is actually reflecting the SD card directly.
When I unmount the SD card in the "Storage" settings, and I get the "Safe to remove..." notification, I presume the actual SD card is not mounted.
I removed the SD card from the NC and reformatted it using Panasonic SDFormatter. It's 1.86GB and has no files on it.
Without the SD card in my NC, it operates normally and still thinks it's writing to the /mnt/sdcard for things like downloading files.
My suspicion is that the partition normally mounted to /media is mounted to /mnt/sdcard
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 245892 32 245860 0% /dev
tmpfs 245892 0 245892 0% /mnt/asec
tmpfs 245892 0 245892 0% /mnt/obb
/dev/block/mmcblk0p2 71164 108 71056 0% /rom
/dev/block/mmcblk0p5 458532 169376 289156 37% /system
/dev/block/mmcblk0p6 5336664 688980 4376592 14% /data
/dev/block/mmcblk0p7 350018 42216 289731 13% /cache
/dev/block/vold/179:8 1050156 1029924 20232 98% /mnt/sdcard
/dev/block/vold/179:8 1050156 1029924 20232 98% /mnt/secure/asec
THERE IS NO SD CARD IN THE NC.
Looks like the NC still THINKS the sd card is mounted.
Notice there also is no mount point for /media
The partition I'd expect to be mounted at /media (/dev/block/mmcblk0p8) is not mounted.
Please, someone explain this to me! Seriously, what's the Nook Color's partition scheme?
Click to expand...
Click to collapse
If there is no SD in... the vold.conf is setup to mount /dev/block/mmcblk0p8 as /sdcard...
Code:
## vold configuration file for zoom2
# modified for encore
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
media_type mmc
partition 4
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
That doesn't seem to be the case, although it would make sense.
Looks like my sdcard is mounted at /mnt/emmc.
Rebooting into CWM after reformatting my SD card and putting it back in blank, putting a couple of files on it, it is found in CWM as /sdcard.
Once I boot, I find that content in /mnt/emmc.
Perhaps this explains it:
http://forum.cyanogenmod.com/topic/36236-help-sd-card-and-emmc-changed-places/
I've had the same issue as the OP since installing CM7 a few weeks ago. It really had me baffled, but I tried the fix linked above just now and it did the trick thank you mr72!
Sent from my NookColor using xda premium
CountKrzysztof said:
I've had the same issue as the OP since installing CM7 a few weeks ago. It really had me baffled, but I tried the fix linked above just now and it did the trick thank you mr72!
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
OK, so to reiterate:
If you have CM7 installed, and in Settings -> Cyanogenmod Settings -> Application Settings, you check "Use internal storage", then CM7 will SWAP the SD card and the internal 1G (default) "Additional storage:/mnt/emmc" partition. The result is that your SD card will be mounted at /mnt/emmc and your internal memory 1G partition will be mounted at /mnt/sdcard.
Also, when you plug the NC into the computer if you have these swapped, then the 1G "internal memory" will be mounted on your computer, rather than the sdcard.
In actuality, this is a good thing, and there is a hack out there to swap these, therefore making use of the normally unused partition that by default in CM7 would be mounted at /mnt/emmc.
I'm lost following your posts but I know
/mnt/emmc is the additional internal storage and /mnt/sdard is the external uSD card.
That's the case when running CM7 off eMMC.
It's set by default, otherwise, maybe I have to set something to twist around.
Also, when having uSD plugged in, connecting to PC (Windows), both mounted as you would see the 1G internal AND the CM7SDCARD
Hello guys,
after flashing ICS on my Kindle Fire I can't see my internal storage files via terminal or file explorer. When I connect the kindle via usb to the computer, I can see files, folders and stuff I put there, but I couldn't find any way to see them from the kindle. Any ideas?
If I try to mount the second internal storage unit via settings -> storage it just tries for half a second and then goes back to where it was.
my mount output is this one:
127|[email protected]:/mnt # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
[email protected]:/mnt #
I had similar problem with ICS but in my case a simple restart did the trick. You probably tried that already
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
dragonsoul84 said:
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
Click to expand...
Click to collapse
After installing droidwall and blocking the 1000 internal kf sync app, and after that unblocking it and uninstalling the droidwall I cannt understand why but it has "woken up" the kindle with wispersync app that it had install being rooted and it asked for regitration (an up that that didnt work before), and from then on I cannot se everything that I put in the "books" and "documents" folders! Have you any idea why?
dragonsoul84 said:
I am in the same boat as OP. I finally took the plunge in rooting and installing ICS ROM on my Kindle Fire, been waiting for a good ICS Build. Unable to access internal storage. Rebooted several times. Clicked "Mount SD Card" and it shows for about a second and goes back to showing "Mount SD Card." Any help is appreciated.
FIXED!!! Booted into recovery, unmounted, remounted sd card, rebooted and was able to see internal storage. Hope this helps.
Click to expand...
Click to collapse
Hey this happended on my LG Optimus 2X when I flashed ICS, I tried more or less all the file managers and the storage settings but they didn't work, then I tried this and it worked...thanks a lot