Database Info

Magisk Root without TWRP for OnePlus 6 Oxygen OS Android 10 Open Beta 5 | OOS 10.3.1

Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.

wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！

Not work here. Bootloop, only see Bootanimation not more.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.

It works for me. That's a great help. Thank you.

SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.

Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.

Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.

geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.

Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.

geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.

What about safety net?

G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first

toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.

MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P

Download link updated with Beta 1 patched image.

Installing OTA after TWRP + Magisk = fail to boot

I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?

These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot

RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?

Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.

whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!

Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.

Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".

I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).

I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick

RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).

Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread

RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.

Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.

Android 10 - Root

Hey guys!
I have a rooted pixel 3. I want to upgrade to Android 10 if they release in the next day or so as reported. I've read they made some progress with magisk...
What is my best bet here?
I would love to keep root, but most importantly I want to keep my data and upgrade to Android 10.
I do really want to keep root too.
Is there a guide?
Thanks!

I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.

kkjb said:
I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.
Click to expand...
Click to collapse
This is a build of blueline TWRP-3.3.1 from the crosshatch tree that is supposedly working from a follow-up post.
https://forum.xda-developers.com/pi...pixel-3-xl-t3861623/post79995400#post79995400

So is there no way to root just now?
I upgraded from a rooted Android 9 by downloading the factory image for 10 and removing -w from the bat file. All okay, data retained.
But there is no TWRP that works and I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.

Audioboxer said:
I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.
Click to expand...
Click to collapse
That works, did it myself. Make sure you are on the latest canary build of Magisk.

TonikJDK said:
That works, did it myself. Make sure you are on the latest canary build of Magisk.
Click to expand...
Click to collapse
Thanks, I was on beta.

Does edxposed work with android 10?

Bubbler4343 said:
Does edxposed work with android 10?
Click to expand...
Click to collapse
It did not work on Android Q Beta 6... just bootlooped. So I am assuming it still does not work for 10.

It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?

stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
Did you try the twrp version in post #3?

Just got a notification for upgrading to android 10 , date Tuesday 10.19 pm.
Since there is no xposed available for Android 10, i' ll stick to android 9

Looks like TWRP won't decrypt. Has anyone ADB sideloaded the Canary version of Magisk through TWRP? That was the old workaround when decryption didn't work.

stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.

jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I assumed it was for 3XL only, glad you pointed that out! It does boot, however TWRP is not able to mount anything (system, data etc.), so I guess this is a dead end.
sliding_billy said:
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.
Click to expand...
Click to collapse
As stated above I am unable to access any partitions, so I guess I'm also unable to run the uninstaller :crying:
Thank you both for your suggestions :good:

jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I have tried, and it doesn't decrypt from what I see (booted into TWRP, but no file access)

Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not

Edemilorhea said:
Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not
Click to expand...
Click to collapse
I rooted 10 with no issues.

sliding_billy said:
I rooted 10 with no issues.
Click to expand...
Click to collapse
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?

Edemilorhea said:
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?
Click to expand...
Click to collapse
No, you have to use a Magisk patched boot with canary magisk. Not even close to the old way. No TWRP. Lot of info on here. You might want to start reading before jumping in.

Manually patching the boot image with the canary build "works" - as in - it shows Magisk installed in Magisk Manager and can grant Superuser to apps --- BUT, you can't write to system, so things like Adaway don't work, also Google Pay doesn't work. I'm not sure what you use root for, but this makes it fairly useless to me for now.

Unresponsive touch screen in TWRP - how can install a ROM?

So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?

kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip

vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device

vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.

kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group

vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.

kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted

vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.

FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant

I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.

s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.

kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.

I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.

TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)

roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.

TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work

This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.

Is it safe to update OnePlus 6 on Oreo 8.1.0 OxygenOS 5.1.11 directly to android 10?

I had problems on pie so downgraded to Oreo. Now I'd like to update to android 10. Is it safe to go straight from Oreo to android 10? How can I keep root? Will my data be wiped?
Also I tried updating first using twrp but got an error. Can someone explain what happened? I will attach a screenshot

You're posting in the wrong section, and probably using the wrong TWRP. I would use MSM tool in your place, and yes, it will wipe your internal storage, so backup

Floodland said:
You're posting in the wrong section, and probably using the wrong TWRP. I would use MSM tool in your place, and yes, it will wipe your internal storage, so backup
Click to expand...
Click to collapse
Would it be safe to make a nandroid backup with the current twrp version I use? Version 3.2.2-0

Also would it work if I tried to flash an older more compatible version of twrp?

First you have to update to OOS 9.0.9 and then to OOS 10. See the following threads:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 (Instructions)
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 (OOS Full zip downloads)
If you do everything correctly, you will not lose any settings or files on internal storage. But please make backups before continuing.
Also, you posted this in the wrong forum section. Maybe a mod can move it.

Flaxe said:
First you have to update to OOS 9.0.9 and then to OOS 10. See the following threads:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 (Instructions)
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 (OOS Full zip downloads)
If you do everything correctly, you will not lose any settings or files on internal storage. But please make backups before continuing.
Also, you posted this in the wrong forum section. Maybe a mod can move it.
Click to expand...
Click to collapse
So despite the error I got using twrp to flash an update, would it be safe to make a nandroid backup using the same version? Would I be able to restore it if I had to?

OnePlus6is7 said:
So despite the error I got using twrp to flash an update, would it be safe to make a nandroid backup using the same version? Would I be able to restore it if I had to?
Click to expand...
Click to collapse
I assume you got the error because you have an old TWRP version and you tried to flash OOS 10 directly. I don't know for sure if the nandroid will work with a new TWRP version, but I'm guessing it will work (otherwise you can just boot old TWRP and restore nandroid).
It's very difficult to actually brick the OnePlus 6, so even if you would do something wrong and end up in a boot loop, there's probably an easy way to fix it.
If I remember correctly, this is basically what I did:
Uninstall all Magisk modules (but not Magisk itself). Uninstall substratum themes etc, if you use any.
Boot into TWRP. Flash OOS 9.0.9.
Flash new TWRP version (for example twrp-3.3.1-14)
Follow section B from the link I sent earlier.

Flaxe said:
I assume you got the error because you have an old TWRP version and you tried to flash OOS 10 directly. I don't know for sure if the nandroid will work with a new TWRP version, but I'm guessing it will work (otherwise you can just boot old TWRP and restore nandroid).
It's very difficult to actually brick the OnePlus 6, so even if you would do something wrong and end up in a boot loop, there's probably an easy way to fix it.
If I remember correctly, this is basically what I did:
Uninstall all Magisk modules (but not Magisk itself). Uninstall substratum themes etc, if you use any.
Boot into TWRP. Flash OOS 9.0.9.
Flash new TWRP version (for example twrp-3.3.1-14)
Follow section B from the link I sent earlier.
Click to expand...
Click to collapse
Thanks for the help. Just one more thing. I read somewhere it was possible to update twrp through twrp. When I got to install image part, there were some options one of them was supposed to be "recovery image" as far as I remember. But in my version in place of that there was something called vendor image. What does that mean? Can I update twrp by flashing a zip file through the current twrp?

OnePlus6is7 said:
Thanks for the help. Just one more thing. I read somewhere it was possible to update twrp through twrp. When I got to install image part, there were some options one of them was supposed to be "recovery image" as far as I remember. But in my version in place of that there was something called vendor image. What does that mean? Can I update twrp by flashing a zip file through the current twrp?
Click to expand...
Click to collapse
Yes, if you already have TWRP installed, you can install the new zip from your current TWRP. But remember if you had Magisk installed before, to reboot TWRP and flash Magisk again.

I followed what you said. It all worked out. I now have latest twrp, android 10 and root. thank you very much.