hexdump0815
commented
2 years ago to answer this topic myself in case someone else runs into the same problem: looking at the existing fixflags images it seems they are built using the procedure from the link i mentioned above. the reason why it did not work in my case is that due to the dead emmc in my chromebook the recovery process already fails before it even gets to the chromeos install script which gets modified usually to fix the flags (it actually fails at get_dst here: https://chromium.googlesource.com/chromiumos/platform/initramfs/+/master/recovery/recovery_init.sh#1088 and the following recover_system would later call the modified script) - so no chance to fix them this way. i had a closer look at the recovery scripts and to me it seems there is no way to enter own code to fix the flags before that point.
best wishes - hexdump
hello,
is there any documentation on how the fixflags images from https://galliumos.org/fixflags/ were created? i assume it is essentially following this one https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/workaround-for-battery-discharge-in-dev-mode maybe?
if yes: are there any additional things done - if no: how are they created then otherwise?
the background is that i try to create a fixflags image to make a chromebook with broken emmc useable for running from usb again, but following the procedure above it looks like my changed chromeos-install script never gets executed really (according from what i can see in the recovery logs) ... so maybe there is some extra magic required i'm missing ...
a lot of thanks in advance and best wishes - hexdump