I have ordered a little refurbished Galaxy A3 2017 (just 5 mm taller than my Moto E). Not e.supported but ‘trebled’ arm64 A/B so I expect to use e.GSI.
Done:
no SIM card, just set language, no config, have a look in OS,
first of all, enable EOM unlock to get FRP LOCK: OFF in ‘Download mode’,
disable or ‘lock’ (no permission, no data use) all non-wanted apps (gg, cloud services),
enable WiFi and launch update to latest firmware (FW) version, needs to use Manual update but worked fine,
verify and download device’s FW (‘Orange’ one) and Stock latest one (thanks again, @piero)
To do:
flash stock OS, with Heimdall CLI (first test),
read three more times all ‘howtos’ and threads I’ve found on the web
Slooow W.I.P. cause of W.I.R.L. I will edit this post and share links and useful howto in a ‘response’ below…
#2 ======
I switched on to test music player but Samsung’s app wants to update and asks to agree ‘Use policy’… I don’t want to link this device ! Turned off, and I will flash as soon as possible !
#3 ======
Hello.
Stock ROM flashed with Heimdall. No more ‘Orange telecom’ inside, securtiy patch 2020.04
Dev’ options and debugging enabled, unfortunately I had:
After I made my A3 2017 treble capable, @harvery186’s /e/ OS Q-GSIincluding MicroG 0.2.13.203915 (Exposure Notification API) runs on my Samsung Galaxy A320FL “a3y17lte”.
I have exactly the same device!
Would you mind sharing the steps you use to install /e/ on the device?
Based on topics about this phone I can read on this forum, I am pretty sure a lot of people will enjoy this!
One note, as you may know opencamera on samsung devices is not working correctly.
The only way to have a working camera for me was to install footej.
This is, I think, the only closed-source application that I have installed on my phone as of today.
This variant worked for me without a bootloop. However, I was shown a device other than my SM-A320FL. My installation variant works with eOS-Q-20201225 …
Thank you!
Whay is there two versions of the rom?
eOS-Q-20201225-UNOFFICIAL-treble_arm64_avS.img.xz
eOS-Q-20201225-UNOFFICIAL-treble_arm64_bvS.img.xz
I thought it is only one that needs to be flashed?
I notice that I am not clear of the process with these ROM’s. Some instructions mention to install some other repartitioner and treble also… not sure if you need that and what they are for?
Would love some clarity here so that I am sure that I am doing the correct thing.
What I did with these is that I unzipped them and in the TWR I Installed the Image - got 3 choices (Boot, Recovery, System Image and Vendor Image) I chose the “System Image”. I did both of them and sometimes I get that there is no operating system installed… and sometimes I get that it is and asks me to install TWR again where I choose No to as per the original instructions.
When booking the phone is still going in a loop… what am I missing here?
The GSI idea was well-intentioned, but in practice various shortcomings become apparent. Bootloops are constant companions during installation. That is why it is important to know what you are doing when you want to install GSI ROMs.
The SM-A320FL is curious. The ROM e-pie-20200416-UNOFFICIAL-treble_arm64_aeN.img is the so-called A-only variant and worked on my treblezied A3 2017. On the other hand, I had to install the A/B variant of the eOS-Q-20201225 because the A-only variant ended in a bootloop. (???!)
Hi there, this got me further than I have ever gotten. Now instead of it looping it is stuck showing the e with the bouncing ball underneath it…
I have also installed the eOS-Q-20201225-UNOFFICIAL-treble_arm64_bvS.img.xz on the system and I got also the bouncing e from that… but it doesn’t continue anywhere…
oh my side, I was not able to boot the Q version, so I stayed on the P.
I was coming from Stock Rom (Android 8 IIRC).
If you are not sure, you can rollback your phone to stock rom using ODIN (you can find the rom on samdevices or other website like this).
Then, apply my procedure and it should be ok.
I need to install my A3 2017 (back to stock 8.0.0)
Édith : one more time, I’m completely lost in a lot of threads and not sure I will use the right set of tools. @SuzieQ : how did you made your a3y17lte treble-capable, please ?
I’m downloading eOS-Q-20210124-UNOFFICIAL-treble_arm64_bvS.img.xz, needing more than an hour, here
Thanks a lot.
.
.
.
PS: download links for unofficial /e/a3y17lte (non-GSI) are dead…
PS2: bootloop, 4x
PS3: I tried to install TWRP-3.3.1, then flash Repartitioner, flash OrangeFox, flash LOS17.1 from xda and it worked
Then, back to OrangeFox, flash eOS-Q-20210124, flash GSI-patch and this … device boots on /e/
PS4 : surprised by a ‘straight’ boot in French + right hour… I tried a clean flash after wiping > recovery loop. So I have to install LOS-17.1 first, config locales and then flash eOS-Q.img and GSI-patch without wipe.
I switched on to test music player but Samsung’s app wants to update and asks to agree ‘Use policy’… I don’t want to link this device ! Turned off, and I will flash as soon as possible !
