Hi @jean78 if it is not on the supported list chances are the build will not work. You may get it to install but the OS would throw up weird errors. At worst a mismatched ROM can brick your phone. You have already added a request for a device - the more the users requesting for support the better the chances of a build for this phone.
@Anonyme thank you so much for your turotial, I succeeded installing /e/ and I feel so happy now!
@anyone;
But now new challenges arise… I followed the steps, including to select the option NOT to install TWRP after flashing the device. However, after installing /e/ a system-update is being offered and I get a message;
Apply update
you are about to upgrade to /e/OS 0.7 - 24 Jan 2020.
If you press OK, the device will restart itself in recovery mode to install the update.
Note: This feature requires a compatible Recovery or updates will need to be installed manually.
When I press OK my device will reboot, but I enter in TWRP menu again. So it seems TWRP is installed, after selecting “do not install”.
My question is;
*is there a possibility to remove TWRP from my device?
*is it safe to remove TWRP from my device?
*how can I install the system-update?
I have to admit I allready tried some ideas myself, for example;
*after being in the TWRP menu I noticed the e-xxx-xxx-xx.zip-file is still there, so I choose to remove the .zip file and the TWRP-directory which where installed and used in the flashing proces.
*have I screwed up when doing this experiment?
thank you
How can I uninstall or remove TWRP from my device?
For the vast majority of devices, you don’t actually remove TWRP to get back to the stock recovery. Installing a different recovery is your only real option. Simply install whatever recovery that you want and that will overwrite or replace TWRP. Usually you can follow the instructions on our website for installing TWRP manually, only use the file for whatever recovery you are choosing to install instead of the TWRP file.
Note, we don’t keep or maintain a database of stock recoveries. If you are trying to reinstall the stock recovery, you will have to find a copy of the stock recovery on your own.
1 Like
my apologies
I found a post precisely answering my questions on this forum in the link below. (also by @Anonyme) @archje thank you for your quick response. Hopefully I keep learning everyday, for a long time to come. 
I want to thank everybody involved and contributing with the /e/ project. You are making my day.
1 Like
I’m hoping someone can guide me around a problem I have come up against, while preparing my Samsung Galaxy III International i5300 phone for flashing with /e/ OS. I have never flashed a phone before, and this phone is only being used as a music player at the moment as I upgraded last year to a Motorola G7.
I am using Anonyme’s very clear instructions “[HOWTO] Install /e/ on a Samsung smartphone with Windows easily” as my knowledge of command- line is sketchy. I realise the phone he has flashed is not the same as my phone, but this phone is on the list of supported devices.
I didn’t get very far… When I came to “3) OEM Unlock” it was missing, so I followed the instructions to activate Developer Options [it was already activated], then looked again but OEM Unlock still wasn’t in Developer Options.
I then attempted to update Android; I unchecked Automatic Date and Time/ changed the date on the phone to 10 days in the past, looked for ‘Auto Update System’ [not there], found ‘Software Update/ Auto Updates’ and unchecked it, tapped on ‘Update’, got the message “latest updates already installed”.
Next I rebooted the phone and turned on ‘automatic date and time’ again; restarted the phone and check to see if OEM Unlock had magically appeared; still not there.
I then did a Factory Reset to see if that changed anything. The Android version is still 4.3 as before.
Where do I go from here? I’m thinking I should save up for one of the refurbished phones with /e/ already installed, anyone think of something else I can try?
So far I have avoided Samsung phones, because the instructions seemed to require building “Heimdall” on Windows (build “not available”?) I could set up a Linux PC just for Heimdall, but overall this is all very confusing.
Is there a problem with installing Odin instead, and why is it not mentioned in the official instructions? Thanks!
There is no difference in the final resulat. Both methods will install TWRP on your Samsung phone.
It’s true it’s not mentioned directly in the installation page of Samsung devices, maybe it should since this HOWTO seems safe a tested by many users.
No, I don’t know any problems of this kind: Wind°ws and “Odin 3” fit together as well as Linux and “Heimdall”.
The majority of “professionals” especially software developers use a Linux derivate and have already given up using Wind°ws a long time ago. Wind°ws is as reluctant to be put into the mouth as G°°gle. So tools are primarily mentioned on Linux basis. They simply “forget” that 3/4 of the “normal” desktop PC / notebook users work with Wind°ws as operating system. An effective Wind°ws tool is Samfirm, a fast free downloader of Samsung Android firmware.
I belong to the Wind°owsers of the first hour. My W°Systems are largely “closed”, so that it can only rarely “phone home”
Good point. Will have a reference to installing Odin also added to the official /e/ documentation.
That’s brilliant. I remember when checking out /e/ for the first time the Samsung instructions looked like a big hurdle, so I only looked at Motorola. Samsung being the most ubiquitous models, it should be as easy as possible for Windows users.
Hello, I installed a Samsung S9 via this method. Worked like a charm and today I tried my luck on the Galaxy S7. No luck this time. I bricked it twice but via Odin I could bring it back to the original Samsung installation. The problem actually was not Windows or Odin related but the phone seemed to be encrypted. In case of wiping as written in the article do this:
Boot into TWRP after the upload to the phone
Choose the button “Keep Read Only” It seems to me that the Galaxy S7 had encryption on by default.
Choose the “Wipe” button
Choose “Format Data”
Type: “yes” and now everything is wiped off the phone
Reboot into Recovery and choose “Do not install”
Choose “Keep Read Only”
Now you can go on with the installation of /e/
Everything went well
Thanks for the nice manual! I trying to use this ROM for my Galaxy S5 Mini (kminilte).
Everything works fine for me until the flashing process.
I am encountering error 7. While I could avoid the device check with the above posted infos, I now have a new error 7 which is the following:
Patching system image uncondituonally...
mkdir "/cache/revovery/
19e673c[...]/" failed:
No such file or directory
E1001: Failed to update system image.
Updater process ended with ERROR: 7
ERROR installi zip file 'e9.zip'
Updating partition details...
... done
Maybe somebody has an idea?
Hi, welcome in the forum 
Which version of TWRP do you have ? The error 7 happens on old version of TWRP, like 3.1.1 for instance. Last version is 3.3.1 (if my memory is good enough).
Oh a 3.4.0 version was released 3 days ago and is available for your device.
Thanks, and thanks so much for the fast reply!
I am using twrp-3.4.0-0-kminilte, so I guess that is not the problem.
OK, I wanted to install /e/ on another phone (Samsung A5 2017, a5y17lte) which resulted in the same error. Finally I just tried so previous TWRP version 3.3.1-0 which worken like a charm on both devices! So I would recomment to abstain from using 3.4.0 for these two devices!
All right, thank you for the tip !
Thank you so much. I had a similar problem installing /e/ on my Samsung J5 and using the TWRP 3.3.1-0 instead of the 3.4.0 solved my problem.
Very helpful comments @izgrimmer @Anonyme:
Had the same Error 7-Problem with a Samsung Galaxy S8 and TWRO 3.4.0. With the TWRP 3.3.1-0 it was no problem at all.
Thanks @Anonyme! I did the flash with your tut and worked well. Way easier than the e tut. I had only troubles that I couldn’t put the zip file in to the internal storage, I put it instead on a micro SD and bootet it from there, merci encore une fois!