Your post is almost entirely about you. Do you only talk about you at work? It might explain a bit.
What are your team members actually like? Their personalities, interpersonal conflicts, aspirations, successes, strengths, weaknesses?
I don't know either you or them, but the fact that you have asked us all for help and told us almost nothing about them suggests (to me - I may well be wrong or biased) that you are not spending enough time getting know them. I expected you to tell us specific situations that would lead them to not like you, but you seem not to know any. I doubt they would be short of reasons if we asked them. It's rare to find anyone who dislikes people for no reason.
For me, a team lead's role is not coding. You are there to assemble, manage and grow the team that will do the coding. Maybe that involves doing some of the code (more likely the code reviews) yourself, but maybe not. Your real role is the people management and that involves a deep understanding of who these people are and what motivates them. If you are trying to stuff engineering knowledge down their throats when what they really want is autonomy (for example), then it's unlikely they will warm to you.
I would recommend approaching this as a completely new skill, which is as hard to learn as coding was. Some people build their careers entirely on being able to manage and grow teams. It's worth noting that these people tend to get paid more than the developers they manage :)
Sorry I can offer much more insight, but there's not a lot to go on. I hope things improve for you.