yashsingh1/xdaforums huggingface dataset:
[Magisk] co-moi:
After i saw that there is magisk manager 765d5d97 is official diskussed on github i think it is save.

I tried magisk hide on another banking app and it also worked fine!
[Magisk] zgfg:
Please download Magisk and Manager from the official, not from elswhere.

Please check the GitHub instructions for download and installation

Btw, the latest Manager versiom number is 267 for Stable and 283 for Canary

Is it safe - not safe if you don't use the official

Magisk Hide is in Settings as always (for the official Manager), but no more checked in by default - so make sure you check yourself
[Magisk] Didgeridoohan:
Well, just because it's got the same name and version string doesn't mean it is the same apk... I don't think apkmirror has put up any different version from what you can download at GitHub, but the only way to be sure is to compare hashes between the files. Easier and safer to just download from the right source to start with.
[Magisk] co-moi:
I uninstalled magisk manager right now, than i downloaded the newest version from the official github and see

Tells me 267 is the newest version
[Magisk] Didgeridoohan:
Latest stable release, yes. Canary is currently at build 283.
[Magisk] esemef:
I'm having problems with this app, apkcombo.com/the-co-operative-bank/com.cooperativebank.bank/download/apk

It seems that once it has detected root, it stores something somewhere in the current user & so deleting it and re-installing it doesn't make any difference.

Does anyone know how to find out how to work round it?
[Magisk] Didgeridoohan:
I don't think so... I just tested it (downloaded from Play Store). I let it detect root once (it refused to start because my device didn't meet the minimum security bla bla), but as soon as I added it to the Hide list it started without issue.

Tested on a OP3T, Android 9, Canary Magisk 20407 with hidden Manager 283.

Could be something about your setup. As always, some tips can be found here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] esemef:
Weird, because I'm not even rooted now and it is still complaining and it didn't until I accidentally ran it without masking (I wish the default on install was to mask everything....). Now I'm on lineageos 17.1 I'm not sure I can even run magisk as everyone is reporting bootloops if you have gapps installed.
[Magisk] Didgeridoohan:
If you don't have Magisk to help you hide root etc, it might easily be detecting an unlocked bootloader or certain "dangerous" prop values.

I don't know what you mean about that last part though... You don't need Gapps to use Magisk.
[Magisk] kg3:
Fingerprint unlock for my banking app is not working. The app developers said they don't support Xiaomi. I have hidden app, repackaged magisk and hide props to spoof to various devices but I still can't get it to work. I have enabled all simulation. There must be something else the app detects that says it's a Xiaomi or maybe that I have a custom ROM? Any other suggestions?

I have a Xiaomi Mi 9T and I believe prop 4 causes the camera to pop-up each reboot. Any way to stop this?
[Magisk] ernie1249:
Help installing Magisk on Galaxy S6 Nougat

Please apologize if this matter has been discussed before. But searching the thread did not give a clue. And reading almost 4000 pages would take a week or so ;)

It is routed with CF-Auto-Root-zeroflte...

Magisk Manager installed. Selecting "direct install" MAGISK, installation stops with "bootimage patched by another program". When I try a second time I only get the options "Download ZIP-File" "Auswählen und patchen einer Datei" (Select & patch a file). Never read anything about what file to select & patch.

When installing TWRP to flash the ZIP file, cannot reboot because dm-verify hits. Maybe a boot image without dm-verify would help? Which one?

So I am totally stuck and any help would be very appreciated.
[Magisk] Skyrider:
I can confirm the uninstall does nothing. I can still install phh supersu (without magisk manager) and root still works. Unable to re-install magisk because of bootloops. Like I said, the rw66 hidesu experimental file completely screwed everything up.
[Magisk] Rhoban:
May be. But most ROMs still come with system SuperSU. At least for my device they do.

Though I'm pretty sure it is the same for all devices.

So, unless a ROM comes with systemless SuperSU as standard root, you still have to unroot the ROM first before flashing Magisk.
[Magisk] TheSaiyan:
Why do I always get ignored??? I waited to v7 to be released, tried it and didn't work, it always gives "unable to detect boot" error. What do I have to do to get it working... Or at least to be considered???
[Magisk] wertzPH:
something seems wrong in Magisk-v7 unpack/repack method. its making my device do bootloop at bootlogo. inspecting new-boot.img seems to me the size is smaller than its used to in Magisk-V6 and i am not able to unpack it with any boot repack/unpack tool.
[Magisk] Citizen_Snips:
Providing logs of errors would be a good start, honestly.
[Magisk] WeirdSoup:
OK, I removed phh's SuperUser and flashed SuperSU v2.78 SR1 and suhide v0.53, then installed the Magisk v7 again via manager app(because it said "Magisk is not installed"). Now everything seems fine, and bypassing the SafetyNet also works well.
[Magisk] adrman:
Looks nice. I'm assuming it's still in development as I'm not seeing it yet in the MM module downloads. Once it becomes available, is it best to flash back to the non-suhide version of phh before applying the module?
[Magisk] Didgeridoohan:
Yes, that's correct. If you have system root you have to unroot before installing Magisk.
[Magisk] soder:
Hmm. OK. Then, is it better to go back to the SuperSU systemless root again then, and not use phh's root anylonger?

What is the best way now to redo the whole process?

/Söder
[Magisk] WeirdSoup:
Unfortunately, v7 + suhide can bypass the SafetyNet, but unlike the v6, it can't do that with many other banking/game apps. I installed the suhide GUI app, but it won't work with many apps. In v6, It was easy to bypass those apps' root detection with the root toggle function.

(Systemless Xposed v86.6 is installed)
[Magisk] soder:
How about Xposed Systemless 86.6, does it work with SuperSU and suhide? I read on the suhide 0.53 site that:

"Xposed is not currently officially supported, but if you want to use it, you must be using [MENTION=4470081]topjohnwu[/MENTION] 's systemless xposed v86.2 exactly"

So, does 86.6 work anyway?

/Söder
[Magisk] Captain_Throwback:
Yes, it does. That post predates the existence of 86.6, and 86.6 added compatibility with suhide. A simple look at the 86.6 change log would've told you this.
[Magisk] philipchoynb:
Hi, I'm not sure am I in the right place to ask these question?

1. What is Magisk? What does it do exactly?

2. What kind of ROM can install this?

3. What is the different to Xposed framework and SuperSU?

4. Is it compatible with Xposed and SuperSU?

Thank you.
[Magisk] cadkey:
Start by reading this mate: http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] rignfool:
Because you need to wipe data for com.android.systemui...

You have some data mismatch issue
[Magisk] CrazyCypher:
No I tried to delete data..the same thing happens, its impossible to boot
[Magisk] bayran321:
How did you remove phh's SuperUser?
[Magisk] WeirdSoup:
Just delete the phh in the magisk manager app's "modules" section(touch the trash icon and reboot), and delete the superuser app. That's all.
[Magisk] edale1:
I haven't been able to find anything about the requirements for phh's hidesu, and haven't had the time to do something that might brick my phone (and thus take an extra 1/2 hour or so unbricking it).

I was hoping someone else on here (hopefully with a lot more Android experience than me) would have already tried to bypass SaftyNet on a 5.11 (Lollypop? yea, I'm that new to Android) device, and knew the answer. Guess I gotta wait a day or two until I have the spare time to experiment with phh's hidesu, and try and figure this out myself...

Also, from the Magisk v7 thread's known not working devices:

What does this mean by "BUMP your boot image", and how do I do it?
[Magisk] :
I flashed phh's superuser but it's not showing in the manager's modules. Any idea why?
[Magisk] JudgeDread11:
I believe Xiaomi had their own system for biometrics, it doesn't use the standard Android approach.

So, if I'm correct, no amount of spoofing will be able to hide that.
[Magisk] meiser:
Hi,

I upgraded from 20.4 to Canary as this properly hides root for TAN2Go. But the negative side effect is that my phone (Xiaomi Mi 9T Pro running self-compiled crDroid 6.5) sometimes doesn't boot if I flash a new ROM and Magisk addon.d script flashes the patched boot.img.

I have to flash the vendor and firmware files again to make it work. I don't know which partition exactly is corrupted by the script.

How could I provide the right logs to fix this issue? I try to get the recovery log the next time and will provide it here. But maybe anything else?

Thanks,

meiser
[Magisk] co-moi:
[MENTION=3150073]meiser[/MENTION] [MENTION=2904561]kg3[/MENTION]

I also use a xiaomi Mi 9t pro and I have this problem with vr bank secure go app, I also think that there will be safed a cookie or something even with trimmer and CCleaner I cannot clean this out that there would not open the browser to go to a stupid site no framwork no root bla bla first it showed me no framwork and uncheckt it in magisk and it was shown no root now all other apps are working only this one goes still to the browser and fails in a not loadable website.

Yes I think there is something saved on my phone and i don't want to do a backup wipe the phone and than install it again on a new environment

---------- Post added at 08:46 AM ---------- Previous post was at 08:46 AM ----------

[/COLOR [MENTION=3150073]meiser[/MENTION]
[MENTION=2904561]kg3[/MENTION]

I also use a xiaomi Mi 9t pro and I have this problem with vr bank secure go app, I also think that there will be safed a cookie or something even with trimmer and CCleaner I cannot clean this out that there would not open the browser to go to a stupid site no framwork no root bla bla first it showed me no framwork and uncheckt it in magisk and it was shown no root now all other apps are working only this one goes still to the browser and fails in a not loadable website.

Yes I think there is something saved on my phone and i don't want to do a backup wipe the phone and than install it again on a new environment
[Magisk] esemef:
It was only magisk that triggered the root error, the app worked perfectly fine before. It works as guest.

I kinda want to know what it actually does check for, because I think it's cached some value in a file somewhere. I'd have thought by now there would be people who have the experience to reverse engineer it, to save me the hassle of figuring it out just for one app.

I understand you don't need gapps, but everyone on lineageos 17.1 with gapps and magisk is reporting boot loops. I couldn't get it to work with magisk on 16.0 either, which is why I believe it has cached a value somewhere.
[Magisk] X46X:
Hi guys I can't pass SafetyNet since yesterday. I don't install anything new, it just stopped working itself when I tried to pay with gPay
[Magisk] Didgeridoohan:
The recovery log would be a good start. Further troubleshooting is likely to be easier after that.
[Magisk] Didgeridoohan:
Both checks or just CTS? Try clearing cache for Play Services.

https://didgeridoohan.com/magisk/MagiskHide#hn_CTS_profile_mismatch_vs_Basic_integrity
[Magisk] Didgeridoohan:
[MENTION=7314739]co-moi[/MENTION] and [MENTION=5377738]esemef[/MENTION]

I've tested both your apps, on Magisk Canary 20407 with hidden Manager 283 and can start them without issue. Even after letting them detect root and without clearing any data for the apps. Just adding them to the Hide list and voilà. As always when posting about stuff like this, I'll leave a link to my guide on this stuff:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Of course, I can only try up until a login is necessary, so if they're doing something else after that you're on your own...

This suggests that the apps are not saving anything to your device concerning if root has been detected and that you've got something else that triggers the app. Something that Magisk can't hide.

If the app really is saving something somewhere it would either be in its own data directories or on your internal storage (but it'll need storage permission for that, so if it doesn't that's out of the question unless the developers of the app are using some serious, otherwise unknown flaws). Getting rid of the apps data is just a matter of uninstalling it, and to be completely sure reboot before installing it again. If you want to be real sure use SD-Maid or similar as well.

[MENTION=5377738]esemef[/MENTION] The Gapps/Magisk issue on LOS 17.1 could be a device or Gapps version specific thing... I've got LOS 17.1 on two devices, with Pico Gapps and have no issues. Pretty darned old devices mind you, so there might be workarounds and stuff that work in my favour, but still.

[MENTION=7314739]co-moi[/MENTION] And to finish off: neither of the users you mentioned have the issue you're talking about (at least from what we can tell)... They're posting about something else.
[Magisk] Jape12:
I need help I’ve installed Magisk manager but inside the app it say Magisk is not installed n I can’t figure it out. Sry I’m new to this I didn’t think it was going to be so tough but I’ve made it this far I need to see it out
[Magisk] zgfg:
Please start with studying Installation guides:

https://www.didgeridoohan.com/magisk/HomePage

https://github.com/topjohnwu/Magisk/blob/master/README.MD

https://topjohnwu.github.io/Magisk/
[Magisk] X46X:
Both checks, clearing cache not working
[Magisk] Didgeridoohan:
Well, then keep reading in that link I posted and see if you can find something that helps.
[Magisk] ndep:
thanks author for such a marvelous tool! I recently flashed MIUI Rom from xiaomi.eu on my Redmi K30 5G, and flashed magisk, then everything was fine until I dirty flashed an upgrade on May 1 for the latest ROM release. After flashing the ROM I immediately flashed magisk 20.4 recovery zip in TWRP, then I got reboot loop. Clear cache/dalvck, same loop.

So I booted into system without root, and installed Magisk Manager Canary, it's showing my device "A/B: no", while as Castro shows it's actually avaiable. Is this the reason for the trouble? Is it safe to flash Magisk Canary from Manager Canary directly? usually I don't try Canary channel,...
[Magisk] Mlokk9:
Hi everyone My phone is OnePlus 7t pro 10.0.8 AA .. I'm wondering if someone else has the same problem ..

My problem is that after i upgrade the BusyBox to the last version in Magisk after I installed it it says reboot i did , after a few minutes turn on with no data found also the Magisk says it's not installed and the wifi not working also the sim but all the apps still in the phone , i did after that reboot and everything works well also the Magisk work but all the files delete .. please if anyone knows tell me what to do

Thank you
[Magisk] zgfg:
With MIUI, it is usually: SAR Yes, A/B No, Recovery No.

You can also check (see Magisk Installation guide) from Terminal emulator by:

getprop ro.build.system_root_image

getprop ro build.ab_update

And best way is to extract boot.img from recovery/zip package of your MIUI firmware, patch it from Magisk Manager (with the three options as above) and flash it from Fastboot.

So you don't need TWRP (although you can flash the patched image also from TWRP)

Before flashing the patched image you can temporarily boot into to check if all is ok:

fastboot boot magisk_patched.img

(observe there is no flash command here, just boot)

And yes, Canary is fully 'safe'
[Magisk] X46X:
Thanks but nothing helps, maybe google change anything in SafetyNet and we need an update..
[Magisk] Didgeridoohan:
If they had I'm fairly sure we would be seeing many, many more reports. We know they're just waiting to flip the switch on key attestation, but even then Basic integrity would still pass.
[Magisk] zukers:
I'm trying to install Magisk 20.4 on quite old phone HTC M7 AICP 13.1 Oreo, but I get an error:

Unpacking bot image

Unsupported/Uknkown image format

how could I install new version of magisk?
[Magisk] samhhmobil:
A single post is enough...

Nevertheless, for M7 it's recommended to use lineageos-14.1 (Android7.1.2) unofficial build by .:B:.

It's the most stable running system you can get, and it will get frequently security updates.

Gapps and Magisk are working flawlessly with that on the M7 (international version).

If you want to have an "experimental" device, you may try unofficial LineageOS 17.1 (Android 10) even with Gapps and Magisk (it's running for me too).

I tried AICP 13.1 too, and have had day by day just only trouble over trouble.

Just my 2¢,

samhhmobil
[Magisk] zukers:
do you mean this version? https://xdaforums.com/htc-one/orig-development/rom-lineage-os-14-1-t3531331/page142
[Magisk] samhhmobil:
That's it. You found it. Great.

It's working for me as daily driver since more than a year.

samhhmobil
[Magisk] meiser:
Please find attached the recovery log.
[Magisk] casouzaj:
Go to 'Settings > Apps', find Magisk Manager (or whatever name you chose after having it hidden), tap on 'Storage' and, if it's not resinding in the internal storage, move it to there. Then, launch Magisk Manage again and test it out.
[Magisk] lapwat:
Hi,

I am developing a Magisk Module. Some users have an error because zip/curl are not available at the time of installation. How is it possible that some devices include zip/curl commands whereas other devices don't?

What is the best way to have zip/curl commands available during the installation of my module?:

1. Ask users to install the relevant package (if any?)

2. OR Include zip/curl binaries inside the module

Thank you for your time.
[Magisk] Didgeridoohan:
Couple of errors in there that could be part of it. What about if you disable the addon.d script and install Magisk manually after the ROM flash? Any difference (and don't forget to save the log)?
[Magisk] Didgeridoohan:
There are so many different setups that it is impossible to expect all of them to have the same set of tools available. Would be nice though....

You could go with either 1 or 2 IMHBCO, whatever is easiest for you. I've used both variants at different stages with my module, but I've settled on requiring Busybox to be installed (and i of course always recommend [MENTION=4544860]osm0sis[/MENTION] excellent module for that). SInce you want it at install though it might be easiest to just include them, but like I said I think it's best to go with whatever option you find easiest to implement.
[Magisk] lapwat:
The thing is that neither zip nor curl are included inside Busybox. But bzip2 and wget are included. I will use those commands instead and force users to install Busybox by checking that /system/xbin/busybox exists on the device.

Thank you for your help.

EDIT:

Found how you checked for Busybox installation in your module code. Gotta get inspiration from that :)
[Magisk] Lynjun002:
I'm stuck in mAGISK checking for updates I'm using android 10
[Magisk] DiamondJohn:
Since its just for installation, I would include a working binary(s) within your install zip.I have seen Magisk modules that include their own binaries for functions already built into many ROMs. And that is for daily running, not just for the install. If you require people to install busybox, you will end up being asked questions when it fails on their device, or they simply have no idea how to do it or people not understanding that its before not after, or if they use a Magisk based busybox, that its a reboot after etc etc.
[Magisk] meiser:
Since switching to canary, I can't use the power menu entry to reboot to the recovery directly. The phone tries to start the system instead of the recovery and fails. I have to switch it off hardly and start the recovery with the key combination.

There's no change in behaviour if I flash the zip or use the addon.d script. Sadly, I forgot to save the log. :( I'll do the next time.
[Magisk] lyoks:
Hello guys, can help me?

Magisk version above 16.7+ NOT working on alot models ZTE. When i flash magisk (example 20.3), and reboot to system, me return to recovery, and further also.... back to revocery. Any ideas how to fix?

I'am attach logs.
[Magisk] Lunatik4552:
Hey there, I have a Pixel 2 XL on Android 10, April Update.

There was an update for Magisk today (don't remember the version number) but now my phone will only boot to the bootloader. Recovery does not work (I had installed TWRP), restarting brings me back to the bootloader, and my USB-C has an issue with connections.

Any advice? My guess is just keep trying a USB connection until I can flash stock.
[Magisk] Badger50:
You could always fastboot the boot.img again, or just update to the May security release. Then patch the May boot.img, then fastboot it to both slots to regain root :good:
[Magisk] :
Is this normal

I have Google pixie xl I'm using a custom rom called Lineageos 17.1 I have the root function turned off and I'm not using modules if someone going to answer my question please
[Magisk] brambles1234:
I have a Smasung A70 SM-A705FN

I have tried to flash magisk update today and this has resulted in a boot loop for me as well. I have tried to flash magisk via TWRP to rectify this however, I still have the same issue. I woud appreciate any advice as to how I can get my phone to boot normally as I didn't back up my phone and do not wish to lose any of the data.
[Magisk] ooops4:
i installed magisk. i was able to gain root access. i changed my NotoColourEmoji.ttf font file from system and i decided to unroot. then suddenly the file which i changed was also back to normal after unrooting? how did this happen? cant't it be for permanent even after unrooting?
[Magisk] meiser:
Here's the logcat if the reboot to recovery fails. This time, the device tried to boot to system, but didn't finish. A "reboot" via adb shell helped so that the device was up again.
[Magisk] brambles1234:
I need help - I flashed the magisk update today and this resulted in my A70 boot looping. Afterwards I tried to flash the Magisk zip file via TWRP however, this did not work. Next I tried to uninstall magisk using the uninstall zip however, it showed an error when flashing that said that 'Magisk is not installed' ?

The TWPR on my A70 is encrypted so I cannot find the original saved boot.img as the folders are jumbled letters and numbers therefore, I am a bit stuck at present and would appreciate some help please, so I don't lose my data on the phone
[Magisk] lyoks:
Guys, can you help me? Post #39854. Magisk 17+ not work on next device:

- ZTE Blade V9

- ZTE Blade V9 Vita

- ZTE Blade A7 Vita

- ZTE Blave V8

- ZTE Blade V8 Mini

- ZTE Blade V8c

- ZTE Blade A6

- ZTE Blade A6 (Claro)

- ZTE Blade A6 (Movistar)

- ZTE Blade A6 Lite

- ZTE Blade A0622 (voyage)

- ZTE Blade A6 MAX

- ZTE Blade A522

- ZTE Blade A520

- ZTE Smart Fresh 5
[Magisk] DiamondJohn:
Did you use a Magisk module to change the font? if so, the module did it systemlessly, ie the system partition was not changed. Otherwise, then yes, the change should be permanent (NB: I have no idea what happens with A/B & system as root devices) you may help others help you by letting them know your device and other details.