maemo.org - Talk - [Android] Guide to getting NITdroid to run.

maemo.org - Talk (https://talk.maemo.org/index.php)

- Android (https://talk.maemo.org/forumdisplay.php?f=54)

- - [Android] Guide to getting NITdroid to run. (https://talk.maemo.org/showthread.php?t=25736)

[Android] Guide to getting NITdroid to run.

NEWS: I've written a script that does everything!

NOTE: THIS GUIDE IS FOR THE N800.

Alright guys, I know quite a few people are having trouble getting Solca's NITdroid port to work, so here's a nice guide I decided to put together.

Also, before you start, BACKUP YOUR DATA! You need to backup the data on your tablet and your internal SD card.

PREREQUISITES:

Nokia N800 Internet Tablet
A computer running Ubuntu Linux (other distros may work)
An internet connection
An SD card (512MB or greater)

Now, assuming you have all of those, we can proceed.
For this tutorial, we'll use the example of a 2GB SD card.

Step 1: Acquire the files.
Note: Download all files into the same directory. For the purpose of this tutorial, we'll use '/home/paul/Desktop/'.

Go to guug.org/nit/nitdroid/ and download the following:

The Kernel
The Root Filesystem
The ADB Binary
The New Keypad Layout File

to your desktop.

Now, go to http://tablets-dev.nokia.com/d3.php and download 'flasher-3.0-static' to the same directory.

NEW: I've written a quick script for downloading all of the files. You'll need to go in and make it executable with:

Code:

chmod a+x

and then run:

Code:

./nitdroid_downloader.sh

Download it here.

Step 2: Create a filesystem.
First, remove your external SD card. Then, turn on the tablet and then plug the usb cable into it. Once the computer detects and registers the tablet, open a terminal and type:

Code:

dmesg

You should get something like this:

Code:

[  813.234547] scsi 5:0:0:1: Direct-Access     Nokia    N800              031 PQ: 0 ANSI: 2

[  813.255419] sd 5:0:0:0: [sdc] 3981312 512-byte hardware sectors (2038 MB)

[  813.258428] sd 5:0:0:0: [sdc] Write Protect is off

[  813.258445] sd 5:0:0:0: [sdc] Mode Sense: 0f 00 00 00

[  813.258453] sd 5:0:0:0: [sdc] Assuming drive cache: write through

[  813.267416] sd 5:0:0:0: [sdc] 3981312 512-byte hardware sectors (2038 MB)

[  813.270419] sd 5:0:0:0: [sdc] Write Protect is off

[  813.270435] sd 5:0:0:0: [sdc] Mode Sense: 0f 00 00 00

[  813.270442] sd 5:0:0:0: [sdc] Assuming drive cache: write through

[  813.270464]  sdc: sdc1

[  813.281546] sd 5:0:0:0: [sdc] Attached SCSI removable disk

[  813.281842] sd 5:0:0:0: Attached scsi generic sg2 type 0

[  813.292614] sd 5:0:0:1: [sdd] Attached SCSI removable disk

[  813.292747] sd 5:0:0:1: Attached scsi generic sg3 type 0

Look closely at the dmesg, and you'll see this:

Code:

[ 813.270464] sdc: sdc1

This is the partition of your SD card.

Before you create a filesystem, go to the terminal and check where the drive is mounted:

Code:

mount

That will display all the mounted folders and drives on your system. If you look at the bottom of the list, there should be something like:

Code:

/dev/sdc1 on /media/disk-1

That is the mountpoint of your drive.

Next, to unmount the card, run:

Code:

sudo umount /dev/sdc1

That should work in most distros.
To double check, type:

Code:

mount

Look at the bottom of the list again, and the mountpoint of the card shouldn't be there anymore.

Now, to partiton, enter the following.

Code:

sudo sfdisk -uM /dev/sdc

,1024,C

,1,L

,,

,,

Then, when it asks whether or not to proceed, simply enter:

Code:

y

It will create partitons-- 3 of them.
Your OS will likely automatically remount them, so once they are created, you'll run these commands:

Code:

sudo umount /dev/sdc1

sudo umount /dev/sdc3

sudo mkfs.ext3 /dev/sdc3

sudo mkfs.msdos /dev/sdc1

These will unmount the partitions, create a FAT32 filesystem that is 1GB, and create an ext3 filesystem that is 1GB (or so).

Step 3: Extracting the filesystem.

To actually create the filesystem, you'll do this:

Code:

sudo mount -t ext3 /dev/sdc3 /mnt

That will mount that partition on /mnt in your root directory as an ext3 filesystem. Now, run this command:

Code:

cd /mnt

And you will be magically transported to the directory you just mounted.

To extract the rootfs onto the partition, enter:

Code:

sudo tar -xjpvf /home/paul/Desktop/rootfs-nitdroid.tar.bz2

Then wait. Once it finishes, enter:

Code:

ls -a

And just check to make sure it extracted.

Next, run these commands:

Code:

cd ..

sudo umount /mnt

Those commands put you in the root directory, and then unmount your SD card from /mnt.

Step 4: Flash the kernel.
Finally, you're almost done!
Now, use this:

Code:

cd /home/paul/Desktop/

To return to your desktop directory.

To flash the kernel, use the following command:

Code:

./flasher-3.0-static -f -k zImage-nitdroid-n8x0 --enable-rd-mode -R

Execute this command, then AFTER you have run it, plug in the USB cable and hold the power and home keys to put it into flashing mode.

This flashes the NITdroid kernel and activates R&D mode, then restarts the tablet.

After it completes, unplug the USB cable and wait. You will see the Nokia logo screen with a little tablet beneath it. Next, the screen will turn black and then to the NITdroid logo. After this, it will flash black again and turn into a pulsating NITdroid logo. It will stay here for a few minutes, and then boot into Android.

EDIT: I have written my second script. This will automatically flash the kernel when run. You will need to make it executable, as with the downloader. It is now downloaded when you use the downloader script. To invoke it, run:

Code:

./nitdroid_flasher

And follow the directions.
It will be located in the 'nitdroid' directory on your Desktop.

Now, to get ADB working.

To extract it, you use:

Code:

bunzip2 adb.bz2

Then, to make it executable, use:

Code:

chmod a+x adb

Once you have, you'll need to use it by executng:

Code:

sudo ./adb command

Where command is your command of choice.

The hardware keys won't work, so to make them work, use the following commands.

Code:

sudo ./adb push Internal_keypad.kl /system/usr/keylayout

This will push a new keypad layout to your tablet, and should give a result something like this:

Code:

paul@paul-laptop:~/Desktop/android$ sudo ./adb push Internal_keypad.kl /system/usr/keylayout

* daemon not running. starting it now *

* daemon started successfully *

8 KB/s (409 bytes in 0.047s)

paul@paul-laptop:~/Desktop/android$

Shutdown your tablet by holding the power button and selecting power off, and then turn it back on. Your keypad should now work.

DISCLAIMER: I TAKE NO RESPONSIBILITY FOR THE CONSEQUENCES OF HUMAN ERROR. DOING THIS INCORRECTLY MAY CAUSE YOUR TABLET TO IMPLODE, A HOBO TO SODOMIZE YOUR DOG AND GRANDMOTHER, OR LCUK TO BURN HIS HAND MAKING BACON AGAIN.

Credit goes to:

Solca, for making NITdroid and creating the keypad layout.
Everyone else for whatever help they provided.
Nokia, for making the Internet Tablets
Anidel, for the bunzip2 command

EDIT: I am in the process of writing a few scripts to automate this process.

EDIT 2: Downloader script done! You can download it at the top of this post.

EDIT 3: Flasher script done! When you use the downloader script, it is automatically downloaded.

Re: Guide to getting NITdroid to run.

Thanks for posting the Guide, it is what I have been hoping for.

I am well placed, having a few spare SD cards and a partition running Ubuntu, so I shall give it a try shortly when I can pluck up the courage and necessary focus.

In the meantime, user contributions posted here about their experiences will help fortify my resolve and save me from the embarrassment of asking dumb questions.

I really want this to work.

Re: Guide to getting NITdroid to run.

To unzip and use the ADB, these are the commands:

Quote:

bunzip2 adb.bz2

followed by:

Quote:

chmod a+x adb

Then you can run it.

Besides, why you specified this works only for N800 ?
These are the very same steps needed for the N810, right?

Re: Guide to getting NITdroid to run.

So, is anyone working on a nice simple GUI wizard for this? Or is NITdroid not at the point yet where this high(ish) barrier to entry is a Bad Thing?

Re: Guide to getting NITdroid to run.

I was just going to ask for a completely new thread like this!

Is there also a pros and cons of NITDroid somewhere?

e.g.
Cons: no onscreen keyboard (is this true?), no Maemo access without taking drastic steps, RD mode (downsides?), no SSU

Pros: A next-gen environment, Java, more apps, etc.

Will this result in an actual first- or second-tier Android platform? Or would it be foolish to, for example, buy things from the Android market?

Thanks again.

Re: Guide to getting NITdroid to run.

Quote:

I'll make a list when I get a chance.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by Jaffa (Post 251694)

So, is anyone working on a nice simple GUI wizard for this? Or is NITdroid not at the point yet where this high(ish) barrier to entry is a Bad Thing?

There's not much point in making a wizard, because it changes so often. I'd have to say this is for more advanced users-- this isn't something you do if you don't know what you're doing. (Also, you need a computer with linux.)

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by anidel (Post 251685)

Besides, why you specified this works only for N800 ?
These are the very same steps needed for the N810, right?

I don't have an N810, so I don't know how partitioning would work on that.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by jakemaheu (Post 251791)

There's not much point in making a wizard, because it changes so often.

Surely the steps remain the same, even if the kernel etc. are changing? Then it's just a matter of wgetting the appropriate parts before unpacking them etc.

Quote:

I'd have to say this is for more advanced users-- this isn't something you do if you don't know what you're doing. (Also, you need a computer with linux.)

If NITdroid's not ready for the masses yet, I won't bother investigating the installation wizard (or hell, even a script).

The advantage of a script - even on a Linux computer - is there's less chance of error and it makes support easier as you know how people have installed things. Certainly, if a user isn't paying attention in the steps above - and they use a SCSI or SATA drive - they could end up repartitioning one of their existing disks, rather than the SD card.

Similarly, it could detect the sizes and suggest partioning schemes etc.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by Jaffa (Post 251807)

Surely the steps remain the same, even if the kernel etc. are changing? Then it's just a matter of wgetting the appropriate parts before unpacking them etc.

If NITdroid's not ready for the masses yet, I won't bother investigating the installation wizard (or hell, even a script).

The advantage of a script - even on a Linux computer - is there's less chance of error and it makes support easier as you know how people have installed things. Certainly, if a user isn't paying attention in the steps above - and they use a SCSI or SATA drive - they could end up repartitioning one of their existing disks, rather than the SD card.

Similarly, it could detect the sizes and suggest partioning schemes etc.

The steps should remain the same, but a script would be quite easy to write. The only problem, as you said, is if they use a SCSI or SATA drive. The script would have to account for that. That's actually why I added the dmesg step, because the latest drive would show up at the bottom. Good ideas, though-- I like it.

EDIT: It's not that it isn't ready for the masses-- it runs quite well (with a couple exceptions), but you need to be careful when flashing and such.

Re: Guide to getting NITdroid to run.

If you're feeling brave (or stupid) enough you can do this using a Linux virtual machine using VirtualBox (and probably the other virtualization solutions).

The only issue I had with installing was the 2nd stage loader (when the NITdroid logo pulses) didn't work at first. I'm not sure if this is where the pause (due to first load caching) is supposed to be or not but the first 2 times it sat there for 5+ minutes before I gave up. I tried again later and now it works fine, could be the sd card didn't make a good enough connection I suppose.

Anyway apart from that it seems to work fine. Apart from it's complete refusal to connect to my wi-fi. I've tried add the connection manually but it still says no. Maybe this doesn't work but the project page implies that it does. Any ideas?

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by rasmithuk (Post 251942)

Anyway apart from that it seems to work fine. Apart from it's complete refusal to connect to my wi-fi. I've tried add the connection manually but it still says no. Maybe this doesn't work but the project page implies that it does. Any ideas?

If you just added the connection, try rebooting-- usually that helps. If that doesn't work, I'd suggest getting the calibration utility.

http://stlc45xx.garage.maemo.org/

You'll need to get stlc45xx-cal and place it on the FAT partition (/sdcard) on your SD card. It should help, even if rebooting fixes it.

Re: Guide to getting NITdroid to run.

I followed this and it seemed to work. When I booted the first time it went to a blank black screen until I pulled out the battery. It booted fine after that.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by jakemaheu (Post 251617)

NEW: I've written a quick script for downloading all of the files. You'll need to go in and change:

Code:

cd /home/yourusernamegoeshere/Desktop/

to whatever your username is on your system.

Replace "yourusernamegoeshere" with "$USER" and it will automatically get the username.

And I'm probably being pedantic here but "dmesg | tail" is nicer to look at than "dmesg" (in this case) :).

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by jakemaheu (Post 252023)

Thanks for the hint. It didn't make any difference, however this morning another new wifi device refused to connect (Dell mini 9) and when I checked the wifi was on channel 13.
Since these extra channels don't exist everywhere I'm guessing by default the wifi chipset ignores them. When I changed to channel 1 both devices work fine.

Re: Guide to getting NITdroid to run.

Has anyone been able to flash NITdriod on the WiMAX tablet? Mine's hardware revision is 1007, and flasher said it flashed the image correctly. When I start the tablet, it shows the Nokia logo, with the picture of a spanner inside the tablet, and does not proceed further. I partitioned my 2G internal card to have 500M vfat, unpartitioned, 500M ext3 all formatted and the android rootfs files copied over.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by sarathmenon (Post 252594)

From what I've read, there's something different about the WiMax N810 that causes a lot of things to fail on it. I don't know however, as I've only got an N800.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by sarathmenon (Post 252594)

The NITdroid kernel have support for the N810W but if it doesn't work for you it would be a good idea to flash the debugging kernel and see what it does. Other thing is being sure to remove the external SD card.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by solca (Post 252930)

Thanks, I'll give that a try. Can you please point me to the location of this kernel? I only see instructions for rd-mode on guug.org. I had removed the external card to avoid the kernel attempting to boot off it.

Re: Guide to getting NITdroid to run.

Dude, are you serious?

http://guug.org/nit/nitdroid/

Quote:

For testing and debugging:
NITdroid debugging kernel for N770 (2.6.28-rc8-omap 2008Dec10)
NITdroid debugging kernel for N8x0 (2.6.28-rc9-omap 2008Dec20)

Its right there... keep reading...

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by Thesandlord (Post 252936)

Ugh, I can't believe I missed that ;) Thanks for pointing out.

Re: Guide to getting NITdroid to run.

Its still the same results. I see the Nokia logo, but nothing happens after that. I suspect whether the bootloader is getting invoked, because I can see hardware and nic details when the factory kernel boots in the rd-mode. While loading android, nothing shows up. I am sure that I got all the instructions correct, this is the output of fdisk -l for this partition.

Code:

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1       16001      512024    b  W95 FAT32

/dev/sdb2           16002       38402      716832   83  Linux    

/dev/sdb3           38403       61440      737216   83  Linux

I did a fresh download of the rootfs tarball and verified with rsync that the files are correctly copied over.

Re: Guide to getting NITdroid to run.

As a followup, I've noticed other weirdness too. A shutdown does not work from the power button, the device goes through a process of closing all apps, and the display blacks out, with the backlight on. $( reboot ) on the shell as root also gives the same results. The firmware was flashed back to the latest Nokia supplied one, RX-48_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin, overwriting the filesystem completely (-f with flasher).

I've also observed random problems with the OS after flashing it to the default. GPS stays on, even though there is no system tray notification saying so (I remember that this was not the case when I first started up the device). The browser randomly crashes, and the hardware keyboard refuses to load sometimes. I haven't restored anything from backup and the system is running the OS in the pristine state (MyDocs and ~user weren't populated with any of my stuff).

Is there any difference in the core OS between the WiMAX edition and the normal one? I've tried googling around, but apart from vague posts, I haven't seen anything on this topic. Either my searching skills on this forum are lousy, or I am the first person here to see these type of problems. Oh well, scream PEBKAC if you want to :-)

I know that this doesn't strictly touch the topic for which this thread was started. Should I move this whole thing to a different thread?

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by sarathmenon (Post 253278)

Again, I don't have an N810W, but starting a new thread for those who do should help it get more attention.

Re: Guide to getting NITdroid to run.

Thanks for the tutorial it's really easy. I've gotten past all the steps up to the fourth one. I try to run the nitroid_flasher. I follow all the steps and it says:

Code:

Flashing sequence activated and RD mode being enabled.

flasher v0.9.0 (Jan 19 2007)



Suitable USB device not found, waiting 

<i turn on the tablet pressing the menu button>

USB device found found at bus 001, device address 004

Error claiming USB interface: Operation not permitted

Restarting...

I don't know why it's giving me this problem. Can someone help?

Re: Guide to getting NITdroid to run.

Did you run the ./flasher command prefixed by sudo? You need to be root.

Re: Guide to getting NITdroid to run.

hmm that's weird. i ran it with sudo and it gave me the same thing but now it works. Thanks.

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by jakemaheu (Post 253307)

Again, I don't have an N810W, but starting a new thread for those who do should help it get more attention.

I got to the root of the problem. The first partition on the 2G SD was formatted as FAT32, but maemo wasn't detecting it. When I went back to the factory default OS, it was going crazy trying to detect an SD card. Strangely, the external miniSD was untouched, but the system gave up on mounting it after it could not talk to the internal SD card. I think some of the default apps need space on the card to write their cache and other data, and was spending more CPU cycles. /proc/loadavg was constantly above 4 which can explain why the battery drained faster. There was a mount in uninterrupted sleep (D on ps wwaux), maybe shutdown froze trying to kill it.

I cleaned up the internal card and reformatted as ext3, and was good to go. I wish I had got some good indication that the OS was spending CPU cycles because of it.

Re: Guide to getting NITdroid to run.

Just say 'maybe' I've done this wrong and want to start from the beginning again, how can I get my N810 back into its 'normal' form?

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by munkimatt (Post 256122)

Just say 'maybe' I've done this wrong and want to start from the beginning again, how can I get my N810 back into its 'normal' form?

It would depend on what you've done. If you just flashed the kernel, you can download the proper image for your tablet and run

Code:

sudo ./flasher-3.0-static -f -F yourimage.bin --flash-only=kernel --disable-rd-mode -R

That will us the flasher to flash only the kernel, leaving your apps intact.

Re: Guide to getting NITdroid to run.

Yes I keep trying to do that but it keeps comign up command not found, very confusing

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by munkimatt (Post 256159)

Yes I keep trying to do that but it keeps comign up command not found, very confusing

In that case, maybe I'm doing this wrong-- try:

Code:

sudo ./flasher-3.0-static -f -k yourimage.bin --disable-rd-mode -R

Re: Guide to getting NITdroid to run.

Just a quick one Jake, I'm now using your full script, when the line comes up saying 'read action1' how long should that take?

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by munkimatt (Post 256182)

Just a quick one Jake, I'm now using your full script, when the line comes up saying 'read action1' how long should that take?

well, it should ask you to type something, and that becomes a variable, in this case it's "$action1". it uses this for unmounting and stuff. once you enter it though, it should ask another question or two.

Re: Guide to getting NITdroid to run.

Sorry to keep bugging you Jake, but I'm getting nowhere. I'm copying in what I'm getting in terminal to see if you have any idea as to what's the issue.

Quote:

matt@matt-desktop:~/Desktop/nitdroid$ #! /bin/bash
matt@matt-desktop:~/Desktop/nitdroid$ #this is a script to completely install NITdroid on an internet tablet
matt@matt-desktop:~/Desktop/nitdroid$ echo Welcome to the NITdroid downloader/installer script.
Welcome to the NITdroid downloader/installer script.
matt@matt-desktop:~/Desktop/nitdroid$ echo This program will do all of the following:
This program will do all of the following:
matt@matt-desktop:~/Desktop/nitdroid$ echo *Download the nescessary files.
*Download the nescessary files.
matt@matt-desktop:~/Desktop/nitdroid$ echo *Create the proper filesystems and partitions.
*Create the proper filesystems and partitions.
matt@matt-desktop:~/Desktop/nitdroid$ echo *Install the rootfs and flash the proper kernel.
*Install the rootfs and flash the proper kernel.
matt@matt-desktop:~/Desktop/nitdroid$ echo Before beginning, please remove the external SD card and plug the USB cable into the computer.
Before beginning, please remove the external SD card and plug the USB cable into the computer.
matt@matt-desktop:~/Desktop/nitdroid$ echo Downloads will begin in 30 seconds...Downloads will begin in 30 seconds...
matt@matt-desktop:~/Desktop/nitdroid$ echo NOTE: This program should NOT be run as root.
NOTE: This program should NOT be run as root.
matt@matt-desktop:~/Desktop/nitdroid$ echo It has specific parts that need to run as root.
It has specific parts that need to run as root.
matt@matt-desktop:~/Desktop/nitdroid$ sleep 30
matt@matt-desktop:~/Desktop/nitdroid$ #beginning of downloader script
matt@matt-desktop:~/Desktop/nitdroid$ cd /home/$USER/Desktop/
matt@matt-desktop:~/Desktop$ mkdir nitdroid
mkdir: cannot create directory `nitdroid': File exists
matt@matt-desktop:~/Desktop$ mkdir adb
mkdir: cannot create directory `adb': File exists
matt@matt-desktop:~/Desktop$ cd nitdroid
matt@matt-desktop:~/Desktop/nitdroid$ echo Beginning downloads...
Beginning downloads...
matt@matt-desktop:~/Desktop/nitdroid$ wget http://www.jakemaheu.com/flasher-3.0-static
--2009-01-12 20:39:18-- http://www.jakemaheu.com/flasher-3.0-static
Resolving www.jakemaheu.com... 67.18.18.74
Connecting to www.jakemaheu.com|67.18.18.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 492816 (481K) [text/plain]
Saving to: `flasher-3.0-static.4'

100%[======================================>] 492,816 48.0K/s in 9.0s

2009-01-12 20:39:28 (53.7 KB/s) - `flasher-3.0-static.4' saved [492816/492816]

matt@matt-desktop:~/Desktop/nitdroid$ wget http://guug.org/nit/nitdroid/rootfs-nitdroid.tar.bz2
--2009-01-12 20:39:28-- http://guug.org/nit/nitdroid/rootfs-nitdroid.tar.bz2
Resolving guug.org... 200.9.255.30
Connecting to guug.org|200.9.255.30|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 34106260 (33M) [application/octet-stream]
Saving to: `rootfs-nitdroid.tar.bz2.5'

100%[======================================>] 34,106,260 43.3K/s in 11m 55s

2009-01-12 20:51:24 (46.6 KB/s) - `rootfs-nitdroid.tar.bz2.5' saved [34106260/34106260]

matt@matt-desktop:~/Desktop/nitdroid$ wget http://guug.org/nit/nitdroid/zImage-nitdroid-n8x0
--2009-01-12 20:51:24-- http://guug.org/nit/nitdroid/zImage-nitdroid-n8x0
Resolving guug.org... 200.9.255.30
Connecting to guug.org|200.9.255.30|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1752836 (1.7M) [application/octet-stream]
Saving to: `zImage-nitdroid-n8x0.5'

100%[======================================>] 1,752,836 36.7K/s in 52s

2009-01-12 20:52:16 (32.9 KB/s) - `zImage-nitdroid-n8x0.5' saved [1752836/1752836]

matt@matt-desktop:~/Desktop/nitdroid$ cd ../adb
matt@matt-desktop:~/Desktop/adb$ wget http://guug.org/nit/nitdroid/adb.bz2
--2009-01-12 20:52:16-- http://guug.org/nit/nitdroid/adb.bz2
Resolving guug.org... 200.9.255.30
Connecting to guug.org|200.9.255.30|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 61068 (60K) [application/octet-stream]
Saving to: `adb.bz2.3'

100%[======================================>] 61,068 59.3K/s in 1.0s

2009-01-12 20:52:18 (59.3 KB/s) - `adb.bz2.3' saved [61068/61068]

matt@matt-desktop:~/Desktop/adb$ wget http://guug.org/nit/nitdroid/Internal_keypad.kl
--2009-01-12 20:52:18-- http://guug.org/nit/nitdroid/Internal_keypad.kl
Resolving guug.org... 200.9.255.30
Connecting to guug.org|200.9.255.30|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 409 [application/octet-stream]
Saving to: `Internal_keypad.kl.4'

100%[======================================>] 409 --.-K/s in 0s

2009-01-12 20:52:18 (33.2 MB/s) - `Internal_keypad.kl.4' saved [409/409]

matt@matt-desktop:~/Desktop/adb$ bunzip2 adb.bz2
bunzip2: Output file adb already exists.
matt@matt-desktop:~/Desktop/adb$ chmod a+x adb
matt@matt-desktop:~/Desktop/adb$ cd ../nitdroid
matt@matt-desktop:~/Desktop/nitdroid$ #beginning of partitioning
matt@matt-desktop:~/Desktop/nitdroid$ echo Files acquired.
Files acquired.
matt@matt-desktop:~/Desktop/nitdroid$ echo Creating filesystems...
Creating filesystems...
matt@matt-desktop:~/Desktop/nitdroid$ echo [************************************************** ************]
[************************************************** ************]
matt@matt-desktop:~/Desktop/nitdroid$ mount|grep -e /dev/sd
/dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro)
/dev/sdf1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1 000,utf8,umask=077,flush)
matt@matt-desktop:~/Desktop/nitdroid$ echo What is the last entry on that list?
What is the last entry on that list?
matt@matt-desktop:~/Desktop/nitdroid$ echo It should look like '/dev/sd*1'.
It should look like /dev/sd*1.
matt@matt-desktop:~/Desktop/nitdroid$ echo Enter the answer in lowercase, with the number included.
Enter the answer in lowercase, with the number included.
matt@matt-desktop:~/Desktop/nitdroid$ echo [************************************************** ************]
[************************************************** ************]
matt@matt-desktop:~/Desktop/nitdroid$ read action1
$action1
matt@matt-desktop:~/Desktop/nitdroid$ .

I've typed in $action1 but it just goes back to the directory. I've also tried action1 (without the $ sign) and /dev/sdf1 (as it's the last one in the list, but every time it just goes back to the directory.

Re: Guide to getting NITdroid to run.

Wow, I've never seen a script echo every line to the console like that. Weird!

Re: Guide to getting NITdroid to run.

Hey, download the script to your desktop, then run in the terminal:

cd /home/$USER/Desktop/
chmod +x nitdroid_complete.sh
./nitdroid_complete.sh

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by BrentDC (Post 256976)

Hey, download the script to your desktop, then run in the terminal:

cd /home/$USER/Desktop/
chmod +x nitdroid_complete.sh
./nitdroid_complete.sh

That's what I'm doing mate. Gonna give it one more shot and then I think I'm going to admit defeat :o

Re: Guide to getting NITdroid to run.

Quote:

Originally Posted by munkimatt (Post 256977)

That's what I'm doing mate. Gonna give it one more shot and then I think I'm going to admit defeat :o

Then ditto to what qole said :o

Re: Guide to getting NITdroid to run.

Well it's got further this time, I'm now getting the NITdroid logo up but it's just frozen on the screen...not gonna give up...lol