Database Info

[Guide] Installing Blu_spark TWRP | Magisk 20.1 On Stable Oxygen OS 10

Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
 @eng.stk for the Blu_Spark TWRP
 @mauronofrio for the initial TWRP Image
 @Akhil701 for the stock boot.img
 @remewer for inspiration to build this guide.​

Patched boot.img or why we need the boot image after flashing OOS10 via local update?

Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide

Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.

no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system

I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching

Functionally on OOS 10.0.1 OP6 ?

So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.

Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand

magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.

Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?

WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works

After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine

Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail

As above. No wifi, no sound. What's going on?

Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...

ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.

Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?

dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.​
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!

loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes

[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

Android 11 Open beta Stuck on Fastboot Mode While Rooting

Hi Everyone
I was rooting My op7 pro after updating to open beta android 11. While i was booting twrp it shows Fastboot Mode screen And stuck on that
Hope i ll find possible solution from the community
Regards
ali_hamza

I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.

benjaminries said:
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
Click to expand...
Click to collapse
You should just be able to run direct install after you boot to A11 with the patched boot image.

Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.

calripkenturner said:
You should just be able to run direct install after you boot to A11 with the patched boot image.
Click to expand...
Click to collapse
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?

benjaminries said:
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
Click to expand...
Click to collapse
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.

calripkenturner said:
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
Click to expand...
Click to collapse
Got it. Yeah my Magisk Manager was still installed from previous beta, but it took away the "direct install" option when I lost root from flashing the unpatched boot.img. Personally I would always rather patch my own boot.img file than rely on something from a filesharing service, especially when trying to get out of brick...
But I can see how until proper TWRP support comes, we can just use Magisk to patch alternate boot slot before rebooting but immediately after flashing the latest OOS beta using the regular system update process. Hindsight...

benjaminries said:
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
Click to expand...
Click to collapse
need to use orangfox recovery

esi2121 said:
need to use orangfox recovery
Click to expand...
Click to collapse
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?

benjaminries said:
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
Click to expand...
Click to collapse
Check the orangefox ,it's only recovery support a11 for now

esi2121 said:
Check the orangefox ,it's only recovery support a11 for now
Click to expand...
Click to collapse
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.

Yesterday i download and tried to flash Pitch Black Recovery Project but results were same.
I think there should be some changes regarding A11 in any recovery so the best is that we should wait for their( Devs) further response

benjaminries said:
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Click to expand...
Click to collapse
yup thats it , but in orangefox git said official support A11

esi2121 said:
yup thats it , but in orangefox git said official support A11
Click to expand...
Click to collapse
Check out this (now locked) thread though: it seems like there's no working port of OrangeFox for guacamole that supports OOS11 yet... lots of people bricking and boot-looping on the hope that there might have been!
[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1] | XDA Developers Forums (xda-developers.com)

Can't Boot to twrp recovery (just displying twrp logo)

Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.

Enossob said:
Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.
Click to expand...
Click to collapse
Which android version are you? 9 10 11?

1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer

@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.

Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
Glad it worked out for you

Noob9496 said:
1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer
Click to expand...
Click to collapse
Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?

tenderloin83 said:
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?
Click to expand...
Click to collapse
Yeah, everything

Enossob said:
Yeah, everything
Click to expand...
Click to collapse
Is there another way to restore twrp?

I don't use twrp anymore. Attached is Magisk patched boot for OP6 11.1.2.2 I patched from the latest payload.
fastboot flash boot_a magisk_patched-23000_OP6_11.1.2.2.img
fastboot flash boot_b magisk_patched-23000_OP6_11.1.2.2.img

tenderloin83 said:
Is there another way to restore twrp?
Click to expand...
Click to collapse
Install the twrp installer directly from magisk

What I did was trying to install Lineage OS 18.1 (the latest nightly from Jan 11 2022) with Lineage OS Recovery. Following the official wiki I always got stuck in the lineage os boot animation. Never got past that. Tried to fastboot boot twrp.img but TWRP stuck on logo. I think I never tried to boot twrp with the userdata erased. I think I will try it.

Anyone trying to install the twrp, check out SHRP recovery for OP6/t. Boot the img and flash the zip from that thread. tested works with both OP6 and OP6t in OOS 11.1.2.2.

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.