MARKARTH boot loops after using gsctool

Support General Device Support
1

System Details

  • Device: MARKARTH (Acer Chromebook Plus 514)
  • OS: fedora
  • Firmware Type: RW_LEGACY
  • Firmware Version: (unable to provide but latest as of post date)
  • Internal storage type: eMMC

Summary of the Issue

Hello. My system has RW_legacy. Today I tried to switch to UEFI. I bridged the J35 jumper. Then I tried the command sudo gsctool -a -o the laptop immediately powered off. When it turns on, it goes to the chromeos logo, but then powers off. This continues in a boot loop as long as the system has power.

Steps to Reproduce

  1. Have RW_legacy

  2. Bridge J35

  3. Sudo gsctool -a -o

  4. Boot loops

This could entirely be my fault, perhaps I misread something?

2

Managed to get into recovery, fixed.

3

what was the issue?

4

I was trying to put UEFI on it. So I bridged the J35 with solder. And ran the GSC command, which caused it to immediately boot loop. I didn’t realize that I needed a debug USB, which is what I think caused this. I somehow managed to get to the recovery screen which I then reinstalled chromeos on to.

5

you don’t need a SuzyQ cable to open the CCD via gsctool.

6

I bridged the J35 and I ran gsctool -a -o

Then the gsctool allowunverifiedro command

Disabled RO verification

I got to step 1 of “using closed-case debugging (CCD) / Using a SuzyQable

Do i need to do step 2? I figured it was suzyqable only based off of the wording?

After these steps it still shows WP on

7

Ok what??? I installed fedora, and now the wp is off, even though it wasn’t before I installed the distro

8

Successfully installed the UEFI