yashsingh1/xdaforums huggingface dataset:
[Magisk] billwoods:
Hello

Bit of help needed if possible, i have installed a custom Rom on my phone and have the latest Magisk 26.3 and manager running, i was looking to install the universal safetynet fix, i have zygisk activated but when looking to select the safetynet zip to install it is "greyed" out and im not able to select it

any ideas ?

Thanks

​
[Magisk] zgfg:
Set another file manager as default. The one you are using does not properly signalizes that you pointed to zip file (assuming you're really pointing to the correct zip file - make sure you didn't download source zip package from GitHub Assets)
[Magisk] billwoods:
Hi

Thanks for the response, after reading your reply i took another look through Magisk install i could see that it was not recognising it as a zip file, this is what confused me because Lsposed , smali etc where all selectable

Anyway, i renamed the file and deleted and readded the zip extension and it recognised it

all installed and running fine now so thanks..
[Magisk] zgfg:
Canary 26302
[Magisk] pndwal:
Latest Magisk Canary and Debug builds:​

Magisk (0352ea2c) (26302)​

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Diffs to v26.3​

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

👍 PW
[Magisk] pndwal:
Anyone using Riru?... Please say if it works with 26302... 😬 PW
[Magisk] aHcVolle:
I've tried to root my p8p running grapheneos (android 14) but i somehow failed. At first everything went fine (patching init_boot) but when enabling zygisk in magisk the phone will not completely boot anymore. All I can see is the message "pixel is starting" with a running bar below it forever.

I can recover when connecting to the phone via adb shell, switching to su (where i can see the su prompt on the phone) and run the command

magisk --sqlite "REPLACE INTO settings (key,value) VALUES('zygisk',0);"

I've tried running 26.3, 26301 as well as 26302 which all behave the same.

I've attached an adb logcat of the (not) booting device, maybe someone has a clue whats going on.

thanks
[Magisk] CobalTitan:
I just installed version 26302 on my S7 Edge to android 9 and the Play store and Samsung Theme continually crashes. I reverted to version 26301 and everything is stable now
[Magisk] pndwal:
Might be best to read/ask here:

https://xdaforums.com/t/october-14-...der-root-pixel-8-pro-husky-safetynet.4633839/

🤠 PW
[Magisk] pndwal:
Does that occur when all modules are disabled?... Do you use font module? 😬 PW
[Magisk] CobalTitan:
Yes all modules were deactivated before the update except Busybox
[Magisk] MeenaJiOfficial:
Android 11

Device - Redmi K20

Magisk - 26.3 (26300)
[Magisk] zgfg:
v1.9.1 and earlier versions (like v1.8.4 worked for you?
[Magisk] J.Michael:
To report to Magisk developer, you need to go to github. You will probably need to rerun with debug version of Magisk, generate log file from Magisk, whatever instructions are posted -- I wouldn't count on the fact that the program asked you to report the problem getting you a pass.
[Magisk] tooandrew:
is there any way to hide root reliably? my safetynet is passing but netflix wont work and usaa knows im rooted

on a redmagic 8s pro. with the 1.3 usnf mod and i attempted shamiko but it didnt help at all. denylist doesnt help. magisk delta canary is no better
[Magisk] sawdoctor:
No idea if this still works but I'd look here see if they can help

[Module] Netflix Enabler - Enable Netflix on rooted devices (Error 5.2 fix)

Background: In the Netflix app for some devices, error 5.2 occurs when a video is being played. I have found a way around this error for these devices, and I managed to make a Magisk module for it. It has nothing to do with Safety Net/Play Store...

xdaforums.com
[Magisk] teraßyte:
Is anyone able to use the Credem Bank app with Magisk/root?

LINK: https://play.google.com/store/apps/details?id=com.EuroMobiliareMobile

I've tried following several guides on how to hide root from it, but nothing has worked so far. 😔
[Magisk] tooandrew:
I used liboemcrypto disabler which, afaik is the same thing. Didn't help. Wondering if it's detecting unlocked bootloader. Hope not. My phone was happy to unlock with some coaxing but it doesn't acknowledge the flashing lock command at all
[Magisk] ssewk2x:
I had the same experience on my OnePlus 8T. Almost all system apps were crashing, including carrier services, play store, etc. Notifications weren't working, calls wouldn't work .. it basically broke everything. Some of the logs said something about an invalid or unsupported operation on a file descriptor. Reverting to the stable build fixed everything.
[Magisk] Regys:
Hi,

I'm having a problem with the latest update (26302). After installing the recommended boot, as usual, some applications no longer work.

Do you know why ?

Regards.
[Magisk] Peter0x44:
Hi all,

I recently tried to update magisk on my Samsung Galaxy S2 SGH-T989 to 26.3

I know this device is very old (almost 12 years), but I still like to keep it for fun

At first, I tried the "direct install" method, but it failed. I then used the "Select and Patch a file", and used the boot.img extracted from the zip of the rom I use

(LOS 14.1 from this thread, if it matters)

[UNOFFICIAL] LineageOS 14.1 | Celox [July 9, 2022]

BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3. I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a...

xdaforums.com

I rebooted to TWRP and flashed the patched file, but when I start the magisk app, I'm greeted with:

"Abnormal State"

"A "su" binary not from Magisk has been detected. Please remove any competing root solution and/or reinstall Magisk"

There is definitely no competing root solution - and I did try reinstalling magisk, it did not help.

The app still reports the correct version is installed (26300). Is this something worth being concerned about? Am I doing anything wrong?

Thanks for your time,
[Magisk] J.Michael:
Some ROMs changed from "boot.img" to "init_boot.img" as the file that needs to be patched.

When you run the LOS ROM without trying to inject Magisk, are you sure you don't have any root capability?
[Magisk] J.Michael:
You should say what Magisk you already had. And what you mean by "no longer work".
[Magisk] HippoMan:
Yes. And what phone do you have? And what OS is your phone is running?
[Magisk] Peter0x44:
@J.Michael I'm not sure I understand your question. Are you saying there are roms that are "rooted by default" or so? And maybe I have one of those?

If so - I'm pretty sure that is not the case. I did not have any root privileges to begin with, and I did need magisk to obtain them

The rom is LineageOS 14.1

right now, I do have the root privileges:

```

adb shell

celox:/ $ su

celox:/ # whoami

root

```

I didn't have to do any such renaming to install magisk before, and it does seem to be functioning correctly aside from the aforementioned prompt
[Magisk] J.Michael:
What renaming are you talking about?

Yes, there are ROMs that have "root" capability by default. Some have Magisk "installed" in what is delivered to you. Some have some other "root solution".

I thought that LOS specifically did *not* come with root capability, but you say you got a message that specifically declares that another root solution has been detected. I don't know what would cause that to happen. Maybe if you install Magisk to both boot partition and to recovery partition.

Can you say with certainty how many times you have flashed, and which partitions you flashed, when trying to install Magisk?
[Magisk] Peter0x44:
You mentioned something "init_boot.img", I assumed you meant to rename boot.img to init_boot.img, then patch and flash. I now realize there wasn't anything indicating you recommended that, and I didn't go through with it.

I can say with certainty I flashed twice. I can say with good confidence I flashed to boot, and not recovery. Wouldn't flashing to recovery overwrite my TWRP?

I did *not* have any such prompt when installing magisk prior, however, when I first did it, I had to use some version downloaded from github actions, since the release had some bug that would constantly prompt me to reboot after flashing the patched boot.img. I have a vague memory of successfully updating since, so I don't think it should still matter. That's all I can think of that may affect it.

Hope this helps.
[Magisk] pndwal:
That's only for devices launched with A13+... (As part of Treble/Mainline generic ramdisk is moved out of boot.img to init_boot.img for GKI compliance.)

Because Magisk was misidentifying devices / erroneously detecting from 26105 and regression wasn't fixed untill Fix device detection scripts and logic and Always check mounts to detect legacy SAR on bootmode in 26202, your device may have be one of the older devices erroneously showing "Recovery mode" if you used these Canary builds or previously updated to 26.2 (26200)... If you took Direct Install and hadn't unchecked Recovery mode beforehand, you will have patched Magisk to/recovery partition ramdisk. This is only meant for A only legacy SAR devices that lack any ramdisk in /boot (ie. Recovery=No) and these must boot to system with root via recovery using special key combo with early release timing... And yes, TWRP recovery can also be patched this way; normal key combo will still land you in recovery... This device ID issue is of course fixed in 26.3+.

That could explain 'conflicting root' though I hadn't heard of the message before... To fix in this case, just flash TWRP again...

🤠 PW
[Magisk] Peter0x44:
@pndwal I tried flashing my twrp and it didn't solve it, the message is still there.

I didn't try using the newer magisk though. Could you clarify which steps I should take exactly? Do I need to install a newer magisk, flash it, then flash the twrp again?
[Magisk] pndwal:
If you've flashed clean TWRP there's now certainly no Magiskinit in Recovery ramdisk... Not sure why Magisk is seeing conflicting SU binary... Does suggest you have pre-rooted ROM which is possible as it's unofficial LOS... Saw no mention of that in the port thread however... Might be worth checking the source... If SuperSU you may be able to install SuperSU manager and remove root using it's menu... Some ROMs with integrated root can be cleaned, some can't...

Others may have more. 👍 PW
[Magisk] J.Michael:
Check again to be sure that you do not have more than one Magisk manager app installed. Go through your app drawer and check the info on any app with a plausible name. Find an app with a name like TBChecker -- it can supposedly detect hidden Magisk managers.

Go to the thread associated with your ROM and ask somebody whether the ROM is already "rooted".

As for "init_boot": Look in your ROM (zip, payload, whatever format it comes in). If the ROM as delivered to you does not contain a file "init_boot.img", then all the talk about init_boot does not apply to you.
[Magisk] AnnetkoO:
Good afternoon, I have Xiaomi 12T pro, custom ROM Xperience on Android 13. There is such a game - Eversoul (from Google play). So, I’m already tormented with it, since error 00004000 has already overcome me. Since I haven't tried anything in magisk, I know that after hiding magisk, the game starts WITHOUT this error. But all subsequent launches this error always appears! What I did was turn off zygisk, install shamiko, and the DenyList toggle switch was in the on position, but not active. It did not help . In DenyList, I checked this game with ticks and sub-ticks - plus Google play services, Carrier Services, Google Play Games, I tried that too. And it didn't help. And, in principle, I tried different combinations - turning off / on zygisk / DenyList / setting ZygiskOnKernelSU (module). I also have the UniversalSafetyFix and Zygisk -LSposed modules. On reddit I found all possible solutions, such as changing the language on the smartphone to English, launching the game via WI Fi, turned off usb debaggin ( such variants found on reddit) but this did not help. They also suggested that I remove magisk. To which I replied that I would rather delete the game. Help me overcome this error! I don't believe that nothing can be done!!!
[Magisk] pndwal:
Many factors/detections may be involved here, but basics are to hide traces of root and pass Play Integrity DEVICEINTEGRITY verdict which many apps now poll... Nb. SafetyNet API is deprecated... You haven't mentioned if you use a fix for DEVICEINTEGRITY... Official USNF module remains broken... You should use @Displax's USNF fork, 2.4.0 mod 1.3 build (avoid 2.0) or a @chiteroman PIF build. Nb if you choose the latter you will need to research the best build as he's experimenting a lot lately...

If your Xperience ROM integrates a SafetyNet/Play Integrity fix the PIF can work better especially if 'strange' spoofing has been employed as with XiaomiEU etc... Also, if SNF etc is integrated and it works, ie. is current (check using Play Integrity API Checker etc), before Magisk is installed, with Magisk you should be able to pass DEVICEINTEGRITY again simply by adding GMS Droidguard/attestation and main (ie. Google Play Services com.google.android.gms.unstable and com.google.android.gms) processes to denylist... No USNF fork solution is needed... Nb. Denylist requires Zygisk enabled and so does Shamiko hiding... Nb. 2. Don't add anything Google in denylist if using a USNF fork solution other than G Pay/Wallet...

You may need more than this of course, but may be enough... 🤠 PW
[Magisk] AnnetkoO:
In general, I installed @Displax's USNF fork, 2.4.0 mod 1.3 build, checked through the Integrity checker - meets device and meets checker are green, and meets strong is red (I don’t know if this has an effect), but this did not help and the game still started with the same error. In addition, I forgot to say that I uninstalled Magisk and installed Magisk delta in the hope that I would conjure something in it. But of course nothing worked out for me. And I uninstalled Magisk Delta and installed the official magisk again. So here it is. I went into the settings and saw that Google processes were not hidden in my DenyList (since naturally I first tried to revive the game WITHOUT them at all). I first hid gms (Google play services), Google play, Carrier Services and launched the game and the error did NOT come out!!!!!!! But when you restart the game, this error appears again! I already wrote above that the same thing happens after hiding magisk - I hid magisk, launched the game and everything is fine! But as soon as you exit the game, restart it, the error is right there again. I did all the manipulations above many times, then I gave up for a while and now again I’m trying to somehow solve the problem... I just don’t have enough anger. I don’t know where to dig anymore so that this damn error doesn’t keep popping up. By the way, thanks for the answers. And yes, I was on xiaomi.eu until custom firmware for my device finally began to come out. I thought maybe the situation would change with custom firmware. But no :(. Thanks for the answers.
[Magisk] xerel89:
I can not flash the module on xdroidOSS rom on my Redmi note 12
[Magisk] iruiz2:
Did you try HMA? Or checking your status with the Ruru app?
[Magisk] hans henrik:
EDIT: Fixed (by using Odin instead of Heimdall)

trying to root a Samsung S22 Ultra, using the guide at https://topjohnwu.github.io/Magisk/install.html#samsung-devices

Stuck on the step

>Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP

it claims AP does not exist, any idea what I can do?

```

heimdall.exe flash --AP ..\SM-S908B_BTE\wtf.patched.tar.md5 --no-reboot

Press any key to continue . . .

Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna

Glass Echidna

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

Donate | Glass Echidna

Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

PIT file download successful.

ERROR: Partition "AP" does not exist in the specified PIT.

Ending session...

Releasing device interface...

```
[Magisk] J.Michael:
AP is not a partition. AP<lots of crap>.tar is the name of one of the standard tar files of which a Samsung ROM is comprised.

If you used Odin, there would be a "slot", i.e., a text input field, labelled "AP". That's where you would identify the file you want used.

If you have used Heimdall before, you should already know that you have to unpack the various tar files provided by Samsung and specify each to tell Heimdall to use it. I have never used Heimdall.

John Wu's original instructions advise against flashing too little at once. For the purpose of installing Magisk, he advises to at least always flash boot, recovery, and vbmeta in the "AP" slot of Odin.

Have you ever used Heimdall before? Have you used Heimdall to flash the entire ROM you are using?

I believe it is a bad idea to download a ROM and just assume that it matches what is already on the device, and that it is safe to just flash a few, patched, images. I would always start by flashing the entire ROM to make sure it seems to work, before trying to patch it.

But, as @pndwal says, brumbies go where angels fear to tread.
[Magisk] pndwal:
Are you able to clean flash your ROM only using the same method, ie:

> Reboot to download mode. Open Odin on your PC, and flash original AP .tar file together with original BL, CP, and CSC (NOT HOME_CSC because we want to wipe data)?...

If not I suspect there's something wrong with your PC or Odin driver setup... 🤠 PW
[Magisk] pndwal:
Was I sleep-talking?! PW
[Magisk] Regys:
Pixel 5, Android 14.

Problem Update > Direct Install (Recommended)

lawnchair, microsoft keyboard, garmin connect, some others. don't work ?
[Magisk] J.Michael:
But what does "don't work" mean?

A common claim is "MyBank app detects root." Usually this is "MyBank app says device not safe." Sometimes this is "MyBank app doesn't open."

I don't recognize most of the apps you name. I don't remember anyone ever reporting that a keyboard app refused to run on a modified device.

Do your problems go away if you uninstall Magisk?

Have you checked github to see if anyone else is having this problem with this version of Magisk?

You still haven't said what version of Magisk you had.
[Magisk] Regys:
I do what I always do when there's a Magisk update.

Update Magisk > Update Boot.img.

But after reboot, some apps don't work.
[Magisk] hans henrik:
@pndwal

Idk, but switching from Heimdal to Odin fixed the issue, it's rooted now :)

There was actually a 2nd issue, my cable was dodgy, got like 3 flash errors and it soft-bricked, but got lucky 4th time.

@J.Michael

No, never used Heimdall before. I did not download a random ROM, I specifically downloaded the one from http://fota-cloud-dn.ospserver.net/firmware/BTE/SM-S908B/version.xml because BTE is close to where the phone was originally sold, and there is currently an unknown issue with downloading the original EUX-region firmware: https://github.com/zacharee/SamloaderKotlin/issues/111

Luckily the BTE ROM worked fine :D Also I wrote a region-scanner to find SM-S908B firmware regions: https://github.com/jesec/SamFirm.NET/issues/3 (because downloading EUX region firmware is broken)
[Magisk] J.Michael:
What version of Magisk was working for you?

What is "don't work"?
[Magisk] zgfg:
Hunter
[Magisk] Regys:
the last

lawnchair, garmin connect, microsoft swiftkey...
[Magisk] J.Michael:
Any chance you could force yourself to reproduce the numerical version number of the version of Magisk that was working for you?

I have been trying to get you to describe the way in which some apps don't work. I am done trying to tease this information out of you.
[Magisk] m0han:
I feel for you. (y)
[Magisk] AnnetkoO:
This is the first time I've heard about this. Can you please provide more details or provide links to study :)
[Magisk] SonOfTheRain:
Hi,

I am using MI11T Pro with MIUI 14.0.1.0 stable from xiaomi.eu. Magisk Alpha 26302 with Zygisk + Shamiko. I configured my denylist but still I am unable to get Absher and banking apps (Saudi Arabia) passing root check. Is there any working configuration for them?
[Magisk] zgfg:
I can give you my hand that HMA=Hide My Apps LSPosed module has been mentioned/suggested to use/even answered more about at least tens of times in this thread😁

Also, about testing with ruru, including Link to download or attachement, or hint to search for download

So please try to search and/or take some time to read

Also google for eg:

XDA Hides My Applist

to get a link to the thread about. And read there OP post #1, follow there the link to Instructions
[Magisk] zoozo25:
Good job my freind
[Magisk] AnnetkoO:
Hello! First of all, I want to thank you so much for telling me about the HMA application. I installed it, as well as ApplistDetecter, and hid the Eversoul game in it. I launched the game twice - via Wi-Fi and via LTE and both times there was no error!!! Hooray! I hope it continues like this! Thank you very much, how could I not know about this wonderful application until now?! I still have one question left - what is RURU? I Googled and searched here too, but I couldn’t find it damn it))) Maybe you meant RiRu?)
[Magisk] iruiz2:
I'm glad you worked it out. Yes, HMA is fantastic. As for Ruru, here's the github: https://github.com/byxiaorun/Ruru/releases