yashsingh1/xdaforums huggingface dataset:
[Magisk] andrew_yousry:
Bank application still detect root

Dear [MENTION=4470081]topjohnwu[/MENTION]

I'm facing a very frustrating problem with my bank application which still detect magisk latest version with hide magisk manager & hide and magisk hide for the bank application applied, ctsProfile & basicIntegrity both true.

I tried many things to check why still the application detects root, I tried removing everything uninstalling magisk and application still detects root, I thought it may be detecting the unlocked bootloader, I did format my memory & reinstalled system firmware to get new android ID, in case server locks the rooted ID and also to have bootloader locked again. I could use the application, It worked also after unlocking the bootloader, and it worked after installing Magisk [with hiding manager and and hide for application applied]. it detected root once I started installing modules [modules installed were: busybox NDK, Vanced Youtube, systemless hosts only].

can you help me with to be able again to use this app

google play link for the app:

https://play.google.com/store/apps/details?id=com.ducont.muscatbank&hl=en
[Magisk] mewbow1:
Open Magisk Manager

Right Swipe from left edge -> Click on MagiskHide

Search your banking app and tick it.

Now again Right Swipe from left edge -> Settings

Click on Hide Magisk Manager

Scroll down and Switch OFF MagiskHide and again Switch ON MagiskHide

Clear the data and cache of banking app

And try to open the banking app again
[Magisk] BrahmaGandhi:
after enabled the systemless-host in mm setting, then i want to edit/replace the host file, which path is correct or safe to do that?

/data/adb/modules/hosts.....

or

/sbin/.magisk/img/host....

*magisk 20.2, havoc Q*

thanks!
[Magisk] guest4711:
Use the one in data. /sbin/.magisk/img is a deprecated compatibility link for older modules (but replacing it should work, too).
[Magisk] Cheako:
NX627J: g.co/ABH

Hello, I've taken an official boot.img file and uploaded it to my phone then patched it and flashed to boot. Booting resulted in an error and soft brick https://xdaforums.com/nubia-z20/help/g-co-abh-t4009569

What does this patched image do and how can I undo it? I've tried to flash the official boot.img and this is inadequate. I now learned of a new developer option I should have set.

My image files are here: https://mikemestnik.net/archives/

Thanks.

Edit: I don't have a Windows computer available, so the current method for installing TWRP is out of reach.
[Magisk] martyfender:
Yoh didn't, by chance, try to do all of this with a locked bootloader, did you?
[Magisk] aschleon:
How to remove Preserve Force Encryption & Preserve dm-verity?

Hello all, can anybody guide me how to remove the Preserve Force Encryption & Preserve AVB 2.0 / dm-verity option on Magisk Manager? Because it kept on coming back after I reopen the app.

I am a newbie and mistakenly checked the 2 options, dont really understand what those 2 options for. I recently realized that I cant no longer uninstall my system apps, I usually freezed them first through Titanium Backup and Uninstalled them later, but after I uninstalled and rebooted my phone, the system apps such Calculator, Calendar, etc kept on coming. When I tried to uninstalled them by another apps they gave me boot-loop. So now I can only disable them.

Are those two options on Magisk Manager related to my issue?

And how can I properly remove the checked mark?

Ps: I used Eu ROM & Kosmos ROM, both gave the same issue.
[Magisk] ktmom:
Those checkboxes are used to configure the patched boot.img when patched through the manager. They don't affect the running kernel otherwise.

I'm guessing you're not in the habit of reading release notes. Since 19.4 Magisk follows the Google standard for system as root (SAR). This has been discussed numerous times in this thread. There are a few work arounds for devices that are on some custom rooms or older devices not on A10, like using root explorer or mi explorer or just using a systemless debloater or freezing apps like you're doing.

---------- Post added at 07:21 ---------- Previous post was at 07:03 ----------

Since you don't say, and looking at other posts you've made, I'm guessing you are having trouble with a ZTE Nubia Z20.

The standard recovery from a boot loop after flashing a patched boot.img is to flash the stock.img as you said you did. You'll want to make sure the stock image you're using matches the one on the device before you started.

If your bootloader is not properly unlocked, it should not have accepted the patched boot.img. Resolving this is best done in the device forum where others with your device are available to help.

Since that's a new release device running Pie, it's possible root has to go to the recovery partition, not the boot partition. Have you read the installation instructions?

OT: As far as your trouble installing TWRP under Linux, try either wine or use a virtual machine (VM). There are loads of tutorials online if you search for them.
[Magisk] Paget96:
Moving app who requires root to /system/priv-app not asking for root rights. When app should ask for root instead of dialog it opens Magisk manager. This not happens to all the users, mostly it's on android 9 or 10 [MENTION=4470081]topjohnwu[/MENTION]

Other fun fact, when this happens other apps wont get root also, are there any Magisk issues at that side?

Tried searching in logs.

--------- beginning of crash
11-22 15:40:06.802 606 7417 W Magisk : su: request rejected (10243)
11-22 15:41:09.640 606 9281 W Magisk : su: request rejected (10243)
11-22 15:41:09.641 606 9281 E Magisk : write failed with 32: Broken pipe
11-22 15:41:32.197 606 9803 W Magisk : su: request rejected (10243)
11-22 15:41:32.197 606 9803 E Magisk : write failed with 32: Broken pipe

Thanks

Edit:

I have attached zip so you can check it up.

While flashing the zip it extract an app to /system/priv-app. Not all users have issues with root, but some of then have issues showed in log above.

20.1:MAGISK (20100) is version used on those devices
[Magisk] JustGuardianIT:
Also my problem

This is laso my problem: when an app requires root it opens magisk. I am on android pie and on a xiaomi redmi s2. If you find a solution please say it there. Thanks a lot if you do.
[Magisk] Paget96:
One of the problem my users have mentioned is that they open up the app, then close app and open again, it somehow pass it. But this is not a thing which can be recreated, so we don't know in what state it happens.
[Magisk] Dry_ice808:
Getting stucked at the magisk manager splash screen, facing freeze sometimes & some apps like terminal emulator or wps tester are not able to get root access....even LSpeed was not able to gain root, this needs to be fixed...

Using Zenfone X00TD / Pixel Experience Q
[Magisk] Paget96:
If you have some logs, pass it here so [MENTION=4470081]topjohnwu[/MENTION] can do a check. Also, don't forget to tell what device, android version, OS and Magisk version are you using.
[Magisk] jcmm11:
I suggest you try the latest Canary to see if it's been fixed. This holds for pretty much any issue. If it's still broken use the debug version of Canary to get Magisk logs.
[Magisk] Paget96:
I have passed your message to my users, so they'll try
[Magisk] CleaveGodz:
I suggest making a temporary fix. Since the superuser dialog sometimes only shows in home screen, you could call the main activity of the launcher *before* root rights are asked so the user is guaranteed to see the pop-up. Just until we find what is the real reason behind that problem, it could even be optional.
[Magisk] Paget96:
That happens if draw over other apps is not probably enabked for Magisk Manager, maybe?
[Magisk] g7755725:
Found the solution

[MENTION=5514152]Paget96[/MENTION] I have found the Magisk Problem's Solution, To get the Root grant, Just go to Magisk Manager, open its Settings and change the Promt to "Grant". Then open L Speed Manager and you will be granted Root Permission in a few seconds.
[Magisk] Anirudh@123:
Screen freez after installation no fix from previous

Screen is freezing and random shutdowns no fix

Same problem exists
[Magisk] Paget96:
App dont appear in there until it don't reject or grant root for it.

It just stuck in a process.
[Magisk] Anirudh@123:
No sir u are not understand, opening lspeed application after rebooting the device . I have made some modifications that too not big changes after a while phone hangs and shutdowns. This happens every time I have checked all latest versions.

I am using Android 10
[Magisk] Paget96:
Provide logs so we can do a check on that side.
[Magisk] martyfender:
I have not yet tested the Magisk module version of Lspeed. I am still on the app version of it, 2.1.2-beta2 and root with the latest Canary works fine on both my Android 6 tablets and also my new Android 9 tablet.

I will wait until govtuner is added to the Magisk module version of it, before I test it.

I have Greenfiy as a /system/priv-app and it works fine. I use the Magisk Module, App Systemizer (Terminal Emulator) to move it to the system. I do suggest your users test the debug version of Magisk Canary where better logging is created.
[Magisk] Paget96:
That's what I'm suggested, now we will see whats going on here.

Thanks for reply
[Magisk] Be4st187:
Huzzah!! The Magisk opening on boot issue that others and myself have been having is down to Magisk starting later than the app that's requesting root. The app I have present that does this is Tasker. I removed all of Taskers permissions and disabled Magisk and Tasker from boot, rebooted and the issue was gone. The second I hit the 'make device admin' option for Tasker or allowed it to run a script, Magisk opened. Next reboot, I opened Magisk first, closed it and then made Tasker a device admin and ran a script and Magisk didn't open.

Need to find a way to delay Taskers root request a couple of seconds or make the Magisk app boot first before anything else.
[Magisk] RandomPooka:
Do you absolutely need Tasker to be set as admin?
[Magisk] Cheako:
Thanks for the reply. I'm sorry I made things difficult! This is about my Nubia Z20. I'm confused why flashing the *stock boot.img didn't restore, I get the same message. I wanted to know more about what the patched boot img does/is. I was curious if I needed to write my own boot.img that undoes some patching or bit twiddling done by the magisk patched boot.img. <inquisitively>I noticed the patched boot.img file being smaller, I assume that's because the original image is compressed?</inquisitively>

* There are 3 firmware images available from Nubia, the latest should match my system. I tried all three for completeness sake.

OT: Please note that Wine does not have any USB drivers in it's kernel, so running adb.exe or fastboot.exe and similar will just crash. I dread finding a pirate copy of Windows to download and then there is the **fight for just installing it, let alone getting it stable enough to run applications. USB passthrough is an option for most VMs, so this would be applicable for someone with a license to run Windows and I'd be happy to advice(for USB device) anyone in that situation.

** Note that a fresh install of FreeBSD is something like 30 seconds and Debian gives the possibility to run applications while it updates after only about 5 minutes(assuming you know to Alt-Fn to another Virtual Console). From what I remember a Windows install is 30min or more of just starting into a void, why anyone would sit through that or suggest that as an option is beyond my comprehension.

---------- Post added at 02:08 AM ---------- Previous post was at 02:04 AM ----------

Sorry for all the repeated posts, I was getting a bad gateway error and didn't know that my post was accepted. I've submitted it to the XDA portal.

---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------

Sorry for all the repeated posts, I was getting a bad gateway error and didn't know that my post was accepted. I've submitted it to the XDA portal.
[Magisk] zzz2002:
If I remember correctly there is Linux version of the android development kit, which includes adb and fastboot. I think it works with Debian. Sorry to be so vague but I have not needed it for last couple of years.
[Magisk] ktmom:
[MENTION=4991290]zzz2002[/MENTION] [MENTION=4403217]Pkt_Lnt[/MENTION]

That's not [MENTION=7936337]Cheako[/MENTION]'s problem. The only TWRP installer for the Z20 appears to be a Chinese windows executable. Nothing available for Linux.

This is heading off into OT territory.
[Magisk] martyfender:
When this happens, don't keep hitting the post reply button again. Instead, go back a few pages, then go to the last page of the post again and in my experience, your reply will have been post, like normal.

Over a period of quite a few years, xda is the only forum that I have had this happen. Does anyone know why this happens on xda?
[Magisk] Cheako:
Sorry I wasn't clear. I was using those examples to indicate why running a Nubia Z20 TWRP installer(https://xdaforums.com/nubia-z20/how-to/twrp-install-t4008263), that looks like malware any way I look at it, wouldn't work in Wine.

---------- Post added at 04:17 AM ---------- Previous post was at 04:11 AM ----------

I'd like to help fix this. Sounds like a cross-site scripting attack vector, not having the form keyed by an ID of some sort.
[Magisk] zgfg:
Please be a little patient when pressing Send (or use another device/browser/app), there is no need to post the same answer four times
[Magisk] Cheako:
Thanks for pointing that out! This will happen until the form software can detect duplicate submissions, so get used to having this happen from new users. It's unreasonable to force everyone to learn about this feature as there will be ppl who haven't seen form software do this and you can't possibly teach them all.

I believe I've apologised and taken steps to correct, but I'm not a web developer at XDA so there is little I can do
[Magisk] Be4st187:
Probably not. After digging a little further, it seems Tasker doesn't need to be set as admin to trigger this issue. If Tasker and my other culprit app ElementalX Kernel Manager are allowed to boot when the device boots, then the repackaged Magisk has a hissy fit. When those 2 are disabled, there is no issue.
[Magisk] ViBE:
i guess my problem is not a new thing but pretty hard to seek after ~3700 pages. so i have a Xiaomi Redmi 4X with MIUI 11. it's in a stock state and i installed Magisk 20.1. then i installed Terminal Emulator and when i tried to run su it stuck for a while then it says that the permission just denied. no prompt, just denied. Root Checker says that root is working btw. any solution for this?
[Magisk] Hellozepp:
Help Pls

- Cihaz platformu: arm64-V8A

- önbelleğe görüntü Kopyalama

içinde 1566 + 0 kayıtları

üzerinden 1566 + 0 kayıtları

1.603.584 bayt (1.5 M), kopyalanan, 0,003287 s, 465 M /

1045 + 1 kayıt

üzerinden 1045 + 1 kayıtları

(1.070.668 bayt 1,0 M) kopyalandı, 0,002738 s, 373 M / s

-

Açılış resminin açılması Açılış resminin ayrıştırılması: /data/user_de/0/com.topjohnwu.magisk/install/boot.img

! Desteklenmeyen / Bilinmeyen resim formatı

! Yükleme başarısız

Yardım
[Magisk] mrvanity:
Hi there.

it supports amlogic devices. It seems the problem is on pie 9.0 roms. In the same boxes in oreo 8.1 magisk worked just fine (i think v18 only).

What kind of logs are required in order to investigate more?

My regards.

P.S.
[MENTION=4544860]osm0sis[/MENTION] I have uploaded a boot.img of a pie rom here.CPU is amlogic s905x2

GT1 Pie 9.0 boot.img
[Magisk] jcmm11:
English must be used. You can post in your native language but include a translation as well. Try to keep the language simple and use Google translate.

İngilizce kullanılmalı. Kendi dilinizde yayınlayabilirsiniz ancak bir çeviri de ekleyebilirsiniz. Dili basit tutmaya çalışın ve Google çeviriyi kullanın.

What device are you trying to install on?

Hangi cihaza kurmaya çalışıyorsun?
[Magisk] Hellozepp:
my phone is k20 pro and i use it on this device. K20 PRO 8/128GB

---------- Post added at 01:29 PM ---------- Previous post was at 12:44 PM ----------

what we'll do right now. Will we process the IMG file?
[Magisk] mrvanity:
The link of stock boot.img was uploaded in continuance of [MENTION=8126387]martyfender[/MENTION] mentioning sending a stock boot.img to [MENTION=4544860]osm0sis[/MENTION]
[Magisk] ktmom:
Wow, this conversation is next to impossible to follow. It seems to have started with:

If this is the the issue, then nowhere has it been stated what the problem is. The image certainly appears to go through the patching correctly on 20.1. So I guess, there's a problem booting after flashing the patched image?

The more complete a problem report is, the better your chances of getting help. Comments like, "it doesn't work" is akin to going to the doctor and saying I sneezed. [emoji6]

Start with explaining exactly what you expect to happen that is not happening. Providing detailed information as to the Android version and device so readers are not forced to hunt through the thread would only benefit you.

You should also try the canary release and provide logs using that release since it provides more verbose logging.
[Magisk] Hellozepp:
[/COLOR]

osm0sis mail gönderdim
[Magisk] RandomPooka:
That's so strange. I've got Tasker running with hidden Magisk Manager out of the box. It sets certain environment variables at boot, but have never had issues with it trying to request root before Magisk is ready for it. Maybe I'm misunderstanding your setup, and there's other stuff at play here.
[Magisk] osm0sis:
No. Do NOT email me things. I will NOT respond to emails or PMs looking for technical support.

I have deleted your email.
[Magisk] Hellozepp:
Okey
[Magisk] Be4st187:
That could be possible as I have just wiped my phone, loaded MicroG instead and the Magisk popup spam was never ending. Magisk itself is fine and works superb, its just when I repackage it to hide it when it plays up.

I thought it was fine with MicroG the other day, but it seems not.
[Magisk] osm0sis:
Not sure if these are the same device or not, but this looks like a normal SAR image to me with no ramdisk present.

Magisk patching creates a cpio ramdisk to force the boot from, but not all devices support this scenario (e.g. Samsung).

Does an Oreo 8.1 boot.img have a ramdisk still? Maybe upload one of those for me to check.

Sounds like a similar situation to this issue, where the OEM removed the ramdisk to go SAR on the latest update: https://github.com/topjohnwu/Magisk/issues/2063#issuecomment-558266030

Have you guys tried the latest (20108) Canary? There was a fix in there for some legacy device rootfs ramdisk support, perhaps could help with your situation too.
[Magisk] Didgeridoohan:
That sounds like your device has issues with broadcasts, resulting in the Manager having to claim full focus on su requests when hidden. Or something along those lines...

Have you tried the Canary builds? [MENTION=4470081]topjohnwu[/MENTION] has moved to a new communication method that should work a lot better and not bring these kind of weird issues.
[Magisk] mrvanity:
Hello again.

In the below link there are 9.0 boot image, 8.1 boot image and recovery logs from twrp.

Boot images and logs

The installation of latest magisk canary debug via twrp ends successfully, but magisk manager (latest debug canary) reports that magisk is not installed.

Also root checker reports not root.

It tried to uninstall magisk via twrp and reinstall (both successfull) and uninstall/reinstall manager. No go.

installed this as well, but no luck

https://xdaforums.com/apps/magisk/magisk-installed-workaround-t3908748

Some more info

The stock roms comes prerooted with custom root binary.

Installling magisk manager apk, removes this prerooting (for some reason)
[Magisk] stingbandel:
what is the latest version? is it 20.1 or 20.2? I keep getting update notif but when I go here I only see 20.1 as the latest.

I tried install 20.2 through the patch method and it bricked my phone as it change my phone from LG V20 H990DS to LG V20 US996 which is US version. I am able to fix it by using my boot file recovered from somewhere on my computer.

Should I try to install 20.2 through TWRP or I just wait?

thanks
[Magisk] jcmm11:
The latest stable/beta is 20.1 (20100), Manager 7.4.0 (253)

Latest Canary is 20.2 (20108), Manager 7.4.1 (260)

Changing Magisk versions shouldn't change your recognized phone variant. Are you using the "MagiskHide Props Config" module by any chance? Or some other method of changing the build fingerprint?

When you use the patch method are you patching the same boot file as you use to recover? (If not, why not?)

Trying through TWRP certainly won't hurt, if necessary you'd recover the same way as currently.

I'm not sure if full install logs would help here but they certainly wouldn't hurt.
[Magisk] syked:
I've only tried installing it via TWRP.

The Beelink GT-KING device uses Android 9.0 and Amlogic CPU.

[MENTION=4544860]osm0sis[/MENTION] and [MENTION=8126387]martyfender[/MENTION] here is the boot img of my GT-KING.

https://drive.google.com/open?id=1DeY8ZaJy4Z3nQsMx-IC-l3pl2E-88zx0

Note this device comes pre-rooted with with stock rom.

---------- Post added at 12:58 AM ---------- Previous post was at 12:47 AM ----------

[MENTION=6617276]ktmom[/MENTION] the device is a beelink GT-KING. It uses Amlogic CPU and runs Android 9.0 It is default pre-rooted by want to run magisk so I have magisk hide.

I have tried to flash Magisk 20.1 via TWRP. The flashing goes successful but then Magisk manager shows that Magisk is not installed. Also Magisk removed default root and root checker now shows the device is not rooted.

[MENTION=1855550]mrvanity[/MENTION] also has a similar device - the beelink GT1 which also uses Amlogic CPU and has tried running the canary build but same result. He has provided logs later in the post

he also advises that Magisk used to work on his device using Android 8.0
[Magisk] RandomPooka:
Possibly. I'm on a OnePlus 7pro, using stock Oxygen OS, and not a custom ROM with separately flashed gapps.

Could be something with the basic Google-ish framework with MicroG
[Magisk] osm0sis:
So what I gather is these are both A-only devices that were updated from rootfs ramdisks to instead use the original SAR implementation with no ramdisk in the boot.img.

Like I said above that's the same issue as the Nvidia Shield TV so you guys should probably add your device info, boot.img files and logs there to gather them and show it's a wider issue: https://github.com/topjohnwu/Magisk/issues/2063#issuecomment-558266030

Do your devices have a recovery partition? Patching it using "Recovery Mode" per the Samsung instructions and booting to it might work.
[Magisk] syked:
Yes using the recovery image in magisk manager works a treat and when I boot to "recovery" it shows magisk is correctly installed.

However, even though I've used magisk hide for a particular app, it still detects root so I'm guessing it is still detecting OEM root.

If I remove that that OEM root, is there any way to boot into "magisk recovery" by default without having to load up the actual system first?
[Magisk] Be4st187:
That worked. Thank you.

Not sure if the canary build is responsible, but I no longer have issues with play store license verification runtime with MicroG. Before it would say I needed to rebuy paid aops, and nothivng anyone said fixed it. Now license verification works after flashing Canary and I can download my paid apps once more.
[Magisk] masdaster:
Hello,

Just a little question regarding the last Magisk update. After installing it, Magisk starts an activity after each boot and closes immediately. Maybe this is only a little bit annoying for me because I've protected the entire app startup with my fingerprint. So after booting I've to unlock the screen and unlock Magisk showing up. Is this 'popup' a normal behavior? Before the latest update there wasn't such a startup.

Thanks in advance for your help!

OS: MIUI 10 based on Android 9

Magisk Manager: 7.4.0

Magisk: 20.1

Magisk Manager is hidden with repacked package.