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
I will try again and wait an hour of just seeing the Samsung Galaxy S5 Neo screen.
To me, the build might be a potential avenue to pursue.
TWRP old and new seemed to work (able to reboot, able to issue adb sideload command, able to install zip on sdcard). I could also try installing with Odin.
Will keep this post updated when I have time to test those things.
I encourage you trying to install lineageos to be sure /e/ is the problem and not your device.
( use their recovery) If it works try to install /e/ with it
You have to format /data, not wipe, when changing the OS to another build lignee, or changing android version grade.
then reboot to recovery and wipe /system,
Finally install the new OS and wipe /cache, and /dalvic-cache
And then in Lineage Recovery, installed lineage-17.1-20210905-nightly-s5neolte-signed.zip from SDCard. I couldn’t see any wiping data options in Lineage Recovery, so I didn’t do any. —> seemingly stuck Samsung boot screen.
I could try again to see if Lineage would boot, if someone knows how to wipe the appropriate partitions using the Lineage recovery.
Edit: I did find the format ability in Lineage recovery via Factory Reset: format system, cache, data. Now try install from sdcard. → reboot → waiting on stuck Samsung boot screen to see if it will progress at some point (I’m not going to wait more than an hour)
Don’t wait more than 2 minutes on the Samsung logo…
Waiting 5 or 20 minutes only make sense if you see the / e / logo bouncing animation !
.
.
Could you flash back to latest Samsung firmware using Odin on a windows PC ?
( or having a Heimdall firmware package ? )
( or create one with TWRP embeded ? so, no need to boot on Samsung OS ! )
I think this is the solution. I just talked to someone who successfully flashed G903W with LineageOS. He looked at my situation and said that I had to flash it with the highest Samsung stock firmware.
He said that I needed that version’s baseband before I could install a custom ROM on that phone.
When I get time and find the correct Samsung stock rom, I will give this a try.
I am stuck in similar place. What I get however is that the phone reboots in recovery mode instead of hanging on the bouncing ‘e’. I am able to install/run properly an older build I found here:
Looks like there is a defect logged, but I am unclear if it’s specific to this case or a general problem for the NEO 5.
Somebody was able to use one of the latest official builds?