yashsingh1/xdaforums huggingface dataset:
[Magisk] Dacraun:
This morning, waking up I recieved the notification that a new magisk manager is available. I installed it as usual, except this time my device suddenly was not rooted anymore.

Si I press the install magisk button that pops up, it flashes magisk, and BAM. Phone restarts, and boot loop.

The phone's a OP5, android 7.1.1, and I had to do a factory reset twice before it would boot. Even using the magisk uninstaller did yield no results.

How come the phone suddenly got unrooted? Can I safely root it again now? Why wouldn't the first factory reset get it out of boot loop?

How can I prevent data loss in the future? Help?

Update 1 - Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.

So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)

Update 2 - TimMayle managed to run the uninstaller and re-flashing magisk v17 on TWRP, try this if you have the issue. (While the uninstaller wouldn't work for me, that might be a device specific issue.)

Update 3 - Thanks void74 for another potential procedure that might fix your issues.

Update 4 - Thank you Shampinger for giving ups a Linux-specific variation on the steps to follow.

Update 5 - While a fixed version is being perfected, Mangraviti summed up what you should do:

Update 6 - If you have Wi-Fi issues after update v17, you can attempt what TAJ_Rocks has found out:
[Magisk] shobhitk:
+1.

Exactly the same issue. The phone lost root and is now stuck in bootloop. How to recover? Any hopes of saving the data?

Please throw some light....
[Magisk] gsosna:
Same issue here... bootloop after update. I wish I didn't update.

Oreo 8 on Huawei Nexus 6p.
[Magisk] icecreamplane:
Same here on HTC U11 with Lineage 15.1

Feels bad man.

How do I fix?
[Magisk] :
I fixed bootloop by uninstalling magisk with magisk uninstaller. After that I installed v16
[Magisk] Didgeridoohan:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
[Magisk] fpaolo2003:
Same here (bootloop) after update from 16 to 17. I used unnistaller but ended in fastboot after reboot :laugh:

Had to install rom and v17 to work.

Redmi Note 5 Pro MIUI 9.6.4.0 Global
[Magisk] startwostroke:
Same thing on s7 with Android 7.0 , now I'm resetting the device.
[Magisk] Dacraun:
Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.

So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
[Magisk] ZioArturone:
Mi Note 3, MIUI 9 Xiaomi eu.

I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.

But now I am unrooted.

What can I do?
[Magisk] Dacraun:
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.

See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
[Magisk] TimMayle:
Hello,

I was on Magisk 16 and probably Manager 5.8.3. (Xperia Z3C on OmniRom).

Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.

Then I was in bootloop.

In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.

Bootloop Gone ! :)

Tim
[Magisk] gsosna:
Yes. That's exactly what I did. OK. So I now ran magisk uninstaller, booted fine. Then installed clean v17.0 and it works now - no bootloop. Many thanks!
[Magisk] edkmho:
I am having the same problem with magisk manager 5.8.3 + v16 zip. After upgrading to v5.9.0(138) all my previous setting all gone. Plus i can install v17 zip at all.

This is on HTC U11+ with android v8.0
[Magisk] TAJ_Rocks:
Same for me had bootloop on android 7.1.2 i was on magisk 16.0 stable. I got notification before an hour. I upadted the apk and it showed magisk not installed. So i downloaded the zip and flashed 17.0 stable zip and had bootloop. So i just cleaned cache and dalvik now phone is started and root and magsik working. But now wifi is unable to switch on
[Magisk] gkmac:
Also got a bootloop on my Samsung Galaxy S4 jfltexx running Resurrection Remix v5.8.5 (Android 7.1.2). Fortunately I took a TWRP backup before this upgrade and was able to restore it.

But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip

Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
[Magisk] startwostroke:
I'm in the same situation with a s6. After another device (s7) has a bootloop I don't think that i flash the v17 from the manager
[Magisk] Dacraun:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

In "Downloads" you have "Latest uninstaller" go to recovery and flash the zip, that should uninstall magisk.
[Magisk] ZioArturone:
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.

It didn't work, I am unrooted.

This update ****ed up all...
[Magisk] Dacraun:
Check the first post, I quoted someone flashing the uninstaller and flashing v17 again and it worked. Maybe that'll work for you?

I do suggest doing a total backup in twrp first though. Just in case.
[Magisk] SignetSphere:
Same here J7 prime bootloop on magisk 17. had to revert to v16.
[Magisk] Donaghy:
Yup, same here. OnePlus 5T. Woke up to the update, downloaded it, flashed it in TWRP, bootloop. Couldn't even get into recovery anymore through hardware buttons. Fastboot worked though, so I flashed the most recent Blu_Spark TWRP via ADB (I was on a much older version of either Blu_Spark or Codeworkx, don't remember... could've been the issue), and now I'm able to get into recovery again.

I'm currently pulling some files off my phone just in case, and I will then use the Magisk Uninstaller to remove Magisk in TWRP. After that, I'll flash Magisk 17.0 from TWRP, as suggested in this thread, to see if it works.

Massive turd by Magisk, though.... Not a good look at all.
[Magisk] Denggie:
the same problem, but my problem was solved after I installed the uninstaller and then deleted the cache & data, then reflash the latest magisk 17, when finished, delete cache & data, then reboot system
[Magisk] Donaghy:
I can't even install the uninstaller or Magisk Manager for TWRP. Flashing either of the two zips gives me an error message stating that the Uninstaller could not be installed because no Magisk is present on my phone or the version in not supported. I literally have nowhere else to go but wipe my phone completely.

Gotta say, I'm pretty ticked off at Magisk right now. Putting it mildly.

EDIT: Factory Reset in TWRP fixed it, even though my phone bootlooped once in the process of booting. Eventually, it booted the phone without issues. I'm now in the process of setting my phone up again (sigh). It's like OP says though: Magisk 17.0 IS suddenly installed on my phone, after the factory reset! It's just there...
[Magisk] AtZ SpeKtruM:
I just wake up and see the update i've just wanted to download the zip only magisk v17 and flash it with TWRP but since my phone is unrooted i don't have a TWRP anymore and my phone is not rooted but the problem is i have modules activated and substratum themes activated so i can't disable them because i didn't have the root. And if i want to reroot my phone and flash magisk again over my magisk modules and substratum themes that's gonna brick my phone for sure. I don't know what is wrong but that's really weird i loose the root without touching anything
[Magisk] void74:
I faced this problem too this morning.

I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:

- volume up and then boot to TWRP

- copied magisk uninstall to phone memory

- installed magisk uninstall

- rebooted in fastboot/bootloader mode

- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")

- rebooted to TWRP

- installed magisk 17.0 zip file

- rebooted to system, all OK! :)

Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it! :)
[Magisk] amkiller:
Bootloop here on a OnePlus 3 too. Flashing the uninstaller then reflashing v17 seems to have worked though.

I have no idea whether this will work or cause you more issues but have you tried flashing v16 from TWRP? Flash it, uninstall it, flash v17.
[Magisk] jackgreyhat:
I can confirm this works one a OnePlus3T running Lineage 14.1

Using the following steps, after bootloop has occured:

- Download the uninstaller, as well as the latest version of Magisk from the following post: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

- Enter TWRP on your phone

- Install the Magisk uninstaller

- Delete Dalvik/ART cache

- Reboot and check weither your phone works again. It should be unrooted, but working.

- Reboot to TWRP

- Install Magisk v17

- Delete Dalvik/ART cache

- Reboot

I am now fully rooted on v17, bootloop solved.

Goodluck everyone.
[Magisk] TAJ_Rocks:
After bootloop i tried install magisk 16 and then it bootloop so o tried uninstaller but it gave me error 255 then i just installed magisk 17 and cleaned cache and dalvik. Phone is back to normal but my WIFI isn't working. What should i do any suggestions

Im on ViperOS 7.1.2
[Magisk] funkyirishman:
On one plus 5 on resurrection remix oreo rom updated and got bootloop had to restore and now unrooted
[Magisk] ang3l:
Glad I was not alone, but I'm also very upset.

The uninstaller from #18 worked on my Xiaomi Mi Mix2 so I only wasted 1h30. Phew!
[Magisk] Donaghy:
That would've been a good option to try, thanks for the suggestion! But I just proceeded with a factory reset, which appears to have fixed the issue. Now I just have to set my phone back up again. Good thing it's Saturday..
[Magisk] AntiDroid:
Same thing happened to my Galaxy S6 (Stock 7.1) and my Xperia Z1 (Custom 8.1) and I was only able to fix my Xperia Z1 by using the uninstaller. My S6 kept doing random stuff.

Edit 1: My Xperia Z1 now even boots with Magisk v17:

- Installed v17 via TWRP.

- Stuck with boot loops.

- Flashed the latest uninstaller.

- Installed v17 via TWRP again.

Success.

Edit 2: Same solution also worked for my Galaxy S6.
[Magisk] funkyirishman:
Is it best to uninstall magisk manager download zip file and load up via recovery to get root?

I'm on a custom rom so do I need to re flash that first and then magisk either this version or 16?
[Magisk] default50:
I'm on LOS 15.1 on a Nexus 6 and upgrading by flashing the zip from TWRP it happened to me.

Fixed it by:

1. Going to TWRP and flashed the latest uninstaller.

2. Rebooted into system and confirmed all working fine.

3. Went back to TWRP and flashed Magisk 17.0 from zip and all ok.
[Magisk] fardeenah:
i flashed the majisk uninstaller 17

then reboot

then back to twrp and flashed magisk, it worked

i just can't pass cts profile on my RN5
[Magisk] Little_Qiu:
I have the same issue with Xiaomi Redmi 4 Pro(markw).

RR 6.0.0 Unofficial, Android 8.1.0, bootloop after install Magisk v17.0.

I upgraded my Magisk Manager and it says Magisk is not installed on my device(but I have already installed Magisk v16.0), I pressed Download Zip, then I rebooted to the TWRP , flashed the Zip pack, reboot to the system, and it happened.

I have to uninstall it. What should I do?
[Magisk] dzidexx:
Bootloop for me too.

Nvdia K1 Marschmallow.

Restored backup, sfnet & cts are OK with Magisk 16 & MM 5.9.
[Magisk] crimescrawl:
I got a bootloop on my Huawei p20 lite (eu version if that matters). Fixed it by uninstalling magisk and reflashing the update. Not a huge deal since it was easy to fix but still I would expect the 'stable' branch to be, well, stable.
[Magisk] angelofskies:
Same issue with same workaround: use magisk uninstaller and reboot to see if the phone start normaly and reinstall magisk v17. Tested on nexus 4 and nexus 5x with lineageOS 15.1.
[Magisk] ZioArturone:
Using the latest twrp Uninstaller, then rebooting system , verifying MManager was gone and then installing Magisk 17.0 via twrp worked on my devices (4 different devices with Marshmallow, Lollipop and Oreo).
[Magisk] Shampinger:
Same issue here on Redmi Note 5 global (whyred). Thanks to this thread I could fix it.

Steps (on Linux):

1. boot into fastboot (vol down + power)

2. from folder with your twrp zip run:

sudo fastboot boot twrp-x.x.x-x-whyred.img

there might be an easier way to boot into recovery without having to use the zip on your computer that I don't know about

3. copy Magisk uninstaller and Magisk v17 to phone (if not already there)

4. flash uninstaller zip

5. go back and flash Magisk v17 zip

6. reboot
[Magisk] metalboyz:
thanks bro.. solved my problem.

got bootloop after updating from magisk manager

i've tried using magisk uninstaller before, but got stuck on the boot logo.

then i tried install magisk 17 from twrp, and it's start booting right now
[Magisk] ninrocket:
ZTE Zmax Pro. Bootlooped. Going to try the uninstall and reinstall. FOCK.
[Magisk] startwostroke:
Fixed! I uninstalled Magisk with the tool and flash v17 version. (Galaxy S6 Andorid 7.1)
[Magisk] nutsh:
Even better here. Uninstalled magisk via twrp, now my phone is encrypted even though it never was.. Like wth is going on
[Magisk] Termi93:
I am stuck in a bootloop too.

Running RR6.1 on my Galaxy S5 KLTE

Update:

Got rid of the Bootloop too by uninstalling Magisk via the uninstaller .zip file.
[Magisk] TAJ_Rocks:
I uninstalled the magisk but still my wifi isn't working what should i do flast the rom again?
[Magisk] djcoolguyno1:
mine stuck on constructing environment

tried all method
[Magisk] ninrocket:
"! Cannot access /data, please uninstall with Magisk Manager"

Updater process ended with ERROR:1 Error installing zip file.

Well NOT what I wanted to be doing on Labor Day Weekend. FOKKKKKKKKKKKKKKKKKKKKKK!!!!!!!!!!!!!!!!!!!
[Magisk] jsc68:
update 1.7

had the issue this morning.. after the update i couldnt boot phone anymore (it restarted itself each time after boot)

(wiko fever)

steps to fix

downloaded both latest stable uninstaller and installer (1.7)

used the links found in topic <<Sticky: [2018.9.1] Magisk v17.0 - Root & Universal Systemless Interface [Android 5.0+]>>

then moved both files on phone

and installed the uninstaller from TWSRP

then i was able to boot my phone again (root acces lost as expected)

then rebooted in recovery mode TWRP and installed the 1.7 version

after install i was able boot my phone without any issues (regained root acces)
[Magisk] Rino_:
This solution also helped on my OP5, thank you very much. A very simple solution. I was already afraid of a complete reinstallation.
[Magisk] nutsh:
In the end had to restore from backup AFTER wiping DATA... Other wise it was encrypted even though I have never enabled encryption.. thank god I keep all my important **** on cloud and backup was only 3 months old...
[Magisk] hbenz2008:
frustrating for sure, but whatever i guess we signed up for this isht lol as some mofo said recently

Did u use the latest uninstaller? stay cool , you will get it resolved. I had to restore a couple weeks old ack up early. Didnt have time to bs with it.
[Magisk] alphasierra26:
Same here (Nexus 7). Got out of bootloop by uninstalling Magisk, but now Wifi is dead -- with or without Magisk 17 and even after re-flashing the latest rom.
[Magisk] TAJ_Rocks:
Same i did flash rom again but still wifi iss dead
[Magisk] JasonVaritekMVP:
OK guys I definitely need some help here. Pixel 2. Same issue as you but after being unable to boot to system (again) I then flashed all to try and get myself working again. Phone still doesnt boot and now I get a "Can't load Android system your data may be corrupt if you continue to get this message you kay need to perform a factory data reset and erase all user data stored on this device."

Any suggestions? Any help is greatly appreciated.

Edit: I've been able to get back into recovery and even install twrp again but I simply cannot get system to boot.
[Magisk] :
When I try to uninstall Magisk in TWRP, it shows this red error message: "Failed to mount '/data' (No such process)"

Do I have to format my SD Card, like I had to when first installing Magisk months ago?

I don't have a recent backup so that would f*** me hard. Phone is a Galaxy S8.
[Magisk] ninrocket:
ZTE Zmax Pro User: I tried everything here and nothing worked. I also tried to reflash my entire phone with Discord ROM 1.1, GAPPS, then MAGISK 17. Stuck in TWRP bootloop. Wiped phone for the 100th time and reflashed DISCORD, GAPPS and MAGISK 16 and my phone is back. MAGISK 17 was fragging the bootloader apparently. :|
[Magisk] mddunner:
same issue on moto x pure (xt1575). bootloop after installing v17 update. Flashed uninstaller and was able to boot into system. Wifi is now dead. wiped cache/dalvik and no luck... anyone found a fix yet for dead wifi?
[Magisk] J4jks:
I got my device into bootloop after flashing magisk v17.0.

First I've selected from MM itself there was no error after reboot itbwent into bootloop. I couldn't be able to install Magisk16, thought a module is the culprit but it is not.

I was able to boot fine after installing kernel

dmsg log shows

**********************

* Magisk v17.0 Installer

************************

- Mounting /system, /vendor

- Encrypted data detected, keep forceencrypt

- Target image: /dev/block/mmcblk0p21

- Device platform: arm64

- Constructing environment

cp: can't stat '/data/adb/magisk/.': Too many symbolic links encountered

cp: can't stat '/data/adb/magisk/.': Too many symbolic links encountered

cp: can't stat '/data/adb/magisk/chromeos': Too many symbolic links encountered

cp: can't stat '/data/adb/magisk/busybox': Too many symbolic links encountered

chmod: /data/adb/magisk: Too many symbolic links encountered

- Adding addon.d survival script

Invalid image: not signed

/dev/tmp/install/META-INF/com/google/android/updater-script: cd: line 112: can't cd to /data/adb/magisk: Too many symbolic links encountered

/dev/tmp/install/META-INF/com/google/android/updater-script: .: line 115: can't open './boot_patch.sh': No such file or directory

Updater process ended with ERROR: 2

I:Install took 5 second(s).

Error installing zip file '/sdcard/Download/Magisk-v17.0.zip'

I:Deactivation_Process: Unable to unpack image

Redmi note 3 aex n
[Magisk] mikeyfnbrennan:
Ran into this issue too, and I'm just performing a restore and then proceeding with flashing the rom I preferred. Hoping that then I'll get the magisk 17 downloaded correctly then.
[Magisk] ticotexas:
I am on a OP3 with Lineage 14.1. Same story here. Updated MM. Downloaded through MM. Installed through TWRP. Bootloop. Restored boot from backup through TWRP. Rebooted. No root. Downloaded zips. Uninstalled through TWRP, wiped Dalvik, rebooted, installed through TWRP, wiped Dalvik, rebooted. Now I have root, but no wi-fi! Does anyone know how to get wi-fi back?
[Magisk] Karls0:
Just flash latest uninstaller to make some cleaning before installation of Magisk v17.0. In most cases it's this simple.
[Magisk] mikeyfnbrennan:
You are running 17?
[Magisk] Phuturist:
Just chipping in here.

Ran into the same issue on my ZUK Z2 Pro. Magisk Manager lost root and asked to update to version v17.0. I did so and was not able Flash Magis v17.0 from Manager so I downloaded the zip and flashed it in TRWP. This all went fine but got me in a bootloop. Followed the instructions from the first post and used uninstaller and then flashed Magisk 17.0 again from TWRP. Bootloop was gone but when reconfiguring Magisk (since settings where lost) my phone soft rebooted and was stuck on boot animation. Hard rebooting it also got it stuck on boot animation. Went into TWRP again, uninstalled Magisk again and now installed Magisk 16.0. This got my phone working again. Hopefully the issues will be fixed soon so I can safely upgrade to v17.0.
[Magisk] ninrocket:
They just rolled back the update. I had to completely reflash my ROM, GAPPS, and Magisk16.4 and now I'm working again.
[Magisk] ticotexas:
No, Lineage 14.1. Do I need to flash a firmware+modem.zip?
[Magisk] Donaghy:
What does this mean for the people who are currently running V17.0? Will we be faced with the same issue when they eventually re-push a 'fixed' version and we install that? I spent my entire day re-setting up my phone. Don't really want to do that again.
[Magisk] mikeyfnbrennan:
Sorry meant as in Magisk if you were running 17.
[Magisk] vasyekv:
Sounds like some bug in V17. I have Samsung Note 3 with lineageOS 14. Update from v16 to v17 make boot loop.

I have to recover phone from TWRP and unmark Check for update in Magisk manager. (Update Magisk manager to 5.9 make phone unrooted)

Everything work fine.

I'll wait for better update...
[Magisk] mikeyfnbrennan:
I'd highly assume a hotfix to the current v17 would not have as many problems of the past issues you experienced.
[Magisk] Mangraviti:
The same happened to me. Half of my apps stopped working then I checked Magisk, which showed as "not installed". I downloaded the zip, rebooted to TWRP, flashed the new zip and bang. Bootloop. I admit that I freaked out a little bit.

Then I also flashed the uninstaller via TWRP, booted to Android, rebooted to TWRP and installed the new zip that I downloaded from here. And it works again.

I really would like to know why Magisk simply stops working when there is a new version. It doesn't make sense. Especially that there is a new version out every couple of days. It can be very inconvenient. Last week, I updated twice. Plus, it doesn't work as it initially intended. Nowadays, most apps that required unrooted devices will detect a custom recovery and won't work anyway. I only keep Magisk over SuperSU because of one specific app, that still works with Magisk and won't work with SuperSU.
[Magisk] mikeyfnbrennan:
Are you not experiencing the dead wifi bug by any chance?
[Magisk] ticotexas:
Oh, yes, sorry. 17. I have root back, but no wifi.

I just flashed OP3 firmware+modem 5.0.5, and still no wifi. The wifi toggle keeps turning itself off. (This is so frustrating, because I'm taking a trip and need wifi.)
[Magisk] SilverZero:
I saw the notification to update Magisk Manager to 5.9.0, so I did, then it asked if I wanted to upgrade to v17.0, so I did, but I couldn't reboot to recovery to install the zip (it only gave me the option to download or flash a patched boot image) because I had lost root. Phone was bootlooping when I tried to reboot. Finally got into fastboot, rebooted to recovery, used Magisk uninstaller zip and then reinstalled v17.0, and now I'm booted and rooted. Lost all my modules.

AND, Magisk Manager crashes every time I try to open the Magisk Hide menu. The main screen also says the latest version is v16.0, but my installed version is v17.0. Otherwise seems to be functioning fine.
[Magisk] mikeyfnbrennan:
Hmm, I would suggest just running the latest edition of Magisk before 17 so I just put on my device 16.7 and haven't ran into a wifi dead issue. Especially if you are going on a trip, would just advise you to run a different version till they fix the 17 one.
[Magisk] Mangraviti:
Yes, I did experience the dead wifi. But now with the new install, wifi works again.
[Magisk] TAJ_Rocks:
Im also leaving out of town and need wifi man alot of data in phone.

Wtf should i do for dead wifi tried every way since 6 hours

---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------

What new did u install