Hi, I have a Pixel XL running 7.1.2 and running the April 2017 security patches. I had previously rooted using superSU, but decided to switch to magisk for its hiding abilities. Usually by 4 pm my battery is around 60 percent, but it is at 20 percent. Any help would be appreciated.
MLGquickscoper said:
Hi, I have a Pixel XL running 7.1.2 and running the April 2017 security patches. I had previously rooted using superSU, but decided to switch to magisk for its hiding abilities. Usually by 4 pm my battery is around 60 percent, but it is at 20 percent. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have any modules installed? Also, do you have the Magisk app battery optimized?
TheBobMiller said:
Do you have any modules installed? Also, do you have the Magisk app battery optimized?
Click to expand...
Click to collapse
I don't have any modules installed and I have the magisk app optimized
MLGquickscoper said:
I don't have any modules installed and I have the magisk app optimized
Click to expand...
Click to collapse
Have you tried uninstalling the Magisk Manager app, restarting and then reinstalling to see if that fixes it? I've been using Magisk for a while and never had battery drain from it so I'm thinking maybe a reinstall could fix whatever bug occurred.
TheBobMiller said:
Have you tried uninstalling the Magisk Manager app, restarting and then reinstalling to see if that fixes it? I've been using Magisk for a while and never had battery drain from it so I'm thinking maybe a reinstall could fix whatever bug occurred.
Click to expand...
Click to collapse
I have tried that and have seen no results
MLGquickscoper said:
I have tried that and have seen no results
Click to expand...
Click to collapse
What percentage in your battery stats is being used by Magisk?
TheBobMiller said:
Have you tried uninstalling the Magisk Manager app, restarting and then reinstalling to see if that fixes it? I've been using Magisk for a while and never had battery drain from it so I'm thinking maybe a reinstall could fix whatever bug occurred.
Click to expand...
Click to collapse
Hello,
Are you using Magisk on stock 7.1.2 with stock kernel? If so can you tell me what your standard flash operation is? I am running stock N2G47E with April security patch now but with SuperSU and TWRP. I would like to move away from SuperSU and run Magisk but not exactly sure what is the best procedure to do so. After the recent SuperSU f-up I fear the new team may have alternate intentions. I suspect I will need to re-flash N2G47E (after removing the -w) to get a clean base but not sure what is my next step? I have always flashed TWRP and SU at the same time in order for both to survive. Can I also do this with Magisk as well or is there a conflict? Also which version of Magisk have you had the best luck with? I am losing root often on my N6 using V12, and I do not check Busy Box. I saw a thread where someone had a modified V11.xx they made but I can't seem to find the post now.
Thanks
jschill31 said:
Hello,
Are you using Magisk on stock 7.1.2 with stock kernel? If so can you tell me what your standard flash operation is? I am running stock N2G47E with April security patch now but with SuperSU and TWRP. I would like to move away from SuperSU and run Magisk but not exactly sure what is the best procedure to do so. After the recent SuperSU f-up I fear the new team may have alternate intentions. I suspect I will need to re-flash N2G47E (after removing the -w) to get a clean base but not sure what is my next step? I have always flashed TWRP and SU at the same time in order for both to survive. Can I also do this with Magisk as well or is there a conflict? Also which version of Magisk have you had the best luck with? I am losing root often on my N6 using V12, and I do not check Busy Box. I saw a thread where someone had a modified V11.xx they made but I can't seem to find the post now.
Thanks
Click to expand...
Click to collapse
I'll send you a pm with all the answers to your questions so we can keep this thread on the topic of the OP.
TheBobMiller said:
I'll send you a pm with all the answers to your questions so we can keep this thread on the topic of the OP.
Click to expand...
Click to collapse
I also forgot to mention that this is a Google store pixel being used on Verizon, therefore I have the Verizon versions of the firmware.
Go to settings/battery and see what's using the battery. May just be a rogue app you need to reset or uninstall. I'm using Magisk on Verizon and have no problems. When you say you're on Verizon firmware I assume it's the Verizon designated firmware from the Google factory image download site? I'm still on April NHG47K build so sounds like same version.
Sent from my Pixel XL using Tapatalk
Related
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
xxBrun0xx said:
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
Click to expand...
Click to collapse
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
prins29 said:
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
Click to expand...
Click to collapse
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
lpchaim said:
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
Click to expand...
Click to collapse
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
prins29 said:
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
Click to expand...
Click to collapse
I've just tried again with the new TWRP and redownloaded files on my phone to be doubly sure, result is the same error others are reporting. Mind detailing how you managed to get Magisk running exactly? I've been looking around for a few days and never found consistent reports of it working on Nougat specifically, so it'd come in pretty handy.
Bump. Anybody succeed yet?
Try the Magisk 12 Snapshot. For me it works.
-=MoRpH=- said:
Try the Magisk 12 Snapshot. For me it works.
Click to expand...
Click to collapse
Can you write a guide please?
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
-=MoRpH=- said:
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
Click to expand...
Click to collapse
V12 definitely doesn't have an error when flashing like v11.1 did, but still doesn't pass safety check even after clean flashing flashallthetime's retbr build. Anyone get this to work with any other roms? One thing I noticed that was odd after clean flashing was viper and Dolby were installed but Dolby crashed and viper said drivers weren't installed. Weird.
Edit: Reflashed several different roms without zip. Tried using unSU zip + epsilon. No way to safetynet to pass, I give up. No androidpay/pokemongo is a small price to pay for working notification sounds, adblock, and greenify.
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
iron maiden said:
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
xxBrun0xx said:
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
Click to expand...
Click to collapse
yep, but i delete de supersu zip from the rom
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
-=MoRpH=- said:
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
Click to expand...
Click to collapse
How do you pass safetynet with SuperSU? Magisk v11.1 and up has SuperSU built in, why flash it?
Not trying to give you a hard time, just trying to understand. Really appreciate the help!
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
-=MoRpH=- said:
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
Click to expand...
Click to collapse
Did you take a nougat OTA? I didn't, so I wonder if my problem is that I'm still on the marshmallow bootloader/modem?
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
-=MoRpH=- said:
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
Click to expand...
Click to collapse
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.[/QUOTE
I'll pm you with the right one
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=529152257862701536
Click to expand...
Click to collapse
Hi at all,
I own this device for two months now and I have read a lot about rooting and flashing. It seems to be quite difficult compared to my former Samsung and Xiaomi devices...
To avoid any kind of bricking my phone I wanted to ask if there's a way to root it. I (still) have a locked bootloader and I installed the latest update to 7.1.1 with 1st July security patch.
Is there any safe way to root and install TWRP (and afterwards some ROMs of course)?
Thank you. :fingers-crossed:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
jst98 said:
I have root on my moto z play with stock 7.1.1. if you don't downgrade you don't get bricked
To unlock and install twrp :
https://forum.xda-developers.com/moto-z-play/how-to/guide-root-xposed-flashing-stock-rom-t3529637
And to root use this:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
To root is better with magisk ( second link)because don't break SafetyNet and the link is a tutorial made by me so if have any questions you can ask in the thread.
Click to expand...
Click to collapse
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
f_ries said:
Thank you so much! This is exactly what I needed and what I wasn't able to find :angel:
I will try this in the next few days and tell how far I will have come
Click to expand...
Click to collapse
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Martin-cai said:
Sorry, but how was it? I'm in the same situation and I want to know. Any recommendation? Do you have any issue?
Thanks!
Click to expand...
Click to collapse
If you are in 7.1.1, unlock your bootloader, download TWRP of @Alberto97 version 3.1.1-0(https://dc4.androidfilehost.com/dl/...673368273298955814/twrp-3.1.1-0-addison.img), flash it, download this kernel( https://drive.google.com/file/d/1i8PfTQ1e-WQkZ5-zD52HzWO3LZ5luaq_/view?usp=drivesdk) and the attached Magisk.zip.
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
xdaVTU said:
Now, after you flashed the TWRP through Fastaboot, enter into recovery mode, select INSTALL, select the kernel and swipe to flash it. Then go back, select the Magisk.zip file to flash and swipe to flash it. After you do it, just reboot you device and check if the Magisk Manager app is installed, if it is, then open it, click on "check safety net", tap OK and wait until it tests the root hiding, if it says everything is okay, then everything is okay.
Congratulations, you are rooted now with Magisk and the Hiding Feature, you can play Pokemon go as well and the same for Snapchat and that stuffs that blocks rooted users from using their apps.
Click to expand...
Click to collapse
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Martin-cai said:
Thanks for your response!
I've read that flashing a kernel when you're in 7.1.1 might cause problems. Did you try this steps being in 7.1.1 or they're just general steps?
In case you were in 7.1.1, did you install xposed after those steps?
Sorry if I ask many questions, but I want to be sure that I'll not brick my phone
Click to expand...
Click to collapse
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
xdaVTU said:
no problem dude, i understand your concern, i'm just like this. Actually I was asking for help until last night and got all the answers.
flashing a kernel won't cause any problem since you do not flash any kernel but for your android version. The link i shared with you is a @logotoy73 kernel, he updated it last night and i used it. It's working properly and with no issues.
Today i've tried to install xposed, but due to the forced encryption in 7.1.1 it wasn't possible, even trying with the systemless xposed(magisk feature), maybe later i'll try again then i give you a feedback.
In magisk there are some xposed modules to be able to use it in nougat, but it caused me a bootloop.
If you follow exactly what i've said, you will be rooted in 7.1.1 in a few minutes!
Any problem you have, pm me so i could help you haha
good lucky
Click to expand...
Click to collapse
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Martin-cai said:
I just tried it and it worked perfectly. Thank you so much! You should make a post with those steps, I think it might help someone else.
Please, tell me if you manage to install xposed properly
Click to expand...
Click to collapse
I think creating a new post won't be necessary because kernel is already in @tomparr post, but in the last page of it, the twrp you cam download from Alberto's post, and magisk from the official thread(it's actually one of the most famous threads for now hahaha), but maybe if someone else have any issue with 7.1.1 i can create the post!
Edit. If i plan to try xposed again I tell you!
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
logotoy73 said:
I have systemless xposed running on 7.1.1 with my kernel. After installing module xposed via twrp if a long start, helps reboot.
Click to expand...
Click to collapse
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Bug camera help me
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
xdaVTU said:
Could you help with a little step by step?
Which xposed module? Magisk?
What did u mean with long start? Helps reboot?
Click to expand...
Click to collapse
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
Gean Teixeira said:
I have root z play 7.1.1 with supersu, but problem bug camera ...using kernel post ...anything solution? I'm sorry my English...
Click to expand...
Click to collapse
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Artim_96 said:
Only Magisk module. Normal XPosed would modify /system which would brick your device. And I don't know if that could be fixed
---------- Post added at 23:24 ---------- Previous post was at 23:18 ----------
On the first site there is a tutorial linked, just follow it. Basically get rid of supersu first. Then the tutorial probably says that you have to install a custom kernel in order to just Magisk modules because the stock one is faulty. If you ask me that's shooting with guns on pidgins. The easiest way is to get the Magisk module F2FS loopback bug workaround. Google for it. When you have it and latest Magisk zip, go to TWRP, flash Magisk and the module, then reboot. Works perfectly, though you shouldn't ever wipe or format /cache because that's where Magisk is installed now, you'd loose it.
Click to expand...
Click to collapse
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Gean Teixeira said:
Thanks attention ...no work...i'll installed ROM 7.1.1 pre rooted in other post.
Click to expand...
Click to collapse
Well then go back to stock first
Artim_96 said:
Well then go back to stock first
Click to expand...
Click to collapse
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Artim_96 said:
Well, in the last post you said you are running a pre-rooted version. So what are you actually running and what are you trying to do and what doesn't work?
Click to expand...
Click to collapse
I'm enganed...ZIP is rooted with magisk ,flashed , It,s ok...no insue
Gean Teixeira said:
Stock Addison rooted magisk e december patch ZIP ...flash a few moments
I'M using stock...
Click to expand...
Click to collapse
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
sergiomc22 said:
Is that a new ROM or the Stock Plus?
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
Stock post shamu17...dez patch, root magisk
I've used systemless Adaway for a long time but haven't figured out how to install it on the November update. In the past I would install AdAway_systemless_hosts_v2.zip from TWRP and then install AdAway-org.adaway-3.1.2-57.apk or whatever is the newest version.
From what I have read, twrp-3.1.1-alpha1-taimen.img will not boot on the November update, so I'd like to know if or how others are installing it. I think I might be able to go back to the October update to do it, but I'd rather not.
JimSmith94 said:
I've used systemless Adaway for a long time but haven't figured out how to install it on the November update. In the past I would install AdAway_systemless_hosts_v2.zip from TWRP and then install AdAway-org.adaway-3.1.2-57.apk or whatever is the newest version.
From what I have read, twrp-3.1.1-alpha1-taimen.img will not boot on the November update, so I'd like to know if or how others are installing it. I think I might be able to go back to the October update to do it, but I'd rather not.
Click to expand...
Click to collapse
Follow the guide to root with Magisk and then just install adaway on the phone. Works fine on my Pixel 2 XL.
ilatimer1 said:
Follow the guide to root with Magisk and then just install adaway on the phone. Works fine on my Pixel 2 XL.
Click to expand...
Click to collapse
So the systemless hosts zip file isn't needed anymore?
JimSmith94 said:
So the systemless hosts zip file isn't needed anymore?
Click to expand...
Click to collapse
Nope. I just installed it in systemless mode. Working fine on my end :good:
Badger50 said:
Nope. I just installed it in systemless mode. Working fine on my end :good:
Click to expand...
Click to collapse
Thanks! I don't remember seeing a systemless mode option when installing the APK before but I'll give it a shot.
JimSmith94 said:
Thanks! I don't remember seeing a systemless mode option when installing the APK before but I'll give it a shot.
Click to expand...
Click to collapse
If you look at the pic, the 3rd line down that's grayed out, you'll see what I mean :good:
Badger50 said:
If you look at the pic, the 3rd line down that's grayed out, you'll see what I mean :good:
Click to expand...
Click to collapse
I installed adaway3_2.apk, enabled it, got the newest host files, and rebooted. The 3rd line is grayed out like yours, but it's not checked and I can't check it. Are you sure you didn't install the systemless hosts zip file, maybe sometime in the past?
JimSmith94 said:
I installed adaway3_2.apk, enabled it, got the newest host files, and rebooted. The 3rd line is grayed out like yours, but it's not checked and I can't check it. Are you sure you didn't install the systemless hosts zip file, maybe sometime in the past?
Click to expand...
Click to collapse
I checked it before I installed the host files. Maybe clear the cache and data from the app, and start over.
Badger50 said:
I checked it before I installed the host files. Maybe clear the cache and data from the app, and start over.
Click to expand...
Click to collapse
I tried to check it before installing the host files but couldn't then either.
JimSmith94 said:
I tried to check it before installing the host files but couldn't then either.
Click to expand...
Click to collapse
Does it have Superuser authorization in the Magisk manager app?
Badger50 said:
Does it have Superuser authorization in the Magisk manager app?
Click to expand...
Click to collapse
Yes it does have authorization. My understanding from installing this on previous phones was that the systemless hosts zip file was required to enable systemless mode in the app. Thus my original question of how to install the zip without TWRP.
JimSmith94 said:
Yes it does have authorization. My understanding from installing this on previous phones was that the systemless hosts zip file was required to enable systemless mode in the app. Thus my original question of how to install the zip without TWRP.
Click to expand...
Click to collapse
I know that's how it used to be, but for life of me, I can't exactly remember what I did to make it work. I just know that it does. Wish I could be more helpful, but now I'm stumped
JimSmith94 said:
I tried to check it before installing the host files but couldn't then either.
Click to expand...
Click to collapse
It doesn't need to be checked. It's a known issue. If it is running systemless it should be greyed out.
You have to enable the systemless host option in setting of MAGISK first then download & enable in adaway. I'll try uploading a ss from other than Tapatalk in a bit. Won't allow me for some reason .
Sent from my Pixel 2 XL using Tapatalk
There you go.
Nathan_Lua said:
There you go.
Click to expand...
Click to collapse
I was about to say the same thing. Not sure the last time OP tried installing Adaway, but I've been using Magisk and Adaway for about a while on my 6P and now on my 2 XL, and don't remember the last time I flashed a zip.
Nathan_Lua said:
You have to enable the systemless host option in setting of MAGISK first then download & enable in adaway. I'll try uploading a ss from other than Tapatalk in a bit. Won't allow me for some reason .
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Aha, that did it, thank you so much! Once I enabled systemless host in Magisk, the box was immediately checked in Adaway. I don't know how I missed that, but I did go back to SuperSU for awhile where the zip file was apparently still necessary.
So I am going to necro bump this thread since I have the exact same issue except that enabling systemless mode. In Magisk does absolutely nothing for me. On the latest Magisk (16.0) and Adaway (3.3).Rooted OnePlus 5, stock Oxygen 5.1.3 (Oreo 8.1)
And while I am at it, once upon a time I was able to turn Adaway on/off on the fly without reboot. Somewhere along the way I lost that capability. Is that an Oreo "feature"?
GroovyGeek said:
So I am going to necro bump this thread since I have the exact same issue except that enabling systemless mode. In Magisk does absolutely nothing for me. On the latest Magisk (16.0) and Adaway (3.3).Rooted OnePlus 5, stock Oxygen 5.1.3 (Oreo 8.1)
And while I am at it, once upon a time I was able to turn Adaway on/off on the fly without reboot. Somewhere along the way I lost that capability. Is that an Oreo "feature"?
Click to expand...
Click to collapse
You might have better luck if you posted this in the OP5 forums
Everything was peachy until the past week and a half bit defender started warning me of malware of app-release.apk searching Google gave some insight about it possibly being related to official signing of Android applications. Only thing that I am aware of changing systemwide is magisk weekly updates. Otherwise only have play store applications installed.
Rooted updated magisk
Viper4android
Activeedge
Busubox
Energized
Custom Kernal kirisakura v 1 2.0
Any ideas before I go and uninstall per bit defender?
Thanks,
Brandon
brandonpa said:
Everything was peachy until the past week and a half bit defender started warning me of malware of app-release.apk searching Google gave some insight about it possibly being related to official signing of Android applications. Only thing that I am aware of changing systemwide is magisk weekly updates. Otherwise only have play store applications installed.
Rooted updated magisk
Viper4android
Activeedge
Busubox
Energized
Custom Kernal kirisakura v 1 2.0
Any ideas before I go and uninstall per bit defender?
Thanks,
Brandon
Click to expand...
Click to collapse
app-release.apk is the Magisk canary installer, and yes it is safe.
sliding_billy said:
app-release.apk is the Magisk canary installer, and yes it is safe.
Click to expand...
Click to collapse
Thanks I appreciate the response. I am pretty sure it started to pop up after an update install but wasn't totally sure.
Thanks again.
brandonpa said:
Thanks I appreciate the response. I am pretty sure it started to pop up after an update install but wasn't totally sure.
Thanks again.
Click to expand...
Click to collapse
That app should only show up if you downloaded it from the canary Magisk thread or from topjohn's Git. That was the only way to root when 10 went live. Are you sure you didn't grab it and install it?
sliding_billy said:
That app should only show up if you downloaded it from the canary Magisk thread or from topjohn's Git. That was the only way to root when 10 went live. Are you sure you didn't grab it and install it?
Click to expand...
Click to collapse
I have it setup to install through the canary update path. I didn't purposefully install it, but probably downloaded with one of the canary updates I would assume.
Thanks again.
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
I found oxygen updater in Google play store. Is that what you're talking about?
sbcdave said:
I found oxygen updater in Google play store. Is that what you're talking about?
Click to expand...
Click to collapse
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Shanemichealrowland said:
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Click to expand...
Click to collapse
Yes it does, I've been using it since I got my op9pro on 1st April.
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Bunecarera said:
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Click to expand...
Click to collapse
I assume you disable all magisk modules prior updating.
netgar said:
I assume you disable all magisk modules prior updating.
Click to expand...
Click to collapse
Yes.
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA
Click to expand...
Click to collapse
This is rather annoying. Why are we left behind?
the bolt of thunder said:
This is rather annoying. Why are we left behind?
Click to expand...
Click to collapse
I think it's because the Global ota's are being stored on Google servers instead of the OnePlus servers for some reason
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
I updated my BA using oxygen updater (download full os, settings/system/system updates/lokal update) without touching magisk at all. reboot, bootloader, reflash https://mega.nz/file/bNozXKJI#0zNfKtRw1IBqG6ojFuW3830dxXLgewmtsbbh4T4WGzs (I know its 1.1.2.4.4, but it works...) done
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
dreinulldrei said:
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
Click to expand...
Click to collapse
thats what i did first of all, my device didnt boot at all but kept going to stock recovery. afterwards i flashed what i wrote above, everythinx fine now.
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
Click to expand...
Click to collapse
I decided to unroot and take the update. I'll just wait until the full OTA comes to us before rooting. :/
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Flying Fox said:
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Click to expand...
Click to collapse
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
dreinulldrei said:
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
Click to expand...
Click to collapse
schmeggy929 said:
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
Click to expand...
Click to collapse
Thx for your answers!! Nice to be back to Oneplus. Great community here...
Does anyone know if oxygen updater from the play store is a trustworthy source for these OTAs?