N900 "Memory card corrupted"

[brankomilosevic]

Hello,

Here is my problem.

settings->general->memory:

device:
(memory cards corrupted)

memory for installable applications
50.8MB available

So, there are no my 32GB...

In addition, when I get plugged my n900 to PC, a can see two new disks. When I open (explorer) first, I get the message "format or not...". When try to open second, message received "pleas insert disk to drive G:"

Thank you in advance

[ossipena]

Hello,

Here is my problem.

settings->general->memory:

device:
(memory cards corrupted)

memory for installable applications
50.8MB available

So, there are no my 32GB...

In addition, when I get plugged my n900 to PC, a can see two new disks. When I open (explorer) first, I get the message "format or not...". When try to open second, message received "pleas insert disk to drive G:"

Thank you in advance

G: could be explained if you have no microSD in.

hard to say what is wrong about internal flash.

[DannStarr]

I say format the thing and take it from there

[brankomilosevic]

G: could be explained if you have no microSD in.

hard to say what is wrong about internal flash.

No, I do not have microSD
How I can format it again?

[Andre Klapper]

Might be https://bugs.maemo.org/show_bug.cgi?id=5767 .

[thonayan99]

Hi,
Please I need help. suddenly I have memory corrupted after i buy the device couple of hours ago. here what happened:

1. i switch on the device, then i explore it and start to download some application from the application manager.

2, meanwhiel, I went to the web browser and it sayd " Operations temporarliy disabled due to low memory".

3. when i start reciving SMS messages i see the preview but could not open it as another message appear " close applications".

4. the ovi map can't started and closed immedaility and I can't open any other application.



then i went to the file manager and i want to access the device internal memory "sfil_li_memorycard_internal" a message then appear " Memeory card format unsupported".

i went through setting> phone > memory and i found that a message wirtten under the device "memery card courrupted" and before that probelm it was showen 32GB as it is the internal deviced memeory.

the external momery are shown to be ok.

the solution i think of is to upfdate the softwear and i found that there is no new update using Nokia softwear update. then i just re-update with the same version but NOT SOLVED.


PLEASE ANY SUGGESTION BESID SENDING IT BACK TO THE NOKIA.




the only thing i can do is just using the device to call.

thanx

[lma]

the solution i think of is to upfdate the softwear and i found that there is no new update using Nokia softwear update. then i just re-update with the same version but NOT SOLVED.


Try reflashing the eMMC as well, see http://wiki.maemo.org/Updating_the_firmware, and this (http://wiki.maemo.org/Updating_the_firmware#Flashing_the_eMMC_in_the_N90 0) part in particular. If it still has problems after that it's probably faulty hardware.

[thonayan99]

Any one have more simple way to overcome this probelm

[thonayan99]

Try reflashing the eMMC as well, see http://wiki.maemo.org/Updating_the_firmware, and this (http://wiki.maemo.org/Updating_the_firmware#Flashing_the_eMMC_in_the_N90 0) part in particular. If it still has problems after that it's probably faulty hardware.

thanks a lot but is there is straight forward way to solve it.

regards,

[Cherrypie]

thanks a lot but is there is straight forward way to solve it.

regards,

regarding the amount of different problems, you have encountered. It's really the best way to reset your firmware with flashing the device. Using the step by step manual, posted above, that should be a matter of 2-3 hours at max.
If you're using windows, visit directly this page:
http://wiki.maemo.org/Flasher

[SubCore]

from http://wiki.maemo.org/Updating_the_firmware#Flashing_the_eMMC_in_the_N90 0

1) download flasher (http://wiki.maemo.org/Flasher)
2) download eMMC image (http://tablets-dev.nokia.com/nokia_N900.php)
3) run ./flasher-3.5 -F <eMMC image> -f -R

that's pretty straight forward i would say... :)

[Cherrypie]

from http://wiki.maemo.org/Updating_the_firmware#Flashing_the_eMMC_in_the_N90 0

1) download flasher (http://wiki.maemo.org/Flasher)
2) download eMMC image (http://tablets-dev.nokia.com/nokia_N900.php)
3) run ./flasher-3.5 -F <eMMC image> -f -R

that's pretty straight forward i would say... :)

0) install your latest service pack, when using windows ;)

[thonayan99]

lady, girl, Gent,and boy....:)

Thank you very much I will try these steps (2-3 hrs) and will see ....and hopfully give postiive post once I finished. ;)

[thonayan99]

0) install your latest service pack, when using windows ;)

ok here what I did and please help me on the rest:

1. download flasher 3.5 (after installation when i run the application it appear like cmd, command secreen starting with "c:\program files\maemo\flasher-3.5>"

2, i download the eMMC from nokia website with the following name "RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM". it is around 156MB size with extension file of .bin,

3. i tried to run the command using the flasher as "c:\program files\maemo\flasher-3.5>$ flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM -f -R"

but did not recognize the command also i tired the other command "c:\program files\maemo\flasher-3.5>./ flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM -f -R" and also didn't recoginze.

the other thing i made my device flashing by holding the "U"" key and it worked well as it appear USB images in top right corner of the device secreen and now the flasher suppose to work but it ddn't.


please any one tell what i need to do now.

[merc248]

That's because you're trying to execute UNIX commands in Windows.

Here's the Windows relevant portion of the document: http://wiki.maemo.org/Updating_the_firmware#Windows

[thonayan99]

That's because you're trying to execute UNIX commands in Windows.

Here's the Windows relevant portion of the document: http://wiki.maemo.org/Updating_the_firmware#Windows

thnaks. i went to the linked page and this is excactly the same instruction i did and follow prevouisly. i am running win7 and i installed the flasher 3.5 related to my OS but when it comes to the command i stuck and got same messages mentioned above.


please I need help.

[kris]

thnaks. i went to the linked page and this is excactly the same instruction i did and follow prevouisly. i am running win7 and i installed the flasher 3.5 related to my OS but when it comes to the command i stuck and got same messages mentioned above.


please I need help.

Hi,

It seems that you ar mixing Unix/Linux commands... $ and ./ are used with Unix/linux. You can try the following:
C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe /?
- that shows the help info

Then the actual command would be like:
C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM -f -R

.. I dont' have N900 yet (still with N810 and that is not with me now)
so can't help much more, but anyway that is the syntax....

Hope this solves the problem...

[lma]

2, i download the eMMC from nokia website with the following name "RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM". it is around 156MB size with extension file of .bin,


That's the firmware image. Just checking, did you really mean to download the "Middle East and North Africa" version or did you just get the highest-numbered one?

The eMMC image is RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin.

You should flash both the firmware and eMMC images.


3. i tried to run the command using the flasher as "c:\program files\maemo\flasher-3.5>$ flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM -f -R"

You need to specify the full path of the firmware image, or (probably easier) just move it into "c:\program files\maemo\flasher-3.5".

[SubCore]

in addition to what kris and lma pointed out (location of the image file and correct eMMC image file), don't forget to specify the full name of the file, including the extension .bin!
so the command would look like this (all in one line):
c:\program files\maemo\flasher-3.5>flasher-3.5 -F c:\download\RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin -f -R

c:\download being the location of the image file. if this path contains spaces, you have to put the whole path in double quotes "".

[thonayan99]

Thanks to all....finally it works with me and the falshing and programming completed. BUT still my original probelm is not solved yet "Memory card corrupted" and i can't do any things with this device only to call.

it good to share with other that the below command shall be used in Windows expect you need to cahnge the eMMC name and you must add the estenion .bin

"flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM.bin -f -R"

again is there any other solution besid doing falshing and sending it back to nokia....please experts help.

[thonayan99]

pls...pls....pls......any body can help....i am sick from this device if it didn't work since i buy it....

[bbns]

I guess it's better for you do return it and get another new one. I have flashed half dozen N900 but never seen this happened. It may cause by hardware defective but not sure.

It's pain that you have to suffer this. However, to return it and get a new one is probably the best way to go.

[jjx]

"flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM.bin -f -R"

If that's the only command you used, then look down a little to Ima's post. You need to flash the eMMC image too.

That's the firmware image. Just checking, did you really mean to download the "Middle East and North Africa" version or did you just get the highest-numbered one?

The eMMC image is RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin.

You should flash both the firmware and eMMC images.

[sjgadsby]

Threads merged.

[thonayan99]

If that's the only command you used, then look down a little to Ima's post. You need to flash the eMMC image too.

thanks these are two different eMMC images here and i think Ima refered to the USA version image as i download and utilized the middel east version image of 156MB size and run it in the command....there are different images and each one is allocated for different countries....please tell me if i am wrong and do appreciate your reply..

[thonayan99]

Threads merged.

thanks. it was deleted.

[anidel]

you're not alone.. you're the second person I hear that has this problem.

[jjx]

thanks these are two different eMMC images here and i think Ima refered to the USA version image as i download and utilized the middel east version image of 156MB size and run it in the command....there are different images and each one is allocated for different countries....please tell me if i am wrong and do appreciate your reply..

My reading of Ima's post is that you need to flash two image files, not just one file - the firmware file, and the eMMC file.

I don't know much about this, though; I don't have a device myself. Just explaining what I think Ima is telling you, because you seem to be missing a file.

[thonayan99]

My reading of Ima's post is that you need to flash two image files, not just one file - the firmware file, and the eMMC file.

I don't know much about this, though; I don't have a device myself. Just explaining what I think Ima is telling you, because you seem to be missing a file.

Yes...will do...i am currently downloading the eMMC file (235.5MB SIZE)....and will post the result here....wish for me the good luck...

[anidel]

good luck :)

[thonayan99]

here is the result...

i ran those two commands:
1. "flasher-3.5 -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin -f -R" and this is for the eMMC image. i noticed that it runs in less than a second with no error.

2. "flasher-3.5 -F RX-51_2009SE_1.2009.42-11.003_PR_COMBINED_003_ARM.bin -f -R" for the firmware images.


and the result still the same of the orginal problem "Memory card corrupted".....

also i tired to change the sequances on running of the two commands but same results.

really i start to heat this device....but i feel it has very powerful softwear through usingn ..


please any other solutions....help...

[thonayan99]

pls any one faced this problem before....pls we need some help here....

[rm42]

1. i switch on the device, then i explore it and start to download some application from the application manager.


Just a question about this. Do you remember what applications you installed? Did you enable any repositories other than the default ones that are already enabled?

[thonayan99]

yes i think it was the bounace game- not 100% sure...then the device start to give the message of low memeory and could not open any other application...only calling from the device could be done.

any suggestion...pls do.

[Flandry]

Are you talking about an external memory card? A removable one? Reflashing won't fix that, of course. If it got corrupted, it will probably need to be reformatted. Are you able to install programs and such on your internal memory?

Also, did you enable extras-devel repository?

[thonayan99]

Are you talking about an external memory card? A removable one? Reflashing won't fix that, of course. If it got corrupted, it will probably need to be reformatted. Are you able to install programs and such on your internal memory?

Also, did you enable extras-devel repository?

Thanks. the problem is in the internal memory 32GB and this make the device applications to not work due to low memory available. the other external memory works normal and just fine...any suggestions?

[FC_]

I had exactly the same problem, and fixed it by reflashing with the eMMC rom, exactly as explained in this thread. After that I could browse the device with the file manager, and it said 30 GB free or something.

Before I reflashed the eMMC, it said memory corrupted or something. And when I recieved a sms, a popup kept popping up saying no messages can be send or recieved because the memory is full. I could only read the sms once, when I recieved it, and then it disappeared.

The calendar app also kept crashing, and when I scrolled to the desktop which had the calendar widget on it, the phone would automaticly reboot after a few seconds. And when it booted it would say "device storage format unsupported". I could install programs, because they are installed on the other partition. The main 30 GB of the device were corrupted.

But then I found out I also had another problem, because my microphone seemed broken. And I'm not the only one as you can see in this (http://talk.maemo.org/showthread.php?p=392425) thread. I returned my phone to Nokia today, hoping to get a new one next week.

[thonayan99]

I had exactly the same problem, and fixed it by reflashing with the eMMC rom, exactly as explained in this thread. After that I could browse the device with the file manager, and it said 30 GB free or something.

But then I found out I also had another problem, because my microphone seemed broken. And I'm not the only one as you can see in this (http://talk.maemo.org/showthread.php?p=392425) thread. I returned my phone to Nokia today, hoping to get a new one next week.

thanks God to hear someone could make it...really i appreciate if you could explain what exactly you did in steps,,,,you can copy the above mentioned steps if you wish,,,,really i am intersted to see somthing work.


thanks inadvance.

[thonayan99]

I had exactly the same problem, and fixed it by reflashing with the eMMC rom, exactly as explained in this thread. After that I could browse the device with the file manager, and it said 30 GB free or something.

Before I reflashed the eMMC, it said memory corrupted or something. And when I recieved a sms, a popup kept popping up saying no messages can be send or recieved because the memory is full. I could only read the sms once, when I recieved it, and then it disappeared.

The calendar app also kept crashing, and when I scrolled to the desktop which had the calendar widget on it, the phone would automaticly reboot after a few seconds. And when it booted it would say "device storage format unsupported". I could install programs, because they are installed on the other partition. The main 30 GB of the device were corrupted.

But then I found out I also had another problem, because my microphone seemed broken. And I'm not the only one as you can see in this (http://talk.maemo.org/showthread.php?p=392425) thread. I returned my phone to Nokia today, hoping to get a new one next week.

thanks FC_, exactly i have te same problem but i meant here to give me the exact steps that you made so that u could over come the memeory corrupted problem,,,like give steps 1. run the comman "xxxxxxxx....." then 2. run the other step or command and so on..

i think with your support we can reach to the solution as seems we exactly having the same problem....i know it is anoying to you but really appreciate your reply.

thanks again.

[FC_]

Well, I couldn't get the flasher-3.5 working under Windows 7, so I downloaded Ubuntu (a linux distribution which can be booted from CD-ROM without installing) and tried it there. But that shouldn't make any difference if you see the flasher program flash it, and saying the flash was succesfull.

I first flashed the RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin rom, which is the global release, because I have a dutch N900. I saw you tried the middle east/northern africa rom, so I assume you live in the middle east or northern africa.

And I used exactly the same command as you did:
flasher-3.5 -F RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin -f -R

But that didn't work. So then I flashed it again with the eMMC rom:
flasher-3.5 -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin -f -R

Both times the flasher-3.5 program said something like "flash succesfull" and after this the device worked perfectly except the for microphone. But that is another problem, and has nothing to do with the memory being corrupted.

[thonayan99]

Well, I couldn't get the flasher-3.5 working under Windows 7, so I downloaded Ubuntu (a linux distribution which can be booted from CD-ROM without installing) and tried it there. But that shouldn't make any difference if you see the flasher program flash it, and saying the flash was succesfull.

I first flashed the RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin rom, which is the global release, because I have a dutch N900. I saw you tried the middle east/northern africa rom, so I assume you live in the middle east or northern africa.

And I used exactly the same command as you did:
flasher-3.5 -F RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin -f -R

But that didn't work. So then I flashed it again with the eMMC rom:
flasher-3.5 -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin -f -R


Both times the flasher-3.5 program said something like "flash succesfull" and after this the device worked perfectly except the for microphone. But that is another problem, and has nothing to do with the memory being corrupted.

did you notice the above step for eMMC command (2nd step) ran less than a second and disappear, when i do this step only it wil ran for one second but the device afterthat is dead you can't switch it on unless i follow and do the other command and it is start to work again. is this happening to you.?

[FC_]

No, the eMMC flash will take at least a minute or two. So I think you did something wrong, because it at least has to say something like "flash failed". Or your memory is even more corrupted than mine was and you can't flash it.

When you flash the "COMBINED" rom of 160MB, does it take a while, and you see "flash successfull" when it's done?

[thonayan99]

what about you mentioned....."the Ubuntu (a linux distribution which can be booted from CD-ROM without installing)"

from wr u get it and did you burn it on CD and run it on your Wind 7? may be this is the trick here...

[FC_]

If the flasher tool works on Windows 7 that really shouldnt matter. But does it really work for you? When you run it you should see the progress of the flash, and get a confirmation in the end that the flash was succesfull, do you see that?

[thonayan99]

If the flasher tool works on Windows 7 that really shouldnt matter. But does it really work for you? When you run it you should see the progress of the flash, and get a confirmation in the end that the flash was succesfull, do you see that?

yes it does for flashing using the middel east image as for the 1st step without problem...but when it comes to eMMC file it doesn't give me the progress the only thing i guss it is work cz it tell me it is waiting for usb connection and once i connect the device to the usb it start to work but in less than a second.

this is way i am asking if i can donload what you mention in a CD so that i can run it in the CD-ROM as you mentioned. by the way how many times you tried reflashing for the eMMC (2nd step).

and thanks to be patiant with us..

[thonayan99]

just clarification here we got two falsh to do one is for the combinde image command and the other is for the eMMC image.

the 1st one i can see the progress report and take 1-2 minutes.

the 2nd one i can't see any porgress and it takes less than a second and disapper but after that the device is dead no way to start it up unless i do the 1st step again then the life come back to it.

[FC_]

Ubuntu is a linux distribution, it's like a replacement for Windows. But you can try it without installing it. You have to download it, burn it to CD, and boot from the CD. You will then enter the linux environment, and you have to open a terminal (like command prompt in windows) and go to the directory where you downloaded the roms, and run flasher (it's already installed).

This is not that easy for someone who doesn't know what he's doing, and difficult to explain.

Download here: http://www.ubuntu.com/getubuntu/download

[thonayan99]

i think the problem i am facing now is in step # 2. Do you have any suggestion.

[FC_]

I don't know man. If you can flash the combined rom in step 1 without problems, step 2 should work. So think your memory is just more corrupted than mine was. I think the only way is to return it to Nokia.

[thonayan99]

thank you FC_. but it will take a week for me to return it back to nokia for different reason. Thank you agian man

any other suggestions from experts N900.

[SubCore]

thonayan99:

you could try to do the following:
get md5sum (http://www.etree.org/md5com.html) - that's just a very small .exe, no installation.
run this with both files in the same location:
md5sum RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin

this should give you exactly this output:
09c8fd8258abf49cf0a8e05d09068a04 RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin

if the long number/letter combination at the beginning is any different than the one here, your download has errors and you can try redownloading.
actually, this string is in the file "MD5SUM" on http://tablets-dev.nokia.com/nokia_N900.php, i assume these files are the same for everyone.

if the string is exactly the same, i would say that your hardware has a fault, and you should return it to nokia...

[thonayan99]

thanks a lot. what i did is i installed the .exe file (48kb) and put the below code in the maemo flasher 3.5 command but fialed to recognize. Any suggestion.

"md5sum RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin"

so the command appears like this "c:\program files\maemo\flasher-3.5>md5sum RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin"

yes all the files are same and from the same source you linked above. .

[SubCore]

this has nothing to do with the flasher, with md5sum i'm trying to help you verify that your downloaded image file is not corrupted.

you put md5sum.exe and the eMMC .bin in the same folder, open a command prompt, "cd" into that folder, and run
md5sum RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin

the output you should be getting is a certain value which has to be the same as in the MD5SUM file from the download page (this is not the .exe you downloaded, but a file at the same location where you downloaded the image files and the flasher).
if the output is any different than what is contained in the MD5SUM file, then your downloaded image file is corrupt and you should download this file again.

[thonayan99]

it runs BUT unfortunatly, they are same numbers/letter. it seems i have real corrupted memeory....so what is your advice now.

[SubCore]

i'm sorry, there is nothing more i can recommend other than returning it to nokia...

[thonayan99]

thanks...i thing that is it ...we will return it back to Nokia.

i just would like to appreciate all those memebrs who helped me here and it seems that maome problems never solve even u got version 5....after 2 hours using the device it get memory corrupted .huh.

please take care all.

[chemist]

I dont have the problem as I dont have a n900 yet but looking at this thread it drives me nuts. people posting linux commands to solve a windows guys problem... the wiki is missing it out aswell, I wont edit it as I have no clue what the procedure does look like. (there is a windows section but is it realy any help for someone who doesnt know how to use a command-line?)

are there different versions of eMMC flash bins or is this for all the same?

as far as I understand the wiki pages, you flash the eMMC first and then you need to flash the FIASCO image. so if he's able to flash the FIASCO but the eMMC we are stuck their.

maybe someone with knowledge of memtests and eMMC testing might know some test he could do with a terminal to post the results to us

[FC_]

I dont have the problem as I dont have a n900 yet but looking at this thread it drives me nuts. people posting linux commands to solve a windows guys problem
You really don't have to use any of these command line tools if your N900 isn't broken. This is really a last-resort measure, with any other phone you'd have probably already returned it to the manufacturer.

And "memtest" is for checking your RAM, and our problem is/was that the internal flash memory was corrupted.

[thonayan99]

You really don't have to use any of these command line tools if your N900 isn't broken. This is really a last-resort measure, with any other phone you'd have probably already returned it to the manufacturer.

And "memtest" is for checking your RAM, and our problem is/was that the internal flash memory was corrupted.

thanks. what is killing me is i just buy and used the device and start using it immedailty and only 2 hours and screwd up immedatliy with this memeory corrupted. when I first switch on the mobile it was showing me 32GB perfectly with around 2 GB used. it is never fall from my hands or shake it or get sharp chock...

the thing amazing me that you refer that device get broken internaly as you state while it is on my hand for the 1st 2 hours peroied. it is driven me crazy....now i need to wait more than a week to return it back to nokia for a personal reson i have.

[rm42]

Sorry if you answer this before, but did you ever answer the questions some of us asked you about whether or not you enabled any extra repositories, such as the "extras" or "extras-devel"?

[thonayan99]

Sorry if you answer this before, but did you ever answer the questions some of us asked you about whether or not you enabled any extra repositories, such as the "extras" or "extras-devel"?

no, i just went ot the application manager and start to download only the Bounace game then memory corrupted.

[thonayan99]

ANY ONE...
Could we do formatting using the keypad numbers or does it have somthing hardware to press it to get back to out of the box state.

[Bundyo]

The EMMC ROM is doing that. It is meant to format your internal flash and put on it its original content. The other ROM on the site is for reflashing the OS itself (which you already did). So you need to flash the EMMC ROM to fix your device or to return it and get a new one. Can you try flashing on different Windows than 7?

[thonayan99]

The EMMC ROM is doing that. It is meant to format your internal flash and put on it its original content. The other ROM on the site is for reflashing the OS itself (which you already did). So you need to flash the EMMC ROM to fix your device or to return it and get a new one. Can you try flashing on different Windows than 7?

thanks for the good suggestion, wil do and see.

[thonayan99]

Yes finally it works well at last for the eMMC flashing with WInd XP SP3 BUT give me the following error in the command:

"Raw data transfer EP found at EP2
Using flashing protocol MK II.
AU_GET_UPDATE_STAATUS_REQ terminated with error code 1"

the falshing of the firmware image was done in both Wind 7& xp without problem but need the above eMMC flashing for completed device restore.

ANY ONE COULD HELP......

[thonayan99]

N900 experts could you help pls....

[thonayan99]

no answer....mmmm...I think it is the time to go back to Nokia...

[mklass]

Could some one please help me?

Ive managed to flash the OS using

cd "c:\Program Files\maemo\flasher-3.5"

flasher-3.5.exe -F RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin -f -R

But I cant flash the eMMC for some reason. Im using,


./flasher-3.5 -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM -f -R


This is not working for me when Im in the command prompt under,

c:\Program Files\maemo\flasher-3.5

Please please help ?

[lemmyslender]

Could some one please help me?

Ive managed to flash the OS using

cd "c:\Program Files\maemo\flasher-3.5"

flasher-3.5.exe -F RX-51_2009SE_1.2009.42-11_PR_COMBINED_MR0_ARM.bin -f -R

But I cant flash the eMMC for some reason. Im using,


./flasher-3.5 -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM -f -R


This is not working for me when Im in the command prompt under,

c:\Program Files\maemo\flasher-3.5

Please please help ?

it looks like you have mixed windows and linux commands. If the first one worked, it looks like you are using windows. Thesecond command should be

flasher-3.5.exe -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM -f -R

[mklass]

I figured it out now...

[netblade]

I bought the device yesterday and had a similar problem. After using the device about 5 hours, suddenly it reboots and lost all the data. Reports only that "internal memory card format is not supported". In settings -> memory it says that the internal memory card is corrupted.

Wen't to Nokia Flagship store today and in 10 minutes time I got a new device. I'm just hoping that this doesn't happen again. Luclily, my wife's device (bought also yesterday at the same time) works like a charm.

[smssa2000]

hi all
i bought my n900 first time with rebooting issue and return it back to Nokia care and today i got other new n900 unit but with memory card corrupted issue

first thing i checked the memory card slot and installed micro SD and it works fine.

after that i re flashed eMMC and the image and this solve the problem at all.

But i did that by MAC OS X not on Windows.

thanks

[afrimi]

sorry form my bad english i have had same problem but i resolve it
firts conect n900 to pc ant put in mass storage
second go to removable disk G propertis and format but quick format.whait little bit and thats it.

[Dexter1759]

sorry form my bad english i have had same problem but i resolve it
firts conect n900 to pc ant put in mass storage
second go to removable disk G propertis and format but quick format.whait little bit and thats it.

Last weekend, me & my OH were tidying out some stuff we had chucked in a cupboard. And I came across the memory card that used to be in her 5800, so thought I'd pop it in to my N900.

It saw it and worked a charm but had loads of 5800 related crap on it. So, on my N900, I selected the Format option on the memory card and since then it has said "Memory Card Format Unsupported" whenever I select it in File Manager.

I've tried the Quick Format option in Windows, but with no luck.

Any help would be appreciated.

I have had a quick skim read though this post but most of it's talking about stuff I don't understand!

Many thanks,
Dex

[sophocha]

Mine says corupted as well!I`ve had the card in my 5800 and it was fine for a year, so I`m positive my card is not corrupted.

I`ve tried making an ext2 partition in Paragon Partition Manager on a windows xp machine (yes! it does work!).What kind of partition does the N900 require??There are a bunch of option in paragon 0x82 0x83 0x84 and so on ( linux hidden, extended, blabla).Do I assign a letter to the partition as well?

Any help appreciated

Thanks

[Rob1n]

Mine says corupted as well!I`ve had the card in my 5800 and it was fine for a year, so I`m positive my card is not corrupted.

I`ve tried making an ext2 partition in Paragon Partition Manager on a windows xp machine (yes! it does work!).What kind of partition does the N900 require??There are a bunch of option in paragon 0x82 0x83 0x84 and so on ( linux hidden, extended, blabla).Do I assign a letter to the partition as well?


The N900 requires a standard FAT32 partition (0x0b), and there's no need to bother assigning a drive letter.

[sophocha]

The N900 requires a standard FAT32 partition (0x0b), and there's no need to bother assigning a drive letter.

I thought that the memory card must be formated in ext2??Am I wrong?I`ve already tried FAT32 and it is not recognized

[Rob1n]

I thought that the memory card must be formated in ext2??Am I wrong?I`ve already tried FAT32 and it is not recognized

No, it should be FAT32. You may want to look at this thread (http://talk.maemo.org/showthread.php?goto=newpost&t=43913), which may be the same issue.

[sophocha]

No worries, I got it working....I`ve made the card unallocated, then formated again with FAT32, put it in and presto it is recognised.

Thanks

[Rob1n]

No worries, I got it working....I`ve made the card unallocated, then formated again with FAT32, put it in and presto it is recognised.

Thanks

That's probably done the same thing, yes - if the initial partition was p4, then changing the type wouldn't help. Making it unallocated will delete all partitions, then when you create the new FAT32 partition it will be p1 instead.

[young-crisis]

G: could be explained if you have no microSD in.

hard to say what is wrong about internal flash.

ey,
evn i got da same problem wat u got with ur n900.
it doesnt show 32gb, its says device memory is corupted.
and so i cant open any applications evn cz its says not enough memory. cant evn open da camera.its jus lyk a dummy phone wid jus makin and recieving calls.

plz if u gt urs fixed let me knw how and if gt mine 1st i will let u knw.

thanx.

[MaxyOne]

Bad post
Same problem here
If i turn off the n900, i can acces the mass memory
LE:
I have a quick question for u guys:
If i wanna flash the emmc, i have to use the flash vanilla emmc, and then flash with any firmware i want?
I need the answer ASAP.
LLE: Ive flashed the emmc, and last firmware, and now i got restart loop and memory card error.
The thing is, i can navigate into mass memory when the phone is off.
This is a fw bug i think, because the mass memory is not broken.
Any solutions?

[MaxyOne]

C'mon guys, i really need to fix this problem.:(

[Rob1n]

C'mon guys, i really need to fix this problem.:(

Check the MD5 sums for the firmware files against those given on the Nokia firmware site - they may have been corrupted during the download. Otherwise take it in to a Nokia Care centre.

[MaxyOne]

i don't know what to say...if that is the problem, why i dont have the same problem if i install 2 times, the same FW?
First time, i cant use the sim card, them i cant access the memory, and now, i get constant resetloop.
If it's a hardware problem, why do i get different results?!
Can someone tell me how to update the eMMC firmware and the firmware?
In wiki, we have, the fw update, and below, the eMMC update.
At the top, on eMMC image, it sais that we should not boot the device.
what is the correct procedure, to update the FIASCO and then the eMMC, without booting the device?
I've tried to remove the -R at the end of FIASCO command line, but i get some error when i'm trying to update the eMMC.
The error is something like this: "SU_PREPARE_DATA_BLOCK_REQ"
Thank you for your time.

[beli]

If you see it as mass storage device, can you run fsck or chkdsk to scan the drive for errors or bad blocks?

I returned my device 3 weeks ago with corrupted internal memory ... hope to get it back fixed soon ...

[MaxyOne]

There are no bad blocks, if i use other firmware, the mass memory is working, but then i get no sim card error....
Sometimes is the mass memory corrupted, sometimes i get no sim card error, and sometimes i get reset loop...

[wrega]

i just cannot reflash emmc with vanilla. error code 1 keeps apearing. For this reason my phone looks like a dummy as well. (32Gb corrupted)

[gepataki]

hi guys,
i gently read this talking forum, cause had the same problem. devices internal memory card corrupted.
but i cant do any flashings, for treason i dont know.
could you please help, what does it mean?
(i have xp as ubuntu as well..)


reg
gepataki

[gepataki]

well, the problem might be mounting failure, i can use the device under xp, it is a 27 gb drive. also by ubuntu.
the phone doesnt want to know it, or mount it.
any suggestion?
thx
gepataki

[setare2006]

Hello............
I have a n900 ...32gb hard drive does not show it inside the phone, but the computer shows ,the format will ,flash with 3 bin file but I did not just lead the way
Please help me..................................

[Rob1n]

Hello............
I have a n900 ...32gb hard drive does not show it inside the phone, but the computer shows ,the format will ,flash with 3 bin file but I did not just lead the way
Please help me..................................

I'm not sure I'm following you - are you referring the the internal 32gb memory, or a 32gb microSD card? If the internal memory, have you tried reflashing the eMMC?

[setare2006]

I'm not sure I'm following you - are you referring the the internal 32gb memory, or a 32gb microSD card? If the internal memory, have you tried reflashing the eMMC?

hard device 32gb

[setare2006]

reflashing eMMc
I sure is explained in this way Reflashing Memory
thankss..

[winslet]

if you are having problems with your memory card then in 80% of the case there is the issue of memory card corruption. The main reason behind this corruption is virus attack, pulling out of memory card while the phone was on, taking photos when the phone's battery is very low, etc. All these issues leads to memory card corruption problems. When this issue occurs you must stop taking the photos and try to recover first the lost photos. YOu can do it by using a good memory card recovery (http://www.memorycardrecovery.biz) software program. From online you will find numerous.

[setare2006]

if you are having problems with your memory card then in 80% of the case there is the issue of memory card corruption. The main reason behind this corruption is virus attack, pulling out of memory card while the phone was on, taking photos when the phone's battery is very low, etc. All these issues leads to memory card corruption problems. When this issue occurs you must stop taking the photos and try to recover first the lost photos. YOu can do it by using a good memory card recovery (http://www.memorycardrecovery.biz) software program. From online you will find numerous.

Hello ,,,THANKS..
What Can I sort my problems hard to solve your phone
Now the problem has to find the phone hard
Hard way what the problem?
Take a problem from the phone or what kind of phone plan is solved??
THANKS......

[abill_uk]

I had this memory card corrupt and i switched off the N900 took out the micro sd card then replaced it and turned back on after that everything back to normal, i do find the micro sd slot somewhat awkward not like the normal Nokia slot that you just push in and if you dont get the 2 tiny tounges under the plastic lips the micro sd card does not seat properly hence future problems like "memory card corrupt" Hope this is a help.

[varac]

I have good news for you all - I had the same problem, my internal 32GB memory card was corrupted.
i found out that the culprit was the big VFAT data partition, /dev/mmcblk1p1, that usually should be mounted on /home/user/MyDocs, but it wasn't.

I ssh'ed to my N900, tried to mount i manually,

mount /dev/mmcblk1p1 /mnt

but got an error.
After i formatted it with

mkfs.vfat -F 32 /dev/mmcblk1p1

and rebooted, everything was fine again !

Hope it will be as easy as at my place,

cheers varac

[khristi80]

i've just got this issue yersteday when i took my phone from a repair job(phone was not charging anymore)
i had to replace mmcblk1p1 with mmcblk0 and it worked
mkfs.vfat -F 32 /dev/mmcblk0

thanks varac for info....otherwise i would have to send the phone to repair centre again and wait for another 3 weeks

[varac]

> i had to replace mmcblk1p1 with mmcblk0 and it worked
> mkfs.vfat -F 32 /dev/mmcblk0

Please be careful ! It looks like the disk numbering depends on whether or not there is an external micro-sc-card inserted or not.

On my device /dev/mmcblk0 ist the whole *external* memory card.
/dev/mmcblk1p1 ist the first partition of the *internal* memory card.

So, be warned - know what you do ! There are even different Filesystems on the interal memory card (/dev/mmcblk1p1 is FAT32, /dev/mmcblk1p2 is ext3).

And please be clear *which* memory card is the problem - internal or external (i mean the micro-sd-card slot).

[khristi80]

the problem wasn't solved.....after that i have recovered my 32gb memory but my phone wasn't working.....only making and receiving calls....always was getting the msg 'operation disabled due to low memmory"(available memory for installable applications was only around 100mb)
i have flashed the device... the fiasco&emmc and after that my phone is working like before except that i have again device-memory card corrupted
if i enter mount /dev/mmcblk1p1 /mnt i get this message "no such file or directory" and after mkfs.vfat -F 32 /dev/mmcblk1p1 i get the same message
if i enter /dev/mmcblk0p1i get the message "device or resource busy" and after mkfs.vfat -F 32 /dev/mmcblk0p1 i get "mkfs.vfat: /dev/mmcblk0p1 contains a mounted file system"
i think maybe the problem is with the device partitioning .....but i don't know how to do that
any help?

[khristi80]

i have managed to solve the problem
partitioning the flash has solved the problem
now everything is working ...it's like new :)

[khristi80]

the problem it seems is not solved

if i switch off or reboot the phone then i get again memory card corrupted but after i type on xterminal rm -rf /home/user and reboot after that the memory ´comes back´ but on next reboot or power off the memory becames corrupted again

i'm not an expert so any sugestions?

[angelo0015]

I have this same problem, 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.
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. Typing the command that khristi80 posted rm -rf /home/user and then rebooting everything works again but after the next reboot back to the same problem

[Unhuman]

My N900 bricked after I installed Nitdroid and played with it a bit too much it seems. So I just reflashed with the "Latest Maemo 5 Global release for Nokia N900 " according ot the guide on the wiki. Now I get "Low memory usage" + "Memory card corrupted" (aka internal memory, I removed my external micro SD card).
In /dev/mmc* I only have - "mmcblk0" and "mmcblk10p1". Any suggestions ? :X

EDIT:

When plugged as mass storage mode into a windows system - Windows says the drive has a unfamiliar file system and must be formated.

[xscorpioplus]

I had the same kinda thing...

Memory card not found yet PC can read it...

I have done almost all things... which on net...

Last resort: Flashed my n900


1. Downloaded (http://tablets-dev.nokia.com/nokia_N900.php)
• flasher-3.5.exe
(http://tablets-dev.nokia.com/maemo-d....5_2.5.2.2.exe)
• RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin
(http://tablets-dev.nokia.com/nokia_N...ED_MR0_ARM.bin)
• RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin
(http://tablets-dev.nokia.com/nokia_N...MC_MR0_ARM.bin)

2. I installed the "flasher-3.5.exe"
3. I then moved
"RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin"
"RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin"
To the directory where I installed the flasher (Default is C:\Program Files\maemo\flasher-3.5).
4. I then done a full backup of my N900 using the backup tool on the phone and moved all my stuff on to the memory card.
5. Ensure the battery is at least half full.
6. Unplug charger cable and switch off the device.
7. Open the Command Prompt (Start then Run or Windows Logo key + R) and type "cmd" then press Enter (this will open a black window).
8. Change the directory to the Flasher's path by typing in "cd "%ProgramFiles%\maemo\flasher-3.5"
9. Hold the u key on the device keyboard and connect the USB cable at the same time.
10. Run the following command by typing:
"flasher-3.5.exe -F RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin -f"

After this completes

11. Run the following command by typing:
"flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R"

The flash will take around 1 minute after which the device will reboot.
The bright Nokia screen will come up on the screen with the USB icon on the top right followed by progression dots with yellow LED blinking for a few seconds
And you’re done. Welcome to the world on 1.2

Next now nokia can saw an corrupted memory card.

Then format it with nokia inbuilt formatting process.

thats it.. working fine now..

[ivyking]

people having trouble with the internal memory , connect your n900 to pc , choose mass storage mode , use disk utility in ubuntu / chkdisk on windows to try and repair the file system or reflash the emmc vanilla image via flasher.

[keflex]

Quick question here (loosely related to this topic, didn't feel like starting up another one): Bought a 32GB microSD just now, the File Manager says it's not supported and long-pressing in the Manager to format it doesn't give me any sort of confirmation ever after long periods of waiting. Is this meant to be the case?

Also tried formatting on Windows via Disk Management & EASEUS Partition Manager. No luck there either, but both programs read the card as only having 30MB. I purchased it from a 3 Store, so I can be relatively assured as to its capacity. Did I just happen to get a dud?

[Parlapipas]

Quick question here (loosely related to this topic, didn't feel like starting up another one): Bought a 32GB microSD just now, the File Manager says it's not supported and long-pressing in the Manager to format it doesn't give me any sort of confirmation ever after long periods of waiting. Is this meant to be the case?

Also tried formatting on Windows via Disk Management & EASEUS Partition Manager. No luck there either, but both programs read the card as only having 30MB. I purchased it from a 3 Store, so I can be relatively assured as to its capacity. Did I just happen to get a dud?

Did you try formatting as fat32 or ntfs? If ntfs, try fat32 on either a pc or mac and give it another go.

[bob555]

hii,am using n900 from past 11 months ,but few days bak i came across a strage problem after conecting it to my pc,my memory i.e internal 32 gb memory has corrupted.then i imidiately took it to the nokia care they it for 2 days returned it to me by saying harddisk corrupted.can any one pls suggest me how to solve this prob.

[tranthao]

Dear, i have the same problem with the 1st post.

i try to accessmouny /dev/mmcblk0p1
dd: cant open /dev/mmcblk0p1 : permission denied
I try : kill /dev/mmcblk0p1
sh: bad pid kill /dev/mmcblk0p1

what should i do now ?

[Raymodise]

Hi,
Please I need help. suddenly I have memory corrupted after i buy the device couple of hours ago. here what happened:

1. i switch on the device, then i explore it and start to download some application from the application manager.

2, meanwhiel, I went to the web browser and it sayd " Operations temporarliy disabled due to low memory".

3. when i start reciving SMS messages i see the preview but could not open it as another message appear " close applications".

4. the ovi map can't started and closed immedaility and I can't open any other application.



then i went to the file manager and i want to access the device internal memory "sfil_li_memorycard_internal" a message then appear " Memeory card format unsupported".

i went through setting> phone > memory and i found that a message wirtten under the device "memery card courrupted" and before that probelm it was showen 32GB as it is the internal deviced memeory.

the external momery are shown to be ok.

the solution i think of is to upfdate the softwear and i found that there is no new update using Nokia softwear update. then i just re-update with the same version but NOT SOLVED.


PLEASE ANY SUGGESTION BESID SENDING IT BACK TO THE NOKIA.




the only thing i can do is just using the device to call.

thanx

I have the same problem with my internal phone memory, i tried to restore original settings but that didnt help. And again the mass storage connection doesnt work, so i cannot format the phone,
Any help??
And again, i am new to this linux thing, so i will appreciate your help to be in a simple way

[jiangziran]

excuse me. your n900 is ok?
my n900 has had the same matter with yours. I just can use it to phone. But sometimes it would be ok and it shows 32g storage perfectly. unfortunately it would rertart in few minutes. and I cant flash with emmc. PC always said device can not be found. have you got any idea? please help

[erg]

I have the same problem. My phone is one year old, 4 times at Nokia Care 2 weeks every time, and ever repair (I think only reflash it), some days later, damaged again. The last time Care say no more repairs, is my fault. MY FAULT? I like a new one. No, it's your fault.

Thanks Nokia for nothing.

Any solution at this time for this problem?

Thanks in advance, and excuse my poor english.

[michaaa62]

You need rootsh from extras repository installed for each of these steps in X-Terminal application:
Easiest solution, if you have no data in the MyDocs folder at all, or you could replace the data easily from your PC, apply a fresh new file system to the partitionsudo gainroot
mkfs.vfat -n MyDocs /dev/mmcblk0p1
If you want to retrieve the data on the phone do not apply a fresh file-system, but check and repair the file-systemsudo gainroot
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
This might be sufficient to get your data back, but depending of the actual corruption additional steps might be necessary.
Please disconnect the phone really careful from your PC every time, give the two systems (PC and Phone) enough time to sync the writing!!!

[JoOppen]

Hi michaaa62. Saw your posts in several threads and followed your advise. However, my problem seems a little bit different. Yesterday I lost all my personal data in MyDocs. I do not know why or how - it was definitely before the thunderstorm over Berlin so I can not blame the weather.

Here are the symptoms:

All my personal files on MyDocs (including Easy Debian image etc.) disappeared

However, "new" and empty MyDocs is there

Memory in Settings menu only shows 27 GB internal Memory

So I assume my "old" MyDocs has gone somewhere I have no direct access to

So far testdisk (thank you for the hint) did not help me to retreive my old MyDocs

Further symptom: when tethered to the Mac, no N900 symbol appears on the Mac desktop for N900's internal memory anymore (as it used to be previously) but only an "untiteled" disk.

Any idea how i could retrieve my "old" MyDocs?

Thank you in advance

[michaaa62]

What does sfdisk -l give you about the card?
sudo gainroot
sfdisk -l

[JoOppen]

What does sfdisk -l give you about the card?
sudo gainroot
sfdisk -l

It took a while until I learned how to create a file withe the output of sfdisk -l (o.k. if you know it, it is really easy, but I am a true greenhorn). Here it is:


Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 1 884864 884864 28315648 c W95 FAT32 (LBA)
/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux
/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris
/dev/mmcblk0p4 0 - 0 0 0 Empty

Disk /dev/mmcblk1: 120576 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 3560448 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk1p1 1+ 1109- 1109- 3854336 b W95 FAT32
/dev/mmcblk1p2 0 - 0 0 0 Empty
/dev/mmcblk1p3 0 - 0 0 0 Empty
/dev/mmcblk1p4 0 - 0 0 0 Empty

I am unable to interpret this information. I suspect that mmcblk1 is my 4MB SD-card

Does this information mean anything to you?

[michaaa62]

This looks okay, the output is your partitiontables from the internal and the external card. MyDocs is just the folder the N900 needs to have some place to mount the internal card to.

But i must admit, i am awfully confused that testdisk failed to recover the files in that partition. Please try to fsck the partition once againsudo gainroot
fsck -af /dev/mmcblk0p1Even try the 'r' option for file-system repairs pleasefsck -r /dev/mmcblk0p1

[JoOppen]

Thanks again.

My N900 is almost normal: I have a MyDocs Verzeichnis, but it is apparently a new one without those files I saved before some mysterious event yesterday morning - just those files Meamo apparently creates itself if MyDocs is lost.

And: N900 (internal memory) looks different when hooked to the Mac in Massenspeichermodus, no N900 symbol as it used to be until yesterday.

This is what fsck -af delivered:


fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Reclaimed 1 unused cluster (16384 bytes) in 1 chain.
Free cluster summary wrong (1768780 vs. really 1768779)
Auto-correcting.
Performing changes.
/dev/mmcblk0p1: 68 files, 84/1768863 clusters

This is what ls -a in MyDocs delivered


.
..
.Spotlight-V100
.Trashes
._.Trashes
.camera
.documents
.fseventsd
.images
.sounds
.videos
Podcasts
gpsrecorder

However, .sounds, .documents etc. are all empty and used to be full of stuff.

[michaaa62]

First try to reboot after the successful fsck to see if things went really successful.

Maemo always creates some of the mentioned folders anyway, because Nokia in their .... wisdom never
thought about the possibility, that vfat is a sensible file-system to been mishandled by PCs. Those other folders are created by MacOS.

[JoOppen]

I rebooted - no apparent effect.

Last night I looked a the creation dates of the files on a Windows computer (N900 tethered in mass storage mode) and found that these files where created while I was sitting in a train to the airport reading the latest news on the N9 via 3G. I am not aware of any event that could have triggered the creation of a new file system (or the loss of my old MyDocs). However, it happened.

Now I discovered further strange behaviour: when tried to restore some old data from an OVI suite backup (what I made only early April, blame me) the data was neither complete nor stored where it was. Instead, a "dev" file within MyDocs was created that now contains some data including a futher .sounds and .documents file.

At least the Easy Debian image was there and I had to move it to MyDocs in order the have it in proper place

When I then started Easy Debian hoping it would work I received the following notice:

EZ-CHROOT ERROR

Mount failure!

/home/user/MyDocs/debian-m5-v3d.img.ext2.lzma failed to mount on loop0

mount: mounting /dev/loop0 on /.debian failed: invalid argument

Meanwhile I come accustomed to the fact that part of my files are lost. So, now it is all about recreating a reliable device.

[michaaa62]

Did you try testdisk in both modes, like Fat Undelete hidden in Advanced and Analyse?

[JoOppen]

Did you try testdisk in both modes, like Fat Undelete hidden in Advanced and Analyse?

How do I activate these modes? To answer your question: no, I did not, because I do not know how.

BTW, battery drain is tremendous now like operating hours is now maybe less than 6 hours whereas it used to be more than 30 hours (with almost no use, off course)

[michaaa62]

Testdisk is an data recovery tool fittingly from the recovery-tools package, you will get it here http://maemo.org/downloads/product/Maemo5/recovery-tools/ or by sudo gainroot
apt-get update && apt-get install recovery-tools
May be you have to enable extras-testing and/or extras-devel repositories.
You will find a short walkthrough here http://talk.maemo.org/showpost.php?p=933433&postcount=46

[JoOppen]

I have used testdisk because I found your instructions in some other thread two days ago. However, I do not know how to use testdisk in both modes, like Fat Undelete hidden in Advanced and Analyse. With advanced, I found a file that I have intentionally deleted myself the other day.

I could not see any of my "old" files. I suspect that is because there is a "new" data structure ("new" MyDocs) so I can not get to my "old" MyDocs in a regular manner.

Considering the overall strange behaviour of what used to be my favourite tool I am now contemplating reflashing the device. However, I learned that this does not neccessarily leads to a clean MyDocs.

[michaaa62]

Did you make a new filesystem after you lost access to the files?
Let testdisk analyse your device with quickly, then hit enter and choose 'Deeper Search', afterwards let it show you the files and folders on the first partition with 'p' . Good luck!

At the end of a day, well, i think there are different series of the N900 around. There are rocksolid devices, where it really is difficult to get your file-system borked, and there is, ahem, yours and some others.... It is the same for overclocking.

[JoOppen]

To be fair: I can not blame the N900 for any true failure. Maybe it was a bit immature when it was released. I am now using it way more than a year oftentimes 2 or 3 hours a day incl. Citrix under Easy Debian etc.

And I poked allot around with it - only semi competent (if at all). The kids are tossing it around and do many thinks I later do not really understand. And I never lost anything - until Tuesday.

My old iMac was much wore in that respect (terribly unreliable) and any Windows machine I owned or used is the same. Compared to Apple or Microsoft, the N900 is really reliable (that is why I did so little backups :-( )

This makes me think of what I expect from a pocket device (not calling it a phone): I enjoy the freedom to play around on every level and I am willing to take the risk to thereby brake something. I see the drawback (some inconsistency included) but prefer it over a closed device like otherwise elegant iPhone.

To continue off topic: that is the reason I put some hopes on Meego.

Back to the topic: I run Testdisk as described and learned that the disk is to small because it is smaller than some 35000000 TB. And some of the Linux partitions can not be recovered. I assume that the relates to now disfunctional Easy Debian, which is not a problem.

I will now try some forensic tool and will report.

[tvsakpal]

Hi All,

i am new to this site. I am unable to access internal memory on N900. It shows 'Memory is corrupted'. the phone is not even detected when i connect to PC vis USB using mass storage mode.

Well I did a blunder by executing KILLALL in X-terminal yesterday. all my personal stuff that I had saved in my internal 32 gb is lost.

Experts - do you think my internal memory is corrupted due to KILLALL command. is there anyway to have it back with my personal stuff.

Thanks in advance for your support.

Tushar.

[michaaa62]

You need rootsh from extras repository installed to get this working.
If you want to retrieve the data on the phone, check and repair the file-system

sudo gainroot
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
This might be sufficient to get your data back, but depending of the actual corruption additional steps might be necessary.

[tvsakpal]

Thanks Mich....

I have rootsh installed. I will try to do what you are suggesting. I will keep you posted in my progress.

[tvsakpal]

Dear All,

Finally I am able to get my 32 GB memory back;)

Well two my office colleagues helped me and we used the codes give my Mich to format the 32 GB internal memory. Well most of my data was recovered. Here is what we followed

1) Connected n900 to my pc which has data recovery tool. I was able to recover upto 1GB (free version) data from my corrupted memory.

2) Formatted the 32 GB memory (only 28 GB partition) using Mich's codes and re-mounted the same

3) Copied the data from my computer.

Well I am using it for 2 days now and it is working like a brand new piece. One more advantage is I have all my old softwares / downloads in tact as only the 28 GB partion was formatted. Hence no need to downlaod those again.

Thanks to my two friends (one is prog. xpert and other from IT) amd Mich, it was time consuming but bettter than flashing....

Thanks again to maemo.org....this is a fundu forum and I don't have to serach google for my queries. It's all here.....good going...

[swatibings]

Hi,
Please I need help. suddenly I have memory corrupted after i buy the device couple of hours ago. here what happened:

1. i switch on the device, then i explore it and start to download some application from the application manager.

2, meanwhiel, I went to the web browser and it sayd " Operations temporarliy disabled due to low memory".

3. when i start reciving SMS messages i see the preview but could not open it as another message appear " close applications".

4. the ovi map can't started and closed immedaility and I can't open any other application.



then i went to the file manager and i want to access the device internal memory "sfil_li_memorycard_internal" a message then appear " Memeory card format unsupported".

i went through setting> phone > memory and i found that a message wirtten under the device "memery card courrupted" and before that probelm it was showen 32GB as it is the internal deviced memeory.

the external momery are shown to be ok.

the solution i think of is to upfdate the softwear and i found that there is no new update using Nokia softwear update. then i just re-update with the same version but NOT SOLVED.


PLEASE ANY SUGGESTION BESID SENDING IT BACK TO THE NOKIA.




the only thing i can do is just using the device to call.

thanx

Hi,

I have the same problem with my n900
i can only make and receive phone calls and see previews of sms's

i was told my hard disk is damaged and this is not repairable

Is there anything i can do???

[swatibings]

I have the same problem with my internal phone memory, i tried to restore original settings but that didnt help. And again the mass storage connection doesnt work, so i cannot format the phone,
Any help??
And again, i am new to this linux thing, so i will appreciate your help to be in a simple way

Even i have the same problems with my N900
any solutions please???

[hhmah]

sudo gainroot
umount /dev/mmcblk0p1
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs

[hhmah]

i had the same problem... here wht i did....


~ $ 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:~# mkfs.vfat -n MyDocs /dev/mmcblk0p1
mkfs.vfat 2.11 (12 Mar 2005)
Nokia-N900:~#

then enter

sudo gainroot
umount /dev/mmcblk0p1
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs

than this came up
Nokia-N900:~# sudo gainroot
root is not in the sudoers file. This incident will be reported.
Nokia-N900:~# umount /dev/mmcblk0p1
umount: cannot umount /dev/mmcblk0p1: Invalid argument
Nokia-N900:~# fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/mmcblk0p1: 1 files, 1/1768863 clusters
Nokia-N900:~# mount /dev/mmcblk0p1 /home/user/MyDocs

checked my file manager and it was there.. the device memory. pressed on it and it saw the folders but they were empty.

checked memory from the setting and still it says memory corrupted, than went bk to the file manager and formated the Nokia N900, than checked again on the setting and finally it was back.

http://talk.maemo.org/showthread.php?t=71702&page=2

[swatibings]

hey thanks for the piece of code

but as i enter the first line 'sudo gainroot'

it says: Enable RD mode if you want to break your device

shld i continue with the rest of the code?

can u please specify the steps from the beginning?

thanks again

[hhmah]

hey thanks for the piece of code

but as i enter the first line 'sudo gainroot'

it says: Enable RD mode if you want to break your device

shld i continue with the rest of the code?

can u please specify the steps from the beginning?

thanks again


check this thread http://talk.maemo.org/showthread.php?t=71702

i dont kno wht i did, just try all the codes in that thread

[swatibings]

thanks for d help
tho my prob still is not solved
i hv a prob with my hard disk only
still getting the same memory low errors :(
thanks anyways

[markarman]

Hello,

Here is my problem.

settings->general->memory:

device:
(memory cards corrupted)

memory for installable applications
50.8MB available

So, there are no my 32GB...

In addition, when I get plugged my n900 to PC, a can see two new disks. When I open (explorer) first, I get the message "format or not...". When try to open second, message received "pleas insert disk to drive G:"

Thank you in advance

The Maximum size card the N900 accepts is 16GB

http://europe.nokia.com/find-products/devices/nokia-n900/specifications

[acantonyclark1]

If your memory card shows less space then it is either corrupted or virus infected. You should try formatting the card to correct the problem. If you want to recover data then you will need to go for memory card recovery software.

[sixwheeledbeast]

The Maximum size card the N900 accepts is 16GB

http://europe.nokia.com/find-products/devices/nokia-n900/specifications

I release this thread is old and has been bumped, but this is incorrect I have used a 32GB SDHC Card and currently use a 64GB SDXC Card with no problems.

One thing that can make the card show as "corrupt" is, if you have swap partition(s) on it and the first partition isn't your data one.

[juwelahamed]

Hello,

Here is my problem.

settings->general->memory:

device:
(memory cards corrupted)

memory for installable applications
50.8MB available

So, there are no my 32GB...

In addition, when I get plugged my n900 to PC, a can see two new disks. When I open (explorer) first, I get the message "format or not...". When try to open second, message received "pleas insert disk to drive G:"

Thank you in advance

yes ......same problem

[michaaa62]

Did you try to check the file system of the partition called N900 , you need rootsh installed to get this working:sudo gainroot
fsck -af /dev/mmcblk0p1
fsck -af /dev/mmcblk0p1
Yes, do it twice.
If no errors remain, you might reboot to check the state of the mass storage.

[Alecsandru]

I have memory corrupted on microsd , the pc recognizes it but the phone doesn't and can't format it , tried with fsck and mxfs , but without result any ideeas
?

[michaaa62]

Please show the X-Terminal output of mount
df
sudo gainroot
umount /dev/mmcblk0p1
fsck -af /dev/mmcblk0p1
for people to look at.

[willi6868]

I have memory corrupted on microsd , the pc recognizes it but the phone doesn't and can't format it , tried with fsck and mxfs , but without result any ideeas
?

If you care about your data you can recover it with Photorec of testdisk (http://www.cgsecurity.org/wiki/TestDisk) later :)

[Alecsandru]

fixed with gparted , created a new partition table - msdos -format to fat32 . without reflash and other things

[willi6868]

Hey I need help I hope someone is able to help me out :confused:
My memory card (4GB) corrupted and I am not able to access and format the card anymore. I tried it with Windows Vista and Ubuntu and both are not recognicing the card anymore. Also tried various software for backing up and restoring the partitions - without success (Also Testdisk does not recognice my card.. ). :( The card contains realy important stuff (have no backup) so pls help me out guys...

My output of (with attached memory card)

Please show the X-Terminal output of mount
df
sudo gainroot
umount /dev/mmcblk0p1
fsck -af /dev/mmcblk0p1
for people to look at.

is:

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.

~ $ 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)
/dev/mmcblk0p2 on /home type ext3 (rw,noatime,errors=continue,commit=1,data=writebac k)
/home/opt on /opt type none (bind)
cgroup on /dev/cgroup/cpu type cgroup (cpu,memory)
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,exec,nosuid,noatime,nodiratime,ut f8,uid=29999,shortname=mixed,dmask=000,fmask=0000, rodir)
~ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 233224 171296 57648 75% /
ubi0:rootfs 233224 171296 57648 75% /
tmpfs 1024 68 956 7% /tmp
tmpfs 256 76 180 30% /var/run
none 10240 76 10164 1% /dev
tmpfs 65536 4 65532 0% /dev/shm
/dev/mmcblk0p2 2064208 1507148 452204 77% /home
/home/opt 2064208 1507148 452204 77% /opt
/opt/pymaemo/usr/lib/python2.5
2064208 1507148 452204 77% /usr/lib/python2.5
/opt/pymaemo/usr/share/pyshared
2064208 1507148 452204 77% /usr/share/pyshared
/opt/pymaemo/usr/lib/pyshared
2064208 1507148 452204 77% /usr/lib/pyshared
/opt/pymaemo/usr/share/python-support
2064208 1507148 452204 77% /usr/share/python-support
/opt/pymaemo/usr/lib/python-support
2064208 1507148 452204 77% /usr/lib/python-support
/dev/mmcblk0p1 28312128 15320704 12991424 54% /home/user/MyDocs
~ $ 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 # umount /dev/mmcblk0p1
/home/user # fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
/dev/mmcblk0p1: 3254 files, 239386/442377 clusters
/home/user #

Does my N900 recognicing the memory card?! How can I format and/or backup the data?

[pichlo]

I am sorry, willi6868, but it looks like a hardware error. Flash cards do not last forever. I suspect your card is a goner and your data with it. There is a VERY small chance that something might be retrievable but I would not hold my breath.

You can try:

root
ls /dev/mmc*
sfdisk -l

to see if the card's hardware is recognized at all.

I once had a card that suddenly failed. It was an 8GB card. Following the failure, any system I tried it on recognized it as a 32KB card and could not write to it. There was no chance of recovering any data from it. Family pictures from the last two holidays gone just like that.

[michaaa62]

Additionally you might post the output of fsck -af /dev/mmcblk1p1

[willi6868]

Ohu dam* :(

here is the output:

~ $ root ls /dev/mmc* sfdisk -l


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:~# fsck -af /dev/mcblklpl
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: No such file or directory while trying to open /dev/mcblklpl
/dev/mcblklpl:
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>

Nokia-N900:~#

What does superblock mean?

But my N900 is recognizing the card in stock filebrwoser but it only tells that it doesn't support the format and that the memory card is damaged? !

[raaj13]

Ohu dam* :(

here is the output:

~ $ root ls /dev/mmc* sfdisk -l


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:~# fsck -af /dev/mcblklpl
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: No such file or directory while trying to open /dev/mcblklpl
/dev/mcblklpl:
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>

Nokia-N900:~#

What does superblock mean?

But my N900 is recognizing the card in stock filebrwoser but it only tells that it doesn't support the format and that the memory card is damaged? !

it's mmcblk1p1

mmcblk 1(one and not L) p 1(one and not L)

also correct command would be
fsck.vfat -af /dev/mmcblk1p1

[michaaa62]

Thanks for the clarification, raaj13.
Nevertheless, please use plain fsck to have the most relevant output of the command. The shell will choose automatically which of the file system specific commands to use. An error here might tell another story than an error for fsck.vfat.

[pichlo]

Looking at his output, fsck decided it was ext3 with invalid superblock. That doesn't look right, it should have been vfat. Try the commands I posted but one at a time please (3 lines).

Edit: Oops, missed the l vs 1 mishmash. Try again with proper spelling.

[willi6868]

Looking at his output, fsck decided it was ext3 with invalid superblock. That doesn't look right, it should have been vfat. Try the commands I posted but one at a time please (3 lines).

Edit: Oops, missed the l vs 1 mishmash. Try again with proper spelling.

sorry I don' understand what you mean :D How to use 3 commands at once? using ' l ' ?? :)

[michaaa62]

Sorry for the confusion:o. Three wise lads having a go at you :D

Just 4 commands please:ls /dev/mmc*
sudo gainroot
sfdisk -l
fsck -af /dev/mmcblk1p1

[willi6868]

Thanks for clarification :)

Here you go:

~ $ ls /dev/mmc*
/dev/mmcblk0 /dev/mmcblk0p2 /dev/mmcblk1
/dev/mmcblk0p1 /dev/mmcblk0p3
~ $ 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 # sfdisk -l

Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 1 884864 884864 28315648 c W95 FAT32 (LBA)
/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux
/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris
/dev/mmcblk0p4 0 - 0 0 0 Empty
/home/user # fsck -af /dev/mmcblk1p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
open: No such file or directory
/home/user #


What do you say?!:confused:

[pichlo]

Three wise lads having a go at you :D

Not at all! I did say one command at a time. Three separate lines.

Looking at willi's last output, the card is listedi n /dev but not in sfdisk output. That doean't look promising but you can try michaaa's fsck command without the p1, like so:

root
fsck -af /dev/mmcblk1

[willi6868]

Not at all! I did say one command at a time. Three separate lines.

Looking at willi's last output, the card is listedi n /dev but not in sfdisk output. That doean't look promising but you can try michaaa's fsck command without the p1, like so:

root
fsck -af /dev/mmcblk1

Here is the output:

~ $ 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:~# fsck -af /dev/mmcblk1
fsck 1.41.3.maemo0 (12-Oct-2008)
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk1
/dev/mmcblk1:
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>

Nokia-N900:~#


So what does superblock mean and should I run this command? :D

[michaaa62]

I would think the error results from no file systems found in /dev/mmcblk1, which should be no partition, but a full card. Linux does neither apply nor expect file systems in full devices.

The irritating fact that sfdisk does not note anything about the external card does not look good at all.
I would suggest to try the command once again after a full shutdown including the removal of the battery for a couple of seconds. After boot try to run the sfdisk command on that device only, again.sudo gainroot
sfdisk -l /dev/mmcblk1If that still does not give any output, try to create the partition table and after a reboot try to create the file systemsudo gainroot
echo "unit: sectors
> /dev/mmcblk0p1 : start= 16, size= 7554080, Id=c" > tableThis a crude estimate for a 4GB card. That size number might be too low, but will not give you an error. You might fine tune later. This command will give you a file, called 'table'. The name has no meaning, but will give you a clue what it is good for. Apply this file to the card as partition table:sfdisk --no-reread /dev/mmcblk1 < tableAny errors? If not, reboot to create the file system, either in HildonFileManager or in X-Terminalsudo gainroot
mkfs.vfat /dev/mmcblk1p1 -n microSD_4GBYou might skip the naming option, if you do not like a label for your devices.

Please interrupt for any errors in the command output!

Viel Erfolg!

[misterc]

did anyone try TestDisk & PhotoRec (http://maemo.org/packages/view/recovery-tools/) yet?
:p :o :)

EDIT: willi6868, if you have access to an *buntu PC, you might want to try to install those utilities there 1st (if you haven't yet)

[willi6868]

I would think the error results from no file systems found in /dev/mmcblk1, which should be no partition, but a full card. Linux does neither apply nor expect file systems in full devices.

The irritating fact that sfdisk does not note anything about the external card does not look good at all.
I would suggest to try the command once again after a full shutdown including the removal of the battery for a couple of seconds. After boot try to run the sfdisk command on that device only, again.sudo gainroot
sfdisk -l /dev/mmcblk1

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.

~ $ 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 # sfdisk -l /dev/mmcblk1

Disk /dev/mmcblk1: 0 cylinders, 4 heads, 16 sectors/track

sfdisk: read error on /dev/mmcblk1 - cannot read sector 0
/dev/mmcblk1: unrecognized partition table type
No partitions found
/home/user #


So he is recognizing the c but cant read it?:)

did anyone try TestDisk &amp; PhotoRec (http://maemo.org/packages/view/recovery-tools/) yet?
:p :o :)

EDIT: willi6868, if you have access to an *buntu PC, you might want to try to install those utilities there 1st (if you haven't yet)

Already tried it on a Windows Vista PC but it is crashing/ have a timeout and doesn't recognizing the memory card after the timeout like every other program/windows explorer I tried..

[michaaa62]

Looks like a corrupted partition table.

Please try the commands from the earlier post to create the table, then apply it to the card, reboot and hope for the best result...

[willi6868]

Badly got an error by applying the partitin table :(


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.

~ $ 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 # echo "unit: sectors
> /dev/mmcblk0p1 : start= 16, size= 7554080, Id=c" > table
/home/user # sfdisk --no-reread /dev/mmcblk1 < table

Disk /dev/mmcblk1: 0 cylinders, 4 heads, 16 sectors/track
read: Inappropriate ioctl for device

sfdisk: read error on /dev/mmcblk1 - cannot read sector 0
/dev/mmcblk1: unrecognized partition table type
Old situation:
No partitions found
Warning: given size (7554080) exceeds max allowable size (0)

sfdisk: bad input
/home/user #

[michaaa62]

looks like /dev/mmcblk1 is only in RAM, the card seems not be connected or attached to this device node.
Please try to get some output from the kernel via HALsudo gainroot
lshal | grep volume
lshal | grep VolumeAs this is case-sensitive and i am not sure which output to check for the external card please check this for both commands to find any reference to an external card.

Did you recently try to eject the card and re-insert it to avoid possible bad contacts of the card to the port?

[willi6868]

Reinserted the memory card before running the commands and my N900 showed me the message 'Speicherkarte beschädigt / damaged memory card'

Here is the log:

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.

~ $ 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 # lshal | grep volume
block.is_volume = false (bool)
udi = '/org/freedesktop/Hal/devices/volume_part3_size_805306368'
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
info.udi = '/org/freedesktop/Hal/devices/volume_part3_size_805306368' (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 = 1572864 (0x180000) (uint64)
volume.partition.flags = {} (string list)
volume.partition.label = '' (string)
volume.partition.media_size = 32015122432 (0x774400000) (uint64)
volume.partition.number = 3 (0x3) (int)
volume.partition.scheme = 'mbr' (string)
volume.partition.start = 31142739968 (0x740408000) (uint64)
volume.partition.type = '0x82' (string)
volume.partition.uuid = '' (string)
volume.size = 805306368 (0x30000000) (uint64)
volume.uuid = '' (string)
udi = '/org/freedesktop/Hal/devices/volume_uuid_9f274d7e_2306_4977_b3e6_079c43d03c46'
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_9f274d7e_2306_4977_b3e6_079c43d03c46' (string)
volume.block_size = 512 (0x200) (int)
volume.fstype = 'ext3' (string)
volume.fsusage = 'filesystem' (string)
volume.fsversion = '1.0' (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', 'acl', 'user_xattr', 'data='} (string list)
volume.mount_point = '/home' (string)
volume.num_blocks = 4194304 (0x400000) (uint64)
volume.partition.flags = {} (string list)
volume.partition.label = '' (string)
volume.partition.media_size = 32015122432 (0x774400000) (uint64)
volume.partition.number = 2 (0x2) (int)
volume.partition.scheme = 'mbr' (string)
volume.partition.start = 28995256320 (0x6c0408000) (uint64)
volume.partition.type = '0x83' (string)
volume.partition.uuid = '' (string)
volume.size = 2147483648 (0x80000000) (uint64)
volume.unmount.valid_options = {'lazy'} (string list)
volume.uuid = '9f274d7e-2306-4977-b3e6-079c43d03c46' (string)
udi = '/org/freedesktop/Hal/devices/volume_uuid_4BB1_E781'
block.is_volume = true (bool)
info.capabilities = {'volume', 'block'} (string list)
info.category = 'volume' (string)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_4BB1_E781' (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 = 'Nokia N900' (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 = '/home/user/MyDocs' (string)
volume.num_blocks = 56631296 (0x3602000) (uint64)
volume.partition.flags = {} (string list)
volume.partition.label = '' (string)
volume.partition.media_size = 32015122432 (0x774400000) (uint64)
volume.partition.number = 1 (0x1) (int)
volume.partition.scheme = 'mbr' (string)
volume.partition.start = 32768 (0x8000) (uint64)
volume.partition.type = '0x0c' (string)
volume.partition.uuid = '' (string)
volume.size = 28995223552 (0x6c0400000) (uint64)
volume.unmount.valid_options = {'lazy'} (string list)
volume.uuid = '4BB1-E781' (string)
block.is_volume = false (bool)
/home/user # lshal | grep Volume
info.product = 'Volume (swap)' (string)
info.interfaces = {'org.freedesktop.Hal.Device.Volume'} (string list)
info.product = 'Volume (ext3)' (string)
org.freedesktop.Hal.Device.Volume.method_argnames = {'mount_point fstype extra_options', 'extra_options', 'extra_options'} (string list)
org.freedesktop.Hal.Device.Volume.method_execpaths = {'hal-storage-mount', 'hal-storage-unmount', 'hal-storage-eject'} (string list)
org.freedesktop.Hal.Device.Volume.method_names = {'Mount', 'Unmount', 'Eject'} (string list)
org.freedesktop.Hal.Device.Volume.method_signature s = {'ssas', 'as', 'as'} (string list)
info.interfaces = {'org.freedesktop.Hal.Device.Volume'} (string list)
org.freedesktop.Hal.Device.Volume.method_argnames = {'mount_point fstype extra_options', 'extra_options', 'extra_options'} (string list)
org.freedesktop.Hal.Device.Volume.method_execpaths = {'hal-storage-mount', 'hal-storage-unmount', 'hal-storage-eject'} (string list)
org.freedesktop.Hal.Device.Volume.method_names = {'Mount', 'Unmount', 'Eject'} (string list)
org.freedesktop.Hal.Device.Volume.method_signature s = {'ssas', 'as', 'as'} (string list)
/home/user #

[michaaa62]

Looks bad! None of the output is referring to an external card. :(
Do you have a second card to check the hardware of the N900 for full functionality?
This card seems to be at the end of its life.

[willi6868]

Looks bad! None of the output is referring to an external card.
Do you have a second card to check the hardware of the N900 for full functionality?
This card seems to be at the end of its life.

Nothing possible anymore? :(

Sure I have a second one.. Wich commands should I use for it? :)

[pichlo]

No commands, just plug it in, close the lid and see if it works.

I am sorry about the loss of your data. It looked like that after your second post but I was secretly hoping I was wrong.

[willi6868]

No commands, just plug it in, close the lid and see if it works.

I am sorry about the loss of your data. It looked like that after your second post but I was secretly hoping I was wrong.

Sure other cards working in my N900...

So the problem is that it doesn't recognice this memory card? It is realy impossible to write a new file System on IT/ just format it? ! :(

Also my N900 and the stock filebrowser is recognizing it but says that the filesytem is not supported... :/

[michaaa62]

My opinion, and it is just opinion... !
This i a generic error message, written 3 to 4 years ago by someone, that was a happy Nokia employee, happily crippling linux to their Maemo needs... There is no real development in the closed parts of Maemo system. There is not very much helpful information in this message.

[lucas777]

Just thought i would post here to help anyone with this issue, i had the same issue last week for the first time about memory corrupt. Anyway i tried for around 2 3 days to flash this with no fix it was doing my head in i tried on WIndows 32/64 bit on 3 4 diffrent machines.

The Emmc couldnt be flashed no matter what i did i kept getting

Waiting for Device etc etc.

So i decided to boot up Linux Ubuntu live cd, and bam flashed first go and everything was great.

So if anyone is having trouble flashing via windows trust me do it via Linux. Good Luck

[willi6868]

So i decided to boot up Linux Ubuntu live cd, and bam flashed first go and everything was great.

So if anyone is having trouble flashing via windows trust me do it via Linux. Good Luck

And what would you do if even Ubuntu doesn't recognice your mmc? :D

BTW big thanks for the efforts of michaaa62 and pichlo! :)

[lucas777]

Well then thats a hardware issue, not Linux so you would have to send it to Nokia or someone who could fix that. Im just talking about the issue A LOT of people were having were Windows would not find a suitable drive under the flashing process but could find the fiasco image not the emmc image.

[willi6868]

Well then thats a hardware issue, not Linux so you would have to send it to Nokia or someone who could fix that. Im just talking about the issue A LOT of people were having were Windows would not find a suitable drive under the flashing process but could find the fiasco image not the emmc image.

The issue which a lot of people have is a damaged file sytsem which you just can fix with chkdsk x: /r or /f in windows (x=your drive) :rolleyes: :D