I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
People had this issue a long time. Many reports on 9.0.6 aswell (and prior tho this). Customs saved me from this, I'm on latest oos now and doesn't have any issues (yet I suppose) . I did a format tho when 9.0.7 got released.
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
For me just uninstall it full, flash full rom(optional but I did)
Reboot then install magisk again, hide all app in magisk hide, hide magisk manager and enable core magisk mode only for 1 day and use it after that it become stable
loque036 said:
I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
Click to expand...
Click to collapse
Keep magisk out of battery optimization.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
qbanlinxx said:
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
Click to expand...
Click to collapse
I will install it in both slots to see what happens. Thanks for the advice.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That doesn't work
qbanlinxx said:
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
Click to expand...
Click to collapse
For me, keep magisk out of battery optimization solved my issue.
loque036 said:
I will install it in both slots to see what happens. Thanks for the advice.
Click to expand...
Click to collapse
How's it been working for you?
qbanlinxx said:
How's it been working for you?
Click to expand...
Click to collapse
No issues so far
Related
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
abati said:
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
Click to expand...
Click to collapse
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
tabletalker7 said:
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
Click to expand...
Click to collapse
Amazing, it worked ! thnx bro
abati said:
Amazing, it worked ! thnx bro
Click to expand...
Click to collapse
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
tabletalker7 said:
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
Click to expand...
Click to collapse
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Barsky said:
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Click to expand...
Click to collapse
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
tabletalker7 said:
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
Click to expand...
Click to collapse
This was a clean install of open beta straight to 17.1.
Barsky said:
This was a clean install of open beta straight to 17.1.
Click to expand...
Click to collapse
Yeah the OP installed 5.1.11. He is still on Oreo. He needs 16.4
hi. i have the same pop up msg after a clean install of 17.1 from here - https://forum.xda-developers.com/gr...om-lineageos-17-0-galaxy-grand-prime-t4034919. magisk was not preinstalled on this rom.
my phone specs - samsung galaxy grand prime
sm-g530h - A.P - XXS2BRLI
CP - XXU2BPB2
MSM - 8916
i tried removing assert line from udater script and reflashed ( clean install again). but the pop p appears still. any ideas how to get rid of it? thank you in advance.
I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?
You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager
Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
No problems here.
b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.
michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.
https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
i did clean install of the recovery image this morning. all seems fine. nothing visually different
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
208.9mb too! Quite large for just a small incremental update too!
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.
Aren't you supposed to boot system before flashing magisk?
Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs
Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.
Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.
Anyone try to sideload the OTA? I believe the file is too big to sideload?
lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.
Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.
Since i got my oneplus 6 i've had magisk and twrp running on it, the last few times the os has updated i get a bootloop wich i've managed to get out of in the past by running magisk remover and reinstalling magisk, although i confess to stumbling my way through that and do not seem to be able to reproduce the effect this time, i'm currently running oxyOS 9.0.7, no magisk and twrp blu spark, any help would be greatly appreciated in getting magisk back on my phone without bootlooping again.
the current version i should be running is 19.3
paul0909 said:
Since i got my oneplus 6 i've had magisk and twrp running on it, the last few times the os has updated i get a bootloop wich i've managed to get out of in the past by running magisk remover and reinstalling magisk, although i confess to stumbling my way through that and do not seem to be able to reproduce the effect this time, i'm currently running oxyOS 9.0.7, no magisk and twrp blu spark, any help would be greatly appreciated in getting magisk back on my phone without bootlooping again.
the current version i should be running is 19.3
Click to expand...
Click to collapse
After updating OOS you need to re-flash TWRP (stock recovery after OOS update), then Magisk.
What Magisk modules are you using? Most likely the issue if you did what I mentioned above (unclear from your post.
Not many modules, vanced youtube, a call recorder, i honestly can't remember the others, when i get this fixed I'll tidy it up.
To be honest I only wanted magisk for YouTube vanced and installed it before I knew there was a non root option.
PS, I did flash TWRP then magisk, it's been working since I got the phone the week they came out, but the last 2 or 3 software updates have not been smooth like they used to and I get a bootloop
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
ImperatorShade said:
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
Click to expand...
Click to collapse
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
strongst said:
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
Click to expand...
Click to collapse
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
ImperatorShade said:
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
Click to expand...
Click to collapse
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
strongst said:
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
Click to expand...
Click to collapse
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
ImperatorShade said:
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
Click to expand...
Click to collapse
And are there any magisk modules or mods left? It can be the reason for this.
Are there any errors within the log while flashing?
You have the twrp guacamole unified from mauronofrio 3.3.1-70, right? You can try 3.3.1-73 if you want.
There were no errors when flashing. But I'm not sure whether I had disabled Magisk Modules before flashing OxygenOS 10. Anyway, what would be the best way to untwrp and clean flash?