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.

[ROOT] and [Solve] every issue in oxgyen os open beta {1/2/3} (Android pie 9.0)

I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

Is there a fix yet for aod/ambient display yet?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/

For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it

BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues

Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!

Can we get incremental ota update even when unlocked and magisk installed (no twrp)?

I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now

droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)

droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.

CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?

JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!

Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?

digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json

sorry, hit send before it finished uploading

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Android 11 Release

Android 11 has been released. Anyone upgraded yet on a rooted device?

Subscribing for root results.

I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.

fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!

We gots Root!
So far so good root is working

XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?

dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?

antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA

dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.

Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^

I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?

Anyone got a replacement for overscan?

matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary

Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.

do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse

Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.

I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz

Magisk - Format data or not

I'm currently running Miui 12.3 Xiaomi.eu rom, and want to root, can I just flash magisk from twrp or will I need to format data

You
Petesky said:
I'm currently running Miui 12.3 Xiaomi.eu rom, and want to root, can I just flash magisk from twrp or will I need to format data
Click to expand...
Click to collapse
You should be able to flash it without a problem. But as it is with any modifications, there is always possibility that something goes wrong so it is wise to have Magisk uninstaller or boot image at hand

Lord Sithek said:
You
You should be able to flash it without a problem. But as it is with any modifications, there is always possibility that something goes wrong so it is wise to have Magisk uninstaller or boot image at hand
Click to expand...
Click to collapse
yeah you should have a boot.img backup on TWRP or have a Uninstaller but you don't need to format /data .
I have MIUI12.0.6 rooted without Formatted /data at rooting.

Petesky said:
I'm currently running Miui 12.3 Xiaomi.eu rom, and want to root, can I just flash magisk from twrp or will I need to format data
Click to expand...
Click to collapse
Actually, are you on A10 or A11?

Lord Sithek said:
Actually, are you on A10 or A11?
Click to expand...
Click to collapse
What do you mean with A10 or A11?

kerem._trk said:
What do you mean with A10 or A11?
Click to expand...
Click to collapse
Android version

Lord Sithek said:
Android version
Click to expand...
Click to collapse
oh hahahah sorry
Im on Android 10 i didnt got the update yet and I will not install the update because they will disable APK installation.
if there is a way to enable it with Magisk modules I will Install it

kerem._trk said:
oh hahahah sorry
Im on Android 10 i didnt got the update yet and I will not install the update because they will disable APK installation.
if there is a way to enable it with Magisk modules I will Install it
Click to expand...
Click to collapse
ok, but I waited for answer from @Petesky Anyway, I think I answered myself since 12.3 build as far as I know is Android 11.
I'm on Android 10 as well, but from what I've heard, so far on Android 11 you should flash Magisk stable 20.4 first and then, without rebooting, flash Magisk 21 beta right away.
I can't guarantee this though as I personally didn't try it.

Lord Sithek said:
ok, but I waited for answer from @Petesky Anyway, I think I answered myself since 12.3 build as far as I know is Android 11.
I'm on Android 10 as well, but from what I've heard, so far on Android 11 you should flash Magisk stable 20.4 first and then, without rebooting, flash Magisk 21 beta right away.
I can't guarantee this though as I personally didn't try it.
Click to expand...
Click to collapse
I did install 20.4 then 21.4 directly on manager but on reboot it cause a bootloop and then i reinstalled it via twrp and I could boot normally but i stuck on 20.4

My main Phone is the Mi 10 and I only have this Phone from Xiaomi my Other Phone where I only flash some things to try it is the Galaxy S5 (G900F) klte

kerem._trk said:
I did install 20.4 then 21.4 directly on manager but on reboot it cause a bootloop and then i reinstalled it via twrp and I could boot normally but i stuck on 20.4
Click to expand...
Click to collapse
I think you should do that in recovery...

Lord Sithek said:
I think you should do that in recovery...
Click to expand...
Click to collapse
I can try it but I don't know when I will test it because I'm scared if I get a bootloop.
I know I fixed it one time but I don't have a Backup and I don't like Backups theyre too big and takes too long time to restore

Lord Sithek said:
ok, but I waited for answer from @Petesky Anyway, I think I answered myself since 12.3 build as far as I know is Android 11.
I'm on Android 10 as well, but from what I've heard, so far on Android 11 you should flash Magisk stable 20.4 first and then, without rebooting, flash Magisk 21 beta right away.
I can't guarantee this though as I personally didn't try it.
Click to expand...
Click to collapse
Yes Android 11,
I read magisk should be flashed after flashing new rom which requires a data format but wasnt sure if I could just flash magisk after setting up phone without formatting again

Petesky said:
Yes Android 11,
I read magisk should be flashed after flashing new rom which requires a data format but wasnt sure if I could just flash magisk after setting up phone without formatting again
Click to expand...
Click to collapse
did that work?

Yes , flashed magaisk 20.4 then 21.0 and I got root

Okay Thanks