Post is pinned.Post has attachment
Requesting TWRP for unsupported devices

There seems to be a lot of misunderstanding about what devices we support and why we choose to support certain devices over others. Official support for a device usually comes about in one of two ways:
1) We somehow get our hands on the device either through someone or a company donating the device to us or occasionally we save up enough money to purchase a device ourselves.
2) Another developer who actually owns the device steps up and ports TWRP to their device, then they work with us to get their device added to our official distribution.

Occasionally there's a third method where we work with a remote tester who owns the device to get the device working in TWRP. This third method is not used very often because most remote testers are a waste of time. Remote testers often need tons of hand holding and line-by-line directions. Remote testers often fail to know how to get things like adb and fastboot working. Remote testers often fail to make themselves available when we need them and they disappear before we're able to finish verifying a completely working build. At this point, we usually only work with remote testers that we already know and have a relationship with so that we can ensure that we're not wasting our valuable time working with someone who doesn't know what they're doing and will disappear before the job is done.

Sure, you can offer files and to be a tester and offer to provide everything we need, but most likely you'll be ignored because we simply don't have the time.

You can compile TWRP yourself by following this guide:
http://forum.xda-developers.com/showthread.php?t=1943625
To put it short, you will need:
-A Linux environment, either virtual or native
-A full Omni build tree, about a 15 or 20GB download
-A copy of the stock recovery and/or kernel source for your device
-A basic knowledge of adb, fastboot, Linux command line, make files, and strong ability to figure things out on your own via searching on Google

If none of the above works for you, feel free to donate the cash or ship us your device and we'll try to work on it when we get a chance.ο»Ώ
Commenting is disabled for this post.

In mount section Vendor partition is not displaying in twrp on my Moto g3 plz solve for it I want to install android pie

Please help us laymen to root our Oppo F7.
We do not know how to port.
TWRP has doled out custom recoveries for other Oppo phones, so I am sure they can easily port it in a jiffy.
I refuse to believe that none of the developers can get their hands on what is one the fastest selling brands.
No offense meant to anyone who felt hurt reading this post.
😁

Galaxy S6 - 920F, latest version TWRP (3.2.2....) Does not seem to recognize, nor be able to mount, USB storage. Sees but reports no space available. Suggestions? Can sort of work around it by using internal storage and transferring backup files via adb but hopefully there is a more elegant solution that eludes me.

Hey what Version do i use for LGG5 LS992?
Is it International or the rs988 one?

I have an Alcatel pop c7 that is rooted but I do not have access to a computer for the time being' is there anyway to unlock the boot loader with out a PC? And when I check availability for my device all I find on the list is the pop c3, is my device company table?

Can someone please tell me how to give an application Root permissions I would be very grateful thank you

I was at TWRP 3.2.1-0. I downloaded TWRP 3.2.3-0 and flashed the image to recovery. rebooted and everything was fine. I booted to system and booted to twrp without any problems (or so i thought). After booting into TWRP I was asked to enter my pin to handle the decryption. No matter how many times i entered the PIN it flagged it as incorrect and could not decrypt my phone. What can i do to recover from this situation? If anything.

Pulling my hair out a little bit here......

I rooted a pixel xl about a week ago on 8.1 and everything went fine according to the guide on XDA. Then I ended up with another Pixel XL, so I tried rooting it on an 8.1 image that I flashed over. It bootlooped. So then I took it step by step and found that when I installed TWRP it would just boot straight into recovery no matter what I tried. Of course flashing the boot.img from the stock rom cured this, but no matter what I tried it wouldn't work. So then I tried Android P. Same deal there. It doesn't matter if the pin is set or not. Nor does it matter what version I try. I did try the last two versions because the previous to newest worked fine before on the old Pixel.

I tried both slots (it flipped slots on the OTA update to 9) and also tried reflashing 9 manually a few times. I would go back to 8.1 and try again, but after at least 3 tries I'm pretty sure I'm going to have the same problem. The phone boots and runs stock android perfectly fine. I have like 5 or 6 hours into this trying different things and nothing really works. Nor does anyone seem to have my specific problem that I can find.

Would anyone have any kind of idea of what's going on here? I need to root this phone for several reasons so not having root isn't really an option right now.

Hey guys. I had 3.2.1-0 on my Asus Tf300T. I downloaded 3.2.3-0 from the official app and flashed it to recovery. It succeeded, I rebooted to recovery and it wasn't updated. So I tried to flash the img file from within TWRP itself, which also said it succeeded but now I can't get into my recovery. When I load into the bootloader and choose recovery, it says unrecoverable recovery.
Wait while more posts are being loaded