yashsingh1/xdaforums huggingface dataset:
[Magisk] xringo:
Is there any reason why my pixel 2 xl bootlooped when I patched boot.img?

I was on android 8.1 on the newest magisk. I wanted to update to android 11. So I uninstalled magisk from the manager and also selected restore images. Everything went good, no errors and magisk was removed (the app) and rebooted and no issues. I updated my phone to android 11 through the phone settings.

Then downloaded the latest android 11 factory image, took out boot.img (I made sure the factory image matched the one installed on my pixel). I put the boot.img onto my phone, ran it through magisk. Moved to my computer, booted to fastboot and flashed it.

Then it just bootlooped and I had to use the flash-all.bat (without the -w) to get it working.

I want to try again but I feel like it will boot loop again. Am I doing g something wrong?
[Magisk] Didgeridoohan:
First thought would be that you have some Magisk module installed that isn't compatible with A11. You could try installing Magisk and then boot to Android Safe Mode. If that works it's very likely a module that's causing issues (and booting to Safe Mode will disable all modules until you reboot to normal boot and enable them manually). If you don't want to use Safe Mode, you could boot to TWRP and manually disable (or remove) modules by adding a file named "disable" (without the quotes) in the module directory.
[Magisk] xringo:
How do I remove any modules or anything like that? I just want to wipe magisk clean and do a fresh install.

The issue is I uninstalled magisk itself, so the modules should be gone right?
[Magisk] Didgeridoohan:
If you picked "restore images" (as per your previous post) Magisk was not removed. The only thing that happened was that you restored the unpatched boot image and left the rest of Magisk intact (including modules).

There's no need to do a wipe and fresh install if you follow what I said in my last post and disable the modules. But you can always rename the Magisk app .apk file to uninstall.zip and flash it in TWRP. That should remove everything (or restore the stock boot image and manually delete the /data/adb folder and you should be good).
[Magisk] xringo:
Thank you. So I just flash ; twrp-3.5.2_9-0-taimen.img through adb/ fastboot and then boot into recovery through fastboot into recovery, and then install the magisk.zip right?
[Magisk] pndwal:
I concur (I think Safe Mode is likely best option as Complete Uninstall wasn't used).

I think you meant rename apk file to uninstall.zip (above) however. 😜 PW
[Magisk] Didgeridoohan:
Sorry! I did a small but crucial typo: you should rename the .apk to uninstall.zip. I've corrected my post above.

But yeah, otherwise it should be fine (you don't even have to install twrp, you can just boot it with fastboot boot twrp.img).
[Magisk] osm0sis:
Good news is diareuse just reached out and is indeed alive and well, just working on multiple paying jobs in real life. 🙂
[Magisk] Lughnasadh:
I just wanted to add one thing in addition to what others have already said. I noticed you have a Pixel 2 XL. Many people have ended up in a bootloop when "installing" TWRP & Magisk together on Android 11 with this device. I'm not sure if anything has changed with the latest TWRP, but as @Didgeridoohan suggested, you might want to just boot TWRP with fastboot rather than installing it to avoid this.
[Magisk] zgfg:
Btw, with TWRP 3.5.2_9-0 you don't need to rename Magisk apk to zip - TWRP recognizes (and flashes) the file as zip file even with its original apk extension

Screenshots from TWRP below
[Magisk] xringo:
Thanks managed to get magisk and android 11 running on my pixel.
[Magisk] 73sydney:
Yup, fastbooting TWRP on the Pixel 2XL is still a good idea
[Magisk] 73sydney:
Love this tip, i had no idea.

Saves me keeping two copies of the file (one apk and one zip), and advising people to do the same

Nice!
[Magisk] Stillhard:
News from canyie
[Magisk] pndwal:
Great stuff!

Please could you give source; I couldn't find those comments in his blog or here:

https://github.com/canyie/Magisk/commits/resetprop

From another GitHub page / telegram channel? PW
[Magisk] azaopung257:
Temporary root by diplomatic@XDA

Home URL:

https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213

--------------------------------------------------

armv7l machine

param1: 0x1000, param2: 0x8040, type: 4

Building symbol table

kallsyms_addresses pa 0x40bbfee0

kallsyms_num_syms 53367, addr_count 53367

kallsyms_names pa 0x40bf40d0, size 637850

kallsyms_markers pa 0x40c8fc70

kallsyms_token_table pa 0x40c8ffc0

kallsyms_token_index pa 0x40c90340

Patching credentials

Parsing current_is_single_threaded

c03623c0: MOVW R0, #0x8d50

c03623c4: MOVT R0, #0xc102

init_task VA: 0xc1028d50

Potential list_head tasks at offset 0x290

comm swapper/0 at offset 0x400

Found own task_struct at node 1

cred VA: 0xdaf3aa80

Parsing avc_denied

c0acf4fc: MOVW R12, #0x4278

c0acf500: MOVT R12, #0xc116

selinux_enforcing VA: 0xc1164278

Setting selinux_enforcing

Switched selinux to permissive

starting /system/bin/sh

UID: 0 cap: 3fffffffff selinux: permissive

Returned 0
[Magisk] Stillhard:
It's from here Marvin, but be aware with /fban posts tho 😙
[Magisk] Shxckz:
Anyone here that managed to open the german banking app "Sparkasse Push-TAN" ?

Dont know why but i can open every other app that detects root except Push-Tan.

Right now im using Magiks Alpha b6298f86

My Modules are:

Bluetooth Library Patcher

Busybox for Android NDK

Gpay SQLite Fix

MHPC

Riru

Riru Enhanced Mode

Riru MomoHider

Universal SafetyNet Fix

After installing several modules etc. i always cleaned data from the app or reinstalled it so i can test properly

I actually have a way to open the banking app by freezing the magisk app with AirFrozen but maybe someone knows a way where i can skip this step?

Thanks for any reply!
[Magisk] rodken:
Remove MomoHider and replace with this version. You can also try SudoHide. After which, only disable GPay SQlite Fix, hide the Magisk App and restart device. If you are utilizing a older version of USNF, try the updated version.
[Magisk] Shxckz:
Thank you for the reply, i already have that modded version where he creates the needed files.

For SudoHide i need LSposed right ?

Tried with GPay SQLite off but still doesnt work. USNF is on the latest version. Magisk is already hidden with a different name.

I guess i still have to freeze the app (which is obv not a big deal, but would be nice when i have "the perfect" setup :D)

Again thank you @rodken :)
[Magisk] rodken:
Just trying to throw a few ideas your way. Whatever will stick - will stick including but not limited to this old school module.

There have been instances where Xprivacy with RootCloak, might hide root detection.

But XprivacyLua doesn't.
[Magisk] Shxckz:
I used that back in the days, is that compatible with Lsposed and android 11 ? :D
[Magisk] rodken:
Yes, tested and confirmed.
[Magisk] pndwal:
Thought I'd give this a try for kicks.

Installed this one:

https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan

Hope it's the same; loads, then immediately asks to open in browser...

Initially allowed to open in Chrome:

Next, allowed to open in Mi Browser:

Not sure why it detects 'security issues / root' in Chrome but not in Mi Browser, but using alternative browser may be your answer.

I also rebooted with no Unshare / MomoHider module enabled, and still had success with Mi Browser.

I am running latest Alpha Magisk on stock MIUI (Android 10) Redmi Note 8T at present, and pass SafetyNet simply with Google Play Services SafetyNet process selected in denylist and Universal SafetyNet Fix 2.1.1 (+ Riru).

Further, this also works in Mi Browser without S Push-TAN selected in denylist (/ hidelist), and without Magisk App hidden.

Hope it helps. 😎 PW
[Magisk] Shxckz:
Nice how fast you got it working :D

So just to make everything clear, you only used these things

Magisk Alpha latest version (i guess cb4361b7)

Riru + USNF Module

Mi Browser as a standard browser

Did you delete app data asweel while changing the standard browser to mi ?

Thank you very much for trying :)

EDIT: I have a Note 10+, i tried Chrome, Firefox, Edge, Opera, Samsung standard browser, all didnt work, pushtan always opens the browser and say "yooo you are rooted bro"
[Magisk] pndwal:
Actually, just realized it's the auto-translate function that's bypassing the detection page... If I select 'go to original URL' I get (German):

Not sure if this trick would work for all S Push-TAN functions... I somehow doubt it...

- No browser set as default (just selecting 'Open with Mi Browser' when asked).

- No data-clear needed.

😜 PW
[Magisk] Shxckz:
Ok i think there is a misunderstanding between us. The app doesnt suppose to open the browser at all, when it does it detects root. You should be able to open the app, configure it like putting a password and co.

What i understand is, it always opens the browser for you right ?

Thank you for taking the time testing it btw :)
[Magisk] pndwal:
Ah, yes; "loads, then immediately asks to open in browser" as I said initially... I did wonder if that was normal which is why I described this behavior...

Sorry I'm unfamiliar with this app / didn't test further...

Re. detection countermeasures, you may be able to find / use an older S Push-TAN app.

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

Also, try with Magisk App uninstalled (you won't loose settings / modules) as even 'Hide the Magisk App' doesn't work for some bank apps.

All best! 😜 PW

Edit:

Also working:

Airfrozen / Ice box methods:

https://xdaforums.com/t/magisk-hide-guide-s-pushtan-app-maybe-more.4294761/

Recent Investigation / Solution (Magisk issue 1084)

Seems Push-TAN is simply detecting Magisk App which is why freezing this works, but 'Hide the Magisk App' alone is not enough as with that

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-893367674

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892775076

So stub app actually needs to be rebuild

Simply put, "a simple app packer [does] mitigate the detection very easily"

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892224424

However simple use of luckypatcher and likes won't be enough (May alter file hash signatures, but you "have to know which code patterns are detected to patch the right location"):

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-926617321

... At least this seems to identify the issue clearly! (Issue is closed, but last post is only 5 days old.)

Hope it helps. 🤠 PW
[Magisk] ipdev:
Yes and No.

Ran out of time to test tonight.

As you already figured out, it is becoming more common to have to disable the Magisk app.

I am not sure who was the first to suggest this but, it has been repeated quite a bit recently.

I gave it a go.

Thanks to Marvin [ @pndwal ] for the PlayStore link :p

As long as the Magisk app was disabled (in some way) before I opened the the S-pushTAN app, it worked.

I was able to enable the Magisk app and then open the S-pushTAN app again with out issue.

Seems to be an error (fc) if the Magisk app is enabled on the initial open of the S-pushTAN app.

The Magisk app had to be disabled (in some way) on (re)boot or S-push-TAN would also ForceClose.

Again seems to be no problem if Magisk app is enabled after opening S-push-TAN after a (re)boot.​

Cheers. :cowboy:

PS.

I used pm hide since I have not used package manager's hide option before, time to test the difference is between hide and disable. 🙃

PPS.

I was going to post a screen shot or three but..

S-pushTAN blocks screen shots. :rolleyes:
[Magisk] zgfg:
Thanks, interesting. I did know for (Terminal commands, if using through adb prepend adb shell to each command):

pm disable-user / pm enable

pm uninstall -k --user 0 / cmd package install-existing

But learned now also for:

pm hide / pm unhide

Btw, seems there is one more:

pm block / pm unblock

Add the package name to the end for each command

Famous 'freezing' is just pm disable-user

---

Btw I tried with S-push TAN

Since I have the latest Magisk Alpha cb4361b7 (with Zygisk), I added S-push TAN to DenyList.

Then I applied pm hide (screenshots below) and rebooted.

Observe that upon pm hide, Settings / Apps did not find Magisk app anymore (for 'freezing', it will be listed but as disabled)

However, S-push TAN still detects the root for me (for the record, I did not repackage Magisk app and I don't use riru and the stuff)

I tried even by uninstalling and re-installing S-push TAN (it remains in DenyList upon uninstalling)

---

Since I still cannot open S-push TAN, I could not test but if you use (it installs as Magisk module) SmaliPatcher /Allow screenshots in secure apps, you should be able to screenshot in the S-push TAN app (e.g., Chrome in Incognito mode does not allow screenshots but with SmaliPatcher screenshots can be taken):

[MODULE] Smali Patcher 7.4

Smali Patcher WHAT THE HELL IS THIS THING? :: To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then...

xdaforums.com
[Magisk] :
That's my understanding. I had no luck myself. But will try again tomorrow. Its late so i might have screwed up.
[Magisk] H4X0R46:
Just tried it myself, didn't work for me either :/
[Magisk] cohiba90:
Hidemagisk is unchecked and when i checked the option and i reboot, it still have the same problem. The box is again unchecked.

Do you know what i mean?

Thanks
[Magisk] H4X0R46:
Oh! I missed this post! So this basically means that magisk isn't going to work. Basically means this is broken? I sure hope Google didn't take that route, so many people have their bootloaders unlocked, me as well as all of XDA.

[MENTION=7135029]babalou62[/MENTION]
[Magisk] Syaani:
According to many reports by users it might be so

https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
[Magisk] Rhoban:
Google are trying to make bypassing SafetyNet pretty much impossible.

Which they will surely achieve at some point.
[Magisk] chudy_85:
Correct information

Uninstall all supersu, magisk and xposed

Flash magisk v8

Flash phhs 259r systemless

Reboot device

Install magisk manager and open

Go to settings and select hidemagisk

Reboot device

Check safety net

HUAWEI MT7-L09
[Magisk] H4X0R46:
Is it the phh superuser found here? http://xdaforums.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
[Magisk] Didgeridoohan:
I got a bootloop after trying to flash a Magisk module yesterday (BusyBox from the modules collection). No worries... Flashed uninstaller and reflashed - everything's back to normal, almost.

Somehow, all my app permissions got reset in the process. Has anyone else experienced this? Any thoughts?

Nexus 6

Stock Android 7.0 NBD90Z, Franco kernel r54

Magisk v8 with Magisk compatible phh's SuperUser r259
[Magisk] xeGox:
Hi friend...can I use MAGISK to use Xposed modules on stock MIUI ROM (MIUI 8 Android 5.1) without custom recovery?

I have a Xiaomi Redmi 3 and it has dm-verity. I can't have custom recovery AND original rom.

When I update original rom with twrp installed, it goes in bootloop

Inviato dal mio Redmi 3 utilizzando Tapatalk
[Magisk] Dalamar666:
Hi all

this is my configuration for avoid problems with safetynet

Suhide 0.54

Xposed 86.6

Magisk 7

Unlocked bootloader

Root off with root switch WITH "stop all su daemons"

Nexus 5, elementalX kernel, xtrafactory (near to stock) 6.0.1 MM

My questions:

If I flash now Magisk 8 and check Hidemagisk, could I pass safetynet whithout root switch?

I had to uninstall anything before flash Magisk8?

Hidemagisk is compatible with suhide/supersu, or only with phh's superuser?

thanks!

edit: "It cannot hide SuperSU, it cannot hide Xposed." from OP. Sorry
[Magisk] mathy007:
I did get bootloop with that BusyBox module too I think something is wrong with it dont use it for now
[Magisk] putridfoetus:
I too have gotten this. Mostly from flashing a viper|Atmos port I'm working on. SystemUI loses Read Contacts permission, therefore causing bootloop until I uninstall magisk, then constant force closing. Granting the permission from an adb shell stopped the FCs, but there were other system apps that lost some permissions well, and rather than figuring all that out, I just reflashed the factory image.

I don't know what I keep doing wrong, but it seems like putting a mod that adds a lot of files into /system breaks permissions somehow.

As for BusyBox, Magisk has it built in. Just check the box to enable it in the manager.
[Magisk] chudy_85:
Yes this
[Magisk] Didgeridoohan:
Interesting. It's not just me then... What is it in Magisk that can cause this? [MENTION=4470081]topjohnwu[/MENTION]

Yes, I know and have that option checked. None of the verification apps I've tried detect BusyBox though, so I was just doing some testing.
[Magisk] putridfoetus:
Typing busybox in terminal yields not found, but typing toybox shows commands. I guess Magisk's BusyBox is nonstandard.

Edit: just checked /data/magisk/.core/busybox, which is mounted to /data/busybox, and there is no ”busybox” command there, so that's maybe why verifiers aren't showing it as installed.
[Magisk] Didgeridoohan:
Ah... I did see it mounted to data, but didn't catch the missing "busybox". Thank you.
[Magisk] Captain_Throwback:
Just because your device doesn't pass SafetyNet doesn't mean that Magiskhide is broken.

I can confirm that Magiskhide is working fine for me with phh's root, as I have several apps that will tell me if root is detected, and those apps are working fine. However Magiskhide can't (currently) make your device look like it has a locked bootloader (if that is indeed why your device isn't passing SafetyNet), and that's not really what it's for.

On a related note, I reported in another thread that the prop ro.boot.verifiedbootstate seems to be the key on my HTC 10 as to whether SafetyNet passes or not. If this prop reports "green" then SafetyNet passes. If it reports anything else, then it doesn't. I was able to confirm this by manually setting that prop to green, and et voilà it magically passes ;). So that seems to be the key, at least on my HTC Mashmallow devices.
[Magisk] H4X0R46:
I wonder if that's the case for other devices as well! Thanks for that! And yea, you're right, it is stated in the op that Magisk isn't meant for passing safety net, that's just what I was using it for lol hopefully it's possible to pass safety net again in another update.
[Magisk] :
Magisk is working fine here.

But it won't pass safetynet. Only reason i care is because the wife and I play pogo.

Only issue i have with magisk is that it won't accept supersu as in it will remove it. But since the supersu+suhide+rootswitch doesn't work for me anymore i will stay using magisk with phh superuser until i find a way to get pogo going.

Magisk is a really nice project and I'm determined to keep using this.

For me. I can easily get green status in safetynet by removing root. So its a matter of hoping there is a new method of hiding or disabling root.

Only thing i haven't tried was a factory reset but i doubt that has any effect since i can dirty flash or remove root and pass safetynet.
[Magisk] Shxckz:
I saw that post several times a few days ago, read a bit yesterday too but had to sleep due work.

I dont know if he actually managed to get the app working, i replied and asked him :P

Again thank you and you dont need to apologize, i appreciate ur time :)

So now i need to learn which patterns S-Pushtan is detecting and building the app with e.g. Android Studio and change minor things with a hex editor.

I guess that will take some time but funny to learn :D

And yes i can confirm that its working, when the magisk app is NOT installed. :P
[Magisk] Shxckz:
I actually tried it and here is the result:

I froze the app with AirFrozen and tried to open S-Pushtan to make sure its working. The App doesnt even need his Data or Cache deleted. (It detects root, i close the app ((not force close)), freeze magisk and pushtan opens fine)

After i successfully opened S-Pushtan i let the magisk app frozen and reboot the phone.

And now i cant unfreeze Magisk :D

When i look under my Apps in my settings, i can see my renamed magisk but it says "deactivated".

Dont know which step i did wrong but thats not a big deal since im testing stuff and am about to factory reset this phone anyways (new phone incoming in a few weeks :p)

Thank you guys for testing and sharing ideas/fixes :)

EDIT: Ok wow, i guess ur not talking about freezing the app with airfrozen or something else when you say, you disabled the app right ? :D
[Magisk] rodken:
For future reference, unhide Magisk before freezing it. I have noticed unruly behaviour with Magisk when it's in the hidden state.
[Magisk] F308:
This is exactly what came to my mind during reading this thread.

Magisk controls root access and itself has it.

Freezing it is like a kill.

One can kill himself or someone else but cannot un-kill.

Any comments?
[Magisk] zgfg:
Did you just simply try to uninstall that 'deactivated' Magisk app

It will not affect your Magisk settings (root, MagiskHide, modules)

Later you just install it again and voila
[Magisk] Shxckz:
I just uninstalled my hidden magisk, installed magisk and rebooted with recovery and im rooted again. Thanks you very much :D

i guess i will wait until someone improves magisk hide and will continue to use AirFrozen when i use Pushtan since im not using it 24/7 like youtube :P
[Magisk] Shxckz:
No, sadly i just need to freeze the magisk app with AirFrozen and i can open the Pushtan app again. Isnt LOS 18 Android 11 and LOS 17 Android 10 ? Because on Android 10 every bank app worked for me but i guess its because John stopped improving Magisk Hide :D
[Magisk] zgfg:
Solution was very simple, see the posts #48222 and #48224

And the key points (to be understood!):

- He did not 'kill'' Magisk, but only its front (like its UI) Magisk app

- Even when you uninstall Magisk app, all the Magisk stuff (/data/adb with Magisk database and modules) and Magisk itself still remain and fully run!!!

You can even maintain MagiskHide/DenyList through Command Line Interface - basically you only cannot install new modules or grant root to the new apps
[Magisk] F308:
What If I put module files directly into /data/adb/modules (and there was other directory yet, I don't remember now, cache or similar...)?

I wonder how root permissions are granted.

They have to be stored somewhere then eventually this stuff could be modified manually?
[Magisk] Didgeridoohan:
Installing modules manually is exactly like you say, just create the necessary directories and files in /data/adb/modules (/cache is only used for logs).

To grant root permission manually you'd have to edit magisk.db.
[Magisk] pndwal:
& @Shxckz

I think you guys are both using Alpha builds?

Do you actually have full SafetyNet pass in A11?

Hope you are aware you need to manually add SafetyNet process in Google Play Services to denylist to pass SafetyNet pre Android 11 with John's new commits, and generally will need Main Google Play Services process in addition for Android 11+ (incl LOS 18.1).

So you'll likely need Universal SafetyNet Fix module 2.x (with Riru) as well as MagiskHide Props Config with a certified fingerprint configured (for official LOS & any other custom ROMs that don't include fixes / spoofing internally), PLUS add process(es) to denylist as follows:

For devices where Magisk resides in /sbin (many pre. Android 11), only deny Google Play Services SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main Google Play Services process, com.google.android.gms also.

😎 PW
[Magisk] Shxckz:
I actually never had a Problem with SafetyNet, i always used MHPC (force basic......) and now im also using USNF.

Yes im fully passing SafetyNet, Google Play Store says Device certified :P