yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Not sure what can we see if it's recovery.log

Strange there is no magisk.log - maybe it was deleted if you flashed uninstall.zip

Must be possible to archive/compres/zip anything on PC, but you can also attach file to the XDA post directly as log or (if it won't accept log, rename to) txt file

Btw, if you did not flash uninstall.zip but you still don't have /cache/magisk.log after you flashed the img patched by magisk (and you flashed magisk.zip in TWRP as well), and you later rebooted but had bootloop, then something totally strange must be going on with Magisk on your side?!
[Magisk] AquilaDroid:
Post deleted.
[Magisk] AquilaDroid:
I'll have another look/go at this (flashing uninstall.zip) when I'm able to. Thanks for everyone's continued support!
[Magisk] AquilaDroid:
YIPPPPPPEEEEE! (American English for YES!)

I flashed the uninstall.zip, totally re-installed the August factory image, then flashed the Magisk.patched.zip and it finally has root and shows Magisk installed! Sure wish I knew what had gone wrong that kept all of you on my case for so long. I'm really glad it's working but sure wish I knew what had gone wrong initially!

THANK YOU ALL SO MUCH FOR ALL THE HOURS YOU'VE HELPED WITH THIS!

One last thing that the mods can remove if I don't take it down before it's reported - a picture of "Aquila" (that loved NZed and AUS!).
[Magisk] J.Michael:
Mazel tov.

Have you been cruising, sipping mai-tais the whole time we've been talking?

Maybe you need to describe "installed the August factory image" in more detail. The advice is usually "restore original system before applying update". If you skipped this step the first time, maybe your new "stock" system was mangled by the presence of Magisk during the install of the August updates. Not the boot partition, you confirmed you were using the same image someone else was using successfully.
[Magisk] zgfg:
He cracked!
[Magisk] AquilaDroid:
I ran the uninstall.zip in TWRP, rebooted, started a command prompt in "Platform Tools", ran "flash-all.bat (-w removed!), let it boot, went in and flashed magisk.patched.img (the checksums of all four iterations of this that I had accumulated were all the same...!), rebooted and it booted fine. The only thing that I did this last time was get rid of the "adb server version (39) doesn't match this client (41); killing..." message in the command prompt by first issuing "adb kill-server command" before doing any of the flashing. Could that have affected the result (it never has in the past)?

Thanks all, I'll be merely a "lurker" here for awhile to keep track of your antics...
[Magisk] AquilaDroid:
I'm an idiot (most of you realized that by now!). I had done: fastboot boot (patched boot.img) so when the phone rebooted after installing the V4A module it reverted to the stock boot.img. I just did that again, but will go back and fastboot flash ...etc.
[Magisk] zgfg:
But that can be used as a proof of concept. If it boots correctly, then you know that patched img is fine and you're ready to flash
[Magisk] AquilaDroid:
Exactly what I did <G>. Just in a very round-about way of continuing education! Thanks for all your help (for the 50th time?)! Now I just have to try to remember what Magisk modules I was so dependant on...
[Magisk] zgfg:
For that reason I make screenshots (and save them to clouds) for important settings like Magisk modules and hide apps; settings autostart apps and apps disabled from battery optimization, etc
[Magisk] Cruzy12100:
Hi

I have installed Magisk V23 from Github and I am able to get access for Root and my safetynet check is also passed. But gpay app is still being detected as root. I have hidden the Gpay app and google play service app from Magisk Hide and Magisk package name is also random. I am on OnePlus Nord device. Any steps that I might have missed?

Ps: Other banking apps work though.
[Magisk] zgfg:
Try with deleting Data for GPay (maybe also for Google Play Services)
[Magisk] pndwal:
As above.

GPay data needs clearing after adding to MagiskHide list. (It will often reset cached detection on its own, but may take days. Clearing data is instant.)

Also, don't add unnecessary processes MagiskHide list (causes instability due to complex timing for method used), especially Google Play Services processes. Default root-hidden is usually only SafetyNet process, com.google.android.gms.unstable. PW
[Magisk] pndwal:
Just a brain-freeze. Starts age 13. You need to enlist 12 year old. They know everything.

May have missed opportunity, but as @ipdev mentioned, once you have temporary root (booted patched image) you will have extra 'Direct install' option, and can simply select that to install Magisk; no need for further manual flashing. 😜

Somehow I think he'd be partial to Leaders & Legends, but mightn't mind VB or Speights... or even a Tooheys or a Carlton...

Cools and Guinness aren't bad either.

Haven't tried Ožujsko or Karlovačko, but I'm fairly certain they'd be popular with some here.

Personally, I'd recommend a Black Mac (with love from Terry and Beverly, and Dean), which you may have tried ...if you berthed at the right port...

Thought you'd forgotten that one. 😉 Love to hear about gulliver's travels... And ain't she a beauty! PW
[Magisk] Cruzy12100:
Did clear data for Gpay and Google Play Services. Same result.
[Magisk] Cruzy12100:
I tried this but same result. Could this be due to a ROM issue as With a different ROM I did not get this error as in the Safety Net Check passes and I do have root access with Magisk. Will posting a screenshot or Magisk logs help for debugging?
[Magisk] jons99:
31 is out and working fine
[Magisk] pndwal:
Do you have Play Protect 'Device is certified' in PlayStore settings?

If not, clear PlayStore data too, then others once certified. PW
[Magisk] pndwal:
👍 Latest @vvb2060 Magisk Alpha build (August 13, 2021) changelog:

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-31)​

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

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

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

Show waiting pop-up window when hide/restore Magisk application

App adapted to Android 12

Hide screen overlay when super user pops up (Android 12+)

For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection

Rewrite MagiskSU's logic to open pty and delete extra sepolicy rules

Fix incorrect signal sending in MagiskHide

Add untrusted_app_30

Prompt that some devices do not load the sepolicy module

Add mount information to the log file

Fix the default shell path of busybox

Oplus.fstab for oppo series devices

Use SELinux context to distinguish zygote processes *

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

*Nb. Change since last build on GitHub

1eb83ad8-alpha-30

My earlier notes:

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

Current notes:

Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

Latest in GitHub magisk_files repo is 1eb83ad8-alpha-31

Latest available from Telegram group is

1eb83ad8-alpha-31

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

Nb. In Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

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

🤠 PW
[Magisk] Cruzy12100:
Yes I Do. I re-cleared my Google play service cache and Gpay cache and now it works :-). You guys are AWESOME.

One small Question: While opening a terminal app, it does not ask me for sudo access when I type sudo. Tried with the default terminal app (enabled from developer options) and Temux . In magisk logs it says su cannot find manager. Any reason what could be the issue?
[Magisk] pndwal:
As I understand it, Android and some other Linux systems including Debian don't come with the sudo command (or similar) installed as target users don't need / have root.

You can use su instead of sudo on Android if it suits your needs. PW
[Magisk] Cruzy12100:
I also tried using su instead of su and I get permission denied.
[Magisk] pndwal:
I get the same... If I deny terminal Superuser access in Magisk! 😉 PW
[Magisk] Homeboy76:
Great job translating the Magisk alpha update logs.

alpha update log - Magic (1eb83ad8-alpha-30)

alpha update log - Magic (1eb83ad8-alpha-27)

alpha update log - Magic (1eb83ad8-alpha-25)

Thank you (y)
[Magisk] Cruzy12100:
Umm. In magisk suepruser access I have allowed both apps and ADB. Unless this is some other setting that I am unaware of.

Also what does PW mean. Slightly confused.
[Magisk] pndwal:
Well, Google (Chrome) gone done it for me... Shows how much they want to make Chinese Magisk accessible to the masses! 😛 PW
[Magisk] pndwal:
That's normal. But root apps appear in Superuser list. If you didn't initially grant root, you can enable (and disable) root access there. --> Shield icon in floating menu at bottom of home screen (swipe down). 👍

Just my initial. Old habit / my peculiarity. 😛 (Used to help me locate my posts before search included search by member function.) PW
[Magisk] zgfg:
Your Terminal app must be enabled for Superuser - like on the screenshot

When you first time typed in: su

Magisk app must pop-up to ask you to grant Superuser access for Terminal like for the other apps

If needed, clear Data/Cache for Terminal app and try again
[Magisk] Homeboy76:
:) Yes, Google Chrome might help you translate them but it is the work you put in locating the Magick alpha update logs that impressed me. Every log has a different url. They are not in one location like topjohnwu's documents.
[Magisk] Cruzy12100:
I did try that but magisk manager popup did not appear on typing su.
[Magisk] pndwal:
Yup. But @vvb2060's GitHub is actually very similar to John's; easy to get to the generic url for changelog.md etc, and that's what most users searching will find first (but of course it changes w/ next update / is not static). Here it is:

https://github.com/vvb2060/Magisk/blob/alpha/app/src/main/res/raw/changelog.md

John's are the same. If you access the file via commits under History (clock icon), you will find static URLs by date / commit.

Actually, I was in the habit of posting John's new changelogs with no reference (didn't think a citation was needed personally), but a member got antsy about that and basically pushed me to find / cite the static URLs, and I've done that since. Part of the saga / details:

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

Thanks for noticing!

- Incidentally, I've finished adding notes etc to 'Latest Alpha Magisk' post now. PW
[Magisk] pndwal:
So have you located / checked your terminal emulator is enabled in Magisk Superuser list yet? PW
[Magisk] zgfg:
Check in Magisk app, Superuser tab, maybe grant was previously denied.

If in the list there, delete it (long press and Revoke) and delete Data & Cache for your terminal app.

Have Magisk app already opened, just in case

I remember somebody reported similar issue with not getting pop-ups for root granting, his problems were in the other apps having permissions for screen overlay (preventing Magisk to pop-up)

And/or, change your terminal app 🤓
[Magisk] Cruzy12100:
Tried with different app after cleaning fo data and cache. Also checked permissions and they do not have the screen overlay permission. (Kept magisk open in background)

Also tried with terminal emulator app but still the same result . Anything else that I can try?
[Magisk] zgfg:
Is Magisk app correctly showing the version of Magisk installed (otherwise, you would have two apps, like one old/hidden and the other new)
[Magisk] J.Michael:
@Cruzy12100 How is "sudo" defined?

(This has little to do with your problem. I am curious since, as @pndwal said, someone decided not to provide "sudo" in Android environments.)
[Magisk] Homeboy76:
FYI, I read all post that contain Magisk Alpha information. I read your Magisk Alpha post two or three times to ensure I have the latest information on Magisk Alpha. The Edits provide additional gems of information. (y)

A member would have to be blind in one eye and couldn't see out of the other :) to not notice this:

(alpha update log - Magic (1eb83ad8-alpha-31)
[Magisk] Cruzy12100:
Yes magisk is showing 23.0
[Magisk] zgfg:
Did you try with some other app, like Reboot (options to reboot to System, Recovery, Fastboot):

Reboot - Apps on Google Play

Reboot menu (needs root)

play.google.com

To work, it must be granted root - first time you use the app, it should pop-up for root grant

And check in Settings, Apps, Magisk, do you have a permission and enabled like on the screenshot
[Magisk] pndwal:
@Cruzy12100, it's still unclear to me whether you have done this:

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

su should work once this setting is enabled since you have confirmed you have root (MagiskHide is working for GPay). PW
[Magisk] zgfg:
This time it was updated in parallel on Telegram and Github (previously, Telegram was a day or two ahead)

Also, so far 20, 25, 27, 30 concided with the dates of releases, now 31 just follows the previous 30

---

Btw, we're kind of spying them - translated by Google from Telegram:

yaer yo:

老外也用这个吗

Do foreigners use this too

LaíZìh🇹🇼Dė MòngWŭNeíDérHwòGérLóng:

少數有

Few have
[Magisk] hellkaim:
Hi.

I can't install a proxy app to hide Magisk from some apps.

The feild is grayed out.

I have 22.0 Magisk and 22.1 App.

On the same phone model I was able to do that, but on a new device I can't... and I do not know why.

I checked permissions for install from unknown sources with no luck. Root works with no issues...

Any help?
[Magisk] hellkaim:
Ok, just updating app to v23 solved the issue. Do not know why.

BTW Magisk can't be install on my model as the new image faild signature check.
[Magisk] ipdev:
sudo is Substitute User Do.

This will run a command as a different user.

sudo -u user command

Substitute User will default to root so if you want to run the command as root, you can drop the -u user part.

To run a command as a different user using su, you can use the -c option.

su user -c command

Substitute User will default to root so if you want to run the command as root, you can drop the user part.

Example.

mata:/ $ whoami
shell
mata:/ $ ls -la /data/adb/
ls: /data/adb/: Permission denied
1|mata:/ $ su -c ls -la /data/adb/
total 92
drwx------ 6 root root 4096 2021-08-13 18:02 .
drwxrwx--x 51 system system 4096 2021-08-13 17:54 ..
drwxr-xr-x 3 root root 4096 2021-08-05 20:21 magisk
-rw------- 1 root root 40960 2021-08-13 18:02 magisk.db
drwxr-xr-x 2 root root 4096 2021-08-05 20:10 modules
drwxr-xr-x 2 root root 4096 2021-08-05 20:10 post-fs-data.d
drwxr-xr-x 2 root root 4096 2021-08-05 20:10 service.d
mata:/ $

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Did you take Direct install? Please say device / ROM. 👍 PW
[Magisk] ASDFGHQWEZXC:
I have the app hidden with magisk hide, safetynet is both passed, twrp folder renamed/deleted, what would be the cause/solution for it? Thanks
[Magisk] Philnicolls89:
Some apps have their own form off root detection used by the developers besides just Google's safetynet checks. There are so many possibilities that it's impossible to try and guess a cause/solution for a particular app. Sorry for not being helpful but if it's only 1 app not working you may just need to resign yourself to defeat lol.
[Magisk] Didgeridoohan:
You don't mention hiding the Magisk app (repackaging it with a random package name, it's in the app settings), so if you haven't done that there's where I would start.

If you have hidden the Magisk app or could be other root apps (Titanium Backup has always been a favourite, but there are others as well), mods like Xposed/EdXposed (although then you'd likely fail SafetyNet as well), the Magisk app is impossible to completely hide until you're on Android 11 and Google enforces apps to target API 30 (this can be worked around with isolation apps and Xposed modules that hide your installed apps from other apps), etc, etc.

Could be a bunch of things...

What app is that?
[Magisk] m0han:
Spoiler content hidden.
[Magisk] ASDFGHQWEZXC:
Already done it

not using TB, xposed, or even magisk modules.

Cell operator app, https://www.apkmonk.com/app/com.linkit.bimatri/

It's ok though, not really an important app, just curious why
[Magisk] hellkaim:
Well, no it is not a direct install. The patched boot.img is provided by device manufecturer. You can find detaiuls here
[Magisk] Didgeridoohan:
Either you're using an older Android version that can't fully hide stuff, or your ROM is triggering it, or it is detecting one of your root apps, or something... Maybe you have the app installed to external storage.

Because Magisk can hide from it just fine (I just tested on my OnePlus 5T, Android 11 custom ROM, Magisk app hidden and the app on the Hide list).

Edit: check here for more.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ASDFGHQWEZXC:
Yes, i'm still using los 16, OP3, up-to-date security patch, doesn't really want to update because the lack of features i need isn't available in los 18

I will read it later. Thanks
[Magisk] pndwal:
Nice / Interesting device!

So, multi OS boot options, Android 9 and 4 month old Magisk prerooted ROM basically.

I believe you will have issues if app is installed as system app; please check it's a user app on internal memory.

Issues may include

Could also just be network access issues. - John's Magisk requires internet for stub APK download when hiding. (Nb. vvb2060's Alpha Magisk doesn't).

Same model could?... bit confused here.

Anyway, I was meaning did you take Direct Install method after updating

and trying

Guess you tried manual patch / flash here?

Can you try direct install? (Nb. It will only show when Rooted_Android boot was selected in boot mode menu.)

Not sure of how device selects / assigns boot images w/ Normal, Rooted_Android, Debian_KDE and Recovery boot modes available. I'm hoping Direct Install will handle this property. 😜

Hope it helps. PW
[Magisk] 73sydney:
Nope i get time to play with backup apps, Migrate has been working (with maybe 2 hiccups in a year and a bit) and its free, so i dont hunt paid apps that are unproven (it might be fantastic, but i aint paying for stuff i dont need, and im not an app reviewer) :) If i wanted to use a paid app id just return to MyBackup Pro :)

p.s. its entirely normal for non-root users to only get apk backups, thats universal, not backup app dependent
[Magisk] Philnicolls89:
Hi guys,

I'm trying to installed LSPosed and am getting an error saying "installation failed, please install magisk v23+".

Has anyone had this particular error with LSPosed?

I have v23 of magisk and the app installed. Screenshots below.
[Magisk] dcarvil:
The first screenshot says you have Magisk 23 installed, but the second says you have Magisk 22 installed. Are you sure you don't have two different versions (one would be hidden) of Magisk installed? Delete both versions and reinstall Magisk.
[Magisk] Philnicolls89:
That confused me aswell, I definitely only have 1 version of magisk installed. I use a custom kernel with v23 pre installed so I wasn't sure if manually uninstalling and re installing magisk would work or if it will screw with the kernel?!

*edit*

I've been using the same phone set up, rom, kernel etc for a long time and never had an issue installing modules. Thats why I thought it could be an LSPosed issue.
[Magisk] dcarvil:
What phone, ROM, kernel, versions, etc.? I have no experience with LSPosed, but I'm sure someone else in this forum will have some ideas, and that information will be helpful.
[Magisk] Philnicolls89:
That's fair enough, I tried searching through the thread using LSPosed as a search term and couldn't find any posts reporting the same issue. So it could very well just be something to do with my set-up. Thanks anyway mate
[Magisk] Didgeridoohan:
The LSPosed installer gets that version info directly from Magisk, so it does suggest there's something wrong with your setup.

Check this file:

/data/adb/magisk/util_functions.sh

What does it say at the top, for MAGISK_VER_CODE?
[Magisk] raphael.e:
I think I also had it once when there was a mismatch of the versions with Magisk manager app vs Magisk version which came along with my Rom. After installing both canary it worked. Maybe it also works to switch to stable, but not sure.
[Magisk] Philnicolls89:
That file you pointed me to says version v22, so it must be something to do with the way I installed my rom/kernel. I'm not sure if I should try to uninstall and re install magisk through the app as im using a kernel with magisk built in. Will this not cause issues?

The only other thing I can think of that would cause this problem is, before I installed the kernel I was running stock rooted firmware by patched the AP file with magisk.

I thought simply installing the kernel would be fine, but someone in the thread said that I should have reflashed completely stock/unpatched firmware before installing kernel.
[Magisk] Artim_96:
Like I said, I think it's included in the boot.img, but I'm not sure.
[Magisk] foxsprout:
Well, I recall boot.img incorporates the current kernel I'm using, so I suppose I just need to find and delete that backup-ed kernel from Magisk, which I don't know where to locate
[Magisk] Artim_96:
Just delete the .img.gz from /data
[Magisk] foxsprout:
Now that is the problem I stated before. There is no such file with that extension
[Magisk] Artim_96:
Not even stock_boot.img? Then the backup was deleted.

Anyway, then just start again with restored boot.img from ROM installation file, flash your kernel and then Magisk.
[Magisk] foxsprout:
Problem solved. I was unsure whether stock_boot.img is the file I'm looking for and turned out it was right. Thank you!
[Magisk] Radit26:
Noob question, so how do I re enable root? Can't open the magisk manager cause phh superuser module is disabled?
[Magisk] Sebastiansm:
I would also like to know
[Magisk] Artim_96:
Maybe just reflash the zip?

I don't use it but the state of the modules, but the manager has to save the save the state of the modules somewhere. I anyway looked into /data/data in the hope it's saved like in XPosed installer, but all I found was in /data/data/com.topjohnwu.magisk/shared_prefs/com.topjohnwu.magisk_preferences.xml a boolean root set to true... I don't know exactly what it does but maybe setting that to false and restarting the manager could prevent it from crashing without root rights.
[Magisk] Captain_Throwback:
Just re-flash the superuser Magisk module.
[Magisk] pdafre4k:
the first page said it doesn't works on sony, but few people here say it works fine, so is it working for sony xperia z3? thanks

and if i try it and fail will it cause any issue?
[Magisk] grep_i:
Just make a full backup and try for yourself.

That's the only way to be sure.
[Magisk] Artim_96:
It won't work with stock kernel. For all I remember try advanced kernel