Writer, Editor, and Advocate at iFixit
Ahoy-hoy! I’m a writer and editor at iFixit. I work on the text of blog posts, teardowns, video scripts, press releases, research, marketing—anything that needs to be written, or have its writing checked and fixed up. I also make the occasional video and speak to the press or at events about repair.
In my time at iFixit, I’ve written features on magnificent product deaths, rants about Amazon doing better on recycling and refurbishment, and reporting on how Apple’s Face ID “bug” crossed the line. They’ve had some real impact.
Education
I studied English at the University at Buffalo, but I spent a lot more time on the student newspaper than on Milton, Chaucer, et al. (although I did learn you should only use et al. when referring to people, not objects).
More relevant to repair, I’ve completed a one-week training course in microsoldering at Jessa Jones’ iPad Rehab. I’m not in regular practice, but the course changed the way I think about electricity, electronics, and what our devices are really like inside.
Experience
I was a traditional newspaper reporter at three different small-to-medium-city newspapers. After that, I wrote for Lifehacker, writing a half-dozen blog posts per day about software and productivity. I freelanced for a few years after that, then joined Wirecutter, where I spent dozens of hours researching product categories to recommend products for people who don’t want to spend those dozens of hours.
Favorite fixes
My proudest fix-it moments:
- Rebuilding a 1988 Schwinn World Sport from the frame up: built the wheels, re-packed the hubs, ran new cables, learned a whole lot.
- Replacing the battery and screen on a friend’s Samsung S8 Plus, which was a lot more intensive than I thought, in my earliest days at iFixit.
- Upgrading the awful dashboard system in my Ford C-Max, and learning all about the world of car hacking in doing so.
- Helping a friend who was quoted $500-$800 to replace the battery and (single) USB-C port on a 2016 MacBook for about one-fifth that price.
More about me
I ride and fix bikes whenever I can. I wrote a post for my previous site about DIY ebike conversions. Not everyone can ride a bike, but every bike should get a rider. Share the road.
I have spent an inordinate amount of time thinking about pizza and chicken wings in my life. I don’t regret it.
Where else to find me
Also?
Go Bills.
Noted! I’ve updated the guide.
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?
Sayfa 1 / 2
Sonraki