yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Vanced, for their YT hack require turning off MIUI Optimization - fortunately, it is not actually needed there

However, two or three years ago I did it and by results my home screens were messed as well as certain permissions for all applications were reset

Google about and check did you have effects on your side

Anyway, the last two days I did my test for hiding/unhiding with the default MIUI Optimization On, and on my both phones I was not (fully) blocked to hide like you

---

Btw, my two Xiaomi phones are on MIUI 12.5 - I see, you are on 12.0.4

Instead of switching MIUI Optimization off - try with turning on Install from USB (also in Developer options, but closer to the top)

That did the trick for Vanced, without the need for switching MIUI Optimization off (and suffering the troubles by turning it on/off)
[Magisk] pndwal:
Yup, lost auto-fill settings (of course) and some permissions need setting again... So far so good otherwise! But I only disabled it, hid Magisk app, and enabled it again...

Homescreen is fine; all shortcuts, widgets, Icon groups are as they were... I'm using Smart Launcher 6 however...

Yup, 12.5.2 has been available for a month or so now (it stayed in beta for a long time for RN8T), I will upgrade soon; just haven't bothered yet... Still on 12.0.4! 🤪

Tried that and reported to you earlier as I said I would:

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

- didn't work for me. 🙁

mmm... Anyway all good for me so far but...

Still hope devs find a better bypass for this MIUI issue anyway; ticket is still open...

You may want to comment there re. symptoms for 12.5 MIUI as these are clearly different but also unexpected, and it seems some change (regression?) is affecting many MIUI devices, updated or not... PW
[Magisk] pndwal:
And we now have a tentative fix:

Add root install back #5522

as well as tacit proof it's a regression... 😛 PW
[Magisk] Stillhard:
Kopine endi... Angry girl works fast

Randomized Magisk App Crashed
[Magisk] Randomginger:
Ok, on next update I'll get the fresh boot.img and do it that way. I've never had any issues with patching the original boot.img from the ROM as I didn't think it would change with an update.

I can follow instructions and get things working, I don't understand what's going on under the hood though. 😉

I think the next Los 18 update will be released over the weekend.
[Magisk] Randomginger:
Pndwal - legend.

Turns out I was using a May 21 boot.img every update since then. Today I extracted the boot.img from latest lineage and patched in magisk, dirty installed and it fixed everything. Phone is like a new device again!

Lesson learnt here.

Thanks again to this awesome community and special thanks to pndwal for your advice.

(y)😁
[Magisk] badabing2003:
Hi All

I have the latest magisk canary installed on my Pixel 6,

Is there a way through command line adb to invoke magisk patching of a boot.img file (no UI interaction)

Could this be done? if yes, could it be done with already installed magisk or additional tools need to be installed?

Thanks
[Magisk] badabing2003:
ok figured it out, the tools are already installed.

adb shell "su -c 'export KEEPVERITY=true; export KEEPFORCEENCRYPT=true; ./data/adb/magisk/boot_patch.sh /sdcard/Download/boot.img; mv ./data/adb/magisk/new-boot.img /sdcard/Download/patched-boot.img'"
[Magisk] pndwal:
Latest Unofficial vvb2060 Alpha (For mavericks only); Chinese translated:

# alpha changelog

## Magisk (e51aacb0-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

- [MagiskInit] Refactor the processing method of two-step startup

- [App] Added crash statistics

- [Script] Support init_boot partition

- [App] Allow loading zygisk modules

- [App] Try root installation first

- [App] Fixed crash on direct launch

### 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

## 2022.3.1 Magisk v24.2

Maintenance release fixing various issues.

- [MagiskSU] Fix buffer overflow

- [MagiskSU] Fix owner managed multiuser superuser settings

- [MagiskSU] Fix command logging when using `su -c <cmd>`

- [MagiskSU] Prevent su request indefinite blocking

- [MagiskBoot] Support `lz4_legacy` archive with multiple magic

- [MagiskBoot] Fix `lz4_lg` compression

- [DenyList] Allow targeting processes running as system UID

- [Zygisk] Workaround Samsung's "early zygote"

- [Zygisk] Improved Zygisk loading mechanism

- [Zygisk] Fix application UID tracking

- [Zygisk] Fix improper `umask` being set in zygote

- [App] Fix BusyBox execution test

- [App] Improve stub loading mechanism

- [App] Major app upgrade flow improvements

- [General] Improve commandline error handling and messaging

(Changelog from source .zip.)

🙃 PW
[Magisk] Homeboy76:
@pndwal

This is the March 1, 2022 Update.

I thought the

Magic

(e7c82f20-alpha) was a

new version of alpha

, not a

typo

.

The next time I wake up from a nap,

I'll make sure I'm fully awake before I Post anything on XDA

. :ROFLMAO::ROFLMAO::ROFLMAO:

There is a newer update Magisk Alpha

---------------------------------------------------------------------

March 2, 2022

Magisk alpha

app-release.apk

10.5MB

e51aacb0-alpha.zip

11.3 MB

5.0K views 09:42

Magisk alpha

MIUI devices may fail to hide/restore the Magisk app after upgrading to official v24.2. This is a problem with the MIUI system itself. Please report the PackageInstaller API to MIUI ( https://developer.android.com/reference/android/content/pm /Package

Installer ) does not work properly.

Temporary workaround: Turn off MIUI optimization and try again.

5.7K views edited 11:28
[Magisk] pndwal:
Actually it is; it's Feb 17 build!

But well spotted, and my bad; Latest is actually March 3 build e51aacb0-alpha

https://github.com/vvb2060/magisk_files/commit/564783f51a520e3f2c8a3da4c65b0ef97d0a9ac4

The version / version code are updated here, but 'notes' hasn't been and is still pointing to notes for latest in main https://github.com/vvb2060/magisk repo, which is e7c82f20-alpha

I'll fix that bad post shortly! 😜

Yup, this a reference to workaround suggested in the issue I raised re. broken 'Hide the Magisk app' function in some Xiaomi / MIUI devices. See here:

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

👍 PW
[Magisk] Homeboy76:
You're, absolutely, correct Magisk e7c82f20-alpha was February 17, 2022.

I'm awake now and the latest Magisk alpha is March 2, 2022.
[Magisk] pndwal:
But we're way ahead of you down-under 😜... We wake up first too, so for us it was a day late, March 3! ... Timezone makes a difference too!

BTW, my update post is now fixed to properly show changes for e51aacb0-alpha...

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

👍 PW
[Magisk] Homeboy76:
:mad: Yeah, I guess XDA being used by a multinational group would create a time difference. I apologize for my one-sidedness thinking. :confused:

Appreciate you updating the information. :)(y)
[Magisk] pndwal:
Under the hood Devs are pushing bug fixes, enhancements, regression fixes etc through updates... Many of these are in the kernel.

The kernel resides in your boot image! - (Boot Image usually contains kernel image (like zImage file) and ramdisk. Sometimes it can contain additional binaries.)

The kernel gets much attention from good Devs... It manages your phone’s CPU resources, the system memory, and the system devices (including the file systems and networking). It is also responsible for managing all the processes or tasks that are running.

Many 'handshakes' are made between system and kernel and for many system fixes to work, corresponding changes in the kernel are also implemented... This means that if you run an older (mismatched) kernel you will clearly have issues with functions it controls including comms, audio, GPS, camera and much more...

You really want to avoid doing this! - Magisk leaves kernel untouched and installs in ramdisk, but it can't control which boot image you choose!

Ok... Hope it works for you then...

Wow... You did all that in 3 minutes! 😀👏🎉... Who's a legend?!

Glad to help. PW
[Magisk] Randomginger:
Not quite 3mins. I think there was some sort of black hole that my posts were whirling around in.

Thanks for the explanation, it makes perfect sense. I'm an electrical engineer, not a software dev, so I am just playing with this stuff, quite successfully though.

I've also fixed most issues on the wife's Mi 8 for the same reasons as I had issues. I'm now level 1 at extracting images from payload.bin in python.

Thanks again
[Magisk] pndwal:
I'm a roofer... 😁

Same same ... I hope...

I've only read about that! 😜 PW
[Magisk] pndwal:
Just a thought; do you run custom recoveries on either phone?

If LOS recovery, I'm not familiar with it, you could check, but if like TWRP, you could take update as before and then make backup of boot.img to patch / flash... Or just rename magiskxx.apk to magiskxx.zip and flash from custom recovery... Just alternatives to python script extraction for your weekly builds...

Otherwise, just train your wife in level 1 image extraction from payload.bin in python... And file transfer, Magisk app updating, boot image patching and ADB fastboot flashing... Never know, she might do a better job than you! 🤪 PW
[Magisk] zgfg:
Ref @Randomginger (?)

To extract boot.img from payload.bin, use PC tool Payload_Dumper (I also use now for the new Xiaomi firnwares) - find the Payload Dumper thread on XDA (I don't remember did I find that for OnePlus or where)
[Magisk] williamsbertoldo:
There's some module to block status bar pull down action on lock screen ? Android 10 Motorola One (doesn't have this option)...
[Magisk] pndwal:
I saw @osm0sis has these I'm his OP:

Thread '[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]' https://xdaforums.com/t/tools-zips-scripts-osm0sis-odds-and-ends-multiple-devices-platforms.2239421/

Scripts:

97-dumpbootimage.sh addon.d+addon.d-v2 script (many devices) - attached

For ROMs with boot.img inside an OTA payload.bin or otherwise inaccessible, it dumps the updated boot partition before further modifications (TWRP, Magisk, etc.), saving it to /sdcard/Download/boot.img or to/from other customizable locations at the top of the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.

Other:

Payload-Dumper-Go for Android Magisk Module (many devices) [with ssssut] - link

payload-dumper-go arm compile and wrapper for use extracting from payload.bin on-device.

👀 PW
[Magisk] zgfg:
I use the following, not sure where did I get:

6.44 MB file on MEGA

mega.nz

At the first glance doesn't look like rhe above but any is good if it dumps
[Magisk] R0298:
How to go back to version 23.0?
[Magisk] unknowndrop:
Hi,

Just a quick question. Does snapchat work under magisk? I want to root it only to use a root adblocker.

Thank you.
[Magisk] 73sydney:
Are we posting payload dumping tools?

One for Win64 - No Python Needed

payload_dumper-win64.zip | Tool by geminids14 for Utilities

Extract payload.bin in xiaomi weekly build zip for MI A1

androidfilehost.com
[Magisk] Randomginger:
Let's not get off topic
[Magisk] Captain_Throwback:
Yes.
[Magisk] edyny1:
I have an unlocked bootloader
[Magisk] royaLred:
Hi.

Can you give me the Link for xsetprop zip?

Still can't find it.

Gesendet von meinem SM-G935F mit Tapatalk
[Magisk] h4mmer4:
Magisk v8 and r266 hidesu flashed

I enabled magisk hide and disabled superuser access in superuser

Still failing safety net

Can't add a card in android pay

Can't login to Snapchat

Ideas?
[Magisk] Timster292:
Hey Guys! I own a rooted OnePlus One and for the last days I've searched for a way to play Pokemon Go again and I stumbled upon this. I tried to install everything properly following instructions but it still doesn't work. My phone was running on Sultans CM 13 with Xposed Xposed Framework. To use Magisk I simply unrooted and deinstalled Xposed, then flashed magisc v8 and the superuser version that was recommended. Then I installed Xposed again and enabled Hide in the Magisc Manager. But even after several restarts and the use of Auto Magisc I still can't login or pass the SafeNet test in Safety Net Playground. Could somebody tell me what I'm found wrong? I really want to play the game again...

Thanks in advance!
[Magisk] mobileman88:
What device are you using? Some will fail because safety net checks for unlocked bootloaders
[Magisk] Timster292:
Whoops
[Magisk] h4mmer4:
Htc m9 developers edition, s off

Team venom custom Rom

So I need to just figure out how to relock my bootloader?

Or fool it into thinking it is locked at least.
[Magisk] drmpk:
With magisk v7 and magisk manager 2.0 i used to see a supersu helper module in the list of modules when magisk was being used with systemless supersu.

Now i started ftom scratch, i flashed stock rom, followed by twrp, then systemless supersu, magisk v8, and magisk manager 2.1. But now i don't see that helper module i used to see earlier. My phone works fine and rooted. I don't care about safetynet.

Why is the helper module missing?
[Magisk] Captain_Throwback:
http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post69291614

Wrong root zip. You should be using the phh Superuser Magisk module.

Xposed trips SafetyNet.
[Magisk] Captain_Throwback:
Because it's not needed anymore.

Please read the release notes in the official Magisk release thread.
[Magisk] wtcheesecakes:
Su binary not found when using magisk hide
[Magisk] andrew2432:
Gotta start from a phone that passes sn to start with. If you aren't passing, you need to make sure your bootloader isn't tripping it, your boot image needs to be original, remove system root files, and some other here and there issues. You need to get it to pass after removing root and stocking your boot image. If you can pass with a cleanish phone you won't with these fixes. You MAY need to put you phone all the way to stock again to make sure you pass.
[Magisk] Techy4198:
So I was super stupid and didn't look at the note about this not working on Sony devices... And I soft bricked my phone. Xperia C4 by the way. How do I get it out of this situation? Currently it bootloops on the Sony logo, and won't even let me access recovery (TWRP). Fastboot and flash mode both still work though.
[Magisk] roshan_shahi:
Not able to flash xsetprop zip. Ends with error.
[Magisk] Captain_Throwback:
You tried from within Magisk Manager? Also, where's the log?
[Magisk] andrew2432:
[MENTION=373298]Techy[/MENTION]4198

Keep trying your button combo, sometimes it will get you there still. Hold power and get it to shut off and not rebooting and try the button combo there.

You may need to find a pc flashing program to put you back to stock :( not fun but if you can get download mode you can basically save it still and always. For LG we use LG flash tools, for Samsung galaxy we use Odin. Not sure what yours is called, search it, find your exact model and variants stock tar or zip or however yours deals with it, smack stock back on, start from scratch. Install your recovery and load up a backup you hopefully have from before doing magisk??
[Magisk] Techy4198:
[MENTION=7785649]andrew2432[/MENTION] Have tried button combo a good 20-ish times. No luck, it just hangs at the bootloader. I put it into fastboot mode and used it to reboot into system, at which point it just stuck on the fastboot screen but disconnected from PC. I have a TWRP backup from last week, which is recent enough for me. Sony flash tool is apparently just known as 'Flashtool' by Andyroxyde, trying it now.
[Magisk] Fedroid:
I have a Huawei P8 Lite Magisk V6 works fine for me.

But installation on a clean rom and boot image of V8 gets on an unrooted rom.

If I install over systemless SuperSU root privileges are lost after reboot.

If I install first V8 and then systemless SuperSU the same.

I don't know how to proceed now....

My device works fine with SuperSU and hidesu 0.55.

Thanks in advance
[Magisk] mrxtc89117:
There seems to be a problem with magisk v8 on some devices losing root. Search for magisk-v8_mod2

I had the same problem.
[Magisk] Stillhard:
Nah, they won't, just let them dance(s) once a while, they deserved some
[Magisk] Randomginger:
I have lots to play with now 😊

I'm just aware that this thread goes wayward every now and again and I don't want my lack of knowledge to be responsible. I've been a member on here for a few years now and usually (eventually) find what I need without the need to post.

I find scrolling through the unhelpful and unnecessary posts quite annoying.

A bit like this has current one has turned out to be. 🤣

I do like how helpful to my cause everyone is being though, trying to keep this Razer Phone alive!
[Magisk] rodken:
Off Topic: Sounds like a 'Social Media' issue to me - especially for folks on Telegram.
[Magisk] zgfg:
This is actually the one I gave a link from my Mega cloud - thanks for the lost source

Btw, my payload.bin is about 2.5 GB, it takes several minutes to dump/extract on the poweful laptop - I wouldn't even mind trying some dumper scripts/modules, for the phone
[Magisk] contwerper:
Hi guys, I'm extremely lost with regard to Magisk. I have absolutely no clue how to install this, despite going through all the available documentation, install guide, and browsing all relevant threads on XDA.

If anyone can help and walk me through it, I would appreciate it.

(I'm using Poco X3 NFC and just flashed Lineage OS 18.1)

Thanks.
[Magisk] pndwal:
You really need to do do Complete Uninstall of Magisk (option 2 in Uninstall Magisk from Magisk app) to go from Zygisk generation Magisk to pre-Zygisk due to incompatible configuration files incl. magisk.db.

Nb if this fails, ie. something is borked, you may need to delete contents of /data/adb using a root explorer or TWRP etc. You can also remove any data/magisk_backup_xxxxxxx files. Do not reboot to system after doing this as Magisk daemon will recreate the file structure if you do as Magisk is still installed in boot image.... If, for example, you used TWRP and need to boot system, flash un-patched boot image (may be a recovery image if device is A-only legacy SAR) first.

Next, download 23.0 apk from Releases in Magisk GitHub main page and fresh install Magisk as normal. (See John's Installation Instruction page.)

Nb. You will need to set / use Custom Channel to successfully 'Hide the Magisk app' due to standard URL channel using JSON that always points to Latest builds and therefore fetches latest (not backward compatible) stub file. I gave settings here:

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

🤠 PW
[Magisk] pndwal:
Really, John is the one who invented the wheel (and periodically reinvents it) here. - He has also supplied a reliable guide (periodically updated) in his Installation Instruction page (and other Useful Links )

Rather than reinventing his succinct instructions, perhaps you could pinpoint what point(s) is/are unclear so members here can give a tailored response? 😀 PW
[Magisk] zgfg:
There is a new thread on XDA, Magisk + Zygisk, opened for the new Magisk v24

I would suggest you to jump there and read the OP posts by ipdev at the beginning of his thread
[Magisk] pndwal:
Anyone bored?

Here's one fix for that:

Try to get your head around 'stupid Linux decisions', ostensibly to provide cryptographically sound data for security purposes, that plague John's efforts to support older Linux on Android by using getrandom to feed an initial 32 bit random seed to an mt19937 pseudorandom generator in order to get some random bytes to keep things going that don't need to be REMOTELY secure AT ALL! ...

Conversion between John and an ASUS RealBench developer:

www.twitter.com/Ars_Dementis/status/1499552791810953218

Think custom modders are the only ones up against security geared computing? - Let's face it guys, security is everywhere, and creating work / challenges / conundrums at every level of every computing / OS food chain! 😜 ... Sorry John! ...

I'm suddenly hungry... need some random bytes... PW
[Magisk] Stillhard:
Any one hungry for latest build w/o the need of random bytes :LOL: (i mean gh account)? Just click here
[Magisk] pndwal:
I think you'd need to be quite hungry! Still, an interesting unofficial way to access experimental workflow test build runs (not at all like other 'nightly' software releases) from GitHub actions... Worth noting:

https://nightly.link/

Of course, if you just go to official source you'll see a list showing what each test run is actually for... Just click top one(s) to obtain the same artifact zip... At least Oleh gives a link...

https://github.com/topjohnwu/Magisk/actions

👀 PW
[Magisk] Stillhard:
Have you test it w/o gh account logged in? Or you can try too in incognito ;)
[Magisk] pndwal:
Yeah, I'm sure it works as advertised, dev / maintainer is experienced game / app coder, and his service was clearly born from an issue for gaming Devs who published links to nightly builds for their member gamers in GitHub artifact archives:

Of course, when GitHub changed policy and the artifact download URLs ceased to be public, nightly build delivery for such games etc broke for non-members.

So this may well be a good solution by one Gaming coder to help other such devs. The service works when a GitHub member "authorises" a particular artifact link to be downloaded by 'guests' using his / her GitHub ID:

Someone (you? 😜) has clearly authorised these Magisk actions test runs...

My concern is that this is NOT at all like trialing early release or even test runs for up-to-the-minute gameplay! ... Magisk tests can EASILY bork a user's device... Entirely! ... And who will help them fix it?! ...

Magisk Devs who suggest users in issue threads try specific solutions / test builds are dealing with users who are necessarily GitHub account holders...

I just can't see any value in making Magisk test runs arbitrarily available to inexperienced users who have never logged into GitHub and likely don't even have experience with bleeding-edge Canary Magisk, much less explode-in-your-face-and-send-you-over-the-edge Dev Workflow Test Magisk... 😬 PW
[Magisk] Stillhard:
That's why we have you here in the first place, so no need to concern 'bout anything, we can always ask the same Q again and again, and you do the A over and over, Kopine Endi... :LOL:
[Magisk] pndwal:
Predicted such a response, but don't push it mate ... I try to give intelligent responses to genuine modders (those not trying to be lazy... or stupid) at any level... We all started at the bottom so repetitititititition is a given, especially in this thread... But I'll leave arguing in my spare time to Michael Palin and John Cleese... I like to keep some of it, and it does run out at times...

At the risk of being called repetitive, that service is an ''interesting unofficial way to access experimental workflow test build runs (not at all like other 'nightly' software releases)'... However the pitfalls SHOULD be noted, and benefits (can't see any... except for some perverse form of entertainment) weighed... 😜 PW