yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
I did not think of that.

Dumb user moment. :oops:

You are correct RootbeerFresh does not support landscape mode. ;)

RootbeerFresh is(was) a fork of scottyab's RootBeer so I assumed they would behave the same.

RootbeerFresh - GitHub - Link​

Cheers. :cowboy:
[Magisk] Soumy1234:
Is anyone else trying out TheHitMan's Magisk builds? I installed it to try it out and I can't enable Magisk Hide. It keeps disabling itself. Zygisk is enabled and I only got the systemless hosts module installed.
[Magisk] pndwal:
Lit of bysdexia never hurts!

Ah, yes - I'm an amateur sleuth, and was recalling vvb2060 / TJW bumps: 'Add new targetSdk domain' and 'Target SDK 31'. (I got fixated on 31 also 🤪)...

I see vvb2060 changelogs do say '[App] Suitable for Android 12 API level'

Interesting that newer Rootbeer fixed app detection for Android 11+, but if you check @zgfg's screenshot, he is already using 'Rootbeer Sample'.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85817131

I can now confirm I get exactly the same results (I've just tried Rootbeer Sample; never tried Rootbeer before) on Android 11 device (Mi Pad 4, LOS 18.1, TJW Magisk 23001):

'No Root Management Apps' are detected w/ Magisk App NOT hidden, whether Rootbeer Sample is added to hidelist or not! (Root Management Apps are detected on Android 10 device (RN8T) unless Magisk App is hidden.)

My result w/ Rootbeer Sample in hidelist:

So it still seems changes in Android API Level 30 are exactly as I indicated!

These are summarised well by Momo home-screen comments (vvb2060, Rikka) I cited:

"Google Play requires all apps updated after Nov 2021 to adapt Android 11, apps will not able to acquire the app list." and "Detecting installed apps has no practical meaning."

Lesson for all on Android 11+:

*** There is NO real point using 'Hide the Magisk app' function post Android 10 !!! ***

This is because apps are prohibited from acquiring app list to detect installed apps anyway!

Please say if I'm missing something. 😬

🤠 PW
[Magisk] pndwal:
Best check it's telegram group (link from Custom Magisk GitHub). I think others have similar issues...

@zgfg is keeping up. PW
[Magisk] zgfg:
MagiskHide worked for me in MagiskCustom (95a4a4b8 - the latest), no problem, see

Disable modules and try with plain Magisk. E.g., some options in Riru-Momohider may affect stability

Btw, I see @Eng.Raman is here (nice), I think he actively uses MagiskCustom (from TheHitMan7)
[Magisk] zgfg:
Thanks (mostly that I'm not insane)

Confirning, RootBeer Fresh target SDK 28, RootBeer Sample target SDK 30

and yes, the old Fresh still detects (on A11) com.topjohnwu.magisk (Magisk app not hidden)
[Magisk] zgfg:
Now (apparently?) more on that matter - detecting apps, prior and post target API 30

For the purpose of testing I had both RootBeer Fresh (target API 28) and RootBeer Sample (target API 30) installedc and confugured in DenyList (latest Magisk Alpha)

Now I uninstalled both of them and then reopened Magisk app to check DenyList - neither of them was showing anymore in DenyList

However, I opened Terminal and used Magisk CLI to inspect which apps are still really in Magisk db enabled for DenyList and found that RootBeer Sample was there, while Root Beer Fresh was removed

In fact I found even more apps there (Native Detector, PushTAN) - apps that I used to have in DenyList but later uninstalled (and whenever I was looking in DenyList tab in Magisk app they were no more showing but apparently I did not take closer look over time either by CLI or by directly opening the denylist table in magisk.db to find that they still remained carved for DenyList)
[Magisk] pndwal:
Just tried Fresh too, same result as you.

In case there's any confusion, to be even clearer:

Lesson for all on Android 11+:

*** There will SOON be NO real point using 'Hide the Magisk app' function post Android 10 !!! ***

This is because all apps / updates hosted on playstore from Nov 2021 will be prohibited from acquiring app list to detect installed apps anyway!

Apps older than this are NOT required to comply with Android 11 rules (API Level 30), so may still acquire app list / detect Magisk app. However no updates may be hosted on Playstore without complying, so such apps (banking etc) will clearly become obsolete / be abandoned in a short time anyway.

- These changes are summarised well by Momo home-screen comments (vvb2060, Rikka).

😁 PW
[Magisk] zgfg:
It also means that "Detecting root managment apps" check in RootBeer Sample is actually pointless
[Magisk] pndwal:
Haha, I think lysdexia is catching today!

Is that Rootbeer Fresh, Rootbeer Sample, or both?... (or are you building FreshBeer Sample? - sounds rather appetizing!)

No need to distinguish however; probably pointless in either going forward.

Nb. This is exactly the point made in Momo:

"Detecting installed apps has no practical meaning." - ie. for the banks.

One for the naysayers; Google actually seem to be doing modders a favour here! 😜 PW
[Magisk] pndwal:
Wondering if this might have anything to do with keeping data/adb/ between Custom and Alpha etc...

@TheHitMan does say:

”Completely uninstall previous Magisk before installing custom Magisk build.

Even switching between custom Magisk builds also require full uninstall."

Also (I'm only guessing) entries not made using app UI may not be tracked / handled as expected. PW
[Magisk] zgfg:
Should not. You can test yourself (few minutes)

I installed (and added to DenyList) RB Sample last evening and RB Fresh this morning

On the other side, since Thursday evening I'm steadily still on Magisk Alpha, not switching among the Magisk builds/flavors
[Magisk] pndwal:
FWIW, I just checked and both have stuck in hidelist on Mi Pad 4 - Android 11- LOS 18.1 w/ TJW 23001 and denylist on RN8T - Android 10 - MIUI w/ latest Alpha.

All 4 installations in past few hours... PW
[Magisk] 73sydney:
Saw this elsewhere

Windows hacker manages to install Google Play Store on Windows 11 WSA

Microsoft recently released their Windows Subsystem for Android (WSA) for Windows 11 Insiders, and while it is an amazing achievement, at present it is pretty limited, with access to only about 50 titles in the Amazon app store. While it is possible to side-load any Android app, in practice the...

mspoweruser.com

Lets see how long it takes the hammer to come down before you get too excited Marvin :)

Still fail to see the point of Android on Windows...
[Magisk] pndwal:
Mmm. Guess we'll have to see.

Interestingly Google have already made concessions to allow whitelisted devices to run GApps as long as these are sideloaded by user (not sold by manufacturer), and device runs a custom ROM. They clearly don't like 'subversion of their security model' to spoof 'Device is certified' however.

It'll be interesting to see if any such concessions will be made for 'uncertified' Windows machines.

It seems certifying these machines in future with CTS is out of the question because 'WSA cannot pass key attestation (KA) as it only implements software backed Keymaster. There is also no verified boot, no "root of trust" in the attestation' (as John states).

I have no idea if the big wigs of MS and G are even on friendly terms, let alone willing to collaborate to make the most of this marriage, but if they want to at least allow Google Play Services and GApps to run as uncertified it's clear they'll need to figure out a foolproof way to achieve a trusted PlayProtect result at least (as things stand), or re-engineer the whole security model to satisfy the needs of corporate partners, customers and their devs before it can happen.

The firing gun is still echoing; the end is way down the track and out of sight to me. PW
[Magisk] zgfg:
If one still needs to hide the Magisk app, then instead of taking Hide Magisk app option in Magisk app settings page (again, not to be confused with Magisk Hide), the following works:

Riru and Riru-LSPosed (Magisk modules)

+

Hide My Applist (LSPosed module)

Screenshot below shows how RootBeer Fresh (old target API 28 that otherwise finds the Magisk apk) cannot detect Magisk apk anymore.

Ofc, I have also DenyList enabled for RBF, to prevent detecting the Magisk itself

I use that MHA module now also for 'dettaching' four apps from Google Play (same thing, MHA hides them from Google Play) to prevent updating them automatically or by mistake (e.g. one of them is YouTube because of Vanced root that requires me to stay on a particular YT version from July or so)

Unlike with some other methods, it's easy to stop hiding/dettaching - just disable hiding in the MHA module
[Magisk] pndwal:
Yup I added that a few days ago (only have that and CustoMIUIzer) but didn't play much yet... Looks to have several uses. - Seems hiding Magisk app will soon be irrelevant however... PW
[Magisk] jnshk:
I'm not sure if this is the correct place to ask, but I've got Magisk 23.0 installed on an Android head unit (Rockchip PX6 - MTCE) with Android 10. I'm trying to convert a couple of apps to system apps using the "terminal systemizer" module and I've discovered that Magisk does not seem to be mounting the systemizer or busybox modules to the xbin path.

When I enter the ls command in terminal, it lists all of the standard functions, but does not list any of the functions that should have been added as a part of Magisk modules.

Can anyone point me in the direction for a fix or workaround to this issue?
[Magisk] zgfg:
With A11, read only SAR (System As Root) is introduced and you can no more write directly to hosts file or restore system apps from Titanium backups, move apps to system, etc

Depending on the manufacturers/models/firmware versions it can start with A10 or even A9 (Huawei EMUI 9)

You can inspect how much 'free space' you have on the system partitions (if they are made read-only they don't need free space) by su -c df command in Terminal app (you will need to grant the root)

Check also (textual file, only READ, do not make changes) /vendor/etc/fstab.*** file for definitions of /system and/or / (root filesystem).

If ro= read only, you can not write/delete/add/change over the system.

This is not 'incomplete root' or some deficiency in Magisk but the way how filesystems are defined by vendors when they release firmwares

This is not new. People should have already be aware of read-only SAR systems, and forget the old-school apps like Titanium, etc

You should be using systemless hosts and systemless modules (all newer modules should be systemless)

If needed, search in this thread, in Magisk documentation on Github, on Internet what the term "systemless" means and how it works

Generally, modules write their changes to /data/adb/modules/***/system... and Magisk takes care to mount those changes to the /system when booting (initializing Magisk)

E g.,for BusyBox use the module BB Android NDK and uninstall all the old BB root apps you have experimented with
[Magisk] vandyman:
Try installing BusyBox into "systems/bin"

For some odd reason I have not been able to install BusyBox pro into xbin for a long time.
[Magisk] jnshk:
Thank you for the detailed response. I will check up on the 'read only' status of my system, as that may be the case for my device's software/firmware.

In this case, I've not bothered with a standalone BusyBox--I simply installed the BusyBox NDK module within Magisk, as well as the terminal systemizer module--and I am not using Titanium Backup. This all came about as I was trying to convert Tasker to a system app in order to give it more capability in order to perform a few automated tasks that I'd like to enable. Although I don't yet quite understand the implications of systemless, I was under the impression that as the system booted up, Magisk would load these modules and merge/mount them into the system so that they would be accessible once

everything was up and running? However, the contents of "busybox-ndk/system/xbin/" and "terminal_systemizer/system/xbin/" do not seem to get merged with the system and are not found/recognized by the shell--which is why I thought that perhaps something is wrong?

So is the ability to convert a third-party app to a system app essentially disabled with modern Android implementations? If the system configuration is locked and read only, in this case, how are system apps able to be updated? I will do some further reading on systemless in regards to Android to see if I can understand it better.
[Magisk] zgfg:
Check with some BB checker - as on the screenshot

My BB applets are installed to:

/data/adb/modules/busybox-ndk/system/xbin

and Magisk mounts them to /system/xbin
[Magisk] jnshk:
I tried changing the directory name inside the module from xbin to bin and it did not seem to make any difference. As before, the files did not get mounted to system/bin just as they had not been getting mounted to system/xbin.

My modules are also installed at /data/adb/modules/#module-name#/system/xbin, however Magisk does not seem to be mounting them to system/xbin. I checked status with a root+bb checker and it reports the device has root but not busybox.
[Magisk] pndwal:
Latest vvb2060 Alpha Magisk build

*** For Mavericks only! ***

Chinese Translated:

Magisk Alpha update log

7496d515-alpha

• [General] Based on 7496d515, the content that has been merged into the upstream is no longer listed

• [App] Correctly handle any data from magiskd

• [App] Support SharedUserld

• [App] Delete the backup file after restoring the boot mirror image

• [App] Built-in current version update log

• [App] Use the local version when you can't download the stub, now it can be used completely offline

• [App] Switch to Java 8 modern time APl

• [General] Add an obsolete cgroup v2 path

• [MagiskSU] If necessary, fall back to /dewpts

• [Busybox] Cancel optimization based on undefined behavior

• [General] No longer automatically unlock the device block

• [Magisklnit] Do not intervene when booting to DSU

• [General] Fix the flicker problem when the Windows subsystem for Android is running

How to install?

Install and load Magisk through the Magisk application. Generally, it should be done directly in the application. For special circumstances such as the first installation, the image should be patched and then flashed in with the fastboot/odin tool. Custom Recovery is not a supported method.

Update Journal

From 23.0 to 7496d515

• [General] Support pure 64-bit devices

• [General] Support Android 12 emulator

• [Zygisk] Code injection framework

• [General] Remove MagiskHide

• [General] Support Simulator to add modules

• [MagiskBoot] Support zlImage format

• [MagiskBoot] Add zopfhi encoder

• [Magisklnit] Support bootconfig

• [App] The repair installation function will now check if the script under /data/adb/magisk/ has been updated or not

• [Magiskini] Support some Meizu devices

• [MagiskSU] If the kernel supports it, use isolated devpts

• [MagiskSU] Fix the pts configuration code, now no additional sepolicy rules are needed

• [MagiskBoot] Support v4 boot image header format

• [Magiskinit] Supports oplus.fstab for some OnePlus and Oplus devices.

• [App] Updated modules to be restarted, not marked as pending deletion.

• [App] Deleted online repository library

• [App] Add mounting information to the saved log file

• [App] Suitable for Android 12 API level

• [App] Display the waiting pop-up window that is running when hide/restore the original app

• [Stub] Open source obfuscation function

• [Script] Check and display the sepolicy rule folder of the module.

• [App] When the window pops up, hide the screen and add layers. Android 12+ is required.

• [App] Delete the floating bottom bar and change it to a general bottom operation bar. • [General] Support compilation and cache

• [General] Add rejection list function

• [App] Delete DoH

• [App] Delete SafetyNet

• [App] Allow the log page to be opened when Magisk is not installed

• [App] Display Zygisk status, add a reminder to restart to take effect

• [Zygisk] Disable conflicting riru module

• [Sepolicy] Fix Android 8 terminal cannot get root

• [Sepolicy] Add execmem to allow hook in zygote and system_server

• [Resetprop] Erase the old content completely when editing/deleting

• [Zygisk] Public module API

👍 PW
[Magisk] arik100:
thanks dude, it works like a charm!

maybe they should post it in the FAQ, it's quite common
[Magisk] zgfg:
Did you try maybe?

There are pretty bad reports on TG...
[Magisk] J.Michael:
Is there anything in your module other than the directory tree you want overlaid?

In particular, is there a hidden file ".disable"?

Could you post the output of "ls -alR /data/adb/modules/module-name"?
[Magisk] pndwal:
Not yet! ... Having my dinner. 🍔🍟😛

Thanks for warning!... Other mavericks can try and report first...

Nb. Last build was a quick fix for prior (same day) broken release... Bound to happen I guess, they are test builds after all... PW
[Magisk] pndwal:
Interesting fix! (... and revealing?) 👀 PW
[Magisk] 73sydney:
Pretty lazy of you to release tease and run to dinner without testing :P

I think you know i wont be the maverick on this one :)

Interesting to read about the change to app listing earlier
[Magisk] zputnyq:
New canary (23010) from TJW has been released today.

I'm not really following development.

Does anyone know about the apps listed on denylist whether it is contained system apps or not ?
[Magisk] pndwal:
Haha... Actually I've often done that... Not teasing, just trying to get an Engrish translation up early as a public service for mavericks... and none of them need my endorsement, nor is it implied in any way...

Alpha use is on your own collective heads! ... Don't shoot the messenger!... Man up and own it!...

But if you don't, you're a wimp with no sense of adventure!

... a tease 🙄...

And what are YOU, a man or a mouse? 😁 PW
[Magisk] Didgeridoohan:
It does contain system apps. I just updated to the 23010 Canary, enabled zygisk and the Deny list. Added Play Service's gms and unstable (gms is necessary depending on your Android version) parts to the list and voilà: SafetyNet still passes.

I'm also using my MHPC module to set all the bootloader props, etc, that was removed from Magisk with this update. If you're using the Universal SafetyNet Fix that's included in that module already.
[Magisk] zputnyq:
Thanks I really appreciate it.

On my device running stock android 6.0.1 none of its system apps listed there. I tapped the arrow button on the upper right but stiil none of the system apps listed. Is it intended on device running stock android 6.0.1 ?
[Magisk] pndwal:
That's the wake-up call we all need! Glad I already ate. 😃

🎉🎊👍 PW
[Magisk] Didgeridoohan:
It doesn't show them by default, you have to enable that option in the search window.
[Magisk] zgfg:
If like on Alpha (expected to be), you have to enable Show System apps and Show OS apps. Then you must manually enable GMS (it's been described here couple of times for Alpha but you'll figure out when you enable/expand as above)
[Magisk] zputnyq:
Th

Thanks, that works
[Magisk] pndwal:
I think they are... But you need(ed) to select System apps from spyglass icon at bottom... 😜 PW

Edit: man my internet is slow on this bus... sorry for redundant advice...
[Magisk] pndwal:
Latest TJW debug (Canary) Magisk Changelog:

Magisk (d7e7df3b) (23010)

A new chapter for Magisk!

For those who missed my blog post, please check here https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Diffs to v23.0

[General] MagiskHide is removed from Magisk

[General] Support 64-bit only systems

[General] Support Android 12

[Zygisk] Introduce new feature: Zygisk

[Zygisk] Introduce DenyList feature to revert Magisk features in use selected processes

[MagiskBoot] Support patching 32-bit kernel zImages

[MagiskBoot] Support boot image header v4

[MagiskInit] Support /proc/bootconfig for loading boot configurations

[MagiskInit] Better support for some Meizu devices

[MagiskInit] Better support for some Oppo/Realme devices

[MagiskSU] Use isolated devpts if the kernel supports it

[resetprop] Deleted properties are now wiped from memory instead of just unlinking

[App] Build a single APK for all ABIs

[App] Switch to use standard bottom navigation bar

[App] Downloading modules the Magisk app is removed

https://github.com/topjohnwu/magisk-files/blob/9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md

...And all the best with it everyone! 🙂 PW
[Magisk] klemi71:
Safety net check is missing of course. Which app do you recommend to check if there will be problems?
[Magisk] 73sydney:
Take your pick:

GitHub - RikkaW/YASNAC: Yet Another SafetyNet Attestation Checker

Yet Another SafetyNet Attestation Checker. Contribute to RikkaW/YASNAC development by creating an account on GitHub.

github.com

or been around for ages:

SafetyNet Helper Sample - Apps on Google Play

Sample app to check if your device passes the Google SafetyNet CTS test

play.google.com
[Magisk] jons99:
YASNAC - SafetyNet Checker - Apps on Google Play

Yet Another SafetyNet Attestation Checker

play.google.com

riru don't work for me with the latest alpha
[Magisk] pndwal:
YASNAC!

https://github.com/RikkaW/YASNAC
[Magisk] edzamber:
Same here

S20 G981b

Same here, S20 G981b
[Magisk] esrvR:
Try this
[Magisk] midgarsormr:
I still can't login to pogo unrooted...so it must be the bootloader.
[Magisk] b.eslabon:
i have unlocked bootloader too (both my 2 sammy phones) but i can login in pogo (using stock rom and stock kernel) in both devices.
[Magisk] midgarsormr:
Frustrating me beyond reckoning. I cannot get it to work whatsoever.
[Magisk] Captain_Throwback:
Yes, my A9 passes SafetyNet. I'm using Magisk v8 with magiskhide enabled and the phh Superuser Magisk module. I'm also using my Magisk module to set verifiedbootstate to green.
[Magisk] zapahacks:
That's awesome!! Thanks a lot :)
[Magisk] b.eslabon:
return to stock :D
[Magisk] pnwsr6:
Has anyone seen an issue with installing a module? I have a issue where it gives me a toast notification telling me that the module I am trying to install is not a magisk module. It started when I installed v8, now it's doing it on v7. I have completely wiped and reinstalled everything, bootloader and all, and can't get magisk to install a module.

Nexus 6

Stock rom N

Twrp

SuperSU 2.78 sr1

Then install magisk v7

Magisk app

Then module that won't install.

I have verified SuperSU is installed seamless and working.

Any ideas?
[Magisk] H4X0R46:
That's awesome!!! It has potential and I'd love to see it through! Would this basically mean MultiROM would work on ANY device? I'm thinking like the OnePlus 2 never got a functioning MultiROM port, this might be the answer!
[Magisk] Sup3rN1c:
I'm sorry for my (probably) stupid question.

I've just followed the installation procedure with official SuperSU and Magisk Manager 2.1 and Magisk 8.

When I open Magisk Manager, I can see the three green tick (all updated), but I can't find the option/selector to root and unroot.

Please, could you help me?

Thanks!

Nic.
[Magisk] locolyric:
hi all,

i am using AICP rom ,root already included in privacy guard. How do i unroot this ???
[Magisk] Mudvayne622:
Very easily actually. Go into developer settings and scroll down to root and change it to disabled. Then do a reboot and you should be unrooted
[Magisk] Ninoh-FOX:
Verifiedbootstate is green for me (this it is for???) but this morning safetynet is blue and cigital is red... I have bootloader unlook.

Enviado desde mi E5603 mediante Tapatalk
[Magisk] napster113:
There is no option/selector to root and unroot in magisk.
[Magisk] Sillik:
Just so you know, I tried flashing SuperSu 2.78 SR1 + Magisk V8 + Xposed 86.6 alt on my Note 4 and got the bootloop again.

I'll try later with phh's superuser, but I'm unrooted for now as it seems to be the only way to play pogo for the moment...
[Magisk] goister:
I'm having trouble installing v8 on my Nexus 5 with PureNexus. I consistently get a boot loop which brings me back to the TWRP recovery once I reboot. I previously have v7 with MagiskManager 2.0 installed and it worked. If I revert back to v7 it boots up. I've tried wiping dalvik cache but didn't help.