Are you using adb sideload option in twrp for flashing purposes? Because if password-protected it won't decrypt.I'm actually on Android 12 now TWRP working perfectly through magisk. Everything working good on Android 12. I was able to flash what I needed to flash without any issues. So if anybody's having trouble with the black screen when you try to boot into it via fastboot, just install it with magisk as mentioned above in some of the comments works perfect
It works perfect for me password and everything just flash it with magic flash the installer with magic and that's it boot into recovery you don't need a PC I flashed my zip files directly after I enter my password that's the only way it would work booting it through fast boot gave me the black screen this was the only thing that worked for me
Thanks for the answer. Last time when i was in android 12 i did the same as you did. Twrp booted fine but i couldn't decrypt with my pattern. Later i downgraded and now i am on android 11. I really missed gravity box in a12 haha.It works perfect for me password and everything just flash it with magic flash the installer with magic and that's it boot into recovery you don't need a PC I flashed my zip files directly after I enter my password that's the only way it would work booting it through fast boot gave me the black screen this was the only thing that worked for me
It wont flash that way. Flash TWRP using Magisk from inside Android OS.I am running on Android 12 Version WW-31.0810.1226.77 with root access gained from patching the boot.img with Magisk version 24.3. Similar to # 153, I could not get booted into TWRP 3.6.1. I saw a black screen and then got booted into Andriod 12 operating system as normal after executing the command "fastboot boot twrp.img".
Thanks. I will wait for an official release that supports Android 12 and hope that it will not take long.
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
You should now be in fastboot mode.Code:
adb reboot bootloader
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot boot twrp.img
Now you are booted into TWRP, but it is NOT permanently installed. To install it permanently, use the "Flash current TWRP" option in the Advanced menu. This will install the currently booted TWRP permanently to both slots. NOTE: If you were previously rooted, you will need to re-install the root apk/zip as the TWRP install will overwrite it!
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!