yashsingh1/xdaforums huggingface dataset:
[Magisk] JudgeDread11:
Yes it will be. As long as we will find ways to bypass security they will counter that. They have to, or they will have to abandon safety net ask together, which would give Android a bad name as in an insecure platform. And then companies like banks etc would stop providing their services for Android devices.

But we should be happy that they choose the way of safety net while still giving us the option to choose to root and not use safety net required apps. They could have chosen to focus more on countering root completely.

Sorry for OT.
[Magisk] DarkN3ss61:
Cannot toggle root or SE

I uninstalled magisk (v1)

flashed update to my OS

installed magisk again

flashed root apk

booted up

installed magisk manager

Opened, no option to toggle on and off as the switch is disabled

Help please.

OnePlus 3 3.2.6
[Magisk] joshuaw84:
Did you remember superuser app from playstore?
[Magisk] DarkN3ss61:
Whoops forgot that! Thanks, it now works
[Magisk] C-3OP:
I have created a Magisk module and have the following problem:

The author and description are not displayed ( No Info provided), installation and function of the module works fine, name and version are displayed normally. What could I have done wrong, I used the Magisk template and also entered everything in module.prop.
[Magisk] jcmm11:
Show the contents of module.prop. You must have entered something wrong in there.
[Magisk] Didgeridoohan:
First guess is that you've added a decimal in the versionCode. It needs to be an integer or things won't work as they should.
[Magisk] C-3OP:
This is my current module.prop:

id=MoreHavocFonts

name=More Fonts for Havoc OS 2.0[9.X]

version=v1.2

versionCode=1.2

author=C-3OP

description=Replaces the original Havoc-Fonts.apk with a pimped up Version

minMagisk=17000

(And here are my modules: https://xdaforums.com/apps/magisk/module-fonts-havoc-2-0-skydragon-t3882764)

---------- Post added at 11:43 AM ---------- Previous post was at 11:23 AM ----------

That's it! 1000 thanks, nice if it's so easy to fix...
[Magisk] Didgeridoohan:
Yup... There's your problem. Here's some reading for future reference:

https://topjohnwu.github.io/Magisk/guides.html#magisk-modules
[Magisk] madkiran:
Thanks bro.. that seems working :good:
[Magisk] rudolfm:
Hi,

I installed the latest Magisk on my phone by patching the boot and flashing it with Spflashtool. The manager is able to reflash, so basically, root must be there. But no app can aquire root, all requests time out. I also don't get a toast.

I tried these settings:

Apps only, Apps and ADB

Prompt, Grant

Device Owner Only, User-Independent

Core Only

I tried letting the app request root and then I switched the manager to foreground while app was waiting for root.

I installed the stuff I found on the Canary thead. These binaries are different, but have the same version number as the stable.

Magisk log says "su: request rejected" followed by userid for each attempt.

Apps: Afwall+, Total Commander, Busybox, Terminal (jackpal, typing "su").

Another post probably had same problem:

https://xdaforums.com/showpost.php?p=78493804&postcount=29960

Device is ZTE A510, Android 6.0, kernel 3.18.19, MT6735P chipset.

If you need logs, tell my which. Thanks in advance for help.
[Magisk] miststudent2011:
Hi is paytm is working for you with magisk v18.0, it is detecting root for me.

magiskhide is enabled.
[Magisk] martyfender:
Make sure that the Magisk Manager is removed from battery optimization in Android settings, battery, or where ever it is in your particular ROM.

I believe another user reported that turning off Magisk Hide solved the root access problem.
[Magisk] KiraYamatoSD:
After update to v18.0 from v16.7, the Samsung Note 8 screen is not responding after the screen standby. The fingerprint sensor is responding which can unlock the device, however, swiping does not respond.

Is there any solution for this, or should I stick to v16.7?
[Magisk] Pkt_Lnt:
I've not seen that issue reported, but I could have missed it. The sure way to find a solution is to provide logs.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] KiraYamatoSD:
I am not sure how to get the logs for this issue. However, there have been some reported cases regarding this issue, but there has been no solution.
[Magisk] Pkt_Lnt:
A logcat will almost certainly show what it happening. Here is a tutorial from XDA Developers. :D :good:

There are many apps if you search "logcat app" your prefered app store. I know XDA Developers web site has many from developers here as well. Matlog, aLogcat, ad nauseum....
[Magisk] xunholyx:
Just a heads up, CatLog hasn't been updated since Feb 2015 and doesn't seem to work with Android 9.0/ Pie properly (at least with my experience on Pixel 2XL)
[Magisk] jcmm11:
Yes. Matlog is based on, and is the successor to, Catlog
[Magisk] RandomPooka:
I did not know this. I appreciate the heads up. Now I can do like Grandpa Simpson and yell "MATLOCK" every time I take a log.
[Magisk] martyfender:
I have problems with Catlog as well on my Nextbook Ares 8A's, x86, Android 6.0.1 devices. As the logcat scrolls, the text on the page jumps up and down, making it illegible.

My first choice is LogcatX, for it's per app logcat feature, followed by Matlog.
[Magisk] madkiran:
Yeah.. paytm is working fine

(I have enabled "hide magisk manager" from settings
[Magisk] Oswald Boelcke:
Matlog (actually I'm on Matlog Libre from F-droid) is working as advertised; however, for good reasons with all devices still on Nougat i.e. especially no own Pie experiences.
[Magisk] AgustinH:
Hello, I have a Le Max 2 and I was never able to root via Magisk, errors in the patch. With the 18 version I would be able? Have any risk with Marshmallow?
[Magisk] andoruB:
Tried posting this over on the Magisk subreddit, but my posts never got approved for some reason, and they don't show up when I log out, so I'll try here as well.

I'm using a AllView P6 Pro and I've tried updating Magisk through the app from 17.X (forgot the exact version, most likely it was the one stable version immediately preceding) to 18.0.

After doing the upgrade, and restarting the phone, I noticed it got stuck on the Android logo (specific to the maker) and would not boot in the OS.

Since my phone doesn't have a detachable battery, I forced it to reboot, but upon doing that I found out that I could no longer boot into recovery, and it would now boot loop instead of being stuck on the Android logo.

So after this, I was forced to reflash the stock rom. In doing so, I wanted to reflash TWRP afterwards so I could restore a recent backup.

Problem is, that since I have a cheapo/uncommon/old phone, there aren't many stock ROM versions available online, so I was stuck with a 5.1 ROM, while the only available TWRP image for this device works only on 6.X ROMs.

Another problem is that since Magisk borked something in the phone, I can no longer run OTA updates the way I did in the past in order to get TWRP...

​

Could anyone suggest anything to get me out of this pickle?

I know I could've made a backup of the 6.0 Stock ROM from the device, but since I only run Linux on my machines, and the tools available for backing up the system are available only on Windows, I wasn't able to.
[Magisk] emes2:
Can you fix Magisk Hide, so that the Tesco Clubcard application can not detect root?

Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
[Magisk] martyfender:
What do you mean? I create nandroid backups in TWRP and then copy them to my duel boot Linux Mint, through mtp. Since my manufacturer does not provide roms, I keep backed up copies created when the device was new as my stock rom, with boot, system and no data.
[Magisk] andoruB:
I wasn't talking about nandroid backups, but rather low-level backup of all the system partitions, the kind you flash through SPTool (in the case of Mediatek phones)

Regardless of this, as I previously mentioned, I no longer have access to TWRP.

Any solution(s)?
[Magisk] Pkt_Lnt:
I use ADB to backup with Linux Mint daily.

ADB backup and restore. Linux Mint is Ubuntu based, see this tutorial,

https://www.maketecheasier.com/back-up-android-data-adb-ubuntu/
[Magisk] andoruB:
That's for backing up the data partition...

*snip* Besides, taking a backup at this point in time is useless...

What I need right now is the ability to get into TWRP (and proceed with restoring the nandroid backup that I have with the older version of Magisk) or to be able to flash a backup of the stock ROM with Android v6.0

Flashing it with SPFlashTool results the phone in not being able to boot into TWRP, since the available ports of TWRP for this phone require version 6.0 of the stock ROM.

EDIT: I took it too far, sorry.
[Magisk] Pkt_Lnt:
Yes, I did, all posts. :rolleyes:

Sorry for trying to help.
[Magisk] albyone:
I have the latest Magisk 18.0 / 6.1.0 installed on a stock Pixel 2 XL (Android Pie 9.0 December 2018), and all rooted applications work great.

I have the Airwatch/VMWare Email apps 'hidden' (VMware Intelligent Hub, Web Workspace ONE and Content Workspace ONE), which worked great for almost a month. Today, it alerted me that the phone was rooted and deactivated itself.

I didn't upgrade it. I was wondering if you know if it somehow was updated by my company to search for Magisk?

Thanks

---------- Post added at 10:15 PM ---------- Previous post was at 10:15 PM ----------

I have the latest Magisk 18.0 / 6.1.0 installed on a stock Pixel 2 XL (Android Pie 9.0 December 2018), and all rooted applications work great.

I have the Airwatch/VMWare Email apps 'hidden' (VMware Intelligent Hub, Web Workspace ONE and Content Workspace ONE), which worked great for almost a month. Today, it alerted me that the phone was rooted and deactivated itself.

I didn't upgrade it. I was wondering if you know if it somehow was updated by my company to search for Magisk?

Thanks
[Magisk] martyfender:
Have you tried hiding Magisk Manager in its settings? You may also need to delete the apps data and cache for them to forget that they found root, if they happen to save that info.
[Magisk] jcmm11:
If you restore to complete stock 5.0 you should be able to take an OTA after that (if I understand you correctly)
[Magisk] andoruB:
Sure, but...

Basically what happens is that after downloading the OTA update, and I request the phone reboot to do the update, 5% into the process, the update stops, and I get the icon with the bugdroid laying down opened and with exclamation mark above with no error message:

I've tried downloading the OTA update multiple times, in case the download didn't finish properly, or it got corrupted along the way, but I get the same result each and every time...
[Magisk] jcmm11:
Have you tried a factory reset? It sounds like you need to wipe the data partition
[Magisk] andoruB:
Well, I flashed the entire stock ROM with SPFlashTool, and as far as I know, that's basically a factory reset since the stock ROM was backed up in the same state as if it came from the factory. I also didn't do any modifications to the phone after flashing, so I'm not sure what this would achieve, but I'm going to try it regardless. In the meantime, if anyone has any other suggestions, please let me know!
[Magisk] Invisan:
Since the boot.img file i had is a boot.img.p and no "real" boot.img. Is there a way to somehow patch the boot.img.p with magisk and then flash it?
[Magisk] manan001:
Regarding Version 18 of magisk

hi dev @topjohnwu i dont know if anyone has reported this issue with Version 18 stable release. after installation of version 18 safnet passes.

issue:- after adding various modules it breaks safnet does not pass and apps stop working as it dispalys the error of rooted device.

Model used Xiomi MIA1 Pie 9.0
[Magisk] Saswata Chakraborty:
Sorry for asking a stupid question. Does resetting Magisk Manager app (by clearing Data and Cache) creates any problem? Or is it just like resetting any other apps?
[Magisk] guest4711:
It does not create problems. Even better the data for root access and hidelist and all modules are preserved ...
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHideHelp

Details that would be useful:

Verbose logging.

Any kind of module, or only specific modules?

Etc...
[Magisk] noukon:
Will there be any issues if I downgrade to Magisk 17.3 because I have to keep restarting my phone for safetynet to pass ? (other people reported the same problem here: https://xdaforums.com/apps/magisk/redmi-note-5-pro-whyred-fails-safetynet-t3881097)
[Magisk] Oswald Boelcke:
Are you aware there's a whole and very active thread by @Didgeridoohan dedicated to "MagiskHide Props Config - SafetyNet, improved hiding, prop edits, and more"? Maybe a great and probably better place to discuss SafetyNet issues...
[Magisk] ktmom:
Downgrading will probably solved your immediate problem, but the right "answer" is to help identify the core problem. See [MENTION=4667597]Didgeridoohan[/MENTION]'s Magisk and MagiskHide Installation and Troubleshooting guide: MagiskHelp

. Probably getting a logcat using adb making it easier cover a long period of time in order to capture the timeframe where safetynet is lost.

You might also remove any modules you have installed and see if the safetynet problem continues.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] AntholifeV2:
Hello guys !

I own a S9. I already know how to install magisk and everything around it ... But I would like a subtlety! I'm trying to root my S9 without TWRP (Odin Method / Boot patcher) So I managed to install Magisk. The problem is that I would like to keep the update OTA! ( it's for her that I tried without twrp ..) Alas even after her, the OTAs cut themselves. Someone to a solution to have MAGISK AND OTA UPDATE please?

It is really impossible to keep OTAs with a root ??
[Magisk] jcmm11:
See https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

It's possible to keep root with an A/B device but otherwise you can apply the OTA but will lose root in the process, so you'll have to re-root via a PC.
[Magisk] AntholifeV2:
Top ! Thank you so much ! After reading, I got my answer. I do not have a partition A / B on the S9 unfortunately (Is it possible to change this system? I think by changing the manufacturer rom, taking care of this, so with a google rom I should have a partition A / B ??) . For now I just have to restore the images via magisk and presto! I was stupid I thought about recovery stock, but I forgot that magisk was working on the image boot.img .. everything is clear now thanks!
[Magisk] ktmom:
No, either the device is setup as an A/B partition or it is not. The bootloader is designed to manage the boot priority on an A/B device so you would have to develop a new bootloaders plus have sufficient eMMC space to have duplicates of all partitions.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] robintan5566:
Hi,

I'm having issue installing the magisk v18. I'm using M9 plus TV box. Below is the installation log. Could someone help me? Many thanks.

- Detecting target image

- Target image: /dev/block/boot

- Device platform: armeabi-v7a

- Existing zip found

- Extracting files

- Unpacking boot image

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

Parsing boot image: [/dev/block/boot]

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

- Checking ramdisk status

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

Loading cpio: [ramdisk.cpio]

- Stock boot image detected

- Backing up stock boot image

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

Compressing to [stock_boot_4feb81dde4715972df6473dc0542873cde5de690.img.gz]

- Patching ramdisk

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

Loading cpio: [ramdisk.cpio]

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Loading cpio: [ramdisk.cpio.orig]

Backup mismatch entry: [init] -> [.backup/init]

Add entry [.backup/.magisk] (0000)

Dump cpio: [ramdisk.cpio]

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

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

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

- Repacking boot image

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

Parsing boot image: [/dev/block/boot]

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

Repack to boot image: [new-boot.img]

! Unable to repack boot image!

Segmentation fault

! Installation failed
[Magisk] martyfender:
For any of you on Sony ELF format devices, Boot Bridge for Sony ELF has been updated to work with Magisk v17+.

https://xdaforums.com/crossdevice-dev/sony/mod-boot-bridge-sony-elf-t3506883
[Magisk] qwer222:
Hi, I am using samsung note 3 SM-N9005 and successfully installed the magisk v18 by patch boot image using magisk manager. But when I open app which need root, magisk didn't prompt out any message to ask root access. I also tried to set magisk manager setting to auto grant access without prompt, and turn off battery optimization, but it still same issue, root app cannot be use. I use root checker to check root status too and it failed, although magisk manager page show install ok and two green color tick.

Two months ago I had use the old version of magisk and it work fine, anyone know how to install old version of magisk by patch boot image using magisk manager? Because the magisk manager always download latest version of magisk to patch the boot image. Below is my phone details and magisk manager log in attachment.

samsung note 3 SM-N9005

android 5.0

baseband version: N9005DXUGBOK3

kernel version: 3.4.0-6408191
[Magisk] martyfender:
You might first try the Canary debug build to see if that helps.

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

Copy and past the bit.ly linked in the OP in Magisk Manager settings, update channel, custom field. Go back to the main page and swipe down to refresh it. It should offer to download a new mm version you can use to patch a stock boot.img, with.

If it does not, you can download the MM debug apk directly from here:

https://github.com/topjohnwu/magisk_files/tree/master/canary_builds

If you do this, you still need to input the the Canary build url in the update channel, custom area:

https://bit.ly/2MPKGY5

If Canary doesn't work, you can download the older version of the Magisk Manager and Magisk that worked for you in the past, patch a stock boot.img with it and flash it.

I'm not quite sure how to patch it with the older version of Magisk, though, since the update channels will be for newer versions of Magisk.

Maybe you can flash the older Magisk.zip through the add module area of MM?

https://github.com/topjohnwu/Magisk/releases
[Magisk] martyfender:
I saw that you posted on github. [MENTION=4470081]topjohnwu[/MENTION] has asked that you be on the Canary debug builds to report issues there. It also provides more verbose logging.
[Magisk] Sannith namani:
Magisk modules not showing in download section keeps loading

V18.0
[Magisk] Spartacus500:
Try to clear the cache and application data of magisk manager, it has helped me.
[Magisk] nurullah192:
Why there are 2 folders?

After magisk 18 update this happened

[IMG="image"]https://i.imgur.com/iFTslgd.png[/IMG]
[Magisk] Jaymin.0.1910:
This is completely normal. The .core folder is a symlink to .magisk folder.
[Magisk] nurullah192:
I understand Thanks for your quick response.
[Magisk] robintan5566:
Hi, I have uninstalled using the magisk-uninstaller.zip and re-installed using app-full-debug.apk. Below is the installation log. Not sure whether I'm doing this correctly.

- Detecting target image

- Device platform: armeabi-v7a

- Downloading zip

... 0%

- Unpacking boot image

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

Parsing boot image: [/dev/block/boot]

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

- Checking ramdisk status

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

Loading cpio: [ramdisk.cpio]

- Stock boot image detected

- Backing up stock boot image

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

Compressing to [stock_boot_4feb81dde4715972df6473dc0542873cde5de690.img.gz]

- Patching ramdisk

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

Loading cpio: [ramdisk.cpio]

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Loading cpio: [ramdisk.cpio.orig]

Backup mismatch entry: [init] -> [.backup/init]

Add entry [.backup/.magisk] (0000)

Dump cpio: [ramdisk.cpio]

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

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

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

- Repacking boot image

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

Parsing boot image: [/dev/block/boot]

HEADER_VER [0]

KERNEL_SZ [7283099]

RAMDISK_SZ [2708738]

SECOND_SZ [32955]

EXTRA_SZ [0]

RECOV_DTBO_SZ [0]

PAGESIZE [2048]

NAME []

CMDLINE []

CHECKSUM [c13a84edd37cc57f9c2f036cfd3ac3346630cfac]

KERNEL_FMT [lzop]

RAMDISK_FMT [gzip]

Repack to boot image: [new-boot.img]

! Unable to repack boot image!

Segmentation fault

! Installation failed
[Magisk] Didgeridoohan:
[MENTION=9646216]robintan5566[/MENTION] You're not doing things correctly (that's still a log from the stable release)... You don't have to dowload anything extra (app-full-debug.apk) to change to the debug builds. All you need to do is to go to the Manager settings and change the update channel to the Canary debug url you find in the Canary thread (the shortened url). After that you can try again and it'll be the debug build that will install (if it makes any difference, I suspect your device is the issue rather than Magisk).
[Magisk] qwer222:
Hi, I had tried to use old version of Magisk Manager to patch stock boot.img, but it will always download latest version of magisk which is magisk v18 to patch the boot.img. I don't know how to set the custom download channel to download old version of magisk.

Two months ago I am using Magisk Manager v5.8.3 and Magisk v16.7 to patch the boot.img. Is it possible to set magisk manager to download magisk v16.7 only before patch boot.img?