yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
I don't doubt that the R.I.P. comment was a nostalgic reference, but I don't think it was a comment on or promotion of detection by MagiskDetector or other! 🤪

MagiskDetector release is cleary only due to it sharing code used in Momo and the 'momo' methods made public relating specifically to MagiskDetector...

The R.I.P. comment came immediately after the latest Alpha release with the release note

and the remark

In this context it's obviously just an expected and logical update to these previous notes about pending removal of MagiskHide in Alpha specifically:

😅 PW
[Magisk] zgfg:
Regarding to:

> According to telemetry data, the number of zygisk users has reached 78.3%, and after more than 85%, alpha will remove magiskhide

Btw, I'm not sure if I ever read they really reached that 85% target (they were slowly approaching 80%), but now it's not important
[Magisk] pndwal:
I'm guessing we can safely assume that this announcement means they've reached 85%... 😜 PW
[Magisk] ipdev:
I am just confused. 🙃

More "What The ???"​

___

- Did you patch the recovery image with Magisk.

- Replace the recovery image with the Magisk patched version and boot into system from Recovery

or..

Did you you use recovery to install Magisk (patch the boot image)?

I have only had a 7T for a few weeks.

Since OnePlus has switched their release/updates to OTA only, it took me a little while to find a boot image.

Once I found it, I patched it with Magisk and ...​

Currently my (new-to-me) 7T is on the a12 beta.

I was testing the fingerprint scanner.​

I was planning on restoring to stable/stock OOS this weekend.

If you are running a custom ROM or kernel, let me know.

I am willing to test. 🙂

___

OnePlus 7T partitions.

Spoiler content hidden.

Cheers. :cowboy:
[Magisk] pndwal:
(Edit: Offending remark has been removed by a moderator...)

Why do you continue this theme... I never read where John Wu said it either; just hearsay...

I don't need to keep hearing such remarks about anyone helping with Magisk etc, but confess I prefer polite company... And this is impolite (at best) at least among English speakers... 🙄 PW
[Magisk] pndwal:
Thanks for that... Confims that I just might be on the money... 😅 PW
[Magisk] Stillhard:
I don't know why i can't?

You brought it here in Official - Magisk General Support Discussion, you could just bring it in it's own thread, but you can, so why i can't?
[Magisk] pndwal:
I did not.

I have never furthered this

(Edit: Offending remark has been removed by a moderator...)

theme here, nor have I been one to take it to any other thread... And, to be quite clear, I'm referring to your self evident sexual suggestions, not some unstated link to things Alpha or any other Magisk related issues...

Sorry to spell it out, but you haven't gotten the (none too subtle) hint! 😜😛 PW
[Magisk] maakosan:
The first thing you said..
[Magisk] Tech = Spy-Biz:
TJW did a great job, I can't possibly read 2648 pages of this thread, I have used older magisk versions before but now with 24.2 loaded the bank apps detect root. I'm using samsung device with android 11, I've enabled zygisk , changed the magisk app name, added all the bank app processes to denylist, rebooted. My ROM shows Software Status: Official even though bootloader unlocked & twrp installed. Can anyone tell me which exact version of magisk might hide root from bank apps? TIA
[Magisk] meric57:
Hello, I agree with Tech = Spy-Biz I propose that each concern be listed in an ad as a pos-it.

Example concern with bank metering the solution concern for updating metering the solution thus immediately, it will avoid overwork to seek the solution in 2648 pages

I'm off topic these for ease and avoid searches
[Magisk] zgfg:
By the way, there is another thread with detailed OP instructions for the new Magisk v24/v25:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

And a thread that was opened for hiding root with the new Magisk:

https://xdaforums.com/t/discussion-how-to-bypass-detections-of-rooting.4426615/

Those new threads were opened because of this old and cluttered thread.

Unfortunately, people still report/ask here (and in parallel complain that thread is too big to read☹️)
[Magisk] pndwal:
Thanks for that... Confims that I just might be am on the money!... 😂

To be honest, I've thought about running dual Magisk iterations this way, but yours is the first case I've seen... And you did it by accident! 😅 ... Well done...

Clearly you need to flash unpatched recovery again to remove (old) Magisk in recovery partition... This configuration was never meant for your device anyway...

So we just need to figure out issue with mobile network in Magisk (25.2) in boot partition to fully solve the puzzle...

I'd flash the stock recovery, then try reboots to see if Magisk 25.2 in boot partition is fixed (ie. Magisk with working Zygisk and mobile network)... Previously such reboots were apparently sabotaged by Magisk in recovery partition booting system with different root binaries...

I have my doubts that this will solve the network issue; I suspect you have also mixed up boot images and may have flashed a patched one from an earlier or different ROM (eg using the same image you had before taking an OTA update = mismatched boot image)... maybe you didn't download properly matching ROM (version must be a perfect match with running version as in Settings, About device).

Mismatched boot images are the most common cause of issues like yours w/ Magisk. These will often allow system to boot, but generally with comms (sim, wifi, bt) and many other issues...

Exact matches are needed because the kernel also resides in the boot image and this gets much attention from devs ... System changes often have corresponding changes in kernel (ie. in boot) with any OTA to accommodate many 'handshakes' made between system and kernel. See: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86520073

Anyway, fix your recovery partition(s) and try the reboots first... 🙂 PW
[Magisk] AndroLinx:
Hi there,

I would like to root a Galaxy Tab S6 lite Wifi running on LineageOS 19.1 using Magisk 25.2.

The installation instructions I found on rooting suggest to download and patch an original Samsung firmware.

Question is whether this really applies if one runs a custom rom like LineageOS or if I should rather patch the lineageOS boot.img?

Thanks in advance for any hints!
[Magisk] henningsieh:
You should exactly do this. 👍
[Magisk] AndroLinx:
Thank you ! :) Do you per chance know if I have to follow some additional / special steps when doing this or if I can just follow the steps outlined by John Wu on his page https://topjohnwu.github.io/Magisk/install.html ?
[Magisk] henningsieh:
Sorry I have no experiences with Samsung or LOS.

Rooting a Samsung is special in many cases, you should do a research in the device and LOS specific threads for solid infos on this.
[Magisk] AndroLinx:
No worries! I will have to dig into it some more then. Thanks a lot for your fast replies! :)
[Magisk] Franzyy:
I have a issue in magisk where i cant activate mobile data and make calls anymore, it also says no imei, please fix it in the next update. I use the A32 (a325f) where i flashed magisk through boot.img

More about this here:

https://xdaforums.com/t/fixed-rooted-a325m-suddenly-no-imei-no-sim.4386753/page-4
[Magisk] zgfg:
Who will fix it?!

Developer(s) don't read this thread

To report issues, you need to go to Magisk GitHub 🤣
[Magisk] pndwal:
So this known stale issue?:

https://github.com/topjohnwu/Magisk/issues/1801

I guess you found workaround(s) linked from that issue...

Assuming you are trying w/ latest Magisk it seems you need that for now... PW
[Magisk] ipdev:
@AndroLinx

A page or two back, I posted how I recently did it with an older Samsung tablet.

Post # 52,872

Not sure if it will work for you but, at least it is some reference.

Cheers. :cowboy:
[Magisk] andrew2432:
I had root, a few apps still recognize it, updating to the newest magisk manager shows n/a for magisk installed. Do I just grab my boot IMG out of my ROM and do it sgain? Will I keep all my data and info...?
[Magisk] pndwal:
Did you have Magisk App hidden when updated?... Classic trap... Supposed to work, but bit like a pot-luck dinner...

You're probably suffering from DACFRAS*, which is NOT fatal but all the clinics are full...

Check in device settings, Apps for your old hidden App... Default name is 'settings', or its what you named it... Uninstall it, and presto!

*Dual Apps Competing For Root Access Syndrome...

😜 PW
[Magisk] m0han:
Experienced this issue on a fork of Magisk too. https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-87255925
[Magisk] pndwal:
It's a general rule: take chances (w/ awareness of issue/remedy) or take Restore the Magisk app before updating App... My success estimate is reducing... 50/100 --> 40/100 --> 30/100 (?).

It's all TJW/vv2060 code, so irrespective of fork... PW
[Magisk] andrew2432:
Alright so I looked a bit and had very little luck and gave up. Then I opened terminal emulator for some unrelated activity, ran su, and "device manager" stopped working. Gonna see what happens when I uninstall that...

Worked lol shows which version is installed access to superuser tab and modules tab active haha
[Magisk] huskydg:
Maybe problem with github server
[Magisk] zgfg:
Very simple (and you don't need Terninal, su, etc):

- look into your Drawer and/or Settings/Apps and find your old hidden/renamed Magisk app

- when you did in the past *Hide Magisk app" you were given a chance to rename it.. Hence you should know what name you gave it (default name is Setting)

Find that app and uninstall, and reboot. You may additionally need to reinstall the new Magisk app

If you look into this thread you will literally find hundredth of such posts and answers. Hence nothing new - before installing/updating the new Magisk app, one MUST open the OLD hidden (if he did hide it) and do "Restore Magisk app"

Otherwise, when you install the new Magisk app, you will have a clash - new Magisk app does not see Magisk (because the old/hidden Magisk app is connected to Magisk)

Unfortunately,v I also don't know why TJW does not acknowledge this problem and if they could not fix it, AT LEAST to make a note into the Installation instructions (I know, nobody would read☹️) and a warning into the Changelog

Of course, he does not read this thread and he doesn't care about all the users experiencing the same problem (99% of them are not on the level to have GitHub account and to report there, and they don't bother him to his lovely Twitter🤣)
[Magisk] m0han:
i guess you're aware about that fork not requiring 'hide/rename/restore the app before updating'... so, maybe this: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87272599
[Magisk] pndwal:
Ah yes, certainly... I see you didn't hide...

Sorry, I assumed issue / quick reply/ didn't check link. 🙁; My bad... (I was up on scaffolding in sun too 🤪)

To be clear, Installed=N/A w/ root is not only a symptom of competing apps after updating with Magisk App hidden, but this is probably the most common cause.

You'll see this from time to time in GitHub issues too with various causes. Not long ago a whole raft of Samsung models faced this, then various devices running custom ROMs w/ Android 6 & 7; regression fixes were found for these...

My approach with this is always to ask 'did you have Magisk hidden when updated?'... And give advice to check 'if so' before looking elsewhere... 🙃 PW
[Magisk] pndwal:
Done... PW
[Magisk] V0latyle:
Honestly we are almost at the point where we should move these discussions into a standalone thread specifically for Play Integrity.
[Magisk] 73sydney:
Meanwhile for users of HideMyAppList, from that place we can sometimes mention and link to comes this news:

Guys long time no see.

The 3.0 version of HMA is under development and will be released soon.

In the new version, we solved a lot of problems existing in the 2.x.

1. Remove the Magisk extension, and introduce a new way (Xposed only) to prevent apps from using file detection to scan /data/data and Android/data (Unfortunately it might only support Android 11+), which does not inject code into app process to prevent detection.

2. UI redesign with full Material You and better interactive logic. Also there will be night mode fix.

3. Introduce a new effective way to implement hide on high version Android.

We reestablished the discussion group, but the verification bot is not well written yet, so the public link will not be visible now.
[Magisk] zgfg:
Released - you have APK?
[Magisk] 73sydney:
Nah, as it says, it will be released soon, i was just giving folks, and you especially a heads up :)

Personally i abandoned it (it had *nothing to do* with that time i removed lsposed but forgot to uninstall the magisk module portion of HMA and bootlooped myself :) :) ) for updatelocker some time ago, as it does all i was really using HMA for.

But with the talk the new HMA will drop the magisk module, i might give it another go :)
[Magisk] martyfender:
I've also done the same thing, more than once and had bootloops, also.
[Magisk] Stillhard:
Here
[Magisk] 73sydney:
im in a post-guinea pig phase at the moment, imma wait for official release :)
[Magisk] Tech = Spy-Biz:
My bank app has 370 services inside the apk, one of the services is named "Detect Root" and this service does a great job at sniffing out open bootloaders and magisk-hide i see. So if I don't find a soulution somewhere then soon the only option going forward would be Net-Banking through phone browser instead of Phone-Banking through bank apps. Infact the bank app pops up an error message stating "Since you have a jailbroken/rooted device you can try Net-Banking instead or restore factory settings".

Lol SMH.
[Magisk] ipdev:
Seems to be device/rom related. :unsure:

In the last year..

I had one issue updating Magisk while hidden (renamed) on a few devices that I still have it hidden. 🙂

Renamed the Magisk app for some reason (probably testing something) and just left it hidden since.

The one issue I had (do not remember the device)..

I think it was the switch in Magisk patching and not so much the hidden (renamed) app.

From a prior post

Spoiler content hidden.

No one will read it but.. :unsure:

We can link users to it though. 😛

Anyone willing to take (have) the time to write up and submit an update to the official Magisk installation instructions.

Magisk Installation - [GitHub] - Improve this page.

Spoiler content hidden.

I do not have the time to write up a proper edit.

Maybe next month..?

Unless you, pndwal or someone else writes it up.

Cheers. :cowboy:
[Magisk] pndwal:
May be device thing... Very common on my Xiaomi RN8T and Mi Pad 4...

I thought much the same re. GitHub issue... Hope someone else does... (I think a few tried and got nowhere)...

I've made a couple of relavent issues for the good of others now that have just been closed with little or no comment or, worse, locked for commentiy by me or others...

Spoiler content hidden.

Bit disheartened by that... Seems workaround is XDA members putting word out here... 🙃 PW
[Magisk] huskydg:
Too long, can't read
[Magisk] pndwal:
Why post it all again then? 😜...

Post I replied to was nearly as long, but I didn't use spoiler tags... I'll learn and put them in... Just for you! 😛 PW
[Magisk] evil-google:
Hi, I am having this strange problem with my sdcard which I suspect is related Magisk and would appreciate if someone can give me some pointers to resolve it.

I was running LineageOS 18.1 with OrangeFox recovery. I used the Magisk module in OrgangeFox recovery to root the system. Recently I noticed that OrangeFox modules were missing and tried to re-install it. This did not go down very well and I was unable to boot to recovery.

Then I tried Twrp and was able to boot to recovery. However, when I booted the system was I could not get pass mounting of SD card. The system says SD Card is missing and goes back reboot and mount the SD card. I then removed the SD card and the system booted perfectly OK. Then re-inserted the SD card and formatted to internal storage (which is what I had earlier). The formatting process goes up to 40% and the system automatically reboots. Tried ths process many time without any luck. However, if I format the SD card as external storage it all goes well. Tried with another SD card to eliminate the possibility of having a faulty SD card but the the outcome was the same.

I checked out the file structure using Twrp file manager and I noted that the internal storage folder names appear to be encrypted - folder names appear as just a random string of characters.

I re-installed Magisk and uninstalled it from the app (which did not report any errors) but my SD card issue still remains.

I would greatly appreciate if anyone can come up with some suggestions.

Many thanks.
[Magisk] zgfg:
Internal storage files and folders are encrypted by use of FBE (File Based Encryption).

You need to be asked for your Android unlock pin/pass/pattern when starting TWRP and only when you enter, TWRP will be able to decrypt file (and folder) names (and content)
[Magisk] evil-google:
Hi, thanks for the prompt response. In my case TWRP does not ask me to enter any unlock pin or password. The issue seems to be when formatting the SD card as internal storage the process stops at 40% and reboots - I do not think this is normal but I may be wrong. However, since the system is already rooted using Magisk shouldn't these folders be unencrypted? Not particularly concerned about not being able to read the folder names on TWRP but not being able to use the SD card as internal storage is the main issue.
[Magisk] Tech = Spy-Biz:
I think I had faced the same issue before but I don't remember exactly what I did to get sdcard as internal...I think I either placed the sdcard then rebooted to twrp/ofox then change file system to ext2 then back to ext4 or I had formatted to ExFat using DOS then placed sdcard in and rebooted to system then the format goes from 40% to done. OR maybe I had flashed decryption.zip, but something had made it work.

(excuse off-topic i think)
[Magisk] samhhmobil:
Offtopic here (it's NOT a magisk issue):

LineageOS is well known to be completely unreliable with SDcards as "internal storage". (It's many times written in this Forum — not in this thread.)

DON'T USE THAT!!

Someone sometimes should have been lucky with that I was told, but in most cases it does not work and destroys at least your file structure.

Moreover I have destroyed physically several SDcards when I was trying to establish/format a SDcard as internal storage with LineageOS. NEVER AGAIN.

Again: DON'T DO THAT, when using LineageOS.

Instead of that: format your SDcard as external storage, and use the Magisk-module "fbind" to mount it into the necessary directories inside your internal storage.

That works flawlessly, but the setup is somewhat tricky. Documentation exists.

Just my 2¢,

samhhmobil
[Magisk] zgfg:
Magisk has nothing to do with File Based Encryption on Data and Storage.

That's part of the File System definition - Magisk does not redefine File Systems.

And when running Android, kernel takes care of FBE

Btw, why would you (and some other users who maybe first time face FBE) dislike FBE (or be afraid of, or what) and want instead your files to be permanently unencrypted?!

If you have a proper custom Recovery, it will ask for your pin/pattern and by use of that pin, it will then unencrypt file by file, on demand - just like Android does when you boot to Android

Then, if your phone is stolen and the thief-hacker reboots to TWRP, he will not be able to steal your documents, phoos, etc, since (s)he does not know your Android unlock pin/pattern (and therefore TWRP cannot decrypt him your files - he can copy the encrypted files to PC but they will be of no use for him)

However, without encryption, if your phone (with the TWRP installed) gets stolen, thief can simply boot to TWRP and copy all your personal files to PC.

He can then open and read your documents, see your private photos, etc

---

The official Google FBE documentation is available at:

File-Based Encryption | Android Open Source Project

source.android.com

---

And one important tip:

When installing custom ROM, usually you have to FORMAT Data (not just Wipe) that your new ROM could properly reformat FBE for itself - only then things will work as described (TWRP and FBE)

But all that is out-of-topic for our Magisk thread

Developers of custom ROMs should provide clear instructions how to properly install their ROMs - and their users of custom should take time to read instructions before flashing👍

---

You can go to /vendor/etc/ (aka /system/vendor/etc one has to be mounted to the other in Android)

and find a file fstab.* (on my phone it is named fstab.emmc).

That's the read-only, textual file

Inside, search for /userdata (filesystem definition).

On my phone it looks like:

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs

Actually, inside that line look for the fileencryption definition - in my case:

fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0

Flag :v2 means that I have FBE v2. It's also emmc_optimized with hardware-wrapped keys (details and description can be found in the Google's FBE documentation as linked above)
[Magisk] evil-google:
Hi, thanks very much for the suggestions. I tried reformating with TWRP and then wiped out everything using kdepartition manager (left unformatted) but none of them worked. Where can I find 'decryption.zip'?
[Magisk] evil-google:
I doubt it is a LOS problem - more likely an operator error! I flashed crdroid and ended up having exactly the same result.

Thanks very much for your warning about destroying the SD card - in fact, I was concerned about repeated formatting/reinserting the SD card.

Will try out using fbind module as you suggested - thanks.

EDIT: I could not locate the Magisk module fbind in the repo - appreciate if you can suggest where I could download it from. Thanks.
[Magisk] evil-google:
It is not just that I do not like FBE - just trying to see why I cannot use the SD card as internal storage.:)

In my case, /vendor has no etc directory. It has lib64 and firmware folders and two xml files, manifest and compatibility-matrix.

I will post this issue on LOS see whether anyone has any further suggestions. Many thanks.
[Magisk] adfree:
Thank you very much for Magisk and all cool infos and Modules etc... for Rooting.

I can use my Galaxy Watch 4...

SM-R870

I was able to root with help of Magisk Version:

24.3

At the moment only tested Version:

EVA8

And just for fun tested patched Kernel (boot.img) from:

FVD4

Mixed with EVA8 Firmware...

Reason only EVA8 complete leak for Odin use...

And my FOTA is now broken... so at the moment no chance to use update.zip for me... to reach higher Firmware Version...

Rooting process require at the moment USB wires...

"We" are not able to bypass Security with netOdin only...

Wireless update mechanism check something in boot.img "Footer"...

USB cable and Odin ignores Security check...

Only as info. :cowboy:

Best Regards
[Magisk] pndwal:
Redmi Note 7?

I may have missed your usage scenario, but why not format SD card for official Adopted Storage? (Will be encrypted and just work with encryption keys stored in /data/misc/vold)

I used to use link2sd, then switched to apps2sd on old devices with very limited storage, then moved to Adopted SD storage when proper Android support came w/ A6 Marshmallow... Was a bit flakey then (config issues/anomalies), but worked flawlessly from A7 Nought... 😛 PW