Related
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
xtartrackR said:
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
Click to expand...
Click to collapse
flash magisk uninstaller, then reinstall magisk v18 and add one module at a time to understand which one causes bootloop
It worked. Thank you!
Just a heads up next upgrade: disable all (except ROMs maybe) magisk mods, also disable substratum themes before updates. They can make your phone bootloop or system UI crash. Glad it works fine now
For me, flashing magisk uninstall and reinstalling v18 still didn't work. I had to install beta version 17.3 after flashing the uninstall, then I installed magisk manager when it successfully booted and finally updated to v18 through the manager. Not sure why v18 wouldn't work even after flashing magisk uninstall, but 17.3 worked.
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Sepero said:
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Click to expand...
Click to collapse
Have you tried magisk uninstaller and fresh start without any module? In my case one of my custom made module was causing problem because i didn't update it to latest template. Try one module at a time to find the culprit.
You need to disable all magisk modules before doing system update, otherwise it goes in auto shutdown and then you need to flash magisk uninstaller and then re-flash magisk
And remember to remove pin/password lock too
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Mord0rr said:
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Click to expand...
Click to collapse
Format DATA from TWRP then boot to system once and when it's ready you can reboot to twrp to install magisk if you want
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.
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?
As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.
Thanks a lot!
benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
stgibson said:
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
Click to expand...
Click to collapse
FYI Update for others' reference: I got what I needed with Zygisk and DenyList, so should be OK without downgrading. If I need to downgrade, I realized an option that may work: re-flashing the previously-used patched boot.img.