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
Related
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
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.
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
So, when I updated from OOS 9 to 10 I forgot to remove magisk and it's modules and completely forgot about it.
When I finished the update I noticed all the emojis where gone and from other posts here I found that it was because of a problem with the reserve partition that could be solved flashing a magisk module. Well, to my surprise, when I tried flashing magisk again on OOS 10 I always got stuck on a bootloop, I tried everything, removing the old modules that where still installed, using different twrp versions, using bluspark kernel, flashing a patched img through adb... But I always got a bootlop after installing magisk.
Since I couldn't get magisk on and was getting frustrated I decided to wait for the next OTA to see if it might fix it, but now that I tried installing it, I get stuck at 89% installation and don't know what to do. It's probably because of the reserve partition where the emoji should be, but since I can't use magisk idk how to fix it.
Is there another way to fix the reserve partition? Maybe a patch through twrp? Will a clean install of some sort help me or will it also get stuck at installation and brick my device?
Any help is welcome!
EDIT: Since noone replied I tried to fix it myself by trying to flash magisk a couple of times again (which gave me bootlops as expected), so I ended up flashing an OOS 5.1 downgrade build (which factory resets your phone so back up your stuff) and updating all the way to 10.3.1 through OTA updates. This fixed both my emoji and stuck update problem, so If you have similar problems and have not had any luck with other solutions I suggest you to downgrade like I did. If you back everything up on the cloud you should be back up and running in under an hour.
How did you flash the downgrade rom since your system updater is stuck?
Go twrp recovery, look for .Ota, flash the downloaded update zip and reboot.(Must be patient for step 2 to complete)
If can't find .Ota, go to File manager app, click storage below, click 3 dot on top right coner, settings, turn Show hidden file switch on
Ive been using magisk for quite some time, rebooted my phone once to check that it worked. Went on for a while without rebooting, decide to reboot it after installing all my apps (no modules), have a couple root apps like adaway and J oneplus tools. Anybody else have this issue, any idea on how to fix it? Im running the latest OOS and the latest Magisk with the most recent Mauronofrio TWRP