yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
Momohider-Mod removed because the original Momohider module author decided to flex on Telegram for an audience of his inner circle on Telegram and accuse me of not including source code, which of course i did, because of course my ONLY alteration/change/addition was to a script file, which is of course its own source....and he also asserted i didnt notify him, when i did. That he was too lazy to check his notifications isnt my fault.

I credited him here as well, and that credit was visible for the 2 months the attached mod was here

So sorry, but my helpful mod is removed due to that idiot

Sorry he was too lazy to automate adding the config switches to make your lives easier, and that he decided to be a **** when i added a way for people to more easily use his module, and informed him of my additions to allow this

Sadly he chose to wait 2 months and then troll me on Telegram....
[Magisk] Primokorn:
Hello,

My device is a Xiaomi Redmi Note 7 running crDroid 3.11 (Android 10) and Magisk 23.0 (23000).

SafetyNet is OK and I enabled Magisk Hide.

My banking app (Google Play link - com.prod.bca) still knows that I'm rooted, why?

I compared my configuration with my other devices (Oneplus 3T - crDroid Android 11) and I have no issue.

I have attached logs.

Thank you in advance for your support.
[Magisk] sporc10:
I somehow locked myself out..

I had magisk installed and all working, then I hide magisk and freezed the repackaged app. Now I have the problem that I cant unfreeze it again, because the app I used to freeze doesn't work anymore (I suppose the root is missing).

What can I do, to get access to magisk again?

I tried to install the latest magisk apk, it says under magisk "Installed: N/A".

Any suggestions or ideas? Thank you
[Magisk] zgfg:
Sorry but it was really a bad and wrong idea to freeze the Magisk app (pretty sure, it was not suggested in this thread) - specially upon it was repackaged.

Without, you cannot grant root access, etc

And of course, your newly installed Magisk app cannot connect to Magisk because the old (repackaged and frozen one - doesn't matter) is still connected to Magisk DB - three were so many posts here about the same problem when the newly installed Magisk app shows N/A for Magisk because of the forgotten, old, repackaged Magisk mngr/app still installed

First, uninstall that newly installed Magisk app (simply from Settings, Apps)

Then, you must find your old, repackaged (and frozen) Magisk Manager/App and uninstall it, too

Unfortunately, when you did repackaging, the package name was randomized and you don't remember that randomized package name (another reason it should have not been frozen then)

Hopefully, you remember which app name you gave it instead of the Magisk mngr/app - try to find it under that name in Settings, Apps and try to uninstall it there (even since it was frozen)

Or, install an app Package Manager from Google Play, search in that app for the app name of your renamed/repackaged Magisk Manager/App.

You can probably uninstall it from that Package Manager but even if not, you can read there its randomized package name

The other way to find its randomized package name will be to use ADB comnand from PC:

adb shell pm list packages -d

That command lists package names for all your "pm disable-user ..." apps (that is, those apps you 'froze')

Look at the output list and if you see some totally strange/randomized package name, that one should correspond to your (frozen and) repackaged Magisk mngr/app

Once you detect its (randomized) package name, you will be able to 'un-freeze' by ADB:

adb shell pm enable <package-name>

and then you should be able to regularly uninstall it from Settings, Apps (or just open it, go to Settings, and take the Restore option to get it back to the 'normal', not renamed/randomized Magisk mngr/app)

Only then, if neccessry, install the new/updated Magisk app

PS: For all who cannot live without repackaging Magisk app.

Upon repackaging, open the app and take a screenshot - on top, under the App info, after Latest and Installed lines, you will see the line Package showing its randomized package name.

Save the screenshot for your reference - in case you ever 'freeze' it, you will know its randoized package name to un-freeze
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85148739 👍 PW
[Magisk] Burt Squirtz:
Will this show updates within the app itself? Or do we have to manually download and install new Alpha branch?

Over-joyed that someone is continuing on with the work. I thought we were done with magisk honestly. Has been Anxiety-inducing
[Magisk] pndwal:
Yes, it should with Alpha Channel set. This commit:

https://github.com/vvb2060/Magisk/commit/f2c6ee7bc2f5be6456a91e85424069e6da16a667

Not really new; @vvb2060's been a main colaborator and contributor of new functionality on (John Wu's) Magisk for some time now. 🙂

His 'Alpha' experimental builds have been available since Dec 2020, and he also has many test / experimental 'Lite' and 'MTK' builds going back to May 2020.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85127113 PW
[Magisk] sporc10:
Yeah sure in retrospect it was stupid..

Thank you for your very detailed answer.

I uninstalled the new installed Magisk manager from setttings -> ok

In settings under all apps I can see the 'old' App which is just called 'Manager' and is stated as disabled -> ok

One point is still not clear for me:

What do do now? If I uninstall the 'Manager' App will I automatically get the old Magisk manager back? OR should I better use the adb command to reenable the renamed app?
[Magisk] zgfg:
You can do either one

If you uninstall, then just install again the newest Magisk app - you will not loose anything (modules, etc), just make sure that you enable MagiskHide again.

You can also repackage then the newly installed Magisk app

Otherwise, use the adb command to re-enable your old repackaged Magisk App or Mngr (depending how old it was)

In the first case you assure that you would have the latest Magisk app.

In the second case you may need to update (upon being re-enabled)!your Magisk app/mngr if you want (and that could possibly fail if you try to update from the repackaged app/mngr)

I would go for the first option, and then also update the Magisk itself (unless you have some old device where Magisk update/installation might fail)

Edit - maybe you have an option in Settings/Apps to enable the disabled/frozen old Magisk mngr/app, in that case you don't need to use adb command for the option (2)
[Magisk] sporc10:
I went for the first option. I uninstalled the renamed package and installed the newest App.

It detects magisk again, thank you!

So it says the Magisk version is 21.1, if I want to update with the direct installation method it says "unable to detect target image". Any hints on this one?
[Magisk] zgfg:
Can you post the screenshot showing your Magisk main window to see the versions

Are you on Stable?

And sorry, you probably posted but what is your phone and ROM?

You could try patching your image but maybe it would also fail (might be that v23 does not install to your phone)
[Magisk] sporc10:
Magisk:

Installed: 21.1 (21100), A/B: Yes, Ramdisk: No, SAR: Yes

App:

Newest: 23.0(23000)

Installed: 23.0 (23000)

I am using an PH-1 with an Android 11 Rom (Build: RQ1A.201205.010)

The main 'problem' I had is solved. I have Magisk back and so far everything is working.

If I get some sparetime I will have a look on patching the boot.img. Until then I will go with the actual setup. So once again thank you for the great support!
[Magisk] pndwal:
Nice / interesting device.

Is 11 ROM modified pixel ROM?

Did you install from custom recovery originally?

"unable to detect target image" (both from custom recovery or App direct Install) is often due to fstab not containing the info where the boot block device is, or missing symlinks with proper names, making it impossible to detect where your boot image partition is. (Could be messed up vendor partition, or other.)

I'm not sure this is your problem as you did get it installed (unless pre-rooted?), but patching image manually should overcome it if it is. PW
[Magisk] pndwal:
A bit further; - I did a little digging into this because I was surprised to see a report of an A/B device w/ Ramdisk = No.

I hadn't seen (factory boot) ramdisk status change before, and I'm pretty sure it isn't meant to.

Clearly, your PH-1 is SAR by Google's definition (legacy SAR by John Wu's.) See this:

https://topjohnwu.github.io/Magisk/boot.html

and is a Type II device with a recovery ramdisk in boot partition.

Devices with any type of ramdisk in boot partition should show Ramdisk = Yes, ie. all types I, II & IV.

Type III are the ONLY type that have no ramdisk in stock (factory) boot partition! ... And these often (but not always) lack bootloader support even for manually added ramdisk in boot partition. See table here:

https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

So it seems to me there's something peculiar (messed up?) with your device, perhaps related to TWRP which resides in boot partition on Type II devices if you have this and Magisk has patched the already TWRP patched boot image. Or perhaps related to a pre-built modded boot image, Android 11 ROM (seems to be a custom port?), device tree used, etc, etc.

Anyway, I'm betting that those on stock images (including the recovery part of boot.img) w/ Magisk patched boot.img only, have Ramdisk = Yes in Magisk App...

Root guide here:

https://xdaforums.com/t/guide-rooting-your-essential-ph-1.3701976/

Incidentally, I noticed here that @ipdev has PH-1 also. Perhaps he can help with configuration, Ramdisk status, etc. 😜 PW
[Magisk] ipdev:
What ROM are you using?

Are you porting/bringing up a rom?

Let me know and I will give it a try. :)

Essential PH-1 (mata) is basically a sister to Pixel 2/XL.

Save for PH1's bootloader not having a boot option.

- You could flash taimen's system image on mata and everything normally worked.

I haven't fired mine up in a while, normally just use it for testing. ;)

---

Installed the current lineage 18.1 nightly...

Using lineage's recovery.​

- Patched the boot image with Magisk canary.

- Flashed the patched image and booted.

- Direct install worked fine.

Cheers. :cowboy:

PS.

When PH-1 was supported, before Essential closed their doors, all the official builds had a ramdisk in boot.

It is what I used to pull the monthly fingerprint and security patch date from.

PPS.

The l18.1 boot image boots AOSP Android 10 GSI on mata. ;)

“We don't make mistakes, just happy little accidents.” - Bob Ross.
[Magisk] pndwal:
This made me think, but guess meant Fastboot option!?

Many thanks for info, especially confirmation A11 (LOS 18.1) works as expected on PH-1. 👌

🤩 PW
[Magisk] ipdev:
There are a few oddities/drawbacks with Essential PH-1 (mata).

Not being able to fastboot boot is one of them.

Broken touch in recovery is another.​

You can not temporarily boot a boot or recovery image.

Only option is to flash it using fastboot.

Taught us mata users how to work around some things. ;)

Cheers. :cowboy:
[Magisk] pndwal:
Ah yes:

https://twrp.me/essential/essentialph1.html

FWIW, seems that issue only occurs if using Official pre-built TWRP (link above) w/ post Sept 2018 ROMs as it hasn't been updated since Sept 10 2018.

Simply replacing Official "initial copy of TWRP" with this TWRP patched boot image should fix touch:

https://drive.google.com/file/d/1YxJJj96Web0ikHXdHf_zboZT_KSYl7Nj/view

according to:

https://xdaforums.com/t/guide-rooting-your-essential-ph-1.3701976/

Next, updating your system by patching boot images for later builds with the TWRP Installer "will allow touch to work flawlessly".

Still, compatibility should be considered using such an old TWRP build.

Additional Information:

I saw this in 2nd post from link above:

https://mata.readthedocs.io/en/latest/

Nb. seems correct partitions are hyp & rpm.

So sideload can be used to patch active slot boot.img with TWRP Installer zip despite broken touch in initial TWRP (in inactive slot)... Or a TWRP patched boot image from a post Sept. ROM build should fix touch (for initial boot only) as it will be compatible with later hyp and rpm files... Or a mouse and OTG adapter can work... Or you could even obtain old hyp and rpm images from pre Sept. 2018 ROM and replace newer ones in inactive slot with these to get Official initial pre-built TWRP working.... 😜

https://xdaforums.com/t/official-twrp-3-2-3-0-for-essential-ph-1.3840931/post-77597383

Yup, "Necessity is the mother of invention".

I agree with that much from Plato... Alfred Whitehead and Agatha Christie can have their opinions. 😬 PW
[Magisk] Joingoin:
Hey im having trouble installing Magisk and im now searching Help here!

I already installed Magisk once and already faced troubles back then. To sum them up:

I own a Xaomi Mi 9T and have to flash to Recovery, back then i got it to work with an image i patched with Canary-Branch of Magisk.

After an Update of my Phone i have to reinstall.

Reinstall with Canary or Normal Branch Magisk Patched Recovery-Image didnt work, it always boots back to Fastboot.

What i´ve tried so far:

Patch Image with different Magisk Versions.

Use different Images.

Remove any remaining Magisk Modules using TWRP.

Attached is the only usefull Log i could find, i hope its usefull to you.

Last_Log

Thanks for all your answers in advance!
[Magisk] zgfg:
For Xiaomi Mi 9T:

- extract boot img from your recovery/zip firmware (or from tgz/fastboot firmware) or use boot.emmc.win from your TWRP backup)

- then patch that boot.img (Recovery option must be disabled by default)

- then flash the patched img to Boot partition

Yes, that is the procedure - although Magisk app says Ramdisk No, nevertheless patch the boot.img (not recovery.img) and everything will be ok

On Recovery, keep the stock recovery or use the latest official twrp-3.5.2_9-0-davinci.img
[Magisk] Joingoin:
Thanks alot for your reply.

The installation worked now, sadly Wifi doesnt seem to be working now.

I flashed the boot image a second time already since google said so ;D.

Any other ideas?
[Magisk] zgfg:
Disable all Magisk modules you may have, reboot and try again

When I used to be on stock (EEA, MIUI 10-12, Android 9-10) I never had a problem with WiFi

For the last 6-7 months I'm on Xiaomi.eu weekly MIUI 12.6, Android 11 builds, also no problem with WiFi (or anything)
[Magisk] Joingoin:
Nah still no luck., ive turned of Magisk Hide and my Saftey-Net fix both.

To specifiy: I cant turn on the Wifi, it instantly turns itself off again!
[Magisk] zgfg:
Are you sure that problems started when you installed Magisk

Disable Mobile Data and test if WiFi stays connected then

Generally, check if similar problem was reported on the Mi 9T forum or ask there (particularly for your firmware, you didn't say are you on Global, EEA, China, Russia or India and what is your particular MIUI and Android version, like V12.0.5.0.QFJEUXM, V12.1.2.0.RFJMIXM, etc):

https://xdaforums.com/c/redmi-k20-xiaomi-mi-9t.8946/
[Magisk] Joingoin:
Yeah, im 100% sure it started when i installed magisk.

The problem is not that i cant connect to a network, i cant even turn on Wifi to even at least scan for networks.

Mobile Data seems to connect but doesnt provide internet!

Im on Global MIUI 12.0.5.0

EDIT: I Downloaded the offical ROM from Xaomis Site and Patched and Flashed it and its still not working :/
[Magisk] pndwal:
Just checking, Recovery mode is unchecked when patching? PW
[Magisk] ghylander:
I have phhuser root

Before this update to the manager i could use android pay and pogo by unmounting the root, but this no longer is possible
[Magisk] Captain_Throwback:
Correct.
[Magisk] ghylander:
So is there a fix for this coming or something?
[Magisk] Tkkg1994:
There is nothing to fix??? Safetynet got updated what means magisk gets detected with its method. So it is a redundant function

You simply need to use suhide

Sent from my SuperMan powered SM-G930F
[Magisk] cubandanger05:
I can't even get safety net or safetynet playground to pass on a stock unrooted rom. Not sure if it's detecting that I'm using multirom or what.
[Magisk] Captain_Throwback:
There is nothing to fix.
[Magisk] ghylander:
So what's the point of magisk now then
[Magisk] Captain_Throwback:
The detection itself seems to be faulty. You should try an actual app that requires SafetyNet and confirm whether it's working or not. And confirm your ROM isn't running in SELinux permissive mode.
[Magisk] agentdr8:
It's what I'm sure [MENTION=4470081]topjohnwu[/MENTION] has always envisioned it to be; a framework to add mods into /system, systemless-ly. Much like the xposed framework, which does nothing by itself without modules.

Maybe it would help if it were named Magisk Framework?
[Magisk] cubandanger05:
Check and check.

Lets just say that SELinux is enforcing, and good ol' Pogo says my OS is not compatible.

Running stock Marshmallow image and stock kernel on Nexus 5. Freshly installed as secondary rom, no root, and gapps, that's all I'm running.
[Magisk] Ninoh-FOX:
I mod suhide 0.55 (I add "setenforce 1" to the file 05suhide in installer file zip) and now I have safetynet screen green... the strange is that this tomorrow this not works and now screen green... I don't know what happen...

Enviado desde mi E5603 mediante Tapatalk
[Magisk] cubandanger05:
Como le hiciste? Puedes mandarme el zip?
[Magisk] Ninoh-FOX:
Aqui lo tienes (se puede hablar español aqui?) http://cloud.tapatalk.com/s/5800fc2c6ade1/suhide 0.56 2.zip

Enviado desde mi E5603 mediante Tapatalk
[Magisk] cubandanger05:
Gracias.

No veo porque no podamos hablarlo :). No estÃ¡ en contra de las reglas.

Ahora pruebo el zip a ver ke pasa
[Magisk] Battery03:
Are you running Xposed? And preferably English rather than Spanish. This because not all understand Spanish.
[Magisk] Ninoh-FOX:
I have xposed, the more strange is that pogo not work...

I install in xposed 86.6 fakegapps too... Now I am confuse...

Enviado desde mi E5603 mediante Tapatalk
[Magisk] Battery03:
So, you can pass safetynet helper but can't play PoGo. :eek::eek: What's going on here? XD
[Magisk] Ninoh-FOX:
It is the apocalipseeee!!! XD

Enviado desde mi E5603 mediante Tapatalk
[Magisk] ataraxist:
I'm not sure how many have seen this...I tested it with non systemless su in Android 5.1.1 stock, and it could hide su. Safetynet helper and playground, both gave it a PASSED! Selinux must be Enforcing to work.

It's Root Switch apk...

https://m.reddit.com/r/pokemongodev/comments/57dpyb/_/?utm_source=mweb_redirect&compact=true

Amazing but not sure for how long...
[Magisk] Jorgesanux:
https://m.reddit.com/r/pokemongodev...etynet/?utm_source=mweb_redirect&compact=true

Enviado desde mi MotoG3-TE mediante Tapatalk
[Magisk] J.Michael:
When you flash official ROM, before trying to install Magisk, does wifi work?
[Magisk] pndwal:
Bit further:

WiFi issues w/ Magisk are usually a result of flashing mismatched patched boot image. (Search closed GitHub issues.)

I noticed latest MIUI for Mi 9T Global Stable appears to be V12.0.8.0.QFJMIXM, as of 2021-04-13.

https://xiaomifirmwareupdater.com/miui/davinci/

Mi 9T EEA is V12.0.5.0.QFJEUXM, and V12.0.5.0 is latest for other variants also.

Mi 9T Global Stable V12.0.5.0.QFJMIXM came out in 2020-10-10.

https://xiaomifirmwareupdater.com/archive/miui/davinci/

Please make sure both current ROM (Global MIUI 12.0.5.0 ?) and boot.img you patched / flashed is actually Mi 9T Global variant as well as same version (build); These must normally be an exact match, especially because boot image contains the kernel which must be compatible with system...

Otherwise, consider updating to Mi 9T Global Stable V12.0.8.0.QFJMIXM, (Nb. Mi 9T Global Stable Beta (Recovery type) V12.1.2.0.RFJMIXM Android 11.0 ROM is another available option) and be sure to extract / patch / flash boot image from this also. PW
[Magisk] pndwal:
Some early news

Latest @vvb2060 Magisk Alpha build (June 23, 2021) change log:​

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Edit:

Following are new commits:

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Display the modal waiting pop-up window when hiding/restore the Magisk application

https://github.com/vvb2060/Magisk/b...af4f3d37e69/app/src/main/res/raw/changelog.md

My earlier notes:

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

Current notes:

[It seems this build is only partially rolled out 3hrs ago, and magisk_files repo is not yet updated with package files.] Repo us now updated! Check 'earlier notes' for installation method / details.

I am not expecting Alpha build users will see Update button notice in Magisk App for this build (as with last build) as Version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

[I'll be sure to update here when package files have been uploaded.] Now updated as mentioned above.

Edit: Package already available on Telegram:

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

See post after next for details.

Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" (Delete wrong info) and "Deployment"

(Add exploit conditions).

https://github.com/vvb2060/Magisk/tree/alpha/docs

😛 PW
[Magisk] pndwal:
Some early news

Nb. It seems Lite builds will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage:

Latest @vvb2060 Magisk Lite build (June 23, 2021) change log:​

Chinese Translated:

Magisk Lite​

In Magisk in the whitelist mode, all applications are hidden by default, and only the applications ticked in Hide can obtain super user permissions. adb shell automatically has super user privileges. Module function is not available.

'magiskhide add UID package name' to add super-user application

'magiskhide rm UID package name' to remove super-user application

'magiskhide ls' lists the super-user applications

Magisk (1eb83ad8-lite)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Edit:

Following are new commits:

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy

Display the modal waiting pop-up window when hiding/restore the Magisk application

https://github.com/vvb2060/Magisk/b...a1bc0ad2802/app/src/main/res/raw/changelog.md

My earlier notes:

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

Current notes:

This seems to be only partially rolled out 1hr ago, and magisk_files repo is not yet updated with package files.

I'll be sure to update here when package files have been uploaded.

😛 PW