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
Related
I got my OP3 1-2 weeks . before i had a S4 (rooted). I'm really happy with this phone but i got some questions and problems.
1. When i video call via skype the camera will freeze in 50sec. when I switch the camera to the back and front it's fixed for 50 sec again and same thing happening again....
2. Rooting the OP3 is it safe to do ? And does someone got a guide for it ? I saw allot off them but I don't know which one works for Oxygen 3.2.1. I got some rooting experience with the S4 but rooting op3 is kinda different.
3. When i got a rooted op3 without a custom rom. Do i still get updates via System updates in the settings ?
Sorry for my bad English and thanks for reading.
1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates
J_Dutch said:
1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates
Click to expand...
Click to collapse
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
Ok, didn't know that. How do you install that?
J_Dutch said:
Ok, didn't know that. How do you install that?
Click to expand...
Click to collapse
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/guide-oneplus-3-how-to-unlock-bootloader-flash-twrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
crysen said:
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Seriously? I've been told several times installing a custom recovery and OTA is a no go...
But thanks, I'm still stock but I don't know for how long. I'm still a flashaholic inside.
crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
On the other hand, when somebody only uses TWRP (for backups for example) without modifying the system and kernel at all,
OTAs will work just fine.
AcmE85 said:
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
Click to expand...
Click to collapse
Oh thanks, I didn't know that, I would've flashed it via normal OTA after work otherwise
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
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Can i use it without root/twrp?
AbOuLfOoOoOuF said:
Can i use it without root/twrp?
Click to expand...
Click to collapse
You can't use it without root access. But TWRP or any kind of recovery is not needed for things like this.
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
So basically I just have to download and installed viper4android fx 2.7 apk and that's it.
No deep buffer removal or any extra steps or magisk module needed
AbOuLfOoOoOuF said:
Can i use it without root/twrp?
Click to expand...
Click to collapse
Without twrp yes. You don't need recovery for viper4android.
But root. Nope.. You need to have a rooted device for the audio drivers to get installed.
And just so you know rooting with trip knox and void your warrenty and it also involves unlocking bootloader and doing so will show a message on phone startup about the phone being insecure.
So keep that on mind before you unlock bootloader and root with magisk
fizzingbees said:
So basically I just have to download and installed viper4android fx 2.7 apk and that's it.
No deep buffer removal or any extra steps or magisk module needed
Click to expand...
Click to collapse
I have done none of them. And it's working like a charm.
There is a Viper4Android module in magisk which is installed but not by me. So I think app is doing necessary things itself.
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
What does it do exactly?
SniperLolz said:
What does it do exactly?
Click to expand...
Click to collapse
Viper4android is an alternative audio driver for Android that offers very granular control over each aspect of audio output coming from your phone.
You can adjust bass, treble reverberations gain etc and many more things with this.
And unlike other sound apps this works system wise.
y.erenbektas said:
You can't use it without root access. But TWRP or any kind of recovery is not needed for things like this.
Click to expand...
Click to collapse
No you don't, I try it and ask me for root
wallah said:
No you don't, I try it and ask me for root
Click to expand...
Click to collapse
Please read it again dude, thanks for agreeing.
y.erenbektas said:
Please read it again dude, thanks for agreeing.
Click to expand...
Click to collapse
Sorry, I was so happy to use it without root ?
My bad ?
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
was using this before and worked well, now doesnt seem to want to install drivers (root granted).
which v4a version are you using?
dj69holland said:
was using this before and worked well, now doesnt seem to want to install drivers (root granted).
which v4a version are you using?
Click to expand...
Click to collapse
Hey, I'm really sorry for this late respond. I'm busy nowadays and just had some time to check my mails etc.
Right now I'm using V4A Version 2.7.1.6. You can find it here.
If you're using Android 10, it's completely normal to have problems with V4A for now. If you're using Android 10 please let me know and I'll explain you how you should install V4A.
y.erenbektas said:
Hey, I'm really sorry for this late respond. I'm busy nowadays and just had some time to check my mails etc.
Right now I'm using V4A Version 2.7.1.6. You can find it here.
If you're using Android 10, it's completely normal to have problems with V4A for now. If you're using Android 10 please let me know and I'll explain you how you should install V4A.
Click to expand...
Click to collapse
thank you.
i had a specific build that worked flawless with android 10, but lost the apk and started then was facing issues with latest apk in xdaLabs (some with installing driver, some driver installed but not processing)
I just went one by one and tried different setups. finally got Team de Witts 2.7.1.0 to work.
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
Please how did you roof & installed twrp?
danbaba said:
Please how did you roof & installed twrp?
Click to expand...
Click to collapse
I haven't rooted myself yet, but on A70 forums there is twrp, magisk and bootloader unlocking guide that you follow
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
loss of magisk
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
helle there
i also installed viper4 adnroid v2.7.1.6 from xda labs . but after reboot i lost magisk root. also the driver didnt worked. on reboot the driver started working ,but the magisk root disappeared.
the only way for me to get magisk root back is to either factory reset in twrp, which will erase v4a ..or to restore stock boot.img which will erase magisk
now i am in this limbo.
if you have some advise to get me out of this mess,kindly post it here
fizzingbees said:
helle there
i also installed viper4 adnroid v2.7.1.6 from xda labs . but after reboot i lost magisk root. also the driver didnt worked. on reboot the driver started working ,but the magisk root disappeared.
the only way for me to get magisk root back is to either factory reset in twrp, which will erase v4a ..or to restore stock boot.img which will erase magisk
now i am in this limbo.
if you have some advise to get me out of this mess,kindly post it here
Click to expand...
Click to collapse
try shuting the phone down. then press and hold volume up and power button till you see the warning screen and then release those buttons. check the magisk again.
y.erenbektas said:
try shuting the phone down. then press and hold volume up and power button till you see the warning screen and then release those buttons. check the magisk again.
Click to expand...
Click to collapse
I am rooted using magisk patched recovery.img. Which was flashed as boot in twrp recovery
Elaborate which warning screen?
I'll try the magisk patched Ap. Tar flashed in AP in odin and then retry this method
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?
If you are asked to update to 25207 from 25206 on canary channel, don't do it! As many people have reported that Magisk immediate crash after the update. If you still want to use 25207, the get the debug version.
Appears the issue has been fixed and hopefully a new version will be released soon.
Fix release build by yujincheng08 · Pull Request #6638 · topjohnwu/Magisk
Fix #6637
github.com
acwcanada said:
If you are asked to update to 25207 from 25206 on canary channel, don't do it! As many people have reported that Magisk immediate crash after the update. If you still want to use 25207, the get the debug version.
Click to expand...
Click to collapse
Just use magisk delta....
Will the update have a new version number?
gpvecchi said:
Will the update have a new version number?
Click to expand...
Click to collapse
Yes, it should.
Unfortunately I've read this topic after the update... And now ?! The app crashes immediately, even if they will make a public fixed version, there'll be no way to update. So for the moment I've uninstalled 25207 and installed the previous 25206...
Anybody have a link to the canary build 25206?
busarida123 said:
Anybody have a link to the canary build 25206?
Click to expand...
Click to collapse
This should be it.
busarida123 said:
Anybody have a link to the canary build 25206?
Click to expand...
Click to collapse
Where is this?
Canary 25208 is out and seems it fixed the crashing issue at least for me. You guys can try it.
You can't hide Magisk app with 25208
Any update on this?
How do we update the hidden magisk app which is crashing and not even opening?
amritpal2489 said:
How do we update the hidden magisk app which is crashing and not even opening?
Click to expand...
Click to collapse
Uninstall it.
Your settings will be keep when you will install the newest version
ShadowJP88 said:
Uninstall it.
Your settings will be keep when you will install the newest version
Click to expand...
Click to collapse
I did the same but now Magisk Installed status is N/A
Can anybody help me out here... I unistalled my hidden magisk canary installation as it was crashing and installed official magisk again but the status is showing as Installed N/A.. tried uninstalling official magisk and installing delta but same issue... I have patched boot.img again and flasshed that but still same issue... How do I resolve it without formatting my phone?
amritpal2489 said:
Can anybody help me out here... I unistalled my hidden magisk canary installation as it was crashing and installed official magisk again but the status is showing as Installed N/A.. tried uninstalling official magisk and installing delta but same issue... I have patched boot.img again and flasshed that but still same issue... How do I resolve it without formatting my phone?
Click to expand...
Click to collapse
This happens a lot when Magisk has been hidden, and there is another instance of Magisk installed. Double check to make sure you actually did uninstall the hidden one. If there are two Magisk managers installed, only one of them will have root access, due to signature verification.
V0latyle said:
This happens a lot when Magisk has been hidden, and there is another instance of Magisk installed. Double check to make sure you actually did uninstall the hidden one. If there are two Magisk managers installed, only one of them will have root access, due to signature verification.
Click to expand...
Click to collapse
How do I check that and uninstall the same as its not being shown in applist in launcher?
You probably have it hidden under another name. You might also find more knowledgeable support in this thread.
V0latyle said:
You probably have it hidden under another name. You might also find more knowledgeable support in this thread.
Click to expand...
Click to collapse
Thanks a lot.. finally resolved