Thanks to Phh and PhieF for patches and build scripts
Please read carefully !
The original build script from PhieF includes a defaut device encryption without password. So there is noway to get access to your data via TWRP. I have removed this in my built script.
The original build script from PhieF includes also rooting the device by default. Because a ‚normal‘ user don‘t need root and a lot of banking apps wont work on rooted devices I have removed root.
The original build script from PhieF builts the full set of 6 different GSI. I have changed to 1 GSI. Between line 119 til 124 of buildbot_treble.sh you can decide which GSI type you want to build. Therefore you have to stop the build script after repo sync.
The patches / additional sources from Phh do have a mistake. So I have created a fork of the Samsung drivers which are incl. in the manifest.xml
The building itself is very easy. Start my built script and after some hours you will have your GSI image in out folder
if you want better use original script with default encryption and SuperSU you should change line 5 in my script to:
git clone https://github.com/phief/e_gsi_localmanifest .repo/local_manifests
First, thank you for your effort for creating and compiling this scripts!
I have tried (Ubuntu 20.04) to create GSI build from this script for 5-6 times but every time my build process fails with (more or less) this errors:
hi, I’m not sure because as I have written, all theses scripts and patches are from others. But I have had also a lot of crazy errors when using a linux with python3 and Ubuntu 20 has python3.
So better to downgrade python or lot better to downgrade to ubuntu 18.04 LTS and trying once more. I hope it will run than without errors.
but wait, it could also be an unix issue. try first
unix2dos gsi.sh
Actually, i saw your post somewere about Linux Mint so i think i’ll better create Mint 19.3 VM and try with that.
Thanks for the your help and the info!
You can’t build a GSI with docker. And I’m a none docker builder. So I have no knowledge about docker.
If you want build a standart rom with docker, pls check the docker build docu.
Your error message is pointing to a wrong repo command
As yku can see here, there is no branch v.011-pie only a ‘tag’. For using the tags, the comnand must be different. But I don’t know how
I would try using ‘v1-pie’
Edit: by the way, you know that there is a Q version under custom rom available for your device?
sorry, I posted the building steps for S9 starlte because I followed the e foundation guide to build a ROM…
When (if) my build were ok, I would have changed to test my own device…
my device is an A7 2018… for this device I would need the Q ROM
Sorry to bother you again…
I am a newbie in this field…
OK, I started to execute the commands of the building script.
The first line is: repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v1-pie
and this is the result in terminal
user@pc:~$ repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v1-pie
gpg: keybox ‘/home/user/.repoconfig/gnupg/pubring.kbx’ created
gpg: /home/user/.repoconfig/gnupg/trustdb.gpg: trustdb created
gpg: key 16530D5E920F5C65: public key “Repo Maintainer repo@android.kernel.org” imported
gpg: key 67B7E448692B382C: public key “Conley Owens cco3@android.com” imported
gpg: Total number processed: 2
gpg: imported: 2
[new tag] v2.9 → v2.9
repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.
… A new version of repo (2.8) is available.
… New version is available at: /home/user/.repo/repo/repo
… The launcher is run from: /usr/bin/repo
!!! The launcher is not writable. Please talk to your sysadmin or distro
!!! to get an update installed.
repo: Updating release signing keys to keyset ver 2.3
Downloading manifest from https://gitlab.e.foundation/e/os/releases.git
Invalid clone.bundle file; ignoring.
fatal: Couldn’t find remote ref refs/tags/v1-pie
manifests:
fatal: Couldn’t find remote ref refs/tags/v1-pie
@harvey186
thanks for your support…
I’ve been able to finally create a VM on LM19.3 with a building chain and I did complete the repo sync command…
this evening I’m going to start building…
I’ll keep you updated