yashsingh1/xdaforums huggingface dataset:
[Magisk] grantdb:
I have redone the uninstaller method and only selected one app in hide menu (my banking app) and everything seems great. Passes safetynet (using a different fingerprint entry in build.prop) with only the banking app selected in hide. Systemless hosts with Adaway working perfectly as well.

Thank you!
[Magisk] neox456:
Help! There is a bug with Magisk Updater. It did not update Magisk, but update my rom to 8.1.0 and non-root instead of keep 7.0 and update Magisk!
[Magisk] xunholyx:
Magisk won't update your ROM. It's impossible for it to do that.
[Magisk] neox456:
:( I always ignored the popup, because I did not wanted it. But now it is here...
[Magisk] la_comedia:
Hey guys,

I'm at the end of my rope here. No installing method works for me.

I'm on a Xiaomi Redmi 4x (santoni) with the latest Nitrogen OS. I use TWRP for flashing.

Updating in the App didn't take.

Flashing in TWRP didn't work.

Patching the boot.img failed.

I flashed back the Stock UI from Xiaomi, flashed Nitrogen new, but all the methods still fail.

What else can I try?
[Magisk] Soumy1234:
Did you try the uninstall.zip? If you are going to use it, it'll wipe your modules, so be warned.
[Magisk] stibich:
The modules are not loading in Vibe k5 with AEX 5.7, I used several modules and not one worked.

Sorry for English because I'm using the Gboard translator.
[Magisk] Fedroid:
On mine and my friends huawei P8Lite 2015 with magisk 17.1 phone turns itself on when pluged to Usb being powered off. So, we are not able of charging our switched off phones because they turn on when plugged to charger.

Happens on single an dual sim versions with all kind of roms.

Best regards
[Magisk] la_comedia:
Hey Soumy1234,

thanks for your reply.

Since I did a clean install from Stock-Rom, there was nothing to uninstall.

So yes, I tried, but it didn't work.
[Magisk] Johnn78:
Is this rom which you have treble ?
[Magisk] xunholyx:
Stock rooted Pixel 2XL, so yeah.
[Magisk] opp820:
when 17.2 version will be realesed??

I had many issues with 17.1
[Magisk] Johnn78:
Is this possible to get ota due to android one ?
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] ordered a new laptop and is waiting to receive it to do further development. He is switching from Windows to a MacBook Pro. This is from his twitter feed.
[Magisk] opp820:
can I go back to 16.7 version ?

It was stable as rock
[Magisk] Badger50:
Sure you can. Just flash the uninstaller zip, then flash the version you want :good:
[Magisk] heindrix:
Hi [MENTION=4470081]topjohnwu[/MENTION] and [MENTION=4667597]Didgeridoohan[/MENTION],

Yes, i can confirm that after latest Patch Update (Patch01) from Huawei, Magisk is not working anymore.

The device will just stuck on boot message.

The details are the same as the post by [MENTION=6870018]Tecalote[/MENTION] : https://xdaforums.com/showpost.php?p=77418253&postcount=6557

I'm using Huawei Nova 2s EMUI 8.0.

Bumped until someone figure it out.

I don't know if this can help, but i've attached kernel and ramdisk image before update patch and after update patch.
[Magisk] bohemist:
I did that just by flashing 16.x over 17.x

However, all the modules were lost.

Right now, I'm running 17.1 as it works stable on my second try. My first try made my OnePlus 6 in a bootloop.
[Magisk] shadavis08:
Hello anyone
[Magisk] Soumy1234:
I guess the only thing we can do is wait for 17.2...:(

Maybe you can go back to a previous version for now.
[Magisk] Julian CM Kwan:
Does anyone having random reboot after installing magisk 17.1? I'm running Resurrection remix Nougat 7.1.2, in my first flash it went to boot loop but after flashing the latest uninstall magisk zip and re flash Magisk 17.1 it booted normally. But having boot loop about once a day. Any advice and feed back is very much appreciated. Thanking in advance.
[Magisk] zhuhang:
User data & Internal storage wiped after flashing 17.1 via TWRP

Flash samsung stock rom build A720FXXU3CRF3 (BL, AP, CP, HOME_CSC) using Odin. Then flash TWRP.

Boot into TWRP, flash Magisk 17.1 zip, flash no-verity-opt-encrypt zip, reboot system, found myself that the Internal storage + data wiped.

In what occasion does Magisk wipe user-data??
[Magisk] shadowcliffs:
My moto z2 force was happily on v. 16 until I responded to the notification to upgrade, not 17.1 won't install and the root is gone.
[Magisk] wes'side:
I'm laughing at the posts because, o boy, do j have some issues, with my device... Lol. So I do on occasion have random restarts out of no where, I had no duce thing when 16.0 an 5.70 where good, now I'm at 17.1 an 5.9.0. I'm getting some things I flashed to update through the mod even through twrp they'll be installed it will show it being cool till next restart, then it's like I never flashed at all an have to repeat it, it's not just 1 mod, it's at least 5 or 6 that I flashed at once or one at a time a restart each one but it won't keep the mod flashed permanently, I'm on a nexus 6p firehound an ex kernel, the phone was extremely stable after my ROMs new update, it was flawless with xposed mods running as well. Maybe I'll go back to the ol set up till the next update to 17.2. My as well been a beta update than stable.

---------- Post added at 03:53 AM ---------- Previous post was at 03:51 AM ----------

May as well went to a Linux, may I suggest Linux mint
[Magisk] cloudblue:
Just installed 17.1 on Moto E xt1766 Qualcomm stock rom and recovery ( I fastboot boot SQUID2 'S TWRP when needed). Root enabled and all's well so far. Question:. Do I need TWRP to "Install" Magisk modules natively? I ask because the first module I tried to install (Xposed framework) failed. Thanks in advance for any insight.
[Magisk] martyfender:
Honor Re-Opens bootloader Unlocking on a Limited Trial for XDA:

https://xdaforums.com/honor-view-10/development/honor-bootloader-unlocking-limited-t3837880
[Magisk] qubyx:
Works perfectly on my stock Nexus 6p! Thanks.

Hope that multirom support comes.
[Magisk] KaMyKaSii:
Install XInternalSD module and allows full access to sd card
[Magisk] james_rokr:
Of course dude, this is what I did

So the order would be:

*go back to stock (FW+Gapps)

*flash custom kernel (if needed)

*enable su from CM13 developer options

*boot to twrp and erase the root under bin and xbin

*reboot

*flash magisk and phh (dont open magisk yet)

*install phh app

*open magisk and try to toggle root, when phh ask grant permissions

enjoy
[Magisk] Nexus11:
_

---------- Post added at 02:05 AM ---------- Previous post was at 02:04 AM ----------

[/COLOR]

What's the bump method use now? Haven't had to for the last 2 years
[Magisk] -chaotix-:
Nested ramdisk (e.g. Sony Xperia Z Ultra - Cyanogenmod 12.1)

Attached is a modified Magisk v6 ZIP that should work on boot images with nested ramdisks. I don't know what devices this is applicable to but it works for my Sony Xperia Z Ultra with Cyanogenmod 12.1 installed. I guess other devices with nested ramdisk (at least with Cyanogenmod) should work too. I haven't tested it with the Sony stock ROM. It might work, it might not. I would not be surprised if it would work with other "only one boot image"-devices with Cyanogenmod installed. Other ROMs might handle the switch to recovery or boot differently or just give the second ramdisk a different name.

What is the problem?

Some devices (like Sonys) don't have a separate kernel for their recovery. They boot the regular kernel with a ramdisk that checks if the user presses any button and then enter the recovery. Otherwise they boot into the regular system. To do this there is a different ramdisk that get's extracted for the recovery and for the regular boot that handle the normal startup. Currently Magisk does not know about the nested ramdisk and tries to modify the outer ramdisk. This does not have the desired effect and results in a bootloop (at least in my case).

What to do about this?

My modification alters the way Magisk un- and repacks the ramdisks. It checks if there is a file 'sbin/ramdisk.cpio' inside the first ramdisk and then also unpacks this archive. On repack it does the opposite and first recreates the file 'sbin/ramdisk.cpio', then the outer ramdisk.

What to do if it still does not work?

If your device also has a nested cpio ramdisk it should be easy to modify the modification. Unpack your boot image, gunzip the ramdisk and use cpio to extract it. Now look for the name of the nested ramdisk archive. Now modify META-INF/com/google/android/update-binary in my ZIP file. There is a line

INNERRAMDISKFILES="sbin/ramdisk.cpio otherpath/otherramdisk.cpio"

Just change "otherpath/otherramdisk.cpio" to the name of your inner ramdisk archive. Repack everything and try to flash it. Good luck.

Precautions:

If modifying the boot image does not work and the result is unbootable you might have a problem with these devices that have just one kernel image. You might not be able to boot into your recovery again. So before leaving the recovery to test if it worked, save /data/stock_boot.img to your PC after flashing the ZIP. If your device does not boot anymore afterwards, just "fastboot flash boot stock_boot.img". This should restore your device to the way it was before. But as always: I don't guarantee anything. Destroy your devices at your own risk.
[Magisk] Captain_Throwback:
If you're going to uninstall system apps with Titanium Backup, then I don't understand why you're using Magisk :confused:.
[Magisk] teddy0209:
I don't know the update, but there should be a flashable zip or something to make it easier or you can do it the old way... Broke my G3... ????????????

Edit: try searching for cbump, if I remember correctly... ?
[Magisk] stangri:
Magisk v6 is working fine on N6 with Nougat DP5. Even made my LED enabler systemless. You may want to freeze system apps instead of uninstalling them if you want to be able to use OTA updates.
[Magisk] Captain_Throwback:
You can also "uninstall" them using Magisk.
[Magisk] Tlailaxu:
I also get "SU binary out of date" notification each time i restart the phone. Root is working but sometimes does not react and doesn´t let me toggle on or off. When this happens, i have to go to developer settings, toggle root off and back on to app only and re-open the Magisk Manager. Then i can toggle it on and off without problems. The Extra step isn´t what irritates me but the message about the binary beeing out of date.

This happens on a Galaxy S3 LTE with Ressurektion Remix 6.01 rom
[Magisk] arsenal3010:
Thanks for your reply !

I have upgraded TWRP to the latest version following this thread http://xdaforums.com/zenfone-5/development/recovery-twrp-3-0-2-0-asus-zenfone-5-t3355749

Also checked again and make sure /system is ro

Still same problem happened... (/sytem could not be mounted)

- Mounting /system(ro), /cache, /data

! Failed: /system could not be mounted!

Updater process ended with ERROR: 1

I:Legacy property environment disabled.

Error installing zip file '/sdcard/Download/Magisk-v6 (2).zip'

Updating partition details...

Please help me to check the log also
[Magisk] DerpleNerple2000:
I just had some duplicate apps, like 2 clocks, along with apps like Gallery (prefer to use G. Photos). Does removing them cause safetynet to fail?

I'm not really worried about the OTA part. I like to use Tupac4U's "stock" n6 build that comes with basics like busybox and root (SuperSU, but im asking if he considered the phh method at all), so I have to flash a new zip every time anyway.

EDIT: I might try to just use a stock image when the Nexus 6 Nougat images come out. Do you know if busybox would trip Safetynet?
[Magisk] Kiid:
Make your changes in magisk/.core/dummy/system..
[Magisk] snke:
Use selinux in permissive mode and substratum works ?
[Magisk] thoiloidainhan:
Do u use android pay or pokemon go? If u aren't worried about ota, and don't use those apps then there's no need to use magisk. Just flash that ROM u mentioned and enjoy. Root is the only thing needed to uninstall bloated system apps with tibu
[Magisk] rignfool:
That is so not true...

Regardless of whether you use Magisk for root cloaking... Has nothing to do with its ability to have system modifications survive dirty flashes... Which is like 50,000 times more useful... And will not be coded around like safetynet will
[Magisk] thoiloidainhan:
Cool another application of magisk. Though i m sure 80% of the traffic here gotta do with those 2 apps. Noticed the surge of new pogo related questions since last week? Anyways the poster I'm responding to seems to have missed the point of using magisk if he only needed root to remove the 2nd clock.
[Magisk] :
N ROMs built from source are also failing so it is not the mods.
[Magisk] DerpleNerple2000:
I actually wiped my phone again, and I installed one of the N Dev preview builds. Its almost done setting up, and I plan to flash Magisk + phh systemless right off to the bat (with elementalX) to see if it works.

---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------

I'd like to try using Android Pay, but I really can't leave Viper4Android behind for it. Since they have a systemless version of v4a, I thought I'd give it a shot. Also, when did Pokemon GO fail to launch with root? I used it the other day and it launched fine w/ SuperSU installed and active.
[Magisk] Wolfchilla:
Samsung Tab S 8.4

Hi, I'm running a Samsung Galaxy Tab S 8.4 and I've completed the instructions and could get everything working except the toggle for unmounting root. It keeps flipping back to on position even though it's been granted root access and all my other rooted apps work.

It also has the SELinux option greyed out with the message that "Samsung do not support switching SELinux status!"

I know this method doesn't work on some Samsung's, is my device one of them?

Also, I did the full uninstall of chainfire's SuperSU. Pokemon Go was working in my unrooted device before I started flashing the Magisk, Magisk phhSuperSU, then installing phhSSU and the manager. Am I missing anything?
[Magisk] OscarBaia:
Hello... can anyone point me to the magisk 17.1 lynk for Samsung S8+?

Thank you so much in advance
[Magisk] cloudblue:
https://github.com/topjohnwu/Magisk/releases
[Magisk] paulesteban94:
Failed SafetyNet Samsung S7 Oreo

Hi everyone.

I updated my Android to last Oreo for my S7 Exynos (July update) and my Magisk from v16 to v17. 1 and now can't pass the SafetyNet test.

[IMG="Failed SafetyNet Samsung S7 Oreo"]https://ibb.co/eENnUe[/IMG]

Sometimes pass the test with a reboot, but later of a few minutes something happen and failed the SafetyNet test again and it stay that way.

I hope can help the report and in a future fix this. Thanks for this useful app.

Sorry for my English.
[Magisk] martyfender:
They don't charge when turned on, on a charger? WTF, my devices always charge when they are turned on, on a charger, that is not normal?
[Magisk] Soumy1234:
I just noticed that the magisk downloads page isn't alphabetically organized. I also lost Play store verification and safetynet checks take forever. After two hours magisk was still checking...
[Magisk] martyfender:
You should be able to, but I think you should use the latest Magisk uninstaller.zip before you do.

---------- Post added at 11:51 PM ---------- Previous post was at 11:48 PM ----------

Doesn't just flashing the Samsung stock rom, wipe your data?
[Magisk] DiamondJohn:
I have tried searching the thread, and the search functionality crashes on me:mad: so sorry if its been asked and answered many times before.:o

I have also read the release notes for Magisc v17.1 at https://xdaforums.com/showpost.php?p=77496559&postcount=45

But I am missing as to where the boot script folders for service.d and post-fs-data.d are now located under 17.1? previously I was using /magisk/.core/service.d but now I cant seem to find where I need to move my scripts to, and the installer has not done this for me automatically, so my boot scripts are not running :crying:

Can someone please tell me where these folder locations have move to under v17.1?
[Magisk] yochananmarqos:
Magisk does not wipe anything. Encrypting the data partition does.
[Magisk] martyfender:
I also use Linux Mint but [MENTION=4470081]topjohnwu[/MENTION] stated on his twitter feed:

Linux Mint is more than great for my daily usage, but I suspect that since he is a Grad student and at the University of Michigan, that apps that he needs to use there are not available in Linux.

If that is true, it is ironic since he is pursuing, I believe, an MS, or possibly an MA, in the School of Computer Science.

He rarely replies, but maybe he will clarify?
[Magisk] OscarBaia:
Thanks :)
[Magisk] amit3880:
[MENTION=5417899]DiamondJohn[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION]

Guys I am trying to investigate the issue with Blackberry work app detecting the root and was reading the https://www.didgeridoohan.com/magisk/MagiskHideBasics support page.

It says :

Logging must be enabled. Magisk uses logging to monitor what apps/processes to hide root from. If you've disabled logd, manually or with an app like Kernel Adiutor, MagiskHide won't work.

Now the question is , how can I know if the logging is enabled or not? I am not sure how to check that.? However other apps are simply able to work with MagiskHide so it must be enabled but still want to make sure if I am not missing that one.

Thanks in advance.
[Magisk] tom1807:
Had a last night a tough time to get everything working, which was partly my fault.

After reading last night the "horror stories" about bootloop with v17 and despite that v17.1 was already available I thought go the "safe" way.

Coming from Magisk Manager 5.8.4 Beta and Magisk 16.8 Beta (I needed Google Pay work) I went directly the Uninstall route by booting into Blu Spark TWRP and flashed Magisk Uninstall and flashed v17.1 directly from TWRP.

After booting normal the mobile Magisk Manager was also uninstalled and I tried to install MM 5.9.1 which failed every single time, same as MM5.8.3.

The only way to get it installed was installing MM 5.8.4 again (no problems here) uninstall it again in Android and then could install MM 5.9.1.

The previous rooting with 17.1 was not successful according to MM 5.9.1

So reboot into recovery again, installed v17.1 and all was fine. (Before that I had to install TWRP again)

SafetyNet passes, Google Play Store sees the device as certified.

Cheers

Tom
[Magisk] purgy:
I had a similar issue, where the script I had didn't seem to be running (flashing the uninstaller, and reinstalling fixed it for me) eventually I found the script at

/sbin/.core/img/.core/post-fs-data.d

service.d is also located in the second .core folder

I think the /magisk folder just redirected to the current location, but it was a much more convenient way of accessing the startup scripts, hopefully it will return in a later version.
[Magisk] guest4711:
The presence of the /magisk folder is used by some apps for claiming that your phone is rooted. So it"s gone in betas for months...
[Magisk] shailesh406:
Not Working on moto z2 Play

Dear sir,

please help me i was on 16.0 magisk on moto z2 Play on stock rom and after updating 17.1 it stuck on startup screen

please tell me what to do.. please please

thanks in advance
[Magisk] DiamondJohn:
Then I think I have a bigger issue.

I located the directory, and the upgrade DID copy my boot-script over to the new location (service.d) but It isnt running :mad: attached is the log from a boot.

Any place is fine for me, as long as I know where it is.;)

I don't run beta's, so the upgrade was my first introduction to the change.

At the end of the log (as attached), it appears to say it is running my script, but it mustn't be, as there is no output logging.

09-04 15:37:28.320 347 485 I Magisk : ** late_start service mode running
09-04 15:37:28.320 347 485 I Magisk : * Running service.d scripts
09-04 15:37:28.320 347 485 I Magisk : service.d: exec [[COLOR="Blue"]zz99_userasynch[/COLOR]]
09-04 15:37:28.533 347 485 I Magisk : * Running module service scripts
09-04 15:37:28.533 347 485 I Magisk : ViPER4AndroidFX: exec [service.sh]
09-04 15:37:55.673 347 367 I Magisk : proc_monitor: com.google.android.gms.unstable

The script has execute permissions (actually 755) and it executed as expected in previous versions, and if I run it from the shell, it also runs correctly:

su;
sh /sbin/.core/img/.core/service.d/zz99_userasynch

Anyone got an idea what I am missing or what needs to be done to get it to run?
[Magisk] daveraver:
Yes, it is right, the same here with a P8 lite 2015. I hope will be solved on next magisk releases, Thanks!!
[Magisk] FlavioV:
The downloads page is sorted by last update by default. If you want to set alphabetical order just tap the second to last button in the top.
[Magisk] Didgeridoohan:
[MENTION=5417899]DiamondJohn[/MENTION] What is the script supposed to do (maybe upload it)? As you see in the Magisk log, the script is running (there won't be any more output than that in the Magisk log, if you want logging for the script, you'll have to add that yourself).
[Magisk] DiamondJohn:
The script is a complex script which wraps and also replaces at the same time, busybox "runparts", calling another bunch of scripts held within another directory (multiple) in an asynchronous (or synchronous) manner, depending on the folder structure of where the script(s) exist. I have built this script and successfully ran it (or previous versions) now for the past 5 years or so.

hmmm i Just checked another thing I do in the script (setprop user.userasynch.active 3) and the property was set, but then I remembered I had just recently manually run the script since boot:o I also log to the logcat from within the script; which also does not get logged.

I reset the prop and rebooted, and the prop is gone. It simply confirms the script isn't running.

I log to two places (in addition to the logcat and a setprop). These being /data/media/0/User/Logs/Log/ (which does exist, and the script creates it if it doesn't anyway) and a log for this "base" script in /data/anr/ (as a fall back to help debug an issue, like this) Neither places contain a log file :mad:

I guess a test with a simple script is called for, to see what is not happening. Posting the actual script would more than confuse the issue. I'll get back to you either way with those results.

I just had a thought that maybe something (like busybox, stericson) had moved, but then I remembered it worked fine with Magisk 16.0 stable :( and all I changed was a Magisk upgrade ie ROM is the same.
[Magisk] abdoh01:
hi guys after number of bootloop and flashing the stock rom cause of magisk 17.1 i finally get successful installing by uninstall magisk 16.7 from magisk manager than uninstall magsik manager than go twrp and flash magisk 17.1 it worked and get citified in lg k10 so the problem was installing the magsik manager 5.9.1 on 5.8.3
[Magisk] ReZzA_No.1:
Well after a brief look over previous posts it was mostly about bootloops :\

I upgraded to 17.1 from 16.4. Everything was fine on 16.4 and i didn't face bootloop but after booting up none of modules were working. I uninstalled magisk and then installed v17.1 again then installed all modules from repo but nothing fixed.

Then i found out something weird, if i install just 1 Or 2 modules they would work fine but when i install all of them (its about 10 for me) they all stop working.

The log below is after i had installed 2 modules (which were working) and on this reboot there were some new ones (none working)

There are some other point that may help, Apps2sd works fine xposed reports that framework is installed but not active.
[Magisk] eliezerjk90:
I had a problem with a/b update on my mi a1. I've follow the steps described here

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md

It always give installation failed result. My suspicion is that I unintentionally change the permission of the system partition to 755 (write for owner) since I used file manager with root access. My question is, will simply revert the permission to 555 solve the problem (only read and execute)? Secondly, I found some directories with sys related naming (/system, /sys, /system_root). Will sys and system_root also be checked during OTA?