Dump an image of root and eMMC.. how to?

[Dany-69]

Hi guys :)
First at all, excuse me for my english :p
By the way... i've searched al lot here and on google about a way to dump the image of the root and the eMMC, but unfortunately without a result.. :confused:

I'd like to create some images that can be flashed throught the maemo-flasher with a simple command, just like the FIASCO images..
This way everybody could create his own "rom" with all the desired advanced personalizations (like transitions, boot videos, power menu, cpu clock ecc ecc), softwares and settings ...
Something much more easy and fast than a backup IMHO ..

Excuse me if this question has already been paid. :)

[chaoyi]

use dd?
for rootfs, dd if=/dev/mtd5 of=rootfs.raw

[abill_uk]

Exellent idea as that would be a good way to restore phone to "last known working" similar to the system restore in windows.
Getting close to my idea of uninstalling completely problem apps or getting the os back to it was prior to a loop or "bricked" situation.

[SD.]

It also might be a good way to compared the leaked PR1.2 vs the supposedly stock hong kong PR1.2

[S0urcerr0r]

use dd?
for rootfs, dd if=/dev/mtd5 of=rootfs.raw
im a inexperienced linux user.
how would i define the destination path to store that "rootfs.raw" on the sdcard / or on the 30 gb partition (users files)?

[Dany-69]

use dd?
for rootfs, dd if=/dev/mtd5 of=rootfs.raw

Wait wait .. :D
What does this command do ?
Does it create directly a file that can be used with the Flasher?
and where does the command place the file ?
Tnx :)

[Kjow]

Great Dany! :D
Good idea!

[brz]

Good idea Dany,
You have my support! ;)

[rash.m2k]

Wait wait .. :D
What does this command do ?
Does it create directly a file that can be used with the Flasher?
and where does the command place the file ?
Tnx :)

dd (data definition), copies bytes from if (input file/device) to of (output file/device).

Not sure if it creates a file that can be used with flasher.

It places the file in the directory you run the command from to have it place the file in the memory card set of=/media/mmc1/rootfs.raw

[rash.m2k]

Also creating a dump of emmc should probably not be done - just copy the directories to an ext3 partition to preserve permission info (ext3 memory card perhaps???), otherwise each time you do it you will get a file thats 2GB big, which will wear down the internal flash.

Only opt needs to be copy to ext3, MyDocs can just be backed up on PC as it's just FAT32.

[Dany-69]

dd (data definition), copies bytes from if (input file/device) to of (output file/device).

Not sure if it creates a file that can be used with flasher.

It places the file in the directory you run the command from to have it place the file in the memory card set of=/media/mmc1/rootfs.raw

Good :) ...
So, if i want the "image" of the whole root, i have to use the command [ dd if=/ of=/media/mmc1/rootfs.raw ] .. not?

And how to restore this image ? :confused:

@ Kjow and brz : tnx my loved guys :D

[Dany-69]

Also creating a dump of emmc should probably not be done - just copy the directories to an ext3 partition to preserve permission info (ext3 memory card perhaps???), otherwise each time you do it you will get a file thats 2GB big, which will wear down the internal flash.

Only opt needs to be copy to ext3, MyDocs can just be backed up on PC as it's just FAT32.

Yes, infact I was referring to the opt partiton :)
The only one necessary to have a complete backup even of the installed programs :)

[MohammadAG]

Wouldn't backing up using dd while the system is running cause issues (cause of procfs and sysfs).
It should work in Mer or any other dual boot system though

[rash.m2k]

Good :) ...
So, if i want the "image" of the whole root, i have to use the command [ dd if=/ of=/media/mmc1/rootfs.raw ] .. not?

And how to restore this image ? :confused:

@ Kjow and brz : tnx my loved guys :D

NO! / is the root file/folder and EVERYTHING inc memory card, screen, touchscreen, swap space i.e. ALL devices are mapped to some directory underneath root '/', external devices are normally mapped /dev directory (so when something changes on the screen for example maemo writes the changes to a file under /dev and this file is connected to the display which then reads this file and updates the display - at least thats how I understand how Linux works).

So by choosing '/' as the input directory you will write, MyDocs (/home/user/MyDocs) , opts (/home/opt), rootfs etc ALL to the memory card! This is not what you want. You need to chose /dev/mtd5, which is where the INTERNAL 256MB FLASH is mapped to.

[Dany-69]

Wouldn't backing up using dd while the system is running cause issues (cause of procfs and sysfs).
It should work in Mer or any other dual boot system though

Azz... :mad: ... (excuse me for my "italianism" :D)
No other way ? ..
That's impossible that no one has ever think to do something like this .. :confused:

[rash.m2k]

Wouldn't backing up using dd while the system is running cause issues (cause of procfs and sysfs).
It should work in Mer or any other dual boot system though

Oh yeah, that will probably cause some issues - is there anyway to mouse the INTERNAL flash onto a LINUX machine?

If that could be done then it would be brilliant! No more bricked devices, just flash with DD on your PC

I'm looking to you for advice on this one! You're more of an expert on this than me! :)

Yes, infact I was referring to the opt partiton :)
The only one necessary to have a complete backup even of the installed programs :)

No not quite - some of the files/libraries/scripts are stored in /opt, BUT where does it store a list of the applications that are installed?? On the rootfs! SO backing up /opt is useless without backing up rootfs.

EDIT:::::::::::::

Could we boot maemo from a memory card like we could with N8xx? Even a basic install with just the x-term working will be enough!

This is interesting:

http://talk.maemo.org/showthread.php?t=36011&page=3

I could have a memory card with a clean maemo install specifcally for when things go wrong - just like I have a bootable linux install for my PC/laptop if it gets screwed up.

EVEN MORE INTERESTING!!!

http://talk.maemo.org/showpost.php?p=444600&postcount=45

[Dany-69]

NO! / is the root file/folder and EVERYTHING inc memory card, screen, touchscreen, swap space i.e. ALL devices are mapped to some directory underneath root '/', external devices are normally mapped /dev directory (so when something changes on the screen for example maemo writes the changes to a file under /dev and this file is connected to the display which then reads this file and updates the display - at least thats how I understand how Linux works).

So by choosing '/' as the input directory you will write, MyDocs (/home/user/MyDocs) , opts (/home/opt), rootfs etc ALL to the memory card! This is not what you want. You need to chose /dev/mtd5, which is where the INTERNAL 256MB FLASH is mapped to.

RIght.. :)
I hadn't focused... :p
The root contains ALL ... :D


No not quite - some of the files/libraries/scripts are stored in /opt, BUT where does it store a list of the applications that are installed?? On the rootfs! SO backing up /opt is useless without backing up rootfs.


:D We are saying the same thing... :p
I meant to do a backup of either root and eMMC... But i got wrong to call it eMMC... i meant only the OPT partition ;)

[Dany-69]

Could we boot maemo from a memory card like we could with N8xx? Even a basic install with just the x-term working will be enough!

This is interesting:

http://talk.maemo.org/showthread.php?t=36011&page=3

I could have a memory card with a clean maemo install specifcally for when things go wrong - just like I have a bootable linux install for my PC/laptop if it gets screwed up.

Yes... intersting..
But this is a process a bit too "long" for my taste ...
It would be intersting to do this with a program that can access to the N900 during the flash mode pressing the U key .. :eek:

[rash.m2k]

Well I'm going to try booting from memory card - I've got loads of 2GB MicroSD cards lying about.

Just one will do - then I can set mess around with my N900 as much as I like knowing I can just boot from memory card and rewrite rootfs!

I'll give it a try once I get home later tonight.

[Dany-69]

Well I'm going to try booting from memory card - I've got loads of 2GB MicroSD cards lying about.

Just one will do - then I can set mess around with my N900 as much as I like knowing I can just boot from memory card and rewrite rootfs!

I'll give it a try once I get home later tonight.

You are amiably mad :D
I hope there won't be problems during flashing the root :cool:

[Kjow]

@ Kjow and brz : tnx my loved guys :D

Go away!!!:eek:

:D:D

[rash.m2k]

You are amiably mad :D
I hope there won't be problems during flashing the root :cool:

Oh - not quite yet! I'm not going to try to flash the root just yet!

Once PR1.2 comes out then I'm going to start from a clean fresh flash so I'll experiment then!

I'm not mad enough to try it now! :D:D


Wouldn't backing up using dd while the system is running cause issues (cause of procfs and sysfs).
It should work in Mer or any other dual boot system though

This is solved by mounting root (/) again using the --bind option.

[zehjotkah]

you're searching for something like mklivecd (http://en.wikipedia.org/wiki/Mklivecd)
project page (http://mklivecd.sourceforge.net/)

[abill_uk]

To get the full os contents is quite a feat as it would require some kind of investigation tool to actually "grab" the os in entirety.
Still would not give you all the closed driver info as this would require investigating each closed device itself to even try to get it to spill its contents out so even armed with the each and every closed device data sheet it still requires some technology to get its contents.
As for the general os i think this may be possible with something like an investigation tool for linux and an unhibited way into the os hmmm food for thought aye.
As for flashsing the os from an sd card in the N900 ha good luck lol cos i think impossible.

[abill_uk]

How would you mount only the os in rediness for extraction using mklivecd ? is it even possible to segragate the os from the rest ?

[zehjotkah]

To get the full os contents is quite a feat as it would require some kind of investigation tool to actually "grab" the os in entirety.
Still would not give you all the closed driver info as this would require investigating each closed device itself to even try to get it to spill its contents out so even armed with the each and every closed device data sheet it still requires some technology to get its contents.
As for the general os i think this may be possible with something like an investigation tool for linux and an unhibited way into the os hmmm food for thought aye.
As for flashsing the os from an sd card in the N900 ha good luck lol cos i think impossible.

Cloning the OS is totally possible. It is not required to disassemble and reassemble the OS.
A comparision. You can copy the .exe from Adobe Photoshop, but you can't disassemble it easily. Got the point?
Cloning the OS was done before with the older tablets. Booting from SD-Card, too.
Flashing the OS from SD-Card could be possible, too, if the OS is booted from SD-Card, too (internal OS not in use).

[zehjotkah]

How would you mount only the os in rediness for extraction using mklivecd ? is it even possible to segragate the os from the rest ?

you don't need to unmount (if you meant unmount, if you really meant mount, I don't know why you would like to mount the OS) the OS. mklivecd is just reading, copying and compressing the files.

[abill_uk]

can you actually read???? who said UNmount???

[santiago]

Cloning the OS is totally possible. It is not required to disassemble and reassemble the OS.
A comparision. You can copy the .exe from Adobe Photoshop, but you can't disassemble it easily. Got the point?
Cloning the OS was done before with the older tablets. Booting from SD-Card, too.
Flashing the OS from SD-Card could be possible, too, if the OS is booted from SD-Card, too (internal OS not in use).
we can disassembly the bin files. one question... how can i open the jffs2 files n windows?! sorry compressed partitions?!?

[zehjotkah]

can you actually read???? who said UNmount???

read my post again and read also what I wrote in brackets.

we can disassembly the bin files.

why would you do this? It is completely unneeded.

[Dany-69]

you don't need to unmount (if you meant unmount, if you really meant mount, I don't know why you would like to mount the OS) the OS. mklivecd is just reading, copying and compressing the files.

In practice you should install the deb (http://prdownloads.sourceforge.net/mklivecd/mklivecd_0.01-1_i386.deb) on a PC with any distro ... create the live cd (hopefully there is a version for ARM architecture, something which I doubt) ... then copy the contents of the CD on a microSD ... Install bootmanager on maemo ... Boot from microSD .. and then dump the image.
Am I wrong?

[abill_uk]

Even if you used something like Helix live cd you would still have to MOUNT the os so i am still at a loss as to get a dump of the os without some kind of investigative method being used.

[Dany-69]

Even if you used something like Helix live cd you would still have to MOUNT the os so i am still at a loss as to get a dump of the os without some kind of investigative method being used.

There's no need to mount/unmount the system..
You can directly read/copy every byte of the root/opt in an image witout mounting i suppose....

[santiago]

read my post again and read also what I wrote in brackets.



why would you do this? It is completely unneeded.
i know... probably i m OT but i want to make a custom PR with my personal image... apps theme... addbook etc... and i need to mount jffs2 partitions on win... is it possible??! or,,, can i mount it on maemo and share it with ssh?! :)

[zehjotkah]

Even if you used something like Helix live cd you would still have to MOUNT the os so i am still at a loss as to get a dump of the os without some kind of investigative method being used.

the OS in use IS mounted. ^^
To ensure we're talking about the same:
I'm talking about normally booting maemo, use something like mklivecd, which reads the entire OS, copies it and compresses it to an image file, for example .bin.
This .bin file contains ALL installed programs, ALL settings and ALL modifications made to the system. It does not contain the files from the 32GB memory, though.
This .bin can be used to flash the device. No need to reinstall every program, or made any modifications again. Just like a flashable backup.
The next step would be to flash this image from the device itself, that means from a previously cloned, booted OS on the SD-Card (or internal 32GB memory, if you've formatted it previously).

[abill_uk]

OK then why dont you attempt to get a complete copy of the os and IF you are successful even i will applaud you !!!.
Something is staring me in the face here and i just cannot see it right now but there has to be a simple way of grabbing the entire contents of the "hard drive" in the n900.
Have you any idea just how important this would be to everyone if you could do this?.

[Dany-69]

i know... probably i m OT but i want to make a custom PR with my personal image... apps theme... addbook etc... and i need to mount jffs2 partitions on win... is it possible??! or,,, can i mount it on maemo and share it with ssh?! :)

I think our goal is the same ... :)
You want to mount the jffs2 image obtained by unpacking the fiasco image and shape it according to your requirements as I understand it. :)

then how should you reinsert the jffs2 image file for use with the flasher?

[abill_uk]

I think our goal is the same ... :)
You want to mount the jffs2 image obtained by unpacking the fiasco image and shape it according to your requirements as I understand it. :)

then how should you reinsert the jffs2 image file for use with the flasher?

Hang on a minute here you just bolted straight past the problem of getting a direct dump of the FIASCO to start with so maybe you could tell us at least how to do that?

[rash.m2k]

Just ignore abill_uk's comments I think he's getting confused.

I have successfully done this BOTH on the N800 and N810. There's no reason why this cannot be done on the N900. Currently I'm following Fanoush's instructions. He's a genuis at this stuff and he helped me getting it up and running last time.

[Dany-69]

the OS in use IS mounted. ^^
To ensure we're talking about the same:
I'm talking about normally booting maemo, use something like mklivecd, which reads the entire OS, copies it and compresses it to an image file, for example .bin.
This .bin file contains ALL installed programs, ALL settings and ALL modifications made to the system. It does not contain the files from the 32GB memory, though.
This .bin can be used to flash the device. No need to reinstall every program, or made any modifications again. Just like a flashable backup.
The next step would be to flash this image from the device itself, that means from a previously cloned, booted OS on the SD-Card (or internal 32GB memory, if you've formatted it previously).

mmm... so mklivecd doesn't create a livecd with a small operating system that allow you to copy everything?
Instead, according to your words, it seems to be a program that does everything directly while in use maemo.. :confused:
But someone said it isn't possible while the system in running.. :confused:

[santiago]

u can extract the fiasco running this in the flasher shell

flasher-3.5 fiascoimage.bin -u

and u ll find the jffs2 partitions... now how can i mount them on win??? i dont want all the things like games and stupid widgets that nokia put in the fiasco... i want to create my personal fiasco to be free to choose what i want to keep on my os

[zehjotkah]

OK then why dont you attempt to get a complete copy of the os and IF you are successful even i will applaud you !!!.
Something is staring me in the face here and i just cannot see it right now but there has to be a simple way of grabbing the entire contents of the "hard drive" in the n900.
Have you any idea just how important this would be to everyone if you could do this?.

I've no programming skills. Just a little bit Linux-knowledge.
But it should work out-of-the-box after recompiling for armel (without the ability to create the required .bin image. mklivecd builds a .iso image)
I haven't checked the debian armel repositorys, yet. Maybe it's already there.
mklivecd would be the simplest way you could get.
By "hard drive" do you mean the eMMC, the internal 32GB memory? This wouldn't be included in the mklivecd, but you can simply copy it.

[Dany-69]

I've no programming skills. Just a little bit Linux-knowledge.
But it should work out-of-the-box after recompiling for armel (without the ability to create the required .bin image. mklivecd builds a .iso image)
I haven't checked the debian armel repositorys, yet. Maybe it's already there.
mklivecd would be the simplest way you could get.
By "hard drive" do you mean the eMMC, the internal 32GB memory? This wouldn't be included in the mklivecd, but you can simply copy it.

And what about the opt?

[zehjotkah]

mmm... so mklivecd doesn't create a livecd with a small operating system that allow you to copy everything?
Instead, according to your words, it seems to be a program that does everything directly while in use maemo.. :confused:
But someone said it isn't possible while the system in running.. :confused:

???
it makes exactly a live cd... a live cd is just an image. What we need.
But it seems, you can extract the image with the flasher? I didn't know that.
The image from the device, with all installed programs and modifications, inclusive the kernel?

[santiago]

i fond this ahhaahah extract to /usr/local/bin

then to create jffs2 files of backup run

#0xFFFF -e /media/mmc1/backup
#0xFFFF -x /media/mmc1/backup

to restore the backups you should run this i think

# 0xFFFF -R -p /media/mmc1/backup/rootfs.jffs


attached file at the end ;)

[abill_uk]

Just ignore abill_uk's comments I think he's getting confused.

I have successfully done this BOTH on the N800 and N810. There's no reason why this cannot be done on the N900. Currently I'm following Fanoush's instructions. He's a genuis at this stuff and he helped me getting it up and running last time.

Maybe but no need for flaming talk OK.
OK wise guy start talking instead of flaming and at least tell everyone how to get a complete dump of the N900?
I am off to lunch so will read when i return.

[santiago]

???
it makes exactly a live cd... a live cd is just an image. What we need.
But it seems, you can extract the image with the flasher? I didn't know that.
The image from the device, with all installed programs and modifications, inclusive the kernel?
yeah but its in jjfs2 now we need infos to mount it... i dont want to do that using the command # 0xFFFF
i need to work with the real fiasco unpartitioned files. i go to luch too... see u later gays... ehmm... gays ahhahahahah

[abill_uk]

Hard drive as in complete dump of the N900, sorry i missed that post went back to read and seen it.

[Dany-69]

???
it makes exactly a live cd... a live cd is just an image. What we need.
But it seems, you can extract the image with the flasher? I didn't know that.
The image from the device, with all installed programs and modifications, inclusive the kernel?

Wait I have not explained well :)
In mklivecd project pages you can download a deb ...
Now my question is ... this "deb" allows you to create a livecd which should be booted as a secondary operating system from device to create ISO (or another livecd, as you call it) of the primary operating system?
A bit like I did with HDD Regenerator if I remember correctly ..i downloaded an exe that created a sort of livecd..
Or you can directly create the ISO of the primary operating system through the program ?

[zehjotkah]

here is the project page of the 0pen Free Fiasco Firmware Flasher

http://www.nopcode.org/0xFFFF/ (http://www.nopcode.org/0xFFFF/)

[abill_uk]

yeah but its in jjfs2 now we need infos to mount it... i dont want to do that using the command # 0xFFFF
i need to work with the real fiasco unpartitioned files

You already got that as in the bin file RX-51_2009SE_3.2010.02-8.002_PR_COMBINED_002_ARM.bin.

[zehjotkah]

Wait I have not explained well :)
In mklivecd project pages you can download a deb ...
Now my question is ... this "deb" allows you to create a livecd which should be booted as a secondary operating system from device Crerar ISO (or another livecd) the primary operating system?
A bit like I did with HDD Regenerator if I remember correctly ..
Or you can directly create the ISO of the primary operating system through the program ?

you can create a ISO of the currently running OS, just like a bootable, installable backup, of your currently running system.
Very usefull before risky operations to safe the last working state of your system.

[Dany-69]

here is the project page of the 0pen Free Fiasco Firmware Flasher

http://www.nopcode.org/0xFFFF/ (http://www.nopcode.org/0xFFFF/)

This seems to do exactly what we need :eek:
Am i wrong? :)

EDIT: Azz... not for windows.. :(

[santiago]

This seems to do exactly what we need :eek:
Am i wrong? :)

EDIT: Azz... not for windows.. :(
cacchio...e se usiamo virtual box ed una distro????

can we open the jffs2 on windows?!
or we must run that on vbox usin a linux distro?!

[zehjotkah]

cacchio...e se usiamo virtual box ed una distro????

can we open the jffs2 on windows?!
or we must run that on vbox usin a linux distro?!

I haven't seen any program to open a jffs2 filesystem on Windows.

[abill_uk]

Found this if it helps ok.
http://www.handhelds.org/moin/moin.cgi/FamiliarBackupHowto
http://www.keyongtech.com/5233440-jffs2-mount-failing

[rash.m2k]

I don't see why you would even need to extract the jffs2 image?

/dev/mtd2 is just a flash chip containing 1's and 0's dd it to your memory card (once you can boot from memory card) and then if need be just flash it back to /dev/mtd2

[abill_uk]

cacchio...e se usiamo virtual box ed una distro????

can we open the jffs2 on windows?!
or we must run that on vbox usin a linux distro?!

Yep vbox will get you working on Linux.

[zehjotkah]

Found this if it helps ok.
http://www.handhelds.org/moin/moin.cgi/FamiliarBackupHowto
http://www.keyongtech.com/5233440-jffs2-mount-failing

nice find. I don't know anything about familiar linux for the iPaq.
But as mklivecd is for debian, and maemo is based on debian, it might be easier to use mklivecd.
Or this open flasher thingi...

btw: did you notice abill? I thanked your post :D

[rash.m2k]

This seems to confirm my speculation:

http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image

[zehjotkah]

This seems to confirm my speculation:

http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image

thanks!

that is exactly what we need.

[rash.m2k]

thanks!

that is exactly what we need.

Well - I'd like to be able to also boot from an micro SD card, as this would mean I can restore my N900 without a PC.

Once I get home tonight I'll partition a micro sd card and try to boot from it.

[zehjotkah]

Well - I'd like to be able to also boot from an micro SD card, as this would mean I can restore my N900 without a PC.

Once I get home tonight I'll partition a micro sd card and try to boot from it.

maybe this wiki helps:
http://wiki.maemo.org/Booting_from_a_flash_card

[rash.m2k]

maybe this wiki helps:
http://wiki.maemo.org/Booting_from_a_flash_card

Some of that still refers to the OLD n810 way of doing things (I vaguely remember doing it).

I'm going to follow the instructions here:

http://talk.maemo.org/showpost.php?p=444600&postcount=45

Fanoush helped us with the N8xx, once I've cloned the OS the rest should be straighforward, I just need to point the bootloader to the microsd card slot.

[Dany-69]

thanks!

that is exactly what we need.

PERFECT :D
I can't try this now... (i have no n900 .. :p)
Btw... What about the opt partition ?

[javispedro]

This seems to confirm my speculation:

http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image

Note that the article mentions that should be done from a USB Recovery Environment, do not do that from the same operating system you're trying to backup!

Also note that the N900 doesn't use JFFS2 but UBIFS, the rest of the instructions should be similar to the N8x0 instructions.

[Dany-69]

Note that the article mentions that should be done from a USB Recovery Environment, do not do that from the same operating system you're trying to backup!

Also note that the N900 doesn't use JFFS2 but UBIFS, the rest of the instructions should be similar to the N8x0 instructions.

The usb recovery mode seems to be a "part of maemo" ... so we shouldn't need another operating system ..
Besides i'm quite sure that the N900 uses JFFS2 ... :confused:

[javispedro]

The usb recovery mode seems to be a "part of maemo" ... so we shouldn't need another operating system ..

No, as you can read on the USB Recovery Mode link right on that page...

Besides i'm quite sure that the N900 uses JFFS2 ... :confused:
No; all Internet Tablets use JFFS2, but the N900 uses UBIFS as the kernel log will tell you.

[Dany-69]

No; all Internet Tablets use JFFS2, but the N900 uses UBIFS as the kernel log will tell you.

The kernel log can say whatever he wants :D :p
But, unpacking every Fiasco image, everyone can obtain another result.. :

[javispedro]

The kernel log can say whatever he wants :D :p
But, unpacking every Fiasco image, everyone can obtain another result.. :
And you're going to trust the utility that is used to flash all the Internet Tablets (not only N900) BEFORE what the actual on-your-hands N900 says and uses? :P

[Dany-69]

No, as you can read on the USB Recovery Mode link right on that page...

http://metalab.at/wiki/Hack-A-N900/Usb_Recovery_Mode :

Patching bootmenu enables us to boot a minimal system with just usb network and sshd enabled. that's still not optimal because this solution relies on rootfs being accessible.

From these words I understand that this mode uses some files in the root to activate a particular mode with only ssh and usb connection avaible...
And it says that this mode is not really a permanent solution because the access to the root is needful ...just because these functions are "taken" from the root .
This always if my English is not so rusty :D

[Dany-69]

And you're going to trust the utility that is used to flash all the Internet Tablets (not only N900) BEFORE what the actual on-your-hands N900 says and uses? :P

o.O .... I'm not trusting in the utility .... i'm trusting in the fiasco image downloaded from nokia and that i use to flash the device :p

[javispedro]

From these words I understand that this mode uses some files in the root to activate a particular mode with dsponibili only ssh and connect usb ...
The important part here is that they don't boot as many binaries from rootfs, and that allows them to remount rootfs as read-only later on the boot process. You cannot do this within the normal environment; you need to use a specialized (external) init script and tools (bootmenu, sshd ...)

o.O .... I'm not trusting in the utility .... i'm trusting in the fiasco image downloaded from nokia and that i use to flash the device :p
That's not the FIASCO image you downloaded from Nokia, since you used THE UTILITY to unpack it. So they forgot to rename the file extension when creating the output file, or probably, they don't even care as the code for that is device independent -- big deal.

What are you trying to do? Copying the rootfs alone in Fremantle is mostly useless, specially with the PR1.2, as $HOME and some system files will be on the eMMC.
And if you want to do this from the device, you really need to boot into a special customized environment, or else you risk getting a corrupted backup (yes, there's a SLIGHT chance only, but would you really trust something like that as a backup?).

[Dany-69]

The important part here is that they don't boot as many binaries from rootfs, and that allows them to remount rootfs as read-only later on the boot process. You cannot do this within the normal environment; you need to use a specialized (external) init script and tools (bootmenu, sshd ...)


Practically we're saying the same thing with different words :p

That's not the FIASCO image you downloaded from Nokia, since you used THE UTILITY to unpack it. So they forgot to rename the file extension when creating the output file, or probably, they don't even care as the code for that is device independent -- big deal.

Wow.. O_O i had no idea that it could be a mistake..

What are you trying to do? Copying the rootfs alone in Fremantle is mostly useless, specially with the PR1.2, as $HOME and some system files will be on the eMMC.
And if you want to do this from the device, you really need to boot into a special customized environment, or else you risk getting a corrupted backup (yes, there's a SLIGHT chance only, but would you really trust something like that as a backup?)

Infact, like you can read in the title, i want to create an image even of the eMMC... or, saying better, of the indispensable OPT partition that contains most of data of the 3d part softwares.. :)
By the way i suppose it is not too much different from creating an image of the root..
We could use the same "dd" command... am i wrong? :)

[abill_uk]

This thread is getting really interesting and am following it with great interest, may i humbly thank everyone on this thread the interest and enthusiasm is fantastic please keep up the good work and spirits this looks like its going somewhere.

PS i happen love Berlin too fantastic city lol.

[zehjotkah]

Just to resume a little bit, so you don't have to read through the thread, if you're new but interested.

We would like to make it possible to "backup" the entire operating system, inclusive every program installed, every preference made and every modification made.
This process can be compared to the debian-script "mklivecd" which is used to make a bootable live cd from your current system.
The aim is then to provide different ROMs which are modded, for example a ROM made to speed up the system as much as possible (OC, transitions removed, maybe different browser and so on) or a ROM for low as possible battery usage (UV, automatic disconnect and so on). Also it will be very easy to backup your system in the current state, so you don't have to reinstall everything after messing up your system and reflashing it. Just flash the last working state.
Currently we have four options. In my opinion they promise success in this order:

1. Use USB recover mode to create an image and flash this image afterwards (http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image) (needs a PC to create and flash the image; dualboot should be possible)
2. Use the 0pen Free Fiasco Firmware Flasher (http://www.nopcode.org/0xFFFF/) (adding N900 support required)
3. Port mklivecd to maemo (http://mklivecd.sourceforge.net/) (maemo is debian-based, so it shouldn't be difficult)
4. Try to profit from the backup function of Familiar Linux for the iPaq PDA (http://www.handhelds.org/moin/moin.cgi/FamiliarBackupHowto) (major work required)

Thanks to rash.m2k, santiago and abill_uk for their time and effort.

[santiago]

;) thanks to you. all the processes the you follow over there, are debian based.... imean that u cant get it working on win i think... win cannot yet mount jffs2 partitions. i was reading that someone made a firware hacking tool, google it and have a look.... it doesnt support yet this jffs2 seems to be in one armagheddon... no way to edit a journal file partitioon on windows :(

[santiago]

now.... the only thing that i cant think its... extract a bin file content.... and mounting those partitions on maemo... maybe we can share it with the ssh !??? what u think bout it?? it can be done i suppose

[rash.m2k]

OK I tried cloning the OS but the problem is that there are some files which cause the tar to fail.

This obviously needs to be done on a clean OS install which I am not going to do yet (damn you PR1.2!)

zehjotkah, if you are willing to have a play with this then I'd be happy to provide input? ;)

With a clean install of the N900, install bootmenu (fanoush's) & rootsh and then follow these instructions:

http://talk.maemo.org/showpost.php?p=444600&postcount=45

Credit also goes to fanoush.

In addition editing the FSTAB will also be required.

EDIT: N900 does not use jffs2 it uses UBIFS.

[Dany-69]

OK I tried cloning the OS but the problem is that there are some files which cause the tar to fail.

This obviously needs to be done on a clean OS install which I am not going to do yet (damn you PR1.2!)

zehjotkah, if you are willing to have a play with this then I'd be happy to provide input? ;)

With a clean install of the N900, install bootmenu (fanoush's) & rootsh and then follow these instructions:

http://talk.maemo.org/showpost.php?p=444600&postcount=45

Credit also goes to fanoush.

In addition editing the FSTAB will also be required.

EDIT: N900 does not use jffs2 it uses UBIFS.

I don't think it has much sense to do this on a clean installation.. o.O :confused:

[zehjotkah]

I will get into it, when I've time.
Today I have to prepare tomorrows work, that shouldn't take too long.
Then I have to test the x86 emu / WINE thingi and after that I can try the cloning OS part.

[rash.m2k]

I will get into it, when I've time.
Today I have to prepare tomorrows work, that shouldn't take too long.
Then I have to test the x86 emu / WINE thingi and after that I can try the cloning OS part.

The OS cloning has been proved to work - fanoush has done it and it shouldn't be too difficult to do.

I've already got bootmenu installed and can edit the partitions I boot from, but the cloning is not working. Might try to extract the f/w from the .bin file - any ideas how to do this?

[javispedro]

Previously, I used to do this on the N810 by extracting the JFFS2 image from FIASCO then replacing individual files from the files on my N810. Then you have tools to recreate the JFFS2 image from a set of directories -- and then recreate the fiasco image.

This is documented somewhere for sure, I didn't remember reading the mkjffs2 manual but a nice blog howto instead.

I'd do the same for the N900, only using their ubifs counterparts. It's better not to dd the flash filesystem as it contains badblock information. For the ext3 filesystem, I'd say its OK.

Note also that if you do this, the images will contain both YOUR personal data and Nokia's copyrighted data. don't distribute them -- but it's completely fine for a personal backup.

[abill_uk]

I think the idea of extracting a mirror image of the complete os is not as easy as we thought if it is indeed possible and am sure there has to be a way and image mountable as a .bin ready for flash this will lead to a system restore if an app is possible to take the system files at anytime as a complete usable image for flashing, that has got to be in line of a brainstorm and incredibly usable for linux devices.
Please try to persist on this *brainstorm* untill it is made possib!le.
Once again many thanks and appreciation to everyone on this thead for their time and brainstaking efforts.

[santiago]

The OS cloning has been proved to work - fanoush has done it and it shouldn't be too difficult to do.

I've already got bootmenu installed and can edit the partitions I boot from, but the cloning is not working. Might try to extract the f/w from the .bin file - any ideas how to do this?



SORRY CORRECTED
flasher-3.5 -F blabla.bin -u it'll extract the images... but i think they are in ubifs???? how can we mount it in on win ?

[santiago]

ROOT is in jffs2 !!! i post the log!


C:\Programmi\maemo\flasher-3.5> flasher-3.5 -F LEAKED.bin -u
flasher v2.5.2 (Sep 24 2009)

SW version in image: RX-51_2009SE_10.2010.12-9_PR_MR0
Image 'kernel', size 1705 kB
Version 2.6.28-20101103+0m5
Image 'rootfs', size 174080 kB
Version RX-51_2009SE_10.2010.12-9_PR_MR0
Image 'cmt-2nd', size 81408 bytes
Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.5+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.5+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.5+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.5+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.5+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.5+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.5+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.5+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.5+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.5+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.5+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.5+0m5
Unpacking kernel image to file 'zImage'...
Unpacking rootfs image to file 'rootfs.jffs2'...
Unpacking cmt-2nd image to file 'cmt-2nd'...
Unpacking cmt-algo image to file 'cmt-algo'...
Unpacking cmt-mcusw image to file 'cmt-mcusw'...
Unpacking 2nd image to file '2nd.bin-RX-51;2217,2218,2219,2220,2120'...
Unpacking xloader image to file 'xloader.bin-RX-51;2217,2218,2219,2220,2120'...
Unpacking secondary image to file 'secondary.bin-RX-51;2217,2218,2219,2220,2120'
...
Unpacking 2nd image to file '2nd.bin-RX-51;2101,2102,2103'...
Unpacking xloader image to file 'xloader.bin-RX-51;2101,2102,2103'...
Unpacking secondary image to file 'secondary.bin-RX-51;2101,2102,2103'...
Unpacking 2nd image to file '2nd.bin-RX-51;2104,2105,2106,2107,2108,2109,2110,21
11,2112,2113,2114,2115,2116,2117,2118,2119'...
Unpacking xloader image to file 'xloader.bin-RX-51;2104,2105,2106,2107,2108,2109
,2110,2111,2112,2113,2114,2115,2116,2117,2118,2119 '...
Unpacking secondary image to file 'secondary.bin-RX-51;2104,2105,2106,2107,2108,
2109,2110,2111,2112,2113,2114,2115,2116,2117,2118, 2119'...
Unpacking 2nd image to file '2nd.bin-RX-51;2201,2202,2203,2204,2205,2206,2207,22
08,2209,2210,2211,2212,2213,2214,2215,2216'...
Unpacking xloader image to file 'xloader.bin-RX-51;2201,2202,2203,2204,2205,2206
,2207,2208,2209,2210,2211,2212,2213,2214,2215,2216 '...
Unpacking secondary image to file 'secondary.bin-RX-51;2201,2202,2203,2204,2205,
2206,2207,2208,2209,2210,2211,2212,2213,2214,2215, 2216'...

C:\Programmi\maemo\flasher-3.5>

[rash.m2k]

flasher-3.5 blabla.bin -u it'll extract the images... but i think they are in ubifs???? how can we mount it in on win ?

Forget windows, it's not worth the hassle - if this is going to work then Linux is our only option.

This here seems interesting:

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_extract

I've only got kernel 2.6.31 on linux laptop so not sure if I can follow the instructions.

This WOULD help in extracting and copying the f/w to say a memory card but i'm unsure if we can package the files back into a bin file? (I don't have the skill to do that!)

EDIT::::::
santiago read this:

http://wiki.maemo.org/Modifying_the_root_image

N900 IS NOT JFFS2 DESPITE THE NAME!

[abill_uk]

I don't think it has much sense to do this on a clean installation.. o.O :confused:

Absoltely right as we need this capability at any point and would be pointless getting an image from a clean install, please think along the same line as the windiws restore point as that is the goal here.

[Dany-69]

ROOT is in jffs2 !!! i post the log!

iavispedro :

"No; all Internet Tablets use JFFS2, but the N900 uses UBIFS as the kernel log will tell you. "

"That's not the FIASCO image you downloaded from Nokia, since you used THE UTILITY to unpack it. So they forgot to rename the file extension when creating the output file, or probably, they don't even care as the code for that is device independent -- big deal."

[santiago]

Forget windows, it's not worth the hassle - if this is going to work then Linux is our only option.

This here seems interesting:

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_extract

I've only got kernel 2.6.31 on linux laptop so not sure if I can follow the instructions.

This WOULD help in extracting and copying the f/w to say a memory card but i'm unsure if we can package the files back into a bin file? (I don't have the skill to do that!)

EDIT::::::
santiago read this:

http://wiki.maemo.org/Modifying_the_root_image

N900 IS NOT JFFS2 DESPITE THE NAME!

il lost ubuntu dvd... on sabayon is it possible??? i ve also backtrack cd

[rash.m2k]

Absoltely right as we need this capability at any point and would be pointless getting an image from a clean install, please think along the same line as the windiws restore point as that is the goal here.

I think you misunderstand me. The image we boot from on the micro sd card is a clean install (after all it's just there incase anything goes wrong).

So you have a clean install of maemo on your micro SD card - you backup your N900 rootfs using this clean image to access the mtd from here and also restore the mtd from here.

But yes the whole point would be to be able to boot from micro sd card and also backup and restore both opt and rootfs.

[rash.m2k]

il lost ubuntu dvd... on sabayon is it possible???

If you have the kernel modules installed probably, but I'm no expert. :confused:

[javispedro]

On that wiki page there is a link to a post with mkubifs instructions, so you can pretty much repeat what I did with the N810.

[abill_uk]

Forget windows, it's not worth the hassle - if this is going to work then Linux is our only option.

This here seems interesting:

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_extract

I've only got kernel 2.6.31 on linux laptop so not sure if I can follow the instructions.

This WOULD help in extracting and copying the f/w to say a memory card but i'm unsure if we can package the files back into a bin file? (I don't have the skill to do that!)

EDIT::::::
santiago read this:

http://wiki.maemo.org/Modifying_the_root_image

N900 IS NOT JFFS2 DESPITE THE NAME!

I think you are right as to attempt this in any way in a windows enviourment as will obviously make too many complications as their aint anything i can find to do debian successfully within windows.
So for the essential exacting of this it can only be done in the format it is written in and thats obviously linux, if someone can find a linux emulator for windows ha ok go for it lol but i doubt it would even come close.
If you need the latest version of linux kernal here are the links,
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.tar.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.34-rc7.tar.gz

Hope this helps.

[abill_uk]

Incidently i am not sure how stable the latest versions are ok.

[abill_uk]

I think you misunderstand me. The image we boot from on the micro sd card is a clean install (after all it's just there incase anything goes wrong).

So you have a clean install of maemo on your micro SD card - you backup your N900 rootfs using this clean image to access the mtd from here and also restore the mtd from here.

But yes the whole point would be to be able to boot from micro sd card and also backup and restore both opt and rootfs.

Hmmm you know i am not so confident that even booting successfully from sd would give you the means of acomplishing a re-flash and also too many weird things are happening and so easy for the image on the sd to become corrupt and in any case doing it the way you suggest even if possible is kind of a long winded flash lol, i think far easier to create a .bin and use flasher in one hit job done, or maybe your thinking a different line here and i am just not understanding you.
My idea is to actually re-flash the last known working os in entirety to get you back before it went wrong and as simple way as possible for user to do as zehjotkah said in his very explanitory post erlier the .bin to include everything, apps and all personal data etc etc..

[rash.m2k]

Hmmm you know i am not so confident that even booting successfully from sd would give you the means of acomplishing a re-flash and also too many weird things are happening and so easy for the image on the sd to become corrupt and in any case doing it the way you suggest even if possible is kind of a long winded flash lol, i think far easier to create a .bin and use flasher in one hit job done, or maybe your thinking a different line here and i am just not understanding you.
My idea is to actually re-flash the last known working os in entirety to get you back before it went wrong and as simple way as possible for user to do as zehjotkah said in his very explanitory post erlier the .bin to include everything, apps and all personal data etc etc..

We won't know until we actually try it, but three things I am pretty sure about:

1) We can boot from micro SD card no problem (fanoush has done this)
2) We can backup rootfs using dd - this confirms it : http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image (we have access to micro sd storage).

3) We can reflash using the reflasher (see link above)

So what does this mean?

This means we can completely restore the N900 to an exact state!

HOWEVER whats more useful is that we have ACCESS to the rootfs!!!!! I remeber I made changes to one text file - and this bricked my N900, if I could have booted from Micro sd then I could have EASILY fixed it without reflashing!

Either way we should have a way to restore our N900s properly! I don't trust the backup manager.

[Dany-69]

We won't know until we actually try it, but three things I am pretty sure about:

1) We can boot from micro SD card no problem (fanoush has done this)
2) We can backup rootfs using dd - this confirms it : http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image (we have access to micro sd storage).

3) We can reflash using the reflasher (see link above)

So what does this mean?

This means we can completely restore the N900 to an exact state!

HOWEVER whats more useful is that we have ACCESS to the rootfs!!!!! I remeber I made changes to one text file - and this bricked my N900, if I could have booted from Micro sd then I could have EASILY fixed it without reflashing!

Either way we should have a way to restore our N900s properly! I don't trust the backup manager.

I have not yet realized if we need to boot from microSD with a clean instalation of maemo or if we just have to do what is described here (http://metalab.at/wiki/Hack-A-N900/Usb_Recovery_Mode), without a second operating system .. o_O

[zehjotkah]

I have not yet realized if we need to boot from microSD with a clean instalation of maemo or if we just have to do what is described here (http://metalab.at/wiki/Hack-A-N900/Usb_Recovery_Mode), without a second operating system .. o_O

we need to boot from sd to gain (writing-)access to the root.
or we could use our PC and the USB connection.
but then you couldn't backup on the go.

sorry, haven't had time today..

[Dany-69]

we need to boot from sd to gain (writing-)access to the root.
or we could use our PC and the USB connection.
but then you couldn't backup on the go.

sorry, haven't had time today..

Ahhhhhh ok :D
So the procedure through pc should already be feasible :eek:

Can anyone test it ? :p

[abill_uk]

We won't know until we actually try it, but three things I am pretty sure about:

1) We can boot from micro SD card no problem (fanoush has done this)
2) We can backup rootfs using dd - this confirms it : http://metalab.at/wiki/Hack-A-N900/Dump_and_Restore_rootfs_Image (we have access to micro sd storage).

3) We can reflash using the reflasher (see link above)

So what does this mean?

This means we can completely restore the N900 to an exact state!

HOWEVER whats more useful is that we have ACCESS to the rootfs!!!!! I remeber I made changes to one text file - and this bricked my N900, if I could have booted from Micro sd then I could have EASILY fixed it without reflashing!

Either way we should have a way to restore our N900s properly! I don't trust the backup manager.

This is getting very close but i am confused as to how to grab the emmc as well as the rootfs and although you can flash the backup of rootfs the problems might still be there because the problem(s) may be in rootfs and emmc and emmc needs to be flashed along with rootfs to give an entire restore if i am not mistaken.
All i want to do is grab rootfs AND emmc in one hit creating the backup file, so i hope i am thinking the same as you are here.
I wish fanoush was around lol.

[rash.m2k]

This is getting very close but i am confused as to how to grab the emmc as well as the rootfs and although you can flash the backup of rootfs the problems might still be there because the problem(s) may be in rootfs and emmc and emmc needs to be flashed along with rootfs to give an entire restore if i am not mistaken.
All i want to do is grab rootfs AND emmc in one hit creating the backup file, so i hope i am thinking the same as you are here.
I wish fanoush was around lol.

Grabbing rootfs is trickier because it's UBIFS and also because it's the rootfs, so problems with copying files arise.

emmc (or opt rather) is just a plain old ext linux partition! To copy it we simply mount it somewhere and copy the contents. Unlike rootfs there's no need for a .img/bin file for emmc.

EDIT;

I've been a little busy, I was trying to get mythtv setup on my laptop.

[Dany-69]

all dead? :D

[rash.m2k]

all dead? :D

Lol, no not quite, I've got a few other things that are more interesting than this atm! :D

I'm trying to setup a samba server on my laptop and configure it - which is almost done. And also setup mythtv as well.

In addition I've got an O2 Joggler (google it) and currently working on getting openSUSE properly setup on it.

Unfortunately this is not yet at the top of my priority! (Plus I work 5 days a week as well.)

[Dany-69]

Hi guys :)
I got my n900 again :p
But i have some problems to understand all the procedures posted here :(
No one can help me? T_T

[abill_uk]

That's the problem it is not easy to derive a solution.

[abill_uk]

As much as i have looked and looked Linux just does not have the commands needed to use on the N900 to take a complete dump and store it to your pc in any way or form.

[Dany-69]

I think the dd comand runned from another Linux system booted from the sd should run ...
But there is no good how to about this procedure.. :(

I'm not a big noob... but some guides like THIS (http://talk.maemo.org/showpost.php?p=444600&postcount=45) are a bit difficult for me T_T

Have you some experience with this procedure?

PS: i found this... mmmm ... http://maemo.org/packages/package_instance/view/fremantle_sdk_non-free_armel/sdk-fiasco-gen/2.8.2.0.1+0m5/

[abill_uk]

Booting from sd is not going to work, what needs to happen must happen from an external source preferably windows not ubuntu to take a complete copy if the "hard drive" within the N900.

[Dany-69]

Booting from sd is not going to work, what needs to happen must happen from an external source preferably windows not ubuntu to take a complete copy if the "hard drive" within the N900.

I saw some video about n900 booting mer from SD.. :confused:
So i think that a way to make it run should exist :p

[abill_uk]

It is a bit like ripping a dvd for instance only in this case the "dvd" is the N900.

[abill_uk]

Why do you insist on booting from sd? this is not going to get you the end result unless it will start off a dump to an external source and that means everything from rootfs apps docs emails contacts and emmc.

[abill_uk]

HMmmm interesting theory though.

[rash.m2k]

I'm a little busy at the moment so don't have much time to do this - plus I don't have a spare micro sd card to try this.

But i'll give it a try once I get one.

[Dany-69]

I'm a little busy at the moment so don't have much time to do this - plus I don't have a spare micro sd card to try this.

But i'll give it a try once I get one.

I'm trying to boot "mer" on microsd following this guide: http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html

All this in order to use the dd command (but also to try a different operating system ..)..

But I have a problem that afflicts me T_T
I partition the SD using gparted, i format it with ext3 file system...
Then i use the tar command to put all the necessary on the sd, copy the content of the firmware directory, create a file called mer.item in /etc/bootmenu.d, install Bootmenu for n900 ...

Finally i insert the card in the phone, push the power button with the keyboard opened...

I select Sd partition...
Then appears Booting from mmck ecc ecc..
But nothing happens and the phone turn off ... :(

What's the problem ???

[b-man]

I'm trying to boot "mer" on microsd following this guide: http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html

All this in order to use the dd command (but also to try a different operating system ..)..

But I have a problem that afflicts me T_T
I partition the SD using gparted, i format it with ext3 file system...
Then i use the tar command to put all the necessary on the sd, copy the content of the firmware directory, create a file called mer.item in /etc/bootmenu.d, install Bootmenu for n900 ...

Finally i insert the card in the phone, push the power button with the keyboard opened...

I select Sd partition...
Then appears Booting from mmck ecc ecc..
But nothing happens and the phone turn off ... :(

What's the problem ???

hmm, that's odd - what partition do you have mer on? - have you also copied the kernel modules from maemo to mer's /lib/modules directory?

[Dany-69]

hmm, that's odd - what partition do you have mer on? - have you also copied the kernel modules from maemo to mer's /lib/modules directory?

Actually now I have no partitions on the SD ... in the beginning I created two partitions, one ext3 and one fat32, but then, having the suspicion that the bootmenu might recognize the FAT partition as the first one, I formatted the entire microsd as ext3 (using the bootable flag through gparted and labeled "mer").
Thus, through Ubuntu Live, I see the partition "mer" as mmcblk0p1.

Afterwards, boot from N900, appears: "Booting from mer (mmcblk1p1 ext3)..." Which should have nothing wrong because the mmcblk0 in this case should be the internal EMMC and sd should become mmcblk1

However I did not copy the kernel modules from /lib/modules .. The guide that i followed didn't say me to do that... :( .. Should i ?

[b-man]

Actually now I have no partitions on the SD ... in the beginning I created two partitions, one ext3 and one fat32, but then, having the suspicion that the bootmenu might recognize the FAT partition as the first one, I formatted the entire microsd as ext3 (using the bootable flag through gparted and labeled "mer").
Thus, through Ubuntu Live, I see the partition "mer" as mmcblk0p1.

Afterwards, boot from N900, appears: "Booting from mer (mmcblk1p1 ext3)..." Which should have nothing wrong because the mmcblk0 in this case should be the internal EMMC and sd should become mmcblk1

However I did not copy the kernel modules from /lib/modules .. The guide that i followed didn't say me to do that... :( .. Should i ?

Sorry if couldn't reply sooner - i was busy all day yesterday :p

I'd recommend that you copy the kernel modules to your mer partition ;)

Also, just as a future reference, you can use the on-device partition/format memory card steps from my Ubuntu Jaunty Guide (http://talk.maemo.org/showthread.php?t=25975) which should make things a bit faster and easier to understand. ;)

[Dany-69]

Sorry if couldn't reply sooner - i was busy all day yesterday :p

I'd recommend that you copy the kernel modules to your mer partition ;)

Also, just as a future reference, you can use the on-device partition/format memory card steps from my Ubuntu Jaunty Guide (http://talk.maemo.org/showthread.php?t=25975) which should make things a bit faster and easier to understand. ;)

GREAT B-MAN :D
It worked... but the results aren't good ... :confused:

http://www.youtube.com/watch?v=OPydkh6OJco

Too much lag... :(... no battery info ... The power button doesn't work ...
It's something useless...
Could the cause be the low transfer-rate of the microsd? :(

But it's strage because it's a good SDHC 4gb Kingstone... :confused:

Then i tryed to boot the same operating system of easy debian copying all the direcotories and then "firmware" and "modules" .. but it doesn't work -.-

[Dany-69]

No one? o.O