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.

[OOS 5.1.11] Pre-Rooted Bootimage

Hi there,
OnePlus is rolling out the OxygenOS 5.1.11 update! According to this thread, I made a pre-rooted bootimage for you to flash
I used the guide on the mentioned thread and used Magisk Manager 5.8.3 (129) with Magisk 16.7
For those who'd rather like to do it on their own, I'll also attach the original bootimage of OOS 5.1.11.
Downloads:
- patched bootimage [MD5: 5EC7C328AEE0D38B43A2727BCD767378]
- original bootimage (5.1.11) [MD5: B6790A9D38F41E0EBC6830D1076FAFF0]
Video instructions:
The awesome @GizmoFreak made a nice step-by-step video for you! :good:
Special thanks for his guide at @b1czu, [MENTION=4470081 ]TopJohnWu[/MENTION] and @GizmoFreak! Please also give him a "thanks" :good:
UPDATE: Magisk 17.1 was released by @topjohnwu ! Many fixes and most important: "Install to inactive Slot (After OTA)" is back! Upgrading our ROM should now be much easier again since already rooted users don't need to use the whole fastboot thing again. However, for new 'unrooted' users, I'll still provide here the always latest patched bootimages.
Cheers,
T.Bear

thanks do we still need to do the direct install from magisk manager?

czerdrill said:
thanks do we still need to do the direct install from magisk manager?
Click to expand...
Click to collapse
Yes, if you whish to keep root. Otherwise your device would take the stock bootimage for the next boot again. This patched one is only for booting with 'temp' root privileges so that you can use magisk Manager to direct install the root stuff to the original bootimage.

does this pass the safety checks?

It's the same procedure as in the thread I mentioned! This is not a standalone 'project', just the missing bootimage for the latest OxygenOS update.
But to answer your question, yes if you follow the instructions on the mentioned thread it passes all checks.
Only if you install things like Xposed framework it won't pass.

RiTCHiE007 said:
does this pass the safety checks?
Click to expand...
Click to collapse
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
fastboot boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
EDIT 1: Added 3rd command which I used but forgot to mention it here ?. Thanks GizmoFreak !

amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
SafetyNet will show the response is invalid because Google recently updated the SafetyNet API. Now developers need to use an API key to access SafetyNet. We need to wait for Magisk to be updated.
---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------
amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
And the second command should be fastboot boot boot.img

Plz make for H2OS OB 1

Thanks

Do I need to install 5.1.11 first?

williamcll said:
Do I need to install 5.1.11 first?
Click to expand...
Click to collapse
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Created a video. I hope it will make things easy for others.

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Will I lose my data in the process?

no, all are retained

GizmoFreak said:
Created a video. I hope it will make things easy for others.
Click to expand...
Click to collapse
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Click to expand...
Click to collapse
Yes feel free to add it to OP.

ed-gonzo said:
no, all are retained
Click to expand...
Click to collapse
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)

Brother, your download link is not working?

williamcll said:
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)
Click to expand...
Click to collapse
Magisk 16.7 is up to date

What's the benefit of keeping stock recovery and not rooting via twrp?

Magisk Manager 7.3.5/Magisk v20 now available (reporting success)

I woke up today to a prompt to upgrade Magisk Manager to 7.3.5, and Magisk to v20. v20 is the one that adds support for Android 10 and complete changes how system_as_root works (which made me nervous).
I was running Magisk v19.3, having never been prompted to install v19.4.
I'm here to report that both install just fine. I have a bunch of modules installed: busybox, debloater, f-droid, magisk manager recovery, riru, edxposed, tzdata. I can't tell if it's using "compat mode" or not. I guess that depends on the specific modules you've got?
I created a new patched_boot for 10.0.14.0 with Magisk v20 (not sure if this is necessary for re-patching now that 19.3 is not current). https://yasmar.net/xda/patched_boot_10.0.14.0_20.img.gz

I'm using it on cr driod works well

on what rom are you running this? i am on 10 gsi rom from here and in v19 riru and edexposed gave me bootloops no mather what i did

Using it on latest stock, no problems so far

loop4444 said:
on what rom are you running this?
Click to expand...
Click to collapse
Stock 10.0.14.0
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.

a1291762 said:
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.
Click to expand...
Click to collapse
And it's back. Stupid mobile network blacklisting me for rebooting
Coincidentally, my TWRP is dead so I'll need to put that back when I get home. Probably affected by the Magisk upgrade.

After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).

a1291762 said:
After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).
Click to expand...
Click to collapse
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'

yashinodon said:
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'
Click to expand...
Click to collapse
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.

Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.

yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
Right, thanks for the info.
Haven't tried Magisk 20 yet, I still use 18.1. Maybe we need an updated TWRP, but since 33bca aka offain left this device I don't have high hopes...

yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
When you see "your system has been destroyed " ,it's most likely conflict between magisk and some module , the easiest fix is to 1.boot to twrp via PC , use magisk manager for recovery. zip and disable all modules.
2. if your recovery says :data is encrypted -flash different kernel , that will disable magisk , reboot to recovery , use magisk manager for recovery , disable all modules and flash magisk again .
In both of the cases you won't need to reflash stock rom every time you see that message , if you want to use twrp again
P. S. BTW , there is an 20.1version of magisk and magisk manager 7.3.6 already

Cannot run TWRP after installing Magisk

Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: twrp-3.3.1-1-guacamoleb.img (from https://twrp.me/oneplus/oneplus7.html)
Magisk: problem started with v19.1 but repeated itself with v20.0
UPDATE: I've found someone else with the same problem https://github.com/topjohnwu/Magisk/issues/1920
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Try to enter TWRP from recovery but boots to stock recovery
Can anyone help me? The feature I need the most is a full system backup

ColOfAbRiX said:
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: 3.3.1-1-guacamoleb
Magisk: 20.0
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Install MagiskHide
5) Try to enter TWRP from recovery. Doesn't work.
Can anyone help me? The feature I need the most is a full system backup
Click to expand...
Click to collapse
Hello,
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Please use Magisk 19.3 on your pie rom.
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)

Hi!
strongst said:
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Click to expand...
Click to collapse
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
strongst said:
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Click to expand...
Click to collapse
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
strongst said:
Please use Magisk 19.3 on your pie rom.
Click to expand...
Click to collapse
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.

ColOfAbRiX said:
Hi!
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
Click to expand...
Click to collapse
Thanks for the update!
Yes, please use the twrp from mauronofrio, it's unified for OP7 and OP7 Pro (check file name like twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip)and and 19.3 magisk.

Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920

I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
ColOfAbRiX said:
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
Click to expand...
Click to collapse
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."

lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.

lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
Really? I have the problem with Magisk version 19.3

strongst said:
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
Click to expand...
Click to collapse
I tried to use 19.3 and nothing.

ColOfAbRiX said:
Really? I have the problem with Magisk version 19.3
Click to expand...
Click to collapse
Hmm, really strange, with 19.4?
lvints said:
I tried to use 19.3 and nothing.
Click to expand...
Click to collapse
Something prevents twrp to stick from magisk side

strongst said:
Hmm, really strange, with 19.4?
Something prevents twrp to stick from magisk side
Click to expand...
Click to collapse
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:

lvints said:
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
Click to expand...
Click to collapse
Sorry, I'm out of ideas at the moment...

And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP

ColOfAbRiX said:
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
Click to expand...
Click to collapse
I'm sad about what happened to you, friend
If you can find a solution put the topic.

I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?

lvints said:
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
Click to expand...
Click to collapse
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart

ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
See other thread(cross posting) https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559

@strongst
Do you think it's best to answer this topic or the other?

lvints said:
@strongst
Do you think it's best to answer this topic or the other?
Click to expand...
Click to collapse
Where the discussion starts
Otherwise you'll lost the line when switching between threads.

ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
I have the same problem as yours. I've tried countless scenarios, followed tutorials on XDA and Youtoube but can't make TWRP work.
Out of curiosity I restarted the device through slot A after flash zip from magisk. My phone has accessed TWRP, but I cannot access my files. When I restart from slot B I have the opposite. Twrp doesn't work, but my files are accessible.
So I believe I somehow "broke" slot A. I just don't know how I did it or how to fix it.

Root OnePlus 6 on Android 10 beta (Magisk patched boot image)

EDIT: Please refer to my other thread here.

thanks
how to flash via fasboot ?
---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------
thanks
how to flash via fasboot ?

SHAY820 said:
thanks
how to flash via fasboot ?
Click to expand...
Click to collapse
fastboot flash boot magisk_patched.img
Testing now to see if this worked. Thanks OP!
---------- Post added at 20:31 ---------- Previous post was at 20:30 ----------
remewer said:
Here are the stock and Magisk patched boot images:
Android 10 OB1:
http://www.mediafire.com/folder/2ffhwvqplh9ui/OnePlus_6_OOS_OB1
Flash using fastboot.
Click to expand...
Click to collapse
Worked perfectly using the command:
Code:
fastboot flash boot magisk_patched.img
Thank you!!!

Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you

Does it not work for OB2?

bright2541 said:
Does it not work for OB2?
Click to expand...
Click to collapse
Which OB2 are you talking about?

Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
I think it's impossible without TWRP, unless you do a data wipe.

Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?

alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
I was in the same situation and can confirm flashing the stock boot.img recovered from bootloop. Now to wait for compatible TWRP

alonroz said:
You'll need to use Magisk Uninstaller, but I've no idea how you'd go about that without TWRP. Try the stock boot.img maybe?
Click to expand...
Click to collapse
Flashing the stock boot runs the system but so I'm not magisk so I'm not the root. I'm just trying to remove the magisk modules to prevent it from installing when I flash the boot patched because if I let it bootloop

Hello!!
Thank for your work.
Work perfect with conmand fastboot flash boot magisk_patched.img, and after instal magisk manager

I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?

vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
There's no way. Unless you flash stock boot image, then factory reset, which will remove all traces of Magisk.

vorsprungtechnik said:
I have the xXx installed via Magisk and flashing the patched boot gets stuck in a bootloop. Seems xXx is not compatible with Android 10 but there's no way to remove the module. Anyway around this, aside from flashing stock boot and staying unrooted?
Click to expand...
Click to collapse
Try to flash back to the same build you just came from, at this point it's try or lose everything anyways. Flash last version you had installed along with whatever twrp/magisk you had.
---------- Post added at 06:26 AM ---------- Previous post was at 06:04 AM ----------
Faylen said:
Hello,
I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher working except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?
Please thank you
Click to expand...
Click to collapse
Have you tried fastboot to change the slot you are booting to? If not you can try using this command in adb
fastboot set_active b
If that does not work try switching to slot a
fastboot set_active a
If you get an error you may need to update your SDK tools. Here is the link to the latest updates
https://developer.android.com/studio/releases/platform-tools

This is for OnePlus 6 with Android 10 beta 1 of 19/10/2019 ?

Will flashing this wipe my phone? and will I still be able to update to future OTAs?

whone99 said:
Will flashing this wipe my phone? and will I still be able to update to future OTAs?
Click to expand...
Click to collapse
No, it won't wipe your phone. Yes, you'll still be able to update, but it will download the whole update, not increment since your bootloader is unlocked.

Flashing this magisk patched doesn't work for me. It's true, i didn't erase anything from magisk when i upgraded, might need to do a autumn cleaning
Until then, winter is coming and i will wait for a working solution.

Does it is work on OP6_o2_Beta 30?
I also have magisk installed and vanced, so it's time to wait for a solution to come out.

Chrome reports virus !!!