yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
A couple of questions:

Are you really using ADB sideload to flash the zip? Why? Do as suggested above by [MENTION=8126387]martyfender[/MENTION] instead.

And I don't see anything about the Magisk image on the log you provided. Care to clarify?

WE KNOW!

Sorry that you're device isn't working, but there's really no need to go spamming the same question over and over and over again in every single thread you can think of.

Answered in the relevant thread...

Logs are always a good thing to provide when asking for help...

Also, have you tried letting the Manager patch your boot image instead of flashing the zip directly (check the installation instructions for details).

And if that doesn't work either, don't forget the logs...
[Magisk] Artim_96:
Just go to your phones forum, there is not likely a dev that supports it unofficially
[Magisk] lvbaal:
Obviously I zipped and uploaded the wrong last_log. I attach the relevant log herewith and refer to line 712 and further regarding the Magisk img not found. Also I shall uninstall Magisk once more and re-install using TWRP Install in stead of Advanced ADB Sideload...
[Magisk] MysteryIII:
There is no dedicated forum and only a few posts like this.

Just searched for it, but basically this phone isn't supported on XDA and I also didn't find anything on google beside old 4PDA version. It seems like this phone rarely got in the hands of developers at all.
[Magisk] zelendel:
Well I hate to say it but that's due to developers always getting flagship only devices.
[Magisk] gothicVI:
Log?

Log?

Try patching your image using the manager and flash it via fastboot.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] IBNobody:
[MENTION=4487388]jcmm11[/MENTION]

Well... That was disappointing... Both the working ROM and the Stock have the same boot.img (pre-Magisk mods, of course).

So... To summarize where I am now...

I was on a stock-ish 6.0.1 custom ROM for my Galaxy Note 4 (910P) based off firmware QI5. That ROM had some serious issues with actual phone functionality, but it had a working MagiskHide and passed SafetyNet.

I decided to ODIN full stock QI5 and TWRP, and then install Magisk. Magisk itself worked, but my checkmarks in MagiskHide would not save. I verified that I could not start MagiskHide from the command line (magiskhide --enable). When I tried, I got a message saying that "Logd is not running, cannot run logcat".

Both the ROM and Stock QI5 have the same boot.img and therefore would have the same ramdisk and kernel.

What else should I try?
[Magisk] lvbaal:
I don't really know if this method is an approved method, it's just the only way I have been doing it until now:) I will follow the steps you describe above:

First I have un-installed Magisk once more through Magisk manager>Uninstall>Complete uninstall.

After that, TWRP Install to reflash the stock boot image. Here I understand that, because of Oreo having split the boot partion into ramdisk and kernel, I have to flash RAMDISK.img instead of boot.img. So I extracted RAMDISK.img according to this guide and placed it in /cache on the device (for which I re-installed Magisk temporarily to be able to access /cache and uninstalled Magisk again, this time flashing Magisk-uninstaller-20180222.zip in TWRP Install which gives ERROR: 1 - so then I unistall Magisk once more via Magisk manager>Uninstall>Complete uninstall).

After that I go ahead to flash the stock boot image:

- boot TWRP

- hit Install

- navigate to /cache

- hit Install Image and select RAMDISK.img

At this point i run into trouble(?), because TWRP only lets me flash the RAMDISK.img either in partition named ¨System Image¨ or ¨Vendor Image¨ where Ramdisk partiton is not an option which is presented. Intuitively I assume that RAMDISK.img should NOT be flashed to neither system nor vendor(?), so I go ahead and flash RAMDISK.img using ¨fastboot flash ramdisk RAMDISK.img¨ after rebooting to bootloader (FASTBOOT&RESCUE MODE):

PS C:\adb2> fastboot flash ramdisk RAMDISK.img

target reported max download size of 471859200 bytes

sending 'ramdisk' (16384 KB)...

OKAY [ 0.383s]

writing 'ramdisk'...

OKAY [ 0.157s]

finished. total time: 0.549s

PS C:\adb2>

and reboot to system which goes fine.

Then I reboot to TWRP to install Magisk through TWRP>Install

So now i can check if the original issue of an invalid Magisk installation (¨e2fsck: No such file or directory¨while trying to open /data/adb/magisk.img¨ in TWRP's last_log) is gone now. To that end I installed systemless_xposed-uninstaller-signed.zip once more through TWRP>Install. This gives error: ¨Updater process ended with ERROR: 1¨. The same error occurs when I install Mount-Magisk.zip. I attach TWRP's last_log once more, where e2fsck error shows up again (or still).

Both [MENTION=8126387]martyfender[/MENTION], [MENTION=4487388]jcmm11[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION] and [Mention=8570610]MCMotherEffin' [/Mention] have pointed me to an improper Magisk installation earlier. Are you guys willing to look into this once more maybe?
[Magisk] guest4711:
Open Magisk Manager -- Superuser and delete the entry (so you will be ask again) or switch it to enable.
[Magisk] nfs32100:
Hy

Is someone who heard about MatrixHCE ?

My Bank(BT PAY from app store) use this MatrixHCE APi.

I can't hide custom rom with magisk,this app works only in stock but after i install Magisk in stock and use Magisk Hide this app tell me "You're phone is rooted".

Only after reflash stock rom app still work.

P.S How Bypass MatrixHCE ?

App : Link https://play.google.com/store/apps/details?id=ro.btrl.pay&hl=ro
[Magisk] Didgeridoohan:
But the ROM have enabled logd, right? So, as we've already established, you'll need to figure out how to enable logging. Have you asked in your device's forum? That's usually the best place for these kind of issues.

Yes, it does seem like you're Magisk installation is broken. Have you asked in your device's forum? That's usually the best place for these kind of issues.

Just to make sure; have you also hidden (repackaged) the Magisk Manager?

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] nfs32100:
Just to make sure; have you also hidden (repackaged) the Magisk Manager?

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot[/QUOTE]

Yes , i hide Magisk Manager.

*Delete Magisk

*Use Magisk unistaller

-Nothing-
[Magisk] Jaymin.0.1910:
Seems like /data/adb is not accessible for your device, can you try various types of file accessibility checks for /data/adb on your own, and report back
[Magisk] jenslody:
Did you check if it is really hidden (random name in the about-tab) ?
[Magisk] lvbaal:
When booted to system, the root file explorer can read /data/adb/magisk.img. When booted to TWRP, the TWRP file manager can read /data/adb but the file names in there are garbled becasue of encryption. What more accessebility tests could I do?
[Magisk] rignfool:
The problem is that if xbin does not already exist... Your BusyBox is loaded in /magisk/mod/system/xbin... And it's looking for it in /system/xbin/...

Funny enough... It makes all the symlinks and applets and such... It just doesn't get mounted properly...

I do not have your module loaded currently... But I can reload it and get you whatever information you need...

---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------

It has no trouble systemizing apps which requires a created directory in system... And I have no trouble replacing fonts...

I can install any other module you want me to check... But no audio mods... They all seem to break everything for me... And without TWRP on device... It's a headache
[Magisk] Didgeridoohan:
Sounds like it could be related to the issue where some devices experience bootloops when Magisk mounts new files and folders to the root of /system.

We never did figure that one out...

A magisk_debug.log when [MENTION=4544860]osm0sis[/MENTION] busybox is installed would be interesting to see.

---------- Post added at 18:53 ---------- Previous post was at 18:50 ----------

So, TWRP can't decrypt /data... That can explain why you can't install modules from recovery. But, have you now tried installing modules from the Manager?
[Magisk] lvbaal:
Unlike before, when I had installed Magisk through TWRP>Advanced>Adb Sideload and could install modules from the Manager, now, when Magisk has been installed through TWRP>Install, I cannot install a module. Here's the install_log_20180317_204600.log:

- Copying zip to temp directory

- Installing Greenify4Magisk-v3.9.7.zip

- Mounting /system, /vendor

update-binary[73]: unzip: not found

! Unable to extract zip file!

Failed!

! Installation failed

Edit: surely this was caused by Busybox not being installed at that time. Now, it is able to install a module
[Magisk] osm0sis:
[MENTION=3290808]rignfool[/MENTION]

I want the outputs without the module loaded, i.e. a working system. I want to know if the path is still normal despite the OEM removing xbin.

If they also altered the path, well then that's one more issue if Magisk is ever able to add things to /system.
[Magisk] Abhishek17599:
Magisk was able to pass safetynet itially on Linage os 14.1 on my device
[Magisk] d3vyarth:
Here it is....
[Magisk] Didgeridoohan:
So now everything is working as it should? A broken unzip is usually helped by installing busybox. :good:

Have you tried turning it off and on again?

Also:

https://www.didgeridoohan.com/magisk

Hm... Have you tried letting the Manager patch your boot image, and then flash that manually (can be done with TWRP)? Check the release thread for instructions.
[Magisk] IBNobody:
I did, and I figured out a solution, but I don't understand why it works.

The custom ROM used Magisk v14 and automatically installed it as part of the TWRP zip install. At no point did the custom ROM boot into system.

I was able to duplicate this with ODIN and stock ROM. As long as I kept the phone from booting to system during the ODIN-TWRP-Magisk install AND as long as I kept to Magisk v14, I could get Magiskhide to work.

Running "ps | grep logd" didn't show me that logd was running, but I had not trouble enabling/disabling magiskhide.

Trying the same thing with v16 did not work. Also replacing the Magisk v14 with v16 in the custom ROM did not work either. Finally, attempting to use TWRP to install another version of Magisk did not work. All yielded the same broken magiskhide.

So... Does this mean that I am going to be stuck on v14 forever?
[Magisk] Sagar Sharma01:
I installed magisk v15.3 using patched boot image method which created boot img (4.43mb) and working perfectly, But when i tried the same wih v16.0 it gives me boot img of 6 kb and with v16.2 beta gives me a boot img of 4.43 mb.

So, when i flash v16.0 my device get stuck in bootloops.

I attached log of patching boot image and a screenshot showing boot images it created.
[Magisk] jenslody:
Patching bootomage with 16.0 is known to be broken on some devices, just use the newest beta instead.
[Magisk] Sagar Sharma01:
Beta releases are built with the debug flag enabled, it will do a lot of verbose logging, how to disable it
[Magisk] Jaymin.0.1910:
Flash a different TWRP with encryption issue fixed:)
[Magisk] problemathic:
is there a way to patched boot.img offine? as long as we have the boot.img and required magisk.zip file?
[Magisk] Sagar Sharma01:
Is there any way to patch boot.img with older versions of magisk like v15.3 using Magisk manager.
[Magisk] cristianodk:
Pokemon Go, detects the device as root with the latest version 5.6.3

plz fix, game always crash
[Magisk] Ja_som:
It is not a Magisk issue.

https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
[Magisk] Artim_96:
This is not a pogo forum. There is s seperate Treff thread for that, this does not belong here.

If the dev finds any time to improve the workarounds he might will on done point. But he has more useful stuff to do and he stated quite clearly back when pogo started to detect root that he has very little interest in it and won't do any support in any such app. If an update fixes something it can be a side product that those apps will start to work too again
[Magisk] Didgeridoohan:
I think we're on to something here... Could it be that Samsung doesn't use logd? Newer releases of Magisk checks for logd and doesn't start MagiskHide if it isn't found running, so that would explain why an older release works.

[MENTION=8340552]jenslody[/MENTION] Could you help me out here. You're much more knowledgeable about Samsung.

If you don't want to have verbose logging enabled, wait for a stable release.

If you create your own custom update channel for a copy of v15.3 that you've uploaded somewhere, yes.

No.
[Magisk] cristianodk:
the magisk hide, does not work for some applications

better so?

the same application of magisk is damaged, from version 5.6.2 full crash,

with the current version follows the same error

motorola z play android 6.0.1
[Magisk] rignfool:
Interesting...

/sbin/su:/su/bin:/su/xbin:/system/bin:/system/xbin

Even though I don't have an xbin directory...
[Magisk] osm0sis:
Apparently you're also using SuperSU, or didn't clean up properly when switching? I'd like to know what it is with a Magisk install over a clean boot.img if possible.
[Magisk] rignfool:
No sir...

Haven't used SuperSU since magisk came out...

I assume magisk put those in... With redirects for poorly coded apps

The install is clean... 2 days old... But I do have elementalx flashed over top...
[Magisk] IBNobody:
I can confirm that it is the logd check added in that is the issue. v15.3 magiskhide works. v15.4 magiskhide does not. The logd check was added in v15.4.
[Magisk] YoshiFan501:
tried many times. i have no clue whats causing the problem
[Magisk] Hemuli:
Magisk Manager 5.6.3 (and older).

Rom: AIM OS v2.5 for Lenovo A7600-F [MT6582][Port]

Channel: Beta (and stable)

Clicking Update Magisk > Install > Direct Install (Recommended). Menu closes and I'm back to Magisk Manager "home" and nothing happens. Logs from me only pressing Direct Install (Recommended).
[Magisk] jcmm11:
That looks like a termux path after you've entered root mode.

Termux sets it's own environment. I don't think you can directly access the parent environment.

Try installing https://play.google.com/store/apps/details?id=jackpal.androidterm and use that to get the path (both before and after gaining root. They'll probably be the same)
[Magisk] GammelBS:
This path is set by termux, see:

/data/data/com.termux/files/usr/bin/su

edit: ninja.d
[Magisk] rignfool:
[MENTION=4544860]osm0sis[/MENTION]

Ok... It was a Termux issue...

Now my PATH is

/sbin;/system/bin;vendor/bin
[Magisk] osm0sis:
Nope.. here's my output from stock OOS OB4 with Magisk clean installed:

OnePlus5T:/ $ echo $PATH
/sbin:/system/bin:/system/xbin:/vendor/bin
OnePlus5T:/ $ su
OnePlus5T:/ # echo $PATH
/sbin:/system/bin:/system/xbin:/vendor/bin
OnePlus5T:/ #

You've got remnants of SuperSU somehow.. I'd recommend flashing the boot.img from your ROM again, then Magisk to make sure it's totally clean.

Edit: Whoops, nevermind, missed these replies with the forum downtime.
[Magisk] GammelBS:
Taimen stock rom has no xbin folder also, but it doesn't bootloop if module with xbin installed.

without busybox:

taimen:/ $ echo $PATH
/sbin:/system/bin:/vendor/bin
taimen:/ $ su
taimen:/ # echo $PATH
/sbin:/system/bin:/vendor/bin

with busybox:

taimen:/ $ echo $PATH
/sbin:/system/bin:/system/xbin:/vendor/bin
taimen:/ $ su
taimen:/ # echo $PATH
/sbin:/system/bin:/system/xbin:/vendor/bin

No idea why.

My issue: I can install only one module in xbin:
[Magisk] osm0sis:
Interesting. I wonder if there's a clue here that could get adding xbin (and other /system root things) working everywhere. Also interesting that the path changes once xbin is created. I wonder where that's coming from now.. used to be in init.environ.rc.
[Magisk] ultradj83:
Failed upgrade

Dears,

I have a failure updating v14 to v16 on a Samsung Galaxy J5.

Here's screenshot and log.

Any suggestions?

Thanks a lot.
[Magisk] Didgeridoohan:
First uninstall v14, then install v16.
[Magisk] siealex:
Your system download manager does not start, look for problems there. When you press "direct install", first the download link is sent to the download manager, MM waits for full download and then installs the zip file.
[Magisk] ultradj83:
Are you sure this can simply by done by the manager?

Or do I have to flash by recovery?

Tks.
[Magisk] Didgeridoohan:
After uninstalling v14, you can let the Manager patch your boot image and then flash that manually. Otherwise you'll have to reinstall by flashing through recovery.
[Magisk] ultradj83:
Sorry for bothering, but just to understand, how can the manager patch the boot image if v14 after v14 removal?

Won't it need root permissions?

Tks one more time.
[Magisk] Didgeridoohan:
You'll need to extract the boot image from your ROM/factory image/firmware package (whatever's applicable) and place it on your internal storage. After that you can flash it manually with fastboot/Odin or with a custom recovery. No root required...

Check out the installation instructions.
[Magisk] Hemuli:
Thanks. Weird then that pressing "Download Zip Only" works as it should. But it probably has nothing to do with MM then.
[Magisk] siealex:
It's very strange. If it downloads the zip file, it must download in all modes.
[Magisk] jenslody:
As workaround you can use the downloaded zip and install it from the modules-tab: press "+" and chose the Magisk-zip, it should work the same as the direct-install.

By the way: do you have any Magisk modules installed ?
[Magisk] IBNobody:
I may be a bit late to ask this, but ever since v15.4, Magiskhide had the hard requirement of having logd (init.svc.logd?) started. (This was the code that does it.) In my situation (stock ROM Galaxy Note 4), logd is not enabled, but logcat works fine. This means that v15.3 was the last build that works with my phone.

Would it be possible to skip the check for logd? Or will v15.3 be the version I am going to be stuck at?
[Magisk] buran666:
Problem instaling using TWRP

The process goes ok until the extraction of boot.img has to happen. It fails. The same happens with SU so I guess it i a boot.img problem. The platform is RK3126 Android 6.1. Magisk manager also fails in ediing the boot.img I have extracted using android tools. Ides? (log attached)

The boot.img - ttp://dox.bg/files/dw?a=deb8386218

The Log from TWRP, includes unsuccesful try to setup SU too - ttp://dox.bg/files/dw?a=e75fb694be
[Magisk] jenslody:
Does logd run at all, or does the rom use a completely different log-mechanism ?

I do not have stock-rom on my J5 currently, but as far as I remember v16 worked.

Can you check for a log-process with "ps" from a terminal or "adb shell" ?
[Magisk] IBNobody:
When I looked into it, the stock init.rc had all "start logd" lines commented out, but I noticed that 15.3 was still able to hide Magisk and su.

I used Root Checker and saw that it could detect/not-detect the presence of su depending on the hide setting of Root Checker in Magiskhide. Also, SafetyNet passes. So... I think v16 would work for me if the logd check wasn't a hard-kill for magiskhide.

Here's my ps.

shell@trltespr:/ $ ps|grep log
root 370 366 3068 1164 poll_sched 00000000 S logcat
root 1565 2 0 0 log_worker 00000000 S mc_log
radio 11649 1 3600 824 hrtimer_na 00000000 S /system/bin/diag_uart_log
shell@trltespr:/ $
[Magisk] Hemuli:
I have ViPER4Android FX for Magisk v15 module.

Installing the zip from modules works. Except that it doesn't (Unable to detect boot image), but I can install Magisk by patching boot image so it's not a huge issue for me.

Hmm... I can't see fstab in /etc folder, but I found fstab.mt6582 straight on root.

E: Theres no /boot mount point in my fstab. I assume this explains the error while installing Magisk with zip.

E2: I get it to the point where it says "Found boot/ramdisk image". Couple lines later it says it can't locate class magisk/utils/BootSigner and throws a couple exceptions. What does this mean as I'm able to patch the original image with manager?
[Magisk] MrElectrifyer:
Hey guys,

Few weeks ago, I finally got the systemless Xposed module for Magisk working on my 256GB Exynos Note 8 via a custom ROM. I wanted this as a means of quickly disabling the Xposed framework on my device whenever I wanted to make use of my mobile payment app, which requires passing Safety Net and having ADB disabled, and re-enabling the Xposed framework once done. Now, I'm looking to simplify the process with a Bixby quick command.

Bixby obviously isn't going to support tasks in Magisk, nor can it toggle ADB. Instead, to do this, I'm looking to use a Tasker profile to turn off the Xposed systemless module, turn off ADB in developer options, and reboot my device. All of which I'll export to a stand-alone app via Tasker App Factory, then I can call it with a simple Bixby quick command like "I want to pay with my phone".

Only problem is, I'm not sure how to turn off Magisk modules via Tasker. Any brilliant mind out there have a suggestion for accomplishing this? Thanks in advance.
[Magisk] jenslody:
Add an empty file named 'disable' (without the quotes) in '/sbin/.core/img/xposed_??' (and reboot).

To reenable xposed, just remove it and reboot.
[Magisk] MrElectrifyer:
Thanks for the response. So I attempted this in Tasker by creating a task with the following action (see first 2 images, not sure how to post them inline with response in XDA Labs app).

However, when I attempt running it by pressimg the Play Button in Tasker, I just get this in Tasker and the file isn't created (see 3rd image).

What am I doing wrong? Please and thank you.
[Magisk] Didgeridoohan:
I believe that action needs an already existing file. You also need to run the command as root. Try using the "Run Shell" action instead, and add this:

su -c touch /sbin/.core/img/xposed_25/disable

And when you want to remove it:

su -c rm -f /sbin/.core/img/xposed_25/disable

The reason I'm using "su -c" rather than the built-in root check is that Tasker won't recognise root of you hide the Manager, but "su -c" still works.
[Magisk] patrickdass:
Ever got this to work?
[Magisk] MrElectrifyer:
Awesome! That worked in disabling the Magisk Xposed module :D Thank you very much!!

Did you happen to also know of the codes for disabling/enabling the ADB toggle under Developer options? Right now, I'm trying to do it via AutoInput, but that has lots of room for errors.
[Magisk] Jaymin.0.1910:
Neither do I, it is completely weird
[Magisk] Didgeridoohan:
That'll soon be a lot easier with Tasker. Writing to Settings.Secure or Settings.Global is already in the new Tasker beta.

Settings.Global.putInt(getContentResolver(),Settings.Global.ADB_ENABLED, 0); // 0 to disable, 1 to enable

---------- Post added at 08:26 ---------- Previous post was at 08:20 ----------

And you've tried reinstalling Magisk? Also, I don't think I've seen you provide a Magisk log.
[Magisk] Jaymin.0.1910:
You need to reboot afterwards

You have a non-standard boot image, send it to Magisk devs for analyzing

You can compile your unofficial build with the logd block removed, it is really easy
[Magisk] MrElectrifyer:
Thanks again for your response. I just pasted that code in Run Shell and got thollowing error regardless if root was enabled/disabled (see attached image). I'm guessing that's not where it's to be used.

I have AutoTools installed and I've given it the Write Secure Settings via ADB on my PC. So, would I be able to use it with your code? If so, how exactly?
[Magisk] reference2myself:
Magisk manager 5.6.3 doesn't open for me, I just get a message that says "magisk manager has stopped". If I revert back to 5.6.2 it works fine. Nexus 6p, latest ABC rom, magisk v 16.

Edit: 5.6.3 works if I uninstall first. Upgrading from 5.6.2 to 5.6.3 breaks it though.
[Magisk] Didgeridoohan:
If you re-read the article I linked, you'll see that you need to use Java until it's been developed further. I can not help with that...

Logs or it didn't happen™...
[Magisk] Quinny899:
The equivalent of that option in shell is

settings put global adb_enabled 0

Replace 0 with 1 for enabled obviously. On newer android versions this doesn't always work outside of ADB shell though, even with su permissions.