yashsingh1/xdaforums huggingface dataset:
[Magisk] hanschke:
my mistake is that I flashed edxposed and got the stuck on bootloop but cannot remove it without twrp for pixel 4 xl and I dont want a wipe and losing my data but got on dp3 the same error as you can read. I try different usb cable and computer too.

So I will wait for twrp that I can delete manual the folder or push the magisk file for core because I try it with adb but it dont work too.

[edit]

I dont understand to unzip the patched magisk boot image to do a core mode for myself
[Magisk] amg314:
Try flash stock boot.img via fastboot:

fastboot flash boot your_boot_name.img
fastboot reboot
[Magisk] wrecklesswun:
so even more i can boot to the patched file - weird fastboot boot magisk_flashed.img

but i can also flash and get stuck.
[Magisk] zgfg:
You could search for Core Only in this thread, to find previous discussions (and success stories) about preparing the Core Only Magisk patch and fixing the bootloop caused by a module

Check also this thread:

https://xdaforums.com/pixel-3a/how-to/magisk-modules-disabler-booting-magisk-t3976621
[Magisk] wrecklesswun:
Ok now i have the daemon running. but remove modules returns the same error.
[Magisk] zgfg:
He/they can boot with stock image but it's not of much use - it means booting without Magisk running, hence with no root

Without root, he/they can not disable or remove module(s) causing the bootloop. But all modules are still there (waiting like a time bomb) in /data/adb/modules and next time he/they boot again with the Magisk patched image, Magisk will find all the module(s) previously installed, it will try to run them, and it will get stuck in bootloop
[Magisk] wrecklesswun:
i think i need to undo what the audio mod lib did, it was the only update before this occured. i tried fastbooting to the magisk boot and same result. i don't have access to modules folder... is there a way to get magisk to blank the modules folder during the img creation.

again if this was C# i'd be a pro, but i suck at this :)
[Magisk] Didgeridoohan:
The only options currently available when a module causes a bootloop are:

Uninstall the module from TWRP (use the file manager and add a file named "remove" to the module directory).

Use the Magisk adb command to remove the module during the bootloop.

Create a Core Only Mode (will be renamed to Safe Mode soon) Magisk patched boot image (example).

Wipe /data.

As you can see, the only options you have at the moment are the last two points.
[Magisk] zgfg:
Please check three posts back (in sandwich between two your posts), hint for another user with also the module bootloop issue
[Magisk] wrecklesswun:
tried that and that didn't work - but i think i now have a clue. The audio mods used for viper, during that install changes are made, and i suspect those are not allowing to boot.

I am thinking not but hoping so, is there a way to to a differential or log of the booting of the patched img, to see where it hangs?

Again if this was windows, i'd be all in it, but i am a novice at linux...
[Magisk] Didgeridoohan:
Like you say, it is likely that you got into this issue when installing V4A. Grabbing a log during boot might of course confirm that, but ether way your only way out of this is to disable or remove module. That can only be done by somehow accessing /data/adb/modules, something that you need root to do. My list above details your current options.

If you really need to grab logs, what you want is to run adb logcat.
[Magisk] wrecklesswun:
sorry for the dups - do i just copy the overlay.d to the root of the ramdisk?
[Magisk] Didgeridoohan:
Yeah. But, have you checked your device's forum? There's a similar thread there, with pre-patched boot images: https://xdaforums.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
[Magisk] wrecklesswun:
seems to get stuck here

04-29 16:27:30.803 623 822 W ServiceManagement: Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default

04-29 16:27:30.804 623 822 I ServiceManagement: getService: Trying again for android.frameworks.sensorservice@1.0::ISensorManager/default...

04-29 16:27:31.804 623 822 W ServiceManagement: Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default

04-29 16:27:31.805 623 822 I ServiceManagement: getService: Trying again for android.frameworks.sensorservice@1.0::ISensorManager/default...

[

over and over

---------- Post added at 09:37 PM ---------- Previous post was at 09:30 PM ----------

That's exactly where I got my directions and followed that did not work
[Magisk] Didgeridoohan:
That's from the logcat? What does it show about the Magisk boot process? You should be able to see there if it is loading the modules and scripts or not. If it isn't it means that your Core Only boot image is doing it's thing and that you might actually have something else going on.
[Magisk] Vs995Child:
Ok, so maybe someone has mentioned this, but I've noticed if you do not update, you can no longer flash mods.....is this correct? Im using version 19.4 and was quite happy with it......i guess all good things come to an end, lol!
[Magisk] DiamondJohn:
A couple of things.

1. I am not sure about Magisk, but as a general rule, the filename makes a difference in boot scripts; I don't remember anywhere you telling us that detail. It should not have any extension (ie no "sh" ) or the more obvious but needs to be said out loud, it should not have a dot as a leading character :silly: Maybe add a log in your script. eg:

cat /sys/devices/virtual/bdi/179:0/read_ahead_kb

2. The following affects the previous point. However, in my boot script, the actual value is being set elsewhere. I actually have a loop going through all my partitions, so its hard to know which one exactly is my internal sdcard, but, the location is more in the format of:

/sys/block/mmcblk0/queue/read_ahead_kb

/sys/block/loop0/queue/read_ahead_kb

Not 100% sure which "loop[n]" is my internal sdcard, as I loop through them all, and I have 7.

3. It should not make a difference, but your path should negate the need to explicitly state the path to the "echo" command.

4. Your "if" statement is not the way I would do it. to test for a file, its normally:

if [ -[B][COLOR="Red"]f[/COLOR][/B] /path/to/my/filer/file_name ]; then

If think "-e" is for a directory not a file.

---------- Post added at 11:30 ---------- Previous post was at 11:23 ----------

ooops... I almost forgot, you may need to change the permissions on the file before you write to it.
[Magisk] JudgeDread11:
You should be able to flash modules with the correct template for your Magisk version.

But the module template has been updated and it might be that the modules your trying to install a are on a newer template then what your Magisk version uses.

In that case you can either try a older version of the module or update Magisk.
[Magisk] Vs995Child:
Ok makes sense. I will try the update. I've been avoiding the updates, since that one update that was crashing phones. We'll see how this one does. ?
[Magisk] delt01:
Hello everyone, just installed Magisk current version on my LG G5 (H850) running Lineage 17.1, works great but sensors (screen rotate, proximity, gyro, magnetic, etc) are no longer working/usable by the OS or apps. Every test app says "No data from sensors" or something to that effect.

Kernel modules clobbered from boot image maybe?
[Magisk] mvdi:
Yes, I looked at the link, there's a lot of useful hints. It's hard to find out how the app ist checking. See below.

Have done this a few times with Catlog app, the banking app generates a lot of entries. Should I only look for the error messages? For example, it sometimes reports not finding a particular file, which may or may not be some clever trick to test root.
[Magisk] delt01:
Update, i reflashed the stock boot partition, wiped everything and did a clean install of LineageOS, still no support for sensors. So maybe i was mistaken in my remembering that at least the screen rotate and proximity sensor did work at first with Lineage?

Tomorrow i'll download the stock firmware for this phone and reflash it, see if the sensors work in stock. I'm pretty sure they should, but just to make sure.
[Magisk] cnjax:
Sensors, camera issues are common in Los builds, you should inquire in the Los support thread for fixes as it has nothing to do with magisk
[Magisk] zgfg:
Is the package name for your banking app ch.postfinance.android (check e.g. by AppInspector - from Playstore)

Your logs indicate that app dies since not white-listed (?!)

Maybe try from Settings/Apps, find your app and Clear Cache or even Clear Data and reboot (if the app remembered that it had previously found Magisk)

04-30 10:38:38.044 I/ConversationToQueryExte(7977): ConversationToQueryExtension.isEnabledForHostApp():257 Conv2Query not enabled due to current app [ch.postfinance.android] not in whitelist
...
04-30 10:38:42.246 I/AndroidIME(7977): AbstractIme.onActivate():83 PasswordIme.onActivate() : EditorInfo = Package = ch.postfinance.android : Type = Password : Learning = Disable : Suggestion = Hide : AutoCorrection = Disable : Microphone = Hide : NoPersonalizedLearning = Disable : AutoStartVoiceInput = Disable, IncognitoMode = false
04-30 10:38:42.301 I/ConversationToQueryExte(7977): ConversationToQueryExtension.isEnabledForHostApp():257 Conv2Query not enabled due to current app [ch.postfinance.android] not in whitelist
...
04-30 10:38:42.899 W/ActivityManager(1275): Force removing ActivityRecord{a957983 u0 ch.postfinance.android/.elibrary.login.ui.LoginFlowActivity t18774}: app died, no saved state
...
04-30 10:38:42.897 I/WindowManager(1275): WIN DEATH: Window{25295fb u0 ch.postfinance.android/ch.postfinance.android.elibrary.login.ui.LoginFlowActivity}
[Magisk] Didgeridoohan:
[MENTION=711602]wrecklesswun[/MENTION] and [MENTION=453210]hanschke[/MENTION].

Soon it seems like you'll have a working adb command to remove Magisk modules:

https://github.com/topjohnwu/Magisk/commit/5fd574a14f6de5cc98b513c884a4269b001d6ba5

Next Canary (no ETA, of course) will fix the crashed daemon that prevents the command working, hopefully.
[Magisk] wrecklesswun:
Question in Magisk hidewhen the item is selected and the radio button is on is that being hidden or do you have to unselect the radio button to actually hide it's a little confusing
[Magisk] zgfg:
Screenstots show settings in Magisk Canary 283

- first screenshot, Magisk Hide enabled

- second screenshot, Magisk hiding from the first two apps, not hiding from the third

Reboot, once you make a change. Some apps may remember that they previously detected Magisk, hence clear their Cache or even Data through Settings/Apps
[Magisk] kpitao:
Hello all...

Does anyone have a problem with an app crashing AFTER root with Magisk? I use this app, it works fine prior rooting but after rooting the app keeps crashing….

The app works on my phone before and after rooting…. Only on my android car stereo unit does not work after root.

App is DI.FM music app....

Any thoughts?
[Magisk] delt01:
Yep, seems to be the case. My apologies for the mistake, and thanks for confirming this.
[Magisk] zgfg:
Actually a question, why Magisk Manager could not write info about the installed modules and/or requested Core Only mode to its folder /data/data/com.topjohnwu.magisk (or the corresponding obfuscated name in case of repackaged Manager) - it doesn't need root to access this private app Data folder

Then, in case of such bootloops there would be no need for TWRP, adb shell Magisk command or Core Only patched images

Simply, you would flash stock image to boot without Magisk, but open Magisk Manager and flag that you want (next time) Core Only mode or certain modules to be disabled or removed.

Then flash your normal Magisk patched image (not the Core Only one), Magisk will find the requested flags from /data/data/com.topjohnwu.magisk and it will reboot to the requested Core Only mode, or it will disable or remove particular module(s)

That can also work in case of repackaged Manager - Magisk will first find from magisk.db at /data/adb the obfuscated package name (as it already does) and it will read then those flags from that obfuscated folder name under /data/data/

Am I missing something?

Since the other data (db, modules, etc) will be still kept in /data/adb, they will still be preserved in case of uninstalling Magisk Manager or deleting its Data (as of now)
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] You would have to ask [MENTION=4470081]topjohnwu[/MENTION] about that. I don't know the inner workings enough to say yay or nay to that suggestion. Keep in mind you'll have to ask him on GitHub, he doesn't read the threads here.
[Magisk] mvdi:
I already tried clearing cache and data, also uninstall and reinstall. I cleared cache and data again and saved the log. Because I cleared data I need to re-register, so the screens are different to normal.
[Magisk] wrecklesswun:
It would be cool if there is a select all etc
[Magisk] zgfg:
Hiding from all apps makes no sence - Magisk must not hide from root apps, they would never be granted root access because Magisk would ignore their requests
[Magisk] wrecklesswun:
beats having to select hundreds vs a few.
[Magisk] Lughnasadh:
You have hundreds of apps you need to hide? To quote [MENTION=4487388]jcmm11[/MENTION], "You should only hide things that are explicitly problematic because they detect root. Hiding everything is likely to lead to problems because of the way that Magisk works."
[Magisk] J.Michael:
Select all what?
[Magisk] Wolfcity:
Select all apps. As said above that would be completely counterproductive and may cause problems that will appear here in this thread again....

Magisk doesn't work that way.

Only hide apps that definitely need it like that one banking app, the game that detects root or for example Rootbeer sample.
[Magisk] zgfg:
I decided to bite the bullet and to make and test such a Core Only Magisk image myself.

I had two rooted devices to test

- (old) Huawei P9, EMUI 8, Android 8

- (new) Xiaomi Mi 9T, MIUI 11, Android 10

For Huawei P9 there is no TWRP supporting the encrypted storage and

adb wait-for-device shell magisk--remove-modules

never worked, hence Core Only would be the only chance

For Xiaomi Mi 9T there is a proper TWRP and adb Magisk deamon starts correctly at the boot time, hence Core Only mode is not a must

So, the method by osm0sis and Tulsadiver is actually quite simple. It takes to install Android Image Kitchen (e.g. for Windows), and to use its two batch scripts unpackimg.bat repackimg.bat.

First to unpack your Magisk patched recovery/ramdisk/boot image, then to copy a particular overlay.d (with their shell script examples to force Core Only mode) into the ramdisk folder (which was obtained by unpacking the image).

Finally to repack the image and flash it

For P9 it worked as expected:

Upon flashing and rebooting, Magisk Manager, Modules tab showed in red that it's running Safe mode, and no modules were listed as installed.

For Mi 9T it didn't work at all:

It rebooted back to the full blown mode with all modules. I checked and found that there was no ".disable_magisk" flag in /cache (as it has to be for Magisk to boot to the Core only mode - meaning that shell script from the added overlay.d was not executed as requested)

I tested more on Mi 9T by modifying the shell script in overlay.d, but could not make it to remove a given module from /data/adb/modules or to leave there "disable" flag

Hence this method also, for some reason, does not work on all devices.

Seems that reason is i n the architecture of the MIUI stock boot image (its ramdisk folder, when unpacked is empty so maybe something is missing there, and also when that image is patched by Magisk, to make the shell script from the added overlay.d to execute)

More about this on the pages 4 and 5:

https://xdaforums.com/pixel-3a-xl/how-to/magisk-modules-disabler-booting-magisk-t3976625/page4

---

Reported to GitHub about this alternative idea, hopefully to the right place and the right way:

https://github.com/topjohnwu/Magisk/issues/2756
[Magisk] Bennyg-:
Hey,

Move Certificates Module.

Didn't know where to post this but I have a Mi A1 and when I updated the module that was released today. Upon reboot it came up corrupted sd card format. I disabled the module and rebooted then the error for sd card went away.

Thanks to the dev for the module!

✌️
[Magisk] J.Michael:
I wanted to know what [MENTION=711602]wrecklesswun[/MENTION] meant by "all". From the context, it wasn't clear to me whether he wanted to select all apps to be hidden by Magisk, or to select all apps to clear their cache/data. If the latter, I might have suggested that he just wipe his device. (I have seen the warning not to hide more apps than absolutely necessary.)
[Magisk] Agret:
My phone was failing safety net so I ran the magisk uninstaller and then flashed the latest canary and the latest manager with the new material design. All seems good now, passing safetynet but failing ctsprofile (I guess this is normal on OnePlus 5T).

My question is how do you use MagiskHide on the new material manager? I go into the second icon and press MagiskHide at the top which brings up a list of all my games/apps. Press the arrow to expand the activities/processes (not sure exactly what the lsit is) and hit the radio button next to each one to mask it. Now I am not sure how to save it as the only icon on my screen is the filter one. If I press the back key and go back into MagiskHide the apps I just ticked off are back to how they were before (unticked). There must be a save button/feature somewhere i'm missing but have spent awhile trying to find out how to and am lost, someone please help thanks.
[Magisk] Didgeridoohan:
Sounds like you haven't activated MagiskHide. Do that and try again.
[Magisk] BeeJ1109:
Hi, Finally got Magisk Hide to be available on my Samsung T330 millet Tab 4. TWRP V3.3.1-0- milletwifi.

Can select any app to Hide. I am on Stock ROM 5.1.1, rooted with Magisk 20.4 and Manager 7.5.1.

Got props, Safety Net v2, latest Magisk Hide, and Busybox.

Got GREEN TICKS on Safety checks. Meaning Magisk Hide is working.

Close down Manager, then restartup Manager again, check that Magisk Hide is still present.

SADLY NOT. Repeat again, same result.

Therefore the settings are not being saved in the config.

If I could locate the settings config file, could be viewed and maybe modified, so MagiskHide is permanent, instead of requiring to be setup everytime I wish to use the prop.

I have uninstalled Magisk, reinstalled via TWRP, wiped cache, restarted Tab, reinstalled manager and tried all again. Still same result, Magisk Hide is saving any previous setup.

Any suggestions. Cheers

[QUOTE =@stormy_gale;82436623]Have you tried just toggling hide in magisk settings rather than configuring it each time?

I've had a similar issue on reboot when all the hide apps would be unhidden, toggling the setting restored all my apps that were hidden before the restart. [/QUOTE]

Didgeridoohan suggested that I move my Questions on Magisk to this Thread.

What do you mean by "toggling magisk hide settings"
[Magisk] BeeJ1109:
Hi Didgeridoohan,

Thanks for your reply,

Years ago I used Flashfire 0.73 Pro to root my devices, but after Android 4.4, Most OLD Root methods do not work any more on later versions. 5.1 onwards,

So I started using Magisk around v14 onwards. Back then on 4.4, I used an app to hide Root called "Hide My Root" v4.0 by amphoras

Which could hide the SU binary or su app being Flashfire. Which is not supported now. OP Chainfire retired.

I can still use Flashfire installed on my Samsung S3 GT-i9305 with RR -N-v5.8.5-20190219-i9305-offical ROM by Rodman based on Lineage 7.1.2 OS Build no. Resurrection Remix Nouggat- 7.1.2_r36 - NJH47F Security patch 5/2/2019.

Problem is Flashfire can identify the device is rooted by Magisk - found root 20.4:MAGISKSU.

"But Access could not be acquired but lists Supported Roots Super SU ( my previous Root method), Magisk (Which I suspect means earlier versions 17 or earlier). CM SU (SELinux/Permissive)."

I suspect the SU is installed in a different location, comparing "Flashfire/SuperSU Root" method that "Hide my Root" worked well. Compared to the latest Root method, using "MAGISKSU, being managed by it's Magisk Manager, using Magisk Hide" does not work for me.

QUOTE "Keep in mind that MagiskHide can't do it's full thing on an Android version before Android 7, and the Magisk Manager can't be fully hidden on versions before Android 9."

I have Samsung S3 i9305T RR Android 7.1.2 ROM as indicated above. Magisk Hide performs the same as Tab 4 SM-T330 using Stock 5.1.1. ROM. Does NOT WORK on either device.

So I will try your other suggestion, using Canary Debug Magisk Log. To troubleshoot.

Regardless I think the Magisk Hide can be selected, select the app to HIDE, but NOT SAVED, after a reboot.

Both devices PASS SAFETYNET.

That's it for, Thanks for your Help so Far.

Cheers
[Magisk] pndwal:
Well, he said 'toggling [read: switch off, then on again] hide IN magisk [Manager] settings.' Hope it makes more sense. PW
[Magisk] martyfender:
Didgeridoohan suggested that I move my Questions on Magisk to this Thread.

What do you mean by "toggling magisk hide settings"[/QUOTE]

Go to Magisk Manager settings and turn on MagiskHide or if it is already on, toggle it off then on again.
[Magisk] Agret:
Thanks you nailed it, looks like a feature needs to be added that disables the magiskhide button when it hasn't been activated in settings.
[Magisk] BeeJ1109:
Go to Magisk Manager settings and turn on MagiskHide or if it is already on, toggle it off then on again.[/QUOTE]

Hi all,

Tried that lots of time.

1. Open Manager settings, move Toggle Switch Magisk Hide to ON.

Then select any app. Ticked. App is supposed to be HIDDEN.

Close Magisk Manager, then reopen, Magisk Hide is still added to list. Check the app that was preselected before is still ticked.

So you think Magisk Hide is working now.

2. So Power down and Power up. Open Magisk Manager, Settings NO Magisk Hide in list.

So latest settings Not being saved, so NOT FIXED.

Tried Magisk Core Only Mode with Magisk Hide both turned ON.

Repeated same as above 1. & 2. After power down and up. Only Magisk Core Only Mode still ON, but Magisk Hide NOT ON again, ie Switched OFF.

So Magisk Hide is NOT PERMANENT Selected in Settings.

Any more suggestions. Cheers.
[Magisk] Didgeridoohan:
Canary Manager is a work in progress still... That particular feature is on the works though (no ETA).
[Magisk] Didgeridoohan:
Sounds to me like you're simply affected by the bug where MagiskHide needs to be toggled after every reboot. There's no fix for that, but you could use something like Tasker or a service.d boot script to automate it.

Take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_fails_after_rebooting
[Magisk] co-moi:
Hi there i nearly have the same problem with my Xiaomi Mi 9T Pro (K20) there is also no more Magisk Hide in the manager. I have read that the developer is busy atm and perhaps there will be some help soon.

I decided to flash the "newest" version of magisk manager 765d5d97 by topjohnwu from apkmirror for Andorid 4.2+ on my Lineage (Andorid 10) and there is Magisk Hide again. The question is: is this magisk manager safe?

Now it is like that some apps recognize that there is framework xposed installed, if i uncheck framework and xposed manager in magisk modules the apps see there is root but they don't care and work.

It now became really wired because i use many different apps which tells "no root!"

Some are working now with magisk hide and one is working only with framework xposed and zuper (hide root) and one is working only with uninstalled framework.

I think this are more possible safety leaks than there just would be hagisk hide working.
[Magisk] Didgeridoohan:
[MENTION=7314739]co-moi[/MENTION] The only way to know for sure that the download is safe is to get everything from [MENTION=4470081]topjohnwu[/MENTION]'s GitHub.

Stable releases:

https://github.com/topjohnwu/Magisk/releases

And if you want the Canary release with the current upstream changes you can find that in the magisk_files repo:

https://github.com/topjohnwu/magisk_files/tree/canary?files=1