Database Info

OnePlus one does not go into recovery after updating it

Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.

Molex69 said:
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Click to expand...
Click to collapse
I guess you didn't read the OP of Oxygen Os correctly,he clearly mentioned that this 'Tuga Power Recovery' is patched to work with Oxygen Os's firmware and one should not flash any other recovery.Now,what you can do is this,
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view?usp=drive_web
> Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Avoid using any Antivirus program while doing this as they might give false alarms.After this you'll be restored to TWRP then you can flash any rom you want.The reason due to which you weren't able to find 'TugaPower Recovery' on TWRP page is because this is an Unofficial Recovery.

Question
What does the program do with the OPO?

If you are familiar with fastboot commands, this method should work. Had my OnePlus in the same situation last night messing around with Efidroid. Phone was bootlooping. Efidroid boot menu as well as recovery mode were both inaccessible. I had tried several other things but none worked for me. *CAUTION: this method did ERASE my userdata.* I downloaded a fastboot-able stock full firmware zip, then manually reflashed device. My beloved OnePlus is no longer my daily driver but still my fave device to experiment with so I just used COS 13.1 file. After full reboot, I downloaded and flashed official TWRP. Device is fully functional again, but without OOS installed.

Molex69 said:
What does the program do with the OPO?
Click to expand...
Click to collapse
It'll change your firmware and alter your recovery to a functional TWRP.You'll lose Oxygen Os after doing this.Though you can use this anytime when not being able to flash TWRP.

What should i do
Thanks a lot thanks to the method you told me my OPO has recovery again really thanks, but I have a question, I still in the TugaPower recovery, should I flash the stock recovery or the newest version of TWRP?
Because I do not know if flashing again the TWRP will happen the same

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Fastboot Bootloop

I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.

Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.

Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....

mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq

OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help

Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.

Help access internal storage from fastboot

So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.

I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.

To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.

Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.

I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"

a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.

cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.

DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com

DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking

DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.