Bricked Chromebook

[Aryan Jaipaul]

A little bit of a warning to those on the dev channel, although it may be too late since chrome auto-updates. But your Chromebook may be getting bricked as I see no possible way of stopping the update without losing local data, so right now if your Chromebook is on, backup everything on that tablet, your save files and everything.because it seems that upon restarting the machine it would go into a boot loop that rebooting will not solve. I am about to power wash it to see if that helps, I will post the update.

[Mike Frysinger]

technically, i don't think it's a boot loop.  the login screen likes to loop.

it seems you can workaround the issue by:

- typing your password really fast and logging in

- try turning off the wifi, logging in, and then turning the wifi back on

-mike

On Fri, Jul 20, 2018 at 3:08 PM Aryan Jaipaul <aryan.s...@gmail.com> wrote:

A little bit of a warning to those on the dev channel, although it may be too late since chrome auto-updates. But your Chromebook may be getting bricked as I see no possible way of stopping the update without losing local data, so right now if your Chromebook is on, backup everything on that tablet, your save files and everything.because it seems that upon restarting the machine it would go into a boot loop that rebooting will not solve. I am about to power wash it to see if that helps, I will post the update.

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

[Kingdon Barrett]

Would it help to walk away from the network?  That seems easier than racing with the boot processes

---
You received this message because you are subscribed to the Google Groups "Chromium OS Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[Ihor Dvoretskyi]

Which model of Chromebook is it? 

[Aryan Jaipaul]

Ooh sorry to you all, It's not stuck on the login screen, but indeed a boot loop. I get the usual Warning for setting a root password, then the boot animation starts, then never stops, I never get to the login screen, to clarify, the machine itself is not frozen, the curser moves around. As for the model, it's a Acer Chromebook 11 C740 series. The model number I get when I turn it on is PAINE D25-B2F-J6A-A6I. 

[Aryan Jaipaul]

Ooooookieeeeeee, so I just wiped it, it boots all right now, switched it back to developer mode now my apps are syncing... Going to miss my save files, I had a 100% complete state on Hatsune Miku Project Diva extend. Time to do a speedrun, you all remember to back up everything ok?

[Aryan Jaipaul]

Aite nvm, maybe just stay off the dev channel for a bit, I opened chrome then it froze for a bit and started the boot loop again, guess I'm using my phone instead for a while, until Google gets their s**t together.

[Nom De Plume]

I don't necessarily think it is a channel thing, but rather a
device/channel combination. I have been on Canary for a couple of
years and I regularly have errors that don't run across all devices.
There are different hardware components and different kernels along
with the differences in the channels.

[Mike Frysinger]

it's the dev channel. sometimes it had bugs (some of which are bad). that's the whole point of the dev channel.

if the occasional bug is too much of a problem for your usage, than don't use the dev channel.

as a reminder, please keep it civil in these groups.

-mike

[Aryan Jaipaul]

Aah, I'll just switch to a more stable channel upon my second power wash then, I'll try beta but I'm not sticking to stable because I like the new UI, I'm still keeping the machine itself in dev mode.

[DennisLfromGA]

I'm getting caught in the loop on the sign-in screen on lulu with the version 69.0.3494.0 / 10888.0.0-dev
I'm not experiencing this issue on eve with the same version.

I tried toggling off wifi but I wasn't quick enough to log in, it kept looping.

I'm in dev mode so I just re-prioritized the kernel partitions and booted back to version 69.0.3473.0 / 10820.0.0

I'll wait for another version >3473 before I try it again unless another method/workaround is found.

~Denny