yashsingh1/xdaforums huggingface dataset:
[Magisk] FlintStoned-:
[MENTION=4470081]topjohnwu[/MENTION] can you bypass the 'Kyetrade Bank' app so it would be able to login again? I've already added it to the hide section but that's not working.

If I'm not mistaking, it's using 'Vasco' as protection: https://www.vasco.com/images/Root-Detection-SDK-Integration-Guide_tcm42-69978.pdf
[Magisk] Rajdeep C:
Not able to use Tez by Google after its update.

[MENTION=4470081]topjohnwu[/MENTION] Not able to use Tez by Google after its update. Could you please make it work again?

Thank you
[Magisk] rhyvu:
Great work on Magisk. I am currently in a situation where I have Magisk installed and the phone rooted, but the current version of TWRP isn't working well on my phone anymore (that's a whole other problem) and it seems like a working TWRP might not come for a while. Therefore I am wondering if I can get Magisk to do the installation steps, but instead of writing the new boot image, just save the image so I can flash it with fastboot after resetting my device?
[Magisk] Dreamer(3MF):
Check This Thread https://xdaforums.com/apps/magisk/module-tez-hider-t3796567.
[Magisk] Groot:
[MENTION=3306843]kantjer[/MENTION] [MENTION=3730810]Badger50[/MENTION] thanks for the responses! I've decided to just flash an updated patched boot image in line with the latest beta releases to avoid malfunctions instead.
[Magisk] DroidJP:
Hey all. Looks like i am having trouble with Safety Net. Magisk can't seem to give me the final result. It goes from passing to invalid response and repeats, basically results keeps switching every time i refresh. Downloaded safety net app, it too keeps switching from pass to fail and pass again, what is going on? Lol. I completely unrooted, still same results.

Google play no longer reports certified in the settings. I made no changes to the system partition.

When i factory reset. First started off with magisk with no verity and no encrypt. But soon i noticed this issue. So used magisk manager to patch stock boot with verity and encrypt and flashed.

Device rebooted and is now encrypted, still did not fix the Safety Net issue. So completely removed magisk using magisk uninstaller. Safety Net results keeps switching.

What gives? Lol.
[Magisk] eliezerjk90:
You just describe what is called "patched boot image file", which is one option if you click install button on magisk manager. I'm not sure how to do it since I've never done it before, but I'm sure that you can see how to do it somewhere in this thread (or maybe on magisk official releases thread). It's well documented. (too lazy to do the search but at least I showed you the direction)
[Magisk] LeftDarkneesGo:
HELP ME !
[Magisk] martyfender:
Just place a copy of your stock boot.img on your internal sd card and in the Magisk Manager, click install, patch boot image file and direct it to the location you have the stock image and choose patch. Copy that patched boot.img to your computer and flash it in fastboot, or if on a Samsung device, through Odin.

Here is the command to use if using fastboot:

fastboot flash boot patched_boot.img
[Magisk] Dreamer(3MF):
Kindly Check The Following Post https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435/post77271698 To Pass The SafetyNet & Certify The Device.
[Magisk] mrspeccy:
Repackaging Magisk Manager breaks su access

I have searched this forum and thread extensively, but did not find anything sufficiently related (an exception being https://xdaforums.com/showpost.php?p=77024041&postcount=25740, which I am in doubt about). The situation is that Magisk 16.7 (and also 16.4 but not 16.0) works fine on my device (Huawei Honor 10 COL-L29 with Android/EMUI 8.1). However, as soon as I repackage the manager (5.8.3 and 5.7.0 showed the same behavior) under a random name (by saying "Hide Magisk Manager"), the list of apps having SU access is cleared in the Manager and all su requests time out. The last lines of the Magisk log say:

08-10 12:14:32.373 486 486 I Magisk : ** Initializing Magisk

08-10 12:14:32.377 486 486 I Magisk : * Creating /sbin overlay

08-10 12:14:32.378 486 486 I Magisk : * Mounting mirrors

08-10 12:14:32.379 486 486 I Magisk : mount: /sbin/.core/mirror/system

08-10 12:14:32.379 486 486 I Magisk : mount: /sbin/.core/mirror/vendor

08-10 12:14:32.379 486 486 I Magisk : bind_mount: /sbin/.core/mirror/bin

08-10 12:14:32.380 486 486 I Magisk : * Setting up internal busybox

08-10 12:14:32.446 496 496 I Magisk : Magisk v16.7(1671) logger started

08-10 12:14:32.447 489 489 I Magisk : Magisk v16.7(1671) daemon started

08-10 12:14:32.449 489 498 I Magisk : ** post-fs-data mode running

08-10 12:14:32.451 489 498 I Magisk : * Mounting /data/adb/magisk.img

08-10 12:14:32.485 489 498 I Magisk : * Running post-fs-data.d scripts

08-10 12:14:32.485 489 498 I Magisk : * Running module post-fs-data scripts

08-10 12:14:32.485 489 498 I Magisk : * Loading modules

08-10 12:14:32.486 489 510 I Magisk : * Starting MagiskHide

08-10 12:14:32.486 489 510 I Magisk : hide_utils: Hiding sensitive props

08-10 12:14:32.487 489 510 I Magisk : hide_list: [com.google.android.gms.unstable]

08-10 12:14:32.520 489 510 I Magisk : hide_list: [XXXXXXXXXXXX]

08-10 12:14:32.534 489 510 I Magisk : hide_list: [XXXXXXXXXXXX]

08-10 12:14:33.163 489 715 I Magisk : ** late_start service mode running

08-10 12:14:33.496 489 715 I Magisk : * Running service.d scripts

08-10 12:14:33.496 489 715 I Magisk : * Running module service scripts

08-10 12:15:09.419 489 510 I Magisk : proc_monitor: com.google.android.gms.unstable

08-10 12:15:58.958 489 510 I Magisk : proc_monitor: XXXXXXXXXXXX

08-10 12:17:17.727 489 10418 E Magisk : su: cannot find manager

08-10 12:21:12.430 489 11468 E Magisk : su: cannot find manager

The message "su: cannot find manager" is suspicious. However, a Google search for this error only produces a single hit at the moment, more precisely to the source code of Magisk.

Even more, after a reboot Magisk will install the Manager stub that is included in the latest betas such that my app drawer shows me two Magisk Managers, with the repacked one still be disfunctional.

I tried enabling dm-verity and used the f2fs patch to outsource Magisk to the cache partition, but this did not change anything.

Any ideas?
[Magisk] HyperCriSiS:
Hi,

Can you please add the possibility to sort modules by creation date?

Regards,

Hyper
[Magisk] rhyvu:
Thank you to you both. Sorry if I didn't explain my problem clearly, I am aware of that option, my problem is more that I would need to get a hold of boot.img somehow or download it from the internet and I rather not download some unknown boot.img to run on my device. Magisk asks for a boot.img and I was hoping there was a way to have Magisk just take the current boot.img like it does with direct install, but instead installing it, just saving it so I could flash it later.

Maybe I can manually do what Magisk does somehow with getting the boot.img file and patching it?
[Magisk] Didgeridoohan:
You somehow need to get a copy of the boot image. Best way is if your OEM is offering up a factory image/firmware package etc for download, where you can find the file inside said package. The Manager cannot grab the currently installed boot image, because that would require you to be rooted...
[Magisk] eliezerjk90:
What device (and rom) do you use? Most OEM provides the image of their ROM in an official site (or at least reliable third party web like samfirmware). It's a good chance that you can extract boot.img from the ROM zip.

Alternatively, maybe you can somehow pull the image with adb. I'm not sure and I don't know what's the code though. Maybe someone here knows.
[Magisk] zeroprobe:
I think it may be to do with zip compression and size calculation. When I didn't compress the zip 60MB instead of 30MB, I could install 4 versions of my module with different ID. Still had the same issue trying to install a 5th version.
[Magisk] :
Just wanted to put this here. I've been using Supersu for years after Darken sort of let Superuser go and I've only had Magisk downloaded 24 hrs and am blown away at the difference! Excellent job dev!
[Magisk] IronTechmonkey:
Pardon some off topic clarification:

AFAIK Darken is not the developer of Super SU but rather is the developer for the very good utility named SD Maid. As to SuperSU the developer was Chainfire who did not "let it go" but rather sold it while it was in good shape and then it was CCMT who let it go. I don't want to inflame any past debates and I apologize for the off topic but if you are going to say that a developer did something at least name the one who actually did it.

That all being said, for newer devices and current development that can be trusted Magisk is the way to go.
[Magisk] Pkt_Lnt:
The superuser before Chainfire was Superuser and Superuser Elite (pro key) by ChainsDD. That was the first root app I used way back in medieval times of Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich. :good: :D

Only the pro key is still in the Play Store. A web search will give you more history if you want.

https://play.google.com/store/apps/details?id=com.noshufou.android.su.elite

https://github.com/ChainsDD/Superuser

https://www.xda-developers.com/superuser-app-gets-refreshed/

Koush also had a version along with CMT recovery.

https://www.androidpolice.com/2013/...d-effort-for-apps-to-declare-root-permission/
[Magisk] srose sp:
Remove systemless supersu by restoring stock boot from previous roms backup,install magisk and its booted but after wipeing cache its not booting i backuped rom before wiping cache so i restored but still not booting please someone reply because i get good battery in this rom but i also want magisk not supersu
[Magisk] mrspeccy:
Sorry for re-posting this, but I am really unsure which thread I should use to ask for help. I found a related issue here: https://xdaforums.com/apps/magisk/hide-magisk-manager-v15-function-changed-t3725895/page4
[Magisk] Didgeridoohan:
Would you mind sharing your module for testing?

Have you tried dirty flashing your ROM? And have you asked for advice in the ROM thread (usually the best place for ROM specific questions)?

That Magisk can't find the Manager means the new package name wasn't properly added to the database. I've seen that on an internal test build, but I don't know when it appeared. It's been fixed, so you could test an unofficial snapshot of the current code to see if it's that issue you're experiencing.
[Magisk] filazaf:
Hello i wanna install Magisk 16.0 and and 16.7 on Vernee X and ...

http://www.wklejto.pl/608396

Infinite loop.

1. Clean ROM

2. TWRP

3. Whipe data - because i get encrypted file system

4. Install Magisk

5. Infinite loop

I do the same with SU and it's ok.

Please help
[Magisk] mrspeccy:
Thank you. Unfortunately the latest unofficial builds (tried the 2018081113 Magisk zip and the accompanying manager) show the same behavior. Also 16.7 and 16.4 have the problem, in connection with both MagiskManager 5.8.3, 5.7.0 and 5.6.4 etc. It seems that at the moment where the manager repackages itself root is lost and the information about the repackaged name cannot be transferred to the database. May it be a synchronisation problem, something that is unique to Huawei EMUI 8.1 ROMs?

As a workaround, how could I manually edit the magisk.db database to feed it with information about the new package name?

Edit: I looked into /data/adb with a root shell and found that the "magisk" folder belongs to root (user and group) but magisk.db is owned by "u0_a292" user and belongs to a group of the same name. Could there be something fishy here? Also, /data/adb is owned by root but it is not world readable ("drwx------") in contrast to many other folders within the /data directory.
[Magisk] Didgeridoohan:
Do a clean install of v16.7 beta (uninstall everything Magisk related, Manager and all, and reinstall) and then grab a logcat when you're repackaging the Manager and the issue manifests.

Edit: Yeah, magisk.db should be owned by root... But /data/adb should not be world readable. That's how Magisk hides it's files from non-root processes.
[Magisk] eliezerjk90:
I just notice that the fingerprint authentication not working on latest MagiskManager. Have the setting enabled but when it prompts root access it shows the normal grant button. Anyone has the same problem?

I tried unofficial build by kantjer just to test and it works fine in his build, so I guess the problem is in the official MagiskManager app. I use mido with official LOS 15 rom, official magisk 16.7
[Magisk] martyfender:
If that unofficial build works, then why not stick with it until The new stable version is released? Many bugs have been fixed in recent unofficial releases. If you find one that works, there is no reason you have to keep updating it like I do.

I update to the newest builds almost daily, but I am willing to risk newly introduced bugs, knowing that I have a good recovery plan in place. I try to report bugs to further future development.

Is Mido a Xiaomi Redmi Note 4? That and watches is what I found in a Google search.
[Magisk] mrspeccy:
I did so (hoping that the log is appropriate; I removed some personal information such as a list of installed apps from it). The new package name is com.xhl2.G85RqoHHwWu.

What I find suspicious is that a root access requested few seconds after repacking was still granted (AdAway) but that all following requests timed out.
[Magisk] Didgeridoohan:
What happens if you change magisk.db ownership to root prior to repackaging the Manager?
[Magisk] eliezerjk90:
I agree with you! I'll use the unofficial build for now. I just posted it because I'm aware that so far no one post it before me. So I just want to make sure if it's only my problem or it's a common bug. And the post is more like an info for the developer so he aware of it and can address it properly in the next official build. ?

And yes, mido is code name for redmi note 4 snapdragon.
[Magisk] mrspeccy:
Nothing changes. I used a root shell to fix the owner, but the repackaged Manager is not functional and after a reboot I again have two Managers. After upgrading the stub to a full Manager, the owner of magisk.db is again changed to u0_a117.
[Magisk] LivArt:
Is it possible for somebody to make module, tak makes new sms, which has been opened from notification (or replied from notification) read? Now it stays unread and this is very annoying for me. Thanks
[Magisk] RandomPooka:
Textra.

The notification has the standard "Reply" button, a "Mark as Read" button, and a setting in the app to mark it as read if you swipe the notification away
[Magisk] Chouiyekh:
hi guys,

i have pixel 2 xl running the latest version of android 9 (P), rooted by magisk 16.7, i have a problem with using fingerprint sign in on a bank's application, it was working on android 8.1 rooted
[Magisk] xunholyx:
I had this before and just had to reset my fp sign in my banking pp.
[Magisk] Rukbat:
And if that doesn't work, the bank has to update their app.
[Magisk] zukers:
problem solved,, please delete
[Magisk] HaMaHe:
I am not really sure if I understand what steps to follow in order to install Magisk in my situation.

I am running custom rom LineageOs (Unofficial) 14.1 on my Galaxy S4.

How do I install Magisk?

Do I need Stock Boot image?

Do I need to flash Stock Boot image first?

Do I need to go back to stock ROM?

I am not sure how to proceed. Can anyone help?

thank you
[Magisk] KevMetal:
You can download official firmware and extract it to find boot.img inside .....

If no official update or firmware for your device is available you have a catch22 since you need a rooted device to easily extract your boot.img but you need your boot.img to root via magisk ....

---------- Post added at 02:27 PM ---------- Previous post was at 02:05 PM ----------

Just flash lineage

DONT FLASH SUPERSU

After flashing lineage just flash magisk .zip

*job done

If it moans about boot.img you might have extract your boot.img from stock rom .zip
[Magisk] teddy0209:
Stock Boot.img here means, the boot.img of your rom (in this case lineage) which is unpatched by other root like SuperSU... You can dirty flash your room then flash magisk after, or extract the boot.img from the room zip, flash it then flash magisk, or you can patched the boot.img manually with magisk manager then flash the patched_boot.img... The first is simpler in my opinion... Good luck!!!
[Magisk] HaMaHe:
Ok, thanks a lot! That sounds much simpler than I feared. So, if I may sum it up:

- I flash my LineageOS dirty with TWRP

- Then before rebooting I immediately flash Magisk (not Magisk Mgr)

- Then I reboot. Then I have Magisk installed.

Correct?
[Magisk] teddy0209:
Exactly...
[Magisk] ThugDang:
my s8+ is rooted. how can i dump my stock boot image file? i can't install magisk because of this
[Magisk] DroidJP:
Is anyone getting reponse is invalid from Safety Net?
[Magisk] KevMetal:
From the official stock rom ( extract it )
[Magisk] jenslody:
Since several days google servers seem to be a little bit wonky.
[Magisk] DroidJP:
Yeah, i am starting to noticed, even going completely back to stock still fails or invalid reponse. Despite all this, play store still says certified and Netflix still shows. So not going to worry about it unless it's really an issue.
[Magisk] HaMaHe:
If your ROM is stock, I guess you need to download it and then extract the boot.IMG from there.
[Magisk] mrspeccy:
I tried to understand what the log reveals but don't really understand what is going on. There is one strange message, though.

08-12 07:36:20.526 I/AppInfoManager( 1835): not delete app info from db : com.topjohnwu.magisk because app exists in other Users

What could that mean?
[Magisk] xabier-bo:
Hi

Sorry if this problem has been solved in any other place, but I've not been able to find it.

Device: Nvidia Shield Tablet 2016 (16 GB). Oreo (nvidia's 7.0.2).

Magisk: current version 16.7, but it was the same in previous 16.0

Installed through twrp-3.2.3-0-foster.img (able to mount vendor).

No error warning. Everything is working, except:

every time I boot I need to re-grant superused apps.

I've already fully removed magisk (with magisk uninstaller), and reinstalled it, but the problem remains.

Is anybody experiencing this problem?

If it's already solved, could you point me to the post?

If not, could any of you with Magisk's inners knowledge, give me a clue of where could be the problem (where is the granted apps list stored..., and why it doesn't survive)

PS. The magisk's log...

08-13 22:12:27.334 307 307 I Magisk : ** Initializing Magisk

08-13 22:12:27.335 307 307 I Magisk : * Creating /sbin overlay

08-13 22:12:27.338 307 307 I Magisk : * Mounting mirrors

08-13 22:12:27.338 307 307 I Magisk : mount: /sbin/.core/mirror/system

08-13 22:12:27.338 307 307 I Magisk : mount: /sbin/.core/mirror/vendor

08-13 22:12:27.339 307 307 I Magisk : bind_mount: /sbin/.core/mirror/bin

08-13 22:12:27.339 307 307 I Magisk : * Setting up internal busybox

08-13 22:12:27.388 314 314 I Magisk : Magisk v16.7(1671) logger started

08-13 22:12:27.389 310 310 I Magisk : Magisk v16.7(1671) daemon started

08-13 22:12:27.393 310 316 I Magisk : ** post-fs-data mode running

08-13 22:12:27.394 310 316 I Magisk : * Mounting /data/adb/magisk.img

08-13 22:12:27.454 310 316 I Magisk : * Running post-fs-data.d scripts

08-13 22:12:27.454 310 316 I Magisk : * Running module post-fs-data scripts

08-13 22:12:27.454 310 316 I Magisk : * Loading modules

08-13 22:12:27.455 310 331 I Magisk : * Starting MagiskHide

08-13 22:12:27.455 310 331 I Magisk : hide_utils: Hiding sensitive props

08-13 22:12:27.455 310 331 I Magisk : hide_list: [com.google.android.gms.unstable]

08-13 22:12:29.270 310 500 I Magisk : ** late_start service mode running

08-13 22:12:29.270 310 500 I Magisk : * Running service.d scripts

08-13 22:12:29.270 310 500 I Magisk : * Running module service scripts

08-13 22:12:29.416 310 500 E Magisk : sqlite3_exec: no such table: strings

08-13 22:13:05.340 310 331 I Magisk : proc_monitor: com.google.android.gms.unstable

08-13 22:13:16.091 310 4146 E Magisk : sqlite3_exec: no such table: settings

08-13 22:13:16.091 310 4146 E Magisk : sqlite3_exec: no such table: strings

08-13 22:13:16.091 310 4146 E Magisk : sqlite3_exec: no such table: policies

08-13 22:13:17.650 310 4253 E Magisk : sqlite3_exec: no such table: settings

08-13 22:13:17.650 310 4253 E Magisk : sqlite3_exec: no such table: strings

08-13 22:13:17.650 310 4253 E Magisk : sqlite3_exec: no such table: policies

08-13 22:13:30.686 310 5822 E Magisk : sqlite3_exec: no such table: settings

08-13 22:13:30.687 310 5822 E Magisk : sqlite3_exec: no such table: strings

08-13 22:13:30.687 310 5822 E Magisk : sqlite3_exec: no such table: policies
[Magisk] guest4711:
It looks like you used the multi-user feature of Android and MzgiskManager is installed for another user, too. So you should make sure MagiskManager is deindtall for all but the first user before hiding/repacking it.
[Magisk] Didgeridoohan:
Do you have several users on your device?

The superuser permissions are stored in /data/adb/magisk.db and apparently there are issues with it on your device. Do you have that file?
[Magisk] xabier-bo:
Thanks Didgeridoohan

It exists but (after copying it to sdcard) I've seen it contains no table)
[Magisk] Didgeridoohan:
I did some quick testing and repackaging the Manager if not on the main user account is severely broken... If you've used a secondary user to hide or unhide the Manager you'll have to uninstall the Manager on that account, make sure the Manager isn't hidden on the main account and then reinstall it. Only hide and unhide the Manager on the main account, unless you've set Multiuser Mode to independent.
[Magisk] Chouiyekh:
i already had two options to sign in but i hope and i prefer to get fingerprint sign in work, any help ?
[Magisk] xabier-bo:
Hi again

I've tested to edit magisk.db.

I've manually added a few apps.

After that, these specific apps no longer require to be granted, but:

- they are not shown in the superuser menu

- apps not added manually require new granting after boot.

Any idea?
[Magisk] seffparker:
Magisk 16.7 SafetyNet check is failing with error message "The response is invalid". Google's SafetyNet API is returning the following:

1 {

3 {

6: "Your application needs its own API key - please see https://developer.android.com/training/safetynet/attestation-checklist"

}

}
[Magisk] DroidJP:
Just ignore. All is working fine for me despite of failed/invalid reponses. I wonder if we overloaded safety net servers by everyone trying to check it all the time [emoji23]
[Magisk] DanGLES3:
Not really,its just the api that magisk and safetynet checkers use is now deprecated if you dont use an api key,here's tophjohnwu post on the matter
[Magisk] Didgeridoohan:
Not really... What are the permissions and owner for the database file?
[Magisk] mrspeccy:
Thank you. Very strange that I get this error message about multiple users. In fact, I never even touched the "Users" settings on my phone and always worked with the default user only. Maybe Huawei's Android variant adds some "phantom" users to the system that mess things up? How can I get a list of Android users from a su shell?
[Magisk] Didgeridoohan:
Hm... Then I don't know. Huawei does do some weird stuff, but I don't know what this could be.

You can check in Android settings - Users if you have more than one user. And you could also check in /data/user. If there's more than one folder (0), you have several users accounts on the device.
[Magisk] Aki_9982:
Sir...topojo(if i wrote I'm sorry)with due respect i like your work on magisk manager it really is a gift for the root users

But I am getting error in safetynet check and the response shows invalid can anyone help me or guide me how to fix it...i am on miui9 global stable built latest

I am also posting the screenshot of the magisk home screen below hpe it might help u.... I'm on 7.0 nougat

My device code name is mido
[Magisk] kantjer:
Follow the steps below:

1. check the last few pages of the thread

2. use the search function.

these steps can also be used for other issues :rolleyes: