yashsingh1/xdaforums huggingface dataset:
[Magisk] Triviox:
Someone can run DGO (Directv Go) with magisk? https://play.google.com/store/apps/details?id=com.directv.dtvlatam

Hello to all! I have a redmi 9t phone with Miui 14, Magisk 26.1, Lsposed 1.8.6, Shamiko 0.7.1, Universal Safetynet Fix by Displax 2.4.0, zygisk 1.8.6, Magiskhide 1.10.3, HMA 3.1.1..and i can pass all checks, safetynet, applist detector, etc.

I can run a lot of app with "root ban", but DGO still detects "something changed in my system".

If someone can pass DGO "check", please tell me how to did it!

Thanks, Diego from Uruguay.
[Magisk] shoey63:
There is no Indian ColorOS, it runs OxygenOS.

ColorOS is for the Chinese variant NE2210.

From a screenshot you provided

From Signed flashable zips in the link I provided

NE2211_A.18_0180_202210201343 is the one you need.
[Magisk] Thehaluzer:
Hello!

How do you know?

You must be an expert or something
[Magisk] pndwal:
Couldn't load this from playstore; not compatible (due to region?)... Sideloaded this:

and it works for me:

with WIP native bridge Zygisk loading to properly hide Zygisk and module memory... It's expected in official Magisk 27.0+ but current Alpha fork is a POC and I have many troublesome apps working with this.

For DGO, HMA was not needed; I have root hidden from app using Shamiko however, and removing it from denylist gives:

Follow links back from this post:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88468151

for more information incl. my device configuration... 🙂 PW
[Magisk] Thehaluzer:
Hello!

I plan to upgrade my phone from ne2211 to ne2213 as that's the European version and i read that it has better internet connection and also there are more guides for ne2213

I saw this link do you think it's safe?

Hey!

I wa thinking yo update my phone from ne2211 to ne2213 European version. As it's easier to google and it has better internet support. Do you think it's safe?.

https://xdaforums.com/t/simple-way-to-change-from-ne2211-to-ne2213.4533979/
[Magisk] pndwal:
😜 PW
[Magisk] shoey63:
I just googled it.

I don't own a One Plus device so I don't know the potential risks.

If other users have done it with success, then I presume it is safe.

Just follow the instructions provided and ask questions in that thread if you have doubts .
[Magisk] Thehaluzer:
You must be know how to google then cause google rare really shows me what i need. Thanks i followed the guides get even more errors. so i got the firmware of ne2211 and ne2213 but i can't do local update verfication failure. some suggested using an android apk 13 updater but that one dident do anything except telling me my phone is updated. extracting the payload.bin doesent work either downloaded the adb tools typed in adb reboot bootloader. doesent find my phone even thought i can transfer files and the oem and debugging is enabled. trying installing sdk tools as i read in a forum that one can help. ells then that im at square one still. Super frustrating when no guide ever works.
[Magisk] Thehaluzer:
https://xdaforums.com/t/simple-way-to-change-from-ne2211-to-ne2213.4533979/post-88558125
[Magisk] zgfg:
Again, don't understand what did you exactly did - btw, somebody advised you to use that other thread, specific to your OP NE211, since you can get better support there, from the users of the same phone

So, if unzipped ROM does not contain boot.img but payload.bin instead, you cannot use payload.bin for patching and flashing

You need to use Payload Dumper tool to extract boot.ing from payload.bin

There are various 'flavours,' of Payload Dumper (for Android - not convenient since payload.bin is a huge file; for Linux, for PC needing Python installed to PC or without Python)

Long ago I downloaded and installed Payload Dumper win64 but cannot find its thread now on XDA (it finds me another that requires Python)

Or install the one that requires Python installed... And when you search and find, read instructions how to use (actually trivial, most users would not need to read instructions)

---

But if you are asking about installing/updating the ROM then I will not help (I'm not familiar with OnePlus and its ROMs - that's why we say, better ask in its thread)
[Magisk] badabing2003:
This one has binaries for Windows and other platforms.
[Magisk] Thehaluzer:
thanks but i already fixed that with the help of an other user. Who eas very experienced and a good teacher
[Magisk] pndwal:
Interesting saga... Glad it had a happy ending... 😋

+1 🤗 PW
[Magisk] dlads:
Lol thanks man, happens a lot for me on here and real life.

Main thing is he's sorted and now knows how to fix it.

Cheers mate 👍🏼
[Magisk] m0han:
Shamiko

Version: 0.7.2 (172), 05/21/2023

What's new

1. Fix a bug causing Zygisk on KernelSU failed to unload

2. Abandon a useless fix leading to more detection

3. Clean service.sh

4. Fix the bug of incorrectly determined as corrupted.
[Magisk] pndwal:
Thanks... Already had from LSP TG, but see it got up in GitHub repo now. (nullptr built that one once they figured out that 0.7.2-170 had failed to fix the issues as canyie was busy...)

If anyone wants new challenges she's also updated Native Test (NativeDetector):

https://github.com/Dr-TSNG/NativeDetector

🤪 PW
[Magisk] pndwal:
NB Zygisk getting closer it seems...

3 month WIP still marked as Draft, but ToDo has gone from:

To:

... Not sure why items are now removed (not necessary?)...

More actions runs occurring ATM... Final touches or months more work?... 😛 PW
[Magisk] pndwal:
... Draft label removed!... Ready for review. 🙂

Here we go!... 😀 PW
[Magisk] zgfg:
Magisk Canary 26102 47d2d4e3 just released
[Magisk] martyfender:
Although I don't have any details yet, this completely messes up my system, just like recent action builds. This has required a factory reset and reverting to an older build.

However, this time I tried something different. I booted into TWRP and deleted data/adb and was then able to boot to Android and logon, so that is a start vs a factory reset.
[Magisk] Homeboy76:
Would you share what system the new Magisk Canary "completely messed up".
[Magisk] badabing2003:
Anecdotal data from me:

One Plus 5, with LineageOS 20 running Magisk Canary 26101, Live booted to Magisk Canary 26102, no issues.
[Magisk] pndwal:
Latest Canary Magisk:

Magisk (47d2d4e3) (26102)​

Implement all logging code in the project with Rust

[MagiskBoot] Support extracting boot image from payload.bin

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

Diffs to v26.1​

[MagiskBoot] Support extracting boot image from payload.bin

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

https://github.com/topjohnwu/magisk-files/blob/48dc969d44f8493ac2421fa50c184c6792381abd/notes.md

👍 PW
[Magisk] pndwal:
Also,

Patching arm (v7a) broken after updating ODNK to r25.3 (f7de649) confirmed Issue is fixed. 👍

Thanks @ipdev! 🙂 PW
[Magisk] J.Michael:
Doesn't that make it sound like the problem is module compatibility?

Have you reinstalled modules since you recovered by deleting /data/adb?
[Magisk] martyfender:
As always, it is in my signature. Note that I have 2 of these devices, one with Magisk debug and one with Delta. I have now attached a bugreport.
[Magisk] dobi3:
I am getting qualcomm crash dump on any Canary newer then Magisk-831a398b(25206). Everything is fine on 25206...26101 and 26102 I get crash dump on boot...

I have OnePlus 7 pro running OOS.11.0.9.1

Any help would be appreciated
[Magisk] Nergal di Cuthah:
One of your modules is probably not compatible. What ones do you run.
[Magisk] dobi3:
I disabled 3 I use, safety net, google dialer framework and wifi bonding qcom.. Systemless hosts for adaway
[Magisk] vMAC:
Does anyone know how I can get a script to run that has the following info:

#!/system/bin/sh
resetprop net.tethering.noprovisioning true
settings put global tether_dun_required 0

looking to have this run after boot. Putting file in post-fs-data folder doesn't seem to be running.
[Magisk] Tirofog:
Try in service.d🤞🏼
[Magisk] zgfg:
Put into two scripts as attached

One to post-fs-data.d but with:

#!/system/bin/sh

resetprop -n net.tethering.noprovisioning true

And the other to service.d with:

#!/system/bin/sh

# Wait to finish booting
until [ "$(getprop sys.boot_completed)" = 1 ]
do
sleep 1
done

settings put global tether_dun_required 0

Observe the differences corresponding to your original script (resetprop -n for the prop and waiting to finish booting for settings)

Just in case, chmod 755 for both scripts
[Magisk] martyfender:
I removed all modules and rebooted. The apk fails to update with the update button. I had reverted to an older, unhidden build.
[Magisk] ipdev:
All I did was report an issue as best as I could. 😉

Thankfully it sparked interest and was fixed quickly. ✌️

Commit 69144942e fixed the boot image patching.

All that was needed for my Nexus 7(s).

---

I now have a weird issue with my Nexus 5. :rolleyes:

Magisk shows Installed : N/A

Boot image is patched and boots.

- Magisk log is created on boot.

- If app is uninstalled, and device rebooted, Magisk stub shows up.

hammerhead:/ $ magisk -c
7087badf8-ip:MAGISK:D (26102)
hammerhead:/ $ magisk -v
No daemon is currently running!
1|hammerhead:/ $

So it looks like I will be creating a new issue when I have more time.

See if I can duplicate it on a different device.

Test and save files along the way. 🙃

Cheers. :cowboy:
[Magisk] ipdev:
post-fs-data is early.

service.d is late.

@zgfg gave you an example of splitting it into both a post-fs and service script.

If you want (need) to set the prop late, add the prop to your service script and skip the post-fs script.

To barrow the example service.d script zgfg gave you.

#!/system/bin/sh

resetprop net.tethering.noprovisioning true

# Wait to finish booting
until [ "$(getprop sys.boot_completed)" = 1 ]
do
sleep 1
done

settings put global tether_dun_required 0

If you need to set the prop after boot complete.

#!/system/bin/sh

# Wait to finish booting
until [ "$(getprop sys.boot_completed)" = 1 ]
do
sleep 1
done

resetprop net.tethering.noprovisioning true
settings put global tether_dun_required 0

Cheers. :cowboy:
[Magisk] xunholyx:
Nexus 7s? I have my 2013 version sitting there waiting for me to fix it. Touchscreen doesn't work. Probably a loose ribbon connection. It's been sitting there waiting for a couple of years now. Maybe I should take it apart and get on fixing it. From what I've been told it happens and also it's an easy fix
[Magisk] ipdev:
One of my favorite and beloved devices. 😄

I have 2 WiFi (flo) and a LTE (deb) currently running followmsi's Lineage 20.

Spoiler content hidden.

As for opening Nexus 7(s)..

The bezel is very easy to crack and break. More than likely you will crack a corner or two.

It is 10 year old plastic after all.

It is cosmetic and will not affect anything if broken.

I have mine in 'fosmon' TPU skin (case) that cover the bezel so, the broken corners are hidden from view. 😏

Cheers. :cowboy:

PS:

Nexus 7 2nd Generation LCD Screen Assembly Replacement

iFixit - [website] - Link
[Magisk] rodken:
No issues here on the OnePlus 8 considering that I am still using the Alpha fork.
[Magisk] Lughnasadh:
For what it's worth, I didn't have this problem using Canary 26102 on my Pixel 2 XL (Android 11) and on my Pixel 6 Pro (Android 14 Beta 2). 26102 shows as installed on both devices.

Haven't tried on my Hammerhead, but if I can find it maybe I will 🙃
[Magisk] pndwal:
Assume you've checked for previous hidden Magisk App in device settings, Apps... (It is actually possible to have multiple stub apps installed!)... Also, nothing in a second space, workspace etc?... And checked magisk -v? PW
[Magisk] ctcx:
PixelFlasher 5 released, hooray.

Now, given this, my previous attempt, and your notes:

Do these notes still apply for everything I should fix in that first attempt of wrapper I did, or should I now fix more beyond that?

Thanks again.
[Magisk] badabing2003:
Mostly yes, let me try to answer them individually.

Still the case, even though the stub might have what we need in data portion, it's not accessible without root, and even if we're rooted, properly extracting it would require some sleuthing / reverse engineering.

Besides unless the app is newer (or Magisk delta) root option is always a preferred option.

(I just discovered yesterday that Magisk delta does not have the stub.apk in /data/adb/magisk)

Yep, you have to make sure it exists somehow.

Some do, and some don't, specially a phone that has never been rooted before.

For me this is still working and good enough

I added an checkbox option in PF where the user can select if they are patching for recovery or not.

I think for PF that should be more than enough, I doubt that it would be used.

PF does that, the generated patch is named something like this. magisk_patched_25210_bac0e555_e3c084bc.img[/icode
Magisk version, stock sha1, patch sha1
[Magisk] ipdev:
Thank you for checking. 👍

Seems the issue was fixed earlier today and will be in the next canary release.

App was never hidden (renamed) and no second version installed.

No other workspace or such setup on device.

Both the `-v` and `-V` options returned.

No daemon is currently running!

The daemon was started according to the magisk log.

---

Looks like it was related to:

Root is not defined

Issue #6976

All good now with current commits.

hammerhead:/ $ magisk -c
dd93556ad-ip:MAGISK:D (26102)
hammerhead:/ $ magisk -v
dd93556ad-ip:MAGISK:D
hammerhead:/ $ magisk -V
26102
hammerhead:/ $

Cheers all. :cowboy:
[Magisk] pndwal:
Not Delta specifically...

This commit:

Remove unexpected files

vvb2060 authored and topjohnwu committed on Feb 26 removed stub.apk from /data/adb/magisk prior to 25207...

this broke boot_patch.sh as it's required per the header, and consequently broke addon.d script...

@osm0sis discovered the issue and stub.apk was restored to /data/adb/magisk in 26100 with:

Fix scripts …

manager.sh + boot_patch.sh:

- all listed files from boot_patch.sh header are required for boot patching, but stub.apk was being removed so install_magisk via addon.d.sh would fail without it; leave it in place

addon.d.sh:

- remove old redundant recovery_actions call (it's also performed by setup_flashable in initialize)

- print ABI to match flash_script.sh output

boot_patch.sh:

- catch and abort on any errors from ramdisk.cpio patching in the future

util_functions.sh:

- fix hiding of mount_partitions /system_root umount stderr

- quote mount_apex .pb DEST name parsing charset for safety even though both work

Fixes #6828

osm0sis authored and topjohnwu committed on Apr 9

... Delta is just getting old (not updated recently); Latest is still based on 25210. (Latest 'Stable' indicates base is 25206. 🤔: https://huskydg.github.io/magisk-files/intro.html ). So if your tester is using latest Delta lacking Stub is expected, and that was the same for official Magisk from 25207 till 26100 arrived...

👀 PW
[Magisk] badabing2003:
Thanks for the heads up,

Right I was aware about broken/missing stub.apk on version 25206-2521x, I don't know what I was thinking to expect anything different on Delta for version 25210 :sleep:
[Magisk] pndwal:
Nice work by @pasha.mcr! ...

Model way to get Devs to re-open and respond. 😜... Thanks to @vvb2060...

... Just noticed you seem to have tried to install debug build on Nexus 5...

Because fix turned out to be speed related (Magisk too slow; Faster get magisk tmpfs path needed) and debug Magisk is known to cause issues with slower/older devices, perhaps that was a factor?... Anyway, faster Magisk seems a good fix.

👍 PW
[Magisk] dobi3:
Canary 25206 works fine... Think newer 26.1 and Canary 26102 have issues on my OnePlus 7 Pro running OOS.v11.0.9.1...get Qualcomm crash dump on newer versions... Canary 25206 works flawlessly...

This is what is causing it I believe:

- Pre-init storage partition device ID: metadata

I don't get that on Canary 25206

Thanks for any help or fix..

👍👍
[Magisk] spida_singh:
FYI husky has advised Delta has merged with 26.1 should be released soon. From TG channel.
[Magisk] martyfender:
Has anyone else on Mediatek ARMv8-A devices had trouble getting the new Magisk update install the apk or update Magisk? See my previous posts.
[Magisk] martyfender:
What would be needed to troubleshoot this, logcats?

Thanks
[Magisk] pndwal:
Bit confused by previous posts... Do you have any Magisk App that opens? Please screenshot home screen... If not, what happens? PW
[Magisk] martyfender:
I have to leave for radiation therapy and work. However I had reverted to the action build I had installed dated about April 10th.
[Magisk] DaOldMan:
In my ViperOS rom I now have a new problem with Magisk 6.x . Any app included in zygisk denylist crashes when run :-( . If I use the older Magisk 5.x eveything is totaly fine, I can even pass safetynet. Alpha version has the same problem.

Rom is Nugat version 7.1. Tried to remove Magisk completely then reinstall, still same problem.

Thanks guys for any help.
[Magisk] osm0sis:
Whoa, magiskboot = payload_dumper now:

Support extracting any partition from payload.bin · topjohnwu/Magisk@659b9c6

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

🤯
[Magisk] tim1aust:
Question: I am new here, please redirect me to appropriate forum if this isn't where I should post my Q.

I have pixel phones rooted with Magisk, thus no OTA updates for me. So I download them from the Google site when the monthly update arrives, and flash using adb sideload. But it's a PITA wrt Magisk, I usually have to fuss around to get Magisk back running, although it's still worth it.

My Q is: if I update the monthly update zip with the appropriately patched magisk_patched file, will that OTA update install successfully and also preserve Magisk?

Thank you for any advise.

Tim
[Magisk] Lughnasadh:
If you want an easy and painless way to update each month while keeping root, I would suggest Pixel Flasher.
[Magisk] tim1aust:
Thank you! I am currently building it from the .tar.gz on my Manjaro box. I will try it when the next update comes round.
[Magisk] sawdoctor:
You don't need to build it the Ubuntu version runs on manjaro, I'm using it. Version 5 had an issue on manjaro but it's been fixed with the latest test build
[Magisk] badabing2003:
It's not actually fixed, if I build it on my machine manually, it works for you guys, but if I let Github build it, it doesn't.

I can't put my finger on it as to why?

I don't want to build manually anymore for each release, but I also don't want users having to build it manually either (unless they want to).

That's why this is bugging me.
[Magisk] tim1aust:
Thanks again for the info. But... too late! I already got it built and running, after learning more about building wxPython (or any python module, actually), and also installing the nautilus browser to select boot images. It's been interesting! This tool seems very well done, I am hopeful to use it successfully soon. Thank you Thank you Thank you, for bringing it to my attention.

Tim
[Magisk] J.Michael:
What you describe has a good chance of working. When it doesn't work, you will have a good chance of recovering by flashing the unmodified "new" ROM, and continuing as you used to.
[Magisk] zgfg:
Please, try to install JamesDSP with Magisk v26 (or Canary 26102):

https://raw.githubusercontent.com/Zackptg5/JamesDSPManager/master/install.zip

Or from the GitHub Readme, View code, download install.zip:

https://github.com/Zackptg5/JamesDSPManager

(Btw, I don't know why he cannot create a Release on GitHub like there are for all other modules from other authors, so that his latest version or an older one can be easily found and downloaded)

If I try to install JDSP when I have Viper4Android and AML, then it complains that there is an incompatible module and that I must use AML (although I do use it)

If I try to install JDSP without having V4A and AML, then it seemingly installs ok, but after reboot, when I open JamesDSP app, it immediately crashes

I tried both with Volume+ ('Huawei', ie, 64bit) and Volume- (not 'Huawei', ie, 32bit)

(Again some oddities - it is known that it's not really about Huawei or not but if 64bit audio drivers are needed or not. So he could have renamed Huawei option to 64bit or so [he released latest JDSP recently and/or his module could find itself are the 64bit drivers needed when installing]. Also that ancient Volume+/- mngmt during the module installation [from the times of installing modules through custom recoveries with no touch screen], where it usually does not detect the button at first and/or on time)

However, with Magisk Delta, JDSP module works perfectly (and together with V4A and AML)
[Magisk] martyfender:
I have now attached a bugreport to my previous report.
[Magisk] martyfender:
bug report
[Magisk] siredux:
I'm getting this error in TWRP 3.0.2, LG G3 D855, clean system, no root, no xposed, no magisk, any clues? Magisk V8 used to work great

! Failed: Unable to extract zip file!
Updater process ended with ERROR: 1
[Magisk] cohiba90:
To play Pokemon Go, did you check only the "pokemo Go" to hide magisk root?

I have this log:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Enabling BusyBox

Mount: /magisk/.core/busybox

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Error occurred...

Thanks!
[Magisk] :
Galaxy s5 g900w8

Stock 6.0.1

Stock kernel enforcing

Magisk itself works as well as root.

Magiskhide does not. Guessing I'll need a permissive kernel like I did for previous version.

Started from unrooted state passing SN

From twrp installed magisk v9

From twrp installed phh superuser 266-2

Cleared cache

From system installed phh superuser apk

From system installed magisk manager 2.5

Enabled Magiskhide in settings and selected apps to hide. Rebooted

Cannot pass SN

Here's the magisk log:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.google.android.gms]

MagiskHide: [com.google.android.gsf]

MagiskHide: [com.nianticlabs.pokemongo]

MagiskHide: [com.scottyab.safetynet.sample]

MagiskHide: Error occurred...

Edit: retried with phoenix kernel for permissive but same log and can't pass SN.
[Magisk] westeight:
Thank you :cowboy:
[Magisk] H4X0R46:
Thanks for the v9 update! One question. Since unmounting root is no longer a function in the magisk manager, how do you hide root from apps? There's something in the OP about using suhide for supersu, but how do you go about this with phh? I'm using the magisk phh module from here: https://goo.gl/lwO5vi Thanks!