but… when you go to the download page for the latest ROM:
https://images.ecloud.global/dev/star2lte/
I only see e-0.13-o-2020120889191-dev-star2lte.zip [MD5 | SHA256] which is pie not Q…
What am I missing?
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
A o in the name means oreo? Not pie and yes, not Q
Not sure, I was confused.by 20201208… Implying december. And still version .13
Dunno
The version number .13 is of little importance. The -o- [oː] aka Oreo aka AOSP Android 8.1.x is much more important. And yes, e-0.13-o-20201208*.zip is from Dec 8, 2020.
This is also about the same topic: Galaxy S9 / S9+
This is an error in the documentation…the download images links have not been activated. This was mentioned here …the Q images should be available for download later today
Sorry for the inconvenience
Looks like they are up 
at least for the S9+
Thanks for all the work guys
hmmm tried the update via instructions and get this error:
ERROR: 7
Vendor image on the device is NOT compatible
Expected Android 10 vendor
sadly , the same for me … it is a e.foundation S9 (ie. bought from e foundation shop)
… so it is not encrypted … may i need to wipe “more” or upload additional “img”?
Not sure. My phone is also not encrypted. I did not try to wipe and not sure what if anything to do with the backup image…
Will try again this evening. Noon over here. Let me know if you have any success 
This thread about Samsung Galaxy S9+ (star2lte) and S9 (starlte) was closed four good hours ago:
Thanks for the help @SuzieQ so far. Do you know a good resouce to flash firmware. I have Samsung SM-G965F/DS and having a hard time flashing updated Firmware. Currently v8. Tried v10 all night with different sources from the net, I think I also tried V9. Using all sorts of software…no success. Usually states something wrong with the file…
Not my first time doing this, never had so much of a problem. Hoping something silly I am missing
BTW Live in USA, phone not sold here so I am using other CSC of course.
Hi @Randy,
Samsung stock firmware is available on various channels. Two reputable ones are sammobil and samfrew. Samfrew has the slightly faster free download, but it still takes hours to download the zipped 4.6 GB ROM.
Right now I can’t tell you why you might be having such “big problems” because your details are too skimpy and not specific enough for me. The number of possible firmware versions is too large, so first tell me which bootloader version is installed on your Galaxy S9+. It can be found under > About > Software Info > Buildnumber QP1A …G965F… The baseband version can also help: G965F…
So… screwed up, as:
Now I have a bunch of .bin ans .img file, BUT I don’t want to flash blindly according to the PIT output, as I want to keep TWRP installed.
Is this even possible ?
What partitions should I flash to “update the Android firmware” to Q, and then be able to install latest /e/ q image for S9+ (without bricking my phone if possible 
)
Well tried odin one more time now phone appears to be bricked…stuck in endless loop of booking and rebooting…
I am done for a few days taking too much time.
Will get back if I am able to get this to work
This HowTo is not suitable in all respects for upgrading from 8-Oreo to 10-Q on a Galaxy S9+ (hero2lte) and S9 (herolte).
The S9 / S9+ and stock Android 10 and therefore AOSP 10, on which /e/OS ‘Q’ is based, have limited comparability with lower Galaxy devices and OS versions.
In order not to lose TWRP Recovery, you should not install the recovery.img file - but I would not flash individual files, but use Heimdall to flash the four unzipped files AP_ BL_ CP_ CSC_ G965FXX*.tar.md5. In the process, TWRP is completely replaced by the stock Android recovery. But this is not a problem, because TWRP 3.5.0_9-0 can be very easily and cleanly reinstalled with Heimdall.
I started going the “flash individual files” path (but I’ll probably follow your advice finally…), and comparing the device PIT content and the files (.img and .bin) available in the stock rom, I see corresponding filenames / partitions:
–BOOTLOADER sboot.bin --KEYSTORAGE keystorage.bin --BOOT boot.img --CACHE cache.img --CM cm.bin --RECOVERY recovery.img --RADIO modem.bin --DQMDBG dqmdbg.img --SYSTEM system.img --VENDOR vendor.img --ODM odm.img --HIDDEN hidden.img --OMR omr.img --USERDATA userdata.im
But I also see several partitions holding files that are absent from the stock ROM:
Partition Name: ECT / Flash Filename: ect.bin
Partition Name: MD5HDR / Flash Filename: md5.img
Partition Name: EFS / Flash Filename: efs.img
Partition Name: PARAM / Flash Filename: param.bin
Partition Name: UP_PARAM / Flash Filename: up_param.bin
Partition Name: DTB / Flash Filename: dtb.img
Partition Name: DTBO / Flash Filename: dtbo.img
Partition Name: NAD_REFER / Flash Filename: nad_refer.bin
Partition Name: STEADY / Flash Filename: steady.bin
Partition Name: CP_DEBUG / Flash Filename: modem_debug.bin
Is this expected, and what are these partitions for ? (just trying to understand before bricking the phone with too much hurry !!)
@alci , my impression is: You are skating on thin ice!
Samsung’s Stock Android 10 comes as a packed file. Depending on the download source, as a single file with the file extension *.zip or *.tar in which there is then either a single file with the extension or as 4 or 5 files included with the extension .tar.md5
AP (System & Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC (Country / Region / Operator)
HOME CSC (Country / Region / Operator)
The first four *.tar.md5 files are conveniently installed with Odin/Heimdall without the user having to worry about which file to flash where. The procedure presented here is the much riskier method and is an invitation to brick your device. If you know exactly what you are doing, the situation looks different again. Do it right!
As you might have guessed, I really don’t know exactly what I’m doing !
So I’ll stick to the way you advice !
I was just trying to postpone the moment where the dice is cast… and to understand a bit more.
So, let go flash the *.tar.md5 
I’ll keep you informed…
Yes, a few words of feedback are always welcome to me and much preferable to wordless “Heart”