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 ..

Re: Introducing ubiboot N9 (multiboot OS loader)
 

When you look at the device filesystem when running harmattan, then the correct place is /boot/ as your mmcblk0p2 is mounted as /

When you look at the device filesystem when running ubiboot, the same location becomes /boot/Harmattan/boot/ because your / is now a RAMFS instance, and your mmcblk0p2 is mounted at /mnt/2/, which is symlinked to /boot/Harmattan/ :D


What happens when your boot does not succeed, will the device just remain with black screen, does it reboot back to menu, or does it start loading Harmattan and then stop?

What is your device's HW revision?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

1- Boot the device press the MeeGo button the device Shutdown
2- Boot the device again choose the MeeGo button device Shutdown
3- Boot the device choose the MeeGo button the Nokia annimation apears and phone

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, now as you have Meego Harmattan running, can you check the ubiboot log which is created on your device as; "MyDocs/boot/ubiboot.log"

For each time you start device with ubiboot you will find an entry in the log, can you post that log somewhere?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Possibly an OTA upgrade ?

So do a:
and good luck.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Here it is :
https://www.dropbox.com/s/7ccb859q0zsi0ex/ubiboot.log

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks.

According to the log, each time you boot Harmattan, it should start normally as far as ubiboot is concerned:

Jan 2 11:13:42 (none) user.notice root: Loading kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Jan 2 11:13:42 (none) user.notice root: kexec_load() successful
Jan 2 11:13:42 (none) user.notice root: Restarting to selected OS

If there was a problem that ubiboot could detect, you would see something else than "kexec_load() successful" in the logfile.
Now, the problem is then something that happens after kexec() which starts the 2nd stage kernel.

Now, I presume your harmattan has to be PR1.3 level, as else you propably could not start the zImage_2.6.32.54-openmode_l2fix kernel at all. (it would require an older PR kernel to match the OS)

So, most propably it is an aegis-related problem in startup. Can you check in your /var/log/syslog (and possibly /var/log/syslog.old) if there is something defilite that occurred when you tried starting harmattan and failed?

One thing that comes to mind, in which way have you entered Open Mode? Unless it is by back-to-back-closedmode-openmode flashing, it can leave your aegis in a state that causes all kinds of funny business, includeing but not limited to boot problems. :mad:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I flashed nitdroid kernel to enter openmode .. Didnt flash the openmode_fix

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That is also OK, it forks with any openmode kernel, but the important thing to do is to first flash it fully Closed Mode and then flash to Open Mode, without letting the device boot between the flashings.

If you do it that way, your device aegis keys will be created for Open Mode and everything will work much better.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Nice service, but not available from N9:
;)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Sometimes I have the same boot problem and now I know why :)
Do you think the same problem affects also backups? For example restore in open mode from a backup done in closed mode? :eek:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yep, for sure ...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have tried this and I, again, have 8MB partition like the other guys. So even after flashing with --no-preserve !

My phone is RM-696 rev. 1507 (16GB black model)
Can you guys confirm you solved the "small partition" issue and how exactly?

BTW I can tether-boot Sailfish with this command in Linux:
flasher -k zImage_2.6.32.54-ubiboot-02_301013 -l -b

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, it will affect that. If you have a backup taken when you have entered Open Mode accidentally or not correctly and you take a backup of that, restoring that backup later will re-introduce the problems... :p

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If flashing with "--no-preserve" does not cure it, then it is very problematic :(


Yes, that will work as when you load it up with flasher in startup mode it never needs to be flashed to MTD2, and it will work correctly.

Now what I am thinking, it would be possible to make a tiny-version of ubiboot, with reduced maintanance mode (for example, no ssh, only telnet access) and if I strip it down enough it will fit onto 8M partition...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme did you tried just starting bme in maintenance mode? it should start charging :) with bmestat you can try to check it.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have tried it, but it does not work like that, it needs a lot of other stuff around unfortunately.

Loading up the BME module is not enough, it needs the DSME server also. However, that is not enough to work, it needs the DBUS framework and some additional crap around to work also... :mad:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Do you have time to try stripping it now? I have tried several images so far, and ended up moslo telling me he is unable to repartition and that I may be in trouble :) I'll try reflashing again but this time with erase option which takes time, but should be better for the phone.

Which image do you recommend flashing, anyway?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have Ubiboot-sailfish installed should I flash Ubiboot-02 kernel normally
or I need to delete the current one first ?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It depends what you want to do? Do you want to update to using the normal (6 bootable-OS version) of ubiboot from your current sailfish-only ubiboot?

In that case, you need not flash the ubiboot kernel, since the kernel is same on both versions. Instead, you need to replace your ubiboot-02.035_SF_v1.cpio with the CPIO file for normal ubiboot, and also edit your ubiboot.conf accordingly.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have started to make the stripped-down version, let's see what the final size is but I am quite confident I can get it smaller than 8M :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks a lot!
P.S. I have tried several more firmware versions with erase option but none repartitioned my phone for this task.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

What ? ..how to edit the ubiboot.conf .. And what to edit in it can't I just replace it with anothet one !

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It is a text file in your MyDocs/boot, you can edit it with any text editor. Why you cannot easily just replace it with readymade file is because you need to tune it with your own configuration...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I fon't understand in these stuff

How to uninstall/remove ubiboot .. ?? And re-install it ... is it easier ??

Re: Introducing ubiboot N9 (multiboot OS loader)
 

To uninstall, just flash a regular open mode kernel (like l2fixed or Nitdroid kernel) to the device.
Once you have a normal kernel on MTD2 your device will no longer use ubiboot :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

then I can install ubiboot-02.. Normally ??

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Released ubiboot-02 (integrated) version, rev. 0.3.6. minimal

New features:

Not really, just a stripped-down version to fit into 8M kernel partition

Bug fixes:

N/A

General enhancements:

N/A

Work in progress:

N/A

Get it fresh from HERE
See the README file

Installation notes:
This version is compatible with 0.3.5, but not older versions.

The files are also uploaded at Skeiron, for your convenience: http://juiceme.cloud-7.de/ubiboot/ub...2-small_060114

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just to confirm Zvjer's experience, flashing with --no-preserve did not set the MTD partition size to 16M for me either. Thanks for looking into a tiny-ubiboot version. :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Confirmed that the small ubiboot fits into the 8MB kernel partition - ubiboot loads fine and Nitdroid and Harmattan boots! Thanks a lot :) Now on to loading the device with Sailfish..