How to install FULL Java 8 on Chrome OS without Crouton (or others) - Chromebooks

There are people who are still looking for a method to install Java on Chrome OS.. and if i told you that Oracle's Java is perfectly installable on Chrome OS without Crouton/Linux/etc? Yeah, that's true.
We are going to treat Chrome OS as a Linux's distribution, in this guide. Because? Well, Chrome OS can run linux binaries..
Let's go:
First of all, press CTRL + ALT + T, this will open the "crosh" (the terminal emulator of Chrome OS), write on crosh "shell" and press Enter, after that write "sudo su" and press Enter.
You will be asked for a password, it usually ranges from build to build, try one of these passwords:
password
facepunch
chronos
chrome
(Even if the shell isn't writing, don't worry, it's writing).
Yeah! Now you have the supreme power.. in the Chrome's shell.
Now write “mount -o remount,exec,rw /” and press Enter, now we mounted the file system as writable.
Do "cd /home" and press Enter.
If you are running Chrome OS on a 32 bit hardware, write "wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=106238 -O jre.tar.gz" and press Enter; if you're on a 64 bit hardware, write "wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=106240 -O jre.tar.gz" and press Enter. This command will download the Oracle's Java Runtime.
After that, do "tar zxvf jre.tar.gz", this will extract the Java Archive.
Do "mv jre1.8* /bin" and press Enter, after that do "cd /bin", this will take you to the "folder of the executables".
Finally write "ln -s /bin/jre1.8.0_45/bin/java /bin/java" (WARNING, the number "45" should be replaced with the number written on the website of Java, if you can find such as "Java Version 8 Update 49", instead of 45 you will need to put 49).
Let's try Java. Do "java -version", if the shell will write the version of Java then the game is done. Welcome to Java's world.
UNFORTUNATELY, on some builds, the Java's graphical programs cannot be seen and will freeze your system (If this will happen, reboot and don't use Java's graphical programs. P.S. you can still use Java's command line programs). In other builds, Java work perfectly without any problem.
That was really easy. With this method, you can execute other linux binaries and Chromebooks will finally be the perfect alternative to traditional laptops.
- Simone Cervino, Soxasora.
ITALIAN VERSION:
Ciao a tutti, con questa guida potrete installare Java sul vostro Chromebook facilmente e senza usare Crouton o altri simili metodi. Questa sara' una completa installazione di Java, nessuna emulazione. Inoltre impareremo ad usare Chrome OS come una normale distribuzione Linux.
Non tutti sanno che questo sistema operativo, in realtà, è una distribuzione Linux. Infatti, Chrome OS, è capace di avviare programmi Linux, inoltre la shell ha anche i basilari programmi che non mancano mai nelle shell delle distribuzioni Linux (come wget, tar ecc).
Seguendo le istruzioni di un mio amico sono riuscito ad installare Java su Chrome OS, vi riporto il procedimento di seguito:
Per prima cosa, fai CTRL+ALT+T e nella finestra di Chrome che ti si apre, scrivi “shell” e premi Invio e poi fai “sudo su” e premi Invio.
Ti verrà chiesta una password, questa di solito varia da build a build, prova una di queste password:
password
chronos
facepunch
chrome
(Anche se non la scrive, non preoccuparti, in realtà la sta scrivendo).
Bene, ora hai il potere supremo nel terminale di Chrome.
Prima di iniziare scrivi “mount -o remount,exec,rw /” e premi Invio, questo ci permetterà di montare il file system come scrivibile.
Ora che sei il capo supremo sul tuo dispositivo, fai “cd /home” e premi Invio, questo ti porterà alla cartella home.
Se ti trovi in un sistema a 32 bit, scrivi “wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=106238 -O jre.tar.gz” e premi Invio, se invece ti trovi in un sistema a 64 bit, scrivi “wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=106240 -O jre.tar.gz” e premi Invio, questo comando ti scaricherà un archivio tar.gz che conterrà tutti i file di Java.
Successivamente, scrivi “tar zxvf jre.tar.gz” e premi Invio, questo comando ci scompatterà l’archivio contenente i file di Java.
Fai “mv jre1.8* /bin” seguito da invio e successivamente “cd /bin” e premi Invio, questo ti porterà alla cartella home, quella dove si trovano i binari importanti di Chrome, i programmi.
Per finire scrivi “ln -s /bin/jre1.8.0_45/bin/java /bin/java” (ATTENZIONE, il numero “45” si deve sostituire col numero scritto sul sito web di Java, se trovi ad esempio “Java Version 8 Update 49″, al posto di 45 dovrai mettere 49)
Ora prova a scrivere “java -version”, se ti scrive la versione di Java, allora il gioco é fatto e finalmente potrai usare Java sul tuo dispositivo Chrome OS.
Purtroppo funzionerà solo tramite linea di comando e su alcune build, i programmi java con interfaccia, non si vedono, anzi, blocca tutto. (Nel caso vi si bloccasse tutto, riavviate).
— Sulle build Chrome OS di Hexxeh, i programmi Java con interfaccia, potrebbero vedersi —
E’ stato veramente facile, vero? Questo perché Chrome OS é solo una distribuzione Linux con un gestore finestre creato da Google, diverso dal solito. Dobbiamo iniziare a vedere Chrome OS come una distribuzione Linux e non come un “nuovo” sistema operativo, questo ci permette di pensare più in grande. Ma cosa ci ha fermati fino ad oggi? Beh, Google ha pensato di aggiungere la funzione di “noexec” alle cartelle di sistema, tranne alla cartella bin (altrimenti i binari al suo interno non funzionerebbero) per evitare che virus e altri programmi, modificassero il sistema. Qui abbiamo sfruttato la cartella bin dove si può eseguire qualsiasi cosa perché non ha la funzione di “noexec“.
- Simone Cervino, Soxasora.

---

I get cannot remount /Dev/dm-0 readwrite is write protected

---

muzab a said:
I get cannot remount /Dev/dm-0 readwrite is write protected
Click to expand...
Click to collapse
Are you in the superuser shell?

---

yep , the text is in red
Intially did shell then sudo su

---

muzab a said:
yep , the text is in red
Intially did shell then sudo su
Click to expand...
Click to collapse
Strange.. With Chromium OS i don't have this problem. Your chromebook is unlocked?

---

Developer mode on and on chromeos with beta build

---

does anyone do a terminal task directly on chrome ?

---

When I do "mv jre1.8* /bin" I get some errors saying I don't have space left on device. Is there any solution for this?

---

Can this work on Toshiba Chromebook running the latest version?

---

The Commands You Said Are Not Valid

---

When I do java -version i get permission denied. even with chmod 777 on all the java binary. yes i'm sudo su. everything else worked

---

Same error
I got the same error. It said that i could only be done as root, so i typed:
sudo su
And got cannot remount. Help us?

---

Just got a Samsung Chromebook and the "shell" command seems to no longer be valid, making the steps above not work.

---

tresf2 said:
Just got a Samsung Chromebook and the "shell" command seems to no longer be valid, making the steps above not work.
Click to expand...
Click to collapse
Sounds like you may not be in developer mode..

---

fattire said:
Sounds like you may not be in developer mode..
Click to expand...
Click to collapse
Correct. Thanks. Had previously followed this tutorial in VM. I was surprised to eventually find out it needed Developer mode to work on physical hardware. Thanks kindly for the reply.

---

@tresf2 now days i'ts much better to just install chromebrew it literally takes no effort. It's as simple as
Code:
crew install jdk8

---

tdct12 said:
@tresf2 now days i'ts much better to just install chromebrew it literally takes no effort. It's as simple as
Code:
crew install jdk8
Click to expand...
Click to collapse
Great to know. This specific use-case is for enterprise roll-out, so I'll have to put the OS on pause until the app can be rewritten in the proper language.
Much obliged and best regards,

---

mount-or remount, exec, rw / does not work says mount-or not found????? do i put a space or what do i do please help!!!!!!

---

"No such file or directory" when calling "java -version"
The procedure worked on Chromium OS (Neverware CloudReady). I moved the jdk dir under "/usr/bin" (instead of "/bin") and correctly symlinked target to "/bin/java":
lrwxrwxrwx 1 root root 31 Oct 20 22:19 /bin/java -> /usr/java/jdk1.8.0_151/bin/java
But when I call "java -version" the following is returned:
bash: /bin/java: No such file or directory
Same for "/usr/java/jdk1.8.0_151/bin/java -version":
bash: /usr/java/jdk1.8.0_151/bin/java: No such file or directory
But the file (and the link) actually exists, with execute permission.
Any hint?
Thanks.

---

ctliv said:
The procedure worked on Chromium OS (Neverware CloudReady). I moved the jdk dir under "/usr/bin" (instead of "/bin") and correctly symlinked target to "/bin/java":
lrwxrwxrwx 1 root root 31 Oct 20 22:19 /bin/java -> /usr/java/jdk1.8.0_151/bin/java
But when I call "java -version" the following is returned:
bash: /bin/java: No such file or directory
Same for "/usr/java/jdk1.8.0_151/bin/java -version":
bash: /usr/java/jdk1.8.0_151/bin/java: No such file or directory
But the file (and the link) actually exists, with execute permission.
Any hint?
Thanks.
Click to expand...
Click to collapse
Symlink traversal in most locations on the stateful partition was blocked in this commit last May. There are exceptions for /usr/local and a few subdirs under /var.
I noticed this a while back but hadn't been impacted by it.
To check it out, I created a symlink (fileA) in /bin pointing to an executable file in /usr/local/bin (fileB).
I then attempted to execute /bin/fileA in the shell, and received the "No such file or directory" message.
As a test, I then entered the following:
Code:
mount -t securityfs securityfs /sys/kernel/security
printf "/bin" > /sys/kernel/security/chromiumos/symlink_policy/allow
I then retried executing fileA and it now worked. (the symlink to FileB was now being followed).
The above is a bit of a hassle, as the change won't persist through reboots etc.
Generally, keeping things in /usr/local/*, where symlinks are still followed, seems like it might be the best option. That's what chromebrew does.
Somewhat related side note: If you do keep binaries etc under /usr/local, in the default configuration you'll need to become root with "sudo su -", rather than "sudo su", for /usr/local to be in the $PATH env.