Related
Hi All,
Been a root user for a few years, so i know the power of the typical root apps such as SU, Magisk and Xposed.
I was messing around last night an managed to find a way to get magisk fully installed on my phone and it passed the safety net ( see pictures). There are pictures to prove i have got magisk, Also there may be a easier method but this is what i used.
Ensure you are on RR as i have not tested.
Here is my method:
1. Download both attached files
2. Reboot to recovery
3.flash SU
4.Reboot
5. Once system loads open up SU app and go through the initial setup
6. reboot back into recovery
7.flash Pixel Magisk RC112
8. REBOOT
9. go into the SU app and into settings, scroll down to full uninstall and click thorough the popups and uninstall.
10. your phone will reboot and go into the magisk app and thank me.
Thanks for reading
EDIT: ALTERNATIVE METHOD BELOW:
How I got this on pn, elemental and flashing the right zip in the op was the key for me, the 2 zips in the first post of this thread
Install pn
Install TWRP
Reboot system
Reboot recovery, install elemental
Reboot to system
Reboot recovery install magisk sr3 zip one on op
Reboot system
Set up super su
Reboot recovery, flash rc112
Reboot system
Super su full unroot, check yes to both
Should reboot system
Open and set up magisk manager,
Go to settings and check hide magisk and systemlesd
Seems to work better on pn
This follows the first post of this thread works good for pn
If magisk manger doesn't show up in your launcher
Install https://github.com/topjohnwu/MagiskM...ger-v4.2.6.apk
CREDIT: mac796
Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP
https://www.androidfilehost.com/?fid=457095661767148610
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Remember to check busy box in magisk manager app,
And give it a couple reboots, takes a bit to kick in.
Edit no longer have to do anything to get titanium backup to work, just check Magisk hide and systemless
Edit. Will work on big and small pixel
Edit updated new Magisk zip
Credit Goodwinc
Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk
ansontyl96 said:
Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not sure I was taking to somebody last night who was trying it, he hasn't got back to me
Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk
ansontyl96 said:
Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
At the very end of my method I had to reboot once to get it all working right.
For the full unroot part do I need to restore the boot and recovery img?
If I choose no it reboot with SuperSU app disappear but still rooted with SuperSU as shown in the magisk app
restore the boot and recovery, it should delete the app and no super su left on your device.
Awesome. Gonna try this out tomorrow morning.
Are there any other useful modules for magisk? I havent looked into them since it was in v6 or v7...
only thing i use is hide su or magisk
everything else seems irrelevant for me, but if you find something let me know.
Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)
rohitece06 said:
Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)
Click to expand...
Click to collapse
Good deal. I had to do a clean flash. You might end up with bugs
mac796 said:
Good deal. I had to do a clean flash. You might end up with bugs
Click to expand...
Click to collapse
thanks, i'll keep an eye out.
Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
xdadevnube said:
Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
I have not seen anyone say they have decrypted the phone, Magisk is just now working on a few roms. I wouldnt bother, this phone has the processor for decryption.
So I take it that even with this it is one or the other with regard to having root (su) working or safety net passing for Magisk. You cant have true SU where you can alter system/app folders with Magisk root, you need true super su. So if I use Magisk root it limits me a little bit. But if I dont I cant use stuff like android pay, LOL
mac796 said:
Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP https://drive.google.com/open?id=0B1xZ4VKT4JKZTnhTdGxDcWlkMXM.
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Edit. Will work on big and small pixel
Click to expand...
Click to collapse
Thank you, worked like a charm on my regular pixel with RR.
jawonder said:
Thank you, worked like a charm on my regular pixel with RR.
Click to expand...
Click to collapse
That's great. I'm trying to get a hold of another guy that said he got it to work on pn. I tried but ended​ up having to start over and flash stock. I'll tell u this if you haven't tried restoring a backup with rc2, don't, it caused all kinds of problems. I went back to rc1.
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
You might have to reboot once, and I uninstalled and reinstalled it. It works. I even used it to back to my stuff after rc2 took it all away lol
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
Make sure and enable busy box inside magisk manager settings. That might do the trick and I installed busy box like normal to, not sure if I had to, I think it might be built in to that app
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system (Edit 8/28/17: DO NOT install TWRP, just boot to system)
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
UPDATE 10/2 The links for SuperSu and SuHide have been updated to the latest releases.
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
GroovinChip said:
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
I've seen some folks report that they couldn't get Magisk to work. I can't confirm that right at this moment though. You can test and see if it'll work by just using the TWRP provided. Not sure if it's based off RC2 or RC1.
raazman said:
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
Click to expand...
Click to collapse
It depends, are you able to boot to system? If not, like you're stuck in a bootloop, I'd suggest flashing completely back to stock. It would mean you'd lose your apps and data, but if you can't boot to system anyway then it doesn't really matter.
If you CAN boot to system, then I'd suggest just starting over and use SuperSu with SuHide. I doubt that any changes actually took place on your device since you didn't flash a custom kernel. But this is only if you can boot to system successfully.
Sent from my Google Pixel XL using XDA Labs
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
GroovinChip said:
3) Download SuperSu Config
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
Click to expand...
Click to collapse
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Mike02z said:
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
Click to expand...
Click to collapse
Great!
I haven't tested my debit card after adding yet either. Been home the whole time
Sent from my Google Pixel XL using XDA Labs
@GroovinChip Is your bootloader unlocked?
Kisakuku said:
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Click to expand...
Click to collapse
Ok, I'll edit the OP. I wasn't 100% sure, that's why I did it anyway.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Rooted perfect however I cannot uninstall system apps, how come?
have you tried going into adb shell and type the su command?
I'm using the system app remover from playstore. It says failed to uninstall.
Root works. AndroidPay works with SUHide!
Thanks!
Ok after reflashing, everything works as intended. Thanks for the guide!
I can confirm this works with the Pixel XL.
Stupid question but I'm guessing bootloader must be unlocked first correct?
Denton.S said:
Stupid question but I'm guessing bootloader must be unlocked first correct?
Click to expand...
Click to collapse
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I was afraid you were going to say that. For one brief, glorious moment I thought I could get rid of adds without having to deal with this damn locked bootloader. My own mistake for getting the phone from EE direct. Thanks dude, much appreciated though
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
maraschino said:
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
Click to expand...
Click to collapse
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Just updated mine via app , after reboot there was no signal , no simcard ,no imei dont panic reboot one more time ,and everything is working as usual.
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
maraschino said:
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
Click to expand...
Click to collapse
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
KOLIOSIS said:
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
Click to expand...
Click to collapse
Thx for info
I always update through TWRP. Just updated. Since I always choose the hide magisk option replacing it with a random name I uninstall the app real quick before I reboot to recovery. Used to be if you didn't you would end up with two apps installed. Don't know if this is still an issue or not. Either way all your settings will still be there. I uninstall the app, reboot to recovery, flash Magisk. Boot back into the OS, all my settings are already there, so the only thing I have to do is rehide Magisk.
Do this update fix the charge problem when the device is off?
ELGeKo24 said:
Do this update fix the charge problem when the device is off?
Click to expand...
Click to collapse
Didn't fix it for me.
OS 9.0.7.
TWRP 3.2.3-9
Magisk v18
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
I usually start over.
I flash a virgin boot age to both slots.
Reboot with TWRP
Install TWRP zip
Install ElementalX and Magisk zips.
Change slots and reboot recovery
Install ElementalX and Magisk in this slot.
I have the same OS version and kernels etc flashed in both slots.
lostunsunghero said:
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
Click to expand...
Click to collapse
Or you can also disable the Battery Optimisation for Magisk
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
What is the recommended install suggestion? Only Zip or with Boot image patch?
Calvin1997 said:
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
Click to expand...
Click to collapse
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
bladestonez said:
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
Click to expand...
Click to collapse
You're right. If tried the safetynet check on the new one, and after that the new one was removed. Completely strange. I hope someone here knows what to do
No problem here just selected install then used recommended.
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
So you just did the direct install option? Also are you running magisk with or without TWRP?
Calvin1997 said:
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
Click to expand...
Click to collapse
This is what I get when I install from magiek manager.
Yes with TWRP
Quick question; I'm on the T-Mobile OP6t. I'm running the stock rom but I'm rooted. If I wanted to update, how would I go about it? Would I just install the update and presumably lose root? So I'd have to flash magisk and re-root again after updating right?
Thanks in advance!
H3adru5H said:
Quick question; I'm on the T-Mobile OP6t. I'm running the stock rom but I'm rooted. If I wanted to update, how would I go about it? Would I just install the update and presumably lose root? So I'd have to flash magisk and re-root again after updating right?
Thanks in advance!
Click to expand...
Click to collapse
Download the full zip update file
Reboot into TWRP
Make Backup (recommended)
Install update
Immediately install TWRP
Reboot into TWRP
Install Magisk
Caltinpla said:
Download the full zip update file
Reboot into TWRP
Make Backup (recommended)
Install update
Immediately install TWRP
Reboot into TWRP
Install Magisk
Click to expand...
Click to collapse
Egh that sounds horrible lol. Any good OxygenOS room recommendations that keep wifi calling?
H3adru5H said:
Egh that sounds horrible lol. Any good OxygenOS room recommendations that keep wifi calling?
Click to expand...
Click to collapse
Its not that bad, actually. Takes like 5 minutes, tops.
Bildo41383 said:
Its not that bad, actually. Takes like 5 minutes, tops.
Click to expand...
Click to collapse
Tried googling around. Where would I pull the official update zips?
H3adru5H said:
Tried googling around. Where would I pull the official update zips?
Click to expand...
Click to collapse
in the root of your memory, along with the TWRP intaller and Magisk installer files as well.
Updating on these phones is super simple thanks to the A/B partition.
Install update as normal but DO NOT restart immediately.
Before restarting, open Magisk manager and press "install magisk" and install to inactive slot.
Restart, done.
stevob21 said:
Updating on these phones is super simple thanks to the A/B partition.
Install update as normal but DO NOT restart immediately.
Before restarting, open Magisk manager and press "install magisk" and install to inactive slot.
Restart, done.
Click to expand...
Click to collapse
That's what I thought. Could have sworn it was very simple to do so. Just update and re-root.
stevob21 said:
Updating on these phones is super simple thanks to the A/B partition.
Install update as normal but DO NOT restart immediately.
Before restarting, open Magisk manager and press "install magisk" and install to inactive slot.
Restart, done.
Click to expand...
Click to collapse
Would you do a local upgrade and select the full image? How do you install magisk to the inactive slot?
Pretty sure both the magisk installer and the twrp install script will automatically install to both slots
Masamune3210 said:
Pretty sure both the magisk installer and the twrp install script will automatically install to both slots
Click to expand...
Click to collapse
Nope.
The best thing to do is to take the standard upgrade or do local install twice to make sure both slots are at the same OS level.
When you boot TWRP then run the zip, it will install in both slots.
Magisk does not install to both slots. It only installs to the active slot.
You need to install, switch slots, reboot to TWRP again and install in that now active slots.
I make both slot_a and slot_b the same.
tech_head said:
Nope.
The best thing to do is to take the standard upgrade or do local install twice to make sure both slots are at the same OS level.
When you boot TWRP then run the zip, it will install in both slots.
Magisk does not install to both slots. It only installs to the active slot.
You need to install, switch slots, reboot to TWRP again and install in that now active slots.
I make both slot_a and slot_b the same.
Click to expand...
Click to collapse
My mistake, just got the phone a couple days ago
If you're rooted it's going to download the whole rom anyways. If yu didn't install TWRP let it download and install and when it tells you to reboot, don't do it. Go to magisk and select uninstall, then restore from the next menu. Go to recents and close everything. Go back to magisk and select install, then install to inactive partition after OTA from the next menu. Magisk will reboot the phone when it's done installing itself to the inactive partition (where your new update is already installed) and the phone will boot to that when reboots. You've just completed a dirty flash and retained root.
This is how you update when rooted.. simple and easy
Screenshot attached and follow this link for complete guide :good: https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-beta-1-oneplus-6t-t3881099
Hi, simple question: will I lose root if I update to the latest oos? If so, will I have to re-root and reinstall every single module?
Simple answer to that exact question: yes.
Simple solution: after the update finished installing, DO NOT RESTART. Go to Magisk, then click install and select install to inactive slot. To the question, just accept, wait for it to finish, then hit restart. Enjoy your rooted 11.0.10.10.
Note: It's recommended to disable (no need to remove) all modules before starting the version update, then enabling them again, once the update has finished and you have already done the Magisk install.
I only use 2 modules, Advanced Charging Controller and Debloater, these don't seem to have any issues staying enabled during an update, but other modules have some issues.
daviddosa said:
Simple answer to that exact question: yes.
Simple solution: after the update finished installing, DO NOT RESTART. Go to Magisk, then click install and select install to inactive slot. To the question, just accept, wait for it to finish, then hit restart. Enjoy your rooted 11.0.10.10.
Note: It's recommended to disable (no need to remove) all modules before starting the version update, then enabling them again, once the update has finished and you have already done the Magisk install.
I only use 2 modules, Advanced Charging Controller and Debloater, these don't seem to have any issues staying enabled during an update, but other modules have some issues.
Click to expand...
Click to collapse
Will this work even taking the smaller OTA update provided through the system, rather than finding the full version and installing it manually?
As soon as you unlock the bootloader, it only offers the full zip instead of the incremental update.
I never tried otherwise, and it's recommended to use the full zip when rooted.
daviddosa said:
As soon as you unlock the bootloader, it only offers the full zip instead of the incremental update.
I never tried otherwise, and it's recommended to use the full zip when rooted.
Click to expand...
Click to collapse
I only ask because the Oxygen Updater doesn't have the newest release, and recently has not had several of the full updates, apparently because OnePlus has not been releasing them. So not sure whether to proceed with just the OTA version.
As far as I know, they're the same. The full zip which you download using Oxygen Updater or by the built-in system updater will work the same, and the method of keeping root is exactly the same. After update, DO NOT restart, install Magisk via app to the inactive slot, then restart.
I got the latest update via the built-in updater, not with the Oxygen Updater app.
What does it mean; install Magisk via app to the inactive slot, then restart ?
ablak44 said:
What does it mean; install Magisk via app to the inactive slot, then restart ?
Click to expand...
Click to collapse
Exactly what it means, if you already have magisk installed, tap install, then when the 4 options come up, tap install to inactive slot. Then reboot
ablak44 said:
What does it mean; install Magisk via app to the inactive slot, then restart ?
Click to expand...
Click to collapse
more understand about oneplus device OTA method if you not.
Nowaday, OP device have many duplicate partitions and its call slot _a and _b.
When you using your phone, its running "active slot", and OTA will install new firmware version to "inactive slot", (to save your phone if any upate fail,..etc).
So after OTA finished, you need to use magisk to setting root (in new partition "inactive slot").
After reboot, inactive slot become active. that 2 slot active alternate after each OTA time.