maemo.org - Talk - 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

The scripts are missing in animatronics_01112013.tar, but I got then in an earlier version, thanks!

juiceme

2013-11-02 10:12

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by traysh (Post 1383866)

The scripts are missing in animatronics_01112013.tar, but I got then in an earlier version, thanks!

? Really ?
I'll have to check that, since the scripts have changed a bit since the last tarfile and you need the latest version because there is a version check... The files are not compatible :(

I am on the road but I'll do it later.

Meanwhile, you can pull the latest version directly off the SVN server.

juiceme

2013-11-02 20:07

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by traysh (Post 1383866)

The scripts are missing in animatronics_01112013.tar, but I got then in an earlier version, thanks!

Can you please recheck what you have, I just downloaded the animatronics_01112013.tar file myself, and all the needed scripts are in the archive.

gemfield

2013-11-04 15:40

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1383790)

Yes, that is the correct command to do it.
There are 3 preinit fules which will be extraced correctly with that.

If I have wrote some random data to /dev/mtd0 by mistake, will it influence the N9 reboot?

juiceme

2013-11-04 17:21

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by gemfield (Post 1384319)

If I have wrote some random data to /dev/mtd0 by mistake, will it influence the N9 reboot?

/dev/mtd0 is the bootloader, so messing with it is generally what you do not want to do, ever.
If you manage to write s**t there your device will not be able to boot, not now and never again.
And they will not be able to fix that in Nokia Care, or in any service shop since it requires equipment present only at the factory and that was closed down a long time ago.

But the question is whether you were able to damage it?

If you are in Open Mode, it depends on how you did the writing. There are some hazardous procedures, but bootloader is locked down against simple intrusion.

If you are in Closed Mode and managed to tamper with it... well, then the odds are pretty badly against you.

Udemzy

2013-11-05 11:38

Re: Introducing ubiboot N9 (multiboot OS loader)

Please help. I can't boot into harmattan with ubiboot. It just gets stuck with a black screen. I waited a while and nothing happen.
Nitdroid only boots with zlmage.pr13. e-yes l2fix doesn't work. Also in nitdroid usb debugging doesn't work nor charging even after plugging it before boot.

Storm_11

2013-11-05 12:01

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Udemzy (Post 1384471)

you're not alone, I've had the same issue with ubiboot too. tried a few different harmattan based kernels, all with the same issue. Black screen, but I haven't got around to getting debug logs yet, havent had the time. HW revision 1501

In the meantime, reflash the standard open kernel if you need to get back into harmattan.

sudo flasher -a <yourmainfirmware.bin> -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

TMavica

2013-11-05 12:06

The preinit.tar is wrong before, that make me same problem, juiceme reuploaded again see whether u use it can fix or not

Storm_11

2013-11-05 12:35

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by TMavica (Post 1384478)

The preinit.tar is wrong before, that make me same problem, juiceme reuploaded again see whether u use it can fix or not

perfect, saw the discussion about the file, but missed the first post about the issue. thanks.

TMavica

2013-11-05 12:38

U are welcome.

Udemzy

2013-11-05 14:08

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Storm_11 (Post 1384476)

Thanks but I use sillyboot instead. But I want ubiboot, would really want to triple boot or penta boot.

gemfield

2013-11-05 15:18

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1384343)

Thanks for your answer.
1, My N9 is in closed mode. in order to use ubiboot, now I am learning to be familiar with the N9 OS :)
2, Here is my code:
RM696-21-3_PR_003:~# cat mtd.c

Code:

#include <stdio.h>

#include <fcntl.h>

#include <sys/ioctl.h>

#include <mtd/mtd-user.h>



int main()

{

    mtd_info_t mtd_info;

    erase_info_t ei;

    int i;



    unsigned char data[20] = { 0xAA, 0x55, 0xAA, 0x55,0xAA, 0x55, 0xAA, 0x55,0xAA, 0x55, 0xAA, 0x55,0xAA, 0x55, 0xAA, 0x55,0xAA, 0x55, 0xAA, 0x55};

    unsigned char read_buf[20] = {0x00};



    int fd = open("/dev/mtd0", O_RDWR); 



    ioctl(fd, MEMGETINFO, &mtd_info);



    printf("mtd0 type: %x , mtd0 total size: %x bytes , mtd0 erase size: %x bytes\n",mtd_info.type, mtd_info.size, mtd_info.erasesize);



    ei.length = mtd_info.erasesize;



    for(ei.start = 0; ei.start < mtd_info.size; ei.start += ei.length){

        ioctl(fd, MEMUNLOCK, &ei);

        printf("Eraseing Block %#x\n", ei.start);

        ioctl(fd, MEMERASE, &ei);

    } 



    lseek(fd, 0, SEEK_SET);

    read(fd, read_buf, sizeof(read_buf));



    for(i = 0; i<20; i++)

        printf("buf[%d] = 0x%02x\n", i, (unsigned int)read_buf[i]);



    lseek(fd, 0, SEEK_SET);

    write(fd, data, sizeof(data));



    lseek(fd, 0, SEEK_SET);

    read(fd, read_buf, sizeof(read_buf));



    for(i = 0; i<20; i++)

         printf("buf[%d] = 0x%02x\n", i, (unsigned int)read_buf[i]);





    close(fd);

    return 0;

}

3, Here is the result:
RM696-21-3_PR_003:~# gcc mtd.c -o mtd
RM696-21-3_PR_003:~#./mtd

Code:

mtd0 type: 4 , mtd0 total size: 100000 bytes , mtd0 erase size: 40000 bytes

Eraseing Block 0

Eraseing Block 0x40000

Eraseing Block 0x80000

Eraseing Block 0xc0000

buf[0] = 0xa0

buf[1] = 0x00

buf[2] = 0x00

buf[3] = 0x00

buf[4] = 0xf0

buf[5] = 0x2d

buf[6] = 0x00

buf[7] = 0x00

buf[8] = 0x00

buf[9] = 0x00

buf[10] = 0x00

buf[11] = 0x00

buf[12] = 0x00

buf[13] = 0x00

buf[14] = 0x00

buf[15] = 0x00

buf[16] = 0x00

buf[17] = 0x00

buf[18] = 0x00

buf[19] = 0x00

buf[0] = 0xa0

buf[1] = 0x00

buf[2] = 0x00

buf[3] = 0x00

buf[4] = 0xf0

buf[5] = 0x2d

buf[6] = 0x00

buf[7] = 0x00

buf[8] = 0x00

buf[9] = 0x00

buf[10] = 0x00

buf[11] = 0x00

buf[12] = 0x00

buf[13] = 0x00

buf[14] = 0x00

buf[15] = 0x00

buf[16] = 0x00

buf[17] = 0x00

buf[18] = 0x00

buf[19] = 0x00

4, Seems that there have no warning or error, but mtd0 data is still old(i.e. write to mtd0 failed in fact).

5, What is the reason that write to mtd0 looks success but in fact failed?
6, If I reboot my N9, any risk here?

Thanks.

juiceme

2013-11-05 15:38

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by gemfield (Post 1384499)

Thanks for your answer.
1, My N9 is in closed mode. in order to use ubiboot, now I am learning to be familiar with the N9 OS :)
2, Here is my code:
RM696-21-3_PR_003:~# cat mtd.c
3, Here is the result:
RM696-21-3_PR_003:~# gcc mtd.c -o mtd
RM696-21-3_PR_003:~#./mtd
4, Seems that there have no warning or error, but mtd0 data is still old(i.e. write to mtd0 failed in fact).

5, What is the reason that write to mtd0 looks success but in fact failed?
6, If I reboot my N9, any risk here?

Thanks.

Ah, I see you are really delibrately trying to write into mtd0. Risque, that is :D

Well, for starters, even as you are in Closed Mode, you do not have enought credentials to do what you're after. :D
The device has pretty good safeguards against that, so even as you run that code as root it still will fail silently due to missing credentials. Now, if you do want to destroy your device permanently, you can run your code under Inception to gain privilidges to make the write happen for real.

As for booting the device now, you should be safe as your code did not really modify mtd0.

plourde

2013-11-05 18:49

Re: Introducing ubiboot N9 (multiboot OS loader)

what exactly do you mean by flashing to closed/open mode back to back i don't understand exactly, please elaborate the commands for this if you don't mind, thanks again, i just ref lashed the device using
sudo flasher -F <yourmainfirmware.bin> -F <youremmc.bin> -f and then flashed the open kernel, please correct what I am doing so Aegis does not have issues, thanks again

plourde

2013-11-05 19:23

Re: Introducing ubiboot N9 (multiboot OS loader)

I got ubiboot booting my device by reading the readme file in ubiboot downloads, i didnt get rid of the openmode warning, now that i got this far is there an easy way to do that, i tried and it gave an error, Thanks again

juiceme

2013-11-05 20:17

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by plourde (Post 1384547)

The back-to-back flashing procedure is to make sure that when the device boots up the first time after a clean flash, it boots to open mode.
Why this is important; After a clean flash, the first boot creates the aegis keys for the device. These keys are different for open mode and closed mode, and if you have closed mode keys in open mode device you will have lots of random problems.

So, how this is done, is you need to clean-flash, and then immediately flash an open mode kernel before the device boots after the clean flash.

In Linux you can enter 2 flashing commands on the same row, separated by semicolon, so that when first command is executed, the second command is executed right after it:

sudo flasher -F firmware.bin -F emmc.bin -f -R ; sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

juiceme

2013-11-05 20:20

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by plourde (Post 1384551)

If you want to remove the openmode warning, you need to flash it clean to cosed mode first;

sudo flasher -F firmware.bin -F emmc.bin -f -R

Then remove the warning:

disclaimer-cal remove View-openmode

And last, do the back-to-back flashing.

gemfield

2013-11-06 14:24

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1383308)

@plourde, you do not need to remove sillyboot at all, sillyboot and ubiboot operate at different boot phases.

How sillyboot works:

boot loader starts up the flashed kernel just as usual
last part of kernel startup is call to /sbin/preinit which does number of things before launching up /sbin/init
sillyboot is a modification of /sbin/preinit which allows starting up different init, based on user selection

How ubiboot works:

boot loader starts up the ubiboot kernel instead of device kernel
ubiboot runs a self-contained linux minidistro which has many things, including the boot menu selection
based on user selection, ubiboot loads up the next level kernel and set sup the correct boot environment.
a) for Harmattan, it prepares kernel to run /sbin/preinit_harmattan from mmcblk0p2.
b) for Nitdroid, it prepares kernel to run /sbin/preinit_nitdroid from mmcblk0p2.
c) for Nemo, it prepares kernel to run /sbin/init from mmcblk0p4.
d) for Firefox, it prepares kernel to run /sbin/preinit_firefox from mmcblk0p2.
e) and so on...
last thing what happens, is that ubiboot executes the loaded 2nd level kernel, which goes on and starts the prepared preinit/init file.

So, now you understand that when you use ubiboot, your sillyboot will never be run at all, the modified /sbin/preinit that is sillyboot is sidestepped totally.

To install ubiboot, this is the simple list of things what to do:
1.) copy the file ubiboot.conf to your /home/userMyDocs/boot/ directory
2.) copy the cpio archive to your /home/user/MyDocs/boot/ directory
3.) copy your kernels to /boot/ directory
4.) copy the preinits to /sbin/ directory
5.) flash the ubiboot kernel

That's it. And remember to check that ubiboot.conf has the correct list of kernels that you copied to /boot/

There are dozens of things you could do differently but this is the basic setup.

Hi, juiceme, I am really intresting in that how ubiboot works:
1, /dev/mtd0 is the bootloader and locked by Nokia, then why it can start the ubiboot kernel? Isn't it can only load official kernel with Nokia signature? Does ubiboot kernel have such signature?
2, what is the difference between /dev/mtd0 bootloader and the Nolo bootloader? If they are different, then which partion that the Nolo bootloader located?

juiceme

2013-11-06 15:08

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by gemfield (Post 1384655)

The bootloader starts any kernel that's correctly stored to the kernel partition (which is mtd2, by the way)
The bootup behaves a bit differently, however, depending on if the kernet is signed with Nokia certificate or not.

If the kernel is "Original Nokia-signed kernel", the device unlocks access to the HW-protected trusted-mode registers and functionality, allowing system trusted services to do prectically anything on the device HW.

If the kernel is not signed correctly, the device locks the trusted mode access and there are some things that cannot be done. (for example the writing to mtd0 that you attempted in your code...)

Ubiboot kernel is not signed by Nokia, if it was things would be very different indeed :D

To use ubiboot, you do not need to mess with MTD, or do any esoteric trics, it is enough just to flash it to the device with the regular flasher.

peterleinchen

2013-11-07 08:26

Re: Introducing ubiboot N9 (multiboot OS loader)

@juiceme
I have sometimes strange selection behaviour?

I have 5 items for harmattan (also configured number correctly), but sometimes when I press a bit below the fifth entry, I get:

Quote:

Nov 6 08:40:08 (none) user.notice root: Started animated OS selection menu
Nov 6 08:40:12 (none) user.notice root: Selected second level menu for OS2
Nov 6 08:40:14 (none) user.notice root: Drawing second level menu items for OS2
Nov 6 08:40:14 (none) user.notice root: Get menuitem for OS2 (5 lines)
Nov 6 08:40:18 (none) user.notice root: Selecting Harmattan OS, running kernel
Nov 6 08:40:19 (none) user.notice root: Cannot load Harmattan kernel
Nov 6 08:40:19 (none) user.notice root: Boot OS/kernel selection failed
Nov 6 08:40:19 (none) user.notice root: Saving ubiboot log files

But when I reboot and take care to press the fifth row(s) exactly then it boots up fine:

Quote:

Nov 6 08:41:08 (none) user.notice root: Get menuitem for OS2 (5 lines)
Nov 6 08:41:12 (none) user.notice root: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage_2.6.32.61-plus_20131030
Nov 6 08:41:13 (none) user.notice root: Loading kernel /boot/Harmattan/boot/zImage_2.6.32.61-plus_20131030
Nov 6 08:41:13 (none) user.notice root: kexec_load() successful
Nov 6 08:41:13 (none) user.notice root: Restarting to selected OS
Nov 6 08:41:13 (none) user.notice root: Saving ubiboot log files

Any idea? [maybe next logger version outputs also number of selected item? ]

juiceme

2013-11-07 08:40

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by peterleinchen (Post 1384839)

@juiceme
I have sometimes strange selection behaviour?

I have 5 items for harmattan (also configured number correctly), but sometimes when I press a bit below the fifth entry, I get:

Quote:

Any idea? [maybe next logger version outputs also number of selected item? ]

This sure looks like the tap was registered for the non-existing sixth line. I'll have to see the scripts whether there's a bug in them.
What should happen is that the touch-map that is generated contains hooks only for the number of lines present in the menu.

juiceme

2013-11-07 08:51

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1384842)

Oh yeah, there's a bug indeed! Nicely spotted. :D

Code:

juice@osiris:~/animatronics$ svn diff menuscripts/select_os_animated.sh

Index: menuscripts/select_os_animated.sh

===================================================================

--- menuscripts/select_os_animated.sh        (revision 70)

+++ menuscripts/select_os_animated.sh        (working copy)

@@ -429,7 +429,7 @@

   else

     mapfile_line_5=$(echo -e "# mapfile_line_5")

   fi

-  if [ $maplines -gt 4 ]; then

+  if [ $maplines -gt 5 ]; then

     mapfile_line_6=$(echo -e "$X6B 0 $X6E 480 6 65 $7")

   else

      mapfile_line_6=$(echo -e "# mapfile_line_6")

juice@osiris:~/animatronics$

I'll fix that and make you a new cpio to test :)

peterleinchen

2013-11-07 09:01

Re: Introducing ubiboot N9 (multiboot OS loader)

most rapid bug solving ever :D

( yes. I forgot to mention that nothing is highlighted on selection)

juiceme

2013-11-07 09:14

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by peterleinchen (Post 1384848)

most rapid bug solving ever :D

( yes. I forgot to mention that nothing is highlighted on selection)

And here's the correction; http://www.swagman.org/juice/ubiboot..._07112013.cpio :D

peterleinchen

2013-11-07 20:37

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1384855)

And here's the correction :D

And here is the confirmation. :)
Everything fine now. Thanks.

Mric	2013-11-10 16:20

Re: Introducing ubiboot N9 (multiboot OS loader)

Hey everyone,
In order to use ubiboot I have flashed my device with openkernel mode but I forgot to delete my accounts and therefore I had to re-renter all my passwords after every boot. I have have tried to fix my account problems but I made it worse and now I can't connect as all to any service, it keeps telling me "unknown error, try again later".
I have backed up all my important files and pictures and now I would like 'reflash' harmattan. If I understand right I don't need to flash it because I'm using ubiboot right ? So my question is what is the equivalent of flashing to start fresh under ubiboot?
Thank you

juiceme

2013-11-10 17:30

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Mric (Post 1385490)

Yes, to correctly flash the device for OpenMode is not just for ubiboot, but it's best to do that for any kind of OpenMode kernel.

The correct way to enter Open Mode is the back-to-back flashing where you first flash the device like in "normal closed mode flashing", both emmc and rootfs. Then you immediately flash the device with an Open Mode kernel, without letting the device to boot up between the two flashing rounds.

If you perform this correctly, the device will start up in Open Mode so that aegis keys are created correctly. This will help you avoid all odd problems caused by running device with incorrect credentials (password problems, strange hangups and boots, general slowing and lagging of device...)

I recommend you do this first, and install ubiboot only after it.

peterleinchen

2013-11-10 20:50

Re: Introducing ubiboot N9 (multiboot OS loader)

If you feel like you do not like the warranty warning on boot do the following before above procedure:

- flash device fully (rootfs and emmc).
- boot up, get internet connection, enable developer mode from security settings, open a terminal (console) and type
disclaimer-cal remove View-openmode
- now continue with above guide ()

@juiceme
wouldnt it be easier for you to copy that to first post and only give a pointer ;)

Eztran

2013-11-11 15:59

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1385500)

The correct way to enter Open Mode is the back-to-back flashing...
...If you perform this correctly, the device will start up in Open Mode so that aegis keys are created correctly. This will help you avoid all odd problems caused by running device with incorrect credentials (password problems, strange hangups and boots, general slowing and lagging of device...)

Does this include the apps crashing on app install thing? I kinda assumed that was related to this problem, but a successful back-to-back flash didn't help. Sorry for offtopic'ing.

juiceme

2013-11-11 16:34

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Eztran (Post 1385637)

Does this include the apps crashing on app install thing? I kinda assumed that was related to this problem, but a successful back-to-back flash didn't help. Sorry for offtopic'ing.

I have been told the "apps crashing when installing something" problem is due to running low on memeory on the device, but cannot verify that as I have not ever encountered that problem myself.

I would be intrested in knowing what are the apps that people see crashing anyway? Are those some self-installed applications or the defult set that come with N9 and are always running (grob, fenix,...?)

Eztran

2013-11-11 16:44

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1385641)

I have been told the "apps crashing when installing something" problem is due to running low on memeory on the device, but cannot verify that as I have not ever encountered that problem myself.

Quote:

Originally Posted by juiceme (Post 1385641)

Are those some self-installed applications or the defult set that come with N9 and are always running (grob, fenix,...?)

Certainly grob, as I said the Store dies a lot (and didn't do so without openmode), built-in settings apps, etc. I can't think if anything non-Nokia crashes for this reason offhand, will experiment.

EDIT: Wait, yes I can. Warehouse has the same problem, and I'm pretty sure that doesn't have a preloader.

Further info, after testing with a fresh flash. This may be old news to many, but I'm just pooling all the info I can collect.

These crashes always happen in the actual install, not while downloading or unpacking (unsurprisingly). They can also happen when uninstalling apps.

Unless the app killer is extremely overzealous, or memory usage spikes faster than I can check, OOM is not the only problem here - I managed to get Warehouse and grob to crash with >300MB of RAM free.

Some apps don't crash at all, despite everything else doing so. I also haven't seen anything running directly from Terminal crash yet (Fingerterm, however, will crash), including apps which do normally.

Can't test any further as it's mysteriously stopped happening for a bit.

gemfield

2013-11-16 16:03

Re: Introducing ubiboot N9 (multiboot OS loader)

I have installed ubiboot-02_0.3.5_301013.tar successfully on black n9. However, I found
/usr/bin/show_png /usr/share/themes/blanco/meegotouch/images/system-services/booting.png (which is in /sbin/preinit_harmattan) didn't work, it didn't show my customized png file.

TMavica

2013-11-16 16:09

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Eztran (Post 1385642)

Seems a little unlikely to me; I rarely have many apps open, and I've seen the Store crash itself with nothing else open at all. OOM would also surely happen with a closed kernel too, and I've never seen these crashes outside openmode.

Certainly grob, as I said the Store dies a lot (and didn't do so without openmode), built-in settings apps, etc. I can't think if anything non-Nokia crashes for this reason offhand, will experiment.

EDIT: Wait, yes I can. Warehouse has the same problem, and I'm pretty sure that doesn't have a preloader.

Further info, after testing with a fresh flash. This may be old news to many, but I'm just pooling all the info I can collect.

These crashes always happen in the actual install, not while downloading or unpacking (unsurprisingly). They can also happen when uninstalling apps.

Unless the app killer is extremely overzealous, or memory usage spikes faster than I can check, OOM is not the only problem here - I managed to get Warehouse and grob to crash with >300MB of RAM free.

Some apps don't crash at all, despite everything else doing so. I also haven't seen anything running directly from Terminal crash yet (Fingerterm, however, will crash), including apps which do normally.

Can't test any further as it's mysteriously stopped happening for a bit.

me too. Apps self closing after install or uninstall, but not everytimes, this only happened in open mode, but not in normal mode

juiceme

2013-11-16 17:36

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by gemfield (Post 1386911)

You checked that it was the "/sbin/preinit_harmattan" for sure, and not "/sbin/preinit" for example?
What did get shown when your boot picture should have loaded, nothing or just the pulsing "NOKIA" logo?
To make sure you really ran code in the preinit to the place where you show the picture, you could add something like;

Code:

echo "testing" >> /root/my_test_file

or something next to the place where you show the bootup picture.
Then, after the boot go and check that the statement had executed.

juiceme

2013-11-16 17:38

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by TMavica (Post 1386915)

me too. Apps self closing after install or uninstall, but not everytimes, this only happened in open mode, but not in normal mode

After that happens, I'd like to see a snip off your syslog, if something can be seen from there...?

gemfield

2013-11-17 02:01

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1386936)

Code:

echo "testing" >> /root/my_test_file

or something next to the place where you show the bootup picture.
Then, after the boot go and check that the statement had executed.

Yes, it is /sbin/preinit_harmattan.

Code:

echo "gemfield2" > /root/gemfield2.log     

        if [  -f /usr/share/themes/blanco/meegotouch/images/system-services/booting.png -a -x /usr/bin/show_png ]; then

            /usr/bin/show_png /usr/share/themes/blanco/meegotouch/images/system-services/booting.png

            echo "gemfield3" > /root/gemfield3.log      

        # fallback to bmp 

        elif [  -f /usr/share/themes/blanco/meegotouch/images/system-services/booting.bmp -a -x /usr/sbin/show_bmp ]; then

            /usr/sbin/show_bmp -i /usr/share/themes/blanco/meegotouch/images/system-services/booting.bmp

        fi

And I put echo "gemfield2" > /root/gemfield2.log in front of showpng and also put echo "gemfield3" > /root/gemfield3.log behind showpng, turned out both are excuted. But still, the customized png didn't show on screen when boot N9.

gemfield

2013-11-17 02:11

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi, juiceme, another question:
As long as I didn't flash /dev/mtd0, then N9 can always be recovered by flasher tool?

juiceme

2013-11-17 14:10

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by gemfield (Post 1386995)

Hi, juiceme, another question:
As long as I didn't flash /dev/mtd0, then N9 can always be recovered by flasher tool?

Well, almost always. Unless you trash your cal and/or mess with your MTD you will most propably be able to fix your device with a reflash.

Eztran

2013-11-17 18:56

Re: Introducing ubiboot N9 (multiboot OS loader)

1 Attachment(s)

Quote:

Originally Posted by juiceme (Post 1386937)

After that happens, I'd like to see a snip off your syslog, if something can be seen from there...?

Here's one (why I haven't looked at the syslog yet, I can only explain with 'whoops'). Can't tell exactly where it happens as I forgot to get the time, but it was definitely within this (could be line 13 onwards? Certainly after this you can see apps exiting/restarting)

All times are GMT. The time now is 12:06.

Page 18 of 35

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8