A Slight Clarification May Improve This Guide
Closed this issue · 6 comments
First, thank you so much for this guide. I've got 15.10 on a C670 and almost on my new i3 Toshiba Chromebook 2.
But a hiccup I ran into with the Toshiba was that the guide correctly illustrates that there is no heatshield to be removed, and the write protect screw simply needs to be removed. But the guide doesn't say that after removing the screw, there is still that conductive ring around the screwhole that needs to removed, just like in the other steps for the non i3 version. My eyesight is not what it used to be, and I missed this ring without carefully looking for it. If you don't remove it, the circuit is still closed, and the "flashrom --wp-disable" will fail.
Other than that, the guide is absolutely perfect, and I thank you for it.
Did you take a picture of the sticker by chance?
On Thu, Dec 3, 2015 at 5:37 AM, ddade notifications@github.com wrote:
First, thank you so much for this guide. I've got 15.10 on a C670 and
almost on my new i3 Toshiba Chromebook 2.But a hiccup I ran into with the Toshiba was that the guide correctly
illustrates that there is no heatshield to be removed, and the write
protect screw simply needs to be removed. But the guide doesn't say
that after removing the screw, there is still that conductive ring around
the screwhole that needs to removed, just like in the other steps for the
non i3 version. My eyesight is not what it used to be, and I missed this
ring without carefully looking for it. If you don't remove it, the circuit
is still closed, and the "flashrom --wp-disable" will fail.Other than that, the guide is absolutely perfect, and I thank you for it.
—
Reply to this email directly or view it on GitHub
#4.
Also as you have personal experience with the issue, feel free to modify the section yourself with the steps you took. Would definitely improve the guide.
You know, I didn't have the presence of mind to do that. But it sounded a
lot like the one for the non-i3 model... Just an adhesive ring of a
metallic-like substance that easily came off in one piece, using the tip of
an X-Acto knife.
On Thu, Dec 3, 2015 at 7:57 PM, Brenden Yule notifications@github.com
wrote:
Did you take a picture of the sticker by chance?
On Thu, Dec 3, 2015 at 5:37 AM, ddade notifications@github.com wrote:
First, thank you so much for this guide. I've got 15.10 on a C670 and
almost on my new i3 Toshiba Chromebook 2.But a hiccup I ran into with the Toshiba was that the guide correctly
illustrates that there is no heatshield to be removed, and the write
protect screw simply needs to be removed. But the guide doesn't say
that after removing the screw, there is still that conductive ring around
the screwhole that needs to removed, just like in the other steps for the
non i3 version. My eyesight is not what it used to be, and I missed this
ring without carefully looking for it. If you don't remove it, the
circuit
is still closed, and the "flashrom --wp-disable" will fail.Other than that, the guide is absolutely perfect, and I thank you for it.
—
Reply to this email directly or view it on GitHub
#4.—
Reply to this email directly or view it on GitHub
#4 (comment)
.
@ddade thanks for adding to the guide to clarify the process!
No problem, I really appreciate this guide... I now have 15.10 running on
my cb3-3350, thanks to you.
On Dec 9, 2015 3:31 PM, "Brenden Yule" notifications@github.com wrote:
@ddade https://github.com/ddade thanks for adding to the guide to
clarify the process!—
Reply to this email directly or view it on GitHub
#4 (comment)
.
No problem, glad it helped you, hopefully it will help more people as well.
On Thu, Dec 10, 2015 at 7:05 AM, ddade notifications@github.com wrote:
No problem, I really appreciate this guide... I now have 15.10 running on
my cb3-3350, thanks to you.
On Dec 9, 2015 3:31 PM, "Brenden Yule" notifications@github.com wrote:@ddade https://github.com/ddade thanks for adding to the guide to
clarify the process!—
Reply to this email directly or view it on GitHub
<
#4 (comment).
—
Reply to this email directly or view it on GitHub
#4 (comment)
.