Crouton: Chroot asking for password that I did NOT set [Solved]

[adhoc92]

I just bought a new Chromebook. I downloaded Chrouton and typed "sudo sh ~/Downloads/crouton -t xfce" into Crosh > Shell.

Then I received the following message:

" We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

1) Respect the privacy of others.
2) Think before you type.
3) With great power comes great responsibility.

Password: "

I've tried every password I can think of with no success. Any ideas?

[DennisLfromGA]

By default, there is no password for chronos or root so if one is set, you'll have to remove it.

Before installing a new chroot or anything else, it might be best if you saved everything you need in ~/Downloads, etc. and do a 'powerwash'.
You can access 'powerwash' from Advanced settings or press Ctrl+Alt+Shift+R from the sign-in screen.

[adhoc92]

I have powerwashed several times. After each wash, I have enabled developer settings. Crosh > shell still asks me for a password after any Sudo command.

Edit: My chromebook is an Acer Cb3-111.

[tcagle]

You should read the sudo man page or google sudo and read what it does.
Sounds like normal behavior to me.

On Sun, Aug 30, 2015 at 2:40 PM, adhoc92 [email protected] wrote:

I have powerwashed several times. After each wash, I have enabled
developer settings. Crosh > shell still asks me for a password after any
Sudo command.

—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/2050#issuecomment-136177657.

[adhoc92]

I just finished reading the manual. I don't see anything that will help me. I have found a few ways to change the password, but I need Sudo access to do so.

[tcagle]

If memory serves (big if) there is a default password for the sudo
(chronos) login and it is documented on the crouton website.

On Sun, Aug 30, 2015 at 4:21 PM, adhoc92 [email protected] wrote:

I just finished reading the manual. I don't see anything that will help
me. I have found a few ways to change the password, but I need Sudo access
to do so.

—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/2050#issuecomment-136195763.

[DennisLfromGA]

I just bought a new Chromebook.

If that's the case, I don't see how you could have anything other than the 'stock' Chrome OS.
But, if a powerwash doesn't do it, then you may need to use the 'Chromebook Recovery Utility'.

[adhoc92]

Dennis, I have done that as well :/ Same result.

[adhoc92]

SOLVED.

I fixed it by NOT enabling debug features on the setup screen.

So if any future adventurers with an Acer CB3-111 Chromebook have the same problem, that should (hopefully) work.

[DennisLfromGA]

I fixed it by NOT enabling debug features on the setup screen.

Well I'd say _that_ was an important omission.

See *_Debugging Features_

Click Proceed. The system reboots and displays a dialog with password prompts
[OPTIONAL] Set the new root password.
Note: If you leave the root password blank, the password defaults to test0000.

[adhoc92]

Yeah, that's my my bad. I thought it was a normal part of the process that went without saying. That was obviously NOT the case. Thanks for sticking around and helping me out guys!

[tedm]

k, so now we know you're not crazy ;)

[billunique]

Thanks, this is just what I am finding.

[DennisLfromGA]

There seems to be a glitch in setting up the Debugging features in CrOS that leads to this issue. I don't know if it's a WAI (works as intended) thing or not but it can throw a kink in things if you're not aware of it.
This thread talks about it and has a workaround for it too - https://github.com/dnschneid/crouton/issues/2927#issuecomment-264746586

Hope this helps,
-DennisL

[scottdavisxx]

I just ran into the same problem. It turns out. it is not asking for your password to download. It is asking you to create a password. If you type in a password of your choice and then confirm that same password. It will then ask for another password to be created. I used the same password.

I followed this guide. https://www.lifewire.com/install-linux-on-chromebook-4125253

This is how they describe this process.
"You may now be prompted to provide and verify both a password and an encryption passphrase at this juncture, the reason being that you chose to encrypt your Ubuntu installation via the "-e" parameter in the previous step. While this flag is not required, it is highly recommended. Choose a secure password and passphrase that you will remember and enter them accordingly, if applicable."

[ollie05w]

Guys I found a password for it
What I did for both debugging and without debugging for when it says think before you type
The password I guessed is
Passwd= localhost lower case
This was lucky I tried so many others it's only this what I found to work

[ollie05w]

Localhost is the password

[aleksclark]

for what it's worth, I discovered the following: the root password you set when enabling debugging tools will work over SSH but will NOT work from the local shell. if you ssh in as root, you can then change all the passwords to be what you want.

[johanwitters]

Thanks @aleksclark That's the solution for me

[cierracarmon18]

The ssh root@localhost keeps refusing the connection I'm not really computer savvy but installing the software did take so long of a time I don't wish to resit through it I just need to reset the password and this is frustrating

[jschnarr]

It's actually simpler than @aleksclark and I previously said, and SSH doesn't work reliably.

Press ctl+alt+forward (by forward I mean the F2 equivalent, not the right arrow). It will pop up the proper developer console which allows you to logon as root with the password you set during setup. It also has instructions for setting the chronos password properly using chromeos-setdevpasswd.

[ghost]

Thank you @jschnarr, your solution worked perfectly.

[IgorGanapolsky]

@johanwitters

Localhost is the password

No it is not

[mosesdel]

what is the login and if possible how do you reset it

[ghost]

I cannot remember exaclty but it prompted me sometime during the install, if I remember correctly. Now when I boot up, if I go CTRL-ALT-T, I get to the crosh prompt, then I type in shell and hit Enter and then I type in sudo enter-chroot and it prompts me for the password I set during install. At that point I am logged in as the username@localhost that I created during install.

To your question, where do you type in chromeos-setdevpaswd? If you go CTRL-ALT-T and type in shell and hit Enter, you will be at a chronos@localhost / $ prompt. Then you sudo su to root and type your command, like so:
chronos@localhost / $ sudo su
Password:
localhost / # chromeos-setdevpasswd
Password:
Verifying - Password:
localhost / #

[KevinVandy]

Took me a while to find all the relevant information on this page, but I was able to figure it out. I had the same problem OP had. I made a root password while putting it into developer mode, but that password did not work in the crosh prompt (Ctrl + Alt + t). Here is exactly what worked for my asus chromebook flip c302 chromeos ver 63.

1. Press Ctrl-Alt-forward
2. Login as the user "root" and the password that you made while putting it into developer mode.
3. You should be in as localhost now. Then from here you can set a new password that works in your crosh shell. So, in the shell that we just logged into, type the command
   chromeos-setdevpasswd
   then you can set a password, which you will probably want to be the same password that you just used if you want to keep it simple.
4. After you have set the password from that prompt you can get sudo privileges with that password.

[tomford007]

KevinVandy, THANK YOUUUUUUUUU!!!!!

[jonmorales89]

@KevinVandy , thank you! Worked for me on an Acer C910.

[laurentschneider]

if you set a root password for debugging, use it with

ssh root@localhost

from shell (CTRL-ALT-T + shell)

[primeroseis]

I had the same issue installing crouton on a samsung chromebook, and solved it skipping to check the debugger features as user adhoc92 pointed out..... I am still waiting for the install to conclude .....but would like to know which might be a good forum about how to use the xfce desktop all the links I follow point to unity ... Thanks for any advice

[ghost]

I uninstalled it all, returned my pixel book to standard and started using
Google cloud shell, I'm connected to the cloud just about 24/7 anyway

On Sat, Aug 11, 2018, 4:43 PM primeroseis [e-mail] wrote:

I had the same issue installing crouton on a samsung chromebook, and
solved it skipping to check the debugger features as user adhoc92 pointed
out..... I am still waiting for the install to conclude .....but would like
to know which might be a good forum about how to use the xfce desktop all
the links I follow point to unity ... Thanks for any advice

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/2050#issuecomment-412300395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEIbNuFo6heXzBWX3fEHAP_aR0muT4piks5uP0H2gaJpZM4F0m-H
.

[amesy]

if you set a root password for debugging, use it with

ssh root@localhost

from shell (CTRL-ALT-T + shell)

Thank you, your method successfully solved my problem!

[ghost]

THANKS TO KEVIN

[ieee488]

Thank you Kevin !!!!

I had enabled debugging features ( didn't mean to do it) but I did not set a password so I had the default password test0000 mentioned by DennisLfromGA.

Dell 11 3120 Chromebook.

[vibraniumdroid]

guys guys guys!

Easy solution CTRL + ALT +2
login with username: root
and password: test0000

run the set password command and leave it empty

Chrome OS with debugging features enabled :)

[Ouranophobia]

if you set a root password for debugging, use it with

ssh root@localhost

from shell (CTRL-ALT-T + shell)

This worked for me thank you!

[clintryan413211]

I'm on a Samsung chrome book and can't get shit done on finding out the password

[DennisLfromGA]

@clintryan413211,

1. Follow the instructions two comments up or
2. powerwash your device and do NOT select Debugging Features. Once you're signed-in you can enable any of the Debugging features you like by running one or more of the following scripts:

/usr/libexec/debugd/helpers/dev_features_chrome_remote_debugging
/usr/libexec/debugd/helpers/dev_features_password
/usr/libexec/debugd/helpers/dev_features_rootfs_verification
/usr/libexec/debugd/helpers/dev_features_ssh
/usr/libexec/debugd/helpers/dev_features_usb_boot

Hope this helps,
-DennisLfromGA

[GCStokum]

was having the same issue, and found that while there Hasn't been a password set, the default is NOT so you should Set one with a quick:
sudo su
passwd

(I've not tried this with setting the su to but has sorted out all my other pw issues)

hope that helps some of you

[schester44]

I was never given a password prompt, but using "localhost" as the password worked for me 👍

[anthello147]

I am running Chromium OS (Version 48, Developer Build) by Neverware on VirtualBox 6.1. As I do not have a Google Account, I login as Guest, and I did not know how to run commands as superuser because I did not know my UNIX password (as I was logged in as Guest):

chronos@localhost / $ sudo su

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
Sorry, try again.
Password: 
Sorry, try again.
Password:
Sorry, try again.
sudo: 3 incorrect password attempts.
chronos@localhost / $

I had tried multiple different passwords, such as localhost, facepunch, test0000. None of these worked. Eventually I stumbled across a website (https://neverware.zendesk.com/hc/en-us/community/posts/206835307-Root-Administrator-password), which said that the default password for user chronos was chrome. I tried this out, and it worked:

chronos@localhost / $ sudo su

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
localhost / #

I hope this helps.

EDIT: According to the website where I found the password chrome, the password may not work in newer builds of Neverware's version of Chromium OS. I have not tested this out, as newer versions don't run in my VirtualBox installation, so I can't be sure.

[sppidy]

better solution which worked for me

sudo -i (logins as root)
passwd root (Change password of root)
passwd {ur username} (Change Ur Password)
exit

now ,
su - root (Enter The Password u Set)

I just bought a new Chromebook. I downloaded Chrouton and typed "sudo sh ~/Downloads/crouton -t xfce" into Crosh > Shell.

Then I received the following message:

" We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

1. Respect the privacy of others.
2. Think before you type.
3. With great power comes great responsibility.

Password: "

I've tried every password I can think of with no success. Any ideas?

[mph-code]

Took me a while to find all the relevant information on this page, but I was able to figure it out. I had the same problem OP had. I made a root password while putting it into developer mode, but that password did not work in the crosh prompt (Ctrl + Alt + t). Here is exactly what worked for my asus chromebook flip c302 chromeos ver 63.

1. Press Ctrl-Alt-forward
2. Login as the user "root" and the password that you made while putting it into developer mode.
3. You should be in as localhost now. Then from here you can set a new password that works in your crosh shell. So, in the shell that we just logged into, type the command
   chromeos-setdevpasswd
   then you can set a password, which you will probably want to be the same password that you just used if you want to keep it simple.
4. After you have set the password from that prompt you can get sudo privileges with that password.

I spent ages looking for this information last year and am so glad I finally was able to quickly take care of this impediment!! Not sure how I didn't find this when I was trying to figure this out a year ago. Thank you for laying out this information. Super easy fix.

[DennisLfromGA]

@mph-code,

The method/procedure you outlined above does work but just an fyi:

• The password you set when you enabled the Debugging Features was for username: 'root'
• The password you set with the script chromeos-setdevpasswd is for username: 'chronos'.

Hope this helps,
-DennisLfromGA