/e/OS - Android 14 2.7 GSI bring-up

[make-nz]

@piero

old and a bit unclear

This is strange to me:

Sooooo many, and so many old Samsung!?!?

• ARM64 A/B - 1
• ARM_binder64 A/B - 2
• ARM A/B - 3
• ARM64 A - 4
• ARM_binder64 A - 5
• ARM A - 6
• Unknown - 7
S
• Samsung Galaxy A3 (2017) - 1
• Samsung Galaxy A6 (2018) - 7
• Samsung Galaxy A6 Plus (2018) - 1 (- 2 when upgrading to One UI 2.0)
• Samsung Galaxy A7 (2018) - 4
• Samsung Galaxy A8 (2018) - 4
• Samsung Galaxy A8 Plus (2018) - 4
• Samsung Galaxy A9 (2018) - 7
• Samsung Galaxy A10 - 2
• Samsung Galaxy A20 - 1
• Samsung Galaxy A20s - 7
• Samsung Galaxy A30 - 1
• Samsung Galaxy A30s - 1
• Samsung Galaxy A40 - 1
• Samsung Galaxy A40s - 7
• Samsung Galaxy A50 - 1
• Samsung Galaxy A50s - 7
• Samsung Galaxy A51 - 1
• Samsung Galaxy A60 - 1
• Samsung Galaxy A70 - 1
• Samsung Galaxy A80 - 7
• Samsung Galaxy A90 - 7
• Samsung Galaxy Fold - 1
• Samsung Galaxy J2 Core (2018) - 5
• Samsung Galaxy J3 (2017) - 7
• Samsung Galaxy J4 (2018) - 5
• Samsung Galaxy J4 Plus (2018) - 6
• Samsung Galaxy J5 (2017) - 5 and - 4 and - 1
• Samsung Galaxy J6 (2018) - 5 and - 1
• Samsung Galaxy J6 Plus (2018) - 6
• Samsung Galaxy J7 (2016) - 4 and - 1
• Samsung Galaxy J7 (2017) - 5 and - 4 and - 1
• Samsung Galaxy J7 Neo - 4 and - 1
• Samsung Galaxy J7 Prime - 4 and - 1
• Samsung Galaxy J8 (2018) - 5
• Samsung Galaxy M20 - 4
• Samsung Galaxy M30 - 7
• Samsung Galaxy M30s - 1
• Samsung Galaxy M31 - 7
• Samsung Galaxy Note 8 - 4
• Samsung Galaxy Note 9 - 4
• Samsung Galaxy Note 10 - 1
• Samsung Galaxy Note 10 Plus - 1
• Samsung Galaxy Note 20 and 20 Ultra (Exynos) - 1
• Samsung Galaxy Note 20 and 20 Ultra (Snapdragon) - 1
• Samsung Galaxy S3 Neo - 6
• Samsung Galaxy S5 Mini - 7
• Samsung Galaxy S6 - 4
• Samsung Galaxy S6 Edge - 4
• Samsung Galaxy S7 - 4
• Samsung Galaxy S7 Edge - 4
• Samsung Galaxy S8 - 4
• Samsung Galaxy S8 Plus - 4
• Samsung Galaxy S9 - 4 (- 1 when upgrading to One UI 2.0)
• Samsung Galaxy S9 [Snapdragon] - 4
• Samsung Galaxy S9 Plus - 4 (- 1 when upgrading to One UI 2.0)
• Samsung Galaxy S9 Plus [Snapdragon] - 4
• Samsung Galaxy S10 - 1
• Samsung Galaxy S10 [Snapdragon] - 1
• Samsung Galaxy S10 Plus - 1
• Samsung Galaxy S10 Plus [Snapdragon] - 1
• Samsung Galaxy S10e - 1
• Samsung Galaxy S10e [Snapdragon] - 1
• Samsung Galaxy S20 (Snapdragon) - 1
• Samsung Galaxy S20 Plus (Snapdragon) - 1
• Samsung Galaxy S20 Ultra (Snapdragon) - 1
• Samsung Galaxy S20 (Exynos) - 1
• Samsung Galaxy S20 Plus (Exynos) - 1
• Samsung Galaxy S20 Ultra (Exynos) - 1
• Samsung Galaxy Tab A 8.0 (2019) - 4
• Samsung Galaxy Tab A 10.1 - 4
• Samsung Galaxy Tab A 10.1 (2019) - 2
• Samsung Galaxy Tab S3 - 4
• Samsung Galaxy Tab S4 - 4
• Samsung Galaxy Tab S5e - 7
• Samsung Galaxy Tab S6 - 7
• Samsung Galaxy Tab S6 lite - 1
• Samsung Galaxy Tab S7 - 1
• Samsung Galaxy Tab S7+ - 1
• Samsung Galaxy Z Fold 2 - 1
• Samsung Galaxy Z Flip - 1

[piero]

old list, not so old devices…
originally shipped with Android Oreo 8 or “treblelized” as the Galaxy A3 (2017)

[Xxpsilon]

For me, the age of the device doesn’t matter as long as it can be equipped with a reasonably up-to-date degoogled operating system and works well.

---

I do not rely on device lists on the WWW.

My first step to check devices for Treble compatibility is gitlab:
TrebleInfo-5.2.3_free.apk

[make-nz]

@piero

not so old devices

@make-nz

• Samsung Galaxy J3 (2017) - 7
• Samsung Galaxy J4 (2018) - 5

@make-nz

• Samsung Galaxy S3 Neo - 6
• Samsung Galaxy S5 Mini - 7

Well, it seems to have started in 2017 and in my case this is good, as I have lots of those from my Repair-Cafe project. I’m all about not throwing them away

[make-nz]

@Xxpsilon

My first step to check devices for Treble compatibility is gitlab:
TrebleInfo-5.2.3_free.apk

Well, I remember this being pretty much wrong half the time back then on Samsung and just yesterday on this:

@make-nz

• Samsung Galaxy J5 (2017) - 5 and - 4 and - 1

Well, again, unless the list is wrong.

I wouldn’t mind so much, but I have to dig through some boxes to find them, then get the right TWRP and ROM on a slowish internet… so happy for any hints on what to try out

[piero]

@make-nz

I got lots of older Samsung, up to ~2019
[…]
it seems to have started in 2017

it was true they can run P/Q/R based GSI,
but older may face some kernel requirements limitations…

@GnuGorets

List of devices compatible with Project Treble:
( -1-2-3-4-5-6-7- referencement coding )

1 -	ARM64 A/B	- 1	treble_arm64_bvN
2 -	ARM_binder64 A/B	- 2	treble_a64_bvN
3 -	ARM A/B	- 3	treble_arm_bvN
4 -	ARM64 A	- 4	treble_arm64_avN
5 -	ARM_binder64 A	- 5	treble_a64_avN
6 -	ARM A	- 6	treble_arm_avN
7 -	Unknown	- 7	Unknown

[Xxpsilon]

@make-nz

Well, it seems to have started in 2017 and in my case this is good, as I have lots of those from my Repair-Cafe project. I’m all about not throwing them away

Devices that were delivered from the factory with Android 8.1 have a chance of receiving a GSI. However, Android 9.0 is better, although the selection of GSI in 2025 is also very small. Android 10 already offers more options.

For devices with first deliveries of Android 11 and higher, the chances are good that even Dynamic Partitions are supported.

Unfortunately, this hardly applies to Samsung Galaxy devices. Even Samsung Galaxy A/B devices with stock Android 13 and 14 usually do not support Dynamic Partition and therefore no Seamless Updates (GSI OTA update)

[make-nz]

@make-nz

Samsung Galaxy J3 (2017) - 7

Here is what TrebleInfo thinks:

[piero]

so as same as the list that say : “Unknown”

[make-nz]

Yes, Unkown to the App, too!
I have a J3 with:

https://xdaforums.com/t/treble-vendor-a64-aosp-project-kebab-2-0-v2-2-1-j330x-7570.4182787/

And there were sooo many devices this App said they would not work.

[piero]

it has been treblelized :

if you are on old Create_vendor please revert it

• Flash Exynos7570_CreateVendor 2.0 Or The new repartition script for J2 Core use this script and reboot recovery, (the new repartition will wipe all data also internal storage but will increase system partition and vendor and you have to wipe system, cache, vendor and format data).
• Flash KEBAB 2.0_EXYNOS7570
• Flash your desired A64 A/B GSI (ARM32_Binder64) : “a64_bvn”

[make-nz]

It is soo long ago, I did all this.

I have found these two working J3, left being F/DS on stock A5 and right being a FN on /e
I had 4 or 5 of them, and maybe reverted the F/DS to stock. There was major trail and error.

What would be needed, to give this F/DS a go?

[piero]

A5 is not on the GSI list…

but photo say :

Retail Branding	Marketing Name	Device	Model
Samsung	Galaxy J3(2016)	j3xlte	SM-J320F
Samsung	Galaxy J3(2016)	j3xnlte	SM-J320FN	e-0.21-n-20221123-UNOFFICIAL-j3xnlte.zip | by tcecyk for Galaxy J3 2016

what CSC do you use ?

[make-nz]

@piero

@make-nz

on stock A5

as in Android 5

[Xxpsilon]

@make-nz

Here is what TrebleInfo thinks:

I assume you are talking about this: TrebleInfo-5.2.3_free.apk

@make-nz

And there were sooo many devices this App said they would not work.

This recent Treble Info app is for initial information. The information is not like the Amen in the church.

---

In the early days of Treble GSI, this app was used very often from F-Droid Store: Treble Info 5.1.1

Both Treble app versions deliver partially different results.

---

@make-nz

https://xdaforums.com/t/treble-vendor-a64-aosp-project-kebab-2-0-v2-2-1-j330x-7570.4182787/

The author @asarre writes:

Some information you should know…

This is a full Treble ARM A64 Vendor/Kernel Based on J4 and J6 for Exynos 7570
…
General features:

• based on J600F a bit with extra Blob and HAL.
• Support most of 7570 Device: G570X, J400X,J260X,J330X.
• Support Q,R GSIs.
• It’s system as root.
• More performance compared to stock.
• Nitrogen Kernel V5 With treble support

In short, this means: This GSI is a special version for the Samsung Exynos 7570 Quad SoC devices and will consequently not work on other SoC architectures.

[make-nz]

Okay, I got too many devices and to little brain memory for all these Samsung names and numbers and years and versions…
Just found the box with the postit:

Samsung Galaxy J3 (2017) Duos with dual-SIM card

So my above J3 2016 is out of the game. Will grab the the 2017s now.

[piero]

@make-nz

all these Samsung names and numbers and years and versions

Supported devices - Google Play Help - Google Support

@make-nz

Will grab the the 2017s now.

Retail Branding	Marketing Name	Device	Model
Samsung	Galaxy J3(2017)	j3y17lte	SM-J330F
Samsung	Galaxy J3(2017)	j3y17lte	SM-J330FN

https://samfw.com/firmware/SM-J330F

originally shipped with android 7, so not originally treble-compatible, it have to be trebelized…

if you are on old Create_vendor please revert it

• Flash Exynos7570_CreateVendor 2.0 Or The new repartition script for J2 Core use this script and reboot recovery, (the new repartition will wipe all data also internal storage but will increase system partition and vendor and you have to wipe system, cache, vendor and format data).
• Flash KEBAB 2.0_EXYNOS7570
• Flash your desired A64 A/B GSI (ARM32_Binder64) : “a64_bvn”

https://xdaforums.com/t/treble-vendor-a64-aosp-project-kebab-2-0-v2-2-1-j330x-7570.4182787/

[make-nz]

It was my brain telling me I did a treble on a J3 and my eyes saw one box with J3

[Xxpsilon]

@piero

so have to be trebelized…

@Xxpsilon

This is a full Treble ARM A64 Vendor/Kernel Based

Standard custom GSI use VENDOR from stock Android and do not require an extra vendor partition.

---

Our last posts have nothing to do with the specific /e/OS - Android 14 2.7 GSI bring-up thread title. /e/OS-U 2.7x A/B GSI will not run on the old Galaxy devices from @make-nz .

[make-nz]

@Xxpsilon

Our last posts have nothing to do with the specific /e/OS - Android 14 2.7 GSI bring-up thread

Absolutly, I got a bit derailed by

@Null

rule of thumb they need 64 bit vendor files and to test if it works try Andy’s Lineage21 GSI

thinking, I’ll just test whatever Treble device I have.