Active Topics

 


Reply
Thread Tools
Posts: 36 | Thanked: 2 times | Joined on Jan 2008
#1
I have an N800 with OS2008, got it just last week. I was logged in as root via ssh from my PC and edited the sudoers file (using visudo). I then opened X-terminal as user and was able to log in as root using 'sudo su' and entering root's password. So all looked good at this point.

I then logged out and powered off the N800, then powered on to reboot it. It started to boot, screen lit up with 'NOKIA', but when the blue line reached the far right that's where it stopped. After some time the screen dims and then goes dark, turns bright again if I tap the screen. It's connected to the power supply so the battery won't run down.

What can be done to restore my original sudoers file? I saved a copy of the original sudoers on the N800 as well as on my PC.

I don't yet know much about how to use the sudoers file. Below is a copy of the one that's in there now, and probably caused the failed boot.
Code:
Defaults env_check+="HOME DISPLAY"
Defaults env_keep+="HOME DISPLAY"
Defaults env_reset
Defaults:user timestamp_timeout=-1, runaspw, passwd_tries=3
root ALL = (ALL) ALL
user ALL = (ALL) ALL
 
EIPI's Avatar
Posts: 794 | Thanked: 784 times | Joined on Sep 2007 @ /Canada/Ontario/GTA
#2
Did you change the file access permissions of the /etc/sudoers file, by chance?

It should be:

-r--r----- 1 root root
 
Posts: 36 | Thanked: 2 times | Joined on Jan 2008
#3
Originally Posted by EIPI View Post
Did you change the file access permissions of the /etc/sudoers file, by chance?
I did not look at the permissions of the /etc/sudoers file after using visudo, so permissions are as visudo left them.

In order to power down, I had to remove and re-insert the battery. Then I tried to reflash OS2008, but the N800 would not go into the firmware upload mode. I phoned Nokia tech support, they told me to send it in for warranty repair.
 
Posts: 234 | Thanked: 40 times | Joined on Nov 2007 @ Cincinnati, Ohio USA
#4
I don't 'know' but, I read there is a battery that keeps time, and perhaps other status info. Take the battery out for two hours and leave unplugged. Then you should be able to get to the update mode at least.
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#5
Originally Posted by LinuxStation View Post
Then I tried to reflash OS2008, but the N800 would not go into the firmware upload mode.
That sounds odd, to be honest. I can understand to some degree why your device might be hanging during the boot sequence - most likely because a script is either stuck at a password prompt or sudo is failing completely - but for the device to not go into flasher mode doesn't sound like it's connected with your sudo modifications. Could just be a coincidence.... have you tried holding the "Home" key while powering on?

Originally Posted by LinuxStation View Post
I phoned Nokia tech support, they told me to send it in for warranty repair.
I think you're very lucky to get a repair under warranty, particularly if your inability to flash is due to your sudo changes!
 
Posts: 111 | Thanked: 31 times | Joined on May 2007
#6
Hmmm, so that could explain why i had to reflash my n800 4 time since i had it (yesterday)... It may well be the sudoers modification (done via visudo, in a way that used to work on n800). I was thinking one third party program was doing it, without finding wich one....

Note that reflashing the tablet always worked here.
 
Posts: 36 | Thanked: 2 times | Joined on Jan 2008
#7
Originally Posted by Milhouse View Post
Could just be a coincidence.... have you tried holding the "Home" key while powering on?
Well yes, holding the Home key (Swap Key) while powering on is the only way I know to begin a firmware upload. After having the battery out for some hours I installed the battery and tried to enter flash mode one more time, but no joy. I usually don't break things this quickly, had it less than a week. Anyway, it's no big deal because it's still under warranty.

Last edited by LinuxStation; 2008-01-22 at 07:05.
 
Posts: 20 | Thanked: 3 times | Joined on Jan 2008
#8
Hmm, my OS2008 sudoers file is MUCH longer than yours. I haven't touched it.

In case it helps:

Code:
### Automatically added by update-sudoers start ###
Defaults env_check+="HOME DISPLAY"
Defaults env_keep+="HOME DISPLAY"
Defaults env_reset
user ALL = NOPASSWD: /usr/sbin/gainroot
user ALL = NOPASSWD: /usr/sbin/mmc-mount /dev/mmcblk0 /media/mmc1
user ALL = NOPASSWD: /usr/sbin/mmc-mount /dev/mmcblk0p1 /media/mmc1
user ALL = NOPASSWD: /bin/umount /media/mmc1,/bin/umount -l /media/mmc1
user ALL = NOPASSWD: /usr/sbin/osso-usb-mass-storage-enable.sh, /usr/sbin/osso-usb-mass-storage-disable.sh
user ALL = NOPASSWD: /sbin/mkdosfs /dev/mmcblk0*, /usr/sbin/mmc-rename /dev/mmcblk0*
user ALL = NOPASSWD: /etc/init.d/af-base-apps stop , /etc/osso-af-init/gconf-daemon.sh stop
user ALL = NOPASSWD: /etc/init.d/af-base-apps start , /etc/osso-af-init/gconf-daemon.sh start
user ALL = NOPASSWD: /etc/init.d/osso-systemui restart
user ALL = NOPASSWD: /usr/sbin/gconf-clean.sh
user ALL = NOPASSWD: /usr/sbin/chroot /mnt/initfs /usr/bin/retutime *
user ALL = NOPASSWD: /sbin/insmod /mnt/initfs/lib/modules/current/g_file_storage.ko stall=0 file=/dev/mmcblk0
user ALL = NOPASSWD: /sbin/insmod /mnt/initfs/lib/modules/current/g_ether.ko
user ALL = NOPASSWD: /sbin/rmmod g_file_storage
user ALL = NOPASSWD: /sbin/rmmod g_ether
user ALL = NOPASSWD: /usr/sbin/osso-backup-restore-locale
user ALL = (install) NOPASSWD: /usr/bin/app-installer-tool
### Automatically added by update-sudoers end ###
### Automatically added by update-sudoers start ###
user ALL = NOPASSWD: /usr/libexec/apt-worker
user ALL = NOPASSWD: /usr/bin/hildon-application-manager-util restore-catalogues
user ALL = NOPASSWD: /usr/bin/hildon-application-manager-util restore-catalogues2
### Automatically added by update-sudoers end ###
### Automatically added by update-sudoers start ###
user ALL = NOPASSWD: /usr/bin/hildon-input-method-configurator.bin
### Automatically added by update-sudoers end ###
### Automatically added by update-sudoers start ###
user ALL = NOPASSWD: /etc/init.d/ke-recv start
user ALL = NOPASSWD: /etc/init.d/ke-recv stop
user ALL = NOPASSWD: /etc/init.d/alarmd start
user ALL = NOPASSWD: /etc/init.d/alarmd stop
user ALL = NOPASSWD: /etc/init.d/osso-hss start
user ALL = NOPASSWD: /etc/init.d/osso-hss stop
user ALL = NOPASSWD: /usr/bin/osso-product-info
user ALL = NOPASSWD: /bin/mv -f /tmp/.opi.tmp.tmp /tmp/.opi.tmp
### Automatically added by update-sudoers end ###
### Automatically added by update-sudoers start ###
user ALL = NOPASSWD: /bin/umount /media/mmc2
user ALL = NOPASSWD: /usr/sbin/osso-prepare-partition.sh *
user ALL = NOPASSWD: /sbin/mkdosfs *
user ALL = NOPASSWD: /etc/init.d/ke-recv stop
user ALL = NOPASSWD: /etc/init.d/hildon-desktop stop
user ALL = NOPASSWD: /etc/init.d/mediaplayer-daemon stop
user ALL = NOPASSWD: /etc/init.d/metalayer-crawler0 stop
### Automatically added by update-sudoers end ###
user ALL = NOPASSWD: /etc/osso-backup/restore.d/always/bluez-restore.sh
user ALL = NOPASSWD: /usr/bin/region
user ALL = NOPASSWD: /bin/mv /etc/rhapsody-install/rhapsody.desktop /usr/share/applications/hildon/
 
Posts: 234 | Thanked: 40 times | Joined on Nov 2007 @ Cincinnati, Ohio USA
#9
Originally Posted by LinuxStation View Post
Well yes, holding the Home key (Swap Key) while powering on is the only way I know to begin a firmware upload. After having the battery out for some hours I installed the battery and tried to enter flash mode one more time, but no joy. I usually don't break things this quickly, had it less than a week. Anyway, it's no big deal because it's still under warranty.
Not to be as condescending.... But (I think) I noticed that it only goes to firmware mode when actually connected to the computer (I don't think the flash program needs to be running).

I've had startup problems myself, so I won't try it to confirm for you.

Edit; guess I was wrong and removed rude comment.

Last edited by TheGogmagog; 2008-01-22 at 19:42.
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#10
Originally Posted by TheGogmagog View Post
Not to be as condecending as the 'hold home key' suggestion....
I wasn't being intentionally condescending - sigh.

Flashing usually works whether you hold the Home button or not, but it's one of those things which people can overlook so is worth asking. If you hold the Home button it will go to flash mode whether it's connected to a computer or not (or will wait longer for a computer to "appear") - if you don't hold the button it will only go to flash mode if it's connected to a computer. Or something like that - holding the button can make a crucial difference. The OP never mentioned it, so I asked. Maybe I shouldn't have bothered...
 
Reply


 
Forum Jump


All times are GMT. The time now is 14:27.