yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Did you patch AP using 27.0 App after updating that on this device, then flash that + other binaries using ODIN?... Sounds like you only flashed previously patched (using 26.1) AP + other Sammy binaries. 😬

Also, are you ensuring Recovery Mode is checked (selected) when doing Direct install or patching AP??... Not doing so will patch boot image within AP, but you need to patch recovery image...

And did you reboot via system via Magisk app reboot menu?... Only Magisk reboot menu may work to properly boot to system via recovery depending on device... And you may still need to fully shut down and boot via recovery with key combo (foolproof method) anyway...

Further, taking Direct Install (even once) while Recovery mode is not checked may be the cause of your bootloops (due to erroneously patching boot image), and you may then need to fix by flashing original or properly patched (with Recovery Mode checked) AP etc...

🙃 PW
[Magisk] pndwal:
Interesting LSPosed Devs working behind the scenes... They've got LSPOSED running in Android on Risc-V linux development board!

... And now this support for Magisk (in Metagisk test branch):

Preliminary support for riscv64...​

• It does not actually enable building on riscv64, but some fixes for riscv64 if we actually build on it.

Where's this coming from/going?:

https://opensource.googleblog.com/2023/10/android-and-risc-v-what-you-need-to-know.html

👀 PW
[Magisk] Thisisrdn101:
Confirmed stable after 2 days of using moar 2.1b on sprint note 4! Fresh moar install with the xtrememusic mod in the aroma installer. Used the pj1 baseband with the ael 9.3 kernel. It also worked with the ok1 Stock boot.img. I was curious with ael and it ended up not bootlooping so I ran with it. I unrooted supersu, flashed Magisk v9 with phh superuser r266-2. Then I installed magisk manager and Xposed installer. installed phh superuser via Google play. Flashed Xposed systemless 86.6. Booted fine and so I updated the newest adaway with systemless hosts support. Did not test Android pay nor safetynet . I am wondering if it's possible to push maxxaudio, viper, and dolby atmos that came with moar 2.1b into systemless without compromising a new audio setup?
[Magisk] yochananmarqos:
First of all, your almost nonsensical run-on sentence hurt my brain.

To answer your question: No. Complex audio mods will not work. Take a peek inside the mod ZIP's, read the install script and see how many files are modified and overwritten.

However, feel free to create your own Magisk module using the provided templates. Let us know if it works.
[Magisk] SimplyCity:
Oh! I am very excited to hear that. One little ask for you kind sir: would you share a single one module of yours which pushes any app to priv-app and actually works? Which is not so specific that could work on any device with magisk v9... That would be great. Much appreciated. Thanks in advance.
[Magisk] dimm0k:
thank you, it wasn't until after reading this post that it hit me that the root folder was not what was in the zip file, but in a directory named after the name of the zip. unfortunately there's still problems after correcting this and that is it is now saying"installation failed". any suggestions there? I've attached two flash files that I see this with
[Magisk] TotallyAnxious:
I rezipped with zero compression for my module, yours are compressed. Only thing I can think of.
[Magisk] SilverSix:
I did that then lost Xposed. Once I reflashed Systemless Xposed 86.6 I lost root again.
[Magisk] Thisisrdn101:
Definitely will do [MENTION=5124760]yochananmarqos[/MENTION]!! My bad, definitely had tons of run ons!
[Magisk] Jeggu:
I also can't pass SN fully as CTS profile match fails.

Here's my process:

1. Install cm 14.1 on my OnePlus 2

2. Remove inbuilt root

3. Check SN (passed every test)

4. Installed magisk + phh

5. Enable magisk hide and reboot

6. SN fails (CTS) but pogo works.
[Magisk] IcyVeins:
[MENTION=4470081]topjohnwu[/MENTION]

Bug-Report here.

With the most recent version, booting fails for my Huawei Mate S running Android 6.0. Magisk used to work at least up to version 6 (have not tested higher versions except version 9).

I have uploaded the clean boot image and the modified one for you:

http://uploaded.net/file/bwkmiclv

The installer itself does not display any error, all checks pass.

If you need additional details, I will provide them. :)
[Magisk] V4LKyR:
To whom it may concern,

Magisk v9 does NOT work with SuperSU (SR4-SuperSU-v2.78-SR4-20161115184928.zip)

My device: Sony Xperia™ Z2 D6503 with 23.5.A.1.291 ROM (Android 6.0.1).

My regards.

EDIT: Yes, I flashed SuperSU first and then Magisk, followed OP instructions of course.
[Magisk] brainvision:
hi guys!

I'm interested into this project, sounds promising but I have to admit that I'm still confused about it..

Hope you can help me to understand if it could help in my situation..

I have a dual boot (Windows / Android) tablet with an Intel Atom x5-Z8300 CPU; Android version is Lollipop 5.1_r1 (API 22); rooted and with custom TWRP recovery..

What I would like to achieve here is to flash and use Xposed: I already tried x86 and arm64 official frameworks and they do NOT work, I guess because of the x86_64 CPU. Tried unofficial porting (for MIUI) and they did not work, too..

So, would Magisk help in such a situation?

Thanks a lot guys, see you! ;)
[Magisk] ss4rob:
Hmmm... I ran out of power this morning, and upon reboot, I'm unable to pass SafetyNet... did Google block my two days of Android Pay and PoGo happiness with v9? :-/ I'm on a Nexus 6P running 7.1.1, and until now, everything was working.
[Magisk] gstanke:
AP and PoGo still working here
[Magisk] olivercervera:
Wow. I'm impressed.

This morning I took a vanilla Nexus 5X running Android 7.0 N5D91L and it works. It's the first time in nearly 3 years I work for this company I see AirWatch "compromised" detection to be defeated (Xposed and Root Cloak were detected at the time).

1. I unlocked N5X bootloader.

2. Flashed latest TWRP

3. Flashed Frano Kernel which has the patch to tamper the unlocked bootloader state for Safety Net

4. Installed Magisk packages and set it up

5. Added AirWatch Agent and Settings to exceptions

6. Enrolled, device is not compromised.!!!

I am tempted to report it internally... but I may get killed by you!

Thanks for the info [MENTION=1162986]Captain_Throwback[/MENTION]!
[Magisk] Siema89:
Since updating to v9, Magisk Hide does not work for me.

SafetyNet Helper, Pokemon GO and Android Pay all fail for me.

Attached log. For some reason, enabling more verbose logging in settings didn't make them any more verbose....

Using Magisk v9, with MagiskManager v2.5 and PHH SuperUser r266-2.

Device: Samsung Galaxy S7 SM-G930F, stock ROM 6.0.1, october security patch.

Had to swipe to enable modifications in TWRP after clean, stock reflash (and patch dm-verity) for Magisk to install at all.

Thanks for any and all help!

edit: added boot image, logcat from boot, and another log (this one includes busybox stuff. for some reason this option sometimes disables itself)
[Magisk] Drivepnut:
Obviously I am doing something wrong. When I enable Magisk hide, then I go to Magisk hide and check android pay for one thing it doesn't stay checked when I back out and and also when I reboot I lose root. I am updated on the latest Magisk and Magisk manager. I am using CM13 on a S5
[Magisk] Didgeridoohan:
The "loosing root" issue is a known bug that a lot of users are experiencing. Unfortunately the only solution at the moment is to disable Magisk Hide.
[Magisk] Captain_Throwback:
I don't have any module that does that which isn't device-specific (most system apps are, especially the privileged apps). So I'm not sure how to help you outside of you uploading the module you're trying to install and I can take a look at it.
[Magisk] Drivepnut:
Yeah thanks that what I did after I restored my back up through twrp thsnks
[Magisk] Captain_Throwback:
A logcat might be more useful, since the Magisk logging is only specific to Magisk operations. To see why failures are happening, both the Magisk log and a logcat from bootup are necessary (though neither may start early enough to provide the insight needed to determine the issue).
[Magisk] pndwal:
Make denylist work when zygisk is disabled is merged now!

Commit comment:

https://github.com/topjohnwu/Magisk/pull/7631#issue-2044963722

👍 PW
[Magisk] forserg:
Direct Install with recovery mode checked worked for me. You were right.

After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
[Magisk] J.Michael:
At some point you recovered by flashing stock. Did that "stock" have the right CSC? Did that stock have the updated bootloader?

What happens when you try to flash the "original" CSC?

Don't just say "updated bootloader", try to cite version numbers.

If you have Magisk installed and running, then it is unlikely that your current bootloader is refusing to run modified/unsigned software.

If the "problem" is that the collection (AP, BL, CP, CSC) with the "right" CSC has an older bootloader, and when you try to flash it balks at "rolling back" the bootloader, you might have more luck if you construct a new set of files. Either do not include BL, or use the newest (not the newest released, the newest you have flashed -- don't go looking for new problems) BL with the "good" CSC.

How does anyone use these ROM files if they include a CSC that makes it impossible to use your phone as a phone?
[Magisk] pndwal:
Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls! 😬

Are you flashing patched AP (Application Processor binary) along with

all

the other package binaries (X4?) for your S10+ (also in Magisk Installation page, Samsung section)??

CP is Cellular Processor (Nb. Oft repeated references to CP as 'core processor' may be misleading) binary package (also referred to as Baseband Modem) so that should have fixed mismatched baseband etc... correct CSC (Consumer Software Customization; region, APN and carrier specific software packages/settings) and even BL (Bootloader) are most likely also important...

Nb. BL doesn't always update bootloader version, but if later firmware has been flashed be aware that these can also cause anti-roll back version for bootloader to be incremented (in the event that an update patches serious vulns) so you original firmware may be blocked and you may need to use later packages only...

If flashing latest complete firmware package via Odin doesn't fix your IMEI / baseband issues it may be that you've messed with partitions that contain unique device values in the past... You may need to ask in Galaxy, S10 or S10+ XDA forums for that. 🤠 PW
[Magisk] forserg:
Out of curiosity, both ways gave a message:

"KERNEL REV. CHECK FAIL. DEVICE :17, BINARY : 16
[Magisk] forserg:
Always use nandroid backup even this time, but I didnt know that bootloader can be updated with no option to rolling back.
[Magisk] J.Michael:
You are still not telling us any version numbers.

What kernel version is listed in Android Settings -> About -> (maybe Software)?

Did you try finding the latest, complete, ROM, like @pndwal suggested?

The error message makes it sound like the problem is where you got the boot image. (I don't know if "rollback prevention" is applied to recovery.)

The reading I did suggests IMEI is *not* changed or wiped out by installing software. It might become invalid if you have the wrong country code. So you don't need the one-and-only-right-CSC, you just need a ROM with the right CSC (and I think CSC means two different things -- there's a CSC associated with a ROM, and there's a file named CSC.tar that is part of the ROM; we can only hope that one is related to the other).

So try a ROM at least as recent as the newest ROM you've ever installed, but with the right CSC code. After your phone is usable as a phone you can think about re-installing Magisk.
[Magisk] pndwal:
So you are simply trying to install a ROM with kernel binary older than anti-roll back version now set in device e-fuses (secure hardware fuses) and the downgrade is blocked by the bootloader... You need to download later firmware (17+) from Samfirm etc... Hopefully that fixes your issues. 🤠 PW
[Magisk] forserg:
My bad.

CARRIER_ID: 02U

The firmware a have now is G975FXXSHHWI1 (CSC - TCE, build date 2023-09-22) Latest for TCE region.

Kernel version:

4.14.113-25257816

The one I tried to install is G975FXXSGHWC1 (CSC - 02U, build date 2023-03-02) This is the latest for 02U region.

Ill try it.
[Magisk] Radzią:
Why is my deny list is empty?
[Magisk] zgfg:
Can you show screenshot from the main Magisk app screen, to see what is displayed there (Installed, etc)

Also, when you click to the dots (top-right) and enable Show System apps - does it list them
[Magisk] pndwal:
Have you opened Magisk App in non-owner profile after setting Multiuser mode to 'Owner only' (only owner has root access)?... I believe that this expected behaviour in this case... The Magisk App in owner profile will only display owner accessable apps in DenyList and apps in other user profiles will detect Magisk; reasonably, Magisk in non-owner profile will not be able to see/configure apps in non-owner or owner profilesin DenyList...

If you change Multiuser mode to 'Owner managed' , other user profiles can then have both root access and ability to deny Magisk modifications and you can apparently set set up denylist in Magisk App in a non-owner profile.

You may be able to configure all options from Magisk App in owner profile too, and you can also try setting multiuser mode to 'User'... Nb. I haven't played with these options personally.

Nb. multiuser behaviour was fixed/properly supported in 24.2. There is a current issue that hasn't been addressed yet however:

denylist not showing apps in other users #7959 opened 2 weeks ago by aruskkk

... This may or may not turn out to be unexpected behaviour, and you may have a similar issue if you actually have 'Owner managed' set or have the behaviour only after taking a recent update for Pixel device... Looks to me that inability to see non-user apps in DenyList from Owner profile may in fact be expected behaviour however. 👀 PW
[Magisk] wei34:
android15 beta能用吗？
[Magisk] Radzią:
I have hyper os im mi10 As far as I remember, I didn't set it, I don't even know where to find it 😀
[Magisk] pndwal:
Translation: "Can android15 beta be used?"

I'm not aware of specific compatibility fixes for A15 yet, but just try it and let us know... It may work...

BTW, please post in English here. 😉 PW
[Magisk] pndwal:
Ah, then you may have a separate or related issue... (Did you have HyperOS originally or update from MIUI?... Never set another user or guest profile in MIUI prior to upgrading?)

If in owner profile, any Multiuser Mode should work anyway... Set in Magisk App Settings BTW. 🙃 PW
[Magisk] Radzią:
Yea update from miui. I don't have time to do a clean installation yet, I have too much data.

Do you have any idea for this?
[Magisk] pndwal:
No idea if you're using an owner profile... Why not try changing Multiuser Mode in Magisk App to Device Owner Managed or User Independent just to be sure?...

If not that, do you have a way to wipe /data/adb/magisk folder and magisk.db file?... Doing that and rebooting will rebuild Magisk configuration in case it just got corrupted... 🤠 PW
[Magisk] forserg:
Didn't work out. Odin just stopped right before passing stage. I rebooted the phone manualy, baseband is still unknown as long as EMEI.
[Magisk] Radzią:
Unfortunately, multi-user mode did not help. Deleting files from a folder adb Neither. I guess the only thing left is wipe data
[Magisk] J.Michael:
Is EMEI IMEI in another language?

Please explain "as long as EMEI".

I can't keep track of your situation. The ROM IDs you posted a week ago do not make it obvious that your device has anything with version 17 while you are trying to install version 16.

I do not understand the country codes. Or the CSC, if that is something other than country code.

Maybe you still aren't trying to install the right ROM. Remember, at this point we don't care what software you wish you had. You are supposed to be finding a ROM that is meant for your device, maybe associated with your carrier, maybe tagged with your location. Possibly complicated by it cannot be older than what is already on your device.

Can you go to your service provider and tell them you need help? (If you bought the phone from someone other than your service provider, start with the person who sold you the phone.) The service provider should have some interest in helping you -- if you can't use the service, you won't keep paying for it.

Maybe you can install a custom ROM. Check other threads to see whether something like LineageOS has been installed on the same device, and whether the device then functions as a phone.
[Magisk] pndwal:
Mmm. Not sure that will help either... You can open a GitHub issue if you're prepared to install Debug Magisk build and supply logs; Devs might help further. 🙃 PW
[Magisk] pndwal:
Other saga details:

https://xdaforums.com/t/sm-g975f-is-this-the-end-of-the-journey-for-my-phone.4663849/#post-89440576

👀 PW
[Magisk] Elvara:
I can't find anything anywhere about it but I have a oneplus Nord 2T, I was using it with android 13 (oxygen) without problem to install the app and root the phone.

I finally upgraded to android 14 through the OTA, my root was gone of course I was able to patch the file and get root again after the reboot, the magisk app was gone.

When I try to install it I have no problem but when I open it the screen change to black for a second then comes back to the menu with the app gone.

I have an app called App Manager that can use root to install/remove or freeze all type of apps, it has a log of the removed app and I can see there it was removed.

I don't understand how or why only magisk seems to be a problem when I have other apps installed from unknown sources that are still there.

Any idea?
[Magisk] J.Michael:
Are you sure 5hat the version of Magisk app you used to patch is the same version you are installing after flashing the patched file?

I have heard that Magisk will not tolerate an out-of-date app, but if you installed the Magisk app once, then patched, flashed, and rebooted, I don't see why there would be a conflict.

Of course, there are lots of reports of problems with lots of versions of Magisk. Maybe you're trying to use a bad one.

Say what version of Magisk you are trying to use.
[Magisk] wackowizzard:
Hi,

When I open LSPosed application, there is something wrong. See screenshot.

There is a message : report problem to Magisk developer.
[Magisk] Elvara:
I actually updated the app from the app itself before doing my OTA upgrade so it get the version 27 of magisk, I tried installing that one again I had in my downloaded folder. But I also downloaded again the app from github.

I do have root, I've modified the boot file with magisk, so I'm not sure what to do now. I'll try installing an older version. But as you see of the screenshot from app manager, I don't know how the app is installed and removed almost immediately. At first I thought it was caused by an android 14 new security change.
[Magisk] J.Michael:
Saying "version 27" is not enough. You have to say "version 27.002-revB_3pm_no-guacamole".

Your screenshot shows 27000. I think I've read of problems. Read a hundred posts and try to pick a version that is *not* associated with problems.

As for the "app manager" showing "removed apps": I've never seen that. Maybe it's not in Android 9. Maybe I just haven't looked in the right corner. But maybe you're running afoul of the "sideload" permission. Could it be that you enabled installing "untrusted" apps originally, but the update to Android 14 reverted the setting and you haven't un-reverted it?
[Magisk] badabing2003:
Run magisk -c from adb shell and see what version it reports.

Then uninstall every copy of magisk app,

You have more than one (including possibly a hidden one)

Then reboot and install magisk app matching the version reported by magisk -c command.
[Magisk] dknight178:
Has anyone been able to use HuskyDG's magic-mount-extender and/or the liboemcrypto.so disabler using magisk 27000/27002 and Android 14? If yes, could you please share your versions/forks? Thanks
[Magisk] dronkit:
Can anyone help me? I accidentally flashed the stock ROM on a galaxy A12 that already had Magisk installed. It went automatically to odin mode with errors in red. Then I realized my mistake and patched the stock rom and flashed it, but I get a bootloop. How can I recover this phone? Thanks!

UPDATE: I got it to work by extracting and flashing the stock boot.img and recovery.img via odin. I guess that's a dirty fix and IDK why this worked and flashing the whole stock rom didn't
[Magisk] Elvara:
Thank you for the help I had an hidden version of magisk that I called "settings" for some reason and that really messed up the possibility for me to find it. that took me forever to find but it's all good now.
[Magisk] J.Michael:
If you flashed a stock ROM, you effectively uninstalled Magisk, except for the /data/adb directory.

Did the flashing of the stock ROM involve doing a "factory reset / wipe data"?

If you have a problem after trying to reinstall Magisk, the things to check are:

did you patch and flash the right file?

did you change the version of Magisk?

did you change the version of Android?
[Magisk] dronkit:
UPDATE: I got it to work by extracting and flashing the stock boot.img and recovery.img via odin. I guess that's a dirty fix and IDK why this worked and flashing the whole stock rom didn't

Ii'll check that folder (if I can install TWRP or something) in order to clean up, but my goal now is to reroot it.

No, but, I did one factory reset from Android's configuration menu in order to clean up, set up the phone and debloat it (I bought it used). It worked afterwards but I screwed up when debloating so then I did the stock rom flash.

I'll keep that in mind when I try to reroot.

Thanks for your response!
[Magisk] pndwal:
Keep in mind that official instructions still state:

although I know many Sammy users have been able to recover from this mistake without wiping data... Seems you've put your finger on the working method for your device... Not sure if trick would work for any Samsung device however, but may be useful for others...

Take care with upgrades in future! 😉

If goal is to reroot, you can leave configuration as-is... Only modules that become incompatible with later Android versions may cause bootloop, but normally the previous Magisk configuration files are OK... If you want to force a configuration rebuild (restore clean Magisk, no modules, superuser list, DenyList etc) after installation, just delete everything in /data/adb after rooted with a root explorer and reboot; configuration files will then be rebuilt.

🤠 PW