Hello
My phone has been rooted for a while now (without TWRP as it wasn't available yet back when I rooted it), but magisk suddenly got issues once I've tried to update my phone.
I downloaded the update KB2003_11_C.33 as soon as it was available on the Oxyen updater app, then i've proceeded to follow the usual steps to preserve root during the OTA update:
restored image in the magisk app -> started the update -> installed magisk to inactive slot in the app
I don't know if it had a real impact, but this time I've done the update through the settings of the phone instead of through the "System Update" app.
Once the phone turned off and back on, it was stuck in a bootloop (it rebooted maybe 3-4 times) until I pressed the buttons to access the Recovery mode, then I just booted it again and it somehow worked just fine. There seemed to be no issue until I opened the magisk app and saw the message "The hidden Magisk app cannot continue to work because root was lost. Please restore the original APK" then I've also noticed that my OxygenOS version was KB2003_11_C.21 instead of 33, so the update basically failed.
I'm not sure if it matters, but I've recently installed modules (Advanced Charging Controller, BlockAds and Universal SafetyNet Fix), magisk manager was hidden (I had access to the app through a fake "settings" app) and I also had zygisk, as well as the deny list enabled to pass SafetyNet.
I've uninstalled/reinstalled Magisk manager, patched the boot.img with it (extracted from the ZIP of my current firmware) then flashed it with adb (several attempts), but magisk manager just doesn't detect anything as it keeps displaying "Installed N/A". I also tried to update my phone again to KB2003_11_C.33, which worked fine this time around, but patching the image and flashing it still didn't do anything.
I don't know what to do anymore to root my phone, I thought I didn't need to factory reset since the bootloader is still unlocked, but maybe I have no choice now.
I found the issue myself actually, I had no choice but to install unofficial TWRP to properly uninstall magisk then to reinstall it and root the phone.
You can close the thread ^^
Related
I have tried to bypass SafetyNet with my F3113 using the guide to root and the "How to install Magisk" but the creator (rrvuhpg) mentioned something about having the internal memory encrypted and i tried but without luck.
So i decided to open a thread if anyone has a clue to do it or have succeeded bypassing SafetyNet with Magisk´s Root.
I will paste my last experience:
Try to encrypt phone right away (Rooted with Magisk)
It freezes at logo after reboot.
Searched Google and found it hangs at Logo when rooted.
Learned to Hard Shutdown with vol+ & Power.
Unrooted, flashed boot.img, rebooted to system.
Start encryption again, ends successfully.
Rebooted to TWRP and flashed Magisk 12, then rebooted
Opened Magisk manager, Magisk is installed but root permissions not present, still fails at basic integrity &CTS.
Rebooted to TWRP, uninstalled Magisk 12, rebooted and installing Magisk 11.6
Root present, encrypted internal memory, but fails at Basic Integity and CTS.
This is my Newest experience:
Unlocked Bootloader
Flashed with 0.9.23.2 Flashtool 33.2.A.4.70 Stock Firmware
Booting to system, executing SafetyNet test
Test Passes
Flashed boot & recovery from root guide
Booted to system & executing SafetyNet test
Test fails
Installing Magisk in TWRP anyway
Keeps failing SafetyNet
That is how i did but failed any help is apreciated. Thanks.
That's the Google OTA / DM verity reset kicking in when it detects modification.. The next roadblock is Sony RIC
Problems about safetynet checks is related to the way that Google use to check it and the updates of Magisk to bypass it. Generally it works after a new Magisk update until Google update the safetynet test again.
I successfully updated from the August Oreo image to the October Oreo image today and installed the latest TWRP recovery image. Then I tried to install SuperSU (SR5) through TWRP, which seemed to go well, but the app wasn't added to in the app drawer, and none of my apps had root access. I rebooted into TWRP and reinstalled SuperSU (SR5), and still, the app wasn't listed in the app drawer. Then I rebooted into TWRP and installed SuperSU (SR3), the last version I'd installed before the October update that worked, and that didn't get added to the app drawer either. Rebooted, reinstalled SuperSU (SR3) in TWRP, and still, not listed. I then uninstalled SuperSU from Oreo, where it surprisingly was listed, and installed SuperSU from the Play Store. Then I opened SuperSU and it needed to update the binary, which I let it do normally (not via TWRP). Now My phone has been booting with the G logo for the past 10+ minutes. What should I do?
After 20 minutes, I rebooted via ADB and now I'm back at the G loading screen with the colorful G with a moving status bar underneath (not the dots).
After another 10 minutes with the colorful G with a moving status bar underneath (not the dots), I tried to reboot into recovery so I could try manually installing SuperSU via TWRP again. I found that there was no recovery partition installed.
Ended up reflashing the October Oreo update (OPR3), which worked on the first try, then reflashed TWRP, SuperSU, and suhide, one at a time. All of that worked, and now everything seems to be working.... Not sure what went wrong, but glad everything is back to normal and no data was lost!
Why do people still use SuperSU? Magisk is a much better alternative and I don't trust it now it's in the hands of some Chinese company.
I didn't know about Magisk... Wiping and installing now...
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
den_zel said:
Hello,
I use my OnePlus 6 rooted with Magisk since the beginning and had no issues. Today the update to Magisk v18 was proposes, so I installed the update in Magisk Manager and of course didn't do a backup before.
After the reboot the system was not really usable anymore. Every 30 seconds I received the message that the system UI stopped working and it froze for a while.
So I wanted to get rid of Magisk and what I did was:
- boot to twrp and uninstalled Magisk (I didn't use the newest uninstaller, I used the one from September).
- tried to reboot but received the message "Wiping, please wait. Do not remove battery of turn off your phone".
- after some seconds the message disappeared, the screen was black and when I pressed the power button it was vibrating but didn't do anything else.
So my tried to get it working again:
- rebooted to TWRP again
- used the latest uninstaller to uninstall Magisk
- then the OS didn't reboot at all
- once more went to TWRP and installed Magisk 18 again. Then the phone rebooted normally but I got a wiped OS.
My sdcard partition (/storage/emulated/0/) is not wiped, everything is still there.
Is there a possibility to go back to a last "stable" version and continue using the phone with the data on the filesystem?
My thought: is it possible to boot from the other slot (before last update) and would this work with my current data on the sdcard partition? Like this I would just lose the Apps and updates I installed since then, right?
Is there another or better solution?
Thank you and best regards
Click to expand...
Click to collapse
If you can get into TWRP dirty flash your ROM. Otherwise change to the other partition either via TWRP or via fastboot set_active A (or B).
Magisk is only installed on the active partition meaning switching it would let you boot into a non-rooted OS.
Apps etc. should be the same as it uses /data. Only /system and some other partitions are A/B.
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!
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).