Saturday, December 25, 2010

NITDroid 0.0.9 xMasDroid

Thanks to e-yes and crevetor we have a new NITDroid version. A complete change log is still due. Check NITDroid forum for news and announcement.

The following will help you install NITDroid 0.0.9 on sdcard with the old kernel while we all wait for a new kernel to be released.

# sudo
# cd /home/user/MyDocs

# wget
# bzip2 -d NITDroid-0.0.9.tar.bz2
# mount /dev/mmcblk1p2 /and
# cd /and
# rm -rf * (this removes all the files from the old installation)
# tar xvf /home/user/MyDocs/NITDroid-0.0.9.tar

# cd /home/user/MyDocs
# wget (yes you have to reinstall the old kernel again till the new one is released)

# dpkg -i nitdroid-kernel-2.6.28-06_final1_armel.deb

If you have it on emmc then change EXT to INT from item file. I will do the emmc install after when the new kernel releases.

Warning: Your current installation will get wiped out. You can backup data folder if you want to restore later.
Update: DO NOT restore /data folder from 0.0.8 installation to 0.0.9.


contro said...

If I backup my data folder upgrade and replace my data folder will all my apps and settings be restored on .0.9 ?

xuggs said...

No they won't. You will get a Kernel panic error on boot.

devilhere said...


Please help.. below is what i did.. and there are errors as below... i am trying to install on EMMC

Devilhere(from Nitdroid forum)

/home/user/MyDocs # apt-get install bzip2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 51.5kB of archives.
After this operation, 188kB of additional disk space will be used.
Get:1 ./ bzip2 1:1.0.5-3+0m5 [51.5kB]
Fetched 51.5kB in 5s (8774B/s)
Selecting previously deselected package bzip2.
(Reading database ... 24677 files and directories currently installed.)
Unpacking bzip2 (from .../bzip2_1%3a1.0.5-3+0m5_armel.deb) ...
Setting up bzip2 (1:1.0.5-3+0m5) ...

/home/user/MyDocs # bzip2 -d NITDroid-0.0.9.tar.bz2

/home/user/MyDocs # mount /dev/mmcblk0p2 /and

/ # rm -rf*

rm: invalid option -- *
BusyBox v1.10.2 (Debian multi-call binary

Usage: rm [OPTION]... FILE...

/ # tar xvf /home/user/MyDocs/NITDroid-0.0.9.tar

tar: cannot remove old file etc: Is a directory

/ # cd /home/user/MyDocs

/home/user/MyDocs # dpkg -i nitdroid-kernel-2.6.28-06_final1_armel.deb
Selecting previously deselected package nitdroid-kernel-2.6.28-06.
(Reading database ... 24696 files and directories currently installed.)
Unpacking nitdroid-kernel-2.6.28-06 (from nitdroid-kernel-2.6.28-06_final1_armel.deb) ...
Android not found. MUST be mounted on '/and'
dpkg: error processing nitdroid-kernel-2.6.28-06_final1_armel.deb (--install):
subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:

Anonymous said...

The problem is you entered "rm -rf*" instead of "rm -rf *". Every time you get a Usage message it means you entered something wrongly. In this case you forogt the space.

@topic: Thx for the great how-to! Got it to work although now my nitdroid is really slow and horribly painful to use. Any idea why?

contro said...

Which item file do I edit I tried editing using:
leafpad multiboot.d

and doesn't let me edit it... opens up to a blank page.

Anonymous said...

I am a noob. please forgive my dumb question. I have never once tried to install ANY NITDROID but I just got a 2GB class 6 micro SD card for christmas.

Do I just need to follow the instructions on this page to get NITDroid to successfully run?

How will I switch back to maemo when it is installed?

there are like 6 sets of instructions and it gets very convoluted.

Anonymous said...

help my phone wont turn on it stays at a dim nokia logo and vibrates on and off when i charge this happen after this process

tar xvf /home/user/MyDocs/NITDroid-0.0.9.tar

anybody help pls

ddd said...

i can't mount mmcblk1p2.. its say no file or directory.. any help please..

mmmisiu said...

well, I have a suggestion for you ;)
Maybe consider editing post and changing "rm -rf * (this removes all the files from the old installation)" to "rm -rf /and/* (this removes all the files from the old installation)" (I know user should be in /and directory at that moment anyway, but you know the result of this command when either he forgot to "cd /and" or something else went wrong and he is in another directory, right?) maybe it's more typing, but it's safer. At least one user ( ) made that mistake.