I have installed nitdroid on emmc and playing GOF2, my phone crash suddenly, it refuse to boot, deadloops. Then i reflashed my OS, but emmc not flashing, my phone not showing any file/folder in file manager, i want to install rootsh but not enough memory. Is thr any way to recover from this ??? Even i cant open any webpage with my n900. Plz help me i have searched alot but found nothing.

No reply ?? Please experts please do something.

There is no need to flash the device due to a 'simple' crash or unwillingness to boot. Most of the time the kernel is corrupted and therefore does not reboot. Just flashing the kernel from a Fiaso Image http://wiki.maemo.org/Updating_the_t...rt_topic.21.29 would boot into the OS again! Please post some info about space usage on your N900.This most likely shows some offending files or folders.
Do you have filebox installed?

home/user # df
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 233344 219044 10020 96% /
ubi0:rootfs 233344 219044 10020 96% /
tmpfs 1024 72 952 7% /tmp
tmpfs 256 72 184 28% /var/run
none 10240 68 10172 1% /dev
tmpfs 65536 4 65532 0% /dev/shm
/home/user # 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)
/home/user # du -kx / |sort -n | tail -n 20
13256 /var/cache
14164 /usr/share/microb-engine/chrome
14844 /usr/share/microb-engine
15068 /usr/share/themes
15200 /lib
18200 /usr/bin
21016 /var/lib/dpkg/info
23172 /var/lib/dpkg
23352 /usr/lib/locale
24288 /usr/lib/microb-engine
31772 /var/lib/apt
31772 /var/lib/apt/lists
50708 /opt/lib
53520 /opt
55540 /var/lib
68820 /var
78596 /usr/share
148012 /usr/lib
250868 /usr
408768
/home/user # du -kx /home | sort -n | tail -n 20
80 /home/user/.local/share/tracker
100 /home/user/.calendar
104 /home/user/.modest
104 /home/user/.modest/cache
172 /home/user/.gstreamer-0.10
172 /home/user/.osso-abook
172 /home/user/.osso-abook/db
208 /home/user/.bookmarks/thumbnails
216 /home/user/.bookmarks
380 /home/user/.mozilla/microb
488 /home/user/.mozilla/rtcom
812 /home/user/.cache/tracker
848 /home/user/.cache
868 /home/user/.mozilla
2264 /home/user/.backgrounds
7920 /home/user/.local/share/sounds
8000 /home/user/.local
8000 /home/user/.local/share
13068 /home
13068 /home/user


this is outcome from above scripts, before 2-3 months, my cell dropped on road but its working fine till 14th january i have installed nitdroid and also flashed emmc and os but on 14th i have plyed GOF2 and i have some work outside then i pause and go, when returns in 2mins it was rebooting and GURU meditation error showed then i reboot in maemo but boot loop. i have tried flashing kernels but i got error somewhat %m i think then i reflashed os but emmc not fleshing. now i have maged to install roots and managed to swap on my 2GB SD card but i am not able to install filebox, package broken error. i think i have cleared all things what was happened. is there any symlinking in OS and emmc ???

This really is trouble ahead!
Your EMMC is not showing at all in mount command output, indicating maybe hardware trouble...
Please try to check the file systems to get some output. These three commands try to get information about the three partitions of the EMMC.
Please also post the partition table of the EMMC, if possible

$ sudo gainroot
Root shell enabled


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.

/home/user # fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk0p1
/dev/mmcblk0p1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

/home/user # fsck -af /dev/mmcblk0p2
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk0p2
/dev/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

/home/user # free
total used free shared buffers
Mem: 245540 240376 5164 0 688
Swap: 995800 45460 950340
Total: 1241340 285836 955504
/home/user # sfdisk -l
/home/user #


this swap is on my SD card. if it is a hardware problem then tell me if there is any way to repaire it ????

May be the crash was the aftermath of the damage the EMMC took a couple of month ago, but who knows for sure?

Still the EMMC is not showing up, but sfdisk seems to ignore your external card as well, which is odd.
Please post the output of

/home/user # lshal | grep volume
block.is_volume = false (bool)
udi = '/org/freedesktop/Hal/devices/volume_part2_size_1019707392'
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
info.udi = '/org/freedesktop/Hal/devices/volume_part2_size_1019707392' (string)
volume.block_size = 512 (0x200) (int)
volume.fstype = 'swap' (string)
volume.fsusage = 'other' (string)
volume.fsversion = '2' (string)
volume.is_disc = false (bool)
volume.is_mounted = false (bool)
volume.is_mounted_read_only = false (bool)
volume.is_partition = true (bool)
volume.label = '' (string)
volume.linux.is_device_mapper = false (bool)
volume.mount_point = '' (string)
volume.num_blocks = 1991616 (0x1e63c0) (uint64)
volume.partition.flags = {} (string list)
volume.partition.label = '' (string)
volume.partition.media_size = 2002780160 (0x77600000) (uint64)
volume.partition.number = 2 (0x2) (int)
volume.partition.scheme = 'mbr' (string)
volume.partition.start = 983072768 (0x3a988000) (uint64)
volume.partition.type = '0x82' (string)
volume.partition.uuid = '' (string)
volume.size = 1019707392 (0x3cc78000) (uint64)
volume.uuid = '' (string)
udi = '/org/freedesktop/Hal/devices/volume_uuid_BE38_5C27'
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_BE38_5C27' (string)
volume.block_size = 512 (0x200) (int)
volume.fstype = 'vfat' (string)
volume.fsusage = 'filesystem' (string)
volume.fsversion = 'FAT32' (string)
volume.ignore = false (bool)
volume.is_disc = false (bool)
volume.is_mounted = true (bool)
volume.is_mounted_read_only = false (bool)
volume.is_partition = true (bool)
volume.label = '' (string)
volume.linux.is_device_mapper = false (bool)
volume.mount.valid_options = {'ro', 'sync', 'dirsync', 'noatime', 'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'utf8', 'shortname=', 'codepage=', 'iocharset=', 'umask=', 'dmask=', 'fmask=', 'uid=', 'flush'} (string list)
volume.mount_point = '/media/mmc1' (string)
volume.num_blocks = 1920000 (0x1d4c00) (uint64)
volume.partition.flags = {} (string list)
volume.partition.label = '' (string)
volume.partition.media_size = 2002780160 (0x77600000) (uint64)
volume.partition.number = 1 (0x1) (int)
volume.partition.scheme = 'mbr' (string)
volume.partition.start = 32768 (0x8000) (uint64)
volume.partition.type = '0x0b' (string)
volume.partition.uuid = '' (string)
volume.size = 983040000 (0x3a980000) (uint64)
volume.unmount.valid_options = {'lazy'} (string list)
volume.uuid = 'BE38-5C27' (string)
/home/user #

Neither kernel nor hal have been able to pick up your internal emmc!

There is a slight chance that still some broken software create this behaviour. A re-flash might be a try to fix it.

But rather it is an hardware issue. You might want to bothe Nokia Care now?!

Nevertheless, there is a thread here with a manual and a scripted solution with an external card: http://talk.maemo.org/showthread.php?t=69081 The solutions start from post#8 on. You might want to get a larger card though.
For this you better reflash the fiasco image, just install rootsh and do not enable those space wasters extras-testing and extras-devel repositories until you applied the solution.

thanx michaaa62, plz tell me procedure for using only 2Gb sd card with 256mb swap 500mb for installing appsand rest for MyDocs. i am a noob in such stuffs plz.