Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have the same problem as @fejd, my cmdline looks like:

mtdparts=omap2-onenand:512k(bootloader),1408k@512k(config),8192k@ 1920k(kernel),1024k@10112k(log),496768k@11136k(var ),16384k@507904k(moslo)

My N9 info:
Found device RM-696, hardware revision 1509
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001

I also flashed the eMMC with 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin, but my N9's product code is 059H6N5. I wonder if that could be the issue here.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I see what you meant now.. since I flashed the country variant, I cannot flash the ROW image because it's considered a downgrade. :(

This is not really related to Ubiboot anymore, so sorry for going off topic.. but is it possible to go from a country/carrier branded phone to generic/ROW? This post (http://talk.maemo.org/showpost.php?p...2&postcount=22) says it's not possible, but the flashing guide states: "Removing carrier branding - installing 00x variant firmware makes your subsidized N9 act just like an unlocked one", or maybe that just relates to the eMMC.

Currently flashed version is:
DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339
Wanted version (at least it matches my product code) is:
DFL61_HARMATTAN_40.2012.21-3_PR_001

Could it be the case that there's a PR version diff between these two as well?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Someone know where to download the Firefox OS - missing here now:
http://romaxa.info/b2g/b2g_n9_droid_hal_fs.tar.gz

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have backup.u want it?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

juiceme, will ubiboot support direct charging?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

No, unfortunately not yet.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[OT]
Yes, there may be a PR diff, but more related to inclusion of some services (skype, fb, ...) and the like.
But not to what you experience (afaik).

Another yes to to your 'upgrading' the firmware to a carrier/country specific. Now you are at that level (339) and there is no chance to go back, at least for us end users / service points.

And a no to the question of 'unbranding/unlocking'. Unfortunately the ultimate flashing guide is a bit unclear here (as well as eMMM should not be flashed alone but together with firmware in one command): such thing as unbranding is possible but always in conjunction with an upgrade. I.e. if you have a higher FW release (e.g. a PR1.4) you will have the possibility to go 'back' to 001/ROW variant.
I am stuck with highest 480/swiss variant but happy
[/OT]

Hopefully rainisto reads about your problem (mtd formatting) and has an explanation/solution.
I would also create a new thread with well chosen title to give qhole community the chance to answer (with links to most interesting posts in this thread).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes thanks!:)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@cthorell, @fejd,

I consulted @rainisto on this and he suspects that the reason for the MTD partitioning being incorrect on your devices might be an upgrade gone wrong.

At some point the MTD partitioning scheme was changed, and when devices were upgraded to next PR level the MTD should have been partitioned accordingly but if there was some problem then the old partition layout could have been preserved on the devices.

It is worth rtying to reflash the device clean back to Closed Mode with --no-preserve flag added on the command line, this should repartition both MTD and EMMC and fix the problem.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

in my N9
zImage_2.6.32.54-openmode_l2fix
is located in /boot
shouldn't be in
/boot/Harmattan ??
...
I can't boot into MeeGo from the first try .. I must boot my phone and press the MeeGo button (and repeat that process 3 times) so I can boot my N9 ..