yashsingh1/xdaforums huggingface dataset:
[Magisk] Vobi1024:
Strange... For me... Could You please check, Your PATH variable? Does it have xbin in it? Thank You!
[Magisk] martyfender:
I do have /system/xbin, with busybox links and files in it.
[Magisk] Vobi1024:
Ookay, then why is Your busybox hidden, and why my phone tells me I have one, when that is not true?
[Magisk] edzamber:
Hi,

Does someone know how to flash a file into /sbin/.core/img/.core/post-fs-data.d from recovery ?

I tried with Package_extract_dir command, even with sh script touch command to create a file in this folder but it don't working...

mount -t rootfs -o remount,rw rootfs
mount -o remount,rw /

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

touch 00selinux

echo "setenforce 0" >> /00selinux
echo "SELINUX=permissive" >> 00selinux

Log :

cd: line 13: can't cd to /sbin/.core/img/.core/post-fs-data.d

about to run program [/sbin/sleep] with 2 args

about to run program [/sbin/busybox] with 3 args

about to run program [/sbin/sleep] with 2 ar
[Magisk] Killua96:
System/xbin also apps that check for root work (apart the ones that check for unlocked bootloader
[Magisk] Vobi1024:
I see. Any idea why my phone thinks it has busybox?
[Magisk] Killua96:
Dunno, I'm in a case similar to yours, FGO detects root but Magisk is hiding everything and don't know what it could be...
[Magisk] jenslody:
If you try it from TWRP you have to mount /data/adb/magisk.img somewhere and cd into it.

If you are in android it should work with a root-explorer or from a terminal-emulator (as root).

And don't forget to make the script executable.
[Magisk] edzamber:
On android i can add it by root explorer, no problem.

Problem is with twrp recovery.

I tried to do like this

mount -t rootfs -o remount,rw rootfs
mount -o remount,rw /
mkdir /mktmp
mount -o loop /data/adb/magisk.img /mktmp
cd /mktmp
mkdir /.core
mkdir /post-fs-data.d
touch 00selinux
umount /mktmp

It create file 00selinux into /sbin/.core/img but not into /sbin/.core/img/.core/post-fs-data.d
[Magisk] jenslody:
If you mount magisk.img the internal structure should be there, .core and subfolders and of course the module-folders (if any).

Otherwise something went wrong. Be aware that .core is a hidden-folder and might not be shown with default settings or from terminal.

Edit:

and you might need to mount /system before all commands work.
[Magisk] Didgeridoohan:
You're forgetting something vital... Making the dir in the right place and moving to it before creating the file. Try:

cd /mktmp
mkdir -p /.core/post-fs-data.d
cd /.core/post-fs-data.d
touch 00selinux
[Magisk] edzamber:
Hi bro

No Luck as well...

My code :

#!/sbin/sh

mount -t rootfs -o remount,rw rootfs
mount -o remount,rw /

mkdir /mktmp
mount -o loop /data/adb/magisk.img /mktmp
cd /mktmp

mkdir -p /.core/post-fs-data.d
cd /.core/post-fs-data.d
touch 00selinux
echo "setenforce 0" >> 00selinux
echo "SELINUX=permissive" >> 00selinux

Log :

I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change

about to run program [/sbin/sleep] with 2 args

about to run program [/sbin/busybox] with 3 args
[Magisk] Vobi1024:
Follow-up:

solved by installing busybox from app then uninstalling it from app.

Now neither busyboy checker nor rootbeer thinks I have busybox installed.

So I guess there is another variable/setting that have been removed by the uninstall process.

Thanks all! :)
[Magisk] paarnoutse:
Great that BlackBerry Work doesn't detect root anymore after the actions you performed.

However, at my device I haven't hided Magisk Manager yet (so it still has his standard package name), but nevertheless BB Work doesn't detect root. This even after upgrading BB Work yesterday to its latest version 2.14.1.1089.

Therefore I guess that it's running OK now at your device as a direct or indirect consequence or additional action during the reinstall of Magisk + Magisk Manager (eg. Upgrade Magisk? Clear dalvik/cache? Clear BB Work data/cache?), and not (only) just because Magisk Manager is hided now.

Because it's running OK now at your device, the goal is reached. However, to make clear whether BB Work yes or no really requires hiding Magisk Manager, it would be interesting to check what happens when Magisk Manager is reverted to its original package name. When this would cause detecting root again by BB Work, then I don't understand why it doesn't at my device :confused:
[Magisk] spartan268:
Hi All,

Having a strange issue with Magisk.

I performed the upgrade Today coming from Android Oreo OOS to pie.

I followed the instructions of flashing the full OTA of the pie update. And then the blusparks TWRP. I rebooted into recovery and then flashed Magisk 17.1 as per the guide.

Booting back into the OS I can see that Magisk Manager is missing and my rooted apps are unable to get root either. Also when I try to goto the themes/display section inside settings; the settings app crashes on me.

I attempted to reinstall Magisk but this did not work. I only noticed that when I was running the uninstaller for Magisk it did detect my boot image is Magisk rooted despite the OS not reflecting this.

I tried both Magisk 17.1 and 17.2 (of course uninstalling before hand). I also tried to install the Magisk manager APK alone and it would simply say "app not installed" on every attempt.

Any help would be appreciated. I'm trying to avoid wiping the phone completely but I may have to do that come weekend time if this persists.

EDIT: OnePlus6
[Magisk] A.lemane:
What's ur phone (provide more info please)
[Magisk] Killua96:
OP6? Try to dirty flash the pie rom, right after the blue spark twrp, reboot to recovery and flash magisk 17.2. Obviously before this run the last magisk Uninstaller
[Magisk] DarkHeart Z:
Android Settings force closes when enter to the link of magisk manager after updating to 6.0.0 . Don't know what happened . Rom : RRN-5.8.5 . Can you take a look at it ? [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] spartan268:
Forgot to specify it's a OnePlus6.

I ran through the above steps (Ran Magisk uninstaller from blusparks TWRP -> Reboot to recovery -> Dirty flash pie and then blusparks TWRP > Reboot to recovery -> Install 17.2)

No dice :( Still the same symptoms as before with no Magisk Manager and try to install APK does not work either.
[Magisk] grumphy:
try this:

https://xdaforums.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
[Magisk] jcmm11:
I have xbin (created by me), xbin in path, BusyBox by osm0sis installed.

When I install, and hide, rootbeer it doesn't see BusyBox and tells me I'm not rooted.
[Magisk] A.lemane:
If nothing else works try this (backup ur contacts & accounts)

Look for /data/system

In twrp file manager rename that folder to "system2"

Restart ur device , it should start as new system settings everything else should be there (I don't know about pie but that's the case with other Android's)

Anyway in any case if anything goes wrong u should be able to restore the old folder , if goes well u should delete the old folder
[Magisk] yuri-rus:
Xiaomi Redmi 4x MIUI 9.6.4.0 global. After installing Stable Magisk v17.1 I get boot loop. With Magisk 16.0, everything works.
[Magisk] Killua96:
So, here i am again, [MENTION=4667597]Didgeridoohan[/MENTION] or [MENTION=4470081]topjohnwu[/MENTION] is there any method or logs to find why a specific app detects Magisk? To sum up what i've tried:

- Safetynet passes

- Hidden the app in Magisk Hide

- Hidden MM

- Downloaded your module to check if some values were unsafe, nope

- Doing a clean install of both Magisk and ROM

- Trying different custom kernel

- Deleted root related apps and files

And... Nothing, now i'm pretty sure it has something to do with Magisk since uninstalling it is enough to get the app (yeah, the usual FGO) to work, last time Didgeridoohan said me that full obfuscation is not 100% present, and it will in the stable release, and he was right, but it's strange that for some users it works and for others it doesn't... Any idea? I'm literally getting crazy, for a game (JK obviously)
[Magisk] A.lemane:
I sense a lot of anger ,

I can't even get safety net to work no matter what I do fresh rom clean slate anything & the moment I uninstall magisk it works & I've gotten use to it @@ CZ I tried everything
[Magisk] mn1968:
I have rooted an Asus Zenphone Max M1 (ZB555KL) via Magisk Manager by flashing the patched_boot.img. Everything is great. However, I am now working on porting TWRP (it is mostly functional as tested by merely booting it). It is my understanding that I will need to flash the no-verity-opt-encrypt.zip. Prior to flashing the no-verity-opt-encrypt.zip, I will need to wipe and format data. Will that, in addition to erasing the internal storage, also remove my current root/Magisk? Not a big deal since I should be able to flash it back with TWRP...I just want to know exactly what to expect/if I am correct in my assumptions.

Thanks!
[Magisk] thaolegend:
i have question

magik last version have support some device xiaomi used android one

ex: mi A2 lite

thanks
[Magisk] spartan268:
That did it! Had to set everything up again but oh well. Thanks kind sir. You helped me out big time.
[Magisk] sash11:
Works fine on Mi A2.
[Magisk] Geddd:
I'm using Mi A1 on pixel experience rom, and I have an app who does not support root, but I can't able to use it even if having it marked on magisk hide.
[Magisk] e4zyphil:
Hey i would highly appreciate help !

I dropped my phone the other day and since then my volume up key is broken irrevocable.

I wanted to update a few modules via the magisk repo and encountered the problem that I can't choose the newest version of some modules because of it.

I don't really know where to ask for a fix so I'm starting here. I already googled and I couldn't find any way around it.

I also tried simulating the pushed vol up key via adb per "adb shell input keyevent 24", but it only responded it would use a legacy-version of key-checking, but after that nothing happened anymore.
[Magisk] A.lemane:
I guess

Go for the module and modify it
[Magisk] jcmm11:
Which modules?
[Magisk] mn1968:
Just an FYI for anyone else....I nearly borked my phone. I wiped/format data while booting into TWRP and that appeared to decrypt the phone as I was able to select& browse both internal and external sd card (couldn't select/browse internal before). I then flashed the no-verity, rebooted and bootlooped. I then booted back to TWRP, wiped/format data, flashed no-verity and magisk. Rebooted and continued bootloop. Booted back to TWRP, restored my backup and rebooted. It booted up as if it was a new phone...not to my my backup. OK...at least it isn't bricked. Went through setup, rebooted to TWRP, wiped/format data, flashed no-verity and magisk...bootloop. Had to "restore" my backup to get to brand new set up again. I guess I can't have a decrypted phone and only boot to TWRP. After all is said though...I am rooted with Magisk.
[Magisk] A.lemane:
Try this

Copy data content manually to SD card (restore it manually through Twrp after wiping data)
[Magisk] martyfender:
removed.

---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------

I thought that by default, Magisk flashes with no verity? Or is flashing a no verity zip something that must be done for certain Android devices? Again if you formatted data, flashed the Magisk.zip, then rebooted, usually a new, unencrypted data partition is created. Is this not true for some devices?

https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
[Magisk] A.lemane:
Yep it should be included in it

But from my point of view (I think some devices require some data in the data partition to boot (oem}}

Or try this , do a factory reset from settings once it's over & try wiping data again , see if it works (the reset part would probably be better with stock recovery)
[Magisk] goldmobile:
Please how UnFreeze android System wepview?

[IMG="image"]https://i.hizliresim.com/lZAXPk.jpg[/IMG]
[Magisk] @srmahunt:
You don't need that as most of its job is done by chrome itself.
[Magisk] yochananmarqos:
See the section titled WebView Issues: https://www.didgeridoohan.com/magisk/MagiskIssues
[Magisk] habylab:
I am having the exact same issue as you describe on my OnePlus 6. It works in core only mode, but not in any other mode. Hopefully it'll be fixed with your logs.
[Magisk] rptb1:
Magisk Manager is stuck on its splash screen.

Fairphone 2

Lineage OS 15.1 20180924 nightly FP2, Open Gapps pico, not rooted.

Magisk v17.1 installed via TWRP.

I've been through several uninstall/reinstall cycles.

How do I find out why it is stuck?

Thanks.

Edit: fixed. Moved Magisk Manager from adopted sdcard to internal storage. Thanks to Magisk Troubleshooting Wiki.
[Magisk] martyfender:
I also posted this problem on [MENTION=4470081]topjohnwu[/MENTION] 's issue area on his github site. You and one other are the only responses I have seen about it.

I think topjohnwu is very busy with school (my guess). He has not posted any recent commits other than updating Android Studio to 3.2. It has been almost a week since a new Canary release. This is not a complaint. I understand you time constraints.

Thanks for spending your valuable time on this when you have it available.
[Magisk] ecompton59:
i believe you have twrp beta checked I'm on 17.2 now he changed how magisk hides itself it goes to downloads and my opinion is grab the magisk uninstaller flash that flash no-verity flash after magisk uninstaller reboot to twrp not SYSTEM then flash magisk v16 or patched boot.img or however your rooted every phone is different and about oem i had issues when i deleted one of the oem apps freeze not delete them

---------- Post added at 10:24 AM ---------- Previous post was at 10:20 AM ----------

hope that helps if not someone hopefully will help you soon I'm going to test on my little issue uninstalling all mods i flash with magisk before v17 then reinstall the with 17 see pic ones download folder other is old magisk foldet
[Magisk] ecompton59:
everything worked right with uninstalling everything i installed before v17 magisk rebooting a extra time or 2 with my g5 stock rooted and Moto z2 force custom kernel working perfectly
[Magisk] martyfender:
A problem I previously reported, a few posts back is solved with core only mode.

One valuable module I use is the Greenify4Magisk Module. When I boot back into normal mode is there a way for Greenify settings to be restored without setting Greenify up from scratch again?

It is not that big of deal to set it up, but you must grant root again, set the settings you prefer and add the hibernating apps, once again.

Thanks
[Magisk] abdoh01:
hi guys there is something wrong in magisk 17.2 it cant be installed in twrp without stacking in lock screen so it must be installed from magisk manager and every time my phone boot i have got android starting and installing thing without any reason
[Magisk] martyfender:
What does that mean? I don't understand the translation. Do you mean a bootloop?
[Magisk] goldmobile:
It is very important for me because my bank application is working with it. no need to open

---------- Post added at 08:13 AM ---------- Previous post was at 08:05 AM ----------

Supersu not Freeze this application
[Magisk] paarnoutse:
Starting with Android 7.0 Nougat, WebView services became part of Chrome.

Therefore you don't need the standalone 'Android System WebView' package anymore as long as Chrome is available at your device. At many devices with Android 7 and above, the standalone Android System WebView package is made *potentially* available at your device, but in 'frozen' (disabled) status, so can't be actually used yet.

Initially and by default, apps and/or other browsers that are invoking WebView services will be redirected to the build-in WebView services of Chrome. In case you have installed another default browser than Chrome *and* you also want to freeze (disable) or even uninstall Chrome, then (and only then) the stand-alone Android System WebView will be required, so must be unfrozen (enabled).

To unfreeze (enable) Android System WebView:

Go to Settings / Apps / Application List

Enable 'Show system apps'

Select 'Android System WebView'

Press the ENABLE button

However, the ENABLE button will be grayed-out as long as Chrome is installed (yeah, it's Google...).

Therefore first uninstall or freeze (disable) Chrome, then enable Android System WebView.

Via Settings / Developer options, you can use the option 'WebView implementation' to view or change whether Android System WebView or Chrome should be used for WebView implementation at your device.

(as long as Android System WebView is disabled, it's shown here but obviously you can't yet select it).

BTW:

You posted the remark that you need Android System WebView because "my bank application is working with it".

Many (most) apps make use of WebView services, but what is actually implemented to perform the WebView functions at your device (Android System WebView, or Chrome) shouldn't be interesting for the app itself. Both should work, and when it doesn't run OK using the build-in WebView services of Chrome, I guess it will also fail after switching to Android System WebView as your WebView implementator.

UPDATE (2018-10-05):

What's actually used as your WebView provider (the Chrome build-in WebView or the standalone 'Android System WebView' package) appears to be not user selectable at all...

Chrome is enforcing to use its build-in WebView by automatically disabling the standalone Android System WebView, and also blocking the possibily to enable it.

ONLY when Chrome is disabled or uninstalled, then (and only then) Android System WebView is automatically and immediately enabled.

Similar behavior for the reversed way: As soon as Chrome is (re-)enabled or (re-)installed, Android System WebView is automatically and immediately disabled again.

In short:

Chrome is installed and not disabled?

Then always its build-in WebView is used

Chrome is not installed, or disabled?

Then always Android System WebView is used.
[Magisk] A.lemane:
What's ur Android version ? Samsung device ?

---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------

He's saying

That he can't get magisk to work when installed through recovery CZ it causes hi phone to gets stuck at the lock screen

---------- Post added at 01:33 PM ---------- Previous post was at 01:27 PM ----------
[Magisk] khangcobra:
the latest 17.2 still cant play fgo jp. anyone have the other results ?
[Magisk] Killua96:
Someone yes, but I can say the same thing as you, latest magisk is detected, have to wait for a release with 100% full obfuscation
[Magisk] khangcobra:
i was hopefully i can move to android 8 and use magisk :( thank you
[Magisk] nilesh0205:
Same thing is happening with 17.2 as well. I have seen that after 17.2 install (through magisk manager or TWRP) after first reboot, the lineage os gif blanks out for few second and then comes back up. but it just keeps running and never even goes to lock screen now. so if I fo back to 16.7 it works fine and phone starts. But the problem is that 16.7 can not hide from Google detection methods anymore and I can not use G Pay at all or some other apps which checks for safety net

Is there a way to resolve this issue of installing 17.2? If needed how can I get the log for installation and boot and then I can post it here?
[Magisk] A.lemane:
Snapchat Xposed users

SnapFreedom - http://repo.xposed.info/module/lp.kenic.snapfreedom

Latest supported version

https://www.apkmirror.com/apk/snap-...ease/snapchat-10-41-5-0-android-apk-download/
[Magisk] btfo:
17+ versions is fckin hell. Broken everything, bootloops, randomly unrooted apps etc.

worst update ever
[Magisk] TheUndertaker21:
yeah fortnite is not working not that i care since i don't play it

but wanted tot est it

kicked me out when i get off the buss

but my spay for gear is working that's all i care about
[Magisk] tool666schism:
Does anyone know of a way to disable Magisk Hide from TWRP?

I was messing around hiding applications and when I attempted to hide a file manager it sent my device into a boot loop. It no longer boots at all into the OS and just goes straight into TWRP. Any advice would be appreciated.
[Magisk] byReqz:
use magisk manger for recovery, you can flash it in twrp and directls use it
[Magisk] Apexpredator12:
Well, I activated Magisk core only so I was able to bypass the check, it worked I logged into the ap that I needed. Then I disabled Magisk core only and rebooted it gets past the first Samsung screen when ti first powers on but won't get to the Samsung loading logo it just stays on the black screen.

I have the current version of Magisk installed my android version is Galaxy S6 MM I have systemless xposed and magisk on.

EDIT: I managed to get it to boot by flashing a zip file that I found which enables Core mode, but if I disable core mode it gets stuck back in the boot loop any help would be appreciated
[Magisk] elmu:
ok i can't heart nothing sound with bluetooth headphones with magis v17.2 and androis 9...i have oneplus 6.
[Magisk] tool666schism:
Thank you! That module is a life saver!
[Magisk] byReqz:
yeah, saved my ass a few times
[Magisk] Djaentz:
If I would update my twrp, do I have to uninstall magisk first? And is it recommend to flash a custom kernel after magisk or before?

Regards
[Magisk] A.lemane:
The easiest way is to flash the uninstaller

---------- Post added at 10:33 PM ---------- Previous post was at 10:30 PM ----------

No don't have to

&

After
[Magisk] Apexpredator12:
I found it was the Systemless xposed I installed via magisk manager, I removed the module and tried to install systemless xposed via the xposed app, but when I try and flash it via recovery it just says zip file is corrupt, I have redownloaded it 4 times and its the same
[Magisk] A.lemane:
Might be the connection , anyway try with Magisk again
[Magisk] Apexpredator12:
I previously had the Xposed installer version installed systemless v89.0 sdk 23, then when I tried to install the magisk systemless v 89.3 systemless it won't boot, but if I try to install the previous version it says it is corrupt even if I try earlier versions it says the same. If I try the magisk version again just goes back to black screen
[Magisk] guest4711:
Move the hidelist out of the way... (rename /sbin/.core/img/.core/hidelist using a good filemanager or from the console/terminal).

su
cd /sbin/.core/img/.core/
mv hidelist hidelist.old
[Magisk] Apexpredator12:
I have tried with an explorer and console, it says read only file system I tried to change that but wouldn't work

EDIT: in recovery I tried running xposed uninstaller to make sure it was completely gone, come up with error 1, magisk is not installed, even though it is and root is working.

I installed an earlier version of magisk in case it was because i updated to the newer one, and it says that /data/magisk is not setup properly
[Magisk] Test_subj:
Package name randomization problem

I'm having a problem with Magisk (16.7-17.2) on LOS 15.1.

When I choose package name randomization, it does exactly what it should until the next reboot. Once I reboot, I then have 2 magisk manager icons. If I click the randomized package, it hangs. If I click the other, it's a stub that asks me to install the full version of magisk manager. This happens even on fresh system/factory reset.
[Magisk] abdoh01:
No i get stuck in lockscreen it s not bootloop and if i install it from magisk manager every time the phone boot it says android is starting and apps starting without installing any thing new or any module

---------- Post added at 07:34 AM ---------- Previous post was at 07:31 AM ----------
[Magisk] donjoe0:
@topjohnwu

^ Fixed what the official installation/troubleshooting guide should say about the F2FS bug. (Mention Lenovo, mention that flashable zip solutions exist that don't require a change of kernel, list the options in order of increasing risk/impact.)
[Magisk] wannaskoo:
Hi everyone! It seems that i have a problem with Systemless Hosts, because when i try to apply Adaway or the Energized module i always get some errors telling me that i have no space in /system, but i have 1.3 GB of free space in that partition, so i really don't know what i am doing wrong. I have a OnePlus 6, LiquidRemix Oreo, Magisk 17.2.