I've just updated my Oxygen OS to 10.0.2 by flashing the OTA via TWRP.
I was following the guide found here https://forums.oneplus.com/threads/...10-0-1-update-keep-twrp-magisk-guide.1118577/
However, after flashing Magisk I get stuck in endless loading on the Oneplus boot screen. It seems like I can get out of it by switch boot slots, either A or B depending on which slot I was on when I flashed the OTA.
The end result when I get back into the system is always no root, I've either had no Magisk manager installed, or if I do have a Magisk Manager, Magisk is not installed and I cant seem to flash it via the manager.
I am at a total loss, this whole Slot A nd B thing confuses me and I've got no idea what I'm doing wrong... Should the OTA be on slot A and Magisk on B, or is it both?
Hoping someone can guide me in the right direction, wish I never updated at this point.
I do the updates through regular OTA and magisk so no clue if it relates but the only time it bootlooped for me was when i had my magisk modules still enabled before updating. There are a few that cause issues there.
There are plenty of guides here as well that should cover these kinds of issues
Pretty sure that updates go to the slot that is inactive at the time if installing the update
I screwed something up updating to 10.0.2 as well. I've messed it up a couple times so I can't remember if I fixed it or just started from scratch with the msm tool.
I would go to twrp and make sure you are on the same slot that boots.
Flash magisk and reboot. Now hopefully it boots with root.
Download the full update and install it via local update, don't reboot. Go to magisk and install on other slot (after ota).
Or backup everything you can and start from scratch.
Thanks all, I got it to work by simply flashing the Factory image and restarting from Scratch.
In doing so I think I was able to re-create my issue, after re-rooting and installing my apps... It seems like my Magisk module Pix3lify was not playing nicely, and once removed the endless rotating circles went away and the system booted normally and with root.
As I had this module installed while trying to upgrade, I suspect that this was always the root cause.
The lesson here is to disable or remove your Magisk modules while you're updating!
Related
Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.
This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
You need to boot into system before flashing magisk.
watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.
Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
You can try to flash the Magisk uninstaller in TWRP and see if it fixes your issue. Maybe you lost root on one partition and some Magisk modules that are still installed are putting your phone into a bootloop.
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Mgssidley said:
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Click to expand...
Click to collapse
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
djsubterrain said:
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
Click to expand...
Click to collapse
I'm actually on stock and doing an OTA update. After it booted up I was able to install the update, A/B retention script, and Magisk (to inactive slot). It rebooted successfully after that, should I still be concerned about a broken slot?
Edit: On closer look, Magisk did not install properly and I'm unable to access internal storage from TWRP to reinstall it.
Mgssidley said:
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
Click to expand...
Click to collapse
You didn't install the ota but you installed magisk to inactive slot?
Hello everyone! Thanks in advance for taking a look at this thread.
I recently upgraded from a Pixel 2 to a Pixel 5 and decide to root my old phone and mess around with that before doing the same with my new phone. It's been several years since I've messed around with rooting a device, so I've spent some time this week refreshing myself on how to do so.
I've already unlocked my bootloader, but the main issue that I'm running into is when I try to install TWRP or Magisk. For some reason, when I try to flash TWRP (version 3.3.0.0), I've managed to install it properly but loading into recovery mode just leaves me stuck at the TWRP splash screen, while booting directly into it doesn't allow me to backup my data (kicking out an error 255 each time). It would be nice to have TWRP to be able to back up rather than starting from scratch each time, even if I've gotten quick at flashing the stock image when I screw up later.
As for Magisk, I've tried flashing the patched boot image through TWRP and received errors (size of image is larger than target device) as well as the .zip file which just caused a bootloop. I know you can install Magisk without TWRP, so I've tried doing that as well. I've been working with both Magisk 23.0 and the Canary build with no luck; after patching the boot image and attempting to flash it using fastboot flash boot magisk_patched.img, I just repeatedly get an error showing "FAILED (remote: 'Error flashing partition')".
So far I've not really been able to find any solutions on how to fix this, so I feel a bit stuck at this point (and definitely questioning my ability to just follow directions). Any advice on how I might get around these errors?
Hello mate,
With regards to installing twrp, I think there is a workaround in the official twrp thread to get twrp installed with working decryption and working pin by rolling back to a pie build prior to encryption being broken for twrp. Personally I just fastboot it when needed to flash anything but sadly twrp back ups don't work (I'm on A11).
It sounds as if you have tried to install magisk a few ways but I found the simplest way was to install the latest magisk.apk then rename it to magisk.zip and flash it via fasbooted twrp.
It sounds as if you tried patching the image etc so may pay to reflash the stock boot.img and then do the APK/zip method to get magisk running.
Lastly, if you don't mind losing your data it may well pay to reflash a full stock.img and then try magisk again. It's solved a few dramas for me when stuff didn't seem to work first time round.
Hey there,
so I've rooted my S10 (SM-G973F) with magisk about 3 months ago, and it worked fine for quite a long time.
Just recently I tried to install the magisk LSPosed module, after about a week I rebooted my phone and was stuck in a bootloop.
I tried to access my Phone via adb but I couldn't fix it, then reflashed the Stock Firmware hoping it would fix it, which actually did, just to be stuck without root now.
Every time I try to flash magisk via Odin, my phone won't boot up properly and displays the message "OS couldn't be loaded" or similar.
If I then Flash the Stock Firmware again, everything works just fine.
Please let me know if you have any idea of how to fix this problem.
(Sorry if I posted this in the wrong place or something, I'm new here)
You probably flashed a recent firmware with a more restrictive security system. The only thing that keeps your device from booting is that it checks boot.img for modifications, you can wait for magisk update (or use canary builds), or try a custom kernel, if it can boot, then flash magisk.
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).