Database Info

I'm really stuck getting recovery installed - please help?

Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch - don't get the 'amber LED' which various guides tell me to press Vol Down at.
I'm using
Code:
fastboot boot recovery.img
to boot the phone into recovery and
Code:
fastboot flash recovery recovery.img
to flash it, which hasn't worked at all. All of theTWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys

[snip]

TimTams said:
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch. I'm using
Code:
fastboot flash boot boot.img
to write the boot images and
Code:
fastboot boot recovery.img
to boot the phone into recovery. All of the other TWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
Click to expand...
Click to collapse
I don't think your bootloader is unlocked because:
1: your device won't boot after flashing an image.
2: your rooting status says: bootloader unlock allowed.
(if unlocked, it says rooting status: bootloader unlocked)
Yes means it can be unlocked.
Unless you unlocked already and use drm fix because then it still shows yes but Im pretty sure your bootloader isn't unlocked.
BTW this thread belongs in Q&A section.
You can request a movement by hitting the small "!" triangle button underneath your post when viewing this page in a browser.
Sent from my E6653 using XDA-Developers mobile app

Thanks heaps - that sounds like it might be the issue, I'll have a play and post back here. It would explain why I've had so much trouble with what seems like a simple task
langeveld024 said:
I don't think your bootloader is unlocked
...
Click to expand...
Click to collapse
EDIT:
It looks like this was done correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure I want to go and have another crack at flashing a recovery... I couldn't seem to get any of them to work.

I've just followed this guide to installing recovery and it hasn't worked... I still just get stuck at the sony logo. Any ideas why? How do I know the recovery image linked is correct for my phone?
http://www.digitbin.com/unlock-bootloader-flash-twrp-root-sony-xperia-z5/

OK, I got recovery installed! Thanks to this guy: http://forum.xda-developers.com/xperia-z5/help/boot-flashmode-fastboot-t3457818
mentions what no other guide mentions...
I need to have a custom kernel before I can flash recovery (first mention of this I've seen)
The kernel I flash needs to match the firmware I have installed
With that, I had instant success.
EDIT:
And now I have managed to get a custom ROM installed at last My procedure was, for anyone that be stuck in a similar way:
If your phone already won't boot:
Download Flashtool and install it. I have mirrored it here as all the sources I found were very slow: http://noobs.wtf/uploads/flashtool-0.9.22.3-windows.exe
Go to the 'drivers' folder inside your Flashtool install directory (default C:\Flashtool\drivers) and follow the instructions to install the "flashmode" driver
Select XperiFirm within Flashtool and download the correct firmware for your phone - mine was "Xperia Z5 > Sumire > E6653 > Australia > Telstra AU > 32.2.A.0.253 / R5C"
Turn off your phone and boot it in flashmode - Insert USB while holding vol down until the LED is green
Once Flashtool has finished downloading your firmware, go back to the main screen and click the 'lightning' button to flash your phone with the new firmware that should show up in the list - leave all the options unticked. Wait for it to say 'complete - un plug your phone'
Your phone should now boot successfully
To install a custom ROM:
I was not able to access my SD card in any version of TWRP - so copy your ROM to the internal storage of your phone. I used v1.5.0 of THIS ROM successfully.
Copy v36 (or newer) of THIS KERNEL .zip file to your internal storage as well. (v32 and higher are in the google docs link) NOTE this must match the firmware version - v36 was the one I used because, as above, I re-flashed my phone with 32.2.A.0.253 from Flashtool. The appropriate versions are listed on that link
[*]Also download TWP-3.0.2-2-E6653.img (or newer equivalent) from that same link.
[*]Follow the instructions HERE to unlock your bootloader (and make sure your fastboot drivers are installed correctly)
[*]Reboot your phone and re-enter fastboot mode (vol-up while plugging in USB) you can issue the command 'fastboot oem unlock' and it will return 'already rooted' if it has been done correctly
[*]Now with your phone in fastboot mode, issue the commands "fastboot flash recovery TWP-3.0.2-2-E6653.img" then "fastboot boot TWP-3.0.2-2-E6653.img" to install and then boot into TWRP recovery
[*]Once in TWRP, go to "Install" and install first the Kernel, then install the ROM, making sure to do the wipes
For me, this completed the process of installing a custom ROM I was stuck on the lack of info around installing the kernal and whatnot.

TimTams said:
I was stuck on the lack of info around installing the kernal and whatnot.
Click to expand...
Click to collapse
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app

langeveld024 said:
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.

TimTams said:
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
Click to expand...
Click to collapse
Hmm maybe u should suggest the OP of those threads to add this information then.
I personally never read those guides lol[emoji14](not anymore at least, at some point I was learning about this like you as well, we all had to learn)
Sent from my E6653 using XDA-Developers mobile app

[SOLVED] Mi A1 BOOTLOOP

THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:

Thanks
---------- Post added at 08:37 PM ---------- Previous post was at 08:19 PM ----------
a question only with that ROM or can I download the latest stock ROM

Dualitydark said:
a question only with that ROM or can I download the latest stock ROM
Click to expand...
Click to collapse
Only with that ROM bro, because the EFS file was backed up from that ROM

I just created this account to say thank you for this solution.
My MI A1 got bricked/in bootloop after the newest update.
I couldn't flash it via MiFlash with a simple stock ROM, I needed to unlock it via the unlocker app of that MIUI thing.
With flashing successfully after, I got the same old bootloop screen.
Then I ran through the steps up until 8.
After that, I rebooted, and the phone started up normally.
So in case people managed to flash their device and do your method, there's no need to flash it again and for TWRP 3.3.1 to solve bootloop issue.
At least for me it wasn't needed.
Once again, thank you very much!!! :good::good::good:

Fantastic. Thanks friend.

My phone just got in to boot loop when I tried to reboot from magisk app. I successfully flashed stock firmware from miflash tool but still stuck on boot loop.
(my phone is bootloader unlocked)

alkoka said:
I just created this account to say thank you for this solution.
My MI A1 got bricked/in bootloop after the newest update.
I couldn't flash it via MiFlash with a simple stock ROM, I needed to unlock it via the unlocker app of that MIUI thing.
With flashing successfully after, I got the same old bootloop screen.
Then I ran through the steps up until 8.
After that, I rebooted, and the phone started up normally.
So in case people managed to flash their device and do your method, there's no need to flash it again and for TWRP 3.3.1 to solve bootloop issue.
At least for me it wasn't needed.
Once again, thank you very much!!! :good::good::good:
Click to expand...
Click to collapse
Me too! Infact, I tried to flash pixel experience and phone was stuck in bootloop, thanks to this guide I was able to make phone working again!
You are a true hero, thank you so much!

it is showing waiting for device

Hi all,
Just sharing my experience. I own two Mi A1 phones (I just love this model and I thought I'd get a spare)
On my first Phone, I got involutarily upgraded to Pie and it wass hell to get it back. I followed a guide here and flashed someone else's EFS partition. That feels dirty to me so I decided to do things properly with my spare phone.
Here's what I did:
- Booted into the OS the phone shipped with (Nougat, good times!)
- Unlocked bootloader and booted into TWRP
- Did a FULL BACKUP. This is what I didn't do with my first one! It's CRUCIAL that you back up your phone first thing when you get it. Don't even connect to wifi, just unlock the bootloader and back it up with TWRP! IF you don't, you will NEVER be able to get back to how things truly were out of the factory. Of course you need to copy the backup to your PC for safe keeping.
- Now I went my merry way installing Lineage os, eventaully upgrading to Pixel Experience (Android 10, which turns out I hate).
- I wanted to get back to stock rom. So I booted into TWRP and did a full restore.
- Unfortunately, It boot looped.
- Flashed EFS and Boot again (from my backup). No luck, no effect.
- Flashed a stock Oreo image (V9.6.8.0.ODHMIFE) using Mi flash Tool and the "clean all and lock" option (I regretted doing this because I realized I wasn't sure if I'd be able to get fastboot again after oem lock, but it turned out fine)
- After flashing it, It was still boot looping! Panic.
- Tried booting into fastboot and succeeded (yay)
- Did a fastboot oem unlock and luckily The bootloader got unlocked no problem.
- Phone finally booted! Hooray.
Just putting this in writing for future reference in case anyone is wondering about the steps to take.

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
OP, all the links are expired ....What do?

my tissot Bootloop android one logo restart
tissot my bootloop. until androidone logo restarts.
can't flash with stock rom.
I've tried flash with miflash.
both edl mode and testpoint flash are successful but still the same.
but I can install twrp and custom rom, no problem.
i just wanna go back to stockrom
if there are friends here who can provide a solution.
thank you
sorry bad english

Hello everyone.
I am asking for your help.
I tried to follow the procedure described step by step until the end.
But the device keeps rebooting in a loop.
It boots up correctly, I can perform a few steps of the initial configuration and then it reboots.
What else can I try to do?
I don't have backups of my device.
Thanks in advance.

surferstory81 said:
Hello everyone.
I am asking for your help.
I tried to follow the procedure described step by step until the end.
But the device keeps rebooting in a loop.
It boots up correctly, I can perform a few steps of the initial configuration and then it reboots.
What else can I try to do?
I don't have backups of my device.
Thanks in advance.
Click to expand...
Click to collapse
[FASTBOOT][OTA] Xiaomi Mi A1 OTA & FASTBOOT Images
I just find and collect all available OTA and Fastboot links for Xiaomi Mi A1 How to extract OTA link: https://forum.xda-developers.com/showpost.php?p=74828109&postcount=2 Tool to unpack OTA images...
forum.xda-developers.com

GOD BLESS YOU

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
Sorry but I have a question
I didn't take a backup from my twrp and now I can't do anything
I just wanna ask that rom you uploaded here is custom rom? I mean I should install it with TWRP or I have to install this rom with mi Falsh tool ?
And what do you mean to flash TWRP ?
We didn't do that at first ?
I'm confused

Hey bro i really breaked my phone
I forgot to flash twrp at the end and my phone only vibrate after flashing
Plz help me

you're my hero man...
solved my problem so far...
now i can flash custom rom again....

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
Kindly explain process 9 in details. I don't know how to flash.

Get this error.
My phone is stuck in bootloop and cannot unlock bootloader.
Anyone have a solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have flash stock from via Testpoint but when I boot into TWRP my touch screen is reversed. How can I fix it?

[RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 3

Code:
*** 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!
Introduction
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 feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
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:
Code:
adb reboot bootloader
You should now be in fastboot mode.
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:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse

Frequently Asked Questions (FAQ)
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP zip from twrp.me
Magisk app
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install TWRP zip in Magisk app
Install Magisk "to Inactive Slot (After OTA)" in Magisk app
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites (for stock images, see attachments to post #3):
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip. Make a note of the slot to which the zip is installing (you will need this after the next step).
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
Open the Reboot menu in TWRP and switch to the slot to which the zip installed from step 4. Reboot to system now, or go to the next step.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse

Stock Boot/DTBO/Recovery Images

Keep up the good work m8 @Captain_Throwback :highfive:

Great job!

Reserved

sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?

Woohoo! Excellent!
Sent from my ASUS_I003D using Tapatalk

about twrp
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.

chacho_2me said:
sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?
Click to expand...
Click to collapse
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.

Captain_Throwback said:
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
Click to expand...
Click to collapse
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now

Monsibd said:
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Click to expand...
Click to collapse
Where is the recovery log from the TWRP boot where it was prompting for password? The OP clearly states that a log should be included with any issues. Do me a favor and try flashing the TWRP attached and let me know if it boots.
https://drive.google.com/file/d/1-2qBUqYv0AWnvqDmxIY2DqRqwG5dSwHg/view?usp=drivesdk
If it does, I can adjust the TWRP image linked in the OP. If it doesn't, I'll definitely need a log to understand the issue, and your device details.

So I did some testing, and it appears that if you're not on the latest .58 firmware, then TWRP may not boot successfully. Can anyone that has had an issue with booting TWRP please report their device variant and firmware version? If you're not on the latest, please update and then try TWRP.
WW 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/...US_I003_1-ASUS-17.0823.2007.58-1.1.9-user.zip
CN 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS661KS/UL-ASUS_I003_1-CN-17.0823.2007.58-1.1.45-user.zip
If that doesn't work, let me know.
EDIT: Actually I need to check again. I think I broke my TWRP tree so it may not be the kernel at all :/

Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?

Captain_Throwback said:
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
Click to expand...
Click to collapse
so basically installing twrp can still be overwritten when flashing original firmware from asus
.thanx sir

Monsibd said:
Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
Click to expand...
Click to collapse
So maybe there is some difference with the CN device that's causing this issue. Everyone it's working for is running WW firmware. Not sure what's different with the CN firmware, but that's unsettling.
Since the full firmware file is available, you can just use payload dumper to get the stock recovery image.
And yes, a clean flash with logs would be great, thanks!

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
same as you im on the latest ww firmware tencent games variant and rooted

bouyhy01 said:
same as you im on the latest ww firmware tencent games variant and rooted
Click to expand...
Click to collapse
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.

Captain_Throwback said:
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.
Click to expand...
Click to collapse
thank you very much captain i'll be waiting for it to test

How To Guide Global/US unbricking guide.

Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.

Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp

akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!

I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?

panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way

@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks

winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!

I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??

from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!

panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help

iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp

winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me

the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.

i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons

papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!

allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx

iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?

OnePlus 8t KB2001 stuck in a loop

I shifted from apple to android recently and I decided to root my device OnePlus 8t KB2001 (I believe I have Android 12) as I wanted to install kali on it. Therefore I decided to follow instructions on this website. I did not type the steps because I did not want to lose out on any key details.
I performed all the steps till here:
I did not perform step 6, instead, I performed step 7 as I wanted to install TWRP Recovery on my phone permanently.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to the instructions I was supposed to boot my device to TWRP. Since I am currently booted to Fastboot, I used the Volume Keys to bring up the Recovery option and hit the Power key to confirm the decision.
As per the instruction as soon as my OnePlus boots to TWRP, it will ask to decrypt data. I was supposed to simply enter my phone’s password/PIN to proceed ahead but this never happened. Instead, I am stuck in a situation where I am seeing the following screen:
I searched every single option and there's no Online Update (keep data) option. I am stuck in this loop for hours. Even the option of formatting data doesn't remove this RECOVERY.
I don't know if this information would help but I can enter the Fastboot Mode by tapping on "Advanced" and selecting "Reboot to fastboot mode".
It would be really helpful if someone can tell me a fix to this problem as I really don't want to throw this phone away as I just got it today.

You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.

I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.

TheNewHEROBRINE said:
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
Click to expand...
Click to collapse
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?

FakeGemstone said:
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
Click to expand...
Click to collapse
Thank you, this really gives me hope that my money will not go to waste. Now I am just in the process of trying to find a solution where I can my make phone the way it was which is without having any TWRP

kooluser said:
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
Click to expand...
Click to collapse
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanism too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.

TheNewHEROBRINE said:
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanisms too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device

kooluser said:
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
Click to expand...
Click to collapse
I'm happy for you too

TheNewHEROBRINE said:
I'm happy for you too
Click to expand...
Click to collapse
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it

Did you flash TWRP after switching slot? If so you should be able to boot into it by holding power and volume down while turning the phone on.

Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?

kooluser said:
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
Click to expand...
Click to collapse
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.

TheNewHEROBRINE said:
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
Click to expand...
Click to collapse
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone

kooluser said:
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
Click to expand...
Click to collapse
It's not a problem to have TWRP installed.

TheNewHEROBRINE said:
It's not a problem to have TWRP installed.
Click to expand...
Click to collapse
Thank you so much for helping me and solving all my queries

kooluser said:
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Click to expand...
Click to collapse
You can install magisk from TWRP recovery.
Changing slots is also possible there.