Is there still a way to root our phones without using Magisk? I've given up trying to pass safetynet, it never worked even with magisk, and having root is more important to me. Systemless root buys me nothing, but it creates a lot of problems. Every time I need to reboot I need to go into recovery by pressing the button combo. Just today I didn't press the button combination quickly enough, it rebooted without magisk and (despite having flashed the multidisabler, vbmeta, etc) it somehow hosed the recovery partition, such that trying to boot into recovery it would just crash, so I lost root (I have no idea how this happened, really). I had to go back into downloader mode to re-flash twrp, which now works but without Magisk, and I'm still trying to restore things as they were, but honestly, if I could just install SuperSU instead of Magisk it would be so much easier.
Is there any modern replacement for SuperSU, which is unmaintained for years, other than Magisk?
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!
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!
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
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).