![]() |
my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail me to boogiie@yahoo.com. thanks colleguies
|
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
First of all: You might want to remove your email address to not get spammed all over the place.
May be your data partition's file system has been corrupted. Please open the X-Terminal command and run a couple of commands. Please try to copy and paste the command to avoid typing errors, also try to copy and paste the output for best possible support. Do you have rootsh or some other application installed to gain the rights of 'root'-user? Please run these commands: Code:
df |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
$ root
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) Enter 'help' for a list of built-in commands. Nokia-N900:~# df Filesystem 1k-blocks Used Available Use% Mounted on rootfs 233344 229064 0 100% / ubi0:rootfs 233344 229064 0 100% / tmpfs 1024 68 956 7% /tmp tmpfs 256 80 176 31% /var/run none 10240 84 10156 1% /dev tmpfs 65536 4 65532 0% /dev/shm /opt/pymaemo/usr/lib/python2.5 233344 229064 0 100% /usr/lib/python2.5 /opt/pymaemo/usr/share/pyshared 233344 229064 0 100% /usr/share/pyshared /opt/pymaemo/usr/lib/pyshared 233344 229064 0 100% /usr/lib/pyshared /opt/pymaemo/usr/share/python-support 233344 229064 0 100% /usr/share/python-support /opt/pymaemo/usr/lib/python-support 233344 229064 0 100% /usr/lib/python-support /dev/mmcblk0p1 3873364 24 3873340 0% /home/user/MyDocs /dev/mmcblk1p1 3872760 3475080 397680 90% /media/mmc1 Nokia-N900:~# mount rootfs on / type rootfs (rw) ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /tmp type tmpfs (rw,noatime,size=1024k) tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755) none on /dev type tmpfs (rw,noatime,size=10240k,mode=755) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k) nodev on /sys/kernel/debug type debugfs (0) /opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind) /opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind) /opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind) /opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind) /opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind) /dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir) /dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir) Nokia-N900:~# mount rootfs on / type rootfs (rw) ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /tmp type tmpfs (rw,noatime,size=1024k) tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755) none on /dev type tmpfs (rw,noatime,size=10240k,mode=755) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k) nodev on /sys/kernel/debug type debugfs (0) /opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind) /opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind) /opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind) /opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind) /opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind) /dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir) /dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir) Nokia-N900:~# du -kx /home/opt/ | sort -n | tail -n20 du: /home/opt/: No such file or directory Nokia-N900:~# du -kx /home/user/ | sort -n | tail -n20 56 /home/user/.intellisyncd 56 /home/user/.mozilla 56 /home/user/.mozilla/rtcom 76 /home/user/.local/share/tracker/data 80 /home/user/.local/share/tracker 96 /home/user/.modest 96 /home/user/.modest/cache 100 /home/user/.calendar 160 /home/user/.osso-abook 160 /home/user/.osso-abook/db 172 /home/user/.gstreamer-0.10 208 /home/user/.bookmarks/thumbnails 216 /home/user/.bookmarks 664 /home/user/.cache 664 /home/user/.cache/tracker 2264 /home/user/.backgrounds 7612 /home/user/.local/share/sounds 7692 /home/user/.local 7692 /home/user/.local/share 11664 /home/user Nokia-N900:~# Nokia-N900:~# x-terminal shows avoid results |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
Looks weird. You may want to educate us about the last steps you did to get to that state.
These are the things i could single out until now: 1. Missing optfs: Basically your file systems seem to be alright, but /dev/mmcblk0p2 is missing completely. This causes the problems of no space to install applications. 2. Your MyDocs partition is only 3.7GB and empty, no files on it. You better remember what you did lately to try to undo things. And you should try to describe what you hope to setup back to working condition. Please post the output of Code:
sudo gainroot Testdisk is a fine tool to recover files from lost partitions. Best used on unmounted partitions, did you use it while the MyDocs partition was unmounted??? Again, it looks like your MyDocs partition in use is a freshly formatted one. |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
I have problems with my device too, ""Memory card format unsupported"" . Your code it s ok? for me dont work :( but you wrote sfdisk -l /dev/mmcblk0 it s oK? mmcblk0 ? I cannot flashing emmc :( only rootfs I can flashing.
|
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
May be the issues of your N900 may be better discussed in a separate thread to get full attention. There are no answer and feedback here anywhere to be found.
Back to your questions: So what is the output of the command Code:
sudo gainroot |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
remove all apps
install backupmenu run a live gparted reseize or not partitions(home must divide to 1024) format home(ext3 or 4) and MyDocs & sd(if you have problems with it) reflash firmware and this is it |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
Quote:
|
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
how many partitions do you have? how many programs installed? i like the rounding thing , it's sounds better , and neither i have encountered problems with sfdisk because of size(corrupted /home because fapman is another story = 4 coruptions with ext3 an none yet with ext4 , let's hope it stays like this)
|
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
sfdisk whinges when partitions do not end on cylinder boundaries, that's all. I have two working devices ATM, both having three partitions. One is stock, the other with 4GB ext4 /home.
But let's stop derailing this thread, shall we? We are waiting for OP's feedback. |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
thanks all. i try all above instructions but i have.t done successfull. then i desided to reflash emmc but i can.t please help
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM_9GBHOME_1GBSWAP.bin -f then can.t load drivers and can.t flash continue i.m going to use gparted live and shrink or reformat emmc memory. is it possible and how to use it please reply detailed instroctions |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
root flash successfull but emmc shows above error i.m usin windows xp 32 bit computer
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_ PR_COMBINED_MR0_ARM.bin -f -R flasher v2.5.2 (Sep 24 2009) SW version in image: RX-51_2009SE_20.2010.36-2_PR_MR0 Image 'kernel', size 1705 kB Version 2.6.28-20103103+0m5 Image 'rootfs', size 185728 kB Version RX-51_2009SE_20.2010.36-2_PR_MR0 Image 'cmt-2nd', size 81408 bytes Version BB5_09.36 Image 'cmt-algo', size 519808 bytes Version BB5_09.36 Image 'cmt-mcusw', size 5826 kB Version rx51_ICPR82_10w08 Image '2nd', size 14720 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2217, 2218, 2219, 2220, 2120 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2101, 2102, 2103 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2307, 2308, 2309, 2310 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2407, 2408, 2409, 2410 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2 113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2 113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2 113, 2114, 2115, 2116, 2117, 2118, 2119 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2607, 2608, 2609, 2610 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2507, 2508, 2509, 2510 Version 1.4.14.9+0m5 Image '2nd', size 14720 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2 210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2 210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2 210, 2211, 2212, 2213, 2214, 2215, 2216 Version 1.4.14.9+0m5 Image '2nd', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Suitable USB device not found, waiting. USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0 105. Found device RX-51, hardware revision 2101 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0 Sending xloader image (14 kB)... 100% (14 of 0 kB, avg. 14 kB/s) Sending secondary image (106 kB)... 100% (106 of 0 kB, avg. 106 kB/s) Flashing bootloader... done. Sending cmt-2nd image (79 kB)... 100% (79 of 0 kB, avg. 79 kB/s) Sending cmt-algo image (507 kB)... 100% (507 of 0 kB, avg. 507 kB/s) Sending cmt-mcusw image (5826 kB)... 100% (5826 of 0 kB, avg. 5826 kB/s) Flashing cmt-mcusw... done. Sending kernel image (1705 kB)... 100% (1705 of 0 kB, avg. 1705 kB/s) Flashing kernel... done. Sending and flashing rootfs image (185728 kB)... 100% (185728 of 0 kB, avg. 185728 kB/s) Finishing flashing... done CMT flashed successfully C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2. VANILLA_PR_EMMC_MR0_ARM.bin -f -R flasher v2.5.2 (Sep 24 2009) Image 'mmc', size 255947 kB Version RX-51_2009SE_10.2010.13-2.VANILLA Suitable USB device not found, waiting. USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0 105. Found device RX-51, hardware revision 2101 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0 Booting device into flash mode. Suitable USB device not found, waiting. |
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
Quote:
Quote:
|
Re: my Nokia N900 low memory to app install and 32 GB only shows 3.7Gb error how to solve this. i use recovery-tools test disk app then nothing happened. please help me and mail
I have the same problem, I modified the EMMC to 3 GIGAS a year ago. since that time I have never been able to flash the EMMC, I can only do it in rootfs without problems. I have used all the commands in maemo flasher as you say over and over again, without using the-R and repeating the steps but no case, only sometimes successfully flashing rootfs. Before my mind could enter mydocs without problems, but when trying to fix mounting and dismounting, to fsck from the terminal I found this reading in all forums to understand and be able to run different command that you know how to use ... but it got worse, now my EMMC (OPT) is corrupt, and I can not delete some folders that are broken. Now I can not enter MyDocs, says "memory card corrupted". When you restart the N900 throws the message "device storage format unsupported" but the rest of the phone works. When connected via USB as mass storage works. MyDocs memory appears and I can use it without problems from your computer.
from terminal: /home/user # mount /home/user/MyDocs mount: mounting /dev/mmcblk0p1 on /home/user/MyDocs failed: Stale NFS file handle Urgent need to restore factory settings. Is that possible? Please help me. I'm sure many have this problem and still fail to flash the EMMC. |
All times are GMT. The time now is 04:53. |
vBulletin® Version 3.8.8