Develop Bugs

Possible to restore recovery and re-lock bootloader without data lost

So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.

DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
You need to have usb debugging enabled in your phone and adb tools installed in your pc before you do this.
For locking bootloader :
Connect the phone to computer,
Restart the phone in bootloader mode
Open command prompt window
Check connection by typing fastboot devices . You should see your device listed
Type fastboot oem lock
Reboot once the process completes. Be aware this will wipe your phone and ALL data will be lost.
It is advisable to keep boot loader unlocked.
For stock recovery :
Download stock recovery image from the forum
Save it in the same folder where your adb is installed in windows. The file name should be recovery.img
Reboot into bootloader mode
Open command prompt and
Type fastboot flash recovery recovery.img
Stock recovery to be installed before you lock bootloader

DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.

theduke7 said:
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.
Click to expand...
Click to collapse
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.

DrUnknownEMC said:
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.
Click to expand...
Click to collapse
A new recovery does not wipe your phone.
There is no patch to remove the boot warning. The only way is to lock boot loader <- this will wipe your phone and data.
If your phone runs well, it is better you keep it as it is. Why fix something that's not broken ?

Magisk Issues on Fresh System Image Install (Feb. 2019)

I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.

clambert11 said:
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.
Click to expand...
Click to collapse
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!

sb1893 said:
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!
Click to expand...
Click to collapse
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.

clambert11 said:
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.
Click to expand...
Click to collapse
If your platform-tools are r28.0.1
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- install ElementalX kernel
- tap Add more zips
- select Magisk-18.1.zip
- swipe slider to install
- reboot

Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!

clambert11 said:
Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!
Click to expand...
Click to collapse

I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?

Ivanstein said:
I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?
Click to expand...
Click to collapse
Forget side loading!
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- tap install select Twrp-3.2.3-1.zip
- swipe slider to install
- reboot recovery
- tap install select Magisk-18.1.zip
- swipe slider to install
- reboot

Pixel 3a XL soft #BRICK - please help

On my way to installing LineageOS I tried to downgrade Android version 11 -> 10. Unfortunately I used the WRONG INCOMPATIBLE firmware files from google's website (I think for 3 XL), that's why I have a brick now. ''Device is corrupt and no bootup possible.''
Access to Fastboot and STOCK Recovery Mode is possible.
Bootloader is Locked Now (it *was* unlocked before for flashing the firmware)
ADB is not working (since I'm getting stuck on ''google'' symbol when booting up I can't go to Developer Settings)
Factory Preset from Recovery Mode fails: ''can't send spi messages.'' Same Brick occurs.
With No Access to ADB (is it possible to set up from fastboot mode without enabling it in den Developer Options?) I can't try stuff.
And with the bootloader locked no way to flash a new Rom right?
I have NO IDEA what to do next, any IDEAS??
Thank you!!
#brick

Since you can get to recovery you should download the latest ota and sideload it from recovery.

https://developers.google.com/android/images
you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"

41rw4lk said:
Since you can get to recovery you should download the latest ota and sideload it from recovery.
Click to expand...
Click to collapse
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
You need the BL unlocked to flash unsigned/unofficial images, so make sure yours is unlocked. That being said, I'm not sure how solid twrp is for our device, I've never tried it. Twrp was/is a little iffy for android 10 never mind 11. Most around here just use fastboot to do what needs to be done. Most of it is pretty quick and painless, and twrp is not really necessary.

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.

teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!

dadu1257 said:
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
Click to expand...
Click to collapse
Cool. No more soft brick for you :good: Congrats on sorting things out. :highfive:

BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse

dadu1257 said:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
Click to expand...
Click to collapse
Twrp doesn't work very well on android 10 and above, there is a twrp install guide around here, but not much has come from it. When was the last time anyone actually made and used a nandroid backup? Not that backups aren't important, but that's a little antiquated. Besides, most are really trying to backup data, which is a shared partition on A/B devices. Generally, restoring data on A/B devices causes more problems than anything. Most data backups can be done with an app and/or making a backup of your internal storage. As for more sensitive things like your persist partition and whatnot, you can always use the 'dd' command to back those partitions up.
I should clarify, restoring nand backups of data causes more problems on A/B devices, apps that restore data and settings tend to handle it better.

Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''

dadu1257 said:
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.

41rw4lk said:
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
Click to expand...
Click to collapse
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.

dadu1257 said:
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
Click to expand...
Click to collapse
A lot of devs wil upload the boot.img separately when they upload the rom, so wherever you downloaded Los from check there. If you just have a payload.bin file in your zip, you can always dump it and grab the boot.img there. You could always just reflash Los period to get boot back, then us 'dd' command to backup your own boot.img.

custom recovery for lineageos 17 based on android 10?
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
thanks!
I got Lineage 17 w/ Magisk root running now and want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for.
thank you for help!

Moto G7 play (XT1952-1) - please help with TWRP install ....

Hi, I got myself an used Motorola Moto G7 play (XT1952-1) with Android 10 Stock update (Build QPYS30.52-22-8-9) and just can't successfully install TWRP on it. What I did:
- Bootloader unlocked
- TWRP temporary loaded with fastboot (fastboot boot twrp.img)
- In TWRP 'Iinstall' selected the matching TWRP .zip and it said it was installed in both slots a and b.
But then, when I select 'restart to bootloader' and try to launch recovery, I get a bootloop (black screen with (N/A) in the top left corner. The OS as such still starts normally. So I guess the main problem here is the bootloop when trying to launch recovery...?
I tried installing over booted TWRP with unmodified boot.img and with Magisk patched boot.img, same result. The G7 play does not have a separate revovery partition, recovery is included in the boot.img
I used the TWRP files (EU) and instructions from here:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
My stock firmware is XT1952-1_CHANNEL_RETEU_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Am I missing something? I've now searched for days (most info is outdated, taken from other places/Motorola phones with just 'G7 play' added, or is ambiguous); so can anyone *PLEASE* help me? Does anyone have a G7 play of the same type with Android 10 Stock who has successfully installed TWRP and was able to access the Recovery afterward without being stuck in a loop?
I also can't create a TWRP backup with a fastboot booted TWRP because system (and internal SD too) seems to be encrypted, and I don't seem to be able to deactivate this in the phone. Is this normal? Some places say that TWRP can decrypt when it's installed permanently...
Or could anybody patch the boot.img in above Firmware and add TWRP for me so I can just flash the boot.img?
Thanks in advance... please reply noob-friendly.

Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed. I followed your links to get boot.img + twrp.img.
NO MAGISK INSTALLED!!!​Please patch before flashing if Magisk is already installed.
I put a log of the repack command into the zip that is showing the checksums of the boot header. Just to have a proof.

WoKoschekk said:
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed.
Click to expand...
Click to collapse
Thanks for trying to help, but this boot.img behaves exactly like the one I made by following the installation instructions on the TWRP website. I flashed it, restarted bootloader, then tried to go into recovery, and it bootloops (black screen with N/A in the top left corner).
But what I need is a boot.img with a WORKING TWRP recovery (that can actually be launched when recovery is selected...
Any idea why this won't work, why TWRP won't start?

@Alonso_Quixana Try the attached one. It's a boot.img patched with twrp + recovery_dtbo. The recovery_dtbo is part of the twrp.img but TWRP's installer.zip doesn't take it into account while repacking the patched boot.img. Maybe (hopefully!) that's the reason why you're able to boot TWRP but not to install it permanently.

Please try also - in any case! - the patched installer.zip that comes with a recovery_dtbo.

Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app

chuy19312 said:
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
Click to expand...
Click to collapse
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?

Alonso_Quixana said:
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
It's a 32bit system on a 64bit CPU (Snapdragon 632). That's not unusual for Motorola devices. Open a terminal app and execute uname -a.

Alonso_Quixana said:
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
I think it only works on certain Moto G7 Play variations or even only on Android 9, also, another way to install TWRP is installing an Custom ROM then flashing an flashable zip of TWRP_11 by SyberHexen on Custom ROM's Recovery
Link to TWRP_11 Flashable Zip
channel-twrp-installer-3.6.2_11.0_RC-1.0.zip | by SyberHexen for Moto G7 Play
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
In my case, flashing TWRP, even by following some tutorials made my MetroPCS Moto G7 Play to stop booting and also, VoLTE stopped working, fortunately, i had an EFS backup to restore my IMEI
Android 10 Stock Rom is an Arm (32 bits) ROM, every Custom ROM i tested are Arm64, but i don't recommend any of them since you will get constant app rebooting and notification problems since this is an 2 GB RAM device

Question TWRP causes fastboot loop

After installing TWRP following their "Preferred Installation Method" on https://twrp.me/oneplus/oneplus9pro.html.
However, after doing this, my device will only boot into fastboot mode. What's the fix to this?
I'm not worried, I have my boot.img backed up, and I can just flash it back, and it's fixed, but then recovery is back to regular OnePlus.
What am I doing wrong?
Go into fastboot > boot into TWRP > Flash Current TWRP > Reboot
And I'll be in a fastboot loop, I did also try wiping Cache&Dalvik after but that also didn't fix it.
What am I missing?
Thanks in advance.

0xZ3ph said:
After installing TWRP following their "Preferred Installation Method" on https://twrp.me/oneplus/oneplus9pro.html.
However, after doing this, my device will only boot into fastboot mode. What's the fix to this?
I'm not worried, I have my boot.img backed up, and I can just flash it back, and it's fixed, but then recovery is back to regular OnePlus.
What am I doing wrong?
Go into fastboot > boot into TWRP > Flash Current TWRP > Reboot
And I'll be in a fastboot loop, I did also try wiping Cache&Dalvik after but that also didn't fix it.
What am I missing?
Thanks in advance.
Click to expand...
Click to collapse
Wrong TWRP... Check this thread if on A13
[RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com

TheGhost1951 said:
Wrong TWRP... Check this thread if on A13
[RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
Click to expand...
Click to collapse
I feel stupid now... Been a while since I needed TWRP. Thank you Ghost