[T-Mobile REVVL V+ 5G] kaliman_chance:
1.Send your boot img , and the results from fastbootd with the command: (fastboot getvar all). I am assuming you have all this prepared. From now on, that will be a prerequisite prior to my giving valuable (billable!) time away, excuse me (op and member who is being replied to), but everyone has to hear this. I'm by no means neo on this discussion board, but there has to be some checks and balances so that users who truly need help (seeds) are somewhat separated from the (leechers).( I use that term/analogy loosely, to represent the point I'm making here.) This craft, in its own self contained niche, is not always challenging, but anyone who came from the bottom as I did back when this knowledge was coveted, unique and the hottest topic since windows explorer gui was created in windows 3.1, there was a certain level of pride and accomplishment felt when a user found a way to obtain root access. (a knowledge we'd have never learned had it not been for those patient enough and willing to somehow siphon this knowledge to us.) Android was designed, at least at first with full customization/ mod access as its pitch to devs, allowing the Google phone to become a serious contender with our own domestic apple company. The info about the hardware and kernel exploits back then were spoonfed to us gradually, in the form of leaks, which again (someone at Google has hella foresight) was by design so that they didnt have to handhold. Rooting and modifying the sys, product etc is and should be pretty much impossible for the average layman. The goal is that if you were adept, and not stopped on the first step, second third steps, you'd for sure be stopped in your tracks by avb, which required a little background in unix and sometimes even electricity for us mediatek people(some mtks you have to short a test point on the motherboard). Each step was a security measure; Not to stop devs or advanced users, but for those who are truly a danger to their device, which if happened caused collatteral damage to the vendors bottom line. (either through the loss of revenue from customers rooting subsidized "free" flagship deals which would root and change carrier next day, or losing a contract with assurion due bricked device insurance claims from users who followed someone's individual experience too closely and ended up with a different dynamic in their situation.) Who would get blamed? op. Doxed and bullied? op. The innocent person who wrote their guide to share the discovery. It was once assumed that same model meant same rooting process. That can never be true due to vendor overlays and carrier specific software, migration of user data, and kernels from last device etc... See where that could cause a problem? I help you, and within 24 hours your phone bricks for any number of weird bugs, now you're stuck with a paperweight or have to pay for someone to repair, who gets blamed? op. WHEN or if you brick (EVERYONE BRICKS THEIR PHONE SOMETIME OR ANOTHER EVEN THE DEVS. I JUST UNBRICKED MY PHONE FOR THE THIRD TIME IN A MONTH MY SELF, JUST PART OF THE TERRITORY) Ill help you, but objectively speaking I need to see effort being given from the requestors side or a cash app transaction. This is by no means directed specifically to you, but to all the future leeches who may read this, and stop themselves in their tracks. I need a person to show me that my help is not given in vain. (Nobody wants to feel their rooting badge snatches away from them by some 17 year old kid who is lethargic and wants 3 or four board members doing all the work for them. It's a slippery slope and we are, at best, in the morally grey area (well most of us.) If I help you, and your device bricks, you will have to begin the harder part of this journey alone for a while, I won't be here for a hot minute. You should expect to brick at least once. If you are not prepared to handle that level of adversity then I cannot help you, nor am I good at data logistics, I just utilized a piece of this guide and that, made a couple phonecalls referencing where I could locate paperback documentation, and ive bricked sooooo many phones... Insurance doesn't wanna hear it anymore. I won't be able to help immediately. Boot.img and 'fastboot getvar all' maybe when I come back from vacation I'll help you further, and its a guarantee someone else will assist you. sorry for the rant.

I don't want to keep teaching fastboot and driver lessons. In this part of this thread the user should be at least eye level on the basics .