It’s the part from the instruction that doesn’t seem to be needed on every device so I first tried it without. But then indeed the installation did fail so I had to execute that as well. (Although I’m not really sure what it does exactly)
On some devices, installation can fail if vendors are not up-to-date. In this case, please:
Download those vendors
Install them
On the device, go into Advanced > ADB Sideload, then swipe to begin sideload
From the computer, please run adb sideload <vendors file>
Ok, so I’m stucked in step 1… Cant install Heimdall in Mac. Is there any way to skip this and somehow use Odin or some other tool that doesnt require command lines? In Nexus 5 i was able to install adb and fastboot and then trough TWRP flash /e/ image, but this time I didnt even reach that phase
Thanks! In my case the phone is the following (second hand):
Model: Galaxy S9-G960F.
Firmware version (can’t find it), but the kernel version says 20.09.2019
Security patch: 1.09.2020 (in case it’s relevant, I don’t know).
Android 9.
Base band version: G960FXXU6CSGD
Hi! Ok, I have another problem. I was following @Anonyme instruction and in step 3, OEM unlock, I activated it (it appeared in developer options). According to the instructions, “activate it and don’t worry about the warning”. I activated it and the phone did a factory reset. It didn’t say anything similiar in the tutorial, but I assumed that after the factory reset the OEM would be activated. But then, after setting everything up, in the developer options there was no OEM unlock button at all, neither activated nor deactivated. I followed the advice of @0x7C0 to make the OEM unlock button appear, but I didnt appear. Any help? By factory reseting it (without internet) did I updated something that prevents OEM unlock? It seems that I’m going backwards in this quest…
EDIT: ok, it appears that after rebooting the date was again set to the actual date, so changing it some days before to day made the trick and now OEM Unlock is showing and bootloader is unlocked.
Almost a year ago I tried to install /e/ in a Xiaomi MI 6 without succes and I got so frustrated I abandoned the quest. After taking strength again, reading a lot in the forum, with the previous experience and (specially) thanks to ALL OF YOU, in this second attempt I managed to install /e/ succesfully in my “brand new” second hand S9!!!
All the little details that @archje mentioned appeared, but I was able to solve them thanks to the answers posted in this thread, as well as others in the forum!
I will briefly describe my process in case it’s useful for anyone like me who is kind of newbie:
As I dont know about command lines and stuff, I didn’t follow the official install wiki and followed @Anonyme s guide for Samsung phones, which is very carefully and clearly explained.
OEM unlock button didn’t appear: I followed this recommendation from another thread, that also @0x7C0 mentioned that could be problematic. It didnt’t solve it at first, but after connecting to the internet and changing again the date, the OEM unloeck toggle reappeared.
In step 6.6 of the guide, i followed the WARNING, but didn’t succed. Then I followed the alternative suggested, and it worked, but I’m not sure if TWRP is permanently installed.
The vendor problem also appeared:
On some devices, installation can fail if vendors are not up-to-date. In this case, please:
Download those vendors .
I copy and pasted the vendors zip in the internal storage, but found that in the guide it says to copy them next to the TWRP folder, and I didn’t find that folder in the internal storage. Therefore, again, not sure if TWRP is permanently installed (I guess that could led to some update problems in the future?) I’ll wait till the next update is released to see if I can update via OTA or not (that would be the ideal for me).
Being able to find all this info has been critical for me to prepare everything before the flashing. That was the main reason I choose the S9, because with the Xiaomi MI 6 there wasn’t as much info and help in the forum to search.
I still have to transfer contacts, data and stuff and check if everything (bluetoth, tethering…) works ok, but, again, that couldn’t had happened without your help and support. I’m happy to be closer to degoogling! Thank you all!
Hi @archie, after I made those changes, then I go to “reboot” and “power off” and the phone goes off, but then when switching on it goes into twrp instead of the normal phone.
install Odin on Windows (Heimdall/adb or Jodin didn’t worked for me on Linux)
install Samsung Drivers on Windows (end of linked page above)
put no-verity-opt-encrypt-samsung-1.0.zip, VENDOR-27_ARI9.zip, e-0.8-o-2020041249358-dev-starlte.zip on SDCard (the links for the 2 first files are higher in the current topic)
install TWRP with Odin. Uncheck Auto-reboot and use the MANUAL method
in recovery mode, advanced wipe Dalvik/ART Cache, Data, Internal Storage, cache, system
repair/change data partition (format exFAT, format back ext4, resize FS) to crypt data afterwards (higher in the current topic)
install/flash no-verity-opt-encrypt-samsung-1.0.zip with TWRP (from SDCard)
install/flash VENDOR-27_ARI9.zip with TWRP
install/flash rom e-0.8-o-2020041249358-dev-starlte.zip with TWRP
wipe Dalvik/ART Cache
Reboot
Wait 5 mins.
/e/ starts
crypt the phone (parameters, security)
if you want, root the phone with magisk AFTER crypting (optional)
