2010-08-30 5:51 - edited 2010-08-30 6:00
When i power on my N900 i get a notification message saying device storage format unsupported.
Note: I DONT have a memory card, this is the Internal Memory Card.
When i check (settings, memory) It says memory card corrupt 1.86GB available.
When i check FileManager, It says no files/folders.
First two pictures on http://talk.maemo.org/showthread.php?t=44203 is basically how it is on mine.


I tried flashing the firmware and emmc and it worked everything was back. But when i restart my phone same notification.When run mount /home/user/MyDocs via X-Terminal, In Filemanager I can see N900 folder but in Settings/Memory is still says memory corrupt. When i restart phone everything does not work again.
Can someone please assits me.
Solved! Go to Solution.
2010-08-30 8:10
It seems you're sending it back, mark this as solved then so people don't take up too much time helping you.
2010-08-30 8:26 - edited 2010-08-30 8:29
Dude that is some other guy i just reference his pictures. I reply even in this post on the same site,same name angelo0015 http://talk.maemo.org/showthread.php?t=34988&page=
Can someone please help me
2010-08-30 13:08
2010-08-30 17:40 - edited 2010-08-30 17:40
As i stated before that is someone else who is retuning it to Dell SB.
As for the flashing it is the lastest firmware and emmc
Firmware: 187721717 PR 1.2 version 10.2010.19-1
EMMC: 262090105 eMMC content 10.2010.13-2
Can someone please help me, when i type via X-terminal rm -rf /home/user
and then rebooting everything works again but after the next reboot back to the same problem
2010-08-30 23:23
well, may as well give it a whirl!
HERE FOR DIRECTIONS TO FLASH YOUR N900
you will need to be sure that you have a non-64 bit pc.
1. Download the Flasher
2. Download the latest firmware image for your N900 (you will need your IMEI of the device)
3. when you save the global variant of the firmware to the "flasher-3.5" folder, save it as "pr1.2.bin"
4. When you save the vanilla file of the firmware to the "flasher-3.5" folder, save it as "vanilla.bin"
5. Turn your phone off
6. launch the flasher-3.5 program
7. type this command: flasher-3.5.exe -F pr1.2.bin -f
it will then scroll a bunch of gibberish and then say it is looking for a unit.
8. with the phone still off, hold slide the kb open and hold the "U" button while you connect the usb cable to the phone. continue holding the "U" until you see the faint "NOKIA" logo and/or the USB connection symbol in the top right. The flasher will find the device and automatically flash the unit to the original rom
9. after about 1.5 minutes, it will be complete. DO NOT DISCONNECT YOUR UNIT!
10. type this command: flasher-3.5.exe -F vanilla.bin -f -R
11. now it should reflash the device and wipe the emmc clean of EVERYTHING. after it reboots, you can disconnect it.
before you load any software into the device via restoring from your backup, be sure to try the backlight settings again and see if it is still having the issue.
if the issue is gone then there was some software that you had installed that was affecting it. if the issue is still there, then have your device replaced.
if the issue is resolved, then a couple of things.
1. depending on how many applications you had installed, you can go back and install them one at a time and re-sync your contacts/calendar separately. or you can do a restore from your back up.
when you do the restore, be sure that you look at all the applications in the list that it is going re-download and install before you allow it to, to be sure they are the only applications you want.
2. mark this post as solution and post a kudos to any post above that has helped you in the effort to resolve your issues as a happy thanks to their efforts in giving you free support for your device that NOKIA did not give you.
2010-08-31 1:43
2010-08-31 11:30
Have you tried un-mounting the mass memory partition and running an file system check on it?
Open the terminal and gain root.
Then type
umount /dev/mmcblk0p1 and enter
Then
fsck -t ext3 /dev/mmcblk0p1 and enter
Let it do its thing and see if it reports back any errors.
Then remount the partition by
mount /dev/mmcblk0p1 and enter
2010-08-31 13:18 - edited 2010-08-31 13:20
After i gain root, I enter umount /dev/mmcblk0p1
I get - Invalid argument.
But when i enter fsck -t ext3 /dev/mmcblk0p1
I get -
alleged total clusters: 445129
checked clusters: 3869
/dev/mmcblk0p1: 1038 files, 3869/445129 clusters
And when i enter mount /dev/mmcblk0p1
It is mounted.
2010-08-31 13:29
Ok, do you have rootsh installed that that you can gain root?
If not, first run
apt-get install root
When it installs, run
sudo gainroot
Then run
umount /dev/mmcblk0p1 (remember the space)
If you still get an invalid argument error, then the partition is not mounted. This may be due to it being corrupted in the first place.
Then
fsck -t ext3 /dev/mmcblk0p1
Run
mount /dev/mmcblk0p1
then
df
And check to see if /dev/mmcblk0p1 is mounted.
Then try and see if it works as it should.
I'll look around for some solutions and post them if I find anything.
2010-08-31 14:01
2010-08-31 14:09 - edited 2010-08-31 14:09
Try this to remake the filesystem on the partition.
umount /dev/mmcblk0p1 fsck.vfat -f /dev/mmcblk0p1
and then reboot.
2010-08-31 14:17
2010-08-31 15:16
2010-08-31 15:36
Unfortunately that's all the advice I have left to give....send it back.
2010-08-31 21:01
2010-09-01 0:21 - edited 2010-09-01 0:34
@matthew_maude
do you have some script un mounting it on start up?
or have you done anything similar with desktop cmd widget?
and are you restoring a backup after the flash?
Answer:
No nothing install except rootsh.
No
No
When i get the error and i type via x-terminal
df
/dev/mmcblk0p1 is NOT mounted.
but when i type
rm -rf /home/user
Restart the phone after using this command it works like it should, no corrupt memory and in FileManager you see the N900 folder until you reboot again then back to the same problem.
When it is working after typing rm -rf /home/user and restarting.
I enter via x-terminal:
df
I can see /dev/mmcblk0p1 is mounted
Is there a way to edit the start up to load /dev/mmcblk0p1 always.
Or repair start-up. Maybe this might fix the problem.
2010-09-01 0:41
2010-09-01 1:17
2010-09-01 2:02