Originally Posted by coderus (Post 1349186)

/boot/Nitdroid/boot ?
why not
/boot/Harmattan/boot ?

Originally Posted by peterleinchen (Post 1349069)

About modules you do not need to care, if you do not know.

Originally Posted by peterleinchen (Post 1349069)

Simple question: where did you put the harmattan kernels (when under harmattan OS itself)? Hopefully directly under '/boot' directory?
To me it looks like it just does not find specified kernel. Or just a typo in image names (not really, as it seems
same for all harmattan kernels).
Another question: Nitdroid starts? As that kernel is located in same directory.

Originally Posted by juiceme (Post 1349142)

What is your variant, is it 16/64G and what color?

Originally Posted by HtheB (Post 1349340)

Somehow, my phone can't boot anymore

I wanted to flash the kernel, but I forget to turn off the lock code.
But now, it just shows the Nokia logo, and turn it self off.
After just pressing the power button once, the phone turns on again, shows the nokia logo, and turns off again after like 5-7 seconds.

What should I do (to save the data at least)?

flashing the original kernel didn't solve the problem:
Edit:
meh, to preserve data... I've flashed with:
it booted fine again after that...
I really dont know why I couldnt boot anymore after trying to flash :/

Originally Posted by MAX9 (Post 1349299)

RM-696 NDT Vietnam Black 16gb 059J661

now boot into Nitdroid/Nemo. And Harmattan sometimes?! min. 3 starts i need to really boot up. I will check in a few days.

many thanks in advance

Originally Posted by coderus (Post 1349314)

if no actions after selecting Harmattan - it can boot or can not boot. 1/3, or so.
but! if i touching screen repeatedly after selecting harmattan - it booting fine always!

there is some extra hw input watchdog, i think.
but it very nice to see when phone need to be touched for boot. it need more care and love :D

Originally Posted by juiceme (Post 1349388)

About the lock code, if it's enabled it should not even try to flash any open mode kernel, the flasher will refuse to do it at some point during the flashing and the device should be left in a normally bootable state... however just as everything even that can go wrong and the device left in boot loop...

So, you did manage to boot it after all, OK?

I am just a bit confused but I guess you had the problem first but now it's fixed.
Sometimes it happens that the device goes in a state it will not really boot correctly, but most often that can be solved by forcing it down with 8s press to the power button and then reflashing.

About the ubiboot versions you asked on IRC; nowdays it's strongly suggested that you use ubiboot-02.
if you do not know why you should use ubiboot-01, do not use it. version 02 is better, and I am no longer supporting 01.
Version 01 has some problems that possibly CAN brick your device to FOREVER. It has happened just once AFAIK but even once is enough, and for that reason version 02 was done.

Originally Posted by juiceme (Post 1349390)

Do you have some tweaks active on your device, like fasterN9, overclocking etc...?

Originally Posted by MAX9 (Post 1349542)

Yes, overclock and many tweaks....but:

I flash my device with your new kernel image, now, 6 starts with 6x boot into Harmattan :)

Originally Posted by peterleinchen (Post 1353298)

@juiceme Congrats for finding 1603 problem.

Finally I managed to update to -02.
And it worked out of the box :)

I still have some remarks.

First one is just "cosmetic". Would you mind taking out partition 8 and 9 from configuration and init? Our standard compiled kernels only support up to 8 devices (7 partitions). We would need to have recompiled kernel to support more than 7 partitions (and that would count for ubi kernel as well as harmattan/nitdroid/nemo (possibly sailfish? ;)) kernels.

Second one is I would like to give my device(s) a unique IP address. Even for telnet usage. I know x.x.x.15 is kind of standard, but would like to have my own. So just adding a G_IP_ADDRESS would be fine. (after reading sources I think just adding IP_ADDRESS= to ubiboot.conf will work. Not yet tested) So maybe obsolete.

Third one is a bug (probably). Did you or anyone else was successful with version -02 and using mtd5?
I moved my old v-01 sources to mtd and worked flawlessly with mtd5 kernel. Then I copied ubiboot.conf and cpio to root of mtd5 and also to MyDocs/boot. But the files from mtd are never read and always MyDocs/boot config used. Of course flashe v-02 ubi kernel.
I think you not only need to detach mtd device, but also delete ubi device (-d 0); otherwise moslo will be mounted to ubi1:moslo. So either add ubidetach -d 0 or just exchange ubi0:moslo to ubi1:moslo.

I also moved my nemo from p7 to p6 and everythings works.
Nitdroid without any changes work.

I wanted to boot nit from p5:
I copied my full p2 to p5 (of course together with all kernels in boot), moved nit folder to p5, changed nitdroid partition number to 5 in config. And here comes my problem. Nitdroid does not want to start. It always shuts down with black screen: selection in ubi works, selecting nit kernel works (ubi log kexec load success), but then I have dim-lighted black screen for about a few (30?) seconds and device is off. Power button for 3 s jsust boots up again. I have nfc what is biting me here? Maybe watchdog, as it seems not to be started by default. Maybe we can discuss this on irc next days?
I already added some logging to preinit_nitdrod, and it seems execution gets stuck randomly during execution (sometimes during check_rootfs, sometimes a bit later at mounting p3, but never getting to droidboot???

--edit
Ah and maybe one more (to be confirmed tomorrow morning).
Charging an empty device with wall charger works in act-dead mode. :) But this morning it was still connected to charger and an alarm fired up: no light on display, no UI at all, no possibility to stop the alarm ...

--edit2
Confirming the total absence of UI, when device is on charger in act-dead and an alarm triggers.
An alarm triggered when off (not charging) works nice. Even so when the device is powered on.

Furthermore I experienced that the act-dead charging mode worked only 1 out of 3 times. I had device off, plugged charger, then it booted, shut down (steady LED) and rebooted to telnet console. I pulled charger, pushed power button for 8s and tried again. Same. Only af the third time I saw the charging symbol.
Logs do not tell any suspicious (to me ;)).

Originally Posted by ncik (Post 1353525)

I feel really stupid posting it. But I seem to have hit a roadblock. Where do I place the kernels? What do I mount what folders do I create? I do have the open kernel and I am able to perform all the steps correctly. but I don't know where to place the kernel. I am stumped having been trying this for over a week now. Can someone please help?:confused:

Originally Posted by death_jax (Post 1353533)

You don't have to mount any partition, because you'd better use (because it's updated) the ubiboot-02 method.
Recapitulating with full path, starting from the root (/), for clarity:

• The kernels (only for Harmattan and NITdroid because for Nemo it's different) must be placed into /boot directory.
• The Ubiboot files (described above) must be placed into /home/user/MyDocs/boot directory

Originally Posted by death_jax (Post 1353412)

Also for me charging a powered off phone (obviously with a wall charger) didn't work; instead of charging was activated only maintenance mode.. In fact I used the flasher trick to do it..
The second edit seems the same problem of the first start alarm bug (maybe isn't this the case) that have users (me too) that installed the CODeRUS Unrestricted System UI, solvable with the deactivation of the orientation widget with:

Originally Posted by peterleinchen (Post 1353298)

First one is just "cosmetic". Would you mind taking out partition 8 and 9 from configuration and init? Our standard compiled kernels only support up to 8 devices (7 partitions).

Originally Posted by peterleinchen (Post 1353298)

Second one is I would like to give my device(s) a unique IP address. Even for telnet usage. I know x.x.x.15 is kind of standard, but would like to have my own.

Originally Posted by peterleinchen (Post 1353298)

Third one is a bug (probably). Did you or anyone else was successful with version -02 and using mtd5?

Originally Posted by peterleinchen (Post 1353298)

I wanted to boot nit from p5:
I copied my full p2 to p5 (of course together with all kernels in boot), moved nit folder to p5, changed nitdroid partition number to 5 in config. And here comes my problem. Nitdroid does not want to start. It always shuts down with black screen: selection in ubi works, selecting nit kernel works (ubi log kexec load success), but then I have dim-lighted black screen for about a few (30?) seconds and device is off. Power button for 3 s jsust boots up again. I have nfc what is biting me here? Maybe watchdog, as it seems not to be started by default. Maybe we can discuss this on irc next days?

Originally Posted by peterleinchen (Post 1353298)

Ah and maybe one more (to be confirmed tomorrow morning).
Charging an empty device with wall charger works in act-dead mode. :) But this morning it was still connected to charger and an alarm fired up: no light on display, no UI at all, no possibility to stop the alarm ...

Originally Posted by peterleinchen (Post 1353298)

Furthermore I experienced that the act#ead charging mode worked only 1 out of 3 times. I had device off, plugged charger, then it booted, shut down (steady LED) and rebooted to telnet console. I pulled charger, pushed power button for 8s and tried again. Same. Only af the third time I saw the charging symbol.
Logs do not tell any suspicious (to me ;)).

Originally Posted by death_jax (Post 1353412)

Also for me charging a powered off phone (obviously with a wall charger) didn't work; instead of charging was activated only maintenance mode.. In fact I used the flasher trick to do it...

Originally Posted by ncik (Post 1353525)

I feel really stupid posting it. But I seem to have hit a roadblock. Where do I place the kernels?

Originally Posted by thedead1440 (Post 1353545)

Regarding the alarms, maybe death_jax is referring to unrestricted sys-ui as its known to cause the same issue on non-ubiboot phones too. However although the symptoms are the same here, your case seems to be caused by ubiboot while his problem is a common unrestricted sys-ui issue...

Originally Posted by ncik (Post 1353601)

You don't have to mount any partition, because you'd better use (because it's updated) the ubiboot-02 method.
The kernel/kernels (I put in mind that everything else is in place), with correct names as writed in the README file, for the Harmattan and NITdroid must be placed into the /boot directory of the Harmattan root; the ubiboot-02.menus.cpio file and ubiboot.conf (this one edited with the correct names that you have given to kernels) file must be placed into /boot of the Harmattan eMMC.

Recapitulating with full path, starting from the root (/), for clarity:

The kernels (only for Harmattan and NITdroid because for Nemo it's different) must be placed into /boot directory.
The Ubiboot files (described above) must be placed into /home/user/MyDocs/boot directory


Thanks a lot for the advice. I was finally able to boot using ubiboot but for some reason it boots into Harmattan even when I pick Nitdroid. I am not sure what to do to resolve this issue. Also where to I find the modules to put in the "/lib/modules" directory. Where can I find instructions to install Nemo. Thanks for all the help.

Originally Posted by juiceme (Post 1353573)

So, your device always wakes up to ubiboot when you plug in the wall charger in a powered-down mode?
That should not happen, do you have the setting "G_OVERRIDE_USB_CHARGER_BOOT=1" in your ubiboot.conf?
Also you do need to have G_DEFAULT_OS and G_DEFAULT_KERNEL set up to start a Harmattan kernel.

Originally Posted by death_jax (Post 1353632)

There is no need, for us, to use the /lib/modules..
For Nemo installation I advise you not to think about it now, but maybe later, after a better understanding of boot of Harmattan/NITdroid.
For NITdroid boot problem: did you put the NITdroid kernel file in the right place?
Did you edited correctly the Ubiboot.conf file?
Did you extracted the NITdroid system files correctly?

Originally Posted by ncik (Post 1353704)

I placed the NITdroid kernel at the same place as the other kernel which is /boot. Does the ubiboot.conf need to be changed or should it be the default one I did extract the files to /home/nitrdoid using the instructions provided in the other thread. I was able to successfully boot in nitrdoid before installing ubiboot. Again thanks for your help.:)

Originally Posted by peterleinchen (Post 1353751)

/boot is correct place and /home/nitdroid also correct ...

What about posting output of
ls -al /boot
nitdroid section of ubiboot.conf
/var/log/ubiboot.log and /var/log/ubiboot.dmesg
?

Originally Posted by ncik (Post 1353601)

Thanks a lot for the advice. I was finally able to boot using ubiboot but for some reason it boots into Harmattan even when I pick Nitdroid. I am not sure what to do to resolve this issue. Also where to I find the modules to put in the "/lib/modules" directory. Where can I find instructions to install Nemo. Thanks for all the help.

Originally Posted by juiceme (Post 1353810)

... preinit file ...

Originally Posted by juiceme (Post 1353810)

The difference of the Harmattan boot and Nitdroid boot is in the preinit file it launches, you propably should check that your "/sbin/preinit_nitdroid" file is corret.

And also, as long as you ar onto it, I'd advice you to use the default Harmattan preinit file instead of the one I provide as "/sbin/preinit_harmattan" in the preinits.tar file... many people report that the file in the archive is not so reliable as the original Harmattan preinit. (I trimmed it down a bit, removed parts that I did not think were that useful and maybe I went a bit too far...)

Originally Posted by peterleinchen (Post 1353874)

That reminds me of another remark :cool::
in your cut down preinit_harmattan is only one problem (compared your version with original one), the early start up of usb network! You remember?
I have it commented out, but now as I write I believe a configurable option could be nice to have early telnet/ssh possibilty during harmattan as we have in nitdroid and nemo. But I do not know if it makes sense at all and how to fetch config values in preinit? Do you get me, juiceme? Or just talking bullsh.t? ;)

Originally Posted by peterleinchen (Post 1353874)

For preinit_nitdroid I also would like to fetch config values from ubiboot.conf, but who cares? Only me probably and so I just edit the preinit_nitdroid directly. Maybe one day I will get it starting from p5 !?

Originally Posted by juiceme (Post 1353998)

Well yes you are right maybe that should be removed once and for all... Having that option in preinit messes up the VOIP and in Harmattan you cannot really access the device via SSH until fairly late stage of boot, it's better to get to the device via seral adapter and R&D mode*if that is required.

Originally Posted by topet2k12001 (Post 1354353)

Hi Friends,

I attempted to make my first Wiki Page. :) I used the Ubiboot Steps to make it. Please review and hope you like it. Feedback is most welcome (preferably via PM as I am not always online on the forums).

http://wiki.maemo.org/Ubiboot

Originally Posted by peterleinchen (Post 1354645)

Taking a deeper look into the files compiled into the kernel, I have seen that you symlink /etc/passwd and /etc/group directly hardcoded from /mnt/2/etc/ passwd respective /mnt/2/etc/group.
This is what I wanted to avoid (to have the need for some harmattan files/dirs accessible on p2).

I edited /init (attached), but I am absolutely not sure if this will work.
When, at what time, the ubi system needs passwd and group?
If it is only when launching a shell, I think my small modification (peterleinchen 1) may work. But when it is already needed for starting /init itself, then I am doomed. In first case what about the maintenance mode: do we need it here also as it starts a shell (I have begun to modify: peterleinchen 2)?
Please take a look and let me know, please.

And i thought about changing the log location to /mnt/p1/boot/log (peterleinchen 3) as this location is visible to all operating systems and easily to access for everybody. I thought also about saving log to the selected OS /var/log location, but after rethinking discarded this idea. What do you think? (of course this needs to be fixed in all files then as well)

Originally Posted by juiceme (Post 1354693)

1. Actually the symlinks to /etc/passwd and /etc/group are not used for anything at all at the moment. The files are there just as I am trying to get SSHD to work. SSHD requires the entries to manage userids, and my idea here was to symlink those from the Harmattan side so that I could reuse the Harmattan credentials on ubiboot domain. This is maybe a futile idea anyway, so the files are totally excess as of current. (meaning, just do not care if the links point to nothing at all...)