yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
FWIW, I avoided installing Canary Magisk (3dc7d77e) (24304) and it's surprises.

Just installed Actions run Magisk (b1faa5ee) (24304) with:

- Update BusyBox …

topjohnwu committed 2 hours ago

- Proper support multiple modules adding same dir

yujincheng08 authored and topjohnwu committed 15 hours ago

- Fix xhook cannot hook app_process …

3 people committed 15 hours ago

Here:

workflow runs: Magisk Build

All working fine for me on RN8T incl. Viper4Android FX 👍 ... Hope we get official build soon, but may help others if adventurous! 😛 PW
[Magisk] martyfender:
Should I be able to switch to this from the magisk alpha without corrupting the magisk db?
[Magisk] VD171:
Google is just protecting their own work.

Even it is open source.

It's just an option.

But, every protection can be bypassed.

Just dedicate your time on it.

I love this game.

Good luck :)

If you really, really, really cares to what you said, you just need to have two devices: one rooted and one not rooted. Lol.

I've never had a problem with SafetyNet.

I never bothered with Safetynet.

I never had to fix the Safetynet.

Safetynet never made a difference to me.

I have more than 120 banking accounts (yes, more than 120).

ALL BANKING APPS ALWAYS WORKED PERFECTLY AND PROPERLY, JUST APPLYING SOME THINGS TO HIDE THE ROOT (since Android 4.4, now I'm on Android 11).

Everything is a matter of how much you will strive.
[Magisk] martyfender:
A new Magisk b1faa5ee-alpha has been released.

# alpha changelog

## Magisk (b1faa5ee-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [App] Added crash statistics

- [App] Allow loading zygisk modules

- [General] Signature Verification

### how to install?

Install and uninstall Magisk through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, you should use the fastboot/odin tool to flash it after patching the image.

By customizing Recovery is not a supported way.

# Upstream changelog

## Magisk (3dc7d77e) (24304)

Fixed several compatibility issues with `magiskinit`

## Diffs to v24.3

- [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

- [MagiskInit] Introduce new `sepolicy` injection mechanism
[Magisk] martyfender:
{Mod edit: Quoted post has been deleted}

Fixed
[Magisk] pndwal:
Nb. I've added link to this. 😝

Maybe, but I wouldn't... Unsure if compatible now, but past builds haven't been...

I'd install App then take Magisk Direct Install but delete all contents of /data/adb (can leave module files if you can identify all of them) before reboot and they'll rebuild.

Well done: I was using Google Translate too...

👍 PW
[Magisk] kk100:
Hello,

Can you Please share how to Run banking apps. It would be great if you could prepare a short Guide which non developers can follow. This is my post link.

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

Best Wishes
[Magisk] martyfender:
Yes, these release notes don't show any of topjohnwu's recent fixes, I'm not sure how to include them?

Thanks
[Magisk] VD171:
There is no guide about how to run a particular app or another.

You should keep trying while you don't get the desired results.

Please, read:
[Magisk] kk100:
Thanks very much for taking time to reply. I wish there were some guides for non developers.

Best Wishes
[Magisk] chinitopex:
It's just a doubt, or question about the magisk, why can not root the samsung A20s-207M,F not support
[Magisk] VD171:
Each app can have a new detection method.

As new apps are constantly updated, hiding methods also need to be.

There will never be an easy guide for hiding root.

But there is a short guide: "keep trying" :-p

In this reply, I describe in short how you can hide root, if you don't have any other xposed/magisk module that undo the hiding methods:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/post-86427499
[Magisk] HippoMan:
I believe that the game is indeed hopelessly lost as long as we are looking for software-only solutions.

I think that the way out of this ever deepening rabbit hole requires a combined hardware/software solution.

My dream is for someone to develop a totally "dual device" which goes beyond the current A/B architecture. This would involve two CPUs, two completely separate RAM blocks, and two distinct instances of *everything* except the SIM card, the screen, the external connectors, the hardware buttons, and some shared storage.

Each of these two instances would be a fully functional Android device.

This would be packaged within a single case, and the user could go back and forth between "sides" by means of a hardware switch which would connect the shared components to one "side" or the other.

One "side" would have a stock Android OS without any rooting. Games, banking apps, and any other software which would be crippled on rooted devices would live in this "side". The other "side" could have a different OS installation which is rooted and has all the normal, useful apps that benefit from rooting. On that second "side", it won't matter if SafetyNet and other mechanisms cripple certain apps, because that subset of apps could be easily run simply by flipping the hardware switch and going to the other "side".

The OrangeFox recovery offers dual boot on certain A/B devices, but this is a software-only mechanism which is still susceptible to Google's device-crippling techniques.

Of course, this dream device does not yet exist, as far as I know. But trying to get something like this created seems to me to be the only way to have more than a snowball's chance in hell of winning this cat-and-mouse game.

It's exceedingly unlikely that this dream of mine will come true, and so as far as I am concerned, rooted Android is pretty much dead.
[Magisk] VD171:
That's a very, big and excessive waste of resources.
[Magisk] pndwal:
I think they do! 😜

Upstream Changlog section shows this Alpha is synced with (built from & including commits / fixes from) Canary 24304, and notes earlier Canary changes differing from last public build, 24.3... 😛 PW
[Magisk] shadowstep:
Just a few minutes back I decided to see if I too got a bootloop with the Canary 24304, and I did. But thanks to your post, I knew exactly what to do to fix it, so thanks for that! The V4A I use uses code from AML too. Back to Canary 24301 that I was using before and all is good! (y)

Spoiler content hidden.
[Magisk] dr4go:
Upgraded without any issue, Samsung Galaxy S10 (G973F), Android 12.
[Magisk] pndwal:
May also be fixed; V4A fine for me w/ this latest TJW test run build, but I haven't had AML installed for a while:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86619257 PW
[Magisk] AndDiSa:
I agree fully ... probably the new virtualization feature of Android 13 can be of help.
[Magisk] VD171:
May you explain more about that, please?
[Magisk] AndDiSa:
@VD171 some additional info's can be found in the XDA article or more deeply on this article

As there is the chance to run e.g. other Linux distributions or even Windows 11 on such a device it should be quite easy to run another Android installation on it. Only as an idea ...
[Magisk] kk100:
Thanks a lot for your Support. I will see the guide and try my best to follow it.

Best Wishes
[Magisk] VD171:
Omg, I kill myself first before to use Windows.
[Magisk] pndwal:
Wow!

Win11 on Android w/ root is here!

Windows on stock Android devices coming soon!

Danny (@kdrag0n) already playing Doom in Win11 on Pixel 6 w/ Android 13 Developer Preview at near-native speed with root thanks to Google's new Protected Kernel-based Virtual Machine (They plan to ship pKVM with Android 13).

And, if Devs like him keep working on cross-platform compatibility, apparently Win11 on stock Android devices (non-root implementation) is coming to us soon! ... just as soon as a virtualization monitor management app (requesting a special permission) is built or simply ported from existing VMs like Google’s crosvm and Amazons Firecracker.

I'll be in! ... not for Doom but... 😝

Worth noting, root (read Magisk) is what facilitates / enables development like this, even for stock device use... and Google know it. (Read Google want Devs using root / SELinux permissive! ... otherwise users would never get stock innovations w/ Security-Enhanced Linux enforced...)

Thanks! 👍 PW
[Magisk] klemi71:
Off topic but really interesting:

A really good Magisk module if you don't know where your storage disappears as time goes by is TrichromeLibrary Squoosh by entrOpia (search for it on GitHub). It removes outdated TrichromeLibrary as Google does a poor job here and leaves masses of remains each time TrichromeLibrary is updated (Chrome, WebView). In my case it freed up 17 GB as I use canary versions. Up to now not even SD Maid does this job.
[Magisk] Denny@83:
Hi, I have a problem with magisk installation, since version 24303... the device is Redmi Note 8 (magisk installed in recovery); custom rom (Arrow OS android 11)

I update the app, then select direct installation in recovery (it is the only option for my device), but after next reboot Magisk remains on version 24302..

how to fix? expect another release or try to flash .zip file in twrp recovery?
[Magisk] MerciLess_6395:
Well I know Vivo Phones are **** but still I can't afford to buy a new one. I need help unlocking my bootloader if there's any way possible or if anyone else knows someone that can help please help me🥺. New to XDA so don't how reply and discussion works. Thank You🥲 and I forgot to tell I have a Vivo Y12s PD2060F
[Magisk] VD171:
Linus Torvalds likes it.

:ROFLMAO:
[Magisk] heinhuiz:
I'm seriously looking at the Pro1 X. With Ubuntu Touch then, obviously.
[Magisk] VD171:
If ubuntu doesn't need apt then it might probably work well.

:ROFLMAO:
[Magisk] J.Michael:
There's a forum for random questions.

There may be a thread dedicated to your device.

Googling " unlock bootloader pd2060f " returns lots of hits.

This one from droidwin rambles but claims to describe how to unlock the bootloader. I don't use fastboot, so I don't know if "fastboot bbk unlock_vivo" is a plausible command, or if it requires that you have a script named "bbk" or "unlock_vivo".

Unlocking the bootloader probably requires erasing all data. Are you ready for that?
[Magisk] zgfg:
Simple googling for "unlock bootloader vivo" finds a dozen of guides

Don't know do they apply to your model - best you read and check for which models are the guides

There is even a thread on XDA:

https://xdaforums.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/
[Magisk] ASIKMKHAN222:
I have a Vivo Device,

Boot.Img have init.rc but doesn't start on boot so systemless magisk root didn't work.

How can i start init service at boot or how can i add magisk in system.img
[Magisk] MerciLess_6395:
Vivo

Well I can take backup of the data no issue with that.🙂
[Magisk] MerciLess_6395:
I have tried googling but the method including the fastboot command didn't work and in the unofficial one i didn't quite understand the process 🙂
[Magisk] J.Michael:
How "didn't work"?

What are you calling "the unofficial one"? At what point do you not understand the "process"?

When I scanned the page whose link I posted I did not notice that it requires a special "fastboot". Reading the first post in the thread provided by @zgfg makes it clear that you need to get a special fastboot to be able to use the fastboot command indicated. That first post also indicates that an alternate command might work. There is some mention of needing to upgrade your device software before unlocking the bootloader.
[Magisk] ParteOjetes:
I just updated to magisk 24.3 and my phone is stuck rebooting and can't access recovery, any idea?
[Magisk] pndwal:
mmm. I avoided installing this Canary (3dc7d77e) (24304) due to bootloop reports, however I installed latest TJW Actions run Magisk (with fixes for testing) (b1faa5ee) (24304):

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

on Redmi Note 8T and it's working fine! 🙂 PW
[Magisk] HippoMan:
... which is one of the reasons for why I said that this dream of mine is unlikely to be realized.

... and for why I believe that root under Android is pretty much dead.
[Magisk] VD171:
An undead can live for a long :cool:
[Magisk] salman.khan1:
I have a query. How does Magisk DenyList work ? I had a look at the code its in C++ being an android developer I have no clue how it is able to bypass root access on my application
[Magisk] m0han:
i saw this page: https://github.com/entr0pia/TrichromeLibrary-Squoosh#readme

couldn't figure out how the module is to be used (after flashing through manager app) and how the results are displayed. and, does it work on android 12 and up?
[Magisk] klemi71:
Just flash and reboot. As files are in system and write protected, deleting is done on reboot, so reboot will restart automatically (normal behaviour, don't panic).

I wrote PM to developer and immediately module was updated to take care of beta, dev, canary versions, too. This shows development is active. Adjustment to new Magisk version was already done before.

Is it reliable? It works on my Android 12 - if it will be necessary in future? If Google does a better job, it won't. 🤷🏻‍♂️

To see the results, do a root (!) search for *com.google.android.trichromelibrary* before and after flashing/rebooting and compare the size of the elements found.

Easier, but less detailed: check your devices storage information for system size before and after flashing/rebooting.

Without root access users usually just accept that their system gets bigger as time goes by and do a factory reset to regain storage. As I mentioned, the module saved me from having to do this.

By the way: maybe complain in playstore. The more people complain about the issue, the faster Google may fix it. 😬
[Magisk] pndwal:
So you equate root with hiding 'root' / passing SafetyNet?!...

But that was just a bit of fun for John; root is about much more than running bank apps!... 😜 PW
[Magisk] zgfg:
Thanks for the info about the module but I usually clean from time to time the old trichrome libs manually

Eg, with this pretty primitive query in Terminal, I can see their paths and lib versions

su
cd /data/app
ls -lR | grep trichr | grep ==:

As on the screenshot, I didn't clean for two months and now I have 5 versions of the trichrome library installations:

484407334

475808734

469209834

484405834

475810134

Obviously, 484407334 is the highest/newest, while the others can be safely deleted by eg MiXplorer (root explorer)

Btw, each corresponding folder is about 110 MB, hence for 17 GB (your case) it would take about 150+ old lib versions, hence maybe 5 years to collect them without cleaning the house or ever factory resetting or so (?!)
[Magisk] klemi71:
As I mentioned I use canary version. It's updated rather often. 17 GB accumulated in around one year.

Thanks for your hint, this way is fine, too. You just have to know about this issue to do it manually.

Do you have any further tips for cleaning manually? I use to rely on SD Maid for keeping my phone clean. 🤷🏻‍♂️
[Magisk] VD171:
Magisk DenyList does NOT bypass root access.

If magisk applies any setting to any other fake value, enforcing denylist will just revert that setting to the original value.

Just it.

Magisk DenyList is NOT a replacement for magisk hide.
[Magisk] pndwal:
No, but DenyList can indeed be utilized for "hiding" purposes! 😛 PW
[Magisk] VD171:
Enforcing denylist does NOT work for hiding.

Magisk keeps EASILY detectable even enforcing denylist.

Enforcing denylist should be avoided for everyone.

Everyone should use the wonderful module: SHAMIKO for hiding purposes.

Shamiko official website:

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] HippoMan:
Well, sort of. I used the word "root" as shorthand for ...

I don't care about hiding root and passing SafetyNet per se, as long as there is some way for me on my rooted device to run the apps that I want to run without them being blocked or crippled.

If that can be accomplished somehow without root hiding and without SafetyNet, then I'm fine with that.

It's mildly pleasant to know in an abstract sort of way that root can exist on my device, but its mere existence alone is meaningless. Root also needs to be usable ... and without lowering the capabilies of my device. What's important to me is that I can run with full rooted capabilities and without root's existence preventing me from running all of the applications that I want to run.

The purpose of root is to allow users to have more capabilities on their devices, not fewer.

Of course Google and app developers have the right to cripple software running on Android devices if root or other mods are present. And sadly, I believe that over time, this will be happening more and more, with increasingly fewer ways to bypass it.

I hope I am wrong, but I wouldn't bet on that.
[Magisk] VD171:
Google is just doing what everyone should do: avoid newbies and kiddies.

Everything else is bypassable, as long as there is commitment and dedication.
[Magisk] pndwal:
Well, I didn't say it replaced MagiskHide! 😛... I said:

John put it this way:

www.twitter.com/topjohnwu/status/1445598601372069890

Actually, both modules and users can 'utilize the DenyList feature for "hiding" purposes'.

Some pre HKA devices as well as later OnePlus models can pass SafetyNet simply with SafetyNet GMS process added by user and denylist enabled, and possibly some changes to sensitive props.

Shamiko and Universal SafetyNet Fix are examples of 'hiding' modules that 'don't actually rely on DenyList for hiding; they do everything themselves' however. (Nb. Shamiko does make use of denylist as a list only for convenience, ie. this eliminates the need for its own dedicated configuration list).

🤠 PW
[Magisk] pndwal:
Somehow I knew you'd reply like this! 😜

But really root doesn't diminish your options / devices capability at all, and does in fact increase both!... It's an individual app's / Dev's code that is preventing the functionality you want and 'cripling' software; root is actually empowering you to subvert the detection of unlocked bootloader and other suspicious traces that an app may flag for its purposes, and when Google swing their own big HKA-full-deployment hammer this will remain the same!; individual app's / Dev's code determines functionality allowed, not Google's SafetyNet or Play Integrity APIs...

Also, root will still increase your devices functionality when that happens; those apps will still report "root detected" even when there are no root privileges as the term is used loosely / erroneously and, in fact, your unlocked bootloader is what first breaks the 'chain-of-trust'. (Root's existence will not prevent you from running 'all of the applications that [you] want to run'.) AVB (Android Verified Boot) and the kernels dm-verity (device-mapper-verity) simply can no longer be fudged for SafetyNet or Play Integrity purposes.

So root is not actually detected at all by these APIs, and will still increase functionality / device capability for unlocked devices. Some types of hiding (hiding in userspace) will still be viable also...

So for anyone using a custom ROM or other custom mods (many don't root), rooting will certainly continue to "allow users to have more capabilities on their devices, not fewer". Root will still give these users powerful modules, root app functionality and more... not less! (Think Viper4Android, root explorers, etc.)

Really, presence of root / Magisk will never be the issue!; Your beef is really that hiding mods' specific ability to subvert banks' / Google's Security models (particularly attestation to a Trusted Execution Environment stemming from secure boot for running code in an A[pplication] P[rogramming] I[nterface]) by exploiting fallback modes, faking keystore and other means will be patched!... securely and properly. 😝

Also, root gives all more powerful devices, incl. those with stock environments... Most great innovations are developed with root. Video apps like Newpipe and VLC come to mind, also enhancements Google has integrated like Move2SD / App2SD (Adopted storage) and more...

And what about @kdrag0n playing Doom in Win11 on a Pixel running Android 13?!... Coming soon to your stock device when you finally give up on root / custom ROM / mods in order make contactless payments for your bagels with the NFC-enabled soc you spent your hard-earned cash on... What a choice Hobson. 😝 ...

So is root really 'dead'? Is the Magisk community Doomed?... I'm sure HKA deployment will shake things up and a few will let go, but I'm personally confident root / Magisk will survive and strive!... if simply because it is much more than a tool for security model subversion. 🙃 PW
[Magisk] fubo73:
Hi, I tried to install Magisk 24.3 from TWRP 3.6.1 and TWRP 3.6.0 on G900F (klte) running LineageOS nightly 20220320. It always failed with "Cannot mount /system".

I tried many things like reinstalling lineageos and TWRP, in the end I was able to install 24.0 without issues and update using Magisk app. I cannot find if it was already reported, has anyone experienced something similar? It seems related to this release (I didn't try 24.1 and 24.2).
[Magisk] dimm0k:
hoping someone has some tricks up their sleeve, but I'm currently up a river without a paddle. installed a module, specifically the MoreNotifications module by Tulsadiver on my Google Pixel 6 Pro running the March update with the latest version of Magisk and now my device is stuck in a vicious bootloop. the phone boots up, flashes the lock screen wallpaper a few times before rebooting. things I've already tried with no success

- tried booting into safe mode to deactivate Magisk, but exhibit same flashing screen before it reboots itself

- I believe safe mode did deactivate at least some of the Magisk modules as my other installed module that changes the battery is no longer in effect (I see the default battery look)

- tried flashing the stock boot image

- tried flashing the March update without -w

- adb seems dead in the water... no devices listed when in fastboot and the brief moment in safe mode adb detects the device, but is listed as unauthorized

any suggestions before I do a complete wipe? ...feeling nauseous
[Magisk] adgob:
Anyone have issues with apps that tie into the camera getting blocked? The United app uses the camera to scan for documents and gets an authentication error when rooted. I've tried to hide google play services, the camera, and the United app itself, but still get stuck. I tried unrooting and it worked fine, so there's a module it's accessing that I think needs to be blocked. I can use banking/google pay no problem.

Stock android 13 on a Pixel 6 Pro, running latest Canary with latest UNSF.
[Magisk] Denny@83:
thanks, for your reply. how can I install actions without updating magisk? (I tried to search but didn't find a guide for that...sorry but I'm a newbie)
[Magisk] zgfg:
IMO, this is not for newbies

Who has GitHub account (and be familiar to use GitHub) and experienced in switching through sorts of Magisk would figure out and make himself in 10-15 minutes

Writing useful guide for a newbie would take 45 minutes or more - with a good chance that newbie will have additional questions about particular steps, that he messes up and will need help, etc

In short:

- MUST have GitHub acc

- From Actions download a zip, from zip extract Magisk app

- Since of diff signatures, you will probably need to uninstall your current Magisk app and turn off Google Protect

- Then, install Magisk as you usually do for your device (more details were in this thread, on Magisk GitHub page, etc)

If THAT is enough for you and you are ready to experiment, and you know how to handle if something goes wrong - good luck

Otherwise (don't ask me for more details) a goodwill advice: wait for the next Magisk (Canary) release
[Magisk] rbouza1:
Use the android flash tool