Open deco493 opened 4 years ago
Ah -- my bad, looks like still some investigation to do. After auto-update locked back out again :(
Some more things to try - will post updates if I can get it working.
@deco493 Galeforce definitely still works. Check out my comment here: https://github.com/marcosscriven/galeforce/pull/47#issuecomment-704491729
I have some good news for anyone who has been following this repo... galeforce still works! Recently I got hold of a couple of spare Google Wifi devices so I had a chance to try the code without breaking my home internet... it took a few tries but I can now reliably flash a new ROM and get SSH root access after a clean recovery reflash from the onhub downloader.
Here's what I had to do to get it working
The version of dropbear has changed in the raspbian package archive, so I've updated this to point to an available version that can start up under Chromeos version 9334.41.3 (Official Build).
I found that I could not build the image under Vagrant. I'm not entirely sure what the problem is but I'm fairly sure it has to do with reading the image and creating loopback devices while Vagrant is simultaneously presenting the gale.bin file via its own loopback mechanism.
Successful building and flashing to thumb drive was thus done on a bare metal linux machine (Ubuntu 16.04 in my case, but a newer release should work fine too). It may help to manually run kpartx and check the loopback devices are created - this has to work to create the image. You can also mount and check your image contains the galeforce directory just to be sure:
~/code/galeforce/output$ sudo kpartx -av gale.bin ~/code/galeforce/output$ sudo mount /dev/mapper/loop0p3 /mnt