yashsingh1/xdaforums huggingface dataset:
[Magisk] rakee:
Have anyone help me?@Davey126 [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] Didgeridoohan:
Please only report for official releases in this thread.
[Magisk] Pandemic:
This is a thread for beta !!
[Magisk] adel alsayed:
Can i install latest version 16.7 on s7 edge G-935FD 8.0 CUSTOME ROM
[Magisk] Didgeridoohan:
Yes it is. And that user is using an

unofficial

build.

Magisk unofficial(20180728) daemon started

This is the

official

beta thread...
[Magisk] kantjer:
That is exactly why I added "unofficial" to the naming of my builds, to prevent these situations.
[Magisk] pxrave:
Can I downgrade from beta to stable?
[Magisk] Dreamer(3MF):
Yes, But The Main Question Is "Does The Stable Version Suit Your Device/Rom/Kernel?".
[Magisk] pxrave:
I think so

Android 8.0 oos 5.0.4 oneplus 3

What do u think
[Magisk] Dreamer(3MF):
Try Magisk-v16.3.1-Testing(ThePatchedBinary).
[Magisk] angelillom:
Sorry I use Google translator

Perdon utilizo traductor Google

Install Magisk latest version on my Huawei P20 Lite and I fail the SafetyNet, I worked on a test but now it fails ctsProfile: false and basicintegrity: false

Please Help and THANK YOU

Instale Magisk ultima version en mi Huawei P20 Lite y me falla el SafetyNet , me funciono en una prueba pero ahora falla ctsProfile:false y basicintegrity:false

Porfavor Ayuda y MUCHAS GRACIAS
[Magisk] Oswald Boelcke:
I'm absolutely convinced you can. I'd just flash the Magisk-uninstaller-zip followed by your desired Magisk version in TWRP.

What did you do during "your test"? How did "your test" look like? Are you also using Xposed? Logs???
[Magisk] kunaldas65:
installed magisk 16.7.everything like root permission is okay but no module is working
[Magisk] kunaldas65:
this log is when i flash 16.4 and all module working..

in this log you can see some kind of bind mount command is running...which not run when i flash 16.7

please see this [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Aguys:
Although my system partition heavily modified, I always passed safetynet check (cts & basicintegrity true) using previous magisk version.

Then I updated to magisk 16.7, now safetynet check failed (cts & basicintegrity false). I have to disable and re-enable Magisk Hide option several time til I get safetynet passed successfully, but it fails again after reboot.

Logs attached (hope it helps). Note: xposed not installed.
[Magisk] Rylsm:
Hello there,

I'm not sure what causing it but sometimes I lost the root access so I need to reboot my device at least once a day.

I've read the release note about the invincible mode but unfortunately it doesn't work for me and leave my device rootless until I reboot.

I tried to grab the logs by rebooting to recovery and extract the log file from /cache/ but I don't see any errors or warning in that log. Is there another log file that I can take a look at?

I'm using Magisk v.16.9 (1671) with Xiaomi Redmi Note 5 (codename whyred).

This root access issue can be found with various custom ROMs available for my device except MIUI since I don't really want to use it.
[Magisk] pxrave:
Mostly its simple

Delete magst manager app cache and settings

Reboot

Open app and untick magisk hide... Reboot

Do verification test again and it should work
[Magisk] manudhomra:
I'm on oos android 9 beta ROM one OnePlus 6. I'm facing problem with magisk. On 16.4 and 16.7 I have same issue.

Magisk manager shows magisk not installed. But after rebooting the device everything back to normal and shows magisk installed. Is there any solution for this issue????
[Magisk] unarj:
same, running DP3. everything seems to work for me, although the force encryption and avb 2.0 boxes don't stay checked (doesn't seem to affect usage).
[Magisk] Divyas:
Hello,

I've been having problems with 2 out of my 3 bank apps today where they are detecting root, Santander and Halifax.

My device is an LG V20 H990DS on Android 7.0 and all 3 apps were working with Magisk 16.7 and Magisk App hidden while using magisk hide up until today. I've checked the apps to see if they were updated recently on the Play Store and the Halifax app is the latest with an update 2 weeks ago so that's not the problem.

I've tried uninstalling Magisk and reinstalling 16.0, 16.3 and 16.7, clearing app cache and clearing device cache/dalvik but nothing is working. I think my device has been flagged by these 2 apps because one mentions it has been flagged. I wonder if there is some new server side checks happening when logging on.

Anyone got an alternative of hiding root or a way of getting logs to see what's happening? Kinda sucks because I need root to stop my screen retention problems.
[Magisk] mobileman88:
Try Magisk core only mode. Then reinstall those apps and hide them
[Magisk] guest4711:
Try MagiskHide_Props_Config Magisk module.
[Magisk] casouzaj:
You could also try to pinpoint any 'offended' sub-process(es) of the app(s) accusing that your phone is rooted, by launching either any terminal emulator app or through adb shell command with your phone connected to your PC, then typing in:

logcat | grep app_or_part_of_app_name

Based upon the results, for each sub-process you found, type in:

magiskhide --add pinpointed_sub_process
[Magisk] jacknb1ack:
Installing via twrp is completed, but magisk not working

EDIT : Fixed by format data ... still don't know what caused it though ...

help,

i've installed magisk 16.7 via twrp, after reboot, there is no magiskmanager app and root is not working, but my banking app detected root.

device : xiaomi mi 6

rom : lineageos 15.1 officiall latest

twrp : 3.2.2-2 shevt

recovery.log attached. anything else needed ?

thank you
[Magisk] angelillom:
HUAWEI P 20 Lite ROOT

Traductor Google

I do not have Xposed installed and only install Magisk by means of ADB Minimal even if I have the TWRP that also installs it in ADB, please note that the Huawei P20 Lite is new

The fact is that SafetyNet does not work, neither of the two

THANKS and I hope help

No tengo Xposed instalado y solo instale Magisk por medio de ADB Minimal aun teniendo el TWRP que también lo instale en ADB , date cuenta que el Huawei P20 Lite es nuevo

El caso es que el SafetyNet no funciona , ninguno de los dos

GRACIAS y espero ayuda
[Magisk] Dreamer(3MF):
To Fix Uncertified Status In PlayStore & Pass The SafetyNet, Download DeviceSpoofingTool4Magisk From This Thread https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Do What Are Mentioned In The General Steps.
[Magisk] bonyjose:
+1

i am on lineage os 15.1 in my device mi a1 and installed latest magisk beta, but since it's an A/B partition device, i am losing magisk installation everytime after doing seamless OTA update. please consider fixing this issue. thanks. :)
[Magisk] Divyas:
Thanks for trying to help, none of these methods have worked sadly.

I've found another thread where a bunch of people are having the same issue. here

One guy got it working again temporarily by using Magisk 16.7.2 but it has stopped working again. It seems like something new is happening to detect root even though the app hasn't been updated since 18th June.
[Magisk] Triviox:
I update to 16.7 in Galaxy S5 Android 8.1 (LineageOS 15.1) and all works OK.

Thanks for this great work!
[Magisk] milomak:
if the first command of the above returns

# logcat | grep barclays
08-02 15:52:21.414 2593 3573 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity (has extras)} from uid 10020
08-02 15:52:21.468 2593 3573 I ActivityManager: Start proc 7387:com.barclays.absa.banking/u0a246 for activity com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity
08-02 15:52:26.154 2593 3550 I ActivityManager: START u0 {cmp=com.barclays.absa.banking/.phone.login.RootTamperActivity} from uid 10246
08-02 15:52:43.774 2593 2623 I ActivityManager: Killing 7387:com.barclays.absa.banking/u0a246 (adj 900): remove task
08-02 15:55:43.888 2593 8529 I ActivityManager: Start proc 13441:com.barclays.absa.banking/u0a246 for service com.barclays.absa.banking/com.firebase.jobdispatcher.GooglePlayReceiver
08-02 15:55:43.891 1954 2271 I Magisk : proc_monitor: com.barclays.absa.banking
08-02 15:55:44.328 13441 13462 I FA : adb shell setprop debug.firebase.analytics.app com.barclays.absa.banking
08-02 15:55:45.803 13441 13441 I Guard : [Guard 'rvg_1'] Verify with APK path /data/app/com.barclays.absa.banking-5qf287vTFSKJg9192bRx4Q==/base.apk

what do for the 2nd part?
[Magisk] casouzaj:
Do you pass both Safetynet tests in Magisk Manager?
[Magisk] milomak:
Yes

And the app is in Magisk Hide
[Magisk] casouzaj:
Does your phone show as certified in Play Store' settings?
[Magisk] milomak:
Yes
[Magisk] casouzaj:
An attempt:

magiskhide --add activity com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity
[Magisk] milomak:
thanks. you've put me in the right direction.

i don't want to clutter this thread. is there a thread where "troublesome" apps are discussed?
[Magisk] casouzaj:
Does this post (and the thread it is from, of course) help? https://xdaforums.com/showpost.php?p=76200861&postcount=169
[Magisk] milomak:
i'll have a look thanks
[Magisk] guitarjorge24:
How to Root Xiaomi Mi 8 Global Stable OEAMIFA ROM?

I have successfully flashed the MIUI 9.5 Global Stable V9.5.13.0.OEAMIFA ROM for Mi 8. I have also flashed TWRP-3.2.2-0711 successfully. However after I install Magisk v16 the phone bootloops and boots to TWRP. If I try to install SuperSU I get a "patching sepolicy" failure. Has anyone with a Mi 8 and the Global Stable ROM been able to root their phone? Ideally, I want to use Magisk instead of SuperSU because it still allows me to use features like Android Pay.

Does it matter which ROM I have (China or Global) for rooting? or does that not make a difference?

I used the instructions from these 2 sites:

https://www.theandroidsoul.com/xiaomi-mi-8-root/

https://www.cyanogenmods.org/for ... d-root-xiaomi-mi-8/
[Magisk] angelillom:
HUAWEI P 20 Lite

Translator Google

I'll try and tell you, MANY THANK YOU Mate

Probare y te cuento ,MUCHAS GRACIAS Compañero
[Magisk] jakson7474:
Where to request a module, if it is here I would like a module that would disable the location completely so that no application uses my location
[Magisk] Artim_96:
1. There is no place you can request anything. You can only ask for help building your own module, but only in the main thread. This is strictly just for problems with Magisk beta

2. Just use the app permission dialog.

3. For a bit more control get App Ops from play store (by Xingchen & Rikka), you can get a "system plugin" inside that you just use with Magisk
[Magisk] dreamland2000:
Any thoughts about this?
[Magisk] Didgeridoohan:
If you're trying to install Magisk v16.0 you're in the wrong thread. This is the beta development thread... And general installation issues are usually best kept in the General Support thread.

Device specific questions are usually best asked in the specific device forum though, so you might want to start there.

When asking for help it can also be good to provide relevant logs with your query.

Good luck.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Cannot_check_SafetyNet
[Magisk] dreamland2000:
I've noticed that magisk hide has also stopped working since yesterday 02/08. I've done clean installs etc but still won't allow banking app or gpay to work. I'm on the latest beta and this apps were working fine before yesterday.
[Magisk] caeter:
Magisk Manager app can be detected by my Banking app.

It always crashes for "security reasons" but works as soon as you uninstall the Manager app.

Is there a way to hide the Manager app?

https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=de
[Magisk] guest4711:
Repack MM using MM-Settings-Hide Magisk Manager
[Magisk] caeter:
Thanks, that did the trick!

I didn't even know this feature :)
[Magisk] saulin78:
I'm on a Nvidia Shield Android TV and Magisk 16.0, when I reboot Magisk does not remember what I granted or denied root access for and asks me again.

Can I install v16.7 on top of v16.0 and does v16.7 fix this issue?
[Magisk] jacob019:
[MENTION=9343800]tripinva[/MENTION], [MENTION=6252833]Fersho[/MENTION]

It is not necessary to flash the no-verity kernel anymore with the latest Magisk BETA (v16.7), follow the other instructions, but skip the kernel (boot) flashing. It will work.
[Magisk] igos2:
hi,

Does the latest version of Magisk trip the knox counter to 0x1 on a new/never rooter samsung galaxy s8+ exynos version when rooter with the ADB method ?
[Magisk] RandomPooka:
Doesn't just looking at the phone sideways trip that counter?
[Magisk] guitarjorge24:
I see, thank you. I also tried Magisk v16.7 BETA but it didnt work. It still resulted in a bootloop.
[Magisk] igos2:
not very helpfull
[Magisk] DanGLES3:
Here's the answer :it will trip knox no matter what as knox detects any changes made on the kernel (and guess where magisk is installed?) magisk can spoof knox to some extent but its not perfect and some apps will refuse to work with the tripped knox
[Magisk] RandomPooka:
Yeah, I apologize for the sarcasm. But, I thought it was painfully obvious that you'd be tripping the knox counter. I honestly assumed that the counter would have been tripped just by the steps taken to get to a point where you can install Magisk, even if you never actually went through with installing it.
[Magisk] gametimebrizzle:
Yes. Just go to settings in Magisk and change the build channel back to 'stable' (from 'beta'), then just install Magisk from MagiskManager.

A cleaner way would be to flash the Magisk uninstaller in TWRP to uninstall your current build - then wipe cache/Dalvik. Then flash Magisk stable (currently 16.0)

---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------

The fact that your banking app is FCing is a GOOD THING.

Dont do your banking on your phone. Definitely don't do your banking on a ROOTED mobile phone.

Unless, of course, you want your ? stolen by a 14 year old script kiddie.
[Magisk] H0wdy:
After I flash magisk on Pixel XL with P DP5, through TWRP, my phone cannot boot till I flash Android P's boot.img.

What to do?
[Magisk] Artim_96:
Maybe play around with the two options in Magisk manager. Otherwise make a proper bug report so it can be fixed
[Magisk] snsone:
Working fine here, i flashed it after initial boot, with setup not completed yet.
[Magisk] H0wdy:
I just installed magisk manager, rebooted to recovery and flashed 16.7 again.

G symbol is there, horizontal bar showing loading, eventually it reboots to recovery.

"Can't load android system. your data may be corrupted."

I have to flash boot.img from DP5 to get it booting again.

I have android P DP5, Verizon Pixel XL, now unlocked.

Which TWRP to use? I'm using latest.
[Magisk] snsone:
I have thr unlocked model, maybe that's why it worked.

Twrp 3.2.2.0 I have used

My method was flash-all command for dp5. Let it boot into the setup screen. Restart to twrp, install magisk 16.7 and then back into system.
[Magisk] H0wdy:
I used this today:

https://xdaforums.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030/page35

So I got it unlocked. But I'm having the other issues.

Now it's just stuck on the Google G screen forever, with horizontal bar moving. I'm going to have to flash boot.img again.
[Magisk] Homeboy76:
flash-all DP5 (to keep data remove -w)

boot twrp

Install twrp

Install magisk 16.7

Reboot system
[Magisk] H0wdy:
Hi,

Thanks.

I did exactly what you just suggested, and the same thing happened. It had the G for Google logo for a while with horizontal progress bar, then rebooted and went to recovery, just like before.

If I don't do magisk, it boots.

Any other ideas?
[Magisk] Homeboy76:
No :(
[Magisk] DB126:
Not really. Device security is clearly important but represents just one layer in a well designed (multilayered) approach to information security. The banking account should be protected with a complex password and multi-factor authentication that has no dependencies on the device in question. Of course, most people simply SMS 2nd factor codes to their phone or use an onboard authenticator which defeats the protection if a bad actor acquires the device. It's really a behavioral vs technical liability using a rooted device for sensitive transactions.

OT for this BETA thread; moving on. :)
[Magisk] exnokiafan:
Hi guys, I'm having serious troubles.

Galaxy S7 Oreo ERG2. I'm tryin to flash TWRP, remove encryption and then root with Magisk 16.

Many peole report that Magisk is the center of the problem because it triggers encryption back to it's default annoying state.

I'm stuck with a non rooted S7, now.

Any advice, excluding not to root?
[Magisk] Seagold:
Is ur device currently running ? fine?
[Magisk] exnokiafan:
Absolutely fine. 100% stock with a tripped knox counter, but yes super fine. Anyway, I need to root it but I don't have the time to try this and that and flash it many times.
[Magisk] Eleo:
If you don't have time, then don't do it. Do it only when you have enough time to read and understand. It is better than doing in haste and breaking it over.

Good luck.
[Magisk] jcmm11:
Get a copy of the boot image. Install Magisk Manager. Start Magisk Manager, uncheck 'force encryption', patch the boot image. Install the patched boot image.
[Magisk] gametimebrizzle:
Good point I guess.

Now if only we could get the AVERAGE person to understand infosec to your degree of expertise, then we'd be in business.

BETA or final release, my (unsolicited) advice is still the same: Don't do your banking on your mobile device, especially if your device has been intentionally modified to bypass built in SECURITY features.

Take it or leave it, I'm indifferent, I just know I'll sleep better knowing I at least tried to save someone the headache of being the victim of identity theft or getting a baking Trojan.

Just trying to look out for our fellow XDA members, I don't really care who can piss the furthest.
[Magisk] exnokiafan:
Sent you a PM :)
[Magisk] jcmm11:
Replying in thread.

Yes and yes. When you click install, in Magisk Manager, then install again you'll be presented with 3 options.

Download zip

Patch boot image

Direct install

This would be the 2nd option. You can find instructions in the release thread https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] 587.saboor:
[MENTION=4470081]topjohnwu[/MENTION]

Any luck on the imei and sim problem on the a8(+) 2018 oreo?
[Magisk] gd6noob:
Im having troubles rooting my P20 Pro..

Its saying

ctsprofile:false

Anyone know how to correct this?
[Magisk] DanGLES3:
Try the magiskhide props module (read the module instructions)
[Magisk] BubuXP:
I'm trying to patch the boot.img of the Mi A2 Lite with Magisk 16.7 (the only version that works with the A/B partitions scheme), because there isn't still TWRP.

I can only patch it with 16.0 from Magisk Manager, there is a way to force Manager to use the 16.7 version? I've already searched but I can't find anything (maybe I'm not searching with the right keywords).
[Magisk] pendor24:
Look at page 1 donload
[Magisk] BubuXP:
No, I already downloaded it. I need to force the Magisk Manager installed in my phone (Redmi Note 4 with LOS) to patch the boot.img from another phone (Mi A2 Lite) with Magisk 16.7

Magisk Manager will always patch the boot.img with Magisk 16.0 even when in the phone is installed 16.7, and I cannot find a way to tell Manager to use 16.7 instead of 16.0.
[Magisk] Didgeridoohan:
Manager settings - Update Channel - Change to beta.
[Magisk] BubuXP:
facepalm.jpg

Thank you very much, I missed totally that. Now everything works fine.

Except that in Mi A2 Lite (Android vanilla) both unzip and BusyBox are missing and Magisk cannot install any module. I could install the BusyBox module via TWRP but custom recoveries still don't exist (too young device). Do you know if there is a way to add the module to a boot.img file? It's not important, I can always download BusyBox from the Play Store, then install the BusyBox module and then remove the Play Store BusyBox.

EDIT: I was sure modules where installed in the boot partition, but after reading some posts in the forum, I can say that I was wrong.
[Magisk] martyfender:
If you can't install modules through either the Magisk Manager's downloads or add module function, it looks like your installation could be broken. Magisk has it's own, built in busybox and if I am not mistaken, unzip function.
[Magisk] Bytegeist:
safetynet cts mismatch

Hello,

I have a OnePlus 6 with the newest Android P beta. I'm also using the newest twrp version.

Magisk installs fine, and it works perfectly. My only problem is SafetyNet, where it passes everything but the ctsProfile which always reports a mismatch.

I attached both magisk.log as well as the older magisk.log.bak on this post.

Thanks in advance.
[Magisk] Dreamer(3MF):
For Passing The SafetyNet & Certifying The Device, Download DeviceSpoofingTool4Magisk From This Thread https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Do What Are Mentioned In The General Steps.

For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v16.7(1671).
[Magisk] BubuXP:
To have a fresh start, I erased userdata partition in fastboot, flashed the stock ROM (Android One device, so it's Android vanilla 8.1), then I flashed the patched boot.img (no TWRP for Mi A2 Lite at the moment), then I installed Magisk Manager apk.

Then I rebooted, I connected to the internet and download some modules. One module says "cannot unzip", the other two say "please install Magisk 15.0+". Logs attached.

If I install BusyBox by Stericson the modules install without problems. Root works fine and also SafetyNet is perfect.
[Magisk] Parnas72:
Hi, you could be facing incompatibilies of those modules with the beta version of Magisk. In this case there is nothing to do but wait for the developers to fix it.

Have you tried running the stable version 16.0, just for a confirmation ? I know it's got issues with A/B devices, but in the end it works. Only problem is it randomly bootloops when you restart the phone, when that happens you just need to force the reboot again. :)
[Magisk] BubuXP:
I exclude incompatibilities, because I use the same modules on the same 16.7 version on Redmi Note 4 with LOS. And every extension I try to install it gives error. I also tried 16.0 before experimenting with 16.7, but the problem was always there (I thought it was because 16.0 was incompatible with A/B). I can only wait for developers to check this.

In the meantime I can try to drop an unzip binary in the right system folder via FX root explorer and check if it works (installing BusyBox that comprehend unzip functions, is confirmed working).

EDIT: I resolved reflashing the fastboot ROM under Windows (not under Debian) and using 16.0 :confused:
[Magisk] DenyDarko:
Obviously.

It's a beta rom, Oneplus (or anyone on his right mind) won't pay Google for certification for a beta rom.
[Magisk] elkay:
Anyone else notice Hide not working anymore on the official P release for Pixel 2 XL? Root works fine. Safetynet fails, and also in Manager if you try to check off apps, if you go back in they're back unchecked. All the beta Ps worked fine for me.
[Magisk] bosox284:
Everything seems to be working fine for me. SafetyNet passes and the apps are checked.
[Magisk] elkay:
Fixed. I was using the "official" 16.7. There is a newer release, build 1674, that I installed and it fixed it.
[Magisk] arh2o:
Where did you get build 1674? I searched this thread and Google but no luck. Thanks in advance.
[Magisk] elkay:
Here you go.

https://xdaforums.com/pixel-2-xl/de...ernel-1-00-t3702057/post77240449#post77240449

Hope this helps.
[Magisk] Bytegeist:
So it's unrelated to Magisk or TWRP? In that case I'm relieved.
[Magisk] DenyDarko:
Yep.

Either rollback or wait for the stable release if you need safetynet.
[Magisk] Bytegeist:
Nope, I'm good. Just wanted to know where the issue was.

Thanks!
[Magisk] fearfighters:
I have this exact issue! Was on 16.4, and when I changed to 16.7 it does exactly what you describe.