Can't Boot to Linux on Dual-Boot Chromebook after Battery Completely Discharges

[ajlenze]

I've used chrx to turn Acer C720 Chromebooks into dual-boot Linux/ChromeOS machines. Everything seems to work great at first - ctrl-L to boot to Linux, ctrl-D to boot to ChromeOS. Since these are laptops, I sometimes run them from their batteries, and I've found that if the battery gets completely discharged, when I plug in and press ctrl-L to boot to Linux, the computer beeps at me but won't boot into Linux. It still boots fine into ChromeOS, either by default or when I press ctrl-D.

Is this a known issue? Is there any way to fix this or get around it?

Thanks,

A.J.

[tuxevil]

i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help

[ajlenze]

Here's a temporary fix for this problem:

1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell.
2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem.

To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu.

Good luck!

A.J.

On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.***> wrote:

i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.***>

[tuxevil]

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

thanks a lot, the temporary fix solved the issue, another day i will try the permanent fix!!! THAnKS!!!!

[ajlenze]

Were you sh*tting your pants when it wouldn't boot into Linux? After all the work it took to make it Linux bootable, I sure was!

Glad it's fixed now.

A.J.

On Mon, Mar 21, 2022 at 6:20 PM Sebastian Real @.***> wrote:

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m4339194927313594172> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

thanks a lot, the temporary fix solved the issue, another day i will try the permanent fix!!! THAnKS!!!!

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074517817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7L3T6ZMJ2SY66PZARLVBD75JANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.***>

[tuxevil]

Indeed! Well I had everything backed Up but It would be a pain in the ass to setup everything from zero again

El lun., 21 mar. 2022 6:24 p. m., ajlenze @.***> escribió:

Were you sh*tting your pants when it wouldn't boot into Linux? After all the work it took to make it Linux bootable, I sure was!

Glad it's fixed now.

A.J.

On Mon, Mar 21, 2022 at 6:20 PM Sebastian Real @.***> wrote:

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m4339194927313594172> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.*> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563>, or unsubscribe

https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q < https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.*>

thanks a lot, the temporary fix solved the issue, another day i will try the permanent fix!!! THAnKS!!!!

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074517817, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AVFOZ7L3T6ZMJ2SY66PZARLVBD75JANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074520199, or unsubscribe https://github.com/notifications/unsubscribe-auth/AECLRQUXHFW3IRB4GJCVS3TVBEAMDANCNFSM5B7E5T7Q . You are receiving this because you commented.Message ID: @.***>

[ajlenze]

Can you please explain this strange term "backed up"? :-)

On Mon, Mar 21, 2022 at 6:29 PM Sebastian Real @.***> wrote:

Indeed! Well I had everything backed Up but It would be a pain in the ass to setup everything from zero again

El lun., 21 mar. 2022 6:24 p. m., ajlenze @.***> escribió:

Were you sh*tting your pants when it wouldn't boot into Linux? After all the work it took to make it Linux bootable, I sure was!

Glad it's fixed now.

A.J.

On Mon, Mar 21, 2022 at 6:20 PM Sebastian Real @.***> wrote:

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m4339194927313594172> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.*> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) <https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q

<

https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.*>

thanks a lot, the temporary fix solved the issue, another day i will try the permanent fix!!! THAnKS!!!!

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074517817, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AVFOZ7L3T6ZMJ2SY66PZARLVBD75JANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074520199, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AECLRQUXHFW3IRB4GJCVS3TVBEAMDANCNFSM5B7E5T7Q

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074523185, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7IWDX6GLLM3PI7PA43VBEA6RANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.***>

[tuxevil]

I meant i have nextcloud doing backup of the files all the time, so i wasnt afraid of loosing any data

El lun., 21 mar. 2022 6:33 p. m., ajlenze @.***> escribió:

Can you please explain this strange term "backed up"? :-)

On Mon, Mar 21, 2022 at 6:29 PM Sebastian Real @.***> wrote:

Indeed! Well I had everything backed Up but It would be a pain in the ass to setup everything from zero again

El lun., 21 mar. 2022 6:24 p. m., ajlenze @.***> escribió:

Were you sh*tting your pants when it wouldn't boot into Linux? After all the work it took to make it Linux bootable, I sure was!

Glad it's fixed now.

A.J.

On Mon, Mar 21, 2022 at 6:20 PM Sebastian Real @.***> wrote:

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m4339194927313594172> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.*> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) <https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q

<

https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.*>

thanks a lot, the temporary fix solved the issue, another day i will try the permanent fix!!! THAnKS!!!!

— Reply to this email directly, view it on GitHub <https://github.com/reynhout/chrx/issues/132#issuecomment-1074517817 , or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AVFOZ7L3T6ZMJ2SY66PZARLVBD75JANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074520199, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AECLRQUXHFW3IRB4GJCVS3TVBEAMDANCNFSM5B7E5T7Q

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074523185, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AVFOZ7IWDX6GLLM3PI7PA43VBEA6RANCNFSM5B7E5T7Q

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1074525439, or unsubscribe https://github.com/notifications/unsubscribe-auth/AECLRQT3C2WL5YNPJEVHRADVBEBM7ANCNFSM5B7E5T7Q . You are receiving this because you commented.Message ID: @.***>

[tuxevil]

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_boot_legacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

For fixing permanently, is just removing the read-only screw or i need also the "servo" device? https://www.collabora.com/news-and-blog/blog/2017/03/08/quick-hack-removing-the-chromebook-write-protect-screw/ https://www.ifixit.com/Guide/Remove+the+Write+Protect+Screw/86362

this problem is happening often and i would like to fix it pemanently

[ajlenze]

I don't know anything about a "servo". But before you take any more advice from me, you should know that I've only installed Linux (in my case Xubuntu) on a few Acer C720s and one C720P; is that the same model you're using? As part of installing Linux, I modified the BIOS using the Mr. ChromeBox script I mentioned in my previous message. I used this same Mr ChromeBox script to permanently fix your problem (using menu option 3), but if you didn't use the Mr. ChromeBox script as part of the process of installing Linux, your permanent solution may be different.

If you do use the Mr. ChromeBox script to fix the problem permanently, you have to first remove the write-protect screw, before running the script. I didn't have to remove the screw during the initial Linux installation - I think that's because I didn't strictly change the BIOS; instead, I actually installed a BIOS extension. However, I may be mistaken about this.

Hope this helps,

A.J.

On Thursday, April 14, 2022, Sebastian Real @.***> wrote:

Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_bootlegacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/ firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m-7678709752897225515_> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) https://github.com/reynhout/chrx/issues/132#issuecomment-1074477563>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

For fixing permanently, is just removing the read-only screw or i need also the "servo" device? https://www.collabora.com/news-and-blog/blog/2017/03/08/ quick-hack-removing-the-chromebook-write-protect-screw/ https://www.ifixit.com/Guide/Remove+the+Write+Protect+Screw/86362

this problem is happening often and i would like to fix it pemanently

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1099458034, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7MPVNGJKANV2OLXTTDVFBJ3LANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.***>

[tuxevil]

I don't know anything about a "servo". But before you take any more advice from me, you should know that I've only installed Linux (in my case Xubuntu) on a few Acer C720s and one C720P; is that the same model you're using? As part of installing Linux, I modified the BIOS using the Mr. ChromeBox script I mentioned in my previous message. I used this same Mr ChromeBox script to permanently fix your problem (using menu option 3), but if you didn't use the Mr. ChromeBox script as part of the process of installing Linux, your permanent solution may be different. If you do use the Mr. ChromeBox script to fix the problem permanently, you have to first remove the write-protect screw, before running the script. I didn't have to remove the screw during the initial Linux installation - I think that's because I didn't strictly change the BIOS; instead, I actually installed a BIOS extension. However, I may be mistaken about this. Hope this helps, A.J. On Thursday, April 14, 2022, Sebastian Real @.> wrote: … Here's a temporary fix for this problem: 1. Boot into ChromeOS and bring up a Linux prompt. On my machine, to do this I first hit ctrl-alt-t to bring up a terminal window, then, at the "crosh>" prompt, type shell. 2. At this Linux prompt, type "sudo crossystem dev_bootlegacy=1". This should fix the problem. To permanently fix the problem, you have to modify the BIOS, which involves removing the write-protect screw, then using some script. I used the command "cd; curl -LO https://mrchromebox.tech/ firmware-util.sh && sudo bash firmware-util.sh", then using option 3 in the menu. Good luck! A.J. … <#m-7678709752897225515_> On Mon, Mar 21, 2022 at 5:19 PM Sebastian Real @.> wrote: i just have the same problem, my chromebook was working perfectly with kubuntu, but after my battery was completely dead, first develppermode was disable, and after enabling it, when i press ctrl + l at the OS verification screen, it beeps and dont go into linux anymore, please help — Reply to this email directly, view it on GitHub <#132 (comment) <#132 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q https://github.com/notifications/unsubscribe-auth/AVFOZ7NDJF6YVZWO3KHFG2TVBDYXLANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.> For fixing permanently, is just removing the read-only screw or i need also the "servo" device? https://www.collabora.com/news-and-blog/blog/2017/03/08/ quick-hack-removing-the-chromebook-write-protect-screw/ https://www.ifixit.com/Guide/Remove+the+Write+Protect+Screw/86362 this problem is happening often and i would like to fix it pemanently — Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7MPVNGJKANV2OLXTTDVFBJ3LANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

I have an ASUS C423 and a HP Chromebook 14 G5 I used the MR. Chromebox script too, but I choosed Kubuntu, and option 3 is disabled i guess becouse of WP screw, I will try to remove it on the HP and give it a try to fix permanently.

Thanks

[tuxevil]

Well, ASUS C423 dont have WP screw https://www.reddit.com/r/chromeos/comments/kirnyn/cant_find_writeprotect_screw/

I will look for another way to fix it

[ajlenze]

Looks like you've reached the limit of my expertise, such as it is. At least I showed you the temporary fix.

On Thursday, April 14, 2022, Sebastian Real @.***> wrote:

Well, ASUS C423 dont have WP screw https://www.reddit.com/r/chromeos/comments/kirnyn/cant_ find_writeprotect_screw/

I will look for another way to fix it

— Reply to this email directly, view it on GitHub https://github.com/reynhout/chrx/issues/132#issuecomment-1099547698, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7KHREEG6HLNWZXXIELVFBVY7ANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.***>

[tuxevil]

Looks like you've reached the limit of my expertise, such as it is. At least I showed you the temporary fix. … On Thursday, April 14, 2022, Sebastian Real @.> wrote: Well, ASUS C423 dont have WP screw https://www.reddit.com/r/chromeos/comments/kirnyn/cant_ find_writeprotect_screw/ I will look for another way to fix it — Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVFOZ7KHREEG6HLNWZXXIELVFBVY7ANCNFSM5B7E5T7Q . You are receiving this because you authored the thread.Message ID: @.>

indeed, thank you so much, you saved me