yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
I suggest you disable MHPC Force Basic option as the changed model prop been is seen globally and can cause issues (and if you have USNF 2.1.0 or 2.1.1 you are now making the change twice); this was a necessary evil until we got USNF 2.1.0 which used Riru to apply changed props (incl. model props to fix September Google server end detection change) to Google Play Services only.

You only need MHPC for certified fingerprint, as stated.

Are you facing 'root' detection issues w/ LOS 18.1 that you didn't w/ 17.1? PW
[Magisk] pndwal:
My bank app runs fine w/ LOS 18.1 on my Mi Pad 4, but I only ever needed SafetyNet pass, Device is certified, and to add it to hidelist...

TJW & Alpha Magisk have always run great too... But you may have a bad build I guess, especially if unofficial.

... BUT are you saying you never had SafetyNet pass?... That's pretty much a prerequisite for Bank apps... Other requirements are additional.

You should solve SafetyNet issue as I described; 3 aspects:

1) USNF 2.1.1 + Riru.

2) A passing fingerprint configured in MHPC (often any will work - I had a Huawei one on Xiaomi for some time in days of old SafetyPatcher module!, but there are sometimes issues with prints for earlier Android versions now it seems. Still, you'll find many working for Android 11 and from same OEM I'm sure 😜).

3) Either MagiskHide enabled for current TJW builds or Google Play Protect process(es) added manually to denylist in current Alpha (generally just com.google.android.gms.unstable for pre Android 11, both that and com.google.android.gms for 11+).

If an unofficial build it is likely your LOS 17.1 included fixes / certified fingerprint (ie. spoofed) inbuilt, and that your 18.1 simply doesn't (no official LOS releases do this due to policy for example, but requisite fixes can easily be applied using Magisk). This may also account for your differing mileage... PW

Edit: Just saw your PS...

Are you saying you don't have GApps? Is that LOS with MicroG?...

If so, most bank apps won't run (and I'd be surprised if 17.1 is any different) as SafetyNet has not passed with MicroG since June 2019 even with GMS installed, and I believe there is no fix as yet!

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85502585
[Magisk] nadastry:
I would like to root my Tab S6 lite WiFi using Magisk.

I already installed Lineage 18.1 and its recovery, since TWRP is no more for this tablet.

I then copied boot.img from lineage zip to the tablet and created a magisk boot.

This I then wanted to flash using fastboot flash boot file.

Fastboot devices reports the tablet in fastboot mode.

But I cannot get the fastboot to flash. fastboot reports an error "target didn't report max-download-size" before sending the file and then does nothing.

The new boot does not get flashed.

I already tried a different USB cable (using the original and a 3rd party), but the same.

I tried a different laptop with USB2 but that has the same error.

PC restarting does not help either.

Could you help me flash the boot?
[Magisk] zgfg:
Did you enable OEM unlocking in Developer options (don't know your device/ROM but usually it must be enabled to let fastboot to flash)

You could also try:

fastboot boot <patched-boot-img>

instead of:

fastboot flash boot <patched-boot-img>

but no guarantee it will work on your device (it doesn't permanently flash but only boots one time with the patched boot img)

Btw, assuming:

fastboot devices

finds and lists your device
[Magisk] Fif_:
Aren't you supposed to flash boot using Odin or heimdal while the tablet is in download mode?

This tablet doesn't use fastboot, and you shouldn't need fastbootd to flash boot.

By the way, I did what you just described a few days ago, all went very smoothly. I used heimdal to flash boot (Linux user).
[Magisk] nadastry:
@zgfg @Fif_

Thank you for your answers.

The lineage wiki states to flash via fastboot.

I now deleted the stock boot.img from the lineage zip and replaced it with the magisk boot.

I then went to recovery and flashed the ROM again with checksum error of course.

Now I have Magisk installed.
[Magisk] xdatin1:
I am on Magisk stabile.

Where can I download Magisk Alpha and how to install this new Magisk?
[Magisk] zgfg:
Pls search for Alpha in the thread, it's been asked/answered/guided several times
[Magisk] xdatin1:
Ok, now I have new Magisk (manager) alpha app and now when I wont to install Magisk (root) I need to patch something...what?

EDIT:

Ok, I somehow fix this and now I have Magisk alpha.

I can see any modules online.

Is this mean if I wont some modules I need to download them?
[Magisk] zgfg:
Yes, Alpha Release Notes have been posted and it was discussed how/why TJW removed support for Modules Repo
[Magisk] pndwal:
Mmm

I had the impression you were seeking solution for bank apps...

But you haven't said what you mean by don't use Google Play Services, or if you don't run GApps... If you have GApps you have SafetyNet API (part of Play Services) and all bank apps I know of require it's attestation to pass...

I found this LOS 17.1 ROM for sm-t510:

https://xdaforums.com/t/rom-sm-t510-unofficial-lineageos-17-1-for-galaxy-tab-a-10-1-2019.4060153/

but couldn't find LOS 18.1... I'd be interested in a link... PW
[Magisk] mukhlesur.millon:
I was able to unlock the bootloader with mtkclient and flash patched boot.img from magisk.

I have tried many times but I am getting bootloop.

Device: Vivo Y81i

boot.img and magisk_patched-23000_4pBBb.img
[Magisk] pndwal:
Ramdisk = yes? PW
[Magisk] zgfg:
In your shoes, I'd try with Magisk Alpha. There were some commits for MTK

And you have nothing to loose - flash the original boot.img if not working
[Magisk] ipdev:
Yep. :)

When you use pm disable or pm enable, the app will still show in the package list as an installed app.

Only changes the flag to disabled or enabled.​

When you use pm hide, the app is treated as an uninstalled package.

Tagged as removed.

You can find it by including uninstalled packages.

pm list package -u​

When you use pm unhide, the app is treated as a new installed package.

Tagged as added.

You will see the new installed badge on the app icon.

If you have it set to add new app shortcuts to the desktop, it will add the shortcut to the desktop.​

Since the app was not uninstalled, all app data still remains.

Unless you cleared the app data manually.

I thought block was depreciated when hide was added.

Android 9 (SDK28) if I remember correctly. ??

--

One of the reasons I started looking into hide a bit more.

Example.

If you do not repackage (rename) the Magisk app.

Disabling it, RootbeerFresh still finds it and shows rooted.

Hiding it with PackageManager, RootbeerFresh does not find it and shows not rooted.

Cheers. :cowboy:
[Magisk] zgfg:
Installed modules (one by one, not neccessary all at once) can be disabled, re-enabled and uninstalled by manipulating their disable and remove files (by any root explorer)

However, CLI for installing a module zip file is valuable tip

Therefore, one can fully maintain the modules without the need for Magisk app
[Magisk] ipdev:
Yep.

I just mentioned the Big Hammer option since it is an option. 🙃

Cheers. :cowboy:
[Magisk] F308:
Exactly.

People don't believe me when I say how powerful command line is.

Mouse click is fast but what to do if there's nothing around to click?

When GUI fails CLI becomes the last resort of action.
[Magisk] zgfg:
Actually, Magisk database can be easily edited directly from MiXplorer

Tables for Magisk Alpha (Stable/Canary will have MagiskHide instead of Zygisk and DenyList) include:

- policies: root granted packages

- settings: zygisk and denylist yes/no

- denylist: packages and proccesses enabled for denylist

Example - how to manually grant root for a new app (e.g. Vanced Manager) without the need for Magisk app and its root granting request pop-up:

1) Find the package name and UID for the given app.

Die hards can do it by CLI pm comnand and so, I used Package Manager from Playstore to make my life easier.

Screenshot "1"

2) Use MiXplorer and go to /data/adb

Just in case, make magisk.bak copy of magisk.db

Click on magisk db to open the database.

On top-left, select policies.

On top-right, press on + sign. Screenshot "2"

3) Fill in the Insert list and press Insert.

Screenshot "3"

4) You will see that the new app was added to the policies (root granted apps).

Screenshot "4"

5) Press diskette icon to Save.

Screenshot "2" again

6) Reboot to put your changes in effect!!!

7) If you open Magisk app, SuperUser tab, you will see that Vanced Manager was successfully granted the root access.

Screenshot "5"

(In case that screenshots do not show up in order, they are named 1,2,3,4,5 as in the guide above)

Edit:

For Magisk Lite, structure of lite_magisk.db is little different:

Instead of the tables policies and denylist/magiskhide, there is a table sulist (with somewhat different structure)
[Magisk] mukhlesur.millon:
Ramdisk = Yes

Zygisk = No

I couldn't find Magisk Alpha. I have built master branch from Github. Still getting bootloop.

Its boot.img is different. It has no .fstab, no prob.default, no selinux file context and magisk patch replaced init binary, maybe for that reason, it can't boot?
[Magisk] zgfg:
Link to Magisk Alpha (Telegram and Github) and instructions for switching to were posted and discussed in this thread several times (search for Alpha and so) in the last weeks (first posts were maybe in May but the interests rolled up mostly last month and onwards)

Btw, rapid-fire has paused?! Last Alpha release was 'way back' on Sep 26
[Magisk] pndwal:
Ah... You said:

MicroG is a way to de-Google and many use it as alternative to GApps, but it hasn't passed SafetyNet for a while now...

Since you said you 'don't use Play Services' I just wondered if you haven't installed GApps as Play Services is included, and pointed out that the use of Play services is actually essential for (most) bank apps as they rely on SafetyNet API... PW
[Magisk] pndwal:
There are a number of current fstab related issues in Magisk GitHub:

https://github.com/topjohnwu/Magisk/issues?q=is:issue+is:open+fstab

Seems there is sometimes difficulty locating correct fstab, and need to strip system_ext for some devices:

- https://github.com/topjohnwu/Magisk/issues/3752

- https://github.com/topjohnwu/Magisk/issues/4638

Hope it helps. PW
[Magisk] ipdev:
At first glance, it appears to be system-as-root.

default.prop -> system/etc/prop.default

etc -> /system/etc

Android 8.1 (SDK27)

AVBv1

You might be running into verified boot.

If you have a copy of the vbmeta image file

You could try and disable verify boot.

fastboot --disable-verification flash vbmeta vbmeta.img

or

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

I do not remember what was needed on SDK27.

You should be good if you are building from John's master branch.

If you want to try alpha builds.

vvb2060 [magisk_files] - GitHub - alpha - Link

Can you get root access to the device?

Quick look but, I did not find a custom recovery for your device.

- Looked for TWRP and OrangeFox.

Since it is a mtk device (if the firmware has not been patched), you could try diplomatic's Temp Root.

Amazing Temp Root for MediaTek ARMv8 [2020-08-24] - xdaThread - Link

Just to make sure.

The boot image you are patching does boot if unmodified?

Cheers. :cowboy:

PS.

If you can get at least temporary root access you can dump the partitions into image files from the device.
[Magisk] xdatin1:
I have latest alpha and in settings zygisk is enabled. Phone is restarted but I do not have zygisk.

How to fix this?
[Magisk] pndwal:
In the middle there is a big blue button! ... 🤪

(sorry - couldn't resist. 😛 )

Do you have MomoHider module? - this caused instability, crashes, Zygisk disabled and (once) loss of root with anything other than initrc hiding enabled w/ Zygisk for me.

Could be other modules incompatible too. If not MomoHider, try disabling others / rebooting. PW
[Magisk] pndwal:
Guess John has given this by now:

He did say to 'non Googlers':

... Just thought y'all might find John's visual aid for understanding new Magisk helpful!

Of course, this is on his Twitter... Sorry I can't give a link...

FWIW, a Mod has told me:

😬 PW
[Magisk] mukhlesur.millon:
I have disabled the verified boot by flashing an empty vbmeta.img.

I have ported TWRP. It was trial and error. it works but needs some more work.

diplomatic's Temp Root does not work on Vivo devices (tried on my Y81i).

I can read, write partitions, unlock bootloader with mtkclient.

I can modify boot.img and it does boot fine. There is the real problem. I can only modify some files.

Somehow the device knows I have modified a certain file -_-

I can modify vendor.img/etc/fstab.mt6761 and it works. But whenever I try to modify files inside vendor.img/etc/init/ and system.img/etc/init/ , the device detects that I have modified that file and it does not execute that .rc file. I can see file size but cat command returns empty (not permission error, I have checked all .rc file permission). (I can cat from recovery). and I can cat other .rc files. I don't know how it detects individual file changes. I have tried to replace md1rom partitions with zeros. same result. I can not also add new .rc file. new .rc file does not execute and ls command does not show it.

so, It is not a Magisk related issue at all. I'll try myself for some more days
[Magisk] zgfg:
cb4361b7-alpha-2 just released
[Magisk] jons99:
yeah you can flash it it's working fine
[Magisk] rodken:
As long as I have Riru installed, it's a no-go for me.
[Magisk] zgfg:
But per screenshot, you did install (although with Zygisk disabled)
[Magisk] pndwal:
Apparently he has Zygisk enabled but it is broken...

Seems he has Xiaomi Mi 9T.

PW
[Magisk] pndwal:
Did you ensure MomoHider is disabled / try with all riru modules disabled as I suggested? PW
[Magisk] 73sydney:
@pndwal

Thanks Marvin

I'll just wait patiently until Momo-Hider works for one of you, then ill swoop in and try it :)
[Magisk] pndwal:
Actually I have it enabled, but only with initrc hiding enabled and have no issues.

With app_zygote_magic or setns set I get instability / crashes / loss of Zygisk or root; haven't tried isolated on its own however...

Seems if you need app_zygote_magic or setns, it's just hard cheese. 🧀

Might as well just give up now... we'll all be going down in a screaming heap soon in any case... can't even joke about it now either... Marvin.
[Magisk] J.Michael:
When you talk about modifying system.img/etc/init/ , are you modifying the system partition image file, or are you putting files in a Magisk module directory tree?
[Magisk] zgfg:
Per Telegram, the following is listed as Update log from Sep 26 cb436b17 to this cb436b17-2 (Oct 4):

Update log:

[Resetprop] Erase old content completely when editing/deleting

[General] Fix the race condition of thread pool

[MagiskInit] No longer intervenes when booting to DSU

Screenshots attached
[Magisk] luridphantom:
is there a way to debug why patching a boot img with magisk doesnt result in root? i have a lg premier pro plus l455dl on pie 9.0 unlocked with mtkclient and every build ive tried including canary doesnt give me root after flashing the patched image to both boot slots
[Magisk] zgfg:
Are you for some particular reason on the old v22.1

Stable and Canary latest were v23

There is Alpha now (lot of conversation about in this thread), and AFAIK, developer vvb2060 had included some fixes for MTK chipsets
[Magisk] luridphantom:
looks like an older alpha build didnt work but the latest one off telegram did, thanks!
[Magisk] rodken:
I took the liberty of removing MomoHider all together to no avail..

I've decided to wait until newer builds are released until I hit paydirt.

I've come to o a conclusion that I need Riru because I utilize LSPosed to it's 'maximum - capacimim'.
[Magisk] zgfg:
On the screenshot you have: Latest N/A and SafetyNet check missing

Looks like you were off-line when taking the screenshot?!
[Magisk] pndwal:
Mmm. Just meant to test... Ie. try booting with Riru enabled but all Riru modules disabled to see if Zygisk is restored.

On RN8T I have NO problem with Riru + LSPosed & late Alpha builds + Zygisk. Only with MomoHider (w/ anything other than initrc hiding)... But I don't know what other Riru modules you may have.

If Zygisk is not restored with Riru & no Riru modules but returns with Riru disabled it would narrow this issue down to incompatibility between Riru and Zygisk on your device (Xiaomi Mi 9T?) or ROM.

I think @zgfg has same device... Perhaps he can confirm if he has no issues with Zygisk / Riru. PW
[Magisk] mukhlesur.millon:
I am modifying the system and the vendor partition image file.
[Magisk] zgfg:
I don't use Riru (no need so far)
[Magisk] pndwal:
Perhaps you could install Riru only (no Riru modules) just to confirm if this is an issue with Zygisk on 9T? PW
[Magisk] rodken:
I am leaning more to the issue being with the ROM considering that I am stock OP8 OOS 11.

After further review, I installed Riru only (disable all other Riru modules), rebooted device twice, just to confirm that the issue might or might not be limited to Zygisk.
[Magisk] pndwal:
& @zgfg

Ah, OnePlus device...

Sorry guys, now clear I've got @rodken and @xdatin1 and devices confused... 🙄 PW
[Magisk] rodken:
Stock OP8 OOS 11 with Horizon kernel.
[Magisk] HippoMan:
I've been debating with myself as to whether or not the following question would be OT here. Since it relates to Magisk, I have decided to post it, but if it indeed is deemed to be OT anyway, I will accept that decision.

I have continued to use my OnePlus 7 Pro under Android 10 and Magisk 23.0, because I want to avoid all of the painful complexities of going down the Android 11+ rabbit hole and of dealing with newer versions of Magisk.

However, my device is becoming outdated, and I am considering a new device. My question is this: what do you folks think would be a good device to switch to that would ...

(1) ... allow me to run rooted Android 11+ with Magisk, with a minimum of painful complexities.

(2) ... allow me to successfully install LSPosed to run with Magisk, so I can utilize GravityBox.

(3) ... be able to perform nandroid backups and restores ... i.e., not just Titanium or SwiftBackup backups, but rather, full, normal nandroid backups and restores of Boot, System, and Data via recovery.

Since this doesn't pertain to any specific device model, I don't think it makes sense for me to post this to the forum for each and every device that I can think of. However, if this is still considered to be OT here, then feel free to respond to me via private message.

Thank you very much.
[Magisk] zgfg:
Xiaomi Mi 9T

Android 11, MIUI 12.5 (Xiaomi.eu Stable)

cb4361b7-alpha-2

Ok, I just installed Riru:

Release 26.1.2 · RikkaApps/Riru

v26.1.2 (2021-09-04) Speedup Rirud launch Warning about incorrect SELinux policy No warning about Rirud socket closed Use getprogname to detect zygote

github.com

and LSPosed:

Release 1.6.0 · LSPosed/LSPosed

Happy Chinese National Day! Changelog Parasitize manager into Shell as it is a system app to avoid detecting manager package name as the manager is not installed on the system! Fix crashes caused ...

github.com

Installed also GravityBox-R and successfully tested Ascending ringtones and Volume keys skip tracks - FYI @HippoMan

Some screenshots attached

Btw, I'm puzzled about Riru detector not finding Riru - although e.g. Riru-LSposed and its module GravityBox-R work fine

Should I test something more?

@rodken , too?
[Magisk] Fif_:
FYI, my OP7Pro works fine with the latest OOS 11 release, Magisk 23.0 & LSPosed 1.6.0.
[Magisk] HippoMan:
Oh ... that's good to know! Thank you.

Maybe I'll stick with OP7Pro then. I'll see.
[Magisk] luridphantom:
nah i took a bunch of screenshots and basically uploaded my last config when i gave up testing every build back to v8

guess i didnt see the alpha scene driven by vvb2060
[Magisk] pndwal:
Thanks for that! (Of course, wrong device for @rodken; my mistake).

All looks good! - I get same results.

You may have read comments in telegram that this build is hiding Riru. I think this is a first, and may be an added value benefit of Zygisk.

I assume this is actually a result of Zygote 'Abnormal behaviour' being properly disguised to hide both Zygisk and Riru (and possibly other hooking frameworks). Compare Momo screenshots:

Now

Previously

👍 PW
[Magisk] ipdev:
To follow up on one of my previous posts.

Post 48,187 - Link

Seems OnePlus 6T is also old enough not to have the hardware for hardware attestation.

So I was able to do the same steps as my 5T to pass SafetyNet.

OnePlus 6T

Stock OnePlus OS 11.0.0 (SDK30)

Magisk (snapshot build)

MagiskHidePropsConf (Magisk Module)

Enable Zygisk

Enable DenyList

add com.google.android.gms.unstable to the DenyList.

add com.google.android.gms to the DenyList.

Enable the MagiskHide props. option in the MagiskHidePropsConf module.

Reboot in between steps as needed.

--

John pushed a WIP commit earlier today so I did a quick build to test updating with a renamed Magisk app.

No problem updating with a renamed Magisk app. :D

My 6T did not have a renamed Magisk app.

So I tested on my Pixel 4a running stock (20210905) rom.

New addition to my Magisk snapshot devices.

Stock Google (20210905) Android 11 (SDK30)

Note: I have not had time to figure out how to pass SafetyNet on it yet. 🙃​

Cheers all. :cowboy:
[Magisk] zgfg:
Hmm, I have more "Suspicious traces"

Regarding "Magisk or TWRP files" - Magisk app is not hidden and I have TWRP folder

But what about "Debugging mode" and "Restriction on non-SDK interfaces"?
[Magisk] pndwal:
Of the times I've tried updating w/ app hidden (lately Alpha builds), it seems to have succeeded w/o complications about 50% of the time, so still a pot luck affair AFAICS even since 22000. PW
[Magisk] zgfg:
One more thing - can you test CustoMIUIzer in LSPosed on your Xiaomi

Available in LSPosed repo and from Playstore, latest 3.1.7

For me it complains that it cannot find XPosed although it is enabled in XPosed, all recommended system apps are enabled, etc
[Magisk] zgfg:
Resolved:

With the latest LSPosed mngr (Parasitic) 1.6.0 from Google Play, CustoMIUIzer does no more complain and it works (tested by changing Status bar height from Default to Max, rebooted, it makes a huge visible difference)
[Magisk] pndwal:
Haha - I've been running that for a while! Only Xposed module I installed, but never had issues... See now I need an update though...

😜 PW

Edit:

Updated from GitHub (haven't gone to PlayStore...

Interesting it didn't replace old 1.5x manager, so deleted manually... New 1.6 working fine so far, but if I click app info on main screen itnfo shows 'Settings version 10', same as real Settings! 🤔
[Magisk] rodken:
New updates are pushed almost on a daily basis via the Telegram channel.
[Magisk] zgfg:
I had to install apk from /data/adb/lspd to get the version 1.6.0 properly showing

But with 1.6.0 you can create a shortcut (instead of its icon) and then you can uninstall the LSPosed app from Settings/Apps - it's 'parasitic', it still works then from the shortcut
[Magisk] pndwal:
Yup: may be different installing from GitHub rather than PlayStore...

App showed property from update/reboot but I selected Create Shortcut immediately and had two icons for LSPosed on home screen. - The shortcutted 'parasitic' one shows 1.6x, 'details' brings up settings, and it's corresponding icon in App drawer gave (only) an option to rename LSPosed to custom name. - The other (original) icon still showed 1.5x version (guess this would have updated to 1.6x if I hadn't selected 'shortcut' option initially), and I uninstalled that. PW