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
Related
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
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?
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
I have a question... I have 2123 not 2125. Previous i have c38 eu but now I just update to c40 global and next c44 thought the updater. I need to re root I need to install install the boot.img from global? In the info my device is still 2123
Nope. You are good
Poloasis said:
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
Click to expand...
Click to collapse
I got that update as well. Is it Android 12 or still 11?
Thank you
netgar said:
I got that update as well. Is it Android 12 or still 11?
Thank you
Click to expand...
Click to collapse
12
Just installed it. Looks like gcam access to all cameras is restored.
Poloasis said:
12
Click to expand...
Click to collapse
Thank you. So I guess I can't just root as always.
Have you been able to root it?
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
alpadie said:
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
Click to expand...
Click to collapse
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
davyleggend said:
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
Click to expand...
Click to collapse
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
alpadie said:
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
Click to expand...
Click to collapse
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
davyleggend said:
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
Click to expand...
Click to collapse
Okej thanks for the info. I'l will wait for when we have root
Installed C.44 EU over C.38 EU using local update app, latest Magisk Alpha, and keep root using the Magisk OTA option before rebooting after the update.
No need to unroot to upgrade
i went from c.39 to c.40 the day before yesterday. i used mlgmxyysd's tool to flash c39's stock images to the device then updated through the updater.
found the flashed boot image, flashed it (just like the old way, fastboot flash boot.img).
i then installed c.44 ota, went to magisk, installed it to the inactive slot, rebooted, and it ran fine.
with magisk alpha, you don't need the toolbox anymore (i believe)
Anyone have problem with haptics on c44? Haptics feedback is just missing on some menu actions.
Looks like an issue with work profile. Work apps such as MS Teams forces closed and an 'IT doesn't allow multiple users' toast notification pops up. Dang!
Damn... I better stay with A11
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
funkyirishman said:
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
Click to expand...
Click to collapse
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
hallo dare said:
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
Click to expand...
Click to collapse
I don't have a work profile but use certain apps like ms authentication and rsa secure I'd to log in