If you want to continue on the team lead track, don't request a demotion, fix the problems. Requesting a demotion is fine if you have decided that being a lead is not for you, otherwise it is running away when the going got tough. In that case, you will never be a succesful lead, because in all honestly, the going is always going to be tough when you are lead.
First you need to get a better idea of the problems. Why do your team members not like you?
What problems did the other teams have with you?
You can't fix what you don't know is wrong.
The deadline is the easiest fix. Most likely the problem is that you didn't comminicate early enough or raise the seriousness of the problems causing the delay forcefully enough.
To be a lead, you have to communicate well, bad news as well as good news. Bad news needs to be communicated as soon as it is known,. Otherwise you are managing by wishful thinking. If you ever find yourself thinging, "well yeah we are behind right now but can make it up later", you are already in trouble. It is far better to say (3 weeks ahead of time), "We are having a problem with XYZ and it is taking longer than we expect and the deadline will need to move by 3 days" than to tell them you won't meet the deadline on the day it is missed. If the deadline is immoveable for some reason, you need to tell them the problem and negotiate what you can leave off the first deployment to meet the deadline. But the biggest thing is to communicate often and communicate as soon as you know something bad especially.
You don't say anything else specific about the problems, so it is hard to address how to solve them but I will add some things I have noticed cause problems for new leads.
The first is that they try to continue to code. Once you are lead, coding is NOT your primary job, leading is. If you are still required to do some coding, you need to take on the tasks that are least important and least likely to cause delays. That is because your first prirotiy is helping your team get their work done.
New leads are often the roadblock to everyone else because they take on the most difficult/fun stuff and make devs wait when they are stuck because they are too busy coding. Helping the devs when they have a question should be your first priority not your last. Code reviews are another thing that new leads blow off as less important but which cause delays for other people if they can't push the code without a code review by the lead.
The problem with the other teams is likely communication again. The view is wider as a lead, you need to be more aware that what you are doing that could affect others and make sure to let them know.