Magisk V6 is no longer working (permanently lost root) but Magisk V7 bootloops. - Magisk

Since about an hour ago, I have lost root with Magisk. I have reflashed Magisk V6 and phh-superuser-17 to no avail so I decided to upgrade to Magisk V7. I reflashed the stock system, boot, and vendor images and let my device boot with that, then I rebooted back into recovery and flashed Magisk V7, and it just bootloops. This is with a Nexus 6P on the October patch level.

I had a similar problem on a Note Edge. I had to flash the latest Magisk Uninstaller via recovery, and then install V7 to get it to work.

Related

absolute cluster**** after attempting to move from 4.5.0 to 5.0

So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0

Magisk v15 problem on S7Edge

Hi, when i updated Magisk from 14.5 to 15 phone stuck on splash screen for few time after that i have bootloop. I have restore boot image in recovery and gry again but problem still is the same. Now i have problem with instalation modules and root access. "Magisk is not active" while i install module and i have non stop prompt for accessing root. What's now?
In v15 an Bug was introduced which causes the bootloops. An fix is on its way. Just flash the fixed version and all errors should be gone
Updated done! On v15.1 everything is Perfect
S7 Edge - TAPATALK

Magisk bootloop. Messed up my phone

Hello guys.
I have a Zenfone 2 Z00A running latest LOs14.1 Nightly
Yesterday I installed three modules for Magisk. Night light and Android WhatsApp emoji.
Night light is useless so I uninstalled after trying it. So far so good.
I activated the WhatsApp emojis and rebooted the phone but the phone never booted again, it entered bootloop...
First thing I did was uninstalling Magisk through TWRP. It also bootlooped. So I installed magisk and the Magisk Module manager and
tried deactivating the module viaTWRP but it still bootloops.
I extracted the boot.img out of the latest lineage ROM and flashed it but it also didn't work. Dirty flashing the latest build of lineage doesn't work... I think it is because it runs a Magisk script at the end of flashing. I don't want this script to run
What I did was run the uninstall .zip and dirty flash the ROM again. But now I can't dirty flash because of TWRP Error 7
I'm going crazy, nothing works... It just bootloops.
Please help

K20 Pro China ROM Magisk Bootloop Problem

Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.

Magisk lost root after upgrade

I updated my magisk manager to the latest version 22000 and i lost root after I did direct install, I tried flashing the patched boot image with fastboot and I also did a clean flash of my phone and replaced my stock image with the patched boot image but magisk manager is still asking me to install magisk, I also tried with the latest canary build but same thing, I'm frustrated already.
My phone is Itel A11 running Android 6.0

Categories

Resources