Can't find extract-files.sh/can't run it while following "How to Build the /e/ ROM?" page

Using /e/OS Build /e/OS
,
9

The necessary files are usually found in the device tree source code for your device. That won’t be present on your build machine until EITHER

  • repo sync has been called, either manually or by the Docker instance OR
  • you manually git clone the repository containing the device tree code

The more usual way of getting proprietary blobs is to get them from a git repository such as TheMuppets github repos. That used to be done automatically by using the USE_PROPRIETARY flag in the docker run command. But /e/ chose to break this functionality when they decided to use their own forks of ‘TheMuppets’ repos, and then decided to make those forked repos accessible only to /e/ developers. This broke a build method that had previously worked for people making unofficial builds.

Instead of reverting that change, they changed the official 'HowTo Build` document to say, in effect “you’re on your own when it comes to the proprietary blobs”. And they did it in such a way that - as you have found - means that following the instructions does not work! :frowning:

If there is a 'TheMuppets` repo for your manufaturer / device, then you can include it in your local manifest, and there will be no need to extract the files manually. Which is good because the instructions of extracting proprietary blobs (which were copied from the LineageOS Wiki pages) are out of date, and don’t actually work for many (most?) devices.

Good luck!

2 Likes