yashsingh1/xdaforums huggingface dataset:
[Magisk] GhostZini:
I saw that it said that but I don't even see where you could select/unselect that
[Magisk] guhvanoh:
Go back and try and flash it through TWRP. Pay close attention to all the screens and you'll see the option.
[Magisk] martyfender:
I'm not sure, but did you try unchecking Zip signature verification and maybe check Disable Digest generation during backup and uncheck Enable Digest Verification of Backup Files in TWRP settings? Hopefully, someone more knowledgeable will chime in here, though.
[Magisk] Didgeridoohan:
It's not necessarily the date of the folder that matters. Keep the one that matches the SHA1 value in /sbin/.magisk/config.
[Magisk] GhostZini:
I tried all variations of what you suggested and still no good . So weird. I wonder if I go back to an older twrp instead of -79. Or maybe the newest update is causing? Pain in the arse
[Magisk] zgfg:
When are actually those backups /data/magisk_backup_* created (eg, when installing Magisk by TWRP or updating Directly)?

Bcs, I do more often image patching than that i have these Magisk backups
[Magisk] BillGoss:
Why doesn't Magisk keep things clean and automatically delete obsolete versions?
[Magisk] xunholyx:
No.

Canary is alpha/beta builds that aren't stable yet. If Magisk is working fine for you, there's no reason to try the canary builds unless

#1 you want to beta test and you know how to get and send a proper logcat (or flash the debug version)

#2 there's something that isn't working on stable and you need canary updates that are fixing it

#3 you are on the Android developer preview and the current version of stable Magisk doesn't support it.

Of course you are more than welcome to flash it, but for regular users stable is probably the best choice.
[Magisk] tqwzUX6fn39GZMEzSnDF:
Thank you. Noted SHA1 value itself is different, but SHA1 value is part of folder name where boot.img.gz is. This is as it should be?
[Magisk] Estebanium:
I use a module to patch my services.jar for signature spoofing. However if I want to dirty flash my ROM with an update, I need to update my module of the services.jar, too. Is it possible to flash or replace the current Magisk module in recovery, so that the updated module is loaded on boot?

I can not boot to system and replace it then, because then my whole MicroG Framework would explode.
[Magisk] Didgeridoohan:
To both those questions the answer is:

I don't know. Haven't looked closer at that part of the code...

Do you mean that there is no folder that has the matching SHA1 value from the config file? Or? Clarification might be needed...
[Magisk] hanschke:
[MENTION=4667597]Didgeridoohan[/MENTION]

Sorry for the delay but I try it again and got the same output.
[Magisk] zfk110:
ctsprofile: false and basicIntegrity: false

Magisk props won't run since it couldn't detect busybox, but it's there. Thanks
[Magisk] Didgeridoohan:
I'm replying to you here since this subject isn't related to the MagiskHide Props Config module.

It's not entirely clear what you have been trying and what modules you're using, but at least you seem to pass SafetyNet. That's a good start...

If the Hide menu isn't showing in the Manager, that usually means that your kernel doesn't support mount namespace. But, then I wouldn't expect SafetyNet to pass either... So, you might have something else going on. Befoer going on, you could search a bit in this thread. I'm pretty sure I've seen another report of not seeing the MagiskHide menu, but I can't currently remember if there was a solution.

If you want to continue troubleshooting, install the Canary debug release (download and install the Canary Manager, change the update channel to Canary Debug and update). If things start working after that you're good to go and we know whatever issue you had has been fixed. If it still doesn't work you know have the Canary debug Magisk log that you can upload and hopefully it will show something.

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.
[Magisk] Didgeridoohan:
According to that log you don't have any Magisk busybox module installed... Can't say anything about other busybox installations, of course.

Start by checking here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Both_CTS_profile_and_Basic_integrity_fails
[Magisk] tqwzUX6fn39GZMEzSnDF:
Sorry for being not clear. What I wanted to say:

Within file /sbin/.magisk/config there is a SHA1 value. Let's assume it is 123ABC.

I have files /data/magisk_backup_XXX/boot.im.gz

None file boot.img.gz has SHA1 value 123ABC which was mentioned in /sbin/.magisk/config.

But one folder name is /data/magisk_backup_123ABC.

Is this as it should be?

Or should file boot.img.gz itself have SHA1 value 123ABC?

So for me 123ABC is not a SHA1 value, but just a part of a folder name.
[Magisk] Didgeridoohan:
That is as it should be.

Magisk uses the SHA1 value to identify your stock boot image. It saves it in the folder name to easily find the correct file.
[Magisk] J.Michael:
If he unzips boot.img.gz will the SHA1 match the containing directory name?

> gunzip -ck /data/magisk_backup_123ABC/boot.img.gz | sha1sum
123ABC boot.img.gz

---------- Post added at 13:00 ---------- Previous post was at 12:52 ----------

How did you do it the first time? You started with a device with no Magisk, and an unpatched services.jar. How did you get to a device with Magisk and a patched services.jar?
[Magisk] Didgeridoohan:
Yes.
[Magisk] Estebanium:
It seems like it has worked this time. Maybe the services.jar did not change. As always TWRP backup and recovery can save a lot of time and effort.

I initially flash the ROM, flashed Magisk. I used Smali Patcher via developer settings to generate the patched services.jar. and added the generated Magisk Module. To that point is is very nice to have a systemlessly flashed services.jar. But when you install MicroG you will get problems with your Apps, when the spoofing feature gets lost.. So flashing an update for your ROM will very likely remove or destroy you spoofing..
[Magisk] zgfg:
Putting it simple and illustrative (everything on screenstots: calculating checksums, un-gzipping, etc, was done simply by MiXPlorer without a need for additional tools like Terminal emulator commands, PC or else)

1) Folder is named (1st screenshot)

/data/magisk_backup_8999a2cb2c443086dded938962eba873f4f0d780

2) That folder contains single archive boot.img.gz

Click on to open the archive and SHA1 checksum of boot.img (2nd screenshot) matches the checksum in the folder name

3) The same SHA1 checksum is saved in /sbin/.magisk/config (3rd screenshot)

Hence in all three cases it's one and the same SHA1 cheksum:

8999a2cb2c443086dded938962eba873f4f0d780
[Magisk] player594:
The rclone module no longer works in the last version of magisk. Is there a fix for this?

---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------

Is there a fix for rclone in the latest magisk version. It no longer populates folders and folder dir are not getting created.
[Magisk] tqwzUX6fn39GZMEzSnDF:
Thank you all. Wasn't known to me that .gz is a compressed archive with file inside it. Good to know that the file inside the archive has a SHA1 value which matches the one mentioned in the config file.
[Magisk] hanschke:
[MENTION=4667597]Didgeridoohan[/MENTION]

I got the bootloop after the install of edxposed build 4547. now 4548 relesed with a fix android r bootloop. Is there any solution for me to flash it without twrp and magisk with bootloop? Can I patch the boot.img and go into fastboot for adb and flash the edxposed with sideload?
[Magisk] Didgeridoohan:
Unfortunately no. Since the adb comman to remove modules didn't work (might be an Android 11 thing, I can't test that personally but maybe there's someone out there who can give that a go?) your best bet is to create/someone creates a Core Only/Safe mode boot image for your device. Have you checked the device specific forum? Other than that you'd have to wipe /data.
[Magisk] krepsz:
Latest version from Magisk will work on my Xiaomi Mi10?
[Magisk] amg314:
Make Nandroid Backup and try))
[Magisk] paarnoutse:
Regarding (re-)installing a repackaged version of Magisk Manager via a backup of the apk at /data/app:

and:

Normally, the size of an apk within /data/app has same size of the apk that you downloaded to install that app.

However, for Magisk Manager it isn't. Surprisingly, the apk file of Magisk Manager (v7.5.1) at /data/app has a size of just 27.94 KiB, while the originally downloaded MM .apk (the download version at https://github.com/topjohnwu) has a size of 2.04 MiB! :confused:

Possibly the much larger original MM apk performs more (potentially required) additional actions during its install? I don't understand why for MM the apk that is saved at /data/app is just about 1.3% of the size of the original apk...

Does anyone have experience whether a (re-)install of the much smaller apk version (backup from the /data/app version) would be sufficient, and if yes what could be the reason for this huge size difference?

Thanks in advance!
[Magisk] Didgeridoohan:
What you are seeing is the result of Magisk Manager obfuscation through using a stub. The stub is tiny and has no identifying features. At first run it downloads the proper Manager and then loads that apk at runtime from within it's cache directory in /data/data/.

Moving a backup of the repackaged Manager from one install of Magisk to the next has an issue... You'll also have to record the apps random package name in the Magisk database, or it won't recognise it as the proper Manager.
[Magisk] zgfg:
Actually, res.apk in /data/data/<obfuscated-pkg-name>/cache (/data/user/0/<obfuscated-pkg-name>/cache) is also only 3.42 KB
[Magisk] Didgeridoohan:
I was taking that info from memory, so I'm not surprised that /data/data might be the wrong location. The basic principle still stands though.
[Magisk] mvdi:
Hi all. Been happily using Magisk for a couple of years. Now the new version of my e-banking app is detecting it. Safety net check ok. Magisk 20.4, manager 7.5.1.

Android 7.1.2 on Xiaomi mi 5.

Ch.postfinance.android

Anyone have a good suggestion?
[Magisk] Estebanium:
If you use GooglePlay install the App RootBeer Sample. It shows what an App could do for detecting root. So run it first just as it is. Then add the App to MagiskHide and run it again. This is pretty helpful to get the root cause for the detection.
[Magisk] hanschke:
[MENTION=4667597]Didgeridoohan[/MENTION]

I checked it but no luck :( thank you!
[Magisk] zgfg:
Every so and often there is somebody who got the bootloop with a particular module, for whose device there is no TWRP available and for whom

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

does not work (deamon not started at a time)

There will be nice to have Core only Magisk installation available from github. E.g, I would flash my boot image with and keep it just in case.

It would be also easier to patch an image with for somebody else in need

So far few built for themselves but made it downloadable (if) only as patched images for their devices, not as a generic Magisk installation (even if somebody wants to make his Core only Magisk installation available for public, he would have to prepare also his http server with his Jason file, to be used for Custom Channel patching)
[Magisk] Didgeridoohan:
That's been on the to-do list for a while now, but hasn't been a high priority, obviously.
[Magisk] mvdi:
Thanks [MENTION=6867525]Estebanium[/MENTION]. The app detected root. When I added it to Magisk Hide, it could only detect the busy box binary (screenshot). So know I have no idea how the e-banking app is detecting root.
[Magisk] Didgeridoohan:
Could be detecting:

Busybox

Other root apps

Directories/files on your device

Other stuff

Take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Estebanium:
As RootBeer Sample shows this is how banking and other Apps detecting root. If you have BusyBox installed, the App assumes that your device is rooted. Nothing more.

If you have MatLog or similar Apps installed, you can check the debug messages of the banking app. Mostly it reports its detection - > what kind of detection was found.

If you installed BusyBox via Magisk systemlessly it should not be detected. Some time ago I flashed MoroKernel, that is shipped with BusyBox. It was pretty annoying, because I was not able to remove it and instead use the Magisk version..
[Magisk] zgfg:
Uninstall your BusyBox app and install Magisk module Busybox NDK

As module, it will be automatically systemless and therfore not detected by RootBeer

Edit:

First two screenshots proving that BusyBox (Magisk module is installed), third screenshot showing how RootBeer is passing
[Magisk] ultrax1887:
Same Problem here since the Update of Sparkasse push tan App.

OnePlus 7t

---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------

Rootbeersample says:

Subinary Red

Su exists

root native
[Magisk] HippoMan:
I can install that NDK Busybox via Magisk, but does anyone know how I can uninstall my existing and long-standing installation of Busybox?

Every Busybox app that I have tried will not allow me to perform the uninstall (neither before nor after the NDK version installation) due to existing Busybox dependencies on my device.

Thank you very much.

.​
[Magisk] zputnyq:
Probably that busybox is built with your device kernel or rom (?). You have to remove it before you flash the kernel/rom.
[Magisk] HippoMan:
Hmm ... my ROM is stock OOS 10.3.2, and I'm sure that Busybox does not come with it.

Does rooting with Magisk install some sort of Busybox?

.​
[Magisk] Didgeridoohan:
No, it does not (there's an internal Busybox, but that is not exposed to the rest of the system).
[Magisk] HippoMan:
Thank you.

It turns out that the BusyBox Pro app on my device shows that BusyBox v1.31.1-osmOsis is installed in /system/xbin, irespective of whether or not I have the NDK BusyBox installed via Magisk.

Isn't that the NDK version?

But in any case, RootBeer Sample fails on my device. It tells me that it sees an "su" binary and some other items.

.​
[Magisk] zgfg:
First of all, make sure you hide Magisk from RootBeer by Msgisk Hide.

Similarly, you have to hide Magisk also from your banking app

---

Magisk Module BusyBox NDK is systemless. It means it is symlinked to e.g. /system/xbin only when Magisk is booted, its module is installed and enabled

It is symlinked dinamically by Magisk - that means its commands are not really copied/installed to /system/xbin, hence if you still have them there when the Busybox module is not enabled (or see them there from TWRP), then they are not there due to the Busybox Magisk module - then they came with ROM, were installed by some Busybox app or flashed by TWRP (in that case there must be a corresponding uninstaller to be also flashed by TWRP)

---

Uninstall Magisk Busybox module or disable it and reboot

Check by Playstore if it shows that you have some Busybox app installed and try to uninstall it, reboot

Otherwise, check by, e.g. App Inspector where the Busybox app is installed (?) and where are its data. If you really have such an app rename it from *.apk to e.g *.bak and reboot.

If all ok you can later remove it together with its data

Check by Root checker or Busybox checker where and which Busybox commands are (still) present, remove them and reboot.

Use MiXPlorer or some other root expolorer

Check again if Busybox is no more present

If all ok you can finally install Magisk module (systemless) Busybox
[Magisk] HippoMan:
Thank you!

Well, after uninstalling the NDK BusyBox, deleting my "BusyBox Pro" app, and hiding Magisk from RootBeer Sample, it stopped showing any "su", and the only thing it does show is "Root Management Apps". After reinstalling the NDK BusyBox, I get the same result.

Does anyone know of a way for me to get a list of these "Root Management Apps"?

.​
[Magisk] Wolfcity:
The Root Management App is the Magisk Manager itself.

If you hide it (repack it with a random name, found in settings) Rootbeer should be all green and root is hidden for most apps.

There are always some apps checking file or folder names like TWRP or Busybox or use different methods to check if a device is rooted, it's a cat and mouse game. But with the manager hidden you've got a good chance.

More info: https://didgeridoohan.com/magisk/MagiskHideMore
[Magisk] HippoMan:
Got it. Thank you!

---------- Post added at 21:26 ---------- Previous post was at 21:15 ----------

PS: ... but after renaming/repackaging Magisk, the resulting program doesn't run. I open it, and it just gives me a white screen.

The Magisk rooting functionality still seems to work, however.

This is on a OnePlus 7Pro (GM-1917) running OOS 10.3.2 (Android Q).

---------- Post added at 21:34 ---------- Previous post was at 21:26 ----------

Oh ... never mind. I did it incorrectly.

After renaming/repackaging the first time I tried, I immediately rebooted before trying to run the resulting app. I shouldn't have done that.

After restoring and trying again, this time I tried to open the newly renamed app, and it did indeed open, and it asked me if I wanted to download the full version of Magisk. After doing so, it is working fine under the new name.

... and RootBeer Sample now indeed shows "Not Rooted".

Success!

Thanks again!

.​
[Magisk] coolpixs4:
I need help...please

I want to run this script on boot for changing the read_ahead_kb for 'SDcard speed up'

I put it in root/data/adb/post-fs-data.d or /service.d

But it seem doesn't work

After reboot, I check in /sys/devices/virtual/bdi/179:0/read_ahead_kb, the value is still '128'

#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "512" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;

My ROM is miui9, it didn't support init.d, but I read somewhere that it can be run script on boot under magisk

My ROM have lastest Magisk 20.4

What can I do or change in script to run at boot ?

Thank you.
[Magisk] Didgeridoohan:
Did you change permissions on the file to make it executable? That is necessary.
[Magisk] coolpixs4:
Yes, It sets to 755

Is it correct to run ?
[Magisk] Didgeridoohan:
Are you sure that the script doesn't execute? If the command works when you're booted and run it manually, it could be that you just need to enter a delay so that everything has time to settle down before you try to change the value. Start with 60 seconds and then try different values depending on how the works.
[Magisk] coolpixs4:
yeap, after boot

I look into /sys/devices/virtual/bdi/179:0/read_ahead_kb

It still the original value '128'

So, does this code is correct ?

#!/system/bin/sh
#
sleep 60
#
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "512" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
[Magisk] Didgeridoohan:
That the value didn't change doesn't mean it didn't run.

Add a check for sys.boot_completed first. Don't run any code until it's set to 1.

And of course, put the script in service.d.
[Magisk] coolpixs4:
Could you do me a favor to modify this in order to compatible with Magisk 20.4 module?

Recently, It seems not compatible installation for Magisk 20.4 module structure.

This is a combination of some script to optimize RAM management which I want to execute after each reboot

Thank you in advance.
[Magisk] Didgeridoohan:
I'm not surprised that doesn't install. It's based on an ancient (relatively) module template.

Everything you need to port it over to a working installer is described in the Magisk docs, right here:

https://topjohnwu.github.io/Magisk/guides.html#magisk-module-installer
[Magisk] mvdi:
Thanks [MENTION=7786725]zgfg[/MENTION] and [MENTION=4667597]Didgeridoohan[/MENTION]. I uninstalled Busy Box using the busy box pro app, and then uninstalled that app. Cleared cache and data from the e-banking app, rebooted. Rootbeer reports "not rooted", due to Magisk hide.

Even when I uninstall the e-banking app, reboot and reinstall, add it to Magisk hide, it still crashes. Maybe it's not to do with root at all this time. I assumed so, because the same symptoms came with a previous version, which was due to root detection. The standard answer to the bad play store reviews is that they improved the security, so "the app no longer works on rooted smartphones". They suggested I call the customer help desk, but they're going to ask me if the phone is rooted!
[Magisk] Didgeridoohan:
Did you check the link I posted for you (if not I suggest you do)? There are many more things than just Magisk that might trigger apps looking for signs of a tampered device.
[Magisk] zgfg:
You can try to check with Logcat (eg Logcat 4U app from Playstore).

Clean the log, reproduce crash, stop the log and export.

Open as text (I always use MiXPlorer), search for the name of your banking app / it's package name (you can find it by AppInspector app also from Playstore), for fail or for exception words, maybe you get a clue why it crashes.

Maybe not root but something benign like permissions (check also for Permissions in Settings/Apps)
[Magisk] wrecklesswun:
GM. Having an issue where when i applied the audio patch for viper eq, now on boot i'm stuck at a scrolling status bar and and G. When i flash stock boot, i'm back to normal. Is there a way to back out and start from scratch? I suspect when i load the patched img, it is also trying to load the mod. It worked prior to trying to load Viper and the audio mod lib.
[Magisk] zgfg:
I think it was two times during the last week asked and discussed about bootloop caused by some module and the options to resolve.

So please for the beginning go through like last 50 posts (some obviously not related to), you will find instructions and try with options like disabling V4A module from TWRP or by ADB command at a boot time
[Magisk] wrecklesswun:
twrp is not an option for pixel 4xl. i do get to a point where i can use adb but still stuck at G with a scrolling line underneath. I uninstalled Magisk and reinstalled, and it appears to be blank.

i also tried ./adb wait-for-device shell magisk --remove-modules and that returned read (4 != 0) failed with 2: No such file or directory
[Magisk] hgarcez:
100
[Magisk] Didgeridoohan:
This is the second report of this error on a Pixel 4 XL in the past few days. Do you happen to be on the Android 11 DP?
[Magisk] wrecklesswun:
I am on Android 10. I have tried 11, although i am tempted to. I can boot using boot.img, but not the patched, and have no way to figure out how. I can get to the G, and adb shell works, i can see the sbin, but it says the files and folders are inaccessible.

---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------

read (4 != 0) failed with 2: No such file or directory

PS G:\Google Drive\Google Drive\Android\Pixel\4 XL\coral-qq2a.200405.005> .\adb.exe shell

coral:/ $ cd sbin

coral:/sbin $ magisk --remove-modules

No daemon is currently running!

1|coral:/sbin $ ./magisk --remove-modules

No daemon is currently running!

1|coral:/sbin $

---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------

read (4 != 0) failed with 2: No such file or directory

PS G:\Google Drive\Google Drive\Android\Pixel\4 XL\coral-qq2a.200405.005> .\adb.exe shell

coral:/ $ cd sbin

coral:/sbin $ magisk --remove-modules

No daemon is currently running!

1|coral:/sbin $ ./magisk --remove-modules

No daemon is currently running!

1|coral:/sbin $
[Magisk] Didgeridoohan:
What happens if you try to manually start the daemon with

magisk --daemon

and then running the remove command?
[Magisk] wrecklesswun:
No daemon is currently running!

---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------

1|coral:/sbin $ magisk --list

su

resetprop

magiskhide

coral:/sbin $

---------- Post added at 02:11 PM ---------- Previous post was at 02:11 PM ----------

1|coral:/sbin $ magisk --list

su

resetprop

magiskhide

coral:/sbin $

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------

1|coral:/sbin $ magisk --list

su

resetprop

magiskhide

coral:/sbin $