So my phone was running very well. Because I am using magisk I cannot get adaway to work since the systemless only seems to work with supersu. I rebooted into recovery flashed a module I found through magisk manager for an ad blocker and when I went to boot it gave me a memory dump ( don't really get what that is ) now it is just booting. It is at the boot logo for about 10 min. I don't want to flash a stock image and restart. This phone is so stupid. I have never had a phone just not like a flash. And I have had to flash this one like 10 times already to get it working. Then it broke. Any ideas on if I should wait longer or what I can do to fix it.
Related
Been unlocked and rooted since day one. Have the latest TWRP, Magisk 19.5, Smurf kernel, and the latest stock PIE installed. Suddenly I cannot boot to recovery. When I try, it boots to fastboot.
I went to Magisk manager and ran the TWRP installer. It said it installed to both slots. Still can't get to recovery. I haven't done or installed anything differently. The only thing I can think of is
updating to Magisk 19.5 through the Magisk manager. I don't recall if I have booted to recovery since then. I do have the option to install Magisk to the inactive slot, but then the phone will boot to
that slot. I don't want to try that without some feedback from here, as I won't be able to boot back to the current slot without being able to boot to recovery. Everything on the phone is
perfect, all the root apps work, etc. I simply can't get into TWRP. The TWRP folder shows up in root explorer. Any suggestions would be greatly appreciated!
Google pixel 3 Android 10 (blue line)
Because of a module I've already installed which my phone didn't like (which is causing the boot loop) I can't get into my phone when I enter through the magisk boot img and have to stick with my non rooted img. Any help on how to delete a module without having magisk? (ALREADY TRIED GETTING RID OF DATA IN MAGISK SETTINGS!)
See this thread.
https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433
Ok, so I had to reinstall my OS through TWRP (2GB Full update)... and rebooting to the Bootloader to reinstall TWRP and rebooting again, I want to install Magisk again.
When I install Magisk through TWRP and reboot, the boot animation is stuck forever and animates very slowly. The only way to get out is to press VOL UP + POWER and inmediately VOL DOWN + POWER to enter TWRP. To fix the stuck boot animation I have to reinstall the full OxygenOS update and reinstall TWRP.
My problem is that I'm in this vicious cicle where if I install Magisk it doesn't work and I have to reinstall the OS and TWRP.
What am I missing? Why Magisk is making my device stuck on the boot screen?
Any help will be appreciated. Thanks!
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
skymera said:
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
Click to expand...
Click to collapse
So let me make sure I understood you. I need to switch to Slot B and also install the OS and Magisk?
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Deses said:
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Click to expand...
Click to collapse
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
dennisgrue said:
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
Click to expand...
Click to collapse
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
skymera said:
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
Click to expand...
Click to collapse
I decided to give up too... Was a bad mistake. I accidentely rebooted the phone after the update today. I will never do that mistake again
That dreadful moment when you have this problem again and googling points you to your own thread with no solutions.
UPDATE: Oh I think I got it! I had to uninstall Magisk Manager AND flash Magisk Uninstaller zip, reboot to OS, reboot to Recovery again and flash Magisk 20.3 again and it finally worked! No more stuck slow boot animation.
Probably the two reboots aren't needed, but I like doing things slow.
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!
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.