Finally, my phone arrived yesterday and it's a beauty! :-)
Unfortunately, the N9 Repomirror installation did not work. (I have tried both versions.)
Then, in the end, I decided to flash my phone with the 339 firmware variant available in the first post. (With the windows flasher with windows 10) And luckily, everything went well!
Repomirror installed, development mode enabled! :-)

But I have another question:
I want to flash the open mode "fix" (Image_2.6.32.54-openmode_l2fix) because I want to install ubiboot and Maemo Leste later.

So do I need to re-flash my phone again with firmware and emmc right before doing it, like this?:
flasher -f -F firmware.bin -F emmc.bin -R ; flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

-or -

Can I just flash the open mode kernel anytime I want to, like this:
flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

I would not want to reflash everything again if it is not necessary...
Thanks!!

It's been a while, but I think this article deals with this issue.

Back then the N9 version of Leste was not receiving as much attention as N900 & Droid 4 & Pinephone versions - has this changed since?

Yes, this is the exact article that I am looking at right now and according to this, it should be done in one sweep. (and lose all installed stuff)
But oh well, if it is safer this way, so be it! :-)

>Back then the N9 version of Leste was not receiving as much attention
Yes, you are probably right, I do not have much info, but for example, the archive date of the N9 version is March 2019 and the N900 version is quite fresh, 2021 may... But both archive has the same version of 1.0.
So I do not know.

I am thinking of posting a comment about this.
At least to ask about the situation. The article writer posted that this version did not seem very usable to him. But as far as I know, this is the only alternate os project that is active at the moment.
(And I hear they received additional funds from the EU which is very good...)

SOLUTION:
I just found a big big post: Re-commissioning N9 in 2018
Following its step, I finally installed the N9QTweak package and installed the aegis-dpkg command. With that I was able to install my the bejeweled2 deb file.
I am still not 100% about openmode, but installation log said that it was succesful, so let's hope it was.
------------------------------------------------------------------------------

I have flashed the openmode kernel, but aegis is still active

Here is what I did:
1. Get rid of the warning:
$ disclaimer-cal remove View-openmode
disclaimer-cal: Disclaimer removed from CAL (truncated to zero size)

The flashed my phone like this: (using windows 7)
flasher -f -F main.bin -F emmc.bin -R && flasher -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

The result of that:

Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 32583 kB/s)
Suitable USB interface (phonet) not found, waiting...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339
Image moslo not present
Image tar skipped
Image config skipped

Battery level 86 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3142 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1927 kB/s]
[x] rootfs [finished 100 % 1170221 / 1170221 kB 10693 kB/s]
[x] mmc [finished 100 % 1627219 / 1627219 kB 16753 kB/s]
Updating SW release
Success
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Picked ape-algo from a FIASCO file
Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 32287 kB/s)
Suitable USB interface (phonet) not found, waiting...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 90 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2068 kB/s]
Updating SW release
Success

I also installed n9repomirror and enabled developer mode successfully.

Then I tried to install bejeweled2-full_0.0.60_armel.deb from a game repository and this happened:

/home/user/MyDocs # dpkg -i bejeweled2-full_0.0.60_armel.deb
x509_sigverify: Certificate failure reason: certificate has expired
x509_sigverify: Certificate verification failed
Aegis rejecting bejeweled2-full_0.0.60_armel.deb: package 'ea-mobile-bejeweled2-full' origin cannot be determined -- signature check failed
aegis aborting dpkg -- all listed package files rejected
Compilation failed in require.

So I do not understand what went wrong!
I thought the openmode kernel disables the aegis security system on the phone.
Is there any other way to check if the openmode kernel is active?
It does not seem to work. :-(

Did you try?

Or, set the date back, to a date where the certificate is not expired. Probably like june 2012 will work

Yes, thank you, after installing aegis-dpkg I was able to install!

Oh yeah, but aegis-dpkg should nkt be needed at all on a device with open kernel!
I guess it is really only a cert ossue and setting date should do the trick.

Please give us the output of
uname -a
to check if kernel is really the open one.

There is another trick necessary when replacing original system packages:
AEGIS_FIXED_ORIGIN=com.nokia.maemo dpkg ...
BUT do this only when you know what you do!

Hi,

This is the output of uname -a:
(I flashed the: zImage_2.6.32.54-openmode_l2fix kernel image)

~ $ uname -a
Linux RM696 2.6.32.54-dfl61-20121301 #1 PREEMPT Sat Mar 2 23:11:21 EET 2013 armv7l GNU/Linux

Since then I installed N9Tweaks, repartitioned and installed ubiboot configured with harmattan and maemo leste and everything works okay. (Well except for maemo leste: but at least it boots up but not really usable.)
So this should be an open kernel. :-) But I cannot determine from the text alone. There is no "open" word in it. :-) :-)

>AEGIS_FIXED_ORIGIN=com.nokia.maemo dpkg ...
>BUT do this only when you know what you do!
I certainly do not know about this. But I will try to look it up.

hope everyone is ok

please I need help to choose which firmware to flash to my N9, I used to flashing symbian devices some years ago, but it's a little different with N9

my product code in 059j203 which refers to central Europe and software info shows v 40.2012.21-3_PR_006

I couldn't find a working link for 006, but found the whole firmware files for its actual product code which is 001, is it ok to flash using these files?

I saw 339 or 480 files, what are these??

sorry for the noob qusetions