yashsingh1/xdaforums huggingface dataset:
[Magisk] ninrocket:
If it ain't broke don't fix it. If you have 17 working I would just consider yourself one of the few lucky ones that were able to get it to work and leave it alone until they re-release 17....probably 17.1.
[Magisk] ticotexas:
I tried flashing OP3 firmware+modem 5.0.4 in addition to 5.0.5. Neither brought back the wifi.

I restored a nandroid backup of the boot, data, and system, and I'm back to magisk 16 and working wifi, thank God. Needlesstosay, I unchecked check for updates in MM.
[Magisk] HighOnLinux:
I'm quite suprised a bunch of people were affected on this. I, myself, was on the OnePlus 6 with OOS 5.1.11 (8.1.0 Oreo) and it gave me a nasty bootloop as well. I'll try out the methods on this thread soon, as it's really helpful
[Magisk] zoneofSAM:
UPDATE ALERT: magisk update 17.1 is live

https://github.com/topjohnwu/Magisk/releases/tag/v17.1
[Magisk] Mangraviti:
I uninstalled using Magisk Uninstaller (zip via TWRP), booted to Android, rebooted to TWRP and installed the version 17.
[Magisk] ninrocket:
ver 5.9.1 with 17.1 still breaking. Will try to uninstall and reinstall Magisk.
[Magisk] jackgreyhat:
Updated v17.0 to v17.1 without issues, using the Magisk Manager v5.9.1 direct install method.
[Magisk] Mangraviti:
It worked for me after a uninstall via TWRP and reinstall via TWRP.

I don't know why though. One thing I noticed is that the phone is considerably slower since the new Magisk.

Using a Galaxy J7 Prime "stock"
[Magisk] ninrocket:
tried using TWRP to get 17.1 working by uninstalling Magisk, Installing 17.1, still bootlooping.
[Magisk] Mangraviti:
Here is what to do, if you HAVE NOT installed the new version:

1) Do not update via Magisk Manager.

2) Do not update via TWRP using the zip you can download via Magisk Manager.

3) Uninstall Magisk using Magisk uninstaller (ZIP).

4) Boot to Android.

5) Reboot to TWRP

6) Install V17 ZIP via TWRP and boot to Android.

If you HAVE INSTALLED and got a bootloop:

1) Download the uninstaller ZIP.

2) Enter TWRP during the bootloop.

3) Uninstall using the uninstaller ZIP.

4) Boot to Android.

5) Download V17.

6) Reboot to TWRP and flash the V17.

7) Boot to Android it it should be working.
[Magisk] jackgreyhat:
Are you clearing cache?
[Magisk] crazedone:
If only it was that simple. Just can't get Wifi to work. Reflashing no luck.
[Magisk] Mangraviti:
In your case, I would try uninstalling again via TWRP and then installing SuperSU.

Have you booted to Android after uninstalling? I mean, without trying to install again and with no root?

---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------

Goodness gracious. We are all doomed. Lol.

Chainfire, please HEEEEEEELP!!!
[Magisk] TAJ_Rocks:
Found fix for dead wifi

Delete this p2p supplicant.conf supplicant made wifi a c#nt:laugh:

Reboot after deleting
[Magisk] crazedone:
Genuis. This works!

Thanks :D
[Magisk] mikeyfnbrennan:
Installed from app its self and rebooted once installed, works for me. and no dead wifi either.
[Magisk] Dacraun:
You might very well be on v17.1 already.
[Magisk] mikeyfnbrennan:
I am, sorry should've stated that.

Not sure if this could help people but it worked for me.
[Magisk] Dacraun:
Did you update to 17.1 from 16.0 or from 17.1 ?
[Magisk] TAJ_Rocks:
Hit thanks button if i helped solve your problem
[Magisk] :
To all of you with a Galaxy S8 who are still in a Bootloop, this is what worked for me:

1 Start TWRP (volume up, bixby, power at the right moment when screen is black)

2 Install magisk v17.1 from here: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

No wipe or formatting required, thus no data will be lost. Good luck.

This will probably work on other devices too.
[Magisk] marusia7:
How to proceed without TWRP Recovery?

I am on HTC U11+ without custom recovery, after update to Magisk 17 I lost root,

MM tells "latest version 17.1", "Magisk not installed".

Should I reflash stock boot.img first and then let Magisk produce patched boot.img or just let Magisk "re-patch" the (most probably) already patch img from v16?

(as I see now that after unsuccessful upgrade from 16 to 17.0 I downloaded 17.1 but did not proceed yet...)
[Magisk] zenos987:
worked for me on my lg gpad 8.3 lineage os, hope this file was not helpfull XD
[Magisk] TAJ_Rocks:
It was useful and caused problem now if u check again the file is back again with proper right and trouble free
[Magisk] Phuturist:
Tried again with v17.1 but with pretty much same result. I can boot but Magisk Hide is not working and the phone soft reboots and is often stuck on boot animation. Back to v16.0 for me.
[Magisk] mddunner:
Had high hopes for this, but didn't work for me on my Moto X Pure xt1575. doesn't look like the file re-generated either, which is odd.
[Magisk] AmjadHi:
Le max 2 magisk v17 boot loop then multiple errors

I got into the same issue of boot loop with Magisk V17 update from v16 on my Le Max 2 with lineage OS 15.1 Only reinstalling superSU by twrp adb side load got me back to boot. Tried the latest magisk uninstaller as suggested in this thread but got “boot image patched by other programs” when I flash to instal. And “cannot uninstall”. Nothing has worked so far . I deleted the uninstall file and magisk manger from twrp and side loaded again using twrp ......but same. Any suggestions?
[Magisk] marusia7:
Got it working:

Uninstalled Magisk Manager 17 and installed Manager 16, reflashed previous patched_boot.img (from v16) and installed v17.1 via Manager with option "direct installation"

Root is back with v17.1, all ok

(I did not have boot loops on my HTC U11+)
[Magisk] Morphello:
In the same situation as you. It seems my only solution will be to wipe it all out and start again.

Edit: ah. I deleted mine from /system/etc/wifi instead of /data/misc/wifi.

I deleted /data/misc/wifi supplicant file and now I have wifi back. Not 100% sure what the damage is to have deleted the /system/etc/wifi but for now it's saved me a clean wipe.
[Magisk] desertcat:
Wow! There was way too much excitement of the kind I did not expect with updating from v16.0 to 17.0 today.

1. Updated from v16.0 to v17.0 - oh no a bootloop - did I mess this up?

2. Check XDA - found that others have the same problem - good, it wasn't something I did.

3. Somewhere between uninstalling v16.0 completely and trying to reinstall v17.0 again, v17.1 available.

4. Successful install of v17.1 (great!)

5. No WiFi (really?)

6. Found a solution in XDA

7. Everything working again - yeah!

Anyway, I would like to thank the XDA community for their all their hard work and contributions.
[Magisk] ripelag:
Google Play unstable after updating 17.1
[Magisk] Mangraviti:
Thanks!

At first, I had no problem with v17. Then I was prompted to update to v17.1 and I lost wifi connection.

Deleted this p2p supplicant.conf and it worked.
[Magisk] Lange_666:
After the 17.1 debacle (i went straight from 15.3 to 17.1) phone completely wiped.

Luckely there is something as Titanium Backup.

But still working on it to set it up again as before.

+1

I can go in and out into the Magisk Hide menu but if select to much or i stay in the menu to long Magisk crashes and my phone then hangs in boot. Only way out is via TWRP and reboot.

(Galaxy S6 7.0)
[Magisk] mddunner:
Quick update from my efforts on the Moto x pure xt1575 - magisk uninstaller fixed the bootloop but I was unable to recover wifi functionality. I performed a factory reset, but the issue persisted. I reflashed the stock nougat rom via fastboot and wifi now works. Flashed magisk 17.1 and all seems well.
[Magisk] TAJ_Rocks:
You should have gone through my fix for wifi. It could have save your phone from factory reset. Hope its solved so go through pages next time :)
[Magisk] mddunner:
Post 106... I did try and unfortunately it didn't work on the Moto x pure. Really wish it had!
[Magisk] amon-san:
my Galaxy Tab S bootloops on a clean install of the upgrade from v16 to v17.1. i will try to provide information if you tell me what you need

up until v17 things always worked fine
[Magisk] atown305:
So I had trouble installing magisk on my formatted pixel. Kept getting bootloop after installing magisk v17 and v17.1. Didn't matter if I tried installing the zip through TWRP, or using a patched boot image. Still bootloop. What worked for me was enabling ADB debugging and then installing v17.1 through a patched boot image.
[Magisk] richinthailand:
Hello ALL, I have 2 phones a Blackview P10000 and a Ulefone Power 3, both of the phones go into bootloop with anything higher than 13.3 even the latest 17.1 is the same..

Any ideas how to fix so I can have the latest version as I dont see any modules on 13.3

Also
[Magisk] jbd7:
Same here.

I was fine with OOS 5.0.4 on oneplus3, Magisk 16 and the Magisk Manager from last month. This week, I updated the Magisk Manager app, and then Magisk Hide menu would behave weirdly: take ages to load, and black screen when I select or unselected one row (only solution here was to press power button for 15sec.).

I thought flashing Magisk 17.1 over 16 would make Magisk Hide work properly again. But what I got was bootloops.

Therefore I guess the Manager app has problems, not only the flasha le zip.
[Magisk] zomgqwert:
Having the same issue on my Pixel XL. I was on an older version of Android with SuperSu so I decided to do a full wipe and revert to stock then install Magisk. I did the wipe, restored everything to stock including recovery and went through the process as if it were a new phone following this great guide. Decided to do TWRP and Magisk, got to the point where I did initial boot to set pin and it worked fine. Loaded back into TWRP to install the Magisk 17.1, ran the installer, log shows no errors, and rebooted to system, but the system does not come up and after a few attempts it boots back into recovery. I am able to run the uninstaller and everything works fine again. Any tips to get around this or ideas on what I may be missing?
[Magisk] Borrisl:
I had exactly the same problem with the Original Pixel (Sailfish). what solved it was: Flashed the latest pie version (9.0.0 PPR2), Went to device settings, changed device security screen lock to none. Booted into latest TWRP, Installed Magisk17.1 WITHOUT INSTALLING TWRP reboot and voila, it boots up.
[Magisk] zosX:
No dice here with or without TWRP installed. I've tried 17.1, 17.2, and now 17.3 Canary.

It bootloops no matter what I try. I took the pin off too and that didn't help.
[Magisk] niccoooo:
i have exactly the same problem with my pixel :-/

I've succeed once (installed vanced yyoutube and greenify) then bootloop, unistal magisk (with offiial uninstaller), then reinstal beta version 17.2 -> bootloop again

(don't want to remove TWRP)
[Magisk] mcgyver83:
Same bootloop issue on nexus 4: updating from magisk 16 to 17 via TWRP makes bootloop.

I tried 17.1 and 17.2 but bootloop still happens.

How can I recover my phone?
[Magisk] FaKK:
Bootloop +1.

Found Magisk 16 here: https://devfiles.co/download/uVZylVXT/Magisk-v16.0.zip

first flashed magisk uninstaller, then magisk 16. worked for note 8 rom on note 3.
[Magisk] Didgeridoohan:
Wouldn't it feel safer to use the official source?

https://github.com/topjohnwu/Magisk/releases
[Magisk] LukaPochi:
Bootloop with magisk 17.1 and 17.3 on Android 9 Xiaomi MI 8 SE... what a shame
[Magisk] jman0:
I have the same problem onm a brand new ZTE Nubia Z17S. Only way to make it work is using Magisk 16.0. Will have to wait.
[Magisk] jman0:
I just managed to solve it. I used latest uninstaller and it apparently uninstalled Magisk 16.0. But then the phone refused to start. After reverting back to the stock rom and then flashing TWRP again, I was able to flash Magisk 17.3. This time, I had no bootloop, but the phone hanged on bootanimation. After rebooting to recovery and wiping data, the phone finally started. Now I have Magisk 17.3 fully working (SafetyNet test ok) and the phone is rooted. The only problem is that I now have to restore the phone to where it was before, but fortunately I have Titanium Backup and all my apps will be back in no time.
[Magisk] kimpoi:
Thanks for your advice.

My phone Asus Zenfone Selfie ZD551KL Encrypted.

Android 6.0.1

Follow your advice, I only got 2 bootloop.

After that, everyting runs normally.

Works great.

:good::good::good:
[Magisk] KHDaze:
Through feverishly banging my head against the wall with various attempts, it does seem like the trick is to just install the 17.x (17.1 currently) and ensure you've unchecked the "Reboot after finished installing" in TWRP. Once it finishes, wipe the cache and reboot. Golden.

---------- Post added at 02:03 AM ---------- Previous post was at 01:48 AM ----------

Nope. I'm dumb. I did get it to work just fine after installing the Havoc ROM though.
[Magisk] Crescendo Xenomorph:
the problem of bootloop is actually there's orphaned inode in your /data partition that needs to be manually fixed via TWRP > Terminal...

mine's always bootloop after updating/installing/removing any modules.

fixed with this command: e2fsck -f -y /dev/block/dm-0

reboot > OK

but this is PITA... dunno ehy it's happening, maybe my memory chip gone bad...
[Magisk] jayesh9920:
In my mi max 2 I am facing bootloop after upgrade magisk manager.

But thanks to you i flashed boot.img and install magisk manager again and it's work .
[Magisk] jbd7:
Many thanks to topjohnwu.

I had bootloops and the MagiskHide menu would always crash with Magisk 16 and 17.*, but I'm all good again with Magisk 18 and MagiskManager 6.1 (on OP3)
[Magisk] poida97:
Stuck in a bootloop after the update here too.

OP5, cannot flash any version of the uninstaller via TWRP - message is "Unable to unpack boot image".

Starting to get very worried...
[Magisk] dgizyn41:
Also stuck in bootloop right now.

Brand new PIxel 3 XL flashed Magisk 18 via twrp and reboot into boot loop..
[Magisk] Axelay.mk3:
I'm in a similar situation. New Pixel 3 XL running a stock ROM which has been rooted via Magisk. The very first time I attempted to install it via TWRP, it bootlooped my device even though I followed instructions to the letter. I wiped everything and started all over again, and it worked the second time. Don't know why... I've been using the phone for about a month now, and I'm almost deathly afraid to update Magisk Manager even though the OTA prompts are starting to come through twice a day. Has anyone found themselves in a situation where they were running a rooted stock ROM and ran the OTA update for Magisk Manager and it choked? Alternatively, can someone recommend a procedure to help me prevent having to start all over again in the event that something goes sideways with the update? Sorry if this is extremely remedial, but I am still quite new to understanding all of this. I am honestly just afraid to try to run the update and risk bootlooping my device. Should I just install the update from TWRP?
[Magisk] phtablet:
nightmare

I also had a bootloop and could not start twrp. I saved the smartphone by flashing the boot origin with fastboot (after grilling my datas by activating fastboot oem unlock). then restored a backup of September.

This is the last time I do this ****ing innocent update via the app.
[Magisk] lordlord6:
How did you flash it? I have mi max 2, xiaomi.
[Magisk] CNZTampol:
Questiooooon !!!

"- must be running lates ftf nougat (E5823_32.3.A.2.33_R2R_AU) Recomended no metter if you are using model (E5803)"

i got E5803 Model , and i run latest nougat 32.4.A.1.54 / R1E (indonesia)

with my model which is E5803 and my TFT version,

will your custom ROM work ??

and if its fine with E5803 32.4.A.1.54 TFT Verison, does the installation instruction will be the same , or a bit different ?

many thanks ...
[Magisk] Tams2013:
stuck at boot animation after v19 magisk

i updated the magisk manager first through magisk update.. then it asked me to update to v19 .. i did it through app flashing.. it asked for reboot.. i did it.. and it stucked at bootanimation... i uninstalled magisk through magisk unisntaller zip.. still no solution.. tried to install v18.1 .. still stuck... what to do now>? device is Redmi note 4 MIDO . using aosp extended oreo latest build
[Magisk] jimmysviken:
my computer cant even feel the phone but i Volume Down and now its in black/recovery mode atleast... I have no idé what to do :(

I just flashed ROM with Emma - Worked. But wrong ROM tho so i need to fix my other ROM again >.<
[Magisk] gchamon:
I use a Zenfone ZE553KL and unadvertedly updated Magisk using the app and entered bootloop

When trying to uninstall, the uninstaller script kept failing, and reflashing Magisk didn't help, because even though the loop was gone, the phone wouldn't get past the Asus logo.

What I did was download the stock firmware from Asus site, unpack the boot.img from it and flash it using fastboot. The phone finally booted and I was able to reflash Magisk using TWRP, unbricking the phone.
[Magisk] alex00006:
Hi guys

I have problem in the root mi9 global rom with magisk 19.3 !

i have mi9 global stable rom V10.2.13.0

after install TWRP and reboot to recovery, next flash magisk 19.3 or 19.4beta but after reboot to system my phone automatic reboot to TWRP again and again !

actually after flash magisk may phone stay in TWRP and I forced reset factory data and wipe cache/wipe dalvik and reboot to system .....

now fixed boot loop !

Who can help me for root mi9 global rom ???

i try and test root with magisk manager and patched boot image but again boot loop and again cause ..
[Magisk] auzli:
Bootloop after Magisk Update

I updated Magisk of my Galaxy Note 5 to v20. But when the phone reboots, it's stuck on a bootloop and TWRP doesn't show up when i go to recovery mode. It just keeps on bootlooping. What should I do so that my phone will be functional again?
[Magisk] Allevart:
Note10+, after uptading magisks from 21.1 to 21.2 got a boot loop.

flashed boot.img of my custom rom via TWRP and is working as per normal now.

magisks stayed 21.1
[Magisk] mario0318:
Same behavior as well. Updated from 21.1 to .2 and the phone seems to get stuck on boot. I've noticed during boot, the subtle lag that often accompanies the animation appears to get into a particular pattern that repeats every 1 to 2 minutes, and the lag is extra noticeable over normal boot. So whatever is causing the loop seems to be constantly running a pretty heavy load task.

On a LG K20+ (2017) on LOS 15.1
[Magisk] Leroy_Sparks:
Me too. Can't get into TWRP to restore. Phone is basically bricked unless I find some way to reset/restore. 🤬

LG G5 H830, stock Oreo
[Magisk] mamama07:
Try boot your phone with recovery image (fastboot boot name_of_your_imgfile.img or similar command for LGs)
[Honor 8 Questions & Answers] Mumtaz77:
Hi.

First: Sorry My bad English. :)

So. The base is: FRD-L09C432 officially upgraded to Oreo. Data partition encrypted, bootloader and FRP unlocked status, TWRP installed and my phone rooted with Magisk. After some read in this and other forums I edited the phone fstab files, to delete data encryption. After edit this files I do a "Format Data" in TWRP. After that the FRP status changed from "Unlocked" to "Locked", and in Settings the "OEM Unlock" disabled and grayed. Bootloader status stay in unlocked. So this is the current state. The Recovery not changeable from TWRP to stock, because FRP-Lock status.

So, My questions is: How do I unlock FRP? If I rollback to Nougat, the FRP is unlock or not, or what? How do I rollback with TWRP? HurUpdater? What can I do, because if I rollback and FRP stay locked, I won't flash back the TWRP. And if this occur, I can't root my phone, and have other problems.

Ideas?
[Honor 8 Questions & Answers] cococchio:
Did you try to unlock bootloader via fastboot?
[Honor 8 Questions & Answers] Mumtaz77:
bootloader already unlocked. I won't try to relock, because 1 months ago I relocked, and my phone is bricked. Won't boot to system, and just DC-Unlocker helps to bring back my phone to life.
[Honor 8 Questions & Answers] cococchio:
Good to know. I am also bricked but I was able to unlock bootloader via fastboot. I only have access to error mode.
[Honor 8 Questions & Answers] nikolas60:
flash via download mode and wifi
[Samsung Galaxy Tab S4 Questions & Answers] Goldenrooster:
It seems that both Dolby Atmos and other sound effects on my brand new Galaxy Tab S4 are not working. Changing the settings does not make any noticeble difference. Are your sound settings functioning properly?
[Samsung Galaxy Tab S4 Questions & Answers] Reuben_skelz92:
Yeah mines working. Not a massive difference but noticeable
[Samsung Galaxy Tab S4 Questions & Answers] crxssi:
The Atmos setting seems to be quite impressive to me, especially when watching video that has Dolby AC3 encoding (5.1). I was actually shocked that sounds were coming from BEHIND me at times. I am not quite sure how they are doing that in a tablet with just 4 tiny speakers in front of me.
[Samsung Galaxy Tab S4 Questions & Answers] directx1971:
Looks like there is a bug in the dolby atmos implementation as it suddenly stops working and you get a normal flat sound , only a restart solves this problem for some reason and makes the atmos work again , some other times

Disabling then enabling the dolby atmos solves this problem , but this problem seems to exist from day 1 i bought this tablet and it still there in the current firmware (Security patch 1 july 2019)

When dolby atmos works you can't miss it as it is as crxssi described the sound is coming from all directions EVEN FROM BEHIND YOU and it is literlly the best 3d sound i heared from any device (In my opinion) ,

It is a real waste That this bug is killing that feature and it is still present until this day , some times i need 2 reboots before it works again but keep trying it will eventually work , i really hope that they sort out this bug soon.
[Samsung Galaxy Tab S4 Questions & Answers] ultramag69:
I think at this time developement for our obsolete (in Samsung's eyes) device has been ended... We might, if we're extremely lucky, get some updated features from the TabS6 if Samsung wants to throw the scraps our way but I wouldn't hold my breath. They can't even keep the security updates current which is against Googles own policies....

Security is a major feature in a business device and they are sadly lacking in that department, why would they rush to fix anything else when they can direct you to a shiny NEW tablet that is better in every way (but still probably has the same issue)...:rolleyes:
[Huawei P20 Pro Questions & Answers] kaleid1990:
I have a rather stupid question/curiosity:

I have P20 Pro and I have noticed that I don't have the automatic brightness checkbox next to the brightness slider in the notification panel, whereas some Mate phones that I saw until now have it - it is a general rule? I haven't got any other P model phones to compare with.

I know, silly ?
[Huawei P20 Pro Questions & Answers] allsts:
I had it on a Mate 10 Pro but it is gone on my P20 Pro (Emui and Android 8.1 156 c432 firmware right now).

If someone knows how to bring it back... thanks in advance.
[Huawei P20 Pro Questions & Answers] Babu mani:
Do u use any themes ?
[Huawei P20 Pro Questions & Answers] allsts:
nope
[Huawei P20 Pro Questions & Answers] kabirjedi:
not missing..Never existing... so ok missing but not bzg features...
[Huawei P20 Pro Questions & Answers] sniper20:
It's a built that way feature.its not missing.
[One (M9+) General] GeoffM:
I Purchased a New M9+ from Amazon Recently Listed as: HTC One M9 Plus 32GB 5.2-Inch Factory Unlocked Smartphone - International Version (Gunmetal Gray) to work on TM/MPCS

which it does very well, it received 2 OTA's to 6.0.1 from stock 5 But I am trying to get to 7.0

So far I've Tried;

RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 (TMob)

RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6 (Unlocked/Dev)

Each as given me a SIGNANURE (yes it's spelled that way) Error and directs me to find use the correct rom

Is there a way to tell exactly which ROM I need? or Force the DEV Rom to Install?

***BOOTLOADER***

***LOCKED***

htc_hiau_ml_tuhl PVT S-ON

LK-1.01.0000

RADIO-UNKNOWN

OpenDSP-UNKNOWN

OS-2.30.401.1

Oct 18 2016, 17:41:47(821792)