I’m an experienced journalist, having reported for newspapers, magazines, and online publications. I was a Senior Editor at Lifehacker and Senior Staff Writer at Wirecutter before joining the iFixit team, with a stint freelancing in-between. I’ve written for Fortune, Popular Science, Fast Company, Mediapost, ITworld. Men’s Journal, and Buffalo Spree magazine, among other publications. You can read some of my favorite work I’ve done on my personal site.
I’d completed a handful of iFixit guides before joining the staff here, for myself and for friends and relatives. Some are lost to my personal account that had to get wiped in favor of this staff account, but some I have reclaimed here.
My proudest fix-it moments:
- Rescuing the lowly HP Stream 11 by figuring out which Linux distribution would work with its cheap/weird drivers.
- Rebuilding a 1988 Schwinn World Sport from the frame up: built the wheels, re-packed the hubs, ran new cables, learned a whole lot.
- Helped my co-founder at CoworkBuffalo build a user access system to open our electro-mechanical door for members: Twilio->Heroku->IFTTT->Python server->Wemo port.
- Replaced the battery in a Big Jambox while at a brewery.
Fixed! Don’t know why that link went bad, but here’s what I was pointing at: https://guide.neverware.com/install-and-...
Glad that you’re 95% working, Dan! The audio issue is interesting - I might have suffered that myself. I’ll take a look around to see if there are any driver solutions.
Yep! You’re all set. Thank you for the verbose feedback - it’s helped me add more detail and steps to the guide that were sorely needed. It’s far too easy to assume things are obvious when you’ve done them before. Glad it’s running for you!
Hi Dan! Seeing that you got “chronos@localhost”, that’s good! You just go on to step 9 next, and enter the command at the linked website:
cd; curl -LO https://mrchromebox.tech/firmware-util.s... && sudo bash firmware-util.sh
I realize it may not be clear that seeing “chronos@localhost” is a successful result, so I will clarify that in the guide. Thank you!
Johan! I have now updated the tutorial with details on getting past the “localhost” login thing (entering “chronos” when prompted for a localhost login). My apologies for not noticing this missed step in the original tutorial.
Igor - see the new details added in Step 8. You can enter “chronos” as your login at the localhost prompt, or you can try running the script from inside ChromeOS after a dev reset (ctrl+alt+t, enter “shell,” and go from there.).
Hi Dean - see the new details I added to Step 8. I missed a step where it asks for your localhost login - you want to enter “chronos” when it asks for your localhost login, and that should let you run the script thereafter. My apologies for missing this detail.
I have updated the guide, because I think I missed a step when it comes to the Ctrl/Alt/-> prompt: you need to enter “chronos” as your login, when asked for a “localhost login.” If it asks you for a password, hit Enter without entering one. That should get you to the shell where you can then run the script. I apologize for this oversight in my original guide.
@pavlovic @funski A few ideas/thoughts:
+ Are you using the shell that you get to by pressing Ctrl+Alt+(forward arrow)? If not, are you using the Ctrl+Alt+T terminal, then typing in the “shell” command?
+ You’ve followed the previous instructions, and you’re sure that your chromebook is in a Developer Mode state? i.e. when it boots up, you hit Ctrl+D to get into the setup, not Space to start recovery?
+ Is the terminal seeming to ask you for a password?
Where are you in the process? Are you seeing any error messages? Are you using the terminal that appears when you press Ctrl+Alt+”forward arrow”, or trying to use the Ctrl+Alt+T shell?
Sayfa 1 / 2
Sonraki