Hi, as no one answers my previous 2 posts. I am writing now this one. I made SuzyQ cable, which works, and outputs USB interfaces, even I ran
echo “wp false” > /dev/ttyUSB0
echo “wp false atboot” > /dev/ttyUSB0
echo “ccd reset factory” > /dev/ttyUSB0
commands, but without output.
The main problem is, CCD mode is always “Locked”. I tryed so much times run “gsctool -a -o”. Also tryed with WP jumper soldered on the board (which only protect WP of SPI flash). The “gsctool -a -o” powers off the chromebook at step numer 6-8, without “Done”. It just turn off, and after entering the developer mode + VT2 console, the CCD remains locked. Looks like the process doesn’t complete. After that, the chromebook doesn’t boot with power button, I must to press Powerbutton + refresh(twice) + release powerbutton + powerbutton + refresh(twice) + release powerbutton, for boot the chromebook. Here is a lot of info missing in MrChromeBox docs.
I found a guy with the same problem:
But he solved it with different chromebook.
Can someone tell me what is wrong and what can I try?
After tryed everything, really everything!! I made somehow to open the damn CCD. I will post the steps I did, you just follow everything in MrChromeBox’s docs (as supposed to), and if someone has the same problem, hope it helps you.
Try to follow this if “gsctool -a -o" doesn’t open CCD (it stays locked). Always test for CCD state with “gsctool -a -I” before and after running “gsctool -a -o”.
The main problem is (maybe) some bugdate that broke gsctool. This one didn’t work as expected. So, I downgraded ChromeOS in my case. Maybe you can try to use dev, beta, canary versions of ChromeOS.
Here what I did:
downloaded version 129 “chromeos_16002.60.0_nissa_recovery_stable-channel_mp-v32.bin”,
downloaded it from here: https://cros.tech/device/yaviks/
ran in a GNU/Linux “sudo dd if=chromeos_16002.60.0_nissa_recovery_stable-channel_mp-v32.bin of=/dev/YOURDISKHERE bs=4M status=progress”.
booted into developer mode and did this steps:
Detailed Steps:
Enable Developer Mode:
Turn off your Chromebook.
Press and hold the Esc and Refresh keys, then press the Power button.
At the “Chrome OS is missing or damaged” screen, press Ctrl + D.
Confirm by pressing Enter.
The device will reboot and you’ll see a message about OS verification being off.
Enable USB Booting:
Once in Developer Mode, open a shell by pressing Ctrl + Alt + F2 (or Ctrl + Alt + T on some devices), then type shell and press Enter.
Log in as chronos.
Enter the command sudo crossystem dev_boot_usb=1.
Reboot your Chromebook.
Boot from USB:
At the developer mode boot screen, press Ctrl + U to boot from the USB drive.
then I just booted the restore image from USB in developer mode.
ran the damned “gsctool -a -o”. When “Press PP button now!” appears, spam the power button until “Another press will be required!” appears, then stop spamming and repeat. It won’t say “PP Done!”, it will just turn off or reboot.
Hi. After running “gsctool -a -o”, my chromebooks just powers off, without any message, no output. Then it won’t boot or reboot. Having to do the power+refresh sequency. So, after booting and entering into developer mode again, and entering VT2, I always found the CCD locked.
No. But I also tryed that method (battery removed, and just remove the battery when running gsctool -a -o only too). Also, I soldered permanent jumper for WP on board. Then removed, and soldered a switch for that (this chromebook really doesn’t like to boot with power button, if you are trying something). I was just trying all combinations.
If you disconnect the battery just before (or you could to boot with disconnected battery method) “gsctool -a -o”, this command will just power off the chromebook instantly. But still it didn’t solve my problem.
For opening CCD I didn’t need to touch the battery or WP jumper.
You only need to disconnect the battery, if it won’t boot even with the power+refresh combinations. This chromebook really doesn’t like to boot if you are doing something special.
Just asked for help, but no body could to give me some info. Maybe because my first post was too complex with too much context. Wrote another post with less context. Same result. And the third post with main problem. And same result. And I’m not trying to blame anyone, really.
Finally, after days of work, with all that stuff and quite a bit of hopelessness, but with enough faith in my skills… Now I have my YAVIKS Alderlake-N fully funcional, with Manjaro, full UEFI MrChromeBox’s rom flashed, working sound, repasted heatsink, a functional DIY SuzyQable…
The rest, is for anyone who is in the same situation that I was a few days ago, doesn’t have to go through the same thing again. Therefore, anyone looking for info for this or for a similar problem, can have the information that helped me with that problem.
Hope that helps someone.
Yes, I solved my problem.
The other posts (not mine ones), I answered because wanted to help.
It was the latest “stable” ChromeOS release, from stable channel. It was 138 or 139 version.
Downgraded to 129 (through developer mode + usb booting), and gsctool became functional. It has the same behavior however, but it just done his job, opening the damn CCD.