yashsingh1/xdaforums huggingface dataset:
[Magisk] elvinguitar:
I've tried the "Direct Install" method of updating to v18.0. However, Magisk crashed and the update won't proceed. I'm using Lenovo Tab 3 8 Plus (Lenovo P8).
[Magisk] nilg0lap:
Hi,

I'm new as a magisk user. Can anyone exlain me what is "preserve force encryption" and "preserve dm variety"?? Should i check these options??

Sorry for the noob question.

Thanks!
[Magisk] kiwigi:
[MENTION=8893719]spawnlives[/MENTION]

I'm back at my desk after a 10 day break away. Before I left I flashed Oreo Stock and installed the basic Apps. Can I verify a few bits before diving once more into Magisk root?

Looking at your instruction I could continue from where I am now with the existing and working OS? How do you backup Apps and Data without TWRP? SmartSwitch?

As Magisk V18 just has arrived I would rather go with 17.3? Any thoughts about that? Update to v18 could be done through the manager any time later.

Thanks in advance!
[Magisk] Nguyễn Thế Vinh:
Forgot to mention, I already tried that
[Magisk] bubuescu:
Nova

After update to 18.0 i cant grant superuser to nova launcher, it just freeze the phone when i select root for lock screen
[Magisk] Towmastersteve:
hello all google pixel 2 xl here did the December ota through sideload and then went and flashed magisk v18.0 via twrp and got bootlooped easy fix just reflashed December ota and fixed but same thing again after i tried rooting with magisk again so just flashed ota so was wondering if December ota broke magisk and we just need to wait on a fix or if its something else i remember reading about some folders that were being left behind in the early days of rooting the pixel 2 xl that after you updated you needed to delete before you could flash magisk again can't seem to find that thread now but I also thought they fixed that and I have done this with other ota updates since August when I first got the pixel and rooted it never had any trouble with sideloading the OTA's and then reflashing with magisk

thanks and please forgive me this is my first post never needed to ask before always was able to figure it out on my own but then again never had anything this new

pixel 2 xl unlocked with bootloader critical unlocked and December ota now
[Magisk] martyfender:
If you have TWRP, I've found flashing through it to be much, much, more reliable than the direct install method. On some devices it always works, on others it is hit or miss. Supposedly it was fixed some time back, but, at least for my devices, it was not. And back then I did provide logs and no one knew why it was happening.

I have not attempted it for some time as TWRP flash for me never fails. I do know others get errors when they try it in TWRP. This is, of course, based on pre 18 builds.
[Magisk] Didgeridoohan:
Some kind of PSA...

Having issues updating to Magisk v18.0?

Try doing a completely clean install of Magisk v18.0. First uninstall whatever version you have installed (directly from the Manager or use the uninstall zip in recovery) and

then

install v18.0, either through flashing the zip in recovery or patching a boot image through the Manager.

https://www.didgeridoohan.com/magisk/Magisk#hn_Updating

If you still can't get things working, very little can be done without any kind of logs:

https://www.didgeridoohan.com/magisk/MagiskHelp

No logs usually means no fix...

Did MagiskHide stop working?

Have you tried turning it off and on again?

https://www.didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_Issues

If you still can't get things working, very little can be done without any kind of logs:

https://www.didgeridoohan.com/magisk/MagiskHelp

No logs usually means no fix...
[Magisk] jenslody:
Did you clear the data/cache of the app and force close it?
[Magisk] chooks06:
I've experienced the hits and misses and after a miss, I would totally uninstall previous version then install new version.

I have never tried flashing the new version via TWRP over the existing version.

Just want to ask if you're usually flashing the new over old directly and getting consistent results?

Going to try anyway but just wanted some "good to have" info for reference.

Thanks!
[Magisk] saspo59:
Hi all

Need a download link for very. 18
[Magisk] chooks06:
You mean Magisk v18.0?

The link to the correct thread is in OP..

Edited.. For your convenience.. Hit the link and go to the first post for the download link..

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
[Magisk] guest4711:
So install "MagiskHide Props Config" module, clear data and cache of your banking app, delete all old magisk directories (e.g.

/sdcard/magisk), reboot and try again.
[Magisk] spawnlives:
I don't really have any preferences to general backup apps/data programs as I don't use them. I mainly use twrp to backup before doing major imstalls/mods or updates (like magisk or exposed modules ).

You can use Smart switch to backup your apps/data and has other features as well . It will also imstall your Samsung drivers for your PC. So it can be handy to have.

Note: Do not to run smart switch and Odin at the same time as they don't play nice with each other.

As for magisk on my S8 I have updated from 17.3 to 18.0 through the manager and am having no issues with the new version so you could try that first.

As mentioned before I would do a complete backup in TWRP before flashing magisk in case something does go wrong.
[Magisk] bohemist:
You can find the download links in the Announcement Thread https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] strike76:
Updated to version 18 via Maanger, Xiaomi mi Max: Bootloop

EDIT :

I flashed the ROM again and put the 17 version of Magisk to avoid problems
[Magisk] klausxda:
Similar on my side. I have a Xiaomi Redmi Note4. Update to version 18 via Manager ==> Phone does not boot, message "The system has been destroyed" appears.
[Magisk] elvinguitar:
The installation of Magisk v18.0 is kinda weird. I've uninstalled the previous version of my Magisk (v17.1) via both the Magisk Manager and flashing the uninstaller.zip file. However, when I installed Magisk v18.0 via TWRP, the installed version is v17.1 instead of v18.0.
[Magisk] Nguyễn Thế Vinh:
I fully wipe my phone, reinstall the rom, setup MagiskHide, MagiskHide Props Config (include improved root hiding) and it still doesn't work
[Magisk] guest4711:
So there are three choices: Either don't use this app or don't root your phone... Or have a look into [MENTION=4667597]Didgeridoohan[/MENTION]s's fine manual at https://www.didgeridoohan.com/magisk/MagiskHide where you'll find other tricks like disabling adb mode, disabling developers options etc. pp.
[Magisk] Didgeridoohan:
Then you must have flashed the wrong zip in TWRP...
[Magisk] Trisks:
Magisk v18 kinda breaks my phone

Xiaomi Redmi Note 4x (Snapdragon)

So, I updated Magisk from v17.3 to v18 through the app using Direct Installation. Rebooted, and it said system broken. So i used the backup I had made 3 days ago and restored it using TWRP. Booted again, but I don't have WLAN and Cellular Network, completely. It doesnt read my Sim card.

Tried using v17.3 and v18 uninstaller, but it wont enter bootanimation and will stay there forever. Only boots again after I restored with the backup, this is kinda frustrating.
[Magisk] elvinguitar:
I'm pretty sure it's the v18.0 zip.
[Magisk] Didgeridoohan:
In either case, without that log I wrote about (in the last post you quoted), there will be no answers...
[Magisk] martyfender:
Have you tried reflashing your stock boot.img then flashing Magisk in TWRP?
[Magisk] the Doctor:
MODERATOR NOTICE: THREAD CLEANED

Discussing Lucky Patcher or any other type of warez is not permitted on XDA.

Sent from a government terminal using my sonic screwdriver
[Magisk] Trisks:
Reflashed MIUI Rom, Booted to system but lost all my apps.

I Guess I'll be careful using Magisk next time.

Also this was v18 Fault, it was running stable last time.
[Magisk] kosmasgr:
Build 18.0 breaks "double tap to wake device" , on my whyred , running Pie. Back to 17.3 and it's ok now
[Magisk] klausxda:
Magisk v18.0 on Xiaomi Redmi Note 4, now working

On my Xiaomi Redmi Note 4 with MIUI 10.1.1.0, I saw a message "The system has been destroyed Press power button to shutdown" after

upgrading to Magisk 18.0 via Magisk Manager.

However, I could still boot into recovery (TWRP) and into bootloader (fastboot).

For me, the following solution worked:

Preconditions: adb is installed on desktop PC, latest TWRP image and Magisk 18.0 are downloaded

(1) Boot into TWRP and create a full Nandroid backup - just for security reasons. Connect phone to desktop PC and copy Nandroid backup to a safe place.

(2) Follow the instructions for "Fastboot Update" on http://en.miui.com/a-234.html. In my case, I needed the MIUI ROM for "Redmi Note 4X Latest Global Stable Version ..." (file name starts with mido_...). In the end, my phone started successfully into the normal system, but

wasn't rooted anymore, and TWRP was no longer present.

(3) Open DOS shell on PC, type "adb reboot bootloader". Phone now boots into fastboot.

(4) Type fastboot boot <latest TWRP image>. Phone boots again and starts TWRP.

(5) Copy Magisk 18.0.zip onto Internal storage and flash it via TWRP. Reboot the phone. Now, it starts normally and is rooted again.
[Magisk] Jaheen:
Magisk 18.0 failed to root the device.

Updating from previous build works.
[Magisk] jcmm11:
So you're saying if you weren't rooted you couldn't install v18, but if you had 17.x (or earlier?) installed then you could upgrade to v18 successfully. Is that right?

If so: how did you try to install v18? (Patch boot image, TWRP, or what)

Where's the install log?

What phone and Rom/Android version?
[Magisk] Rjaa:
Running the latest xiaomi.eu weekly on a redmi 4a.

I updated magisk from 17.3 to 18. Update ok, it tells me to flash the zip. I flashed the zip, no problems. Reboot, open the app: magisk is not installed. I tried again, no errors, no problems: magisk is not installed.

What now? Downgrade to 17.3? How?
[Magisk] @srmahunt:
Hey guys, i am having issue enabling fingerprint authentication in magisk manager, any help??
[Magisk] Jaheen:
Yes, i meant the same.

I flashed v18.0 in twrp aftr flashing Havoc rom - Asus XOOTD device.

I don't know how to pull install log. Will it be in my device now (not wiped anything)? Can you tell me how can i pull it.

Now using v17.3, just flashed it on top on v18.0 as it did not root successfully. Manager pops up for latest version and flashing it via magisk works & the status shows v18.0 installed.

I found the log but it has no v18 records.
[Magisk] Noor9933:
Is there any possible solution for ctsProfile.

I am getting false always on miui beta (pie) on my poco f1

Tried V17.1, 17.3,18.0 and even 18.1 custom

Please help i have to do always clear data to get Google playstore certified thrice in a day.

Thank you.
[Magisk] xunholyx:
Use the Magisk uninstall.zip, then reinstall v18
[Magisk] Jaheen:
Try the universal magiskhide fix
[Magisk] Noor9933:
Flash the zip again from magisk repo save the log after flashed successfully.
[Magisk] Didgeridoohan:
That's not from a modified /system. The OTA would still appear, you just wouldn't be able to get past the integrity verification that the installer performs. So, you've got something else going on...

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] Jaheen:
Attached the log, but the problem arises only when initially flashing v18.0.

Updating from previous build, works fine.
[Magisk] IODroids:
Uninstall old magisk via Uninstaller.

Reinstall latest
[Magisk] Didgeridoohan:
The log that would be interesting is the recovery log from flashing v18.0 clean in TWRP. Info here:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Jaheen:
The twist is I dont get any error from twrp. It went as it was coded & gives success but upon boot, manager says not rooted.

I'll try to get that log when i switch/update rom.

Im tried of flashing roms 3 times today.
[Magisk] Hopie:
After update to v18 on HTC 10 Viper 5.11.0 (Nougat) , fc htc sense and many other system apps, random reboots, some settings reset to factory... restore backup and stay at 17.1
[Magisk] vMAC:
How can I determine what is causing this? Happening on my Pixel 3XL and my Pixel 2XL. My Pixel 2XL only has system less module installed no others,so I'm at a loss of what is happening.
[Magisk] Towmastersteve:
Thanks I used the uninstaller and did another side load of the ota then flashed magisk v18 and it worked I will do this from now on for all my ota just never had to do it before but will be doing it from now on
[Magisk] aputtapa000:
Ok, I'm sorry I don't have a lot of patience to read through the whole past pages of this thread to see if someone has my same problem, and I apologize for that but let me just describe what happened with me.

Yesterday morning I received a notification inside Magisk that the new 18.0.0 update is out and I'm like sure why not, so I got it(along with Manager app update). After rebooting things started to go wrong. First of all, I noticed an immense battery drain. Secondly(since I use GNow Launcher), I wasn't able to slide to the right to get to my feed. A lot of Google Apps stopped working(Google, Play Store, Drive, Hangouts, etc.[exceptions are GMail and Translate), a lot of my other apps(e.g. AccuWeather) would not open or give a blank screen. I also noticed a lot of my on-screen/ongoing notifications are not working. Started to assume something was messed up with GPlay Services so after a failed attempt to regain working conditions when I cleared data for Google Play Store and Cache for Services(since it gave me a blank screen when I clicked manage space), I made the decision to get rid of Magisk and get back su(for LOS). After doing so, I still have these issues and am lost on what to do and unfortunately very short on time for solving this issue. Any solutions or recommendations are greatly appreciated.

Device Specs: HTC One M8(Verizon Variant) w/ Unlocked Bootloader running latest Lineage OS
[Magisk] n.p.:
Having problems with the 6.1.0/18.0 update.

First device: Samsung Galaxy Tab2.

After update, all I see when starting Magisk is "Installed Version v18.0" and "Uninstall." There is no "Latest Version," no "Tap to start SafetyNet check," no "Advanced Settings" ("Preserve force encryption" and "Preserve AVB 2.0/dm-verity"), and no "Install" (with the Magisk icon).

The menu is normal, EXCEPT there is no "Downloads" entry. Root works. I have tried uninstalling and reinstalling several times.

Second device: Bluboo Maya Max.

When I press "Tap to start SafetyNet check, I get the "Download Proprietary Code" popup asking for permission to extension for SafetyNet checks. After I select Yes, nothing happens, until I get "SafetyNet API Error." I have searched for this, and have tried (several times) going into Settings / Apps / Magisk Manager, and clearing data (which doesn't work).

Any ideas how to correct either (or both) of these?
[Magisk] mbze430:
Been having issue with Magisk v18.0 with ROG Phone. After 30mins or so my Cellular Data completely stop working (WiFi works just fine). Flashing back to the v17.x works just as before without any issues.
[Magisk] xunholyx:
Flash the latest uninstall.zip with TWRP, then flash Magisk v18 with TWRP. You can find downloads for both in the OP of this thread
[Magisk] martyfender:
They should not touch the system because Magisk is systemless.

---------- Post added at 04:00 PM ---------- Previous post was at 03:44 PM ----------

For the Samsung device, I get that if my device is not connected to the internet.

For the second device, after clearing data, did you re-enable storage permissions for the app?
[Magisk] Didgeridoohan:
At least for the first case it sounds like you don't have internet access for the Manager.
[Magisk] partridge79:
Longwinded rant deleted

Edit ALL MY OWN FAULT IN USERSPACE BAD TIMING IT WAS SUBSTRATUM THAT UPDATED {IM IN BETA} NOT MAGISK AT ALL :crying: :silly:
[Magisk] realista87:
where can i download 17.3 ? i can't find a repo with all versions to download
[Magisk] martyfender:
https://github.com/topjohnwu/Magisk/releases
[Magisk] aputtapa000:
Thanks for the reply. Unfortunately, it only helped minimally to do this. Some apps now open that did not before but in overall I am still seeing the issue with most apps and notifications are still not working. I tried to do a safetynet test via magisk manager but ended up with just a spinning icon and no result or progress. Hopes someone else can help solve my issue.

--Edit: Does anybody think that switching back to old Magisk version will fix my problem because I will surely do that just want to know if I should invest my time on that or not?
[Magisk] martyfender:
I had something similar happen in the past on one of my devices and restoring the factory rom, resetting up Android and reflashing Magisk solved for me. Later, on a device of the same type, I found that a factory reset then flashing Magisk was sufficient. I probably reflashed my stock boot.img, before flashing Magisk, also.

In my case, I didn't have too many problems with apps, but my notifications were not showing and I could not open recents from the task bar to kill apps, etc.
[Magisk] aputtapa000:
Thanks for replying. Ya looks like restoring an older backup is the only way to go at this point. Unfortunately., my backup is around a month old and just 5 months after i flashed LOS so I'm going to have fun with getting around all that again :p:p but atleast I'm not in this situation. Feel kind of dumb to only get Magisk just so I can use GPay which I actually never use so might just stick with standard SU or find another workaround thats not as detrimental to my system but truly only if I actually need it. Anyway, thx again.
[Magisk] Scyhammr:
Maybe somebody can help me. Recently I tried applying an OTA update for my Pixel 2 XL and updating Magisk to v18 via TWRP. Now I have the issue where each time I try to apply the Magisk zip my phone reboots into a weird Recovery menu where I can only restart or factory reset. The only way I've managed to get out of that loop is booting into the bootloader and reapplying the OTA update. So, I'm currently unrooted with no way to reinstall Magisk as not even the older v17.1 works. Many thanks for any advice!
[Magisk] xunholyx:
I had the same problem with my P2XL after updating via factory image

Follow the advice I gave in this post
[Magisk] guest4711:
This behavior is normal if MagiskManager can not reach the internet. Mostly it is caused by firewall (e.g. AfWall+). After updating and hiding MagiskManager it is not recognized by the firewall so you have to allow internet access for MM again.
[Magisk] Scyhammr:
Thanks a lot! That worked but now I have the problem that Magisk request additional setup. If I try to allow it to download the Magisk setup zip then it says "setup failed". Any tips for such a problem?
[Magisk] xunholyx:
Magisk setup zip? I don't remember having to use that, but I was having beers and smoking when I did it, so maybe I forgot about it?

You used the downloads from the thread linked in my other post for the newest uninstaller and Magisk v18? I used the latest uninstall.zip and the beta v18 (although the stable one should be the same).

It also might have to do with me using the factory image instead of the OTA.
[Magisk] Scyhammr:
Yes, it request specifically for this setup zip but fails to download it everytime. I tried it again this time using the v18 from the beta channel but same thing. I normally wouldn't care so much but I can't access Magisk Hide or the SuperSU section of the Magisk app.
[Magisk] guest4711:
Perhaps you have an old MagiskManager installed which uses another key for signing. Try to uninstall it before you install the new apk. If your ROM includes it already you can find and remove it using TWRPs file manager.

You could also try flashing the uninstaller zip and reinstalling Magisk afterwards.
[Magisk] Mycroft2046:
Is there any dedicated feature request thread, or is this sort of all in one thread?
[Magisk] udinkaget:
can you tell me where i can found the newest gojek mod which have anti perform ???
[Magisk] tezukaryoma:
On v18, it break the function of magisk hide of dual app, either one of the dual app will lost the function of hide. Once i revert back to 17.3, both same apps of dual apps will function like usual. I m on miui pie rom. Tq
[Magisk] Soumy1234:
Samsung Galaxy Grand Prime (SM-G530W)

AEX 5.6 Oreo ROM

No special kernel other than the one that came with the ROM

Other Mods:

Ainur Sauron

Acp

Aml

Dolby axon Oreo 10.23.18

Viper4android 2.6.0.5

Notification helper remover

Terminal systemizer and debloater

BusyBox

Energized

GBOARD themes

Google lens enabler

Gpu turbo boost

Greenify4magisk

Init.d

iOS 12.1 emojis

Liboemcrypto disabler

Los recoder

Magisk Google dns

Mm for recovery

Props config

Midnight

Single user mod

Gms doze

Mi a2 camera

Xml pack

Vanced black
[Magisk] titiz33:
Hello,

I tried to upgrade Magisk from v17.2 to v18.0 directly via the Magisk Manager but my phone is now in a bootloop. I tried to uninstall Magisk via TWRP with the latest uninstaller but I get an error (Updater process ended with ERROR: 1) before the uninstallation is complete. It looks like the error comes from "No boot image magic found! ! Unable to unpack boot image".

Therefore I'm stuck with the recovery for now. I also tried uninstalling with previous uninstallers but I get the same error. Same again when I try to flash Magisk via TWRP.

As mentioned on the wiki, I'm considering deleting the Magisk image (/data/adb/magisk.img), but I don't know if that would be effective or if that would do more harm.

Or maybe I should just flash an unmodified copy of the boot image.

My phone is a Mi 5s on Android 7.0 running Xiaomi.eu stable ROM v9.5.2.0.NAGCNFA.

Thanks in advance for your help. :good:
[Magisk] ktmom:
The safest solution is always to flash a unmodified boot.img.

A general side note: I'm wondering if people who are having trouble with updating through the manager have used some version of a pre-patched image and as a result, there is no backup of the stock image on the device - one made by Magisk when flashed through recovery.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] iamcurseal:
I'm using Xiaomi Redmi Note 4x, after I update the magisk from v17.3 to v18 direcly, I got a message "system error" and It bootlooped, so I tried to Dirty flash the stock boot.img via TWRP, and flashed the Magisk v18.zip. It worked somehow, It just auto close the Manager whenever I connect to the Internet, so I launch first the manager and connect to the wifi.

[IMG="Redmi Note 4x"]https://i.ibb.co/kS6jGfz/Screenshot-2018-12-09-23-31-32-898-com-K-P4-WM200y-F8-NXi.png[/IMG]

Thanks for the Update [MENTION=4470081]topjohnwu[/MENTION]

More power and Godbless!
[Magisk] titiz33:
Thanks for your answer, problem solved.

So here is what I've just done: I simply booted into recovery, flashed an unmodified boot.img and I successfully booted into system (it took a while though), with Magisk Manager telling me "Magisk is not installed". I rebooted into recovery and flashed Magisk-v18.0.zip with success this time. Everything works like a charm now.

FYI, regarding your side note, before I flashed Magisk 18.0, I looked in /data and there was a backup of my boot image which I guess was the one made by Magisk when I flashed the previous version I was using until then. I'd be also curious to know why people are having trouble.
[Magisk] xunholyx:
Not for me. I had issues with a magisk patched boot.img that I got from the factory image. That's what I do every time
[Magisk] ktmom:
You patch the boot.img in Magisk manager then flash the patched image? Or flash the Magisk zip in recovery?

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] xunholyx:
Patch it and flash it. The last time I needed to use the uninstall.zip and TWRP flash