yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
How did you attempt to reinstall it? Do you have TWRP installed and you tried to flash it? Or what?

If TWRP attach a copy of the install log (after attempting install go to Advanced, Copy Log. Log will be closed to /sdcard/)
[Magisk] ClothedKing:
I attempted to reinstall it through the app, that's all. And I cannot attach links until I hit 10 posts, I will try to post it here: //imgur c

o

m/gallery/XllTrBB

This is the link to the error code sorry for the hassle and thanks for the help
[Magisk] martyfender:
Thanks for the clarification. I had never looked at my magisk.log before I installed modules.

Also, on the Adaway thread, I just saw another user reporting that TiB and Adaway are not giving a root prompt for him on v18.
[Magisk] jcrompton:
Yes ,,, yesterday I suddenly had the same experience.

Not sure what triggered because I've been using the same device for months with no other changes.

Had anybody else suddenly experienced Snapchat login issues?
[Magisk] RebelLion_:
Is xposed installed? That's usually the culprit.
[Magisk] Airtioteclint:
LG gpad x 8.0 running nougat 7.0 here. Never had a problem up to magisk 17.1. Anything above that causes bootloops. I've tried uninstalling and reinstalling in twrp and checking dm verity and forcing encryption in magisk manager before updating with no results. Going back to magisk 17.1 is the only solution for now.

Any ideas? Could 17.2 and up be incompatible with nougat 7.0? I have no problems with magisk 18.0 on my oreo and pie devices.
[Magisk] B__B:
Is this the tmobile version if it is you need download original boot. Img patch it and flash it with fastboot that what i had to do
[Magisk] ClothedKing:
Help please
[Magisk] jcrompton:
Nope
[Magisk] davcbr:
Probably you're very right but as i try to do so Magisk crash without any log file. No matter how many time i try again.
[Magisk] chooks06:
There are some posts regarding the issue in this thread.

Toggling the hide option may have worked for some users, as suggested by other members here.

You may want to use the forum's search feature to locate the relevant post.

Cheers!
[Magisk] davcbr:
I've tried to get Magisk via its manager because i've no root or custom recovery i selected img.tar patch file export then click install and point to last boot image right downloaded from sammobile of my S8+.

No fun,i get the app crashing,then i tried pointing directly the AP file after unzipping the image but same result. Where do i mistake?
[Magisk] jcmm11:
Start by reading here, then if you have specific questions ask. https://www.didgeridoohan.com/magisk/HomePage

Yes, you will need a PC. At a minimum you'll probably need adb and fastboot, along with drivers for your phone (assuming Windows, Linux usually has drivers built-in. Not sure about Mac). This requirement may be different depending on your hardware.

Also, your device specific forums probably have posts on how to root your device.
[Magisk] ipdev:
You are still not quite at the correct file. ;) You need boot.img

The unzipped download should give you a few .tar.md5 files.

You want the one named AP_NameOfRomFile.tar.md5

Uncompress it and you should get a few more files one will be boot.img.lz4

Uncompress it and you will get the proper boot.img

Note:

These are tar and lz4 compressed files.

You will need either tar and lz4 or an app/program that can handle tar and lz4 compression.
[Magisk] davcbr:
Et Voilà it's done thank you so much for explaination! A question more: now i've the patched boot.img file do i need to repack everything in the AP format file to flash with Odin or it's sufficientnto flash just the boot.img.tar file using the Odin's AP box?
[Magisk] jenslody:
MagiskManager has an option in settings to create an odin flashable tar-file.

Other tar formats night not work, depending on their settings. Odin is a little bit nitpicking about that.

Edit:

The accent grave in voila broke my answer with the forum app twice (the second time I copied my answer to clipboard before saving), vwdore I noticed thw cause:

it was cut after it, so I removed it inside the quote tags.
[Magisk] davcbr:
Ok got it. I'll flash directly the magisk output tar file.

Is the AP Odin's box the correct one to pick?
[Magisk] Mahendar01:
Problem with Magisk 17 / 18

I'm using Le 1s with Android 7 custom rom

With Magisk 17/18 I'm unable to using titanium backup feature like enable, disable, backup & restore. I tried with other Root Apps

With Magisk <=16 Works fine
[Magisk] 气人小萌新:
Okay thank you
[Magisk] 314mp:
I'll third this, pixel 3 magisk 18, I can check magisk manager and im good on safetynet, try to login to snapchat i get an error and can't login, check magisk manager it shows safetynet failed and I have to reboot my phone and it works fine until I try to login to snapchat.

I think snapchat must have updated their app and that is why its suddenly breaking.
[Magisk] jcrompton:
I had to delete all snap data on the phone. Uninstall the app, then unroot by reinstalling without Magisk, install Snap

Login

Viola

Then reinstall Magisk
[Magisk] 314mp:
Not sure if you mean just unroot, I figured of I unroot I could login but I want root and Snapchat, I was able to unroot login and reroot, but after about a week they reevaluate the login and it failed and temp banned me on snap.
[Magisk] BHUSHAN7988:
Device oneplus 6t

ROM stock OOS 9.0.11

Magisk 18

Lost twrp after doing a system update using magisk guide fine with this

But now I lost safety net sometimes and sometimes the magisk is shown as uninstalled but a reboot fixes it somehow.

Will post a log if it happens once again
[Magisk] 314mp:
This is the same issue I'm talking about above you, my safety net fails after after I try to login to Snapchat
[Magisk] wych42:
no prompt for nokia x5 with stock rom PDA-102A-0-00CN-B07

Device: Nokia X5

OS/Magisk Version: Android 8.1.0/ Magisk Manager 6.1.0(163), Magisk v18.0

Unlock & Root Process:

I followed those two posts to unlock bootloader and install Rom PDA-102A-0-00CN-B07(china version stock rom(with help from hikaricalyx) and root with magisk.

Basically: I flash Rom PDA-102A-0-00CN-B07 to my phone, extract boot.img, patch with magsik, flash patched_boot.img to boot_a(which is active). Then reboot, clean userdata& grant storage permission again, put app in settings/battery/background activity manager to allow auto active and work in background.

Problem: no request for root Prompt popup when I ran `su` via adb shell or using an app(icebox) request root permission.

The superuser section has no app listed.

Tried Methods: 1. uninstall completely and start over again, still not working. 2. Search this thread with keyword "no prompt", found some posts, like "disable battery optimization", but none of them work.

Logs: the only log I saw was `W/Magisk (24135): su: request rejected (2000->0)`, log file attached.

Didn't find how to post attachment, I post logs to gist

Any help would be great, thanks.
[Magisk] jazef1:
Hi guys,

I have a Telecast T20 tablet Helio X27 android 7.1, rooted running magisk 17. I've tried updating via magisk manager several times and although the process completes successfully, it does not actually update. I reboot the tablet after flashing is completed and when it reboots, magisk remains on 17 and again I am prompted to update to 18. I do not have a custom recovery as of yet so I can't flash the zip myself. I've considered just flashing either the zip or patching the boot IMG again via adb, but I thought I'd check in and see if this is an issue that has been raised b4 or if I'm forgetting something. Any thoughts would be greatly appreciated.
[Magisk] dan60:
Hello everyone!

Magisk manager has been freezing in All versions. It happens handomly (sometimes it works, sometimes it's frozen) and I can state I didn't have such problem with Super Su when I used together with my Motorola Razr HD. With Motorola Moto Z Play only magisk will work, but as I've told, partially.

I wonder what in Super Su granted it a 100% of effectiveness and what might be happening with magisk.

Best regards!
[Magisk] nguhanhson:
Hi!

My device: Samsung Galaxy A7 (2016) (SM-A710FD), custom ROM Android 7.0, Magisk 18.

Some apps still detect that my device is rooted, such as Samsung Pay, Vietcombank (com.VCB), VCBPAY (com.vcb.vcbpay), even though Magisk Manager package is renamed.

Please help me to solve this trouble.

Thanks and regards,

Son Nguyen.
[Magisk] zfk110:
Hi, failing CTS profile on this ROM

https://xdaforums.com/galaxy-tab-a/development/rom-crdroid-5-0-64bit-20181227-t3883791

I tired to use HideConfig module, but this tablet isn't listed there and also there is no finger print scanner on this tablet SM-T580

edit

also flashing Magisk-v18.0.zip on twrp wont bring Magisk app, I had to install Magisk manager apk after Magisk-v18.0.zip install

attaching logs
[Magisk] zfk110:
Samsung Pay and Google pay wont work, you can go to Magisk manager then Magisk Hide and try to hide those apps then restart to see if its working for you or not
[Magisk] Didgeridoohan:
Make sure that the Magisk Manager isn't installed to external or adoptable storage. That's been known to cause issues like that.

The installs log might be the only way to know for sure, but I'd just go with the patched boot image...

Grabbing a logcat when it freezes might be the only way to know for sure what's going on.

I tested both the Vietcombank apps and on my device they don't detect root with the app on the Hide list and the Manager repackaged. Can't test Samsung Pay, but I'd say your out of luck there with your Knox likely being triggered. Maybe the other two apps check that as well...

It's got nothing to do with a fingerprint scanner. It's the device fingerprint, the ro.build.fingerprint prop.

And you can generally use whatever fingerprint provided with the module, as long as it's certified. Or, if you really want one that matches your device you can check here how to go about that: https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] Machine318:
Has anyone discovered a better solution to loosing SafetyNet after boot then running the script "/sbin/magiskhide --disable ; sleep 2 && /sbin/magiskhide --enable" I dislike having to use band-aids like this..

OnePlus 5T, OOS 9.0.2, Maisk v18

---------- Post added at 02:39 PM ---------- Previous post was at 02:39 PM ----------

Has anyone discovered a better solution to loosing SafetyNet after boot then running the script "/sbin/magiskhide --disable ; sleep 2 && /sbin/magiskhide --enable" I dislike having to use band-aids like this..

OnePlus 5T, OOS 9.0.2, Maisk v18
[Magisk] DDR2424:
I have a problem. I updated magisk modules (i accidently hit install on two on once). Phone freezes.

NOW it every Time tries to configure device for a first Time. Also twrp says it is ecrypted (it never was).

What happend? My girlfriend set password and fingerprint only (did not reboot since then). Is it possible to encrypt without knowing about it?

I dont want to format all data to disable encryption.

Problem is on device: Vince with Arrow OS 9 (android 9.0)
[Magisk] wych42:
No,it's not. There's only one internal storage with my phone, no sdcard added.
[Magisk] dizM0nkey:
[MENTION=7187684]ianmacd[/MENTION] the last several updates I've done through your release of Magisk and Magisk Manager have booted me directly to TWRP vs. rebooting the phone. I'm currently on v18.1-2019010201 but any subsequent updates take me to TWRP after installing directly via Magisk Manager.

I'm on OnePlus 6 9.0.3

I've tried uninstalling using the uninstaller in TWRP and starting fresh with more recent versions to v18.1-2019010201 but I get the same result. Just reporting here.
[Magisk] jcmm11:
This probably belongs in https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[Magisk] castlekeep:
is it possible to use magisk on the galaxy s7 oreo that is currently rooted?
[Magisk] martyfender:
You say currently rooted. Rooted with what? If it is SuperSu, you need to flash [MENTION=4544860]osm0sis[/MENTION] UnSu.zip and possibly reflash a stock boot.img in TWRP followed by flashing Magisk, all before rebooting. UnSu.zip can also remove some other root solutions, as well, I, however don't recall which ones.
[Magisk] AttoR:
Hello everyone...

Every time I install a module on magisk 18 it is always bind_mount in the log...

because I can't delete files in the system :(

is there a way to overcome this...?
[Magisk] Didgeridoohan:
Well, yes, that's what Magisk does... It mounts the module files over your regular /system partition.

If you really need to delete system files you can find the stock /system partition under /sbin/.magisk/mirror/system.
[Magisk] AttoR:
Is there no other way than in the folder, because I need several modules such as viper :laugh::victory:
[Magisk] Didgeridoohan:
What do you mean? If you need to delete system files you're going to have to navigate to their location anyway. Now they just happen to be somewhere else...

I have a feeling you have an issue that you've not quite managed to communicate. Could you be a little more detailed about what it is you're actually trying to accomplish and what it is that doesn't work.
[Magisk] AttoR:
Sorry if the sentence is difficult to understand...

I mean, is there a way to overcome bind_mount after installing the module in Magisk... that's all.
[Magisk] Didgeridoohan:
No. That's part of the fundamental basics of what Magisk does with it's modules...
[Magisk] kotvmeshke:
Good day! Write with the help translation. Have a problem with your Huawei P10 emui 9, Android 9. When installing beta Magisk side faces of the screen are not active, about 5 millimeters on each side. Is there a way to solve the problem?
[Magisk] demonoidmaster:
And you're suspect asf, why email him? You wanna know if you can buy him out like Chainfire did selling SuperSU ? Ya ain't getting nada if Magisk is what you're after
[Magisk] Microsnow:
Magisk won't work after android update

Hi there,

I really hope this is the right place to post this. I'm new here and I'm not 100% sure whether this is the right place or not, but after some research I thought this was the most appropriate of the one I've seen.

I had Magisk installed in my Xiaomi Mi A1 working fine and without any trouble. I decided to update it a month back (the phone) and when It came out updated, magisk was no longer installed I tried to update it with the zip but then this log always comes out:

- Copying image to cache

- Device platform: arm64-v8a

- Existing zip found

- Extracting files

- Unpacking boot image

MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

No boot image magic found!

! Unable to unpack boot image

! Installation failed

I updated my phone to android Pie yesterday to see if I was able to install magisk this time, but the same log shows up every time.

As I sad my device is a Xiaomi MI A1 currently with Android 9.0 the bootloader is opened and no custom kernel was ever involved as far as I know.

Thanks in advance! :)
[Magisk] demonoidmaster:
Uhh, Magisk now downloads zips to Download folder, Topjohnwu changed that a while ago, doesn't use Magisk folder anymore

As for internet connection, i ain't got no issue on my end ever so mostly it could be either your internet not working right or such, clear the Magisk Manager app data and try again, might work then

---------- Post added at 12:51 PM ---------- Previous post was at 12:44 PM ----------

That flashing text doesn't look like the usual text that outputs when flashing the magisk zip ? are you using the zip from the main thread or? Also the text refers to some boot img it keeps finding in your storage, try getting rid of the cached premade boot img and have the zip do it's thing naturally via using your current boot image

Understand that sometimes premade boot imgs just won't work, when that happens just don't use it and instead let magisk make a new one
[Magisk] nikal:
[MENTION=4667597]Didgeridoohan[/MENTION]

Just to update on my root detection issues. First of all, to make the test I used TWRP and created a backup/copy of my running system which then was cleared from other apps that use root and installed only Adaway and TB along with matlog. That's why logs are so "lean". Now regarding my issue. I was trying to get another one log using the Canary release but not the one with the debug flag ON, by mistake. Well, with this version which is considered not stable and probably buggy, both Adaway and TB (and any other root aware app that I have used ever since) work without issues so far.

Therefore, I am using now Magisk Canary release channel and I will report any possible issue in the future if any. As for the moment, I will consider my issue Fixed.

Thanks for your time.
[Magisk] zfk110:
since I was failing CTS profile, on my tablet I used Samsung Note 4 and then Note 8 fingerprints but using any of those made it worst now I'm failing Safetynet check with CTS failing

Microsoft Windows [Version 6.1.7601]

Copyright (c) TeamOS{RoHiT} Corporation. All rights reserved.

D:\SM-N910T-4.4.4\910V\fastboot>adb shell getprop ro.build.fingerprint

samsung/gtaxlwifixx/gtaxlwifi:7.0/NRD90M/T580XXU2BRB2:user/release-keys

so I ran this on my other tablet which is passing safetynet, I got this info so how can I download or find this file samsung/gtaxlwifixx/gtaxlwifi:7.0/NRD90M/T580XXU2BRB2:user/release-keys and then move to my other tablet and then save in it so I can pass cts profile? I looked around on this link

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

but I didn't get that info about how to get that file then move and then save it on another similar tablet to get the CTS pass?

edit

OK so I created this file attached with this message,and moved to CTS failing tablet's root but when I got to Terminal and type Props, I don't see option for "The fingerprints added to this list will be found under the Custom category in the fingerprints menu"
[Magisk] jcmm11:
It's not a file. It's simply a string associated with the ro.build.fingerprint entry in build prop. I'm pretty sure that [MENTION=4667597]Didgeridoohan[/MENTION] has documented how to add your own string using MagiskHidePropsConf
[Magisk] Didgeridoohan:
The file works fine (I tested here) and it should show up in the fingerprints list (option 1 in the main menu and then option f).
[Magisk] zfk110:
I was able to install it using custom, but now Im failing safetynet with CTS profile
[Magisk] dan60:
Thanks for the hint, but, please, how would I grab a logcat when it freezes? I've never done such a thing before.

EDITED: Oops! I've found out you've provided such answer already. Thank you!
[Magisk] castlekeep:
im not 100% sure i used the guide here https://xdaforums.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616

but with the v8 bootloader (after the root superSu is on my phone now)
[Magisk] jcmm11:
You're rooted with, an apparently customized, version of SuperSU. Based on what I've seen very briefly glancing through that thread I don't know if Magisk will work for you or not. He's using eng boot images and customized Odin.

I don't want to say more because I don't do Samsung and I'm afraid of sending you in the wrong direction. If you want to try it just be ready to reset the phone and start from scratch. Make sure you have backups and you know how to recover from a soft brick.
[Magisk] Didgeridoohan:
The fingerprint is good (I tested it), but have you ever been able to pass the Basic Integrity check? If not, you've got other issues...

First thing to do is to toggle MagiskHide off and on in the Manager settings, that might get it running again. It's also good to confirm that MagiskHide is actually working, by adding a root app to the Hide list and see if it still can detect root. More details here: https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] dope77:
Got this error while installing Greenify4Magisk-v4.5.1

- Copying zip to temp directory

- Installing Greenify4Magisk-v4.5.1_(BETA).zip

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

inflating: common/unityfiles.tar.xz

Killed

! Installation failed

And magisk hide isn't working, i tried turning it off and on, but when turning it off it just turns on by itself, tried reflashing 18.0 again but still same problem
[Magisk] 气人小萌新:
You misunderstood, I just want to ask a few questions.
[Magisk] Harlock1978:
Every App that I add to Magiskhide freeze with a white screen when I start it. Everything is working fine when I remove from the Magiskhide list.

I try also with app not looking if your telephone is rooted or not like Amazon or Navybattle
[Magisk] guest4711:
Ask then here in the forum, and you'll get some answers (but perhaps not from TopJohn himself, but from other members).
[Magisk] 气人小萌新:
I have already asked the question and got a solution, although it doesn't work.
[Magisk] Fabbrox:
Guys, Pokemon go is detecting my magisk! Any solutions? I've hidden the app and reinstalled with different package name but nothing..

And I can't find a Magisk folder into the phone
[Magisk] garylawwd:
Did you pass cts profile check?
[Magisk] Fabbrox:
I've passed all test on the magisk app
[Magisk] coolman7:
I had Magisk 17.1 on LeTV X600 EUI 5.9 23S (Android 6.0). I saw there is an update to Magisk 18.0. I choose to update Magisk with Magisk Manager's recommended method. Magisk Manager said update is completed and I press reboot button. Phone restarted but dropped in boot loop. Constantly rebooted itself. So I decided to open TWRP and restore from a backup. But TWRP dropped in bootloop too. So I cannot open TWRP too. I only can open fastboot. I flashed TWRP again with fastboot, but nothing has changed. I flashed stock recovery. Nothing has changed. I downloaded unbrick ROM from internet and flashed boot.img from unbrick ROM with fastboot. Now I can open TWRP but I can't boot into android. If I select boot to system from TWRP, it boots into TWRP again. I restored a previous TWRP backup. But nothing chanaged again. I flashed a stock ROM with TWRP. No change. So I decided to flash unbrick ROM with SP Flash Tool. After flashing, my phone bricked. I can't open fastboot or recovery. Now I just only can flash with SP Flash Tool. But flashing unbrick ROM does not change anything. My phone is still bricked.

Anybody experiences similar problems after upgrading Magisk? What should be solution before flashing unbrick ROM with SP Flash Tool which ruined my phone.

Thanks