From stock Android 5.1.1, I installed TWRP, formatted data and cache/system, and then adb sideload e/f e-0.18-q firmware, then reboot into Recovery a couple times before rebooting into System.
Boot is stuck in the Samsung S5 Neo words - I have to remove the battery in order to power off. Even if I wait 10 minutes, it never gets to the bouncing /e logo.
I tried older versions e-0.16-q but it still gives the same stuck boot screen result.
I tried itsclarence unofficial e-0.17-r and it gives a different result: the Samsung S5 Neo words come up for a few seconds and then the phone powers itself off.
I restored with boot/data/system of Android 5.1.1 backup via TWRP to return to the stock firmware.
Any ideas on getting this Canadian SM-G903W flashed with /e?
Models after the Samsung S7 SM-G930W8 appear to not be able to unlock the bootloader or whatever technical incompatibility is caused. So yes, G965W won’t work.
However, supposedly people have gotten /e working on their G903W.
ok: I wiped data, cache and system and then reboot to recovery. then adb sideload e-0.7-p-20191015-UNOFFICIAL-s5neolte.zip and reboot to recovery. then reboot to system
→ still stuck on Samsung boot screen
I might be way off here, but the clues I picked up were that often “just flashing the manufacturers ROM first” is the answer ( … to stuck on boot screen) … you have lots of people reporting difficulties … cannot quite specify the issue … you have multiple “original ROMs”.
How do you decide which ROM to flash in order to give you a “fresh start”?
This was to highlight that it took an exceptionally long time at one of the boot screens. I let it be for about 15 minutes at least but likely an hour while it seemed to hang or be doing something.
The build wasn’t supposed to be the point. It was included as I did have other builds not work though. Unfortunately I don’t. I just looked up the Build from the settings on my device. The repo was linked to from this forum. I found the thread by searching for s5neo " or something like that. Don’t remember much more.
(One other thing I find Odin to be much more reliable to install a custom recovery. I can’t recall if you got your recovery working