yashsingh1/xdaforums huggingface dataset:
[Magisk] Ash7898:
So I'm running Pie on the OnePlus6 with the BluSpark TWRP. I lost root randomly somehow and now I can't root it back again because I get a "Updater process ended with error: 1". Also, it shows an exclamation mark before "unable to repack boot image".

I tried

- Running the uninstaller and flashing the latest 17.3 from the release thread

- Flashing the stock boot.img and then flashing 17.3

- Even tried flashing a patched boot img to boot but that results in the phone getting stuck at the bootup screen

I'm unable to upload a log here but I can send it to someone if you can help me

Also, all of this is happening for the second time. I already tried formatting everything and flashed stock Rom and I was able to flash Magisk successfully and had root privileges for some time before randomly losing them somehow and then the same errors started coming up.
[Magisk] fleischbanane:
My bank has a new app and I can't open it. Of course it is in my Magisk Hide list.

This is the app: id=de.fiducia.smartphone.android.securego.vr

Here is a log while I open the app: https://pastebin.com/atxDgxFC

I use a OnePlus 6 with the OpenBeta5 and Magisk 17.3.

If I can provide any more data to help please let me know! I hope it can be fixed.
[Magisk] Saswata Chakraborty:
I have one question from a long time. Are magisk modules really system-less? I mean once we uninstall a module, it is completely gone from the device without leaving any trace or effect?
[Magisk] DanGLES3:
They should as they only overlay your system with modules that are stored on magisk.img,once you remove the module all of its files get removed from magisk.img thus removing amy changes caused by those modules
[Magisk] Saswata Chakraborty:
So that means if I flash a module which cause unstability and slow performace, is completely gone from the device after I uninstall it? Or is there a possibility that it may still affect the device (even slightly) after uninstalling the module? (Sorry for asking)
[Magisk] DanGLES3:
Yes,any changes that module did to your system should be gone as soon as the module is removed and the device is rebooted
[Magisk] Saswata Chakraborty:
Thank you so much, buddy! Actually, I don't have much knowledge about this Systemless method. I flashed a module which promised to show data speed on the status bar. However, as soon as I flashed the module and restarted the device, Google services and a few other Google apps kept force closing. So, I uninstalled the module immediately and now everything is fine. But still, I wanted to confirm that the module doesn't leave any trace behind which may compromise the performance of my device.
[Magisk] Didgeridoohan:
[MENTION=8839962]Rowdyy Ronnie[/MENTION] [MENTION=8714092]DanGLES3[/MENTION] Magisk modules are supposed to be systemless, that's kind of the point. But, it completely depends on the module in question. It's perfectly possible that a module does things that aren't systemless. You'd have to look at the code to know for sure.
[Magisk] complicazio:
[MENTION=4667597]Didgeridoohan[/MENTION]

I did not understand one thing, but a "camera 2api enabler" module that modifies the build.prop as it does to be systemless?

Thanks
[Magisk] fooiskandar:
Why on bpjstku apps force closed with magisk hide on ... Please everyone test it ...
[Magisk] play8oy:
Yes, I have the same problem. Went back to 6.0.0 n flashed magisk zip through TWRP instead.

Oppo Find 7 here running crdroid 4.7 Oreo
[Magisk] android_smater:
For me magisk manager 6.0.1 working perfectly magisk hide crash fix thank you....

Oneplus 6

Oos 9.0

Stock kernel
[Magisk] rub1k:
Is anyone else failing SafetyNet with the new 17.3 version?

I'm on MIUI 10 on a Xiaomi Mix 2 phone and I updated from the 17.2 beta to 17.3 (via TWRP flash) and both check marks are red/failing under SafetyNet.

FWIW, it was passing/both green using 17.2 beta (and the previous MM version, sorry, didn't jot down the version number).
[Magisk] paolocorpo:
Xiaomi Mi A1 stock 8.1.0 October patch Magisk beta 17.3 no issue con Il Safety net check

But I am using a relevant module that I suggest to you:

MagiskHide Props Config

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] ric69:
It's just cts profil failed here on s7edge
[Magisk] android_smater:
Bug report

When ever i reboot mobile safty net pass but after 5 or 10 min saftynet failed

With 17.3

However not with magisk 17.2

Device oneplus-6

Oxygenos 9.0

Android 9.0

---------- Post added at 09:49 PM ---------- Previous post was at 09:49 PM ----------

Bug report

When ever i reboot mobile safty net pass but after 5 or 10 min saftynet failed

With 17.3

However not with magisk 17.2

Device oneplus-6

Oxygenos 9.0

Android 9.0
[Magisk] yldlj:
Use 17.2 you won't have any problems.
[Magisk] Ash7898:
So running the uninstaller from TWRP and then the 17.2 installer gives me same error
[Magisk] Didgeridoohan:
If it actually modifies build.prop, it's not going to be systemless. If it uses Magisk's resetprop tool to change the prop values, either directly in the post-fs-data.sh or service.sh script or with the module's system.prop file, it's systemless.

Like I said, you'd have to look at the code to know for sure. If you familiarise yourself with the Magisk module template and compare that with whatever module you're wondering about you can quite quickly get a feel for what a module does. If the module is using more advanced scripts, you can easily search the web for the commands used to find out what their syntax is and in no time at all you'll be a module expert.

Have fun!
[Magisk] tag68:
To have a protection against remount system rw is what I suggested probably about 2 years ago.

IMHO It would be necessary to replace the mount command (systemless, of course) by some script or executable which checks if the parameters contain system and rw (or similar, may need some brain to get it failsafe), and pass every other call to the original mount command. Maybe a pop-up asking if it should really get mounted is a good idea, notifying the user in this way about the request to break OTA possibility.

Using this method Magisk would make sure that no bad implemented root app modifies system without permission.

I'd like to be protected against any module or app being able to remount system rw. Then one wouldn't have to analyze source which is not always available. If a file explorer has a button for remount rw, that is fine. Some people want to do it. You would be safe if you accidentally press it. It just could be denied, keeping your ability to do OTA update after restoring just boot partition, while keeping all the other root operations possible in the file explorer.
[Magisk] bluenote73:
As has been reported by others in this thread months ago, Magisk only boots back to TWRP when installing 17.3 on the Axon 7 A2017U. 16.7 works. I don't suppose if anyone knows if this is being worked on?
[Magisk] Saabs0448:
Whenever i tried to search the modules in magisk app, it automatically gets crashed. Waiting for the help:)
[Magisk] Didgeridoohan:
Unless you provide the recovery log showing what that error 1 actually means there's very little chance of anyone being able to help at all...

I doubt it, since I don't think I've seen anyone providing a proper bug report that could be used for an attempt to fix anything. There are way too many different devices available for developers to actively support them all. In a community like this, user provided info and data are often essential (as long as it's usable info and data, which unfortunately can be quite rare).

Waiting for the logs.

The source of a Magisk module is always available. It's just to open the zip.
[Magisk] preference:
When I try to download any module I get a process error.
[Magisk] preference:
Fixed my issue by clearing app data
[Magisk] tag68:
In case of Magisk modules that's true, but I also talked about apps. If you want to have the possibility do OTA later, it does not help only preventing all Magisk modules from remounting system r/w. It is enough if if one app does it one time to do the harm.
[Magisk] showlyshah:
Guys any one can explain this.. ?
[Magisk] guest4711:
/vendor is a separate partition on a lot of devices. It's mounted read-only. Magisk allows you to mount userspace into /system so you can change /system systemless, but it does not mount into /vendor...

If you really need to write to /vendor you should remount it r/w.
[Magisk] ILoveLamp2234:
Haven't seen anything for the LGV30 in a minute, probably didn't look hard enough. But I know that we were stuck at v16 for a little while. As of yesterday v17.3 works for the US998D converted from VS996. Magiskhide doesn't crash and everything checks out ?.
[Magisk] Ash7898:
htt"a"ps://drive.google.com/open?id=1BoWHXYrVG5V0stLu7cNUngwFifO_DixG

(remove the "a")

Here's a log
[Magisk] showlyshah:
So does usual mount command with terminal work?
[Magisk] guest4711:
Yes, if you execute it as root (and remount option if needed).
[Magisk] virsys:
Magisk : su: cannot find manager

Good morning,

there is an issue regarding magisk on my device. With oreo everything was working. But after porting Android 9 / LineageOS 16 to my tablet, the magisk daemon is unable to "talk" to Magisk Manager. The installation via recovery is successful every time and with different versions of magisk (16.7, 17.0, 17.1, 17.2, 17.3). The problem is: after bootup there is no magisk manager visible in Android. Not in the launcher, not in Settings>Apps, nowhere. Installing magisk manager as .apk is possible, but it says "magisk not installed". Deleting dalvik && cache didn't help. Uninstalling via the uninstaller and reinstalling didn't help. Completely "nuking" the device (deleting every bit on the flash storage) and retrying multiple times didn't help. I searched the forum for help, but I couldn't find a fix. Could you point me to the right direction?

Device: Galaxy Tab A 9.7 (gt510wifi)

ARM; MSM8196; SELinux permissive; latest repo sync, but the error is persistent since the first Android 9 build 2 weeks ago.

logcat: https://pastebin.com/wfhxpL3a
[Magisk] Ibuprophen:
Does anyone experience the Magisk XposedInstaller reflecting that 301/302 Error for the Repo URL?

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Magisk] sconly:
Doesn't hide root from NatWest app.

Any workaround?

Thanks
[Magisk] philcoo2:
Hi Sconly,

I can use the Nat West app without hiding via Magisk, the Nat West app updated today and still works without having to hide it. I am on Magisk 17.3 android Oreo 8.0, might be worth stopping the Nat West app then clearing data and re-trying.

Phil
[Magisk] metropical:
is there a way to check what version of SuperSU I'm using within Magisk?

In doing some reading here, it appears Magisk can completely replace SuperSU, which I'd like to do.

But I have several apks cleared with SuperSU. How do I go about losing Super SU for Magisk and clearing these apks thru Magisk?

EasyReboot, Greenify, GSam, RCTD, Safe removal.

I also have one Xposed module called Text aid that I use some elements of.

Is this accurate information to remove SuperSu and just use Magisk?

Some tough English there, so I'm a little unsure.
[Magisk] yochananmarqos:
Yep. Choose to permanently uninstall SuperSU via the SuperSU app, flash unsu, flash your stock or custom ROM's boot.img, then Magisk.
[Magisk] metropical:
I assume then:

Boot to recovery, TWRP for me.

Flash SuperSU (it's hidden with Magisk installed. I only know it's there coz I see it in Magisk) .

Boot to Android and uninstall SuperSU.

Back to TWRP and flash unSU.

Reboot Android to check unroot.

Back to TWRP and flash the stock boot.img and Magisk (& Magisk Manger?).

Anything missing or can be skipped or I have wrong?
[Magisk] yochananmarqos:
No, do not flash SuperSU. In the SuperSU app there is an option to permanently uninstall it. Do that then reboot to TWRP. Flash unsu, stock boot.img and Magisk. Then reboot back to Android.
[Magisk] martyfender:
Why would you install SuperSu again?

Usually for me it is sufficient to flash unSu.zip, do not reboot. Immediately flash your stock boot.img, followed by Magisk.zip, all in TWRP, before rebooting.

Maybe to be safe, uninstalling SuperSu, while still in Android may be a good idea, first, but I have not had to do that, but results may vary for different devices and Android versions. I think the Idea is to get rid of all remnants of SuperSu before installing Magisk.
[Magisk] metropical:
doh, I'm reading SuperSU in my head on the phone but it's Superuser in Magisk.

Sorry, boneheaded. I'm set. I need a bourbon.
[Magisk] yochananmarqos:
I just said that. Stop copying me. :silly:

You're telling us this whole time you've had Magisk installed properly? :eek:

Well, I guess you learned something today, then. :highfive:
[Magisk] taiheng:
Happen same for my device.

After several time check, whatever I reboot, it totally can't pass safty net.

Tried uninstall & reinstall magisk, it will safty net pass, but after some period, it will fail saftynet again.

Was Magisk 17.2 no have such issue.

Device Xiaomi Note 3

LOS 15.1

Android 8.0
[Magisk] NYLimited:
The admirable patience of a greenie! Impressive! :svetius: :svetius: :svetius:​
[Magisk] DeeRV:
Device: Samsung S7 Edge

OS: Android 8.0.0

Baseband version: G935FXXU3ERHC

A week ago I got a new stock ROM from Samsung and after flash it to my device and install Magisk 17.1 it becomes unusable because two kind of boot loops,

- Samsung S7 Edge logo, Samsung flashing logo and reboot

- Samsung S7 Edge logo, Samsung flashing logo and after 2 or 3 minutes, Optimizing apps X of X and reboot

As I had a TWRP backup so I have tried to downgrade to the previous ROM and restore my backup but due to some Samsung trick there was no way to downgrade to the previous ROM (Bootloader Device: 3, Binary: 2)

I was just able to boot the device in Download mode and, only a few times, rebooting from Download mode the device booted normally but as soon I powered off there were no way to power on it.

After some days trying several fixes I have managed to fix it only disabling Magisk Hide at Magisk Manager settings.

I guess there is a bug and hope you may fix it in the next update.

Thanks
[Magisk] Dery94:
Hello sir

My device is Samsung Galaxy S8+ with custom rom

I can't open my bank app after i update the bank app

I can't open my bangking app because root detected

I was check my bangking app in magisk hide but still can't opened

I'm using magisk 17.3 with green safety net

Thank you
[Magisk] Dery94:
This an screenshot
[Magisk] doomscooter:
Hahaha itu sudah benar SOP nya.

Thats right that SOP.

EDIT :

Uninstall mandiri online. Reboot. Download mandiri online from Play Store.

Using magisk hide. Reboot and open mandiri online
[Magisk] jenslody:
Try to hide the Manager (from Manager settings), and if that does not work, force-close the app an clear its data. And if that does not work, make sure no folder with magisk in the name exists in internal storage.
[Magisk] Dery94:
Still nothing happen

Its same also with another app with root detection
[Magisk] doomscooter:
Tsel wallet. LoL

U can try uninstall magisk and reinstall again.

Or you can try

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] mido800:
Guys

I have Lenovo A5000 Android 5.0

Magisk manager 6.0.0 was working fine

The i got an update to 6.0.1 after installing it just crashes

Uninstalled it and downloaded it from the website installed it again same thing

What can i do
[Magisk] metropical:
don't sit in front of the screen too long or too late .....
[Magisk] tinhsoftware:
Hello, my pixel 2 currently on 8.1 and rooted with magisk. I want to update to 9.0 this weekend. I wonder if there any problem that i should know to root 9.0 with magisk. Thankz.
[Magisk] gvsukids:
On Pixel 3, while uninstalling root it downloaded the zip, rebooted and now has the Android with red triangle and "no command"
[Magisk] nicesoni_ash:
I am using latest stable build of magisk on my oneplus 2, 8.0 android version. Magisk crashes if I try to check its log.

Here is the log attached.

https://pastehere.xyz/58582/

Edit:

Looks like the issue was adding a new module but not rebooting after that, after reboot the issue is gone..
[Magisk] vandyman:
Install your backup using Adb.
[Magisk] gvsukids:
What backup? Factory image?
[Magisk] vandyman:
You did not make a backup of your device before.? Always make a backup before making major system changes.

I would start over and install the factory image via flash-all.

Or install TWRP and install a kernel.

Not saying the kernel will work for you are not. For me on my Pixel 2, a kernel install will get me out of a boot loop.

---------- Post added at 04:54 PM ---------- Previous post was at 04:52 PM ----------

You can also just install the boot.img.
[Magisk] gvsukids:
The modified_boot.img in Pixel 3 removed chrome browser making it hard to reset phone
[Magisk] Homeboy76:
What/Where is twrp for Pixel3?
[Magisk] yochananmarqos:
You can always backup via ADB.
[Magisk] vandyman:
I do not know anything about the Pixel 3, I am just throwing some ideas out there.

The best thing to do if are having issues is to go to the Pixel 3 thread.

You will be able learn more about the Pixel 3 there.

As far as getting stuck on the recovery or bootloader screens. You can extract the boot.img from the factory Google image

and use fastboot.

Fastboot boot boot.img

---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------

Sorry for format, I am using Tapatalk... [emoji53]
[Magisk] mariosaraylian:
Magisk 17.3 & Magisk Manager 6.0.1

Hey All:

Pardon the stupid question, but......will they release an update to the Magisk Manager itself so that it will show the current installed proper release version of 17.3 and also continue to offer the updates to the current versions?

I attached a screenshot of how it looks on my HTC 10 on Android 7.0/Viper10 5.11.0 ROM, I'm using the most current version of the Magisk Manager (Ver. 6.0.1 - 151).

I know there was a "bug" with v17.2 posted:

"2018.9.21 Magisk v17.2 -- Unexpected early release due to a bug in Magisk Manager that never surfaced until some online repo triggered it LOL. But well this means you get several sweet features early too"

I assume what I am talking about is the "bug" ?

Thanks!
[Magisk] martyfender:
It looks like you need to change the update channel in the Magisk Manager settings to the beta channel.

V17.3 is the current beta version of Magisk, as far as I can tell from this page:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

---------- Post added at 07:22 PM ---------- Previous post was at 07:09 PM ----------

I did not copy you. I just related my own experience in doing it in the past and it had nothing to do with you.
[Magisk] yochananmarqos:
I was kidding, hence the emoji. :p
[Magisk] Mrnicgeuy633:
Not sure where to ask this. But having unlocked my bootloader, rooting, and installing magisk 17.3 on my pixel 3 everything worked fine, until I tried to hide magisk. After I restarted, I had two magisk apps. One that did nothing but freeze and force close, and the other that forced me to reinstall magisk. I know it's beta, just wondering if anyone else had a problem with 17.3 and hiding magisk
[Magisk] brian 11:
I've noticed Other people failing safety net newest Beta release. Same here, but Easily easily fixed by going back to 17.2. But I've noticed that Root Checker says that I fail safety net. Google play says device certified and I'm pretty sure google pay still works ( it does). I'm running lineage 14.1 and this phone doesn't have a working SIM card, I don't know why that would make a difference, but I seem to remember root checker passing safety net when this phone was active. If anyone has any ideas I'd appreciate it just curious thanks
[Magisk] brian 11:
Are you talking about apps that need root or magisk modules? And you and you can just pick the apps that you want root to be hidden from. Are you losing root?
[Magisk] Mrnicgeuy633:
No mean the actual magisk manager. I test safety net and it passes. Then I go into the settings, and hit the hide magisk manager. It says it's repacking. Once it's done, if I restart the phone if I open The app draw in Android, it shows two separate magisk manager
[Magisk] allanjohnkemp:
Hi All,

Have an oddball inquiry, ive just upgraded to 9.0 on my mate 10 pro and twrp is unable to flash the magisk zip. I thought i would just patch the boot image in manager although the rom has no ramdisk.img to patch. Any ideas??
[Magisk] Didgeridoohan:
The Magisk Manager shows you that you pass SafteyNet, so things are working as they should. That other app isn't updated to work with SafetyNet's new APIs. Notice the reponse "N/A" to both CTS and Basic integrity; it can't do the check so the app reporting a failed result is just lazy programming on the developer's part.

You failing SafetyNet on v17.3 is, with all possible likelyhood, just a fluke. Note that you'll not get any support if not using the latest verions. If it's not a fluke, the proper way to report it is with logs.
[Magisk] brian 11:
I think that's just the app renaming itself. One of the two apps shortcuts will say app not installed if you try to open it. But I never have to use that function, I just choose my bank app in the magisk hide section and it automatically hides root from Google pay and play services. I think it sounds like yours is working right.
[Magisk] NOMIOMI:
flash everything correctly after reboot the Magisk is not installed .then i download zip only through magisk manager and flash but still magisk is not installed

i have smasung note 8 with custom recovery
[Magisk] kakabobo:
cannot use magisk hide when using f2fs on data slice ?

once enabled and root is lost. restore package and root is back on.
[Magisk] FullWipe:
Same problem.

My data partition is f2fs formatted and when Hide magisk manager is enabled i lose the root.

Unfortunately i cannot use the banking app w/o losing the root :(

I hope in a fix [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Mrnicgeuy633:
Ok that makes some sense. But neither apps are useable at that point after hiding. They will both ask "upgrade to full Magisk manager to finish the set up. Download and install? When I do that, it downloads magiskmanager-v6.0.1(151).app and install again. Is that the way hiding works? Do you have install again everytime for it to be useable after hiding?
[Magisk] wanafiff:
Pixel Experience 9.0

Sorry Im still new..can I flash with this custom rom? Using on Samsung Galaxy Note 3..before this I tried to flash SuperSu but then the phone stuck on loading screen forever and only after i have dirty flash this rom again to get in the phone :confused:
[Magisk] Wolfcity:
You can try this f2f2 loopback bug module:

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875/post71554247

I'm using an older build of it and it's working well.
[Magisk] horlamedyy:
Pls i have been able to removed supersu on my htc one e8 but i cant seem to installed magisk on my phone.its said failed
[Magisk] martyfender:
Your boot.img was patched by SuperSu. You need to flash your stock boot.img before you can install Magisk, just like the message states.

An alternative that may work is to flash UnSu.zip in a custom recovery followed by the Magisk.zip, but that may be dependent on whether the stock boot.img was properly backed up by SuperSU. Normally it is backed up.
[Magisk] chickygamon:
Anyone use nexi app? It's not working here...it's hide but it closes everytime with "security problem" ....
[Magisk] casouzaj:
Do you mean Nexi Pay? Well, I don't use it, but I have installed it just to try to troubleshoot your problem, but just by adding it to Magisk hide, it is started correctly. Might be because I'm running the latest Canary build?