I never do back to back flashing method, it worked before. Just this time not work. Maybe I try flash to plain open mode kernel instead of urs l2fix, then flash ubiboot kernel to try?

I mean i need flash whole device and lost thing again..

Re: Introducing ubiboot N9 (multiboot OS loader)
 

hmm, I am not sure if it can be done without flashing everything, important is that you need to flash first to closed mode and then to open mode, without letting the device boot between the flashes...
It is not enough to flash just closed mode kernel, you need to flash so that the device as whole is in closed mode.

The reason for this procedure is that when the device boots the first time after a clean flash it will prepare a lot of things it needs to do; aegis keys are generated, files created with correct mode etc...

When you do the back-to-back flashing procedure, you make sure that the first boot after flashing is with an Open Mode kernel. This ensures that everything will be created with compatible keys and access modes.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

juiceme explained full

What you might do (to preserve at least MyDocs data) is to omit the
"-F emmc.bin"
but then need to give
"--erase-user-data=secure"

So you will loose for sure all apps and data on /home.
But this is the most error free way to do. With all other methods (delete aegis dirs) you might experience strange things.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

btw
thanks juiceme (and Hurrian) for new version.
Installed yesterday, loaded new kernel 2.6.32.61 and it booted :) (in contrary to the 59 version). Will be my default kernel now!

Understood

Re: Introducing ubiboot N9 (multiboot OS loader)
 

After that,will the warranty warning present?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, unless you disable it first.

The info I gave to TMavica assumes that you have disabled the open mode warning before this procedure.
(you only need to disable it once, after that even reflashing it will not bring back the open mode warning)

Just remember, the warning removal has to be done in closed mode. If you already are in open mode you need to do the following:

1.) flash emmc+firmware to get back to closed mode
2.) remove the open mode warning
3.) flash the device back-to-back closedmode/openmode
4.) enjoy :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

One question here, as I never tried that:
what is the
--suppress-warranty-warning
flag in flasher for?
Could this be used to just flash back-to-back (closed mode/open kernel) and then give this paramter during flashing the open mode kernel?
Worth a try, or? Volunteers, do not step back. ;)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I was told it's a kind of joke :D

What it does, it just suppresses the warranty warning that flasher gives when you invoke it, this one:

Quote:

WARNING: This tool is intended for professional use only. Using it may result in permanently damaging your device or losing the warranty.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

you dont need to flash emmc to get back to closed mode
you dont need to perform --erase-user-data
you can flash only fiasco image and you dont lose MyDocs data, userfs data including conversations, contacts and etc. (but lose all installed apps)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

He he, nice one :)


@coderus
But .aegis and .accounts are on /home (p3). They will not be deleted on 'just' flashing fiasco, right? So how to do then? Again need to delete these dirs? Or are they not created when booting up on closed mode, enabling developer mode and disable warranty warning. Flash back to closed and again open mode (would not be necessary according to your post)?

p.s.: maybe we should open up a new thread for this, as it seems that there is still not a full proven theory?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Good point... Maybe those are overriden when firmware is flashed? The flashing is not "just" flashing, as the APE might do other things as well, for example delete/modify files not on the flashed partition.

Well it should not be too difficult to test, just check the directories, content&timestamps, and then flash just firmware.bin and compare if anything changed.

Another indication should be if you need to re-enter passwords and account details after it...
Personally I have always flashed emmc+firmware if I needed to initialize the device, so I would not know...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

just remove .accounts folder. its enough. as common user you will never get profit after removing aegisfs mounts.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Mee too :), that's the reason I asked again...

You mean remove contents of .accounts folder, not whole directory, right?
Personally I am running my device that way atm (having removed contents of folders .aegis .accounts and .activesync).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That works for the problem with user accounts and passwords, but there are other things that are left hanging.

I do not know exactly what is the reason, but these things affect especially unit startup when Harmattan is ran as 2nd level boot under ubiboot.
If the device is not correctly prepared, there's going to be a lot of process trashing in startup, and some devices / variants are more susceptible to this. In worst case it means that device will not boot, or will do so slowly or not every time.

If this procedure is done like I described, then this will not happen, the device will boot cleanly.

After read, i decided to flash my n9 again..

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi,

First, thank you so much for this marvelous piece of software. It is not only functional, it is pretty and makes not only N9, but open source software in general look better.

I installed it 2 days ago following the instructions in the wiki page, but it didn't work reliably. The simptoms were similar to the ones TMavica is reporting, but sometimes (< 10%) the system booted. So I found the post quoted above, and checked:

I never edited, chmoded or chowned these files, so this is how they were inside preinits.tar. The problem is not that the files belong to an inexistent user, but that preinit_harmattan is not executable. After fixing this, now I can boot successfully all the time.

Please fix preinits.tar!

Now I would like to edit the "info" menu option, can someone point me to a post/document/readme that show me the way?

Thank you so much again!

Edit: also, md5sum of preinit_harmattan is wrong in the wiki.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I flashed the plain open kernel and its booting fine, i added kernels and got nothing to boot at all, NITDroid wouldnt and no kernels for Harmatten would boot, i added the open kernel and even just letting the device go on its own to boot would just black screen and shut down as it appeared but I would need to hold power 8 seconds and then hold power again for it to reboot, I DID get the menu however and could see the OS's and when I had the phone plugged in to the computer on boot it did go in maintenance mode

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have never removed the openboot warning, could that be a reason why i can not boot any kernel? i am back to the openboot kernel and really want to get this working, I am not sure why nothing will boot

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Sorry last post, what version of Ubiboot should i be using in ubiboot2 folder?

@traysh

i just checked and found preinit_harmattan is not execute too, now I chmod +x it and it is excuted same as preinit_nitdroid and preinit.

Will try flash ubiboot see whether will be fixed or not tonight

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OMG you are correct in this, I just checked it and for some reason the Harmattan preinit in nonexecutable.
I am very sorry about this, I'll correct it immediately.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

See the section "Configuration and personification" in the README document.

What you need is animation toolkit source, the latest is animatronics_01112013.tar in the /source/ directory of ubiboot repository.
You need a Linux computer, where you extract that tarball.

• The info text is in file "imagebase/ownerpanel.png", so you need to create a 400x400 sized panel of your choosing, with Gimp or whatever you prefer and replace that image with your custom panel.
• Then, run the script ./create_animations.sh which will build the animation sequences and support files for you. The result is a tarball called "animatronics.tar" in the same directory.
• Next, run the script ./pack_cpio.sh --create animatronics.tar which will create an archive called "ubiboot-02.menus.cpio" in the same directory.
• Copy the CPIO into your ubiboot config directory on the device, and check that the name you give it matches the configuration key G_UBIBOOT_ARCHIVE in your ubiboot.conf.

Now your new info panel will show up in the menu :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It should not make a difference AFAIK, the only problem with the Open Mode Warning is that booting takes longer as the device stops for a while to show up the warning.

I do belive however that the reason you cannot boot correctly is because you have some Aegis conflict, caused by signing keys not been created correctly for Open Mode (see this posting for example: http://talk.maemo.org/showpost.php?p...&postcount=656)

To get rid of the Open Mode warning and Aegis conflicts, you should do the following:

• back up your device, as this is going to erase data on it
• get the correct emmc.bin and firmware.bin for your device variant
• flash device to closed mode
• activate developer mode to get console
• give command disclaimer-cal remove View-openmode as user to get rid of the Open Mode Warning
• do the back-to-back closedmode/openmode flashing to get to open mode with correct Aegis keys created.
  (Note that is is not enough just to flash open mode directly, your keys have been already created and you will get the same Aegis problems as before...)
• set up your kernels
• set up your ubiboot config files
• flash ubiboot kernel

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The latest is ver. 0.3.5

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have corrected that to the preinits.tar file now.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

To juiceme's honor:
it seems I am the bad guy here. :(
I sent original harmattan preinit to juiceme via e-mail, but it took a short stop on MyDocs (vfat) for attaching to mail. This for sure removed all user rights from that file. As juiceme is only used to Linux, he did not check it once more before taring?
So my bad (should have zipped from ext drive). I do apologize!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

True enough, however hopefully the worst that happeded was some extra work and frustration :D
PS as a bonus added also preinit_firefox to the tarball...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Huh!
Going to check against my self-made one .....
:)

--
Okay, looks pretty much the same. :D

Backup/restore with ubiboot N9 (multiboot OS loader)
 

Short tutorial to backup full device with ubiboot (for console enthusiasts only :)):

- power down device

- connect USB to device and PC (be it Linux or Windoze flavor)

- wait for maintenance mode screen
at this time you should notice also mounted drive(s) on PC,
on Windoze only p1, on Linux all partitions (according to your ubiboot.conf)
do NOT touch that drive under Windoze yet

- open a console on PC and telnet/ssh into N9

- create some mount points
mkdir /mnt/p1
mkdir /mnt/p2
mkdir /mnt/p3
mkdir /mnt/px #for other partitions you might have

- mount MyDocs read-write, rootfs (p2) and home (p3) read-only
mount -w -t vfat /dev/mmcblk0p1 /mnt/p1
mount -r -t ext4 /dev/mmcblk0p2 /mnt/p2
mount -r -t ext4 /dev/mmcblk0p3 /mnt/p3

- tar up rootfs and home on MyDocs
cd /mnt/p2
tar -cvf /mnt/p1/p2.tar *
cd /mnt/p3
tar -cvf /mnt/p1/p3.tar *

you may also use
tar -cvzf /mnt/p1/pX.tar.gz *
for compressed tar, but it will take ages...

- now unmount all
umount /mnt/p1
umount /mnt/p2
umount /mnt/p3

- if you like, grab the tar files on N9/MyDocs NOW via the mounted drive from PC (do this first at this stage/unmounting as MyDocs seems mountable twice from PC and from N9, read access should not get you into trouble, but concurrent write access may do so, to the extent of fully broken file system)

That's it. Full backup of device done under Windoze with the help of ubiboot maintenance mode.
For Linux you may do it the same way or just directly mount and tar from PC.

Thanks again to juiceme for providing such wonderful tool!


Just thought I write it down, even all above is obvious. ;)
Maybe worth to add to wiki or Readme?



--
Restore:

- power down device

- connect USB to device and PC (be it Linux or Windoze flavor)

- wait for maintenance mode screen
at this time you should notice also mounted drive(s) on PC,
on Windoze only p1, on Linux all partitions (according to your ubiboot.conf)
do NOT touch that drive under Windoze yet

- open a console on PC and telnet/ssh into N9

- create some mount points
mkdir /mnt/p1
mkdir /mnt/p2
mkdir /mnt/p3
mkdir /mnt/px #for other partitions you might have

- mount MyDocs read-only, rootfs (p2) and home (p3) read-write
mount -r -t vfat /dev/mmcblk0p1 /mnt/p1
mount -w -t ext4 /dev/mmcblk0p2 /mnt/p2
mount -w -t ext4 /dev/mmcblk0p3 /mnt/p3

- untar rootfs and home from MyDocs
cd /mnt/p2
rm -fr *
tar -xvf /mnt/p1/p2.tar
cd /mnt/p3
rm -fr *
tar -xvf /mnt/p1/p3.tar

if you have compressed tar.gz, use
tar -xvzf /mnt/p1/pX.tar.gz

- now unmount all
umount /mnt/p1
umount /mnt/p2
umount /mnt/p3

If you need to copy the backup from PC back to N9 first, then do it as first step before mounting.

Disclaimer: verified the restore up to now only to copy Harmattan root from p2 to p5 and it worked. So I am convinced, this will work.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks for the guide, that's pretty much how it can be accomplished.
One minor suggestion, though;

For people using Windows, and hence never needing to mount the ext4fs partitions outside the device, I suggest you change the key
G_EXPORTED_PARTITONS="/dev/mmcblk0" to G_EXPORTED_PARTITONS="/dev/mmcblk0p1"

Reason for that is that even as the WinPC is not going to try to mount other than mmcblk0p1 ever, it is still safer not to try to export the other partitions if you are going to mount them inside the device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yep, generally a good idea.
BUT...
... this is one thing I wanted to ask you either:
when using maintenance mode with windoze (having G_EXPORTED_PARTITONS="/dev/mmcblk0"), I only get the first partition offered and it is mounted automatically. The others not. So no prob at all, right? Or we would get device busy error, or?
When using modified usbmoded, I do get all partitions offered and may mount my extfs partitions manually.
I would like ubiboot to behave the same way!?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hmm, that indeed so? But can you mount the rest of the partitions in Windows anyway, even if offered from the device since I thought there's some kind of ext2fs support but no ext4fs...?
Now I am not sure about this and have to test a bit. However, as for Linux, when /dev/mmcblk0 is offered all partitions are seen by the host computer.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Isn't this an ext4fs for windows:
Paragon_ExtFS_for_Windows_2.41.exe ?
https://www.google.com/search?q=Para...ndows_2.41.exe

https://www.google.com/search?q=Para...4+for+windows8

http://www.paragon-software.com/home/extfs-windows/

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, now I have tested a bit :D

The results are as follows;

• if you set G_EXPORTED_PARTITONS="/dev/mmcblk0", you will get all partitions exported.
• if you set G_EXPORTED_PARTITONS="/dev/mmcblk0p1", you will get just one partition exported.
• if you set G_EXPORTED_PARTITONS="/dev/mmcblk0p1,dev/mmcblk0p2", you will get both partitions 1 and 2 exported.
  (the driver will contain 2 different luns in this case, one for each partition)

Now this above is what happens on Linux.
My guess is that on Windows the 1st and 2nd behave similarily, only the partition 1 gets exported, but the 3rd case would export both partitions correctly.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, this is OSS evolving, this kind of thing happens. Besides, we are all grown ups, we can deal with bugs.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Successful after use new preinit..lucky I havent reflash it yet

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Absolutely correct ( I assume ;) ).
Windoze recognizes only first partition on flash drives (default).
In usbmoded I have defined the partitions item by item (but without root and home, you remember? :D). And it worked, so could have thought of trying it the same way (dumb me :)).
Once more thank you.

Will test and let you know.
About ext support: I am using ext2Fsd, as it is OSS. ext2 rw, ext3 r(w), ext4 ro. But I normally need only to read from ext, When I have the need to write, I rely on a VM.
Paragon is closed (despite having had good experiences with their SW). Do not know about their reliability about write support.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi, is it correct to simply put the new preinits.tar to MyDocs and do tar -xvf preinits.tar -C / as in the wiki or? Thanks