yashsingh1/xdaforums huggingface dataset:
[Magisk] TiZiO.Cover:
Hiding Magisk did it.

Thanks Mate!
[Magisk] Wesley_NL:
guys it dont install on sony xperia x perfoamce
[Magisk] paarnoutse:
Yeah, be careful. Imagine people believe that uploading pictures in XDA threads fails - next hoax is born... :)
[Magisk] kantjer:
Magisk is signed with a private key. TWRP signature verification only works with public test keys.
[Magisk] JollyDrifter:
So I live in Denmark and we use something called nemid. It is a authentication system with 2fa included . It has a companion app named nemid, and I cannot get it to work. Has anyone gotten it to work?

I pass safetynet. I have the app selected in magisk hide, and I have renamed the folder name of magisk manager. It didn't work. Then I tried Magiskhide profs Config module, and used improved hiding. It didn't work either. My phone is Xiaomi Redmi note 5 pro with lineageos 15.1. Thx in advance.
[Magisk] difr:
Is it possible to patch boot image with older version? via Magisk
[Magisk] osm0sis:
There's also a bug I'm tracking, starting in Magisk 1664, which results in a large script with redirects just silently failing. It worked in 1663 so hopefully a narrow set of changes to work out the regression.

I've reported it internally to [MENTION=4470081]topjohnwu[/MENTION] - no response yet - but I think he's on development vacation until his new laptop arrives.
[Magisk] martyfender:
He is back at development, as he just released a new commit.
[Magisk] TonikJDK:
Double check all you root apps and make sure they have root. I had a similar issue with an app that was trying to get root but it never popped the toast message. It burned my battery retrying and ran hot.
[Magisk] zelendel:
To be honest. This is something that will most likely not happen. There will always be people that add all apps. Hell I add them all myself. I dont want any app looking for root and more and more apps are starting to look for and block apps with root.
[Magisk] wes'side:
Adding all the apps is a cause of many of the issues allot users are having, that's why you read the info first, I was silly once to before commen sence came forth.

My issue on my nexus 6p is when I go Back to 16.0 /5.7.0 it has no root, no modules, no hide magisk. So it seems goinG back to the most stable version isn't possible unless you format your device, I know this because well, trial an error. An it seems silly that when all is fine, this awesome update which should be a beta, was released saying stable, it was stable until I went to the most date updates, with that in mind I can't even update or add certain modules, even when I had them before the update they were removed as if I never had them in my download section. Reliable update is needed.
[Magisk] greenys':
On clean Lineage OS 15.1 latest with stock kernel Magisk 17.1 stable causes the phone to freeze after 30 mins of usage and only hard reboot helps. Then does it again. Rolled back to Magisk 16.0 vcustom(modified version to support treble) the issue is gone. Ideas?
[Magisk] roseyhead:
What does freezing the game do? I've been doing the time trick just fine without that.
[Magisk] maybeme2:
You are correct. I had a stable system until I started hiding some apps. That caused system crashes and a boot loop.

So if we are limited in how many apps we can safely add to the hide list, which apps belong there?

Edit. And more importantly, which apps do not belong there?
[Magisk] fd.svensson:
5 posts up you can read ⬇️
[Magisk] whiteak:
I have 3 different devices all now on Magisk 17.1, I have no apps in the Hide List on any of the devices. 2 of these devices have no problem, no freezes, no reboots, nothing, everything is working fine. The last device has the exact same setup, no apps in the Hide List, no modules loaded at all, yet it has constant freezes and reboots on 17.1, but if I go back to 16.7 on this device, it runs perfect again. So while you might say it is people hiding apps that is causing bootloops etc, it is not the case for everyone, there is definitely some kind of problem with certain devices now running 17 or 17.1. Not a big issue for me, but the end user can't always get the blame when all they are trying to do in most cases is make the dev aware of issues they are seeing on their device.
[Magisk] xunholyx:
Add the apps that look for root, like bank payment apps and some games.

The apps that don't belong there are apps that won't look for root, obviously.

If you need to pass safetynet to use an app, that is the one you will want to add.

Easiest thing is to just use apps until they won't work because of root (you'll get a prompt telling you so) . Add them to hide, then go to settings > the app you are hiding > clear storage/data > reboot
[Magisk] master64nl:
Yeah, you are right :good: I had always 7 apps in the hide with no problem but after magsisk 17 and later 17.1 I was struggeling for 2 whole days to get everything right. Now I am on a custom rom and had to do a full wipe and loosses my oem tic.
[Magisk] Killua96:
Shoup help with the game constantly crashing
[Magisk] roseyhead:
Ah, so the game is crashing when it's in the background for people, as well as not starting up because of Magisk? I haven't had that problem thankfully.
[Magisk] Didgeridoohan:
Technically, there's no real limit to how many apps you can put on the Hide list. It's mainly about what apps you put there. System apps and services are generally a bad idea.

If you re-read my text, you'll see that I wrote that I suspect that

many

of the issues reported, not

all

, may be because of this. Of course there will be other issues... If a user doesn't have a single app on the Hide list and is still experiencing issues, the post wasn't aimed at them...

The big issue here is that practically no-one is providing anything useful about the issues they are seeing with their devices. It makes any real issues incredibly hard to fix, if you can't get the details about what is actually wrong.

I saw a lot of posts suggesting that having put the wrong app/process on the Hide list might be the culprit, hence I posted my little announcement.
[Magisk] martyfender:
I agree with you. Very little info has been posted to be able to help users with their issues.

A few days ago I had suggested that the OP be edited similar to the beta thread to add info for ssers to post to help us troubleshoot issues.

But that has not been done. I do not understand why. Many of these posts are totally useless for us who spend our valuable time trying to troubleshoot.

The OP should be edited with something similar to this from the closed, beta thread:

Plus device, Android version and if you have a stock or custom ROM.

I realize many are to lazy to search and are looking for a quick fix, but the number of these people that ignore xda rules and apparently skip even reading the Op are becoming outrageous.

It is almost like posters are doing Google searches and getting to the last post in the thread without even reading the OP or bothering to do even minimal searching.

Please, please, edit the OP, at least, so the few who are responsible will at least make minimal efforts to help.
[Magisk] thunderserpent:
I haven't had any luck opening YouTube, YouTube music or Google podcasts since updating to 16.06 and now 17.1. Has anyone else had this problem?

On OP5, August patch, android 8.1, magisk 17.1
[Magisk] greenys':
Well I don't understand anything from that but I presume the script causes this error. Either way I'm glad it was reported and thanks for the reply.
[Magisk] Strephon Alkhalikoi:
This is reality here on XDA today. Fixing the OP won't change the behavior.
[Magisk] mayur.3.92:
Magisk hide doesn't work for me, Airwatch detects I'm rooted:(
[Magisk] Aki_9982:
Yeah but mine is failing the safety net nd here is the log below
[Magisk] Artim_96:
Topjohnwu is already working on an update for detection circumvention. He just wanted to finish 17.0 first
[Magisk] mayur.3.92:
Thanks brother!
[Magisk] _Melkiy_:
Friends! Google Pixel, Majisk 17.1, Official LOS, Bootloader unlocked. Does not work GPay!!!

On other ROM everything works.
[Magisk] demonoidmaster:
Sounds like a rom problem and not a magisk problem, there's nothing to fix here, switch roms

---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------

he said it's a known problem that decryption could fail on OP3T devices, just because yours works doesn't mean everyone elses work too
[Magisk] yochananmarqos:
Try the Magisk Hide Props Config module.
[Magisk] jcmm11:
I just want to confirm:

The only difference between the 15 and 17 templates is the update-binary? Or did I miss something else?
[Magisk] :
No, he wasn't mentioning op3t, he was refereing to oneplus devices.

I never claimed something like that. "twrp-3.2.2-0 and 3.2.3-0 aren't able to decrypt data on oneplus devices" is just not true - exactly that was claimed. Please read my posting and the one I've responded to. I was never claiming it's working on each and every oneplus device, I have given one example of a working oneplus device. The generalisation you claim to be in my answer was in the posting I responded to.

Read before blaiming me for something I've never stated!
[Magisk] amit3880:
Hello guys [MENTION=5417899]DiamondJohn[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION]

Thought my post is missed in between .. So repeating..

Sorry for inconvenience...

Please suggest me on how to investigate further.

Thank you in advance.
[Magisk] yochananmarqos:
The module.prop also has one line changed:

minMagisk=17000
[Magisk] silver311:
Currently using the 17.1 version. However, it seems I cant open the Magisk Hide section at all. Whenever I try to open the Magis Hide, the app crahses. Anybody else having this issue?
[Magisk] jcmm11:
LOL I assumed that was a given. But thanks - I appreciate it.
[Magisk] martyfender:
The official nightly builds of Magisk are available.

[DEV] Magisk Canary Channel - Bleeding Edge Builds:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

Enter this link in Magisk Manager settings, custom update channel:

https://bit.ly/2MPKGY5
[Magisk] iamelton:
exactly.. i have a oneplus device on latest twrp v3.2.3, and see no problem in decrypting the data partition..

that generalisation on oneplus devices (by some clueless user) was plain wrong..

appreciate that you took the time to show counter proof.. :good:
[Magisk] DroidJP:
How do i get my version of twrp to mount encrypted data partition? In the logs it says crypto footer not found unable to mount data.

Twrp version 3.1

Thanks.
[Magisk] iamelton:
sorry i cannot help with this..

your issue is not related to this thread, and im no expert in dealing with the problem..
[Magisk] MrBrady:
How do I report a bug for topjohnwu about Magisk no longer working with Samsung Pay (specifically the Gear Plug-in App).
[Magisk] Terrigible:
Oh it's not a bug. It's designed by Samsung. If you root any Samsung device, you will trip KNOX and lose all functionality of Samsung Pay and never get it back.
[Magisk] MrBrady:
I'm not on a Samsung device. I'm on a Pixel 2 XL. Trying to get Samsung Pay (Gear Plugin) working. Old versions (1.5) work, but new versions detect Magisk. The issue is old versions are forcing updates to the new version.
[Magisk] Snowpuppy:
Verizon Pixel XL

I was getting the below issues on 16.7. Still getting the same thing on 17.1, both stable and beta.
[Magisk] mayur.3.92:
Will rolling back to previous version fix this? And if yes can you please share the version number
[Magisk] Terrigible:
Do you have Magisk Hide enabled for the Gear companion app? Have you repackaged Magisk Manager?
[Magisk] MrBrady:
I have hidden/repackaged Magisk Manager. I've also hidden all the Samsung/Gear related apps.

When I look at the Samsung Pay log on the root of my internal storage it says (among other things):

<Detection>

Date Time Source Policy Summary Current Warning Ver Name Description

2018-09-06 22:39:11 [6042] 52355100 00004000 00004000 00004000 4.4.4 (ROOTED ) MAGISK

2018-09-06 22:39:11 [6043] 52355100 00006000 00002000 4.4.4 (ROOTABLE ) MAGISK

2018-09-06 22:39:11 [6041] 52355100 02006000 02000000 02000000 4.4.4 (RSH ) MAGISK

</Detection>
[Magisk] lionelia:
Hi

I have found some problem with magisk 17.1

Device is Huawei mediapad T3 (KOB-L09) using F2FS filesystem.

When I install F2FS looback workaround module with TWRP and reboot the device, module is well installed.

Then if I want to install other module, every modules installed are lost after reboot even if no error was repported during installations.

I had to rollback to Magisk 16.0 to have it working.

On my Nexus 5X using F2FS as well, everithing is working fine with Magisk 17.1

Thank you.
[Magisk] DarkSide®:
Hello, i have some trouble with last magisk's build

I have xiaomi redmi note 4 with MIUI 9.6.2.0 and twrp 3.2

After reboot wifi don't work and some times sim card refuse to work

I have this issue only with latest build of magisk
[Magisk] Homeboy76:
There is no Magisk 17-1.zip BETA

Go here: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch

Do #7 use twrp-3.2.3-1 img/zip.
[Magisk] Artim_96:
No, only an update
[Magisk] Wolfcity:
Latest f2fs loopback bug module supports Magisk versions only up to 16.6. Check the thread, [MENTION=5228676]VR25[/MENTION] made a notice there.
[Magisk] Ecna:
The other day Magisk asked to update to 17.1. Cool, let's do it. The zip would download fine, but my only option was to patch the boot image. Later I noticed it said Magisk wasn't installed anymore. But I've been running Magisk for months! So I tried to patch the boot image and install via adb:

PS C:\Users\micro\Downloads\platform-tools_r28.0.1-windows\platform-tools> .\fastboot.exe flash boot .\patched_boot.img

Sending 'boot_a' (24664 KB) OKAY [ 0.581s]

Writing 'boot_a' OKAY [ 0.015s]

Finished. Total time: 0.608s

Should work! Except it still says Magisk isn't installed! What can I do to get Magisk back? I'm running the 8.1 stock image on a Pixel 2.
[Magisk] nagi_007pk:
Hey guys

I'm using a OnePlus3T with official firmware (5.0.5). Whenever I update Magisk to V17, it keeps on giving me the prompt initialising factory reset and phone reboots to recovery. I have tried the Magisk uninstaller a thousand times still whenever Magisk Manager is run the prompt appears and phone restarts. Anyone facing a similar issue? Magisk is working fine otherwise.
[Magisk] John360:
Bootloop on OnePlus3 with latest O.S.

I'm having issues with both 17.0 and 17.1 on Oneplus3 with the latest software update. Magisk still causing bootloops, I already tried to update from magisk manager (first time), patching the relative boot file and then via Twrp install.

I had to reinstall the system twice from recovery already.
[Magisk] Ecna:
Actually nevermind, I was flashing the wrong patched_boot.img. 17.1 is installed again. \0/
[Magisk] gewe:
I had the same problem on my Moto G5S Plus, running stock 7.1.1. Magisk Manager updated, said there was a new version of Magisk. After downloading the zip, the option to install let me select "an original image". I didn't know what that meant. The original boot image prior to installing Magisk? An original Magisk image?

So I went to TWRP recovery, flashed the Magisk uninstaller, and then installed Magisk from scratch. That worked.

Previous updates installed perfectly well from Magisk Manager, so I think there was something wrong with this one.
[Magisk] Soumy1234:
How do you mount magisk partition?
[Magisk] guest4711:
I use "Magisk Manager for Recovery Mode" to maintain the modules in TWRP.

If booted normally the image is mounted (as /sbin/.core/img).
[Magisk] Soumy1234:
Thank you!
[Magisk] Snowpuppy:
Updated my TWRP as recommended (from 3.2.3-0 to 3.2.3-1) and installed Magisk and yet the exact same thing is happening. Yes, I have a brain and followed the instructions exactly, and my log doesn't differ from before. Something is going on here, hopefully someone has a real idea and answer.
[Magisk] peterlee928:
1) assume you have an unlocked bootloader?

2) have you tried starting with a clean install of the latest factory image?

3) are you using the latest platform tools (september 2018 version)?

4) unless you need/want twrp installed on your phone, have you tried using twrp img file instead?
[Magisk] Snowpuppy:
1) Yeah, bootloader is unlocked (and hopefully once all is said and done that annoying warning on boot can be removed)

2) The factory image install was done on Aug 19th with the latest stock, TWRP and Magisk files available at that time. (Would enjoy not doing a factory reset again if possible).

3) I am not, was using the latest from the above date. They're updated now, I'll try again in a bit.

4) I don't know what you mean by this, do you mean trying to install Magisk using a fastboot of the img file instead of using one installed on the phone? If you think this would make a difference I can try.

I wish there were logs of what's causing the phone to forever load after Magisk install. If there were a way to generate or retrieve this info that would likely help.
[Magisk] AoEKiller:
Did you set a PIN code before flashing TWRP? also you don't need to un-root to keep A/B integrity, just check the option to keep both DRM-Verity and A/B and a PIN code is also needed because TWRP will delete partiton A, then reboot in TWRP, wipe only cache or reset to install new ROM in B, flash your ROM, install magisk ( don't bother with the first magisk in A partition ) then your kernel, always flash magisk before custom kernel even if that guy told you so because it will patch the boot.img from the custom kernel you will break dm-verity in that case use magisk-uninstaller and dirty flash OTA and restart.
[Magisk] Snowpuppy:
Yes, I did have a pin when I flashed the first and updated TWRP just an hour ago. Sorry, IDK what you mean by A/B integrity. I've seen it mentioned a few times but it's not in the guides for rooting (which is all I want to do. I'm not looking for roms or anything yet, just extra app functionality).

So, basically my steps were Flash TWRP 3.2.3-1, reboot into flashed recovery> Tap install and select "Magisk 17.1.zip"; install completes successfully > Reboot and meet infinite loading.

I would try re-flashing TWRP and seeing if any verity or slot options show themselves, but I'm already on the latest version so the option doesn't work simply from booting the twrp.img file. I'm sure there's a way to re-flash it if necessary, just gotta find the command.
[Magisk] Homeboy76:
Ok.

I know you are frustrated, relax we're trying to help you.

Keep your cool and your frustrations to yourself:

"Something is going on here, hopefully someone has a real idea and answer."

Try this flash the September's boot image to both slots

(You will not lose your data)

Look at #6 of the Guide for help flashing the boot image.

Boot twrp-3.2.3-1.img

flash twrp-3.2.3-1.zip (If you want to install twrp)

Add this: Flash Magisk uninstaller.zip

reboot recovery

flash Magisk 17.1.zip

reboot syatem
[Magisk] Snowpuppy:
Hmmm? I'm not at all frustrated. I'm sorry you took it that way but not everyone on the internet lacks manners or is inherently upset when something isn't working properly. What prompted you to say that all of a sudden, didja even read my last few posts? Thanks for the motivational handout though c:

I'll try these steps right now and post results after they're completed, likely in 15 minutes or so as baked goods are done in about 5.

Thank you!

Edit:

After following these steps exactly the same problem still occurs. To note, I've been flashing the uninstaller every time as it's the only way to get my phone to load again. The log shows Magisk only flashing to current boot slot (b) so maybe that's a hint towards something?

Anyways, I'm flashing the uninstaller (again) so I can boot my phone once more.

Also, a piece of information that may help... I'm currently on the August 5 security patch, Android 9 build PPR1.180610.009
[Magisk] xunholyx:
That TWRP log you posted earlier.......your current boot slot was set to B. And you said later that you didn't know about slots. You just need to change to slot A in TWRP I would guess. I think that's probably default.
[Magisk] Snowpuppy:
Yeah, even after all this reinstalling I notice slot b is still chosen. I'll figure out how to change this and repeat the process.

Edit:

I don't know if that would be it, pulled this from Reddit
[Magisk] heindrix:
Thanks man, you're the hero!
[Magisk] peterlee928:
https://www.didgeridoohan.com/magisk/MagiskHideHelp

this may help with pulling a log.

wrt factory reset, have you tried flashing the factory image without the "-w" in the flash-all.bat file? this will give you a clean start without wiping your data. of course, the obligatory disclaimer - make sure to back everything up before doing this.

perhaps that first, then flashing the magisk uninstaller, then flashing magisk 17.1 in twrp. sometimes a clean start is all that is necessary.
[Magisk] AoEKiller:
Security patch is only revelent if you downgrade firmware, your device can randomly press random key, pulldown top menu, reboot and battery drain only if you try to downgrade and keep verity. Security patch trig 3 flags K for Kernel, S for System and B for Bootloader I think. Updating bootloader and ROM reset flags to 0 for each of them.

Again this is not Magisk fault.

---------- Post added at 05:56 AM ---------- Previous post was at 05:53 AM ----------

Is your kernel install is based on Aroma?
[Magisk] Snowpuppy:
Opening my flash-all.bat file doesn't show a -w flag so I can only assume when I first did this I removed that, or it wasn't there to begin with. I'll try another factory reset though, I have time this weekend.
[Magisk] peterlee928:
unless u previously edited the file, it should absolutely be there. i presume u downloaded the full factory image from this site:

https://developers.google.com/android/images

if you are willing to do a factory reset, that works also. good luck :good:
[Magisk] Snowpuppy:
Yep, that's where I downloaded from. Something tells me a factory reset isn't going to fix this though. Something's preventing the Magisk boot file from loading. Re-flashing the stock bootfile fixes the issue.
[Magisk] Didgeridoohan:
Actually, you can, with a simple terminal command in TWRP:

https://www.didgeridoohan.com/magisk/Magisk#hn_Keeping_dm-verity_and_forced_encryption
[Magisk] TiZiO.Cover:
I can confirm that.

Version 5.18.10090 is the last one that passes, the latest 5.19.10130 is being detected.
[Magisk] mayur.3.92:
Can you tell why is this?
[Magisk] Aki_9982:
So i have an update on my problem to saftetynet on 17.1..

So when i installed magisk 17.1 i got a the saftetynet fail(cts-fail)

But when i installed the magisk 15.4 it passed though it did so i flashed the universal safteynet fix beta v5 through recovery and then it passed but in magisk manager it shows invalid so [MENTION=268073]top[/MENTION]jhonwu, so i request you to provide a patch for miui 10(official) devices.

If u want the magisk logs i can provide you later.
[Magisk] Artim_96:
Because they updated their app to detect Magisk so topjohnwu has to implement a new workaround, obviously. Magisk isn't magically learn on it's own how to do that
[Magisk] Homeboy76:
When, I wrote about you expressing your frustrations, I was reminiscing about my past frustrations the first time I tried to root my device. :eek:

After, reading your post 'again'. I noticed there are some Verizon Pixel XL owners that have unlocked their bootloader with this method:

[How-to] Unlock bootloader on Verizon Pixel/XL by burduli

That are unable to root their phone. It doesn't seem to matter which factory image their using, or if they did a factory reset. I am not technically proficient enough to figure out why. :(
[Magisk] 25Swagat:
Hey mate! Can you help me? What file does it mean by flashing patched ramdisk.img. Is it the stock ramdisk image that my phone software is in? I tried fastbooting patched ramdisk.img but magisk doesn't give me the option to continue. I can't even install magisk zip file. It just downloads but doesn't get installed.
[Magisk] byReqz:
Im on Magisk 17.1 and latest Magisk Manager and still my Safety Net answer is invalid