1-10 of 24 Answers
On the Chromebook keyboard press the Power button and the Reload button at the same time. Some flip style Chromebooks have the power button located on the side of the Chromebook. This forces the Chromebook to turn off and then back on.
Sorry, there was a problem. Please try again later.There might be a refresh key at the top of the keyboard (a curly arrow circle). Hold it down at the same time as the Power button. This may work. It works on my Acer chromebook, which is a piece of garbage paper weight, essentially.
Sorry, there was a problem. Please try again later.I have found pushing the off button and ESC simultaneously restarts it.
Sorry, there was a problem. Please try again later.So far the only way that I found that works on this is completely let your Chromebook died by charging your phone or tablet or something once it dies that reboots when you plug it in to charge it. And then it goes back to normal before it froze
Sorry, there was a problem. Please try again later.Someone was smart enough share to hold down power button & refresh, the curly Arrow upper row, left side of keys. Great!
Sorry, there was a problem. Please try again later.Holding down the alt and power off button at the same time helped me.
Sorry, there was a problem. Please try again later.This has happened to me a couple times, I have not been able to find another solution other then to let it die and then once it dies plug it in and use it as normal.
Sorry, there was a problem. Please try again later.i have a Chromebook and if you just hold down the power button for like at least a minute or a little less than a minute then it will shut off for me. If this doesn't work then just let the power/battery drain. It might take a while but it works.
Sorry, there was a problem. Please try again later.Power button and alt worked for me good luck
Sorry, there was a problem. Please try again later.if nothing works, let your chromebook die and plug it in. give it a few seconds and open, it should work. it does for me.
Sorry, there was a problem. Please try again later.