Please help me. When i plug my n900 with nitdroid all loaded up into the pc it cant install the android driver. So this means i cant see whats on the sd card nor put stuff onit. Direct link for correct driver please, windows 7 ultimate x64. Cheers
i used the auto installer, and i just realized that it said it is downloading Nitdroid 0.0.8. i thought the auto installer installs 0.0.7?
The auto-installer installs the latest version. Usually.
Sadly, the auto-installer, NitDroid, and the wiki are not developed on the same schedule. There's a lot of info in the wiki and they seem to have a hard time getting to all of it.
At first I was a little ticked, then I decided I'd rather dj_steve and e-yes and that other guy whose handle I can't remember spend their brain cycles working on NitDroid instead of working on the website.
Since upgrading to PR.1.3, when I try to use the auto-installer it just hangs on "formatting mmcblk1p2 ext3". I've let it doing that for around half an hour, tried reformatting the card and doing it again, but still nothing?
Anyone else had this problem?
Edit: Sorted it. I had to manually repartition my SD card, the auto-install then works fine.
I'm curious as to what would happen if I tried to use the autoinstaller on the N800? I'm trying to do the N800 instructions from the wiki, and I'm having troubles with my linux seeing my N800 correctly (Getting "error claiming usb interface: Device or resource busy" and I guess it's not uncommon, but I've tried all the suggested fixes and it's still not working.) so I'm wondering....how bad could it be? lol
Since upgrading to PR.1.3, when I try to use the auto-installer it just hangs on "formatting mmcblk1p2 ext3". I've let it doing that for around half an hour, tried reformatting the card and doing it again, but still nothing?
Anyone else had this problem?
Edit: Sorted it. I had to manually repartition my SD card, the auto-install then works fine.
Does anyone know if NITdroid is going to switch to the u-boot method instead of the flash wearing kernel reflash whenever a OS change is required?
Of course I'm hoping for that only after the release of the pending 0.0.9
It looks the N900 is going the u-boot way overall (PR1.3, Meego in genera), the multiboot solution was just a quick way to get the requirements fulfilled but now in PR1.3, there should be build-in support to do things in a better, more standard way.
It is recommended that you disable the 'extra-devel' in maemo, as the installer from that repo has errors. For more info visit this thread.
hi guys , i have been following the steps given below but when i type the 3rd command , this is the situation .....
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ $ sudo gainroot
Root shell enabled
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/home/user # umount /dev/mmcblk1p1
/home/user # sfdisk -uM /dev/mmcblk1 << EOF
> ,<6100>,C
> ,,L
> ,,
> ,,
> EOF
Checking that no-one is using this disk right now ...
OK
Disk /dev/mmcblk1: 243328 cylinders, 4 heads, 16 sectors/track
Old situation:
Warning: The partition table looks like it was made
for C/H/S=*/96/22 (instead of 243328/4/16).
For this listing I'll assume that geometry.
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End MiB #blocks Id System
/dev/mmcblk1p1 4 7603 7600 7782400 b W95 FAT32
start: (c,h,s) expected (3,84,9) found (0,130,3)
end: (c,h,s) expected (1023,95,22) found (969,95,22)
/dev/mmcblk1p2 0 - 0 0 0 Empty
/dev/mmcblk1p3 0 - 0 0 0 Empty
/dev/mmcblk1p4 0 - 0 0 0 Empty
trailing junk after number
sfdisk: bad input
help needed , i have tried the auto-installer but its getting stuck at
FORMATTING /dev/mmcblk1p2 .....
help needed .....
Is it possible to boot Maemo again once Nitdroid is installed? Like what happens after every reboot, is there just an option of which one you want to boot up?
Is it possible to boot Maemo again once Nitdroid is installed? Like what happens after every reboot, is there just an option of which one you want to boot up?
Power on the device with the keyboard open. You should see a menu,
hi guys , i have been following the steps given below but when i type the 3rd command , this is the situation .....
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ $ sudo gainroot
Root shell enabled
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/home/user # umount /dev/mmcblk1p1
/home/user # sfdisk -uM /dev/mmcblk1 << EOF
> ,<6100>,C
> ,,L
> ,,
> ,,
> EOF
Checking that no-one is using this disk right now ...
OK
Disk /dev/mmcblk1: 243328 cylinders, 4 heads, 16 sectors/track
Old situation:
Warning: The partition table looks like it was made
for C/H/S=*/96/22 (instead of 243328/4/16).
For this listing I'll assume that geometry.
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End MiB #blocks Id System
/dev/mmcblk1p1 4 7603 7600 7782400 b W95 FAT32
start: (c,h,s) expected (3,84,9) found (0,130,3)
end: (c,h,s) expected (1023,95,22) found (969,95,22)
/dev/mmcblk1p2 0 - 0 0 0 Empty
/dev/mmcblk1p3 0 - 0 0 0 Empty
/dev/mmcblk1p4 0 - 0 0 0 Empty
trailing junk after number
sfdisk: bad input
help needed , i have tried the auto-installer but its getting stuck at
FORMATTING /dev/mmcblk1p2 .....
help needed .....