yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
In Magisk Alpha TG:

😱 😁 PW
[Magisk] HippoMan:
I was running on a standard OnePlus 7Pro for a year or two. I always ran a standard factory A10 ROM. I applied normal, standard OTA updates when they were offered.

One time I wasn't paying good attention, and I didn't notice that the offered OTA was actually an upgrade to A11. After applying the OTA, a few of my apps didn't function well, and my system had some issues.

The fact that I had taken a full nandroid backup right before applying the OTA allowed me to easily revert back to my comfortably working A10 system within 10 minutes.

This had nothing to do with modding.

I would have needed much more time than 10 minutes to investigate new apps and to change to some of them, and to reconfigure some other apps to work in the new OS version in the ways I was accustomed to. However, there was no benefit to me in jumping through all those time-consuming hoops.

Yes, Google wants us to upgrade when they're the one doing the modding and they institute new OS features. But I may not like each and every Google "enhancement", and when I accidentally accept one of their "improved" upgrades without checking it first, I want a way to easily undo my mistake and roll back.
[Magisk] pndwal:
So can I assume you had unlocked bootloader and custom recovery?... or do you mean you were somehow able to dump/backup partitions and restore these without modifying your device?

Nb. Modding starts with unlocking bootloader; this means an OS may run or be running that is no longer verified as signed with non-custom keys... PW
[Magisk] HippoMan:
Irrespective of the definition chosen for the word "modding", I would have had a huge headache going back to A10 after my error without the full backup and full restore that I was able to do.

My point is that if there was some sort of official, supported way to perform full nandroid-like backups and restores, we would be able to deal with this kind of situation without even having to unlock the bootloader, etc.

But there is no such thing, and therefore, I'm glad for my unlocked bootloader.
[Magisk] lenoid:
I tried also that but same here, Recovery not offered. Nevertheless I patched my boot.img file and flashed it, but it's the same as before, no root anymore and no Direct Installation option anymore.

I'll wait for a new Magisk version and give that a try because I don't think that it's possible to get v26.3 working on my Xperia X Compact without a lot of effort (in the past I updated the Magisk app and made a direct installation and it worked fine for the last 5 years).

If you need some more information for getting this issue fixed, I'd try v26.3 again of course to give you detailed information.
[Magisk] zgfg:
Are you on Magisk Alpha?

I don't have evil service but Injection and Prop modified - on Canary 26301 and Shamiko
[Magisk] zgfg:
And interestingly, I also have Evil Srvc 0x02, but if I enable Play Integrity Fix from @chiteroman

Since I don't need PI Fix module on my Xiaomi.eu 14, I don't use it and then I don't have the evil srvc in Minotaur v14
[Magisk] pndwal:
That's what I thought...

My point is/was that dumping partitions/nandroid is for modders/developers only...

What you are really saying is you're glad of moddable Android and custom recovery functions...

Since there ain't an 'official' (guess you really mean stock) means to do 'nandroid-like' backup & restore, you're also glad to be a modder who had had the foresight to use a key modder's utility not available to stock users...

AFAIK we need unlock and/or root (understandably) to get access to or dump/backup partitions... That's also the quandary (chicken and egg scenario) modders wanting to root (or other) devices where manufacturers don't supply ROM packages (even if unlocked) face...

😛 PW
[Magisk] pndwal:
Yes...

Interesting...

I also noticed Momo finds Alpha's 26301 NB-Zygisk (ie. Shamiko doesn't hide) but doesn't find Canary 26301 Zygisk on my RN8T, stock MIUI A11. Despite this, as you'll know, most banks don't detect Alpha Zygisk (some like Starling can) while many detect TJW Zygisk...

Could have something to do with

PW
[Magisk] chiteroman:
Maybe due Dobby builded in Zygisk lib.
[Magisk] HippoMan:
I consider it to be unfair to define "modder" or "developer" as "anyone who dumps partitions/nandroid".

Many people who want or need full backup/restore capabilities (e.g., people who want to roll back OTA updates) have no intention to do any kind of system modfication or development, aside from rolling back to a previously saved system snapshot in order to avoid a full factory reset and all the subsequent work that is necessary to get back to the OS version that they were previously running.

An official Google/Android utility to perform such full backups and restores on a system with a locked bootloader would be very helpful to people like that.

But since there is no such utility and it's not likely that there *ever* will be such a utility coming from Google, people who have no system modding nor rooting intentions whatsoever still have to get the unfair label of "modder" stuck onto them and to receive the punishment that goes along with that label, simply for wanting to be able to run full nandroid backup/restore and nothing else that would require an unlocked bootloader.
[Magisk] pndwal:
Well they've necessarily modded their devices first!... And what's more, that also depends on the OEM allowing it and the user agreeing to a disclaimer like:

... How are they not device modders?

All this is beside the point.

Since it's not available without unlocking, 'anyone who dumps partitions / performs nandroid' has to agree to modify the device by unlocking which changes original product features including disabling security functions and other features... Then they generally install a custom (modified) recovery...😆

Well they want that custom mod function!...

... Whether the label is 'unfair', they otherwise 'receive punishment' or they happen to be pining for the fjords don't enter into it!... At least for fully stock users this is a DEAD parrot!... However desirable it's plumage... Remarkable bird though... 😜 PW
[Magisk] ipdev:
I miss the days when I could just use adb to dump the data partition into an image file and flash it back. 😿️

Better yet, when I could wipe system, install a different OS version and leave userdata alone.

[The original Clean/Dirty flash install.] 🙃️

As for the Cat and Mouse game...

My money is on the Mice. 😜️

"Look, sorry - are we talking about the little white furry things with the cheese fixation and women standing on tables screaming in early sixties sit coms?"

Slartibartfast coughed politely.

"These creatures you call mice, you see, they are not quite as they appear. They are merely the protrusion into our dimension of vast hyperintelligent pandimensional beings. The whole business with the cheese and the squeaking is just a front."

― Douglas Adams, The Hitchhiker's Guide to the Galaxy​

Cheers all. :cowboy:

PS.

I miss FlashFire. 😥️
[Magisk] HippoMan:
Yes, but now, Android has improved so, so, SO very much! In its current beautiful, evolved state, it no longer allows very many of those evil Modding Activities (gasp!) from the past that you described.

And Android just keeps getting better and better and more and more evolved to ensure that even less and less Satanic Modding will be possible in the future.

Yeah, we Modding Mice need to utilize all of our Pandimensional Powers to prevent today's Golgafrinchians from Google (aka "Googlefrinchians") and the other Golgafrinchians from the app developer community from doing to Android what the original Golgafrinchians did to our planet when they "landed" here.

FlashFire Forever!

42!
[Magisk] pndwal:
Can we still do that with root, or root shell?... Did Verified boot, Android Verified Boot put an end to this ability without modding? (I haven't found the definitive answer yet)...

👍

Yup; they've been experimenting on you I'm afraid...

Such subtlety... one has to admire it.

Yes Earthman, they really are particularly clever hyperintelligent pan-dimensional beings.

Your planet and people have formed the matrix of an organic computer running a ten-million-year research programme... Let me tell you the whole story... It'll take a little time...

Yup... but, depending on your viewpoint, we have more options now. 😛

Anyway, I think that enforced fun is probably not what you need at this point..

And speaking of pipe dreams, the Hitchhiker's Guide to the Galaxy has a wonderfully detailed section on RECREATIONAL IMPOSSIBILITIES that explains how learning to miss the ground can actually be far more fulfilling than reminiscing about past recreational possibilities that have recently become impossible...

Please consider the following ponkle seriously as it treats this remedy and I really think a bit of a physical challenge would help draw you out of yourself... 😜 PW

Spoiler content hidden.
[Magisk] HippoMan:
This is just another form of Evil Modding ... and I miss it, also!

I'd be happily surprised if the Googlefrinchians would actually allow this kind of Modding on a device with a locked bootloader.

Unfortunately, I don't have any device with a locked bootloader to try this on.
[Magisk] pndwal:
Actually doesn't find Ramdisk as there is none before patching... Magisk creates ('manually adds') the basic ramdisk containing magiskinit in these cases... It 'has mechanism' to know there is no ramdisk, therefore must add it with magiskinit instead of just injecting magiskinit in an OEM ramdisk... Nb. It will always add this when missing, even in devices where bootloader won't support ramdisk in boot since Magisk cannot determine if support is present... That's why No (OEM supplied) ramdisk is still indicated, the logical conclusion being that ramdisk in /boot shouldn't work (ie. is most likely unsupported in B/L if OEM/Android architecture doesn't implement it).

I find that Magisk annoyingly re-sets this user option whenever the App is fully closed and reopened or some App functions are performed, ie. the option is automatically checked again in the Install menu, since 26105 and 'device detection scripts and logic' regression...

The detection issue as well as specific detection for legacy SAR was fixed in 26102, but the Recovery mode user setting retention issue seems to have been missed.

I've finally gotten around to making a GitHub Issue for this:

App loses Recovery mode user setting for A-only legacy SAR devices

Reboot system will boot to recovery (it's trying to reboot to system wilh Magisk via recovery) simply with Recovery mode checked... You will have erroneously patched /recovery only if you took Direct Install with that checked... Samsung users will get recovery.img patched when taking Patch image with AP binary too...

But reboots normally if uncheck Recovery mode?... PW
[Magisk] kudichode:
This 💯

Can't say I've ever bought a device which didn't support bootloader unlocking out of the box. Before even putting my sim in a new phone, bootloader unlock comes first 😄
[Magisk] zgfg:
Yeah, that was an interesting idea - to open Install, uncheck Recovery mode, then to go to Modules, install a module, and after that Magisk will correctly reboot to System, not to Recovery

And every time, before rebooting to System from Magisk, to open Install first and to uncheck Recovery

So it works, but it's pretty inconvenient and not an obvious or expected way to operate (and of course, such tricks were not needed with earlier versions of Magisk)

Anyway, I actually have a Reboot app installed and use it to reboot to System/Recovery/Fastboot through that app, so I will not bother to use that workaround for Magisk v26.3 on my old 'Recovery No' phone :)

I use that same and simple old Reboot app (it was removed from Playstore long ago and I like it more than any similar Reboot apps that can be found there) on my various phones since 2017, it's always first thing for me to install that Reboot apk, MiXPlorer apk and Terminal emulator apk (I keep the installation apk files) upon rooting any phone (software reboot requires root, MiXPlorer is mainly useful in root mode as well as TE)
[Magisk] pndwal:
Yup, that's what I've been doing... not necessarily before installing modules etc, but need to go to Magisk Install menu and uncheck the Recovery mode box before rebooting from Magisk, using Install (patch) functions or closing out of the app ATM... Seems option is checked again on opening App if app has been fully closed (removed from memory)...

Interestingly, I have reboot option standard with MIUI since update to Android 11 / 12.5.x which works correctly even when Recovery mode is checked:

...I think I needed CustoMIUIzer mod previously even for basic reboot (to system)... CustoMIUIzer also adds various 'extended' reboot options:

... Extended reboot menu seems to work correctly even when Recovery mode is checked also. 🙂 PW
[Magisk] SysGhost:
Are there any neat guides on how to get SafetyNet fully working with Magisk + LineageOS 20? On older devices such as Oneplus 6 for instance?

Been looking around and trying various methods. No luck so far. The best so far was some custom unofficial LOS20 with a fully working SafetyNet but got tons of Bluetooth issues instead.

Now looking back to get this Magisk + SafetyNet working on my Oneplus 6
[Magisk] pndwal:
Official LineageOS is clean of spoofing and will never integrate SNF or other means of passing device integrity verdicts... On the other hand, clean ROMs are the best for use with Magisk solutions as inbuilt spoofs won't conflict as they do with many custom ROMs like XiaomiEU and PixelExperience... Nb unofficial LineageOS builds often do integrate such solutions...

Official University SafetyNet Fix is still broken, but fixes have been implemented in two forked projects... Either should be good for a passing Play Integrity deviceIntegrity verdict...

NB. SafetyNet API is deprecated and banks have generally migrated to new Play Integrity API... The equivalent of old ctsProfileMatch with basic only evaluationType is deviceIntegrity... The equivalent of old ctsProfileMatch with hardware-backed evaluationType is strongIntegrity and you cannot pass that with unlocked bootloader (or locked with custom keys).

Solutions:

@Displax - https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/

@chiteroman - https://xdaforums.com/t/module-play-integrity-fix.4607985/

Use Play Integrity API Checker etc to check deviceIntegrity verdict... 🤠 PW
[Magisk] zgfg:
I have also extended Power menu but I prefer to save my Power button (specially when it also includes fingerprint sensor) - that's why I like software methods like Reboot app, or rebooting from Magisk (but without the need for tricks as now in 'Ramdisk No' case)

Also, reboots can be executed through Terminal Emulator (or via adb):

reboot

reboot recovery

reboot-bootloader
[Magisk] Uluru25:
... only in case you are interested in an alternative app from F-Droid: Simple Reboot
[Magisk] zgfg:
Thanks but the popup from the Reboot app I use (see the attachement in my previous post) is smaller and properly centered

The popup from this app from F-Droid wastes me the space and displays towards the corner - screenshot
[Magisk] Uluru25:
... very clear and totally up to you (I have never imagined that this could be a preference, my preferences are - if ever possible - to take an app from F-Droid) 🤠
[Magisk] wittymav:
1. Only one device has the volume down button damaged. I am afraid the other may follow.

2. Yes, Magisk was installed in recovery mode. However, if you go to magisk and choose to reboot from its menu, the devices reboot with Magisk active. But, if you reboot from any other way other than from Magisk or using the power + vol down combo, it reboots without magisk. So, I was actually thinking there might be a way to use adb to instruct system reboot using magisk.

3. If I could also restart com.android.systemui, it may solve my problems too.
[Magisk] wittymav:
I will try a complete shutdown followed by a startup to see if Magisk is loaded up.

If I try adb reboot recovery, there may be no way to escape the process and boot to system considering there's no button sequence to escape from/with.
[Magisk] gertmenkel:
After upgrading from 26.1 to 26.3 my phone's selinux status has suddenly switched to permissive. Does anyone know how this could've happened and how I can fix it?
[Magisk] pndwal:
Are you sure?... Are you on a custom or developer ROM that may have selinux disabled in the first place? ... Possible the rules aren't properly set or accessible too... PW
[Magisk] gertmenkel:
My ROM doesn't disable SELinux. It's based on LineageOS and Trust actually warned me after a reboot about SELinux being turned off.

It's possible some script is bailing out before SELinux state is restored on boot, but I find it rather strange that this would happen during a minor version upgrade.
[Magisk] J.Michael:
I've seen lots of posts asking how to change SELinux to Permissive, but I think this is the first time anyone has wanted to go the other way.

Have you googled to see if there's a way to switch to Enforcing in Linux? You might be able to do the same thing, since you have root privilege.
[Magisk] J.Michael:
The hope is that using "adb boot recovery" (maybe "reboot recovery") when Magisk gets control there are no buttons being pressed, so it is as if you released them in time.

Only one way to find out...
[Magisk] pndwal:
So it is custom...

Please say device and ROM, and link source...

Also, did you take Direct install, or flash Magisk as .zip archive from recovery?...

In the latter case you will only have partial root and need to reinstall Magisk by taking Direct install on opening the App as refactoring requires Magisk selinux/module rules directory to be set with booted system now... Did you do that if/when prompted?

Further, while the major refactoring for Magisk sepolicy was built in 26.0, several more sepolicy changes were made for 26.2 so there could be regressions... 🙃 PW
[Magisk] chiteroman:
KernelSU >>>> Magisk 😝

I'm using ZygiskOnKernelSU + Shamiko.
[Magisk] pndwal:
👍

Please say if this is with Magisk (build?) or KernelSU proper, device, ROM and any other mods... 😛 PW
[Magisk] chiteroman:
It's KernelSU, using lybkernel on ArrowOS Android 11 for POCO X3 Pro (vayu). The other modules I have are for Youtube Revanced 😂
[Magisk] pndwal:
... Wanna re-test Starling Bank? 😛 PW
[Magisk] chiteroman:
If I disable ZygiskOnKernelSU, Shamiko and PlayIntegrityFix it works. Starling detects all Zygisk versions (and resetprop utility).
[Magisk] chiteroman:
Also I can implement PlayIntegrityFix into framework.jar so I don't need the module. But Starling doesn't check Play Integrity neither SafetyNet.
[Magisk] gertmenkel:
Yes, that's what makes Googling this stuff quite difficult. SELinux is an important security measure in Android, without it the sandboxing features are horribly broken. People who want to disable it are usually running into issues with ROMs and mods that aren't configured correctly, and disabling all security is easier than fixing the underlying issue.

Android and normal Linux enable SELinux in different ways. I've found setenforce to be doing something, but Trust still claims SELinux is off.

Xiaomi Mi 9 running the latest CrDroid (from here). I haven't flashed the zip from recovery. SELinux is enabled by default without Magisk.

I believe Magisk did offer me to directly alter the boot partition during the update(rather than patching boot.img and flashing that through recovery, like it normally does) but I'm not sure if that's relevant. My device doesn't have A/B boot so I don't think the matter in which the boot partition is flashed should matter too much?

I suppose 26.2 could be the real culprit. Do you happen to know what could be causing SELinux to get flipped during these refractors? I would expect regressions to appear in the form of a boot loop, not disabling it.
[Magisk] zgfg:
Direct Install works only for updating Magisk, when Magisk app does have root (since the root is needed to patch the live partition). But you can still patch the boot.img

Without root, only patching the img is available
[Magisk] pndwal:
So you took Direct Install it seems (I didn't consider you'd update Magisk by Patch image and flash... although it's offered Direct install is recommended) rather than flashing Magisk as zip installer from recovery so selinux rule directory should be properly set... It isn't only when using deprecated installation using custom recovery method...

Nope... doesn't matter on A/B either... Always installs to current slot unless "Install to inactivate slot' appears and is selected...

Yup, seems strange and many possibilities...

- I see "addressed some sepolicy" appears twice in your crDriod changelog...

- Magisk 26.2 basic changes included:

MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support printing out the loaded sepolicy rules

Some commits:

Print permissive rules

topjohnwu committed on Aug 3

Update libselinux and libsepolt

topjohnwu committed on Aug 2

Support dumping sepolicy rules

topjohnwu committed on Aug 2

Update xperm parsing

topjohnwu committed on Aug 1

magiskpolicy: Fix old xperms being cleared when adding new xperms …This commit updates sepol_impl::add_xperm_rule() so that it loads the current xperm bits from the existing avtab entry before setting or clearing xperm bits. This fixes new allowxperm rules causing old xperm rules within the same xperm specified/driver to be removed.

Fixes: #7176

chenxiaolong authored and topjohnwu committed on Jul 25

I suspect it's a regression; could be complicated by current move from C++ to rustlang...

Unless a Dev comments here, I think you should open an issue on Magisk GitHub... Install latest Debug build (for verbose logs), supply logs per https://github.com/topjohnwu/Magisk#bug-reports, Include "Magisk version code: 26301" in the text body (to avoid bot auto-closing issue), provide description and wait for Devs to analyse. 😜 PW
[Magisk] gertmenkel:
That explains a lot, I almost always install Magisk after a ROM update reformats the boot partition. I guess I never thought about it!

Thank you very much for your help! I'm going to look into these commits and figure out if something I did to my phone messed up Magisk, or I'll open an issue if I can't find anything. My Rust is a lot better than my C++ but hopefully I'll be able to figure it out.

Edit: just today I received a CrDroid update, I was hoping it fixed the issue but sadly it didn't. Thought I'd add that for clarity.
[Magisk] y khuyen knul:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

I want kai hybrid magisk

*************************

Tôi muốn kai lai magisk
[Magisk] Oswald Boelcke:
@y khuyen knul Welcome to XDA! I hope you'll always get the support you require.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Vietnamese posts.

Spoiler content hidden.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Magisk] portsample:
No cigar. I've created a tar file with stock vbmeta and boot images in it.I am getting the following messages from Magisk when I try and get it to patch the archive per your suggestion...

-Installing 26.3 (26300)

-Copying image to catch

-unpacking boot image

-Unsupported/unknown image format

-installation failed

I have tried tar'ring both with and without the ".img" suffix on the files. What are the boot files named in the Samsung tar? I named my tar file recovery.tar if that makes a difference. Am attaching both stock boot and vbmeta images. Thanks in advance.