nobody can't solve this problem?
You have been given two solutions. If they are not OK for you, you need to explain why.
Oh, I see now that you have changed the expected results since I and Cosmog posted our queries.
If that is the result you want, you should reconsider your table design. What you have is known as EAV, Entity-Attribute-Value. EAV has the advantage of being dynamic. One more attribute - just add it! But there is also distinct disadvantages, and your question is a token of this.
You are asking for a dynamic pivot, which is a non-relational operation, so you get duly punished when you try this in a relational database. Not that you have to serve time, but the code gets complex.
As this is a common question, I have written a general text on dynamic pivot which you find here: https://www.sommarskog.se/dynamic_sql.html#pivot. But beware that it is part of a longer article on dynamic SQL, and if you have not worked with dynamic SQL before, you may want to back up to the beginning.
Tip: you may find it easier to do this operation client-side.